Updating Oracle HTTP Server Configuration Restarting Oracle HTTP Server Changing Host Assertion in WebLogic

Extending the Domain with Oracle Adaptive Access Manager 12-9 running the setNMProps.sh script located under the MW_HOMEoracle_ commoncommonbin directory. prompt MW_HOMEoracle_commoncommonbin prompt .setNMProps.sh 3. Stop and Start the Node Manager as described in Section 20.1, Starting and Stopping Oracle Identity Management Components so that the properties take effect.

12.4.2.2 Starting Oracle Adaptive Access Manager on OAAMHOST2

Start Oracle Adaptive Access Manager on OAAMHOST2 by following the start procedures in Section 20.1, Starting and Stopping Oracle Identity Management Components for: ■ Node Manager ■ WebLogic Managed Servers WLS_OAAM1 and WLS_OAAM_ADMIN1

12.4.3 Validating OAAMHOST2

Validate the implementation by connecting to the OAAM Administration Server at http:OAAMHOST2.mycompany.com:14200oaam_admin. The implementation is valid if OAAM Administration console login page is displayed and you can login using the oaamadmin account you created in Section 10.4.3, Creating Users and Groups for Oracle Adaptive Access Manager. Validate the implementation by connecting to the OAAM Server at: http:OAAMHOST2.mycompany.com:14300oaam_server The implementation is valid if the OAAM Server login page is displayed.

12.5 Configuring OAAM to Work with the Oracle HTTP Server

This section describes how to configure Oracle Adaptive Access Manager to work with the Oracle HTTP Server. This section contains the following topics: ■ Section 12.5.1, Updating Oracle HTTP Server Configuration ■ Section 12.5.2, Restarting Oracle HTTP Server ■ Section 12.5.3, Changing Host Assertion in WebLogic ■ Section 12.5.4, Validating Oracle Adaptive Access Manager

12.5.1 Updating Oracle HTTP Server Configuration

On each WEBHOST, create a file in ORACLE_ INSTANCE configOHSohs1moduleconf called oaam.conf with the following lines: Location oaam_server SetHandler weblogic-handler WebLogicCluster oaamhost1.mycompany.com:14300,oaamhost2.mycompany.com:14300 WLProxySSL ON WLProxySSLPassThrough ON Location 12-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management The OAAM Administration console must only be available through the admin.mycompany.com site. You achieve this by editing the file ORACLE_ INSTANCE configOHScomponentmoduleconfadmin.conf. You created admin.conf in Section 6.9, Configuring Oracle HTTP Server for the WebLogic Administration Server . Edit the virtual host definition in admin.conf. After editing the file should look like this: NameVirtualHost :80 VirtualHost :80 ServerName admin.mycompany.com:80 ServerAdmin youyour.address RewriteEngine On RewriteOptions inherit Admin Server and EM Location console SetHandler weblogic-handler WebLogicHost ADMINVHN WeblogicPort 7001 Location Location consolehelp SetHandler weblogic-handler WebLogicHost ADMINVHN WeblogicPort 7001 Location Location em SetHandler weblogic-handler WebLogicHost ADMINVHN WeblogicPort 7001 Location Location oaam_admin SetHandler weblogic-handler WebLogicCluster oaamhost1.mycompany.com:14200,oaamhost2.mycompany.com:14200 Location VirtualHost

12.5.2 Restarting Oracle HTTP Server

Restart the Oracle HTTP Server on WEBHOST1 and WEBHOST2, as described in Section 20.1, Starting and Stopping Oracle Identity Management Components.

12.5.3 Changing Host Assertion in WebLogic

Because the Oracle HTTP Server acts as a proxy for WebLogic, by default certain CGI environment variables are not passed through to WebLogic. These include the host and port. You must tell WebLogic that it is using a virtual site name and port so that it can generate internal URLs appropriately. To do this, log in to the WebLogic administration console at http:admin.mycompany.comconsole. Proceed as follows: Extending the Domain with Oracle Adaptive Access Manager 12-11

1. Select Clusters from the home page or, alternatively, select Environment -

Clusters from the Domain structure menu.

2. Click Lock and Edit in the Change Center Window to enable editing.

3. Click the Cluster Name cluster_oaam.

4. Select HTTP and enter the following values:

■ Frontend Host : sso.mycompany.com ■ Frontend HTTP Port: 80 ■ Frontend HTTPS Port: 443 This ensures that any HTTPS URLs created from within WebLogic are directed to port 443 on the load balancer.

5. Click Save.

6. Select Clusters from the home page or, alternatively, select Environment -

Clusters from the Domain structure menu.

7. Click the Cluster Name cluster_oaam_admin.

8. Select HTTP and enter the following values: ■ Frontend Host: admin.mycompany.com ■ Frontend HTTP Port: 80 9. Click Save. 10. Click Activate Changes in the Change Center window to enable editing. Restart Managed servers WLS_OAAM1, WLS_OAAM2, WLS_OAAM_ADMIN1 and WLS_ OAAM_ADMIN2 as described in Section 20.1, Starting and Stopping Oracle Identity Management Components.

12.5.4 Validating Oracle Adaptive Access Manager