Troubleshoot: WebSphere Application Server Administration and administrative console

Use the following resources to determine the cause of the problem when attempting to use the administrative console or the WebSphere admin scripting tool (wsadmin):

• Administrative functions are supported by the application server (such as "server1") for a WebSphere Application Server instance, or the Deployment Manager (such as "dmgr") for a Network Deployment instance.

  The server process must be running in order to use the administrative console. For wsadmin, many functions require a connection to the server as well. Verify that the server is running and ready to receive administrative requests. For more information on how to verify that the server is running in WebSphere Application Server, see Verify that the WebSphere Application Server environment has started in the Installation topic. For more information on how to verify that the server is running in Network Deployment, see Verify that the Network Deployment environment has started in the Installation topic.

  If the server is not started and you are using wsadmin for an administrative function that does not require the server to be started, ensure that you have specified -conntype NONE when invoking wsadmin.

• Use the TCP/IP ping command to test that the hostname where the application server or Deployment Manager is running is reachable from the system where the browser or wsadmin program are being used. If you are able to ping this hostname, this indicates that there are no firewall or connectivity issues.

• If the host where the application server or Deployment Manager is running is remote to the machine from which the client browser or wsadmin command is running, ensure that the hostname in the browser URL for the console is correct, or the -host hostname option of the wsadmin command is being used to direct wsadmin to the right server.

• If you are using the wsadmin tool, read the The wsadmin administrative tool topic in Administration. Also check the wsadmin log files located in the logs directory of your instance (by default) for errors.

• Check the logs files for the server for errors. For information on the log files and where they are located, see WebSphere Application Server log files.

• Read the release notes.WebSphere Application Server Release Notes (http://publib.boulder.ibm.com/was400/docs/relnotes502.html) .

• Check the WebSphere Application Server FAQ database .

• Refer to the WebSphere Application Server for iSeries newsgroup .
  This iSeries Technical Support Web-based forum is dedicated to WebSphere Application Server for iSeries.

• Contact IBM support. See Get support for WebSphere Application Server for more information.