Upgrading an Application
You upgrade an application from the GUI or the CLI.
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
- Click Applications and click an application from the list. .
- 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.
- Click
Browse to navigate to a DAA file.
- Navigate to a directory containing the DAA file.
- Click the DAA file.
- Click Open.
The DAA is validated. - If the DAA is not uploaded click the More details link to see the errors.
- 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.
- 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.
- Click
Deploy.
The application is upgraded on all the nodes where it is deployed.Note: While upgrading an application, resource templates are imported at the same scope where the resource templates were first imported during initial application creation. Moreover, an existing resource template is not overwritten. Only new resource templates are created at the specified scope.
CLI
- Procedure
- 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 the default value is set to the manual distribution.
The target application cannot be changed at a later time.
If you set the propertyimportResourceTemplates="true"
then resource templates are imported. If the property is not set, or set toimportResourceTemplates="false"
, then resource templates are not imported.You can also import specific resource templates by using
<ImportResourceTemplateName>RT_Name</ImportResourceTemplateNames>
. - 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" />
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.