11
Monitoring the Single Sign-On Server

This chapter explains how to use Oracle Enterprise Manager, the Oracle system management console, to monitor the single sign-on server.

The chapter contains the following topics:

• Accessing the Monitoring Pages

• Interpreting and Using the Home Page on the Standalone Console

• Interpreting and Using the Details of Login Failures Page

• Updating the Port Property for the Single Sign-On Monitoring Target

Accessing the Monitoring Pages

The single sign-on monitoring UI on the standalone console consists of two pages: The home page and the Details of Login Failures page. The first provides general information about server load and user activity. The second provides a login failure profile for a particular user.

To access the home page for single sign-on monitoring:

1. Go to the standalone console for the instance of Oracle Enterprise Manager that you want to administer. This is effected by entering the host name of the computer hosting the OracleAS instance and the port number of Oracle Enterprise Manager. The default port number is 1812, but it may be configured in increments of one, up to 1816.

2. Log in using the credentials of an OracleAS administrator.

3. From the Standalone Instances section of the Farm page, choose the appropriate OracleAS instance.

4. From the System Components list of the Application Server page, choose the single sign-on server.

Interpreting and Using the Home Page on the Standalone Console

The home page, reproduced in Figure 11-1, displays the following metrics in the General section:

• Status

  A green "up" arrow signifies that the database serving the single sign-on schema is running. A red "down" arrow signifies that the database is down.

• Start Time

  The start time of the database serving the single sign-on schema.

• Database

  SID/instance name of the database serving the single sign-on schema.

• Database Version

  Version of the database serving the single sign-on schema.

The Last 24 Hours Status Details section contains the following metrics:

• Logins

• Successful Logins

• Failed Logins

As the heading implies, the statistics displayed are for the previous 24 hours.

The Login Failures During the Last 24 Hours section enables you to determine the number of login failures that have occurred during the previous 24 hours. You choose a name from the Login Failures During the Last 24 Hours table. You then choose the associated link under the Failures heading. When populated, this link contains the number of login failures for the user. Clicking it takes you to the Details of Login Failures page.

Figure 11-1 Monitoring Home Page for OracleAS Single Sign-On

Text description of the illustration monhome.gif

The Related Links section contains the following links:

• HTTP Server

  Takes you to the monitoring home page for the Oracle HTTP Server

• Administer via Single Sign-On

  Takes you to the home page for single sign-on administration

Interpreting and Using the Details of Login Failures Page

Clicking a link in the Login Failures During the Last 24 Hours table takes you to the Details of Login Failures page (Figure 11-2). This page contains a table that displays login failure times and associated IP addresses for a particular user.

Figure 11-2 Details of Login Failures Page

Text description of the illustration monitor_.gif

Updating the Port Property for the Single Sign-On Monitoring Target

A change in the port number of the Oracle HTTP Server requires a change in the port property of the single sign-on monitoring target on that server. Perform these steps to effect the change:

1. Back up the targets.xml file:

   cp $ORACLE_HOME/emd/targets.xml $ORACLE_HOME/emd/targets.xml.backup
   
   

   This file is the configuration file for the various "targets" that Oracle Enterprise Manager monitors, one of which is OracleAS Single Sign-On.

2. In targets.xml, find the target type "oracle_sso_server"; then locate and edit the HTTP port value associated with this target type:

   <Property NAME="HTTPPort" VALUE="7777"/>
   
   

3. Save and close the file.

4. Reload the OracleAS Console:

   $ORACLE_HOME/bin/emctl reload
   
   

   Note: For more information about port dependency changes, see Oracle Application Server 10g Administrator's Guide.