Installer Stops Responding While Installing On Websphere; Unable To Federate Websphere Custom Profile If Agent Is Already Installed; Section 9.5, "Installer Stops Responding While Installing On Websphere; Section 9.6, "Unable To Federate Websphere Custom Profile If Agent Is Already Installed - Novell ACCESS MANAGER 3.1 SP1 - AGENT GUIDE Manual

9.5 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
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 script from a command line.
wsadmin
To work around this problem:
1 Kill the installer process.
2 Run the script from a command line interpreter. If you are prompted to confirm the
wsadmin
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.
9.6 Unable to Federate WebSphere Custom
Profile If Agent is Already Installed
When a WebSphere server instance that is created in one machine is federated into the deployment
manager of another machine that already has server instances with J2EE Agent installed, the newly
federated server instance will not start. This is because, the security configuration changes that are
performed applies to all the instances of the deployment manager and all the application server
instances that are part of it.
To work around this problem, copy the following files from the
machine that has agents installed, to the
the server:
NidsCommonAgent-unsign.jar
NidsWebSphere-unsign.jar
nxpe.jar
jcc-unsign.jar
nxpe-toolkit-unsign.jar
$WAS_HOME$/lib
folder of the new machine, then restart
$WAS_HOME$/lib
script
wsadmin
folder of the
Troubleshooting the J2EE Agent 107