Managing an Application
An application is an instance of a deployment archive. It has an independent lifecycle with regard to an AppSpace or AppNode. After completing the design process in TIBCO Business Studio, the application can be deployed.
An application provides the business logic to perform one or more related tasks and contains an application module that was defined in TIBCO Business Studio. The module itself can include processes, subprocesses, a process starter or a process service, and multiple activities. See TIBCO ActiveMatrix BusinessWorks Application Development for information about creating applications in TIBCO Business Studio.
Deployment occurs after an archive is uploaded to a domain and before an application is started. An archive is deployed to an AppSpace. One or more applications can be deployed to an AppSpace.
If an AppSpace spans multiple machines, the application is deployed onto each of the machines. If there are multiple AppNodes attached to the AppSpace either on a single machine or across multiple machines, the start command starts the application on each of the AppNodes. The runtime status of the application is reported for each AppNode and can be monitored using bwadmin.
When an application is deployed, you can choose to also start the application by giving the -as option on the command line. By default, this option is off and the application must be started explicitly after being deployed.
To configure an application, provide the desired profile that should contain the variable values for the application. This step is necessary if you want to run the application with different sets of variables and deploy it with different argument values, for example, for a Windows machine or a Mac.