Configure Oracle Access Management 12c

Introduction

This tutorial shows you how to run the Repository Creation Utility to load the Oracle Access Management (OAM) database schemas. It also shows how to create the Oracle Access Management 12c domain.

This is the fifth tutorial in the series Getting Started with Oracle Access Management 12c. Read them sequentially.

Objective

To load the OAM schemas into the Oracle Database, and create the Oracle Access Management 12c domain.

Prerequisites

To have followed Install Oracle Access Management 12c.

Run the Repository Creation Utility

  1. Launch a terminal window as oracle and enter the following commands:

    cd /u01/app/oracle/product/middleware/oracle_common/bin
./rcu

  2. Follow the table below to guide you through the installation screens:

    Step Window Description Choice or Values
    1 Welcome Click Next
    2 Create Repository System Load and Product Load
    3 Database Connection Details Database Type: Oracle Database
    Host Name: oam.example.com
    Port: 1521
    Service Name: orcl.example.com
    Username: sys
    Password: <password>
    Role: SYSDBA

    Click OK in Checking Prerequisites window
    4 Select Components Create a new prefix: DEV
    Under IDM Schemas select Oracle Access Manager

    Click OK in Checking Prerequisites window
    5 Schema Passwords Use same passwords for all schemas
    Password: <password>
    Confirm Password: <password>
    6 Map Tablespaces Click Next

    Click OK in Confirmation and Creating Tablespaces windows
    7 Summary Click Create
    8 Completion Summary Click Close

Configure the Oracle Access Management 12c Domain

  1. Launch a terminal window as oracle and enter the following commands:

    cd /u01/app/oracle/product/middleware/oracle_common/common/bin
./config.sh

  2. Follow the table below to guide you through the configuration screens:

    Step Window Description Choice or Values
    1 Create Domain Select Create a new domain
    Domain Location: /u01/app/oracle/admin/domains/oam_domain
    2 Templates Select: Oracle Access Management Suite
    3 Application Location Application Location: /u01/app/oracle/admin/applications/oam_domain
    4 Administrator Account Name: weblogic
    Password: <password>
    Confirm: <password>
    5 Domain Mode and JDK Domain Mode: Production
    JDK: Oracle Hotspot
    6 Database Configuration Type Host Name: oam.example.com
    DBMS/Service: orcl.example.com
    Port: 1521
    Schema Owner: DEV_STB
    Schema Password: <password>

    Click Get RCU Configuration
    If successful, click Next
    7 Component Datasources Click Next
    8 JDBC Component Schema Test Click Next
    9 Advanced Configuration Select Node Manager, and Topology
    10 Node Manager Node Manager Type: Per Domain Default Location
    Username: weblogic
    Password: <password>
    Confirm Password: <password>
    11 Managed Servers Click Next
    12 Clusters Click Next
    13 Server Templates Click Next
    14 Coherence Clusters Click Next
    15 Machines Click Add
    Name: oam_machine
    16 Assign Servers to Machines Select Admin Server, oam_server1 and oam_policy_mgr1.
    Select oam_machine and click the right arrow to move the servers under oam_machine
    17 Virtual Targets Click Next
    18 Partitions Click Next
    19 Configuration Summary Click Create
    20 Configuration Progress Click Next
    21 End of Configuration Click Finish

Apply Patch 33903365

Due to an issue with JDK 1.80.331 or later you must download and apply Patch 33903365.

Note: This section is true at the time of writing. If you are unsure about whether to apply this patch please contact Oracle Support.

  1. Launch a browser and access My Oracle Support.

  2. Download Patch 33903365: OAM CONSOLE LOGIN FAILS AFTER APPLYING 1.80.331 JDK ( APRIL JAVA CPU ) for OAM 12.2.1.4.0

  3. Run the following commands to set the PATH before applying the patch:

    export ORACLE_HOME=/u01/app/oracle/product/middleware
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH

  4. Apply the patch as per the patch README.

For any issues applying the patch please contact Oracle Support.

Start the Servers

  1. Launch a terminal window as oracle and enter the following commands to start the Oracle Access Management 12c Administration server:

    cd /u01/app/oracle/admin/domains/oam_domain/
./startWebLogic.sh

    When prompted enter the WebLogic administrator credentials (weblogic/<password>):

    Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server: ********

    Wait until the terminal displays the message The server started in RUNNING mode, then minmize the window:

    <DATE> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.> 
<DATE> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>

  2. In another terminal window start Node Manager by running the following command:

    cd /u01/app/oracle/admin/domains/oam_domain/bin
./startNodeManager.sh

    Wait until the terminal displays that node manager is running, then minmize the window:

    <DATE> <INFO> <Secure socket listener started on port 5556, host localhost/127.0.0.1>

  3. Launch a terminal window as oracle and enter the following commands to start the OAM Managed Server:

    cd /u01/app/oracle/admin/domains/oam_domain/bin
./startManagedWebLogic.sh oam_server1

    When prompted enter the WebLogic administrator credentials (weblogic/<password>):

    Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server: ********

    Wait until the terminal displays the message server started in RUNNING mode, then minmize the window:

    <DATE> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.> 
<DATE> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>

  4. Launch a terminal window as oracle and enter the following commands to start the OAM Policy Manager Managed Server:

    cd /u01/app/oracle/admin/domains/oam_domain/bin
./startManagedWebLogic.sh oam_policy_mgr1

    When prompted enter the WebLogic administrator credentials (weblogic/<password>):

    Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server: ********

    Wait until the terminal displays the message server started in RUNNING mode, then minmize the window:

    <DATE> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.> 
<DATE> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>

Validate the installation

Access the WebLogic Server Console

  1. Launch a browser and access the WebLogic Server Console at http://oam.example.com:7001/console. Login as weblogic/<password>.

  2. In the Domain Structure pane, under oam_domain navigate to Environment > Servers. Make sure all the servers show as running:

    Description of the illustration weblogic.jpg

Access the OAM Console

  1. Launch a browser and access the Oracle Access Management Console at http://oam.example.com:7001/oamconsole. Login as weblogic/<password>. The OAM console should be displayed:

    Description of the illustration oamconsole.jpg

Access the OAM Policy Manager Console

  1. Launch a browser and access the OAM Policy Manager Console at http://oam.example.com:14150/access. Login as weblogic/<password>. The OAM Policy Manager console should be displayed.

    Note: The OAM Policy Manager console looks the same as the Oracle Access Management Console, however it does not contain the full functionality available in the Oracle Access Management Console deployed on the AdminServer. The Policy Manager Console has only the policy administration functionality.

Configure boot.properties

In this section you create boot.properties files to prevent having to enter the weblogic username and password on startup.

  1. Launch a terminal window as oracle and enter the following commands:

    mkdir /u01/app/oracle/admin/domains/oam_domain/servers/AdminServer/security
mkdir /u01/app/oracle/admin/domains/oam_domain/servers/oam_server1/security
mkdir /u01/app/oracle/admin/domains/oam_domain/servers/oam_policy_mgr1/security
cd /u01/app/oracle/admin/domains/oam_domain/servers/AdminServer/security
echo -e "username=weblogic\npassword=<password>" >boot.properties
cp boot.properties ../../oam_server1/security/
cp boot.properties ../../oam_policy_mgr1/security/

    where <password> is your weblogic password.

Next Tutorial

Configure SSL for Oracle Access Management 12c

Feedback

To provide feedback on this tutorial, please contact idm_user_assistance_ww_grp@oracle.com

Acknowledgements