{"id":878,"date":"2012-02-06T15:00:04","date_gmt":"2012-02-06T09:30:04","guid":{"rendered":"http:\/\/www.oratraining.com\/blog\/?p=878"},"modified":"2013-02-24T10:55:22","modified_gmt":"2013-02-24T10:55:22","slug":"configuring-oracle-identity-and-access-management-components-old","status":"publish","type":"post","link":"https:\/\/www.oratraining.com\/blog\/2012\/02\/configuring-oracle-identity-and-access-management-components-old\/","title":{"rendered":"Configuring Oracle Identity and Access Management components"},"content":{"rendered":"

Important Note: <\/span><\/h2>\n

This is OLD guide for old version 11.1.1.5. Please follow instructions at\u00a0<\/span>http:\/\/www.oratraining.com\/blog\/2012\/12\/oracle-fusion-applications-installation-step-by-step-guide-11-1-5\/<\/a><\/h2>\n

for latest guide for current version i.e. 11.1.5<\/span><\/h2>\n

\u00a0<\/a><\/p>\n

Oracle Fusion Applications Installation<\/span>: Configuring Oracle Identity and Access Management components
\n<\/strong><\/span><\/p>\n

Previous:\u00a0Installing Oracle Identity and Access Management Components<\/a><\/strong><\/p>\n

Configuring Oracle Identity Management components” can be divided into following tasks.<\/p>\n

    \n
  1. Configuring the Web Tier<\/li>\n
  2. Create Weblogic Domain for Identity Management<\/li>\n
  3. Extending the Domain with Oracle Internet Directory<\/li>\n
  4. Extending the Domain with Oracle Directory Service Manager (ODSM)<\/li>\n
  5. Extending the Domain with Oracle Virtual Directory<\/li>\n
  6. Extending the Domain with Oracle Access Manager<\/li>\n
  7. Extending the Domain to Configure Oracle Identity Manager and Oracle SOA Suite<\/li>\n
  8. Installing and Configuring WebGate<\/li>\n<\/ol>\n

    Please note that this post is going to be long so allow time to load all images.<\/span><\/p>\n

    Configuring the Web Tier
    \n<\/strong><\/span><\/p>\n

    Start the configuration from <Web_Home>\/bin
    \n<\/strong><\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/Oracle_WT1\/bin<\/strong><\/p>\n

    [oracle@fusion bin]$ .\/config.sh<\/strong><\/p><\/blockquote>\n

    \"\"<\/p>\n

    \"\"<\/p>\n

    Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select “Oracle HTTP Server<\/strong>” and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    For Instance location enter “\/app\/fusion\/bea_default\/instances” since we will keep all instances in this location. Provide any appropriate Instance name and OHS component name. We will go for the defaults. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select “Specify Ports using Configuration File<\/strong>” and enter file name as \/home\/oracle\/staticports.ini
    \n<\/strong><\/p>\n

    Now we will copy staticports.ini default file from <repository_location>\/installers\/webtier\/Disk1\/stage\/Response to home directory \/home\/oracle<\/p>\n

    cp \/mnt\/fusion\/installers\/webtier\/Disk1\/stage\/Response\/staticports.ini ~\/staticports.ini
    \n<\/strong><\/p><\/blockquote>\n

    Now click on “View\/Edit File<\/strong>” to edit this file.<\/p>\n

    \"\"<\/p>\n

    Uncomment and set the following values. Click Save<\/strong><\/p>\n

    OPMN Local Port = 6700
    \n<\/strong><\/p>\n

    OHS Port = 7777
    \n<\/strong><\/p>\n

    \"\"<\/p>\n

    Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Deselect email notification and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Save summary if needed and click Configure<\/strong> to start configuration.<\/p>\n

    Important Note:<\/strong> If SELinux is enabled in your Linux operating System then it will throw an error. Since we already disabled it during installation, we will not see that error here.<\/p><\/blockquote>\n

    \"\"<\/p>\n

    Once installation finishes, click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Save installation summary if needed and click Finish<\/strong> to complete the installation.<\/p>\n

    It would have already started HTTP server now. We can verify the same.<\/p>\n

    [oracle@fusion instances]$ ps -ef | grep http<\/p>\n

    oracle 3521 3491 0 10:06 ? 00:00:00 \/app\/fusion\/bea_default\/Oracle_WT1\/ohs\/bin\/httpd.worker -DSSL
    \n<\/span><\/p>\n

    oracle 3547 3521 0 10:06 ? 00:00:00 \/app\/fusion\/bea_default\/Oracle_WT1\/ohs\/bin\/httpd.worker -DSSL
    \n<\/span><\/p>\n

    oracle 3548 3521 0 10:06 ? 00:00:00 \/app\/fusion\/bea_default\/Oracle_WT1\/ohs\/bin\/httpd.worker -DSSL
    \n<\/span><\/p>\n

    oracle 3549 3521 0 10:06 ? 00:00:00 \/app\/fusion\/bea_default\/Oracle_WT1\/ohs\/bin\/httpd.worker -DSSL
    \n<\/span><\/p><\/blockquote>\n

    Check \/app\/fusion\/bea_default\/Oracle_WT1\/instances\/instance1\/config\/OHS\/ohs1\/httpd.conf to make sure it reflects correct user and group name<\/p>\n

    User oracle<\/strong><\/p>\n

    Group oinstall
    \n<\/strong><\/p>\n

    We can launch http:\/\/fusion:7777<\/span> (Homepage of Oracle HTTP server) now. It will look as follows.<\/p>\n

    \"\"<\/p>\n

    Create Weblogic Domain for Identity Management
    \n<\/strong><\/span><\/p>\n

     <\/p>\n

    Start the configuration from <Middleware Home>\/oracle_common\/commin\/bin<\/strong><\/p>\n

    [oracle@fusion bin]$ \/app\/fusion\/bea_default\/oracle_common\/common\/bin\/config.sh<\/p><\/blockquote>\n

    \"\"
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Select “Create a new Weblogic domain” and click Next
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Select “Oracle Enterprise Manager \u2013 11.1.1.0 [oracle_common]<\/strong>” and “Oracle JRF \u2013 11.1.1.0 [oracle_common]<\/strong>” and click Next
    \n<\/strong><\/p>\n

    \"\"<\/p>\n

    Enter details as above or accept default values and click Next.
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Since it accepts minimum 8 characters set password again to
    \n<\/strong>oracle123. Please note that you can also change username from weblogic but in future whenever we refer to weblogic user you must enter the new user which selected. We will go for default “weblogic” username<\/p>\n

    \"\"<\/a>
    \n<\/strong><\/p>\n

    You would see option of Oracle JRockit here. So select that JDK in this list.<\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Select “Administration Server” and “Managed Servers, Clusters and Machines”. Click Next<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Keep defaults but make a note of the port since this will be widely used during next part of installation. Click Next
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Just click Next
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Click Next<\/strong> again<\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Select Second Tab “Unix Machine<\/strong>” and enter the hostname as above. Click Next
    \n<\/strong><\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Click on AdminServer<\/strong> and Click right arrow. Click Next<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    It will now look as above. Click Next
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    On Summary page click Create
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Once installation finishes, click Done
    \n<\/strong><\/p>\n

    Make sure that the encrypted username and password values are already in boot.properties<\/p>\n

    [oracle@fusion security]$ more \/app\/fusion\/bea_default\/user_projects\/domains\/IDM_domain\/servers\/AdminServer\/security\/boot.properties<\/strong>
    \n<\/span><\/p>\n

    # Generated by Configuration Wizard on Mon Jan 23 10:59:07 GST 2012<\/p>\n

    username={AES}zaXc3+4y2KGuxnK6WkI7ehKcliQDeandkjdTdu0vpuY=<\/p>\n

    password={AES}WZ6Zo+j6aGoCyE2nQmCCdboEkA8TDGRlagdSqFGRedo=<\/p><\/blockquote>\n

     <\/p>\n

    Set StartScriptEnabled=true in nodemanager.properties by running following script<\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/oracle_common\/common\/bin<\/span><\/strong><\/p>\n

    [oracle@fusion bin]$ .\/setNMProps.sh<\/span>
    \n<\/strong><\/p>\n

    Appending required nodemanager.properties<\/p><\/blockquote>\n

    Verify the change.<\/p>\n

    [oracle@fusion bin]$ tail -f \/app\/fusion\/bea_default\/wlserver_10.3\/common\/nodemanager\/nodemanager.properties
    \n<\/span><\/strong><\/p>\n

    #Required NM Property overrides (append to existing nodemanager.properties)<\/p>\n

    StartScriptEnabled=true<\/p><\/blockquote>\n

     <\/p>\n

    Start Node manager
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/wlserver_10.3\/server\/bin
    \n<\/span><\/strong><\/p>\n

    [oracle@fusion bin]$ nohup .\/startNodeManager.sh &<\/span>
    \n<\/strong><\/p>\n

    \u2026
    \n<\/strong><\/p>\n

    IDM_domain -> \/app\/fusion\/bea_default\/user_projects\/domains\/IDM_domain<\/p>\n

    \u2026<\/p>\n

    INFO: Secure socket listener started on port 5556<\/p><\/blockquote>\n

     <\/p>\n

    Start Weblogic AdminServer
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion bin]$ nohup<\/strong><\/span>
    \n\/app\/fusion\/bea_default\/user_projects\/domains\/IDM_domain\/bin\/startWebLogic.sh &
    \n<\/strong><\/span><\/p><\/blockquote>\n

    tail nohup.out file until it shows following message.<\/p>\n

    <Jan 23, 2012 11:55:21 AM GST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode><\/strong><\/p>\n

     <\/p>\n

    Open Weblogic Admin Console
    \n<\/strong><\/span><\/p>\n

    Launch Weblogic Admin console through
    \n    http:\/\/fusion:7001\/console<\/a>
    \n<\/strong><\/p>\n

    \"\"<\/p>\n

    Login with weblogic\/oracle123<\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

     <\/p>\n

    Note: Go to preferences and change “automatic acquire lock” settings to avoid accidental changes since we are in development mode.<\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

     <\/p>\n

    Configuring HTTP server for the Administration Server<\/span>
    \n<\/span><\/strong><\/span><\/p>\n

     <\/p>\n

    Create a new file admin.conf as follows.<\/p>\n

     <\/p>\n

    [oracle@fusion moduleconf]$ more \/app\/fusion\/bea_default\/Oracle_WT1\/instances\/instance1\/config\/OHS\/ohs1\/moduleconf\/admin.conf<\/span>
    \n<\/strong><\/p>\n

    <VirtualHost *:7777><\/p>\n

    ServerName fusion:7777<\/p>\n

    ServerAdmin you@your.address<\/p>\n

    RewriteEngine On<\/p>\n

    RewriteOptions inherit<\/p>\n

    RewriteRule ^\/console\/jsp\/common\/logout.jsp \/oamsso\/logout.html [PT]<\/p>\n

    RewriteRule ^\/em\/targetauth\/emaslogout.jsp \/oamsso\/logout.html [PT]<\/p>\n

    # Admin Server and EM<\/p>\n

    <Location \/console><\/p>\n

    SetHandler weblogic-handler<\/p>\n

    WebLogicHost fusion<\/p>\n

    WeblogicPort 7001<\/p>\n

    <\/Location><\/p>\n

    <Location \/consolehelp><\/p>\n

    SetHandler weblogic-handler<\/p>\n

    WebLogicHost fusion<\/p>\n

    WeblogicPort 7001<\/p>\n

    <\/Location><\/p>\n

    <Location \/em><\/p>\n

    SetHandler weblogic-handler<\/p>\n

    WebLogicHost fusion<\/p>\n

    WeblogicPort 7001<\/p>\n

    <\/Location><\/p>\n

    <\/VirtualHost><\/p><\/blockquote>\n

     <\/p>\n

    Restart http server.<\/strong><\/p>\n

    ORACLE_HOME=\/app\/fusion\/bea_default\/Oracle_WT1<\/p>\n

    export ORACLE_HOME<\/p>\n

    ORACLE_INSTANCE=\/app\/fusion\/bea_default\/Oracle_WT1\/instances\/instance1<\/p>\n

    export ORACLE_INSTANCE<\/p>\n

    PATH=$ORACLE_HOME\/opmn\/bin:$PATH<\/p>\n

    export PATH<\/p>\n

     <\/p>\n

    opmnctl stopall<\/p>\n

    opmnctl startall<\/p><\/blockquote>\n

     <\/p>\n

    Now we need to Register HTTP server with Weblogic Server so that Enterprise Manager can monitor the instance.
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion ~]$ opmnctl registerinstance -adminHost fusion -adminport 7001 -adminUsername weblogic<\/strong><\/span><\/p>\n

    Command requires login to weblogic admin server (fusion):<\/p>\n

    Username: weblogic<\/p>\n

    Password:<\/p>\n

    \u2026<\/p>\n

    Done<\/p>\n

    Registering instance<\/p>\n

    Command succeeded.<\/p><\/blockquote>\n

    Note: We will not enable load-balancer access since we have skipped load-balancing in this single node installation guide.<\/p>\n

     <\/p>\n

    Enable Weblogic Plugin
    \n<\/strong><\/span><\/p>\n

    Log in the Oracle Weblogic Server Administration and click on Lock and Edit. Click on IDMDomain and Click on Configuration tab and then select the Web Applications tab.<\/span><\/p>\n

    \"\"<\/p>\n

     <\/p>\n

    Scroll down and enable “Weblogic Plug-in Enabled”.
    \n<\/strong><\/span><\/p>\n


    \n<\/span><\/a>Click on Save and Activate the Changes.<\/p>\n

    \"\"<\/p>\n

    Restart the Weblogic Administration Server.
    \n<\/strong><\/p>\n

     <\/p>\n

    Extending the Domain with Oracle Internet Directory
    \n<\/span><\/h2>\n

    Start the configuration from\u00a0<IDM Oracle Home\/bin<\/strong><\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/Oracle_IDM1\/bin<\/p>\n

    [oracle@fusion bin]$ .\/config.sh &<\/p><\/blockquote>\n

    \"\"<\/p>\n

    \"\"<\/p>\n

    Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select “Configure Without A Domain<\/strong>” and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Make sure to select any directory inside MW_HOME\/instances. You can accept default for Instance Name. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Deselect email notification and click Next<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Select only “Oracle Internet Directory<\/strong>” and click Next<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Select “Specify Ports using Configuration File<\/strong>” and enter file name as \/home\/oracle\/staticports.ini
    \n<\/strong><\/p>\n

    In another terminal window copy the staticports.ini file to home directory.<\/p>\n

    [oracle@fusion bin]$ cp \/app\/fusion\/provisioning\/idm\/idm\/Disk1\/stage\/Response\/staticports.ini ~\/<\/p><\/blockquote>\n

    Click on View\/Edit file<\/p>\n

     <\/p>\n

    VERY IMPORTANT:
    \n<\/strong><\/span><\/p>\n

    As per Oracle Manual we should Change it to as follows.<\/p>\n

    #The Non-SSL port for OID
    \n<\/span><\/p>\n

    Oracle Internet Directory Port No = 389
    \n<\/span><\/p>\n

    #The SSL port for OID
    \n<\/span><\/p>\n

    Oracle Internet Directory (SSL) Port No = 636
    \n<\/span><\/p>\n

     <\/p>\n

    But OID fails to configure and start at the end of installation with these values so we will stick to the OID values for 11g in the staticports.ini and just remove the comments.<\/p>\n

     <\/p>\n

    #The Non-SSL port for OID
    \n<\/span><\/p>\n

    Oracle Internet Directory Port No = 3060
    \n<\/span><\/p>\n

    #The SSL port for OID
    \n<\/span><\/p>\n

    Oracle Internet Directory (SSL) Port No = 3061
    \n<\/span><\/p>\n<\/blockquote>\n

     <\/p>\n

    \"\"<\/p>\n

    Click Save<\/strong><\/p>\n

    \"\"<\/p>\n

    Once saved, click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Enter oracle123 or any suitable password. If you are using different passwords then please make a note of all of them. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Since we are not using any domains as such but as we have added an entry in our hosts file for fusion.localdomain, we will add “dc=localdomain<\/strong>” for Realm. Enter oracle123 or any suitable password. Click Next<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Save summary if needed and click Configure<\/strong> to start configuration.<\/p>\n

    \"\"<\/a><\/strong><\/p>\n

    Once installation finishes, click Next<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Save installation summary if needed and click Finish<\/strong> to complete the installation.<\/p>\n

     <\/p>\n

    Validate the OID installation
    \n<\/strong><\/p>\n

    [oracle@fusion ~]$ export ORACLE_HOME=\/app\/fusion\/bea_default\/Oracle_IDM1
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion ~]$ export ORACLE_INSTANCE=\/app\/fusion\/bea_default\/instances\/oid_inst1
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion ~]$ export PATH=$ORACLE_HOME\/opmn\/bin:$ORACLE_HOME\/bin:$ORACLE_HOME\/ldap\/bin:$ORACLE_HOME\/ldap\/admin:$PATH
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion ~]$ ldapbind -h fusion -p 3060 -D “cn=orcladmin” -q
    \n<\/strong><\/span><\/p>\n

    Please enter bind password:<\/p>\n

    bind successful<\/p>\n

    [oracle@fusion ~]$ ldapbind -h fusion -p 3061 -D “cn=orcladmin” -q -U 1<\/strong><\/span><\/p>\n

    Please enter bind password:<\/p>\n

    bind successful<\/p>\n

    [oracle@fusion ~]$ opmnctl status<\/strong><\/span><\/p>\n

    Processes in Instance: oid_inst1<\/p>\n

    ———————————+——————–+———+———<\/p>\n

    ias-component | process-type | pid | status<\/p>\n

    ———————————+——————–+———+———<\/p>\n

    oid1 | oidldapd | 19810 | Alive<\/p>\n

    oid1 | oidldapd | 19798 | Alive<\/p>\n

    oid1 | oidmon | 19785 | Alive<\/p>\n

    EMAGENT | EMAGENT | 19325 | Alive<\/p><\/blockquote>\n

     <\/p>\n

    Registering Oracle Internet Directory with the WebLogic Server Domain<\/span>
    \n<\/span><\/strong><\/span><\/p>\n

    [oracle@fusion ~]$ echo $ORACLE_HOME<\/strong><\/span><\/p>\n

    \/app\/fusion\/bea_default\/Oracle_IDM1<\/p>\n

    [oracle@fusion ~]$ echo $ORACLE_INSTANCE<\/strong><\/span><\/p>\n

    \/app\/fusion\/bea_default\/instances\/oid_inst1<\/p>\n

    [oracle@fusion ~]$ opmnctl registerinstance -adminHost fusion -adminPort 7001 -adminUsername weblogic
    \n<\/strong><\/span><\/p>\n

    Command requires login to weblogic admin server (fusion):<\/p>\n

    Username: weblogic<\/p>\n

    Password:<\/p>\n

    Registering instance<\/p>\n

    Command succeeded.<\/p><\/blockquote>\n

     <\/p>\n

    Note:<\/strong> We have skipped next steps related to SSL since we are setting up non-SSL connections here.<\/p>\n

     <\/p>\n

    Update the Enterprise Manager Repository URL<\/strong>
    \n<\/span><\/p>\n

    Next we will update the Enterprise Manager Repository URL using the emctl utility with the switchOMS<\/strong> flag. The emctl utility is located under the\u00a0ORACLE_INSTANCE<\/em>\/EMAGENT\/EMAGENT\/bin <\/span>directory.
    \n<\/span><\/p>\n

    [oracle@fusion ~]$ cd \/app\/fusion\/bea_default\/instances\/oid_inst1\/EMAGENT\/EMAGENT\/bin<\/strong><\/span><\/p>\n

    [oracle@fusion bin]$ .\/emctl switchOMS http:\/\/fusion:7001\/em\/upload
    \n<\/strong><\/span><\/p>\n

    Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.<\/p>\n

    Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.<\/p>\n

    SwitchOMS succeeded.<\/p><\/blockquote>\n

     <\/p>\n

    We can now verify whether this instance is registered for monitoring agent.<\/p>\n

    Login to http:\/\/fusion:7001\/em<\/strong><\/p>\n

    Click on Farm->Agent monitored targets.<\/strong><\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    You should be able to see the OID instance under this. Make sure that the Agent URL is showing up fine. If the status shows as “Need Configuration” then click on Configure and then in next screen enter weblogic user credentials. It should now show the correct Agent URL.<\/p>\n

     <\/p>\n

     <\/p>\n

    Extending the Domain with Oracle Directory Service Manager (ODSM)
    \n<\/strong><\/span><\/p>\n

    Start the configuration from <IDM Oracle Home>\/bin<\/strong><\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/Oracle_IDM1\/bin<\/p>\n

    [oracle@fusion bin]$ .\/config.sh &<\/strong><\/span><\/p><\/blockquote>\n

    \"\"
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Click Next
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Select “Extend Existing Domain<\/strong>” and enter details of existing weblogic Server and AdminServer port. Click Next<\/strong><\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    You can ignore this error since we created this domain using the Identity Management installer. Click Yes<\/strong> to ignore.<\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Verify that the weblogic server directory shown is correct as per previous steps. Specify name and path for Oracle Directory Service instance. Make sure to keep the instance in same parent directory as previous instances. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Deselect email notification and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select Oracle “Directory Service Manager<\/strong>” and click Next<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Select “Specify Ports using Configuration File<\/strong>” and enter file name as \/home\/oracle\/staticports.ini<\/strong><\/p>\n

    Meanwhile in another terminal window copy the staticports.ini<\/strong> to home directory.<\/p>\n

    [oracle@fusion bin]$ cp -p \/app\/fusion\/provisioning\/idm\/idm\/Disk1\/stage\/Response\/staticports.ini ~\/<\/p><\/blockquote>\n

     <\/p>\n

    \"\"<\/p>\n

    Uncomment the ODS Server Port and keep it default 7006. Click Save.<\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Once Saved click Next.<\/p>\n

    \"\"<\/p>\n

    Save summary if needed and click Configure<\/strong> to start configuration.<\/p>\n

    \"\"<\/p>\n

    Once installation finishes, click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Save installation summary if needed and click Finish<\/strong> to complete the installation.<\/p>\n

     <\/p>\n

    Password-less startup for ODS
    \n<\/strong><\/span><\/p>\n

    cd \/app\/fusion\/bea_default\/user_projects\/domains\/IDM_domain\/servers\/wls_ods1\/security<\/p>\n

    cp ..\/..\/AdminServer\/security\/boot.properties .<\/p>\n

    cd \/app\/fusion\/bea_default\/user_projects\/domains\/IDM_domain\/bin<\/p>\n

    nohup .\/startManagedWebLogic.sh wls_ods1
    \n<\/strong><\/p><\/blockquote>\n

     <\/p>\n

    Now you can access ODS homepage at http:\/\/fusion:7006\/odsm\/faces\/odsm.jspx<\/a> (as per the above post-installation summary screen)<\/p>\n

    \"\"<\/p>\n

     <\/p>\n

    Register ODS with OID
    \n<\/strong><\/span><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Click on Connect to a directory<\/strong> -> Create A New Connection<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Enter the details for OID.<\/p>\n

    Name: fusion-oid<\/strong><\/p>\n

    Server: fusion<\/strong><\/p>\n

    SSL Enabled: Unchecked<\/strong><\/p>\n

    User Name: cn=orcladmin<\/strong><\/p>\n

    Password: oracel123<\/strong><\/p>\n

    Start Page: Home<\/strong><\/p>\n

    Click Connect<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Once connection is successful, you should be able to see OID page.\"\"<\/p>\n

    You can randomly check whether you are able to see details of any user, for example cn=orcladmin<\/strong><\/p>\n

     <\/p>\n

    Configuring Oracle HTTP Servers to Access the ODSM Console
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion moduleconf]$ cd \/app\/fusion\/bea_default\/Oracle_WT1\/instances\/instance1\/config\/OHS\/ohs1\/moduleconf<\/p>\n

    [oracle@fusion moduleconf]$ vi admin.conf<\/p>\n

    # Append following lines in admin.conf<\/strong><\/p>\n

    <Location \/odsm><\/span>
    \n SetHandler weblogic-handler<\/span>
    \n# WebLogicCluster fusion:7006<\/span>
    \n WebLogicHost fusion<\/span>
    \n WeblogicPort 7006<\/span>
    \n <\/Location><\/span><\/p>\n


    \n<\/span><\/p><\/blockquote>\n

    Note:<\/strong> The reason we have kept commented cluster entries is that in case if you have setup cluster then you can use cluster entry instead of standalone entry.<\/p>\n

    Restart HTTP server.
    \n<\/strong><\/p>\n

    Now we can access ODSM through http:\/\/fusion:7777\/odsm\/faces\/odsm.jspx<\/a><\/p>\n

     <\/p>\n

    Extending the Domain with Oracle Virtual Directory<\/span><\/strong><\/span><\/p>\n

    Start the configuration from <IDM Oracle Home>\/bin<\/strong><\/p>\n

    [oracle@fusion ~]$ cd \/app\/fusion\/bea_default\/Oracle_IDM1\/bin\/<\/p>\n

    [oracle@fusion bin]$ .\/config.sh &<\/p><\/blockquote>\n

     <\/p>\n

    \"\"<\/p>\n

    Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select “Configure Without A Domain<\/strong>“. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Provide values for Oracle Virtual Directory (OVD) instance. You can accept default values. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Deselect email notification and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select “Oracle Virtual Directory<\/strong>” and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select “Specify Ports using Configuration File<\/strong>” and enter file name as \/home\/oracle\/staticports.ini<\/strong><\/p>\n

    Open a separate terminal\/putty window and copy staticports.ini<\/strong> file to home directory.<\/p>\n

    [oracle@fusion ~]$ cp \/app\/fusion\/provisioning\/idm\/idm\/Disk1\/stage\/Response\/staticports.ini ~\/<\/p><\/blockquote>\n

    Click on View\/Edit<\/strong>.<\/p>\n

    Edit the\u00a0staticports.ini\u00a0file to assign ports\u00a06501\u00a0and\u00a07501, as follows.
    \n<\/span><\/p>\n

    \n

    # The non-SSL port for Oracle Virtual Directory
    \n<\/span><\/p>\n

    Oracle Virtual Directory port = 6501
    \n<\/span><\/p>\n

    # The SSL port for Oracle Virtual Directory
    \n<\/span><\/p>\n

    Oracle Virtual Directory (SSL) port = 7501
    \n<\/span><\/p>\n<\/blockquote>\n

    Click Save<\/strong> and then Next
    \n<\/strong><\/span><\/p>\n

    \"\"
    \n<\/span><\/p>\n

    Provide OID login details.
    \n<\/span><\/p>\n

    Uncheck “Configure Administrative Server in secure mode” since we are not using SSL anywhere in this installation. Click Next<\/strong>
    \n<\/span><\/p>\n

    \"\"<\/p>\n

    Click Ok
    \n<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Save summary if needed and click Configure<\/strong> to start configuration.<\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Once installation finishes, click Next<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Save installation summary if needed and click Finish<\/strong> to complete the installation.<\/p>\n

     <\/p>\n

    Registering OVD with the Oracle WebLogic Server Domain
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/instances\/ovd_inst1\/bin<\/span><\/p>\n

    [oracle@fusion ~]$\u00a0export ORACLE_HOME=\/app\/fusion\/bea_default\/Oracle_IDM1<\/span><\/p>\n

    [oracle@fusion ~]$\u00a0export ORACLE_INSTANCE=\/app\/fusion\/bea_default\/instances\/ovd_inst1<\/span><\/p>\n

    [oracle@fusion bin]$ <\/strong>.\/opmnctl registerinstance -adminHost fusion -adminPort 7001 -adminUsername<\/span><\/strong><\/span> weblogic<\/strong><\/span><\/p>\n

    Command requires login to weblogic admin server (fusion):<\/p>\n

    Username: weblogic<\/p>\n

    Password:<\/p>\n

    Registering instance<\/p>\n

    Command succeeded.<\/p><\/blockquote>\n

     <\/p>\n

    Update the Enterprise Manager Repository URL using the emctl utility with the switchOMS flag.<\/strong>
    \n<\/span><\/p>\n

    The emctl utility is located under the\u00a0ORACLE_INSTANCE<\/em>\/EMAGENT\/EMAGENT\/bin <\/span>directory.
    \n<\/span><\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/instances\/ovd_inst1\/EMAGENT\/EMAGENT\/bin<\/span><\/p>\n

    [oracle@fusion bin]$ .\/emctl switchOMS http:\/\/fusion:7001\/em\/upload<\/strong><\/span><\/p>\n

    Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.<\/p>\n

    Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.<\/p>\n

    SwitchOMS succeeded.<\/p><\/blockquote>\n

     <\/p>\n

    We can now verify whether this instance is registered for monitoring agent.<\/p>\n

    Login to http:\/\/fusion:7001\/em<\/strong><\/p>\n

    Click on Farm->Agent monitored targets.<\/strong><\/p>\n

     <\/p>\n

    \"\"
    \n\"\"
    \n\"\"\"\"<\/p>\n

    You should be able to see the OID and OVD instances under this. Make sure that the Agent URL is showing up fine. If the status shows as “Need Configuration” then click on Configure and then in next screen enter weblogic user credentials. It should now show the correct Agent URL.<\/p>\n

     <\/p>\n

    Validate the Oracle Virtual Directory Instances
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion ~]$ export ORACLE_HOME=\/app\/fusion\/bea_default\/Oracle_IDM1
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion ~]$ export ORACLE_INSTANCE=\/app\/fusion\/bea_default\/instances\/ovd_inst1
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion ~]$ export PATH=$ORACLE_HOME\/opmn\/bin:$ORACLE_HOME\/bin:$ORACLE_HOME\/ldap\/bin:$ORACLE_HOME\/ldap\/admin:$PATH
    \n<\/strong><\/span><\/p>\n

    [oracle@fusion bin]$ ldapbind -h fusion -p 6501 -D “cn=orcladmin” \u2013q<\/strong><\/span><\/p>\n

    Please enter bind password:<\/p>\n

    bind successful<\/p>\n

    [oracle@fusion bin]$ ldapbind -h fusion -p 7501 -D “cn=orcladmin” -q -U 1
    \n<\/strong><\/span><\/p>\n

    Please enter bind password:<\/p>\n

    SSL handshake failed<\/p>\n

    This is fine since we did not configure SSL mode.<\/span><\/p><\/blockquote>\n

     <\/p>\n

    Creating ODSM connections to Oracle Virtual Directory
    \n<\/strong><\/span><\/p>\n

    Open http:\/\/fusion:7777\/odsm\/faces\/odsm.jspx<\/a><\/p>\n

    Click Connect to a directory<\/strong> -> Create a new connection<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    \"\"<\/p>\n

    Enter details of OVD here.<\/p>\n

    Name: fusion-ovd<\/strong><\/p>\n

    Host: fusion<\/strong><\/p>\n

    Port: 8899<\/strong><\/p>\n

    SSL Enabled: Unchecked<\/strong><\/p>\n

    User Name: cn=orcladmin<\/strong><\/p>\n

    Password: oracle123<\/strong><\/p>\n

    Start Page: Home<\/strong><\/p>\n

    Click Connect<\/strong><\/p>\n

    \"\"<\/p>\n

    It will display OVD home page.<\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Note: We are skipping the adapter creation for now. We will create them later once needed.<\/p>\n

     <\/p>\n

    Extending the Domain with Oracle Access Manager
    \n<\/strong><\/span><\/p>\n

     <\/p>\n

    Start the configuration from <Middleware Home\/oracle_common\/commin\/bin<\/strong><\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/oracle_common\/common\/bin<\/p>\n

    [oracle@fusion bin]$ .\/config.sh<\/strong><\/span><\/p><\/blockquote>\n

    \"\"<\/p>\n

    \"\"<\/p>\n

    Click “Extend an existing WebLogic domain” and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Scroll down and select user_projects->domains->IDM_domain<\/strong>. Click Next
    \n<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Select only “Oracle Access Manager with Database Policy Store”<\/strong> and click on Next.<\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Here you need to provide the database connection details and choose schema owner username. You can keep the name default but make sure to keep a note of it since you will need this later. Choose a password for example oracle123. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Now it will test the database connectivity through JDBC.<\/p>\n

    \"\"<\/p>\n

    Once successful, click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select “Managed Servers, Clusters and Machines” only and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    The first row was from previous configuration of ODS and now there will be another row for OAM. Keep the default port and make a note of it. Enter wls_oam1 for the instance name (or whichever you chose while creating instance) and click Next<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Just click Next<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    On the “Machines<\/strong>” tab make sure that correct hostname is entered. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select wls_oam1<\/strong> and click the right arrow.<\/p>\n

    \"\"<\/p>\n

    Now it should look as above. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    On the summary page Click Extend<\/strong>.<\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Click OK<\/strong> Since we are aware that these are correct ports being used by AdminServer and wls_ods1 instance.<\/p>\n

    \"\"<\/p>\n

    Once configuration finishes, click Done<\/strong>.<\/p>\n

    You can start the managed server by using following command.<\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/user_projects\/domains\/IDM_domain\/bin<\/strong><\/span><\/p>\n

    [oracle@fusion bin]$ .\/startManagedWebLogic.sh wls_oam1<\/strong><\/span><\/p><\/blockquote>\n

    This will create the directory \/app\/fusion\/bea_default\/user_projects\/domains\/IDM_domain\/servers\/wls_oam1<\/strong><\/p>\n

    Press CTRL+C to stop the process since we will need to configure startup without password prompt.<\/p>\n

    [oracle@fusion wls_oam1]$ cd \/app\/fusion\/bea_default\/user_projects\/domains\/IDM_domain\/servers\/wls_oam1<\/strong><\/span><\/p>\n

    [oracle@fusion wls_oam1]$ cp ..\/wls_ods1\/security\/ boot.properties .<\/strong><\/span><\/p><\/blockquote>\n

     <\/p>\n

    Now we can start the managed server without prompting for password.<\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/user_projects\/domains\/IDM_domain\/bin<\/strong><\/span><\/p>\n

    [oracle@fusion bin]$ nohup .\/startManagedWebLogic.sh wls_oam1 &<\/strong><\/span><\/p><\/blockquote>\n

     <\/p>\n

    Configuring Oracle HTTP Servers to Display Login Page and Oracle Access Manager Console<\/strong>
    \n<\/span><\/p>\n

    Append<\/strong> following entries in \/app\/fusion\/bea_default\/Oracle_WT1\/instances\/instance1\/config\/OHS\/ohs1\/moduleconf\/admin.conf<\/strong><\/p>\n

    \u00a0<Location \/oam><\/span><\/p>\n

    SetHandler weblogic-handler
    \n<\/span><\/p>\n

    #WebLogicCluster fusion:14100<\/span><\/p>\n

    WebLogicHost fusion<\/span><\/p>\n

    WeblogicPort\u00a014100
    \n<\/span><\/p>\n

    <\/Location>
    \n<\/span><\/p>\n

     <\/p>\n

    <Location \/oamconsole>
    \n<\/span><\/p>\n

    #SetHandler weblogic-handler
    \n<\/span><\/p>\n

    WebLogicHost fusion
    \n<\/span><\/p>\n

    WebLogicPort 7001
    \n<\/span><\/p>\n

    <\/Location>
    \n<\/span><\/p><\/blockquote>\n

    Note:<\/strong>\u00a0The reason we have kept commented cluster entries\u00a0is that in case if you have setup cluster then you can use cluster entry instead of standalone entry.<\/p>\n

    Restart HTTP Server<\/strong> to bring this to effect.<\/p>\n

    Note: <\/strong>There are few other steps as well as per Oracle documentation but we will skip them for now.<\/p>\n

     <\/p>\n

    Extending the Domain to Configure Oracle Identity Manager and Oracle SOA Suite
    \n<\/strong><\/span><\/p>\n

     <\/p>\n

    Start the configuration from <Middleware Home\/oracle_common\/common\/bin<\/strong><\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/oracle_common\/common\/bin<\/strong><\/span><\/p>\n

    [oracle@fusion bin]$ .\/config.sh &
    \n<\/strong><\/span><\/p><\/blockquote>\n

    \"\"<\/p>\n

    \"\"<\/p>\n

    Select “Extend an existing WebLogic domain<\/strong>” and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Scroll down and select user_projects->domains->IDM_domain<\/strong> and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select Oracle Identity Manager<\/strong>. It will automatically select Oracle SOA Suite<\/strong> and Oracle WSM<\/strong>. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Check all to modify all entries together. Provide database connect details and select a password for all. Accept default value for Schema owner names. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Now it will test the database connectivity through JDBC.<\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Once JDBC test is successful, click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select only “Managed Servers, Clusters and Machines<\/strong>” and click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Add entries for soa_server1<\/strong> and oim_server1<\/strong>. As per Oracle documentation you can change them to wls_soa1<\/strong> and wls_oim1<\/strong> as well. But here we have kept them as default.
    \n<\/strong><\/p>\n

    Note the ports and click Next. <\/strong><\/p>\n

    \"\"<\/p>\n

    Just click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Since we are using Linux\/Unix machine, delete<\/strong> entry from above screen. And proceed to Unix Machine<\/strong> tab.<\/p>\n

    \"\"<\/p>\n

    Make sure correct hostname is entered here. Click Next<\/strong><\/p>\n

    \"\"<\/a><\/p>\n

    Select oim_server1<\/strong> and soa_server1<\/strong> and click right arrow. (if you had renamed them to wls_oim1<\/strong> and wls_soa1<\/strong> then you will see those entries instead of this)<\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    The screen will now look like above. Click Next<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    On Summary screen click Next<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Click OK<\/strong><\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Once configuration finishes, click Done
    \n<\/strong><\/p>\n

     <\/p>\n

    Configuring Oracle Identity Manager
    \n<\/strong><\/span><\/p>\n

    Now we will configure the Identity Manager from <IAM Oracle Home>\/bin<\/strong><\/p>\n

    [oracle@fusion bin]$ cd \/app\/fusion\/bea_default\/Oracle_IAM\/bin<\/span>
    \n<\/strong><\/p>\n

    [oracle@fusion bin]$ .\/config.sh &<\/strong><\/span><\/p><\/blockquote>\n

    \"\"
    \n<\/strong><\/p>\n

    Click Next
    \n<\/strong><\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Select only OIM Server and click Next<\/strong><\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Enter database details in shown format “fusion:1521:fusiondb<\/strong>“. Select Schema names (keep default) and enter password (oracle123). Make sure to keep a note of these schema names DEV_OIM<\/strong> and DEV_MDS<\/strong>. We will need these later during provisioning plan. Click Next
    \n<\/strong><\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Enter AdminServer details in t3:\/\/<hostname>:<port> <\/strong>format. Here t3:\/\/fusion:7001
    \n<\/strong><\/p>\n

     <\/p>\n

    Important Note: <\/strong>Before clicking next make sure that AdminServer is running otherwise it may throw following error on next page. Start or restart AdminServer if you see this error.
    \n<\/strong><\/p>\n

    INST-6180: Error while retrieving OIM Managed Server URL from the domain.<\/span><\/p><\/blockquote>\n

     <\/p>\n

    Click Next<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Enter passwords as follows and keep a note of them since we will require them in provisioning wizard.<\/p>\n

    OIM Admin password: Oracle123<\/p>\n

    Keystore Password: oracle123<\/p>\n

    Enter OIM HTTP URL as http:\/\/fusion:14000<\/a> (based on port value in previous configuration step). Click Next<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Deselect both and click Next
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Save the summary if required and click Configure.
    \n<\/strong><\/p>\n

     <\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Once configuration finishes click Next
    \n<\/strong><\/p>\n

    \"\"
    \n<\/strong><\/p>\n

    Save the configuration summary if needed and click Finish<\/strong> to complete the configuration.<\/p>\n

     <\/p>\n

    Configuring Oracle HTTP Servers for Oracle Identity Manager and SOA<\/strong><\/p>\n

    Append<\/strong>\u00a0following entries in \/app\/fusion\/bea_default\/Oracle_WT1\/instances\/instance1\/config\/OHS\/ohs1\/moduleconf\/admin.conf<\/strong><\/p>\n

    # oim admin console(idmshell based)<\/span>
    \n <Location \/admin><\/span>
    \n SetHandler weblogic-handler<\/span>
    \n WLProxySSL OFF<\/span>
    \n WLProxySSLPassThrough OFF<\/span>
    \n WLCookieName oimjsessionid<\/span>
    \n #WebLogicCluster fusion:14000<\/span>
    \n WebLogicHost fusion<\/span>
    \n WebLogicPort 14000<\/span>
    \n WLLogFile “${ORACLE_INSTANCE}\/diagnostics\/logs\/mod_wl\/oim_component.log”<\/span>
    \n <\/Location><\/span>
    \n # oim self and advanced admin webapp consoles(canonic webapp)<\/span>
    \n <Location \/oim><\/span>
    \n SetHandler weblogic-handler<\/span>
    \n WLProxySSL OFF<\/span>
    \n WLProxySSLPassThrough OFF<\/span>
    \n WLCookieName oimjsessionid<\/span>
    \n #WebLogicCluster oimvhn1:14000,oimvhn2:14000<\/span>
    \n WebLogicHost fusion<\/span>
    \n WebLogicPort 14000<\/span>
    \n WLLogFile “${ORACLE_INSTANCE}\/diagnostics\/logs\/mod_wl\/oim_component.log”<\/span>
    \n <\/Location><\/span>
    \n # SOA Callback webservice for SOD – Provide the SOA Managed Server Ports<\/span>
    \n <Location \/sodcheck><\/span>
    \n SetHandler weblogic-handler<\/span>
    \n WLProxySSL OFF<\/span>
    \n WLProxySSLPassThrough OFF<\/span>
    \n WLCookieName oimjsessionid<\/span>
    \n #WebLogicCluster soavhn1:8001,soavhn2:8001<\/span>
    \n WebLogicHost fusion<\/span>
    \n WebLogicPort 8001<\/span>
    \n WLLogFile “${ORACLE_INSTANCE}\/diagnostics\/logs\/mod_wl\/oim_component.log”<\/span>
    \n <\/Location><\/span>
    \n # Callback webservice for SOA. SOA calls this when a request is approved\/rejected<\/span>
    \n # Provide the SOA Managed Server Port<\/span>
    \n <Location \/workflowservice><\/span>
    \n SetHandler weblogic-handler<\/span>
    \n WLProxySSL OFF<\/span>
    \n WLProxySSLPassThrough OFF<\/span>
    \n WLCookieName oimjsessionid<\/span>
    \n #WebLogicCluster oimvhn1:14000,oimvhn2:14000<\/span>
    \n WebLogicHost fusion<\/span>
    \n WebLogicPort 14000<\/span>
    \n WLLogFile “${ORACLE_INSTANCE}\/diagnostics\/logs\/mod_wl\/oim_component.log”<\/span>
    \n <\/Location><\/span>
    \n # xlWebApp – Legacy 9.x webapp (struts based)<\/span>
    \n <Location \/xlWebApp><\/span>
    \n SetHandler weblogic-handler<\/span>
    \n WLProxySSL OFF<\/span>
    \n WLProxySSLPassThrough OFF<\/span>
    \n WLCookieName oimjsessionid<\/span>
    \n #WebLogicCluster oimvhn1:14000,oimvhn2:14000<\/span>
    \n WebLogicHost fusion<\/span>
    \n WebLogicPort 14000<\/span>
    \n WLLogFile “${ORACLE_INSTANCE}\/diagnostics\/logs\/mod_wl\/oim_component.log”<\/span>
    \n <\/Location><\/span>
    \n # Nexaweb WebApp – used for workflow designer and DM<\/span>
    \n <Location \/Nexaweb><\/span>
    \n SetHandler weblogic-handler<\/span>
    \n WLProxySSL OFF<\/span>
    \n WLProxySSLPassThrough OFF<\/span>
    \n WLCookieName oimjsessionid<\/span>
    \n #WebLogicCluster oimvhn1:14000,oimvhn2:14000<\/span>
    \n WebLogicHost fusion<\/span>
    \n WebLogicPort 14000<\/span>
    \n WLLogFile “${ORACLE_INSTANCE}\/diagnostics\/logs\/mod_wl\/oim_component.log”<\/span>
    \n <\/Location><\/span>
    \n # used for FA Callback service.<\/span>
    \n <Location \/callbackResponseService><\/span>
    \n SetHandler weblogic-handler<\/span>
    \n WLProxySSL OFF<\/span>
    \n WLProxySSLPassThrough OFF<\/span>
    \n WLCookieName oimjsessionid<\/span>
    \n #WebLogicCluster oimvhn1:14000,oimvhn2:14000<\/span>
    \n WebLogicHost fusion<\/span>
    \n WebLogicPort 14000<\/span>
    \n WLLogFile “${ORACLE_INSTANCE}\/diagnostics\/logs\/mod_wl\/oim_component.log”<\/span>
    \n <\/Location><\/span>
    \n # spml xsd profile<\/span>
    \n <Location \/spml-xsd><\/span>
    \n SetHandler weblogic-handler<\/span>
    \n WLProxySSL OFF<\/span>
    \n WLProxySSLPassThrough OFF<\/span>
    \n WLCookieName oimjsessionid<\/span>
    \n #WebLogicCluster oimvhn1:14000,oimvhn2:14000<\/span>
    \n WebLogicHost fusion<\/span>
    \n WebLogicPort 14000<\/span>
    \n WLLogFile “${ORACLE_INSTANCE}\/diagnostics\/logs\/mod_wl\/oim_component.log”<\/span>
    \n <\/Location><\/span>
    \n <Location \/HTTPClnt><\/span>
    \n SetHandler weblogic-handler<\/span>
    \n WLProxySSL OFF<\/span>
    \n WLProxySSLPassThrough OFF<\/span>
    \n WLCookieName oimjsessionid<\/span>
    \n #WebLogicCluster oimvhn1:14000,oimvhn2:14000<\/span>
    \n WebLogicHost fusion<\/span>
    \n WebLogicPort 14000<\/span>
    \n WLLogFile “${ORACLE_INSTANCE}\/diagnostics\/logs\/mod_wl\/oim_component.log”<\/span>
    \n <\/Location><\/span><\/p><\/blockquote>\n

    Note:<\/strong>\u00a0The reason we have kept commented cluster entries\u00a0is that in case if you have setup cluster then you can use cluster entry instead of standalone entry.<\/p>\n

    Restart HTTP Server<\/strong>\u00a0to bring this to effect.<\/p>\n

     <\/p>\n

    Installing and Configuring WebGate
    \n<\/strong><\/span><\/p>\n

    Start Webgate 10g installation from <repository_location>\/installers\/webgate<\/strong><\/p>\n

    [oracle@fusion webgate]$ cd \/mnt\/fusion\/installers\/webgate<\/strong><\/span><\/p>\n

    [oracle@fusion webgate]$ .\/Oracle_Access_Manager10_1_4_3_0_linux64_OHS11g_WebGate \u2013gui
    \n<\/strong><\/span><\/p><\/blockquote>\n

     <\/p>\n

    \"\"<\/p>\n

    Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Enter the OS oracle user details. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Select a path where you want to install webgate. We have selected \/app\/fusion\/webgate<\/strong>. Click Next<\/strong><\/p>\n

    \"\"<\/p>\n

    Click Next<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Open a new terminal\/putty window and execute following commands. Once done enter the location \/app\/fusion\/oam_lib in this screen and click Next<\/strong> to start the installation.
    \n<\/strong><\/p>\n

     <\/p>\n

    [oracle@fusion oam_lib]$ mkdir \/app\/fusion\/oam_lib<\/strong><\/p>\n

    [oracle@fusion oam_lib]$ ln -s \/usr\/lib64\/libstdc++.so.5 \/app\/fusion\/oam_lib\/libstdc++.so.5
    \n<\/strong><\/p>\n

    [oracle@fusion oam_lib]$ ln -s \/lib64\/libgcc_s.so.1 \/app\/fusion\/oam_lib\/libgcc_s.so.1<\/strong><\/p><\/blockquote>\n

     <\/p>\n

    \"\"<\/p>\n

    \"\"<\/p>\n

    Now WebGate Configuration will start. Select “Open Mode<\/strong>” and click Next<\/strong><\/p>\n

     <\/p>\n

     <\/p>\n

    \"\"<\/p>\n

     <\/p>\n

    Since this screen requires WebGate ID from Access Manager. We need to first create a Webgate Agent in Access Manager. So keep this Java window open and open Oracle Access Manager Console in browser by entering http:\/\/fusion\/oamconsole<\/a> or http:\/\/fusion:7777\/oamconsole<\/a><\/p>\n

     <\/p>\n

    Note: We could have done this before starting Webgate installation as well but keeping it here in the guide gives you an idea where we are going to this configuration. Next time when you install, you can do this step before itself.<\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Login with weblogic admin user.<\/p>\n

    \"\"<\/p>\n

    Once logged under SSO Agents, click on New “OAM 10g Webgate<\/strong>” (since we are installing 10g webgate).<\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Enter name: Webgate_sso<\/strong> or any name<\/p>\n

    Base URL: http:\/\/fusion:7777
    \n<\/strong><\/p>\n

    Host Identifier: Webgate_sso<\/strong><\/p>\n

    Security: Open<\/strong><\/p>\n

    Uncheck all 3 options on right.<\/p>\n

    Click Apply<\/strong><\/p>\n

     <\/p>\n

    Now Edit<\/strong> the same Webgate Agent again. It will show following screen.<\/p>\n

    \"\"<\/p>\n

     <\/p>\n

    We did not put domain<\/span> since we are using only http:\/\/fusion<\/a><\/p>\n

    Change Max Connections<\/span> to 4<\/strong><\/p>\n

    Logout URL:<\/span> Enter following values.<\/p>\n

    \/oamconsole\/logout.html
    \n<\/strong><\/p>\n

    \/console\/jsp\/common\/logout.jsp
    \n<\/strong><\/p>\n

    \/em\/targetauth\/eamlogout.jsp
    \n<\/strong><\/p>\n

     <\/p>\n

    Click Apply
    \n<\/strong><\/p>\n

     <\/p>\n

    \"\"<\/p>\n

    Once webgate Agent is created in OAM, go back to the already open configuration window and enter following details and click Next to finish the configuration. In case if the configuration window was closed, you can also launch the configuration from command prompt.<\/p>\n

    [oracle@fusion webgate]$ \/app\/fusion\/webgate\/access\/oblix\/tools\/configureWebGate\/start_configureWebGate -i \/app\/fusion\/webgate\/access -t WebGate<\/strong><\/span><\/p>\n

    Please enter the Mode in which you want the Web Gate to run : 1(Open) 2(Simple) 3(Cert) : 1<\/strong><\/p>\n

    Please enter the Web Gate ID : Webgate_sso<\/strong><\/p>\n

    Please enter the Password for this Web Gate : <enter oracle123 or any password here. Make note of it><\/p>\n

    Please enter the Access Server ID : wls_oam1<\/strong><\/p>\n

    Please enter the Access Server Host Machine Name : fusion<\/strong><\/p>\n

    Please enter the Access Server Port : 5575<\/strong><\/p>\n

    Preparing to connect to Access Server. Please wait.<\/p>\n

    Web Gate installed Successfully.<\/p>\n

    Press enter key to continue …<\/p><\/blockquote>\n

     <\/p>\n

    As per Oracle documentation there are a few steps to use the Webgate and validate but we will skip them for now.<\/p>\n

    Next step is to prepare Identity and Policy Stores by creating necessary users and groups for provisioning Fusion Applications.<\/p>\n

    Next:\u00a0Integrate Oracle Identity Manager (OIM) and Oracle Access Manager (OAM)<\/a><\/strong><\/p>\n

    Installing Oracle Fusion Applications \u2013 steps<\/a><\/strong><\/p>\n

      \n
    1. Installing Fusion Applications Provisioning Framework<\/a>
      \n<\/strong><\/li>\n
    2. Installing Oracle 11g Database (Applications Transactional Database)<\/a>
      \n<\/strong><\/li>\n
    3. Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)
      \n<\/a><\/strong><\/li>\n
    4. Creating another database for Oracle \u00a0Identity Management Infrastructure\u00a0<\/strong>(optional)
      \n<\/strong><\/li>\n
    5. Running Repository Creation Utility (RCU) for Oracle Identity Management components<\/a><\/strong><\/li>\n
    6. Installing Oracle Identity and Access Management Components<\/a>
      \n<\/strong><\/li>\n
    7. Configuring Oracle Identity and Access Management components<\/a>
      \n<\/strong><\/li>\n
    8. Integrate Oracle Identity Manager (OIM) and Oracle Access Manager (OAM)<\/a><\/strong>
      \n<\/strong><\/li>\n
    9. Creating a New Provisioning Plan<\/a>
      \n<\/strong><\/li>\n
    10. Provisioning an Applications Environment<\/a><\/strong><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

      Important Note: This is OLD guide for old version 11.1.1.5. Please follow instructions at\u00a0http:\/\/www.oratraining.com\/blog\/2012\/12\/oracle-fusion-applications-installation-step-by-step-guide-11-1-5\/ for latest guide for current version i.e. 11.1.5 \u00a0 Oracle Fusion Applications Installation: Configuring Oracle Identity and Access Management components Previous:\u00a0Installing Oracle Identity and Access Management Components Configuring Oracle Identity Management components” can be divided into following tasks. Configuring the Web […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[32,33,34,35,36,3,4,5,6,10,12,37,39],"tags":[46,47,66,70,72,73,74,80,81,87,98,198,99,101,103,104,146,149],"class_list":["post-878","post","type-post","status-publish","format-standard","hentry","category-fusion-applications-provisioning","category-fusion-middleware-oracle","category-http-server","category-identity-management","category-installing-oracle-applications","category-linuxunixsolaris","category-oracle","category-applications","category-oracle-applications-dba","category-oracle-dba","category-oracle-fusion-applications","category-oracle-internet-directory","category-webgate","tag-access-manager","tag-administration","tag-fusion-11g","tag-fusion-applications-installation","tag-guide","tag-http-server-2","tag-identity-management-2","tag-installation","tag-installing","tag-installing-oracle-fusion-applications","tag-oracle-applications","tag-oracle-applications-dba","tag-oracle-apps","tag-oracle-directory-service","tag-oracle-fusion-applications-2","tag-oracle-internet-directory-2","tag-virtual-directory","tag-webgate-2"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/posts\/878","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/comments?post=878"}],"version-history":[{"count":0,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/posts\/878\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/media?parent=878"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/categories?post=878"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/tags?post=878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}