Novell ACCESS MANAGER 3.1 SP2 - README 2010, Manual

Page: 331 / 374

Maintaining an Identity Server 331
n
ov
do
cx (e
n)
16
Ap
ril 20
10
Status Category If not healthy
Status: Indicates whether the Identity Server is
online and operational.
Verify whether the Identity Server has been
stopped or is not configured.
Also verify that network problems are not
interfering with communications between the
Identity Server and the Administration Console.
Services: Indicates the general health of all
configured services.
If one service is unhealthy, this category reflects
that status. See the particular service that also
displays an unhealthy status.
Identity Server Configuration: Indicates the
status of the configuration.
Configure the Identity Server or assign the
server to a configuration. See
Chapter 1,
“Configuring an Identity Server,” on page 15 .
Configuration Datastore: Indicates the status
of the installed configuration datastore.
You might need to restart Tomcat or reinstall the
Administration Console.
If you have a backup Administration Console,
you can restore it. See “
Backing Up and
Restoring ” in the Novell Access Manager 3.1
SP2 Administration Console Guide .
If you don’t have a backup, you can try repairing
the configuration datastore. See “
Repairing the
Configuration Datastore ” in the Novell Access
Manager 3.1 SP2 Administration Console Guide .
If you want to convert a secondary console to
your primary console, see “
Converting a
Secondary Console into a Primary Console ” in
the Novell Access Manager 3.1 SP2
Administration Console Guide .
User Datastores: Indicates whether the Identity
Server can communicate with the user stores,
authenticate as the admin user, and find the
search context.
Ensure that the user store is operating and
configured correctly. You might need to import
the SSL certificate for communication with the
Identity Server. See
Section 3.1, “Configuring
Identity User Stores,” on page 104 .
Signing, Encryption and SSL Connector
Keys:
Indicates whether these keystores
contain valid a key.
Click Identity Servers > Edit > Security and
replace any missing or expired keys.
System Incoming and Outgoing HTTP
Requests:
Appears when throughput is slow.
This health check monitors incoming HTTP
requests, outgoing HTTP requests on the SOAP
back channel, and HTTP proxy requests to
cluster members. If one or more requests remain
in the queue for over 2 minutes, this health
check appears.
Verify that all members of the cluster have
sufficient bandwidth to handle requests. If a
cluster member is going down, the problem
resolves itself as other members of the cluster
are informed that the member is down.
If a cluster member is slow because it doesn’t
have enough physical resources (speed or
memory) to handle the load, upgrade the
hardware.