Troubleshooting
Problem
Collecting data for problems with the Administrative Console in IBM WebSphere Application Server V8.5.5, and V9.0. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
Cause
WebSphere Application Server Collecting data for problems
Resolving The Problem
If you are unable to login into the administrative console:
- Stop the dmgr process in federated environment or stop the server in a stand-alone Application Server process.
- Backup and purge the logs in the following directories:
profile_root/logs/server_name
profile_root/logs/FFDC
- Edit the server.xml file located in the following directory:
profile_root/config/cells/cell_name/nodes/node_name/servers/server_name/
- If WebSphere Global Security is not enabled, change the following trace specification:
From:
startupTraceSpecification="*=info"
To:
startupTraceSpecification="*=info:com.ibm.ws.management.*=all:com.ibm.ws.sm.*=all:Webcontainer=all:Webui=all"
If WebSphere Global Security is enabled, change the following trace specification:
From:
startupTraceSpecification="*=info"
To:
startupTraceSpecification="*=info:Webui=all:com.ibm.ws.management.*=all:com.ibm.ws.sm.*=all:Webcontainer=all:SASRas=all:com.ibm.ws.security.*=all:SSL=all:com.ibm.websphere.wim.*=all:com.ibm.wsspi.wim.*=all:com.ibm.ws.wim.*=all"
- Save the changes.
- Run the following command:
startServer server_name
OR
startManager
- Try to login to the administrative console to reproduce the problem. Note to try a different type of browser.
- Run the collector tool on the Network Deployment (for federated environment only) or base Application Server profiles.
- Follow directions in MustGather: Read First to open a case and send data to IBM® Support.
- Follow instructions to send diagnostic information to IBM support.
For further details, reference Setting up a trace in WebSphere Application Server
Tracing from the administrative console, if you can login into the administrative console:
- In the administrative console, expand the Troubleshooting section and click on Logs and Trace
- Click on the link for your server or dmgr where administrative console is running.
- Click on Change Log Detail Levels. Click on the Runtime tab.
- If WebSphere Global Security is not enabled, change the following trace string:
From:
*=info
To:
*=info:com.ibm.ws.management.*=all:com.ibm.ws.sm.*=all:Webui=all
If WebSphere Global Security is enabled, change the following trace string:
From:
*=info
To:
*=info:com.ibm.ws.management.*=all:com.ibm.ws.sm.*=all:com.ibm.ws.security.*=all:Webui=all
- Click Apply.
- Repeat the administrative console step to reproduce the problem.
- Run the collector tool on the Network Deployment (for federated environment only) or base Application Server profiles.
- Follow directions in MustGather: Read First to open a case and send data to IBM® Support.
- Follow instructions to send diagnostic information to IBM support.
What to do next
Once you have collected the preceding information, you can begin Analyzing the data or simply submit the diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials specific to the administrative console, search the WebSphere Application Server support site.
Related information
Submitting information to IBM support
Steps to getting support for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server
To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:
- Service Request (SR)
- FTP to the Enhanced Customer Data Repository (ECuRep)
MustGather: Read first for WebSphere Application Server
Cluster ripple start problem Deployment problem Discovery problem on Deployment Manager Discovery problem on Node Agent JMX problem Profile wizard problem Start problem Stop problem System administration problem WASService problem (Windows only) WSAdmin problem
Related Information
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server - SSEQTP"},"ARM Category":[{"code":"a8m50000000CdPnAAK","label":"WebSphere Application Server traditional-All Platforms-\u003ESystem Management-\u003ETraditional WAS-\u003EAdmin Console"},{"code":"a8m50000000CdPnAAK","label":"WebSphere Application Server traditional-All Platforms-\u003ESystem Management-\u003ETraditional WAS-\u003EAdmin Console"},{"code":"a8m50000000CdPnAAK","label":"WebSphere Application Server traditional-All Platforms-\u003ESystem Management-\u003ETraditional WAS-\u003EAdmin Console"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;9.0.0"},{"Product":{"code":"SS7JFU","label":"WebSphere Application Server - Express"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Administrative console","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.0;7.0;6.1;6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"7.0;6.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Was this topic helpful?
Document Information
Modified date:
03 January 2023
UID
swg21199337