You can undeploy an application from the GUI or by using the CLI.
When you undeploy an application, the system queues the request and applies it
to components as they become available. During undeployment, dependencies are
taken into account to allow processing to clean up before removing components
and bindings.
GUI
Procedure
Click the
Applications button.
In the Applications list, click one or more applications.
Choose an undeploy option.
Option
Procedure
Undeploy
Dependencies on target product applications are checked.
Do one of the
following:
Click
Undeploy.
Select
UndeployUndeploy
Note: If the application has multiple versions
deployed, a dialog will display all the versions. Select the version to
undeploy.
If any of the
selected applications has dependencies, the Application Dependencies to
Undeploy dialog displays with target applications.
Check the
checkboxes next to the target applications to undeploy.
Click
Undeploy. The selected target
applications are undeployed. The length of time this action takes to complete
depends on how long it takes for the target applications to complete their
processing. It may take up to several days or longer.
Force Undeploy
Dependencies on target product applications are not checked.
Select
UndeployForce
undeploy
Note: If the application has multiple versions deployed, a
dialog will display all the versions. Select the version to Force undeploy.
Click
Undeploy. Components in the selected
applications are allowed to perform clean up operations. In rare cases, a
component may hang while performing its cleanup. When that happens a node that
becomes unusable might need to be restarted. If a component stores information
in a database or file, that data may remain after a force undeploy and must be
cleaned up manually.
More undeploy options
Select
UndeployMore
undeploy options
Check the
checkboxes for one or more of the following options:
Resolve Mode -
Dependencies on target product applications are checked.
If any of the selected applications has
dependencies, the Application Dependencies to Undeploy dialog displays with
target applications. The applications are deleted from the node and the runtime
state changes to Not deployed. The nodes where the applications are undeployed
are restarted to load software updates.
Force Undeploy
- Dependencies on target product applications are not checked.
Components in the selected applications are allowed
to perform clean up operations. In rare cases, a component may hang while
performing its cleanup. When that happens a node that becomes unusable might
need to be restarted. If a component stores information in a database or file,
that data may remain after a force undeploy and must be cleaned up manually.
Click
Undeploy to undeploy the application
or
Cancel to cancel the undeployment
process.
CLI
Procedure
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>
In the build file, set the
action
attribute of the
AMXAdminTask element to
undeploy and the
objectSelector attribute to
Environment/Application. To perform a force
undeploy, specify the
-force option.
