Novell Access Manager 3.1 SP 2, Руководство пользователя, Страница: 121 / 126

Troubleshooting the J2EE Agent 121
n
ov
do
cx (e
n)
16
Ap
ril 20
10
The J2EE installer Java 1.5 or later. To fix the problem, download and nstall JRE 1.5. Set the
PATH
environment variable to point to the
bin
directory of the newly installed JRE.
For example:
Š
In Linux or UNIX:
export PATH = <JREDirectory>/bin:$PATH
Š In Windows:
set PATH = <JREDirectory>/bin;%PATH%
run the J2EE installer .
9.5.2 Issues With the Administration Console
Administration Console has the following issues:
Š The installation directory of the administration console reachable LDAP.
Š
Check if firewall block the ports. If the port.
Š eDirectory is running.
Š
The Aministration Console is installed properly.
9.6 Installer Stops Responding While Installing
on WebSphere
If the J2EE installer stops responding while installing on the WebSphere server, check if the
installation was performed on a new instance of the WebSphere Application Server that is part of the
WebSphere Cell. If it is, the possible cause could be that the installer uses the
wsadmin
script
provided by WebSphere to perform configuration changes to the application server. When the
installer is run on a new server instance of the WebSphere Application Server instance that is part of
the WebSphere Cell, WebSphere requests the user to authorize signer certificates given by the
deployment manager. The installer eventually connects to this deployment manager. To verify this,
run the
wsadmin
script from a command line.
To work around this problem:
1 Kill the installer process.
2 Run the
wsadmin
script from a command line interpreter. If you are prompted to confirm the
signer certificate, confirm it.
3 Run the J2EE Agent installer.
4
If you are prompted to confirm overwriting some of the files that were installed during the
previous failed attempt, click
OK .
Contact Novell
®
Support if the problem persists.