You can use the dumpXdState.py script
to dump the current state of various WebSphere® Virtual Enterprise processes. You can use
this script for problem diagnosis and debugging purposes when requested
by IBM® support. The detailed state of the on demand
router (ODR), the deployment manager, and application server processes
are displayed when using this script.
Purpose
You can dump the state
of active
WebSphere Virtual Enterprise processes
with this script.
Location
The dumpXdState.py script
is in the install_root\bin directory.
Usage
The
dumpXdState.py script
must be run from the
install_root\bin directory
using
wsadmin.sh. To automatically detect active
WebSphere Virtual Enterprise processes and write
their state information to a file, use the following command:
wsadmin.sh -lang jython -f dumpXdState.py --auto > output_file_name
Where
output_file_name is
the name of a file to save the output.
Use wsadmin.bat for
the Windows® operating systems.
Options
- -–auto
- Exports information for all of the WebSphere Virtual Enterprise processes into the specified
text file. This option exports a large amount of data, for example,
a small topology might result in a text file that is over 2500 kilobytes.
- -–dom
- Specifies a domain. The default is *, or
all domains.
- -–dmgr=deployment_manager_name
- Exports information for the deployment manager that you specify
in the option.
- -–help
- Displays the help for this script.
- -–odr=odr_name
- Exports information for the ODR that you specify in the option.
The output for this option is similar to output that you get from
the dumpOdrState.jacl script, but includes additional
information from internal processes.
- -–svr=server_name
- Exports information for the server that you specify in the option.
Example
The following example automatically detects WebSphere Virtual Enterprise processes and writes
their state information to a file1:
wsadmin.sh -lang jython -f dumpXdState.py --auto > file1
Results
The dumpXdState.py script
dumps the state of various WebSphere Virtual Enterprise processes
by invoking the managed beans (MBean) of those processes. The dumped
information is written to the output file name specified on the command
line. Provide this file to IBM support for diagnosis and debugging
of problems.