Mandatory form-data fields

     -F "deploymentFile=@YourDeploymentFileName.properties"

 -v "http://YourSilverFabricBrokerName.com:<port>/livecluster/rest/v1/sf/engines/archives"

Where the default http <port> is 8080 and optional form-data fields can specify other continuous deployment behavior.

Where your archive application deploys and what it is called depends on what you specify with AppName. For example, when you use TIBCO Designer to create an .ear file with a name such as MyAppArchive, varying the AppName specification gives following behavior:

• If the AppName form-data field is not specified, MyAppArchive is deployed at the top level of the directory.
• If -F "AppName=A" is submitted in the curl request, MyAppArchive is renamed A and deployed at the top level.
• If -F "AppName=A/" is sent, the directory folder A is used or it is created and MyAppArchive is deployed within that subdirectory.
• If -F "AppName=A/B" is sent, the subdirectory A is used or created, and MyAppArchive is deployed there and renamed B.
• If -F "AppName=A/B/" is sent, the folder A with a subfolder B is used or created and MyAppArchive is published within the subfolder B.

The full application name is derived from the AppName directory location and the application archive name as it is deployed.

Optional form-data fields do not need to be specified unless you want to change the default behavior. By default, all archives in the archive file are deployed and started unless an archive of the same name is already deployed and started, in which case that archive is allowed to run without interruption or replacement.

All deployment configuration cURL expressions takes the form:

 -F "AppSettings.element1.element2=SomeValue"

Some examples:

-F "AppSettings.localRepoInstance.encoding=UTF-8"
-F "AppSettings.description=This%20application%20deployment%20is%20for%20validation%20testing."

Where the element is one of the following (plus any subordinate element2 where applicable):

 -F "Archives=Archive_A,Archive_B,Archive_X"

-F "InstanceSettings.initHeapSize=64" 
-F "InstanceSettings.maxHeapSize=512" 
-F "InstanceSettings.threadStackSize=512"

• description: specify any pertinent information about the binding.
• contact: name the person responsible for this application instance.
• startOnBoot: when true, the service instance starts when the computer is restarted. The default value is false.
• enableVerbose: when true, sets the enabler for verbose tracking for service instances. The default value is false.
• maxLogFileSize: sets the maximum size (in kilobytes) that a log file can reach before the engine switches to the next log file.
• maxLogFileCount: specifies the maximum number of log files to use. When the maximum number of log files have been written, the engine begins writing to the first log file again.
• threadCount: specifies the number of threads to use to execute process instances. The number of threads determines how many process instances can execute concurrently.
• prepandClassPath: the values supplied here are prepended to your CLASSPATH environment variable.
• appendClassPath: the items you supply here are appended to your CLASSPATH environment variable.
• initHeapSize: specifies the initial size (in MB) for the JVM used for the process engine. The default is 32 MB.
• maxHeapSize: specifies the maximum size (in MB) for the JVM used for the process engine. The default is 256 MB.
• threadStackSize: specifies the size of the thread stack. The default is 256 KB.
• runAsNT: when set to true the service is run as a Microsoft Windows Service. You can then manage the engine as you would any other service, and you can specify that it starts automatically when the machine reboots.
• startUpType: specifies the instance service startup type as either: Automatic, Manual, or Disabled.
• login: specifies the login account for the service, if any. The domain name must be specified as well.
• password: sets the password for that service, if any.
• checkpoint: when set to true, the process engine waits for all jobs to finish (up to the maximum timeout) before shutting down the engine, rather than remove jobs at their next checkpoint.
• timeout: the maximum timeout in seconds the process engine will wait for jobs to finish before shutting down the engine. A zero (0) value means 0 seconds, which effectively turns the graceful shutdown into an immediate shutdown.
• iv : this element uses a comma-separated string with name-value pairs with each key value pair joined by an equal (=) sign.

 -F "configurationFile=YourConfigurationfile.xml"

Where your XML configuration file should use the same format as an enabler or component level configure.xml file with the outermost XML element as follows:

 <archiveConfig name="YourArchiveName">
    ...
 </archiveConfig>
For more information on writing an archive configuration file, see the "Using the Silver Fabric SDK" chapter of Silver Fabric Developer’s Guide.

 -F "ForceDeploy=true"

 -F "VariableProvider=Some_PROVIDER_Name"

 -F "NoStart=true"