Deploying Applications

You can deploy an application from the GUI or from the CLI. The GUI allows you to deploy with or without starting the application. You can also select other deploy options.

Note:
ActiveMatrix components and bindings depend on functionality provided by ActiveMatrix product applications. The ActiveMatrix platform product application installed on every node supports:
  • Java
  • Spring
  • Web Application
  • Components
  • SOAP, REST, and JMS Bindings

Before deploying an application containing any other type of component or binding on a node, an instance of the product application template that supports that component or binding must be deployed on that node. For Mediation components, the product application name is TIBCO ActiveMatrix Mediation Implementation Type Application and the product application template name is TIBCO ActiveMatrix Mediation Implementation Type Application Template. For all other component and binding types, see the documentation for the component and binding type for whether a product application is needed and for the name of the required product application template.

The required driver must be provisioned using TCT before deploying the application.

If you are deploying a very large application, the deployment can take a significant amount of time. As it goes through the deployment phases optPreFlight, startPreFlight, and deploy its progress is recorded in the SystemNode.log file (using the logger 'com.tibco.amx.admin.api.application' at the INFO level). For more information about the deployment phases, see Deployment Preflight Check.

GUI

Procedure

  1. Click Applications.
  2. In the Applications list, click one or more applications.
  3. Choose a deploy option as mentioned in the following table.
    Option Procedure
    Deploy with Start

    Dependencies on target product applications are checked.

    1. Do one of the following:
      • Click Deploy.
      • Select Deploy > Deploy with Start.
    2. If the applications depend on undeployed target product applications, the Deployment Application Dependencies dialog displays.
    3. Check the check boxes next to the target applications to deploy.
    Deploy without Start

    Dependencies on target product applications are checked.

    1. Select Deploy > Deploy without Start
    2. If the applications depend on undeployed target product applications, the Deployment Application Dependencies dialog displays.
    3. Check the check boxes next to the target applications to deploy.
    More Deploy Options
    1. Select Deploy > More deploy options
    2. Check the checkboxes for one or more of the following options
      • Start applications - Dependencies on target applications are checked.
      • Resolve mode - Dependencies on target product applications are checked.

        Deploys the selected applications on the nodes, restarts the nodes, and causes all applications deployed on the nodes to use the latest versions of the features on which they depend. Use this operation to deploy an application with a new version of an existing feature, to force applications that reference the existing feature to use the new version, or if after clicking Deploy you get an error that says that because the node is running in stable mode, it cannot accept the deployment of the application.

      • Force deploy - Dependencies on target product applications are not checked and validation errors ignored. Might result in broken applications and should be used with caution.
      • Skip preflight - Specifying this option causes the preflight check to be skipped. The preflight check ensures that target applications, follower applications, and dependencies are all in-sync, plus any applications that the application being deployed is dependent upon are running. This option should be used only if you know for certain that those conditions are all met. For more information, see Deployment Preflight Check.
  4. Click Deploy to deploy the application or Cancel to cancel the deployment.
    Tip: If Application deployment fails with the following error, regenerate the DAA and deploy the project: 
    Invalid action URI "null" is specified

    This error appears when the SOAP Action in the Concrete portion of a WSDL is an invalid URI (for example, it contains a space).

  5. To track application deployment progress in the Administrator UI, click the button in the upper right corner. Deployment progress of application is displayed in a new window. For more information about specific application deployment, click the percentage link in Percentage column of Application deployment progress dialog box. For more information, see Tracking Application Deployment Progress.

Result

The applications are deployed and if auto-provisioning is enabled, those applications that provide implementation or binding types to the applications being deployed are also automatically deployed to the target nodes.

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 set to deploy and the objectSelector attribute to Environment/Application. To deploy without starting the application, specify the options attribute and set the value to nostart. 

    <target name="deploy.app">

		<AMXAdminTask
			remote="true"
			propsFile="${instance.properties.file}"
			action="deploy"
			dataFile="${basedir}/cli_data.xml"
			objectSelector="Environment//Application"
			overwrite="true"
			merge="true"
			createIfNotExists="true"
			force="false"
			failOnError="true"
			options="auto-resolve"/>
	</target>
  3. Invoke the command-line interface on the build file.
    • The application is deployed and started.
    • If the application is a dependent application and its target application has been deployed, the application is deployed and started. If the target application is not deployed, the deployment will fail.
    • If an application is a target application, it and all its dependent applications are deployed and started.