This topic discusses problems that you can encounter when
you attempt to access the console.
New feature: This topic
references one or more of the application server log files. Beginning
in WebSphere Application Server Version 8.0 you can configure the
server to use the High Performance Extensible Logging (HPEL) log and
trace infrastructure instead of using
SystemOut.log ,
SystemErr.log,
trace.log, and
activity.log files or native z/OS logging
facilities. If you are using HPEL, you can access all of your log
and trace information using the LogViewer command-line tool from your
server profile bin directory. See the information about using HPEL
to troubleshoot applications for more information on using HPEL.
newfeat
What kind of problem are you having?
If you can bring up the browser page, but the administrative console
behavior is inconsistent, error prone, or unresponsive, try upgrading
your browser. Older browsers might not support all the features of
the administrative console. For
a listing of supported web browsers, see the Supported hardware and software web page.
IBM
® Support has documents and tools that can
save you time gathering information needed to resolve problems as
described in
Troubleshooting help from IBM. Before opening
a problem report, see the Support page:
An Internal Server Error, Page cannot be
found, 404, or similar error occurs trying to view the administrative
console
Here are some steps to try if you are unable to
view the administrative console:
- Verify that the application server
which supports the administrative console is up and running.
- For a base configuration, the administrative console is deployed
by default on server1. Before viewing the administrative console,
you must verify that server1 is running. Do so by issuing the following
command on the MVS console to list active processes:
D A,L
Check for the application server procedure name of
BB05ACR with the server short name of BB0S001. If it is not running,
enter the following command on the MVS console:START appserver_proc_name,JOBNAME=server_short_name,
ENV=cell_short_name.node_short_name.server_short_name
Example:
START BBO6ACR,JOBNAME=BBOS001,ENV=PLEX1.SY1.BBOS001
- For a network deployment configuration, the deployment manager
runs the administrative console. For example, to start the deployment
manager, you can issue the following command from the MVS console:
START BBO5DCR,JOBNAME=BBODMGR,ENV=PLEX1.PLEX1.BBODMGR
- View the joblog or stdout for the application server or deployment
manager to verify that the server supporting the administrative console
has started.
- Check the web address you use to view the console.
- Try to eliminate connection, address and firewall
issues by pinging the server machine from a command prompt, using
the server name in the URL.
An Unable to process login. Check user
ID and password and try again. error occurs when trying to access
the administrative console page
This error indicates that
security is enabled for WebSphere® Application Server,
and that the user ID or password supplied is either not valid or
not authorized to access the console.
To access the console:
- If you are the administrator, use the ID defined as the security
administrative ID. This ID is stored in the WebSphere Application
Server security.xml file.
The directory paths in the administrative
console contain strange characters
Directory paths that
are used for class paths or resources specified in an assembly tool, in configuration
files, or elsewhere that contain strange characters when they are
viewed in the administrative console might result from the Java run time interpreting a backslash (\) as
a control character.
To resolve, make sure you have no back
slashes in your class paths. Replace any back slashes with forward
slashes.