Stopping Applications

You can stop applications from the Administrator GUI or by using the CLI. If you are using the GUI, you can choose the Stop Immediately options to have the application exit right away without cleanup.

GUI

Procedure

  1. Click the Applications button.
  2. In the Applications list, click one or more applications.
  3. Choose a stop option.
    Option Procedure
    Stop

    Allows applications to complete processing before shutting down.

    Dependencies on target product applications are checked.

    Applications may take anywhere from a few seconds to an hour to stop.

    1. Do one of the following:
      • Click Stop.
      • Select Stop > Stop
    2. If there are target applications, the Application Dependencies to Stop dialog displays.
    3. Check the checkboxes next to the target applications to stop.
    4. Click Stop.

      Components with dependencies will be stopped only after the components they depend upon have stopped.

    Stop immediately

    Applications may take a few seconds to stop.

    Applications are allowed to perform cleanup operations but not complete their current processing.

    Applications are not stopped in dependency order.

    1. Select Stop > Stop immediately
    The selected applications and target applications are stopped.

CLI

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 stop, the options attribute to immediate and the objectSelector attribute to Environment/Application. 
    <AMXAdminTask action="stop" objectSelector="Environment/Application" />
  3. Optionally, specify that the stopPreFlight operation be performed before stopping the application. The stopPreFlight operation ensures that all dependent applications are stopped before proceeding.
    This is done by including the option attribute set to handleDependencies: 
    <AMXAdminTask action="stop" objectSelector="Environment/Application" option="handleDependencies" />
  4. Invoke the command-line interface on the build file.

Result

The selected applications and target applications are stopped.

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