17.5 Postinstallation Configuration

This section describes some postinstallation steps. This section includes the following topic:

17.5.1 Installing and Configuring Webgate with OAM

For webgate to work with Oracle Access Manager 11g, you must install and configure webgate manually. For information about installing and configuring webgate as the access client, see Installing and Configuring Oracle HTTP Server 11g Webgate for OAM in Oracle Fusion Middleware Installation Guide for Oracle Identity Managment.

Postinstallation, you must register webgate with OAM 11g so that webgate can directly communicate with Oracle Access Manager 11g services. Registration with OAM can be done by creating OAM 11g agent by using either RREG tool or through OAM console.

For information about registering webgate as an agent by using either OAM console or RREG tool, see Register the New Webgate Agent in Oracle Fusion Middleware Installation Guide for Oracle Identity Managment.

Reports OAM Integration Webgate

The mod_osso module is no longer included with Oracle HTTP Server. Oracle WebGate is the recommended replacement. WebGate is now installed with Oracle HTTP Server. For more details, see https://docs.oracle.com/middleware/1213/webtier/HSADM/whats_new.htm#HSADM1182 Webgate Configuration

Configure webgate in classic shiphome domain

Refer to https://docs.oracle.com/middleware/1213/core/WTINS/webgate.htm#WTINS870 for more details.

$MW_HOME/webgate/ohs/tools/deployWebGate/deployWebGateInstance.sh -w $DOMAIN_HOME/config/fmwconfig/components/OHS/instances/ohs1 -oh $MW_HOME
$MW_HOME/webgate/ohs/tools/setup/InstallTools/EditHttpConf -w  $DOMAIN_HOME/config/fmwconfig/components/OHS/instances/ohs1 -oh $MW_HOME -o webgate.conf Registering an OAM Agent Using the Console

For more details, see https://docs.oracle.com/cd/E28280_01/admin.1111/e15478/agents.htm#AIAAG219.

  1. Open the OAM Administration console and Login using OAM credentials.


  2. Click on New OAM 11g Webgate link on the welcome page.

  3. Provide the following information in the "Create OAM 11g Webgate" screen

    • Name: Any name to the webgate agent

    • Base URL: http://<OHS_HOST>:<OHS_PORT>

    • Protected Resource list: /reports/rwservlet/*

    • Public Resource List: / and /.../*


      We are currently seeing some issues with the Webgate public resource list. So skip steps Protected Resource List and Public Resource List. This will flatly protect all the entries accessed through OHS Host/port.
  4. Click Apply and, you will get a information box indicating the location of the artifacts generated.

Copy the output to OHS instance directory in Classic domain

  • cp <OAM webgate artifacts> $DOMAIN_HOME/config/fmwconfig/components/OHS/instances/ohs1/webgate/config

    The following two files will be copied:

  • cwallet.sso

  • ObAccessClient.xml

Restart OHS

Restart the OHS using the following commands:

DOMAIN_HOME/bin/stopComponent.sh ohs1

DOMAIN_HOME/bin/startComponent.sh ohs1

To access OHS reports url and test use the following command:



Instead of using OAM console you can also use RREG script to register a OAM agent. Refer to the links mentioned above.