Configuring using scripting and command line tools

How to create scripts for configuration.

Scripting

This documentation provides information on creating custom scripts for configuration.

These scripts only work on local servers and nodes. They cannot operate on a remote server or node. To administer a remote server, you can use the wsadmin tool connected to the Deployment Manager for the cell in which the target server or node is configured.

For more details about scripting, refer to the WebSphere® Application Server Network Deployment information center:

Command line tools

WebSphere Application Server provides command line tools for adding and removing voice servers from a voice server cell.

To manage using command line tools, perform the following steps:

  1. Open a system command prompt.
  2. Change to the WAS_ROOT/bin directory. Where WAS_ROOT is the directory where you installed WebSphere Application Server.
  3. Run the desired command.

The command runs the requested function and displays the results on the screen. Refer to the command log file for additional information. When you use the -trace option for the command, the additional trace data is captured in the command log file. The directory location for the log files is under the default system log root directory, except for commands related to a specific server instance, in which case the log directory for that server is used. You can override the default location for the command log file using the -logfile option for the command.

For additional information, see the section on managing using command line tools in the WebSphere Application Server Network Deployment information center:

Terms of use | Feedback

(c) Copyright IBM Corporation 2004, 2009. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.