56 lines
2.8 KiB
HTML
56 lines
2.8 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<HTML>
|
||
|
|
<HEAD>
|
||
|
|
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
<TITLE>Troubleshoot: WebSphere Application Server - Express administration and
|
||
|
|
administrative console</TITLE>
|
||
|
|
</HEAD>
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
<h3>Troubleshoot: WebSphere Application Server - Express administration and administrative
|
||
|
|
console </h3>
|
||
|
|
<P>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):</P>
|
||
|
|
<UL>
|
||
|
|
<LI>
|
||
|
|
<p>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,
|
||
|
|
see the <a href="../install/invrfy.htm">verify the installation</a> topic.</p>
|
||
|
|
<p>If the server has 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.</p>
|
||
|
|
</LI>
|
||
|
|
<LI>
|
||
|
|
<p>Use the TCP/IP ping command to test that the hostname is reachable from
|
||
|
|
the system where the browser or wsadmin program is being used. If you are
|
||
|
|
able to ping the hostname, this indicates that there are no firewall or
|
||
|
|
connectivity issues.</p>
|
||
|
|
</LI>
|
||
|
|
<LI>
|
||
|
|
<p>If the host where the application server is running is remote, ensure
|
||
|
|
that hostname in the browser URL for the console is correct, or the -host <EM>hostname</EM> option
|
||
|
|
of the wsadmin command is being used to direct wsadmin to the correct server.</p>
|
||
|
|
</LI>
|
||
|
|
<LI>
|
||
|
|
<p>If you are using the wsadmin tool, see the <a href="../admin/wsaappstr.htm">Start and stop applications with wsadmin</a> topic. Check the wsadmin log
|
||
|
|
files located in the logs directory of your instance for errors.</p>
|
||
|
|
</LI>
|
||
|
|
<LI>
|
||
|
|
<p>Check the log files for server errors. For information on the log files
|
||
|
|
and where they are located, see <a href="trblogs.htm">WebSphere Application
|
||
|
|
Server - Express log files</a>. </p>
|
||
|
|
</LI>
|
||
|
|
<LI>
|
||
|
|
<p>Read the release notes. See <a href="http://www-1.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/express/docs/relnotesexp50.html" target="_new">WebSphere
|
||
|
|
Application Server - Express Release Notes</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0"> for
|
||
|
|
more information.</p>
|
||
|
|
</LI>
|
||
|
|
</UL>
|
||
|
|
</BODY>
|
||
|
|
</HTML>
|