|
Problem |
MustGather for problems with the WebSphere® Application
Server Administrative Scripting Tools component (for example: the wscp
tool) for all releases of V3.5 or V4.0. Gathering this information before
calling IBM® support helps familiarize you with the troubleshooting
process and saves you time. |
|
Solution |
If you already contacted support, continue to the
component-specific MustGather information. Otherwise, click MustGather:
Read first for all WebSphere Application Server products.
WebSphere Control Program (wscp) specific MustGather information
For wscp problems, information is required from both your
administrative server and client sides.
- Domain configuration information
Gather the following files:
- The product.xml file, located in your
install_root/properties/com/ibm/websphere
directory.
- The admin.config file, located in your
install_root/bin directory.
Note: If it is a stand-alone or remote wscp client, your
client side product.xml file must be gathered.
- Administrative server and client traces
Both of the following traces must be configured prior to running the
test to recreate your problem with wscp.
- Administrative Server
This trace must be enabled on the node where your wscp client is going to
run.
- Edit the admin.config file, located in your
install_root/bin directory. Ensure the following
two lines appear as shown:
com.ibm.ejs.sm.adminServer.traceString=com.ibm.ejs.sm.*=all=enabled
com.ibm.ejs.sm.adminServer.traceOutput=install_root/logs/admin.trace |
|
- Exit and save.
- Stop the administrative server.
- Empty out the install_root/logs
directory.
- Start the administrative server.
- Client side
To set up your trace, see the following technote:
Tracing
WSCP in WebSphere Application Server.
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the Administrative Scripting Tools component, search the WebSphere
Application Server support site. |
|
|