|
Problem(Abstract) |
Collecting data for problems with the IBM WebSphere
Application Server System Management/Repository component. Gathering this
MustGather information before calling IBM support will help you understand
the problem and save time analyzing the data. |
|
|
|
Resolving the
problem |
If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
Deployment Manager specific MustGather information
MustGather data needed to diagnose your problems with starting and
stopping the WebSphere Deployment Manager V5.0 (all releases) dmgr
application server process.
If your dmgr does not start when you issue the command
startManager at the command line, collect the following documents:
- Backup and purge your logs in the
install_root/logs/dmgr directory and in the
install_root/logs/FFDC directory.
- Set up tracing using server.xml file
- Backup and edit the server.xml file for the dmgr located in
install_root/config/cells/cellname/nodes/nodename/servers/dmgr
directory.
- Find the TraceService xml tag section.
- Modify the startupTraceSpecification entry to look like the
following:
*=all=enabled |
|
 |
 |
- Make sure enable is set to true.
- Execute the command startManager -trace. This will log the
trace to the startserver.log file located in the
install_root/logs/dmgr directory. If you want the
trace to be written to a unique file, execute the command:
startManager -trace -logfile
<absolutepath>\dmgrtrace.out |
Note: If you specify the -logfile option with only a
filename, and you do not specify a directory path for your log file, the
file will be created in the
install_root/bin directory.
 |
- Run collector.sh/collector.bat tool from
install_root/bin.
- Follow instructions to send
diagnostic information to IBM support.
Note: If your dmgr does not stop when issuing the command
stopManager at the command line, follow the same procedure
documented above for collecting trace documents. However, this time
execute the command stopManager -trace in place of
startManager -trace.
For a listing of all technotes, downloads, and educational materials
specific to the System Management/Repository component, search the WebSphere
Application Server support site. |
|
|
|