InfoCenter Home >
8: Problem determination >
8.5: Problem determination quick reference >
8.5.2: Administrative client problems
8.5.2: Administrative client problems
You can remotely administer WebSphere Application Server using:
Use can run the administrative console remotely using the adminclient.bat file on Windows NT, or
adminclient.sh file on UNIX.
Typical remote admin console problems are:
- The com.ibm.ejs.util.cache.FaultException error occurs in the stack trace because
the JDK running on the client machine cannot communicate with the JDK running on the administrative server
machine. The resolution is to upgrade the backlevel JDK.
- The Network Address Translation (NAT) function in firewalls cannot be used with a remote administrative client.
The internal address of the administrative server is not recognized by the administrative client outside the
firewall. No circumvention exists for this problem.
X windows client software can run on any platform but requires a UNIX X Windows server.
(Currently the X Windows server is only available on AIX and Solaris platforms.)
Typical X Windows client problems are:
- You cannot run an administrative console remotely through the X Windows client using an
authorized, non-root account with global security enabled.
The error message, FATAL Could not bind to the Administrative Server on {0}{1}, displays on
the screen when the adminclient.sh or .bat file is executed.
No circumvention exists for this problem.
When you cannot start the administrative client (the console) refer to the problem explanation
here.
|
|