Upgrading an Application

You upgrade an application from the GUI or the CLI.

Prerequisites

The application template version to which the application is upgraded must exist in the Administrator software repository or you must upload a DAA containing the new template.

GUI

Procedure

  1. Click Applications and click an application from the list. .
  2. If the new template does not exist in the repository, in the General tab click Upload DAA or EAR to upload a DAA containing a new version of the application.
    The Upload DAA or EAR dialog displays.
  3. Click Browse to navigate to a DAA file.
    1. Navigate to a directory containing the DAA file.
    2. Click the DAA file.
    3. Click Open.
    The DAA is validated.
  4. If the DAA is not uploaded click the More details link to see the errors.
  5. After you have resolved any errors, select the features to import and click Save.
    A dialog box displays the effects of updating the application template to the new version.
  6. Choose an action based on whether you want to continue the process of upgrading the application.
    • Save - Continues the process of upgrading the application.
    • Cancel - Does not upload the new version of the application template.
    • Click Print Preview to print the displayed information.
  7. Click Deploy.
    The application will be upgraded on all the nodes where it was deployed.
    Note: While upgrading an application, resource templates will be imported at the same scope where the resource templates were first imported during initial application creation. Moreover, an existing resource template will not be overwritten. Only new resource templates will be created at the specified scope.

CLI

Procedure

  1. In the data file, specify an application element in full format.
    Distribution Data Object
    Manual 
    <Environment xsi:type="amxdata:Environment" name="EnvName" >
 <Application xsi:type="amxdata:Application" name="AppName" importResourceTemplates="true">
  <ApplicationTemplate xsi:type="amxdata_reference:ApplicationTemplate_reference" 
    name="AppTemplateName" version="1.0.0.201005040925" />
 </Application>
</Environment>
    Product Application 
    <Environment xsi:type="amxdata:Environment" name="EnvName" >
 <Application xsi:type="amxdata:Application" name="AppName" importResourceTemplates="true">
  <ApplicationTemplate xsi:type="amxdata_reference:ApplicationTemplate_reference" 
    name="AppTemplateName" version="1.0.0.201005040925"/>
	 <TargetApplication	xsi:type="amxdata_reference:Application_reference" name="TargetApp" />	 
 </Application>
</Environment>

    Specify the target application when creating the application or it will default to manual distribution.

    The target application cannot be changed at a later time

    If you set the property importResourceTemplates="true" then resource templates will be imported. If the property is not set, or set to importResourceTemplates="false", then resource templates will not be imported.

    You can also import specific resource templates by using <ImportResourceTemplateName>RT_Name</ImportResourceTemplateNames> .

  2. In the build file set the action attribute of the AMXAdminTask element to upgrade and the objectSelector attribute to Environment/Application. In the build file set the action attribute of the AMXAdminTask element to deploy and the objectSelector attribute to Environment/Application. 
    <AMXAdminTask action="upgrade" objectSelector="Environment/Application" />

Result

The application is upgraded.

When upgrading an application, the upgrade process waits for the previous version of the application to be first undeployed. In cases where you do not want this selective polling where the upgrade process waits for the previous version to undeploy, use the disableSelectivePolling option.