![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
1.
− Click Undeploy.
−
d. 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.
a.
b. 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.
a.
− Resolve Mode - Dependencies on target product applications are checked.
− Force Undeploy - Dependencies on target product applications are not checked.
c. <Environment xsi:type="amxdata:Environment" name="envName" >
<Application xsi:type="amxdata_base:Application_base" name="app" />
</Environment>
2. 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.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |