If you log in
with your developerWorks ID, you can leave comments and feedback for the development team.
WebSphere Virtual Enterprise Version 6.1.1
On demand router scripts
You can use Jacl and Python scripts to create, delete, or debug an on demand router (ODR) from the command line.
You can use scripts to perform the following tasks on the ODR:
- [Dita2Wiki file name not found]
- [Dita2Wiki file name not found]
- [Dita2Wiki file name not found]
Create an ODR
Use the createodr.jacl script to create an ODR server. At installation time the script is copied onto the installation target machine(s) in the install_root\bin directory.
To create an ODR, you must have administrator or configurator privileges.
To run createodr.jacl with wsadmin, use the following command:
In place of nodename use the name of the node upon which you want to create your ODR. You might need to modify wsadmin to
wsadmin.sh or
wsadmin.bat, depending upon your operating environment.
In Version 6.1, a template parameter is required. Options for odr_templates are: odr, http_sip_odr_server, http_sip_odr_server. For example,
For the z/OS(R) operating system, options for odr_templates are: odr_zos, http_sip_odr_server_zos, http_sip_odr_server_zos. For example,
You might be more comfortable with first launching the scripting client. You might be more comfortable with first launching the scripting client. See the Getting started with scripting article in the WebSphere(R) Application Server information center for more information. In wsadmin:
In place of nodename use the name of the node upon which you want to create your ODR.
Delete an ODR
You can use the deleteodr.jacl script to delete an ODR server. At installation time the script is copied onto the installation target machine(s) in the <install_root>\bin directory.
To delete an ODR, you must have administrator or configurator privileges.
To start the deleteodr.jacl script with wsadmin, use the following command:
In place of nodename use the name of the node upon which your ODR exists. You might need to modify wsadmin to
wsadmin.sh or
wsadmin.bat, depending upon your operating environment.
You might be more comfortable with first launching the scripting client. See the "Getting started with scripting" article in the WebSphere(R) Application Server information center for more information. In the wsadmin tool:
In place of nodename use the name of the node upon which your ODR exists.
Diagnose HTTP errors that the ODR returns
You can use the odrDebug.py script to diagnose errors that the ODR returns, such as 404 errors and 503 errors.
You can specify the following parameters:
- nodeName Specifies the name of the node that you want to debug.
- odrName Specifies the name of the ODR that you want to debug.
- errorCode Specifies the HTTP error code. You can specify 404, 503, and so on.
- expression Specifies if the error code is being debugged. Specify false to disable debugging when the error occurs. Specify true to have debugging enabled when the error occurs.
- debugLevel Specifies how much information is provided for debugging. You can use one of the following debug levels:
- 0: prints a concise description on a single line.
- 1: prints a subset of target.xml file information.
- 2: prints the entire target.xml file.
*Example usage*
Example output
If a 503 error occurs because no servers have been started, the SystemOut.log file contains the following message:
Related links
Copyright IBM Corporation 2007,2008,2009. All Rights Reserved.
Content source for this Wiki page: todrscript.dita