The
wsStartServer task enables you to start a standalone server instance. This is not used to start a server
controlled by DeploymentManager. Therefore, this task is useful for the Base Application Server, and to start
the Node Agent and/or DeploymentManager. If you wish to start a server managed by the Deployment Manager, use
the wsadmin task to execute a scripting command.
The structure of the wsStartServer task is shown here:
<wsStartServer
server="name of the server to start"
profileName="the profile name of the desired server"
noWait="true | false"
quiet="true | false"
logFile="name of the file to log to"
replaceLog="true | false"
trace="true | false"
script="the name of a script file to execute during server startup"
timeout="amount of time to wait for the server to start"
statusPort="port for the server to send status messages to"
username="name of the admin userid id to authenticate with"
password="password of the admin user to authenticate with"
wasHome="WebSphere Installation directory"
failonerror="true | false"
fileEncoding="UTF8"/>
The
server attribute is required and contains the name of the server you wish to start
The
profileName attribute is optional and it contains the name of the server profile to be used
The
noWait attribute is optional. If true, the task with return immediately without waiting for the server to start (default is false).
The
quiet attribute is optional. If true, the task will not print any status information (default is false).
The
logFile attribute is optional and specifies the name of the file to log the server start information to.
The
replaceLog attribute is optional. If true, the task with erase an existing log file, instead of appending (default is false).
The
trace attribute is optional. If true, the task with print trace information (default is false).
The
script attribute is optional and specifies the name of a script file to execute during server startup.
The
timeout attribute is optional and specified the amount of time to wait for the server to successfully start.
The
statusPort attribute is optional and specifies the TCP Port the server should send status messages to.
The
username attribute is optional and specifies the id of the admin user to authenticate with for administrative access.
The
password attrubute is optional and specifies the password of the admin user to authenticate with for administrative access
The
wasHome attribute is optional and it specifies the WebSphere installation directory
The
failonerror attribute is optional and if set to true causes the build to stop if the task has an error (default is false).
The
fileEncoding attribute is optional and sets the file.encoding System Property for the underlying VM.
To use this task, add the following to your Ant build.xml