mirror of
https://github.com/apache/ant.git
synced 2025-05-18 05:54:48 +00:00
00988f5180
git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@272053 13f79535-47bb-0310-9956-ffa450edef68
202 lines
6.8 KiB
HTML
202 lines
6.8 KiB
HTML
<html>
|
|
|
|
<head>
|
|
<meta http-equiv="Content-Language" content="en-us">
|
|
<title>ServerDeploy Task</title>
|
|
|
|
</head>
|
|
|
|
<body>
|
|
|
|
<h2><a name="serverdeploy">serverdeploy</a></h2>
|
|
<h3><b>Description:</b></h3>
|
|
|
|
<p>The <code>serverdeploy</code> task is used to run a "hot" deployment tool for
|
|
vendor-specific J2EE server. The task requires nested elements which define
|
|
the attributes of the vendor-specific deployment tool being executed.
|
|
Vendor-specific deployment tools elements may enforce rules for which
|
|
attributes are required, depending on the tool.
|
|
</p>
|
|
|
|
<h3>Parameters:</h3>
|
|
<table border="1" cellpadding="2" cellspacing="0">
|
|
<tr>
|
|
<td valign="top"><b>Attribute</b></td>
|
|
<td valign="top"><b>Description</b></td>
|
|
<td valign="top"><b>Required</b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">action</td>
|
|
<td valign="top">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"...</td>
|
|
<td>Yes</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">source</td>
|
|
<td valign="top">A fully qualified path/filename of the component to be deployed.
|
|
This may be an .ear, .jar, .war, or any other type that is supported by the server.
|
|
</td>
|
|
<td>Tool dependant</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<h3>Nested Elements</h3>
|
|
|
|
<p>The serverdeploy task supports a nested <code>classpath</code> element to set the classpath.</p>
|
|
|
|
<h3>Vendor-specific nested elements</h3>
|
|
|
|
<h3>Parameters used for all tools:</h3>
|
|
<table border="1" cellpadding="2" cellspacing="0">
|
|
<tr>
|
|
<td valign="top"><b>Attribute</b></td>
|
|
<td valign="top"><b>Description</b></td>
|
|
<td valign="top"><b>Required</b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">classpath</td>
|
|
<td valign="top">The classpath to be passed to the JVM running the tool.
|
|
The classpath may also be supplied as a nested element.</td>
|
|
<td>Tool dependant</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">server</td>
|
|
<td valign="top">The address or URL for the server where the component will be deployed.</td>
|
|
<td>Tool dependant</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">username</td>
|
|
<td valign="top">The user with privileges to deploy applications to the server.</td>
|
|
<td>Tool dependant</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">password</td>
|
|
<td valign="top">The password of the user with privileges to deploy applications to the server.</td>
|
|
<td>Tool dependant</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<p>Also supported are nested vendor-specific elements.</p>
|
|
|
|
<h3>Generic element</h3>
|
|
This element is provided for generic Java-based deployment tools.
|
|
The generic task accepts (but does not require) nested <code>arg</code>
|
|
and <code>jvmarg</code> elements.
|
|
A JVM will be spawned with the provided attributes. It is recommended
|
|
that a vendor-specific element be used over the generic one if at all
|
|
possible.
|
|
<p>The following attributes are supported by the generic element.</p>
|
|
<p>
|
|
<table border="1" cellpadding="2" cellspacing="0">
|
|
<tr>
|
|
<td valign="top"><b>Attribute</b></td>
|
|
<td valign="top"><b>Description</b></td>
|
|
<td valign="top"><b>Required</b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">classname</td>
|
|
<td valign="top">This is the fully qualified classname of the Java based
|
|
deployment tool to execute.</td>
|
|
<td>Yes</td>
|
|
</tr>
|
|
</table>
|
|
</p>
|
|
|
|
<h3>Nested Elements</h3>
|
|
<p>The generic element supports nested <arg> and <jvmarg> elements.</p>
|
|
|
|
<h3>Example</h3>
|
|
|
|
<p>This example shows the use of generic deploy element to deploy a component
|
|
using a Java based deploy tool:</p>
|
|
|
|
<pre>
|
|
<serverdeploy action="deploy" source="${lib.dir}/ejb_myApp.ear">
|
|
<generic classname="com.yamato.j2ee.tools.deploy.DeployTool"
|
|
classpath="${classpath}"
|
|
username="${user.name}"
|
|
password="${user.password}">
|
|
<arg value="-component=WildStar"/>
|
|
<arg value="-force"/>
|
|
<jvmarg value="-ms64m"/>
|
|
<jvmarg value="-mx128m"/>
|
|
</generic>
|
|
</serverdeploy>
|
|
</pre>
|
|
|
|
|
|
<h3>WebLogic element</h3>
|
|
<p>
|
|
The WebLogic element contains additional attributes to run the
|
|
<code>weblogic.deploy</code> deployment tool.
|
|
<p>Valid actions for the tool are <code>deploy</code>, <code>undeploy</code>,
|
|
<code>list</code>, <code>update</code>, and <code>delete</code>.
|
|
<p>If the action is <code>deploy</code> or <code>update</code>,
|
|
the <code>application</code> and <code>source</code> attributes must be set.
|
|
If the action is <code>undeploy</code> or <code>delete</code>,
|
|
the <code>application</code> attribute must be set. If the <code>username</code>
|
|
attribute is omitted, it defaults to "system". The <code>password</code> attribute is
|
|
required for all actions.
|
|
<p>
|
|
<table border="1" cellpadding="2" cellspacing="0">
|
|
<tr>
|
|
<td valign="top"><b>Attribute</b></td>
|
|
<td valign="top"><b>Description</b></td>
|
|
<td valign="top"><b>Required</b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">application</td>
|
|
<td valign="top">This is the name of the application being deployed</td>
|
|
<td>Yes</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">component</td>
|
|
<td valign="top">This is the component string for deployment targets.
|
|
It is in the form <code><component>:<target1>,<target2>...</code>
|
|
Where component is the archive name (minus the .jar, .ear, .war
|
|
extension). Targets are the servers where the components will be deployed</td>
|
|
<td>Yes</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">debug</td>
|
|
<td valign="top">If set to true, additional information will be
|
|
printed during the deployment process.</td>
|
|
<td>No</td>
|
|
</tr>
|
|
</table>
|
|
|
|
|
|
<h3>Examples</h3>
|
|
|
|
<p>This example shows the use of serverdeploy to deploy a component to a WebLogic server:</p>
|
|
|
|
<pre>
|
|
<serverdeploy action="deploy" source="${lib.dir}/ejb_myApp.ear">
|
|
<weblogic application="myapp"
|
|
server="t3://myserver:7001"
|
|
classpath="${weblogic.home}/lib/weblogic.jar"
|
|
username="${user.name}"
|
|
password="${user.password}"
|
|
component="ejb_foobar:myserver,productionserver"
|
|
debug="true"/>
|
|
</serverdeploy>
|
|
</pre>
|
|
|
|
<p>This example shows serverdeploy being used to delete a component from a
|
|
WebLogic server:</p>
|
|
|
|
<pre>
|
|
<serverdeploy action="delete">/
|
|
<weblogic application="myapp"
|
|
server="t3://myserver:7001"
|
|
classpath="${weblogic.home}/lib/weblogic.jar"
|
|
username="${user.name}"
|
|
password="${user.password}"/>
|
|
</serverdeploy>
|
|
</pre>
|
|
<hr>
|
|
<p align="center">Copyright © 2002 Apache Software Foundation. All rights Reserved.</p>
|
|
</body>
|
|
</html>
|