Extending Domain for Oracle Adaptive Access Manager

12-2 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 4. Create a WebLogic domain described in Chapter 6 . 5. Install and Configure Identity Store Oracle Internet Directory or Oracle Virtual Directory. 6. Install and configure Policy Store as described in Section 10.3, Preparing the OPSS Policy Store. 7. Create Oracle Adaptive Access Manager Administrative groups and user in LDAP as described in Section 10.4.3, Creating Users and Groups for Oracle Adaptive Access Manager.

12.2 Configuring Oracle Adaptive Access Manager on IDMHOST1

Although OAAM is deployed on servers dedicated to it OAAMHOST1 and OAAMHOST2, the Weblogic domain must first be extended with OAAM on IDMHOST1. This section describes how to configure Oracle Adaptive Access manager on IDMHOST1. This section contains the following topics: ■ Section 12.2.1, Extending Domain for Oracle Adaptive Access Manager ■ Section 12.2.2, Starting Administration Server on IDMHOST1 ■ Section 12.2.3, Creating OAAM Administration User in WebLogic Console ■ Section 12.2.4, Configuring Oracle Adaptive Access Manager on OAAMHOST1

12.2.1 Extending Domain for Oracle Adaptive Access Manager

Start the configuration wizard by executing the command: MW_HOME oracle_commoncommonbinconfig.sh Then proceed as follows:

1. On the Welcome Screen, select Extend an Existing WebLogic Domain. Click Next

2. On the Select a WebLogic Domain screen, using the navigator select the domain home of the Administration Server, for example: ORACLE_ BASE adminIDMDomainaserverIDMDomain. Click Next. 3. On the Select Extension Source screen, select the following: ■ Oracle Adaptive Access Manager - Server ■ Oracle Adaptive Access Manager Admin Server ■ Oracle WSM Policy Manager ■ Oracle Identity Navigator Click Next 4. The Configure RAC Multi Data Sources screen displays the schedulerDS Data Source configured for Oracle Directory Integration Platform and Oracle Directory Services manager ODSM. Do not make any selections or changes on this screen. Click Next. 5. On the Configure JDBC Component Schema screen, select all of the data sources, then select Configure selected data sources as RAC multi data sources. Extending the Domain with Oracle Adaptive Access Manager 12-3 Click Next. 6. On the Configure RAC Multi Data Source Component Schema page Real Applications Cluster Databases only, select all the schemas for your component. Do not select schemas listed for previously configured components. Then enter the following information: If you are using Oracle Database 11.2, replace the vip addresses with the 11.2 SCAN address. Click Next. 7. On the Test Component Schema screen, the configuration wizard attempts to validate the data source. If the data source validation succeeds, click Next. If it fails, click Previous, correct the issue, and try again.

8. On the Select Optional Configuration screen, select Managed Server Clusters and

Machines . Click Next 9. When you first enter the Configure Managed Servers screen, the configuration wizard has created a default Managed Server for you. Change the details of the default managed server . Schema Name Service Name Host Names Instance Names Port Schema Owner Password OAAM Admin Schema oaam.mycomp any.com oaamdbhost1-v ip.mycompany. com oaamdb1 1521 EDG_OAAM password oaamdbhost2-v ip.mycompany. com oaamdb2 1521 OAAM Admin MDS Schema oaam.mycomp any.com oaamdbhost1-v ip.mycompany. com oaamdb1 1521 EDG_MDS password oaamdbhost2-v ip.mycompany. com oaamdb2 1521 OAAM Server Schema oaam.mycomp any.com oaamdbhost1-v ip.mycompany. com oaamdb1 1521 EDG_OAAM password oaamdbhost2-v ip.mycompany. com oaamdb2 1521 OWSM MDS Schema oidedg.myco mpany.com oiddbhost1-vi p.mycompany.c om idmdb1 1521 EDG_MDS password oiddbhost2-vi p.mycompany.c om idmdb2 1521 12-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management For the oaam_server_server1 entry, change the entry to the following values: ■ Name : WLS_OAAM1 ■ Listen Address : OAAMHOST1 ■ Listen Port :14300 ■ SSL Listen Port : 14301 ■ SSL Enabled : Selected. For the second OAAM Server, click Add and supply the following information: ■ Name : WLS_OAAM2 ■ Listen Address : OAAMHOST2 ■ Listen Port : 14300 ■ SSL Listen Port : 14301 ■ SSL Enabled : selected Select the oaam_admin_server1 entry. Change the entry to the following values: ■ Name : WLS_OAAM_ADMIN1 ■ Listen Address : OAAMHOST2 ■ Listen Port :14200 ■ SSL Listen Port : 14201 ■ SSL Enabled : Selected For the OAAM Administration Server, click Add and supply the following information: ■ Name : WLS_OAAM_ADMIN2 ■ Listen Address : OAAMHOST2 ■ Listen Port : 14200 ■ SSL Listen Port : 14201 ■ SSL Enabled - selected Leave all the other fields at the default settings and click Next. 10. On the Configure Clusters screen, create a cluster by clicking Add. ■ Name : cluster_oaam. ■ Cluster Messaging Mode : unicast Create a second cluster by clicking Add. Note: When you first enter this screen the config wizard has created a default Managed Server for you. Change the details of the default Managed Server to reflect the following details. That is, change one entry and add one new entry. Do not change the configuration of any Managed Servers which have already been configured as part of previous application deployments. Extending the Domain with Oracle Adaptive Access Manager 12-5 ■ Name : cluster_oaam_admin ■ Cluster Messaging Mode : unicast Leave all other fields at the default settings and click Next. 11. On the Assign Servers to Clusters screen, associate the Managed Servers with the cluster. Click the cluster name in the right pane. Click the Managed Server under Servers , then click the arrow to assign it to the cluster. The cluster_oaam has the Managed Servers WLS_OAAM1 and WLS_OAAM2 The cluster_oaam_admin has the Managed Servers WLS_OAAM_ADMIN1 and WLS_OAAM_ADMIN2 Click Next. 12. On the Configure Machines screen, create a machine for each host in the topology. Click the tab UNIX if your hosts use a UNIX-based operating system. Otherwise, click the Machines tab. Supply the following information: ■ Name : Name of the host. Best practice is to use the DNS name oaamhost1.mycompany.com. ■ Node Manager Listen Address : The DNS name of the machine oaamhost1.mycompany.com ■ Node Manager Port : A port for Node Manager to use Click Next. 13. On the Assign Servers to Machines screen, indicate which Managed Servers to run on each of the machines you created. Click a machine in the right pane. Click the Managed Servers you want to run on that machine in the left pane. Click the arrow to assign the Managed Servers to the machines. Repeat until all Managed Servers are assigned to machines. For example: oaamhost1 : WLS_OAAM1 and WLS_OAAM_ADMIN1 oaamhost2 :WLS_OAAM2 and WLS_OAAM_ADMIN2 Click Next to continue. 14. On the Configuration Summary screen, click Extend to extend the domain. Note: Do not change the configuration of any clusters which have already been configured as part of previous application deployments. 12-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

12.2.2 Starting Administration Server on IDMHOST1