sun-appserv-undeploy (Sun Java System Application Server Enterprise Edition 8.2 Developer's Guide)

Sun Java System Application Server Enterprise Edition 8.2 Developer's Guide

sun-appserv-undeploy

Undeploys any of the following from a local or remote Application Server instance.

Enterprise application (EAR file)
Web application (WAR file)
Enterprise Java Bean (EJB-JAR file)
Enterprise connector (RAR file)
Application client

Subelements

The following table describes subelements for the sun-appserv-undeploy task. These are objects upon which this task acts.

Table 3–7 sun-appserv-undeploy Subelements


Element	Description
server	An Application Server instance.
component	A component to be deployed.
fileset	A set of component files that match specified parameters.

Attributes

The following table describes attributes for the sun-appserv-undeploy task.

Table 3–8 sun-appserv-undeploy Attributes


Attribute	Default	Description
`name`	file name without extension	(optional if a `component` or `fileset` subelement is present or the `file` attribute is specified, otherwise required) The display name for the component being undeployed.
`file`	none	(optional) The component to undeploy. If this attribute refers to a file, it must be a valid archive. If this attribute refers to a directory, it must contain a valid archive in which all components have been exploded.
`type`	determined by extension	(optional) Deprecated.
`droptables`	`sun-ejb-jar.xml` entry	(optional) If `true`, causes database tables that were automatically created when the bean(s) were last deployed to be dropped when the bean(s) are undeployed. If `false`, does not drop tables. If not specified, the value of the `drop-tables-at-undeploy` attribute in `sun-ejb-jar.xml` is used. For details, see Generation Options.
`cascade`	`false`	(optional) If `true`, deletes all connection pools and connector resources associated with the resource adapter being undeployed. If `false`, undeployment fails if any pools or resources are still associated with the resource adapter. This attribute is applicable to connectors (resource adapters) and applications with connector modules.
`user`	`admin`	(optional) The user name used when logging into the application server administration instance. This attribute is inherited by nested `server` elements.
`password`	none	(optional) Deprecated, use `passwordfile` instead. The password used when logging into the application server administration instance. This attribute is inherited by nested `server` elements.
`passwordfile`	none	(optional) File containing passwords. The password from this file is retrieved for communication with the application server administration instance. This attribute is inherited by nested `server` elements. If both `password` and `passwordfile` are specified, `passwordfile` takes precedence.
`host`	`localhost`	(optional) Target server. When deploying to a remote server, use the fully qualified host name. This attribute is inherited by nested `server` elements.
`port`	4849	(optional) The administration port on the target server. This attribute is inherited by nested `server` elements.
`target`	name of default instance	(optional) Target application server instance. This attribute is inherited by nested `server` elements.
`asinstalldir`	see description	(optional) The installation directory for the local Application Server installation, which is used to find the administrative classes. If not specified, the command checks to see if the `asinstalldir` parameter has been set. Otherwise, administrative classes must be in the system classpath.
`sunonehome`	see description	(optional) Deprecated. Use `asinstalldir` instead.

Examples

Here is a simple application undeployment script with many implied attributes:

<sun-appserv-undeploy name="simpleapp" passwordfile="${passwordfile}" />

Here is an equivalent script showing all the implied attributes:

<sun-appserv-undeploy
 name="simpleapp"
 user="admin"
 passwordfile="${passwordfile}"
 host="localhost"
 port="4849"
 target="${default-instance-name}"
 asinstalldir="${asinstalldir}" />

This example demonstrates using the archive files (EAR and WAR, in this case) for the undeployment, using the component name (for undeploying the EJB component in this example), and undeploying multiple components.

<sun-appserv-undeploy passwordfile="${passwordfile}">
 <component file="${assemble}/simpleapp.ear"/>
 <component file="${assemble}/simpleservlet.war"/>
 <component name="simplebean" />
</sun-appserv-undeploy>

As with the deployment process, components can be undeployed from multiple servers in a single command. This example shows the same three components being removed from two different instances of the Application Server. In this example, the passwords for both instances are the same.

<sun-appserv-undeploy passwordfile="${passwordfile}">
 <server host="greg.sun.com"/>
 <server host="joe.sun.com"/>
 <component file="${assemble}/simpleapp.ear"/>
 <component file="${assemble}/simpleservlet.war"/>
 <component name="simplebean" />
</sun-appserv-undeploy>