Ant tasks

The ws_ant tool supports these tasks:

• wsadmin
  The wsadmin task runs the command-line administration tool with the specified arguments. The implementation class for this task is com.ibm.websphere.ant.tasks.WsAdmin. You can run this task from a remote machine that has the WebSphere Application Server - Express administrative tools installed.

  Note: When you use the wsadmin scripting objects, you must include an additional dollar sign ($) before the name of the object. For example, if you want ws_ant to invoke the $AdminApp list command to list the applications on your application server, include this task in the ws_ant buildfile:

  <taskdef name="wsAdmin" classname="com.ibm.websphere.ant.tasks.WsAdmin"/>
    <target name="target">
      <wsAdmin command="$$AdminApp list"/>
    </target>

  where target is a value that is passed on the ws_ant call.

• wsInstallApp
  The wsInstallApp task installs an application into an application server or a cell. The implementation class for this task is com.ibm.websphere.ant.tasks.InstallApplication. Because wsadmin cannot perform remote installations, you must run this task on the local machine.

• wsJspC
  The wsJspC task compiles a directory of JSP files into .class files. The implementation class for this task is com.ibm.websphere.ant.tasks.JspC. You must run this task on the local machine.

• wsListApps
  The wsListApps task lists all the applications installed on an application server or a cell. The implementation class for this task is com.ibm.websphere.ant.tasks.ListApplications. You can run this task from a remote machine that has the WebSphere Application Server - Express administrative tools installed.

• wsNLSEcho
  The wsNLSEcho task provides message retrieval with translation and variable substitution. The implementation class for this task is com.ibm.websphere.ant.tasks.NLSEcho. You must run this task on the local machine.

• wsServerStatus
  The wsServerStatus task displays the status of one application server or all application servers. The implementation class for this task is com.ibm.websphere.ant.tasks.ServerStatus. You must run this task on the local machine.

• wsStartApp
  The wsStartApp task starts an application in an application server or cell. The implementation class for this task is com.ibm.websphere.ant.tasks.StartApplication. You can run this task from a remote machine that has the WebSphere Application Server - Express administrative tools installed.

• wsStartServer
  The wsStartServer task starts an application server. The implementation class for this task is com.ibm.websphere.ant.tasks.StartServer. You must run this task on the local machine.

• wsStopApp
  The wsStopApp task stops an application in an application server or cell. The implementation class for this task is com.ibm.websphere.ant.tasks.StopApplication. You can run this task from a remote machine that has the WebSphere Application Server - Express administrative tools installed.

• wsStopServer
  The wsStopServer task stops an application server. The implementation class for this task is com.ibm.websphere.ant.tasks.StopServer. You must run this task on the local machine.

• wsUninstallApp
  The wsUninstallApp task uninstalls an application from an application server or cell. The implementation class for this task is com.ibm.websphere.ant.tasks.UninstallApplication. Because wsadmin cannot uninstall applications remotely, you must run this task on the local machine.

• wsValidateModule
  The wsValidateModule task validates the deployment descriptor, extensions, and bindings documents of an EAR, WAR, EJB Jar, or Application Client Jar. The implementation class for this task is com.ibm.websphere.ant.tasks.ModuleValidator. You must run this task on the local machine.