Troubleshooting the J2EE Agent
9
119
n
ov
do
cx (e
n)
16
Ap
ril 20
10
9
Troubleshooting the J2EE Agent
This section has the following information:
Section 9.1, “Troubleshooting the J2EE Agent Import,” on page 119
Section 9.2, “Authorization Policies Fail for Some Attributes,” on page 119
Section 9.3, “The Health Status Displays as “Server Is Not Responding,” on page 120
Section 9.4, “Auto-import Agents Fails on WebLogic Running on RedHat,” on page 120
Section 9.5, “Error: Invalid Administration Server IP Address,” on page 120
Section 9.6, “Installer Stops Responding While Installing on WebSphere,” on page 121
Section 9.7, “Unable to Federate WebSphere Custom Profile If Agent Already Installed,” on
page 122
Section 9.8, “Authorization Fails in the WebSphere Application,” on page 122
Section 9.9, “Audit Log Event Problems on 64-Bit Platforms,” on page 123
Section 9.10, “JBoss and SSL,” on page 124
Section 9.11, “Viewing Log Files,” on page 124
Section 9.12, “Troubleshooting Access Control,” on page 124
9.1 Troubleshooting the J2EE Agent Import
If the J2EE Agent does not appear in the Administration Console after the installation has finished,
try one or more of the following:
If the import started and failed to complete, a
repair import
link appears at the bottom of the
table on the J2EE Agents page. Click this link to repair the import.
If your J2EE server is not running, the Administration Console cannot import the J2EE Agent.
Start J2EE server and wait 30 seconds before trying to configure the agent in the
Administration Console.
If you installed the J2EE Agent on a WebSphere server, make sure you have restarted the
WebSphere server. The J2EE Agent does not import into the Administration Console until
WebSphere is restarted.
If you are running WebSphere with additional Java 2 security checks, the agent cannot import
into the Administration Console. In the WebSphere console, turn off the additional Java 2
security checks or create a policy that grants full access to the nesp application.
9.2 Authorization Policies Fail for Some
Attributes
The authorization policy fails if they are configured based on any of the following attributes:
LDAP Attribute
Liberty User profile
Summary of Contents for Access Manager 3.1 SP 2
Page 4: ...4 Novell Access Manager 3 1 SP2 J2EE Agent Guide novdocx en 16 April 2010...
Page 8: ...8 Novell Access Manager 3 1 SP2 J2EE Agent Guide novdocx en 16 April 2010...
Page 44: ...44 Novell Access Manager 3 1 SP2 J2EE Agent Guide novdocx en 16 April 2010...
Page 83: ...Preparing the Applications and the J2EE Servers 83 novdocx en 16 April 2010...
Page 108: ...108 Novell Access Manager 3 1 SP2 J2EE Agent Guide novdocx en 16 April 2010...