Extending Domain with Oracle Access Manager

Extending the Domain with Oracle Access Manager 11g 11-3 ■ Section 11.3.3, Propagating the Domain Changes to the Managed Server Domain Directory

11.3.1 Extending Domain with Oracle 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 WebLogic Administration Server, for example: ORACLE_ BASE adminIDMDomainaserverIDMDomain. Click Next 3. On the Select Extension Source screen, select Oracle Access Manager with Database Policy Store . Click Next 4. The schedulerDS Multi Data Source is shown the Configure RAC Multi Data Sources screen, if you have Oracle Directory Integration Platform configured in your domain. Do not make any changes to this data source. Click Next. 5. On the Configure JDBC Component Schema screen select the datasource OAM Infrastructure . Select Configure selected data sources as RAC multi data sources in the next panel. Click Next. 6. On the Configure RAC Multi Data Sources Screen: ■ Service Name : Service name of the database that contains the Oracle Access Manager repository oamedg.mycompany.com ■ User Name : EDG_OAM ■ Password : Password for user EDG_OAM In the top right box, click Add to add the second Oracle RAC node. ■ Host Name : OIDDBHOST1-VIP ■ Instance Name : idmdb1 ■ Port : 1521 Click Add again to add the second database host: ■ Host Name : OIDDBHOST2-VIP ■ Instance Name : idmdb2 ■ Port : 1521 If you are using Oracle Database 11.2, replace the vip addresses and port with the 11.2 SCAN address and port. Click Next. 11-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 7. On the Test Component Schema screen, the Wizard attempts to validate the data sources. If the data source validation succeeds, click Next. If it fails, click Previous, correct the problem, and try again.

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

and Machines . Click Next 9. When you first enter the Configure Managed Servers screen, the configuration wizard creates a default Managed Server for you. AT this point, you must do two things: a. Change the values of the default Managed Server. b. Add a second Managed Server and supply values for it. That is, you must change the existing 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. For the default Oracle Access Manager server oam_server entry, change the following values: ■ Name : WLS_OAM1 ■ Listen Address : IDMHOST1 To add the second Oracle Access Manager Server, click Add and supply the following values: ■ Name : WLS_OAM2 ■ Listen Address : IDMHOST2 ■ Listen Port : 14100 Leave all the other fields at the default settings. Click Next. 10. On the Configure Clusters screen, create a cluster by clicking Add. Supply the following information: ■ Name : cluster_oam ■ 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_oam has the Managed Servers WLS_OAM1 and WLS_OAM2. 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 Linux or a UNIX-based operating system. Otherwise, click machines. Supply: Note: Do not change the configuration of any clusters which have already been configured as part of previous application deployments. Extending the Domain with Oracle Access Manager 11g 11-5 ■ Name : The name of the host. Best practice is to use the DNS name. For example: idmhost1.mycompany.com and idmhost2.mycompany.com for the first and second nodes respectively. ■ Node Manager Listen Address : The DNS name of the machine. For example: idmhost1.mycompany.com and idmhost2.mycompany.com for the first and second nodes respectively. ■ Node Manager Port : A port for Node Manager to use. If you have already configured Oracle Directory Integration Platform or ODSM, machines already exist for those hosts. 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: IDMHOST1 : WLS_OAM1 IDMHOST2 : WLS_OAM2 Click Next to continue. 14. On the Configuration Summary screen, click Extend to extend the domain.

15. On the Installation Complete screen, click Done.

16. Restart WebLogic Administration Server as described in Section 20.1, Starting and Stopping Oracle Identity Management Components.

11.3.2 Removing IDM Domain Agent