4 Configuring Identity Management Targets

4.1 Prerequisites Before Configuring Grid Control for Identity Management Targets

The configuration steps in this chapter assume that:

• You have installed and configured Oracle Application Server Infrastructure installation type as a prerequisite for installing Oracle Collaboration Suite Release 2.

• You have installed and configured Grid Control 10g Release 2.

  As part of installing and configuring Grid Control, you should have also installed the Oracle Management Agent on the Oracle Collaboration Suite host computers.

  
  

  See Also: "About Local and Remote Monitoring with the Management Agent" for information about specific cases where the Oracle Management Agent can be installed on a system other than an Oracle Collaboration Suite component host.

  
  

• You have detailed knowledge of the Oracle Application Server Infrastructure components configured and where the different Oracle Application Server Infrastructure servers are running.

4.2 Overview of Identity Management Target Types

Oracle Application Server Infrastructure is installed as a set of services spread over hosts and databases. When you configure Grid Control to manage Oracle Application Server Infrastructure, you create the following Identity Management targets:

• One LDAP Server target for each Oracle Internet Directory (OID) node, which includes one OID server and one OID database.

• One Oracle Application Server Single Sign-On (SSO) target for each instance of the SSO server

• One OID Client target co-located with each Oracle Collaboration Suite component

• One SSO Web Application with representative transactions

• Related Host, Database, and Listener targets

This section includes the following sections that provide more information about Identity Management targets:

• About the OID Client Target

• About Discovery of the Identity Management Targets

4.3 Creating the LDAP Server Target

These sections describe the two ways to add an LDAP Server target to Grid Control:

• Automatically Discovering the LDAP Server as Part of an Existing Oracle Application Server Installation

• Manually Adding the LDAP Server Target

4.4 Creating the Single Sign-On (SSO) Server Target

These sections describe the two ways to add an SSO Server target to Grid Control:

• Automatically Discovering the SSO Server Target as Part of an Existing Oracle Application Server Installation

• Manually Adding the Single Sign-On Server Target

4.5 Creating the OID Client Target

OID Client targets are useful to measure responsiveness of the OID (Oracle Internet Directory) component. An OID Client target should be created on each machine where an Oracle Collaboration Suite middle tier is installed (on each machine where an Oracle Application Server for Oracle Collaboration Suite is installed).

To create the OID Client target:

OID Client targets are useful to measure responsiveness of the OID (Oracle Internet Directory) component. An OID Client target should be created on each machine where an Oracle Collaboration Suite middle tier is installed (on each machine where an Oracle Application Server for Oracle Collaboration Suite is installed).

To create the OID Client target:

1. In Grid Control, navigate to the Agent home page for the Oracle Management Agent that was installed on the OID Client host. Use these steps to navigate to the appropriate Agent home page:

   1. Click Setup at the top of any Grid Control page.

   2. Click Agents in the Overview of Setup page subtab.

   3. In the Agents table on the Agents page, click the link for the Management Agent for the OID Client host.

2. In the Monitored Targets section of the page, select OID Client from the Add box, then click Go.

   Grid Control displays the property page for the OID Client target type. Provide the required information, as described in Table 4-3.

3. Click OK to create the target.

   
   

   See Also: "Adding Targets to be Monitored and Administered by Enterprise Manager" in the Grid Control online help

   
   

   Table 4-3 OID Client Target Properties

   Property	Description
   LDAP Client Oracle Home Path	The path of the Oracle home of the LDAP client machine. This will be used to invoke the ldapsearch/ldapcompare utility for the computation of the various OID Client metrics. As a result, the ldapsearch/ldapcompare utility should exist in the following directory: $<LDAP_Client_Oracle_home>/bin/ This is always the case for any OCS install.
   LDAP Host	The host name of the machine where the LDAP server is running.
   LDAP Port	The port where the LDAP server is running.
   LDAP User	The user name of a test user account that is needed for the ldapsearch/ldapcompare command. It is possible to simply use the default user setup for Enterprise Manager monitoring: "cn=emd admin,cn=oracle internet directory".
   LDAP Password	The password of a test user account that is needed for the ldapsearch/ldapcompare command. For the Enterprise Manager monitoring user, the default is welcome.
   DC	The domain component, that is, the domain name of the component in a Domain Name System (DNS). For example: dc=uk,dc=acme,dc=com

   
   

4.6 Creating a Single Sign-On Web Application Target

To monitor your Single Sign-On instances, you create a Web Application target. Web Application targets can be monitored for availability and performance with Application Service Level Management transactions. You can also measure the response time of pages in your Web Applications using End-User Page Performance Monitoring.

To create a Web Application target for your SSO instance:

1. Click Submit to create the target.

2. Navigate to the Web Application home page and use the instructions in the online help to create representative transactions to measure the availability and performance of the Web Application you just created.

   
   

   See Also: "Creating Transactions" in the Grid Control online help

   
   

   Specifically, create a transaction that accesses the following URLs:

   1. https://<collaboration_suite_host>/help/hello.html - User Action

      This URL will not work in the default Single Sign-On environment in OCS release 2. In this case, you should create a transaction by going to the Portal page, logging in, and then logging out.

   2. https://<sso_server>/pls/orasso/orasso.wwsso_app_admin.ls_login - User Action

   3. https://<sso_server>/pls/orasso/orasso.wwsso_app_admin.ls_login - User Action

   4. https://<sso_server>/oiddas/login/signon.jsp - User Action

   5. https://<sso_server>/pls/orasso_basic/ORASSO.wwsso_app_admin.ls_login - User Action

   6. https://collaboration_suite_host>/help/hello.html - Redirect

3. Configure the Web Application target so that the transaction you just created is used as the availability transaction for the target.

   
   

   See Also: "Defining Availability Transactions and Beacons" in the Grid Control online help

   
   

4. Enable End-User Page Performance Monitoring for the Web Application using the procedures for earlier versions of the Oracle Application Server described in "Configuring End-User Performance Monitoring Using Earlier Versions of Oracle Application Server Web Cache" in Oracle Enterprise Manager Advanced Configuration for Oracle Enterprise Manager Grid Control 10g Release 2 at:

   http://www.oracle.com/technology/documentation/oem.html

   
   

   Note: Before you enable End-User Page Performance Monitoring to monitor your Oracle Collaboration Suite Web Application target, you must apply patch number 3040716 to the Oracle Application Server middle-tier instance. You can download this patch from OracleMetaLink: http://metalink.oracle.com/

   
   

5. On an Oracle HTTP Server middle tier where mod_osso is configured, create a directory named private under htdocs and an HTML file in the private directory that contains <html>hello</html>. Name the file helloworld.html.

6. Statically protect the URL for the HTML file with mod_osso by applying a directive to the mod_osso.conf file, which is found at $ORACLE_HOME/Apache/Apache/conf. Create the following directive to protect the /private directory located just below the Oracle HTTP Server document root:

   <IfModule mod_osso.c>
   
     <Location /private>
       AuthType Basic
       require valid-user
     </Location>
   
   <IfModule>
   
   

7. Restart the Oracle HTTP Server:

   $ORACLE_HOME/opmn/bin/opmnctl restartproc type=ohs
   
   

8. After making the entry to the mod_osso.conf file, perform this test:

   http://host:port/private/helloworld.html
   
   

4.7 Creating the Identity Management Group Target

After you configure the Oracle Application Server infrastructure targets, you can create a group target so you can manage these targets as a single entity. To ensure the group is created correctly, it is important to ensure that all the Oracle Application Server infrastructure targets have been created. Also, ensure that the host targets and application server targets used by the Oracle Application Server infrastructure targets are discovered and visible in Grid Control.

To create the group target:

1. Click the Targets tab in Grid Control.

2. Click All Targets.

3. Select Collaboration Suite Component from the Add box, then click Go.

   Grid Control displays the Create Collaboration Suite Component page.

4. Select IM from the Component Type box.

5. Enter a name for the Oracle Application Server Infrastructure group in the Name field.

   For example, enter Oracle AS Infrastructure Group.

6. Select the targets that you want to add to the group from the Available Targets list and add them to the Selected Targets list.

   Be sure to add the following targets to the Oracle Application Server Infrastructure group:

   • The hosts where the Oracle Application Server Infrastructure targets resides

   • The LDAP Server target you created in Section 4.3.

   • The SSO Server target you created in Section 4.4

   • The OID Client target you created in Section 4.5

   • The OID and SSO database target

   • The listener for the OID database

   • The SSO Server Web Application target you created in Section 4.6

7. Click OK to create the group target.

8. Add the Oracle Application Server Infrastructure group to the Oracle Collaboration Suite group you created in Section 3.4.4.