ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzatz_5.4.0.1/51/trb/trbadmin.htm

59 lines
3.3 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<!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><a name="trbadmin"></a>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 Application Server 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:</p>
<ul>
<li><a href="http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/express/docs/relnotesexp51.html" target="_">WebSphere
Application Server - Express V5.1.0.X Release Notes</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0"> (http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/<br>express/docs/relnotesexp51.html)</li>
<li><a href="http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/express/docs/relnotesexp511.html" target="_">WebSphere
Application Server - Express V5.1.1 Release Notes</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0"> (http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/<br>express/docs/relnotesexp511.html)</li>
</ul>
</LI>
</UL>
</BODY>
</HTML>