This topic discusses problems that you can encounter when you attempt
to access the console.
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 that supports
the administrative console is up and running. For a base configuration, the
administrative console is deployed by default on server1. ![[AIX HP-UX Linux Solaris Windows]](../../dist.gif)
Before
viewing the administrative console, you must take one of the following actions:
- Run the startServer server1 command for the Windows platform from
a command prompt in the install_dir\bindirectory,
or the ./startServer.sh server1 command for operating systems such
as AIX or Linux.
- Click the Start application server link from the first steps panel.
- Start WebSphere Application Server as a service or from the Start menu,
if you are using a Windows operating system.
If you are using the
deployment manager for a multinode configuration, run the startManager command
from the Network_Deployment_install_dir\bin directory.
View the SystemOut.log file for the
application server or the deployment manager to verify that the server that
supports the administrative console started.
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 BBO5ACR,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 sysprint 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. By default, this address
is http://server_name:9060/ibm/console,
where server_name is the host name.
If you are browsing the administrative console
from a remote machine, try to eliminate connection, address and firewall issues
by pinging the server machine from a command prompt, using the server name
in the Web address.
Try to eliminate connection, address and firewall issues
by pinging the server machine from a command prompt, using the server name
in the URL.
If you
have never been able to access the administrative console see Troubleshooting installation.
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.
If
you are not the administrator, ask the administrator to enable your ID for the administrative console.
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 this problem,
modify Windows-style class paths by replacing occurrences of single back slashes
to two. For example, change c:\MyFiles\MyJsp.jsp to c:\\MyFiles\\MyJsp.jsp.
To resolve, make sure you
have no back slashes in your class paths. Replace any back slashes with forward
slashes.