The ejbdeploy task is used to run a "hot" deployment tool for
vendor-specific J2EE server. The task runs the tool in a separate JVM. The
task requires nested elements which define the attributes of the
vendor-specific deployment tool being executed.
| Attribute | Description | Required |
| action | This is the action to be performed. For most cases this will be "deploy". Some tools support additional actions, such as "delete", "list", "undeploy", "update"... | Yes |
| classpath | The classpath to be passed to the JVM running the tool. The classpath may also be supplied as a nested element. | No |
| serverUrl | The URL for the server where the component will be deployed. | No |
| username | The user with privileges to deploy applications to the server. | No |
| password | The password of the user with privileges to deploy applications to the server. | Yes |
| source | A fully qualified path/filename of the component to be deployed. This may be a EAR, JAR, WAR, or any other type that is supported by the server. | No |
The ejbdeploy task supports a nested <classpath> element to set the classpath.
Also supported are nested vendor-specific elements.
The WebLogic element contains additional parameters to run the
weblogic.deploy deployment tool.
Valid actions for the tool are deploy, undeploy,
list, update, and delete.
If the action is deploy or update,
the application and source attributes must be set.
If the action is undeploy or delete,
the application attribute must be set.
| Attribute | Description | Required |
| application | This is the name of the application being deployed | Yes |
| component | This is the component string for deployment targets.
It is in the form <component>:<target1>,<target2>...
Where component is the archive name (minus the .jar, .ear, .war
extension). Targets are the servers where the components will be deployed |
Yes |
| debug | If set to true, additional information will be printed during the deployment process. | No |
This example shows the use of ejbdeploy to deploy a component to a WebLogic server:
<ejbdeploy action="deploy"
serverUrl="t3://myserver:7001"
classpath="${classpath}"
username="${user.name}"
password="${user.password}"
source="${lib.dir}/ejb_myApp.ear">
<weblogic application="myapp"
component="ejb_foobar:myserver,productionserver"
debug="true"/>
</ejbdeploy>
This example shows ejbdeploy being used to delete a component from a WebLogic server:
<ejbdeploy action="delete"
serverUrl="t3://myserver:7001"
classpath="${classpath}"
username="${user.name}"
password="${user.password}">
<weblogic application="myapp"/>
</ejbdeploy>
Copyright © 2002 Apache Software Foundation. All rights Reserved.