Starting Applications

You can start applications from the GUI or by using the CLI. If the application starts successfully, the runtime state changes to Running.

GUI

When an application is deployed and started, deployment artifacts such as the application, data, data files are created in the folder CONFIG_HOME/data/ext. Do not modify the .tra file of the deployed application

Procedure

  1. Click the Applications button.
  2. In the Applications list, click one or more applications.
  3. Click the Start button.
    If there are target applications, the Application Dependencies to Start dialog displays.
  4. Check the checkboxes next to the target applications to start.
  5. Click Start.
    The target applications are started and the selected applications are started after the target applications are running. The Runtime State of the selected applications changes to Starting.
  6. Click the Refresh button until the Runtime State changes to Running.

Result

The selected applications and target applications are started.

CLI

When an application is deployed and started, deployment artifacts such as the application, data, data files are created in the folder CONFIG_HOME/data/ext. Do not modify the .tra file of the deployed application

Procedure

  1. In the data file, specify Environment and Application elements in base format. Drivers required for the application resource instances can be specified inside the <Application> element in the data.xml file. 
    <Environment xsi:type="amxdata:Environment" name="envName" >
 <Application xsi:type="amxdata:Application" name="test.app1" contact="TIBCO Inc." description="Test application with imported resource template which requires a driver feature" importResourceTemplates="true" resourceTemplatesScope="Application">
		
            <Node name="${dev.node.name}" environmentName="${dev.envt.name}"/>
            <ApplicationTemplate xsi:type="amxdata_reference:ApplicationTemplate_reference" name="AppTemplate"/>
			
			<!-- Specify the resource template in the DAA and the required driver feature. -->
			<Driver resourceTemplateName="OracleResourceTemplate" driverFeatureName="com.tibco.tpcl.gen.oracle.jdbc.feature" driverFeatureVersion="11.2.100.001"/>
			
        </Application>
</Environment>
  2. In the build file set the action attribute of the AMXAdminTask element to start and the objectSelector attribute to Environment/Application. 
    <AMXAdminTask action="start" objectSelector="Environment/Application" />
  3. Optionally, specify that the startPreFlight operation be performed before starting the application. The startPreFlight operation ensures that all target applications are started before proceeding with the application start.
    This is done by including the option attribute set to handleDependencies: 
    <AMXAdminTask action="start" objectSelector="Environment/Application" option="handleDependencies" />
  4. Invoke the command-line interface on the build file.

Result

The selected applications and target applications are started.

It is likely that the status of the application and target applications is not immediately reflected in the Administrator UI.