To set up the RREG tool, complete the following steps:

1. Log in to one of the Oracle Access Manager hosts in the Application tier.

2. Change directory to the following directory in the Oracle Access Manager Oracle home:

   Note:

   The location is required only for the out-of-band mode.

   OAM_ORACLE_HOME/oam/server/rreg/client

   In this example, OAM_ORACLE_HOME refers to the Oracle home on the system where the Oracle Access Manager software was installed.

   Note:

   If the Oracle Enterprise Deployment Guide for IDM was used, OAM_ORACLE_HOME may be /u01/oracle/products/access/iam.

   Note:

   If you do not have privileges or access to the Oracle Access Manager server, then you can use out-of-band mode to generate the required files and register the WebGate with Oracle Access Manager. See About RREG In-Band and Out-of-Band Mode.

3. Unzip the RREG.tar.gz file to the required directory.

4. From the unzipped directory, open the oamreg.sh file and set the following environment variables in the file, as follows:

   • Set OAM_REG_HOME to the absolute path to the directory in which you extracted the contents of RREG archive.

     Set JAVA_HOME to the absolute path of the directory in which a supported JDK is installed on your machine.

Before you can register the Webgate agent with Oracle Access Manager, you must update some required properties in the OAM11gRequest.xml file.

To perform this task:

1. If you are using in-band mode, then change directory to the following location on one of the OAM Servers:

   OAM_ORACLE_HOME/idm/oam/server/rreg/input

   If you are using out-of-band mode, then change directory to the location where you unpacked the RREG archive on the WEBHOST1 server.

2. Make a copy of the OAM11gRequest.xml file template with an environment-specific name.

   cp OAM11gRequest.xml OAM11gRequest_edg.xml

3. Review the properties listed in the file, and then update your copy of the OAM11gRequest.xml file to make sure the properties reference the host names and other values specific to your environment.

<hostPortVariationsList>
  <hostPortVariations>
    <host>soainternal.example.com</host>
    <port>80</port>
  </hostPortVariations>
  <hostPortVariations>
    <host>admin.example.com</host>
    <port>80</port>
  </hostPortVariations>
  <hostPortVariations>
    <host>osb.example.com</host>
    <port>443</port>
  </hostPortVariations>
</hostPortVariationsList>

The files that get generated by the RREG Tool vary, depending on the security level you are using for communications between the WebGate and the Oracle Access Manager server. See Securing Communication Between OAM Servers and WebGates in Administrator's Guide for Oracle Access Management.

Note that in this topic any references to RREG_HOME should be replaced with the path to the directory where you ran the RREG tool. This is typically the following directory on the Oracle Access Manager server, or (if you are using out-of-band mode) the directory where you unpacked the RREG archive:

OAM_ORACLE_HOME/oam/server/rreg/client

The following table lists the artifacts that are always generated by the RREG Tool, regardless of the Oracle Access Manager security level.

The following table lists the additional files that an administrator has to generate, if you are using the CERT security level for Oracle Access Manager: