ORATraining Blog

Configuring Oracle Identity and Access Management components

Oracle Fusion Applications Installation: Configuring Oracle Identity and Access Management components

Previous: Installing Oracle Identity and Access Management Components

Configuring Oracle Identity Management components” can be divided into following tasks.

Configuring the Web Tier
Create Weblogic Domain for Identity Management
Extending the Domain with Oracle Internet Directory
Extending the Domain with Oracle Directory Service Manager (ODSM)
Extending the Domain with Oracle Virtual Directory
Extending the Domain with Oracle Access Manager
Extending the Domain to Configure Oracle Identity Manager and Oracle SOA Suite
Installing and Configuring WebGate

Please note that this post is going to be long so allow time to load all images.

Configuring the Web Tier

Start the configuration from <Web_Home>/bin

[oracle@fusion bin]$ cd /app/fusion/bea_default/Oracle_WT1/bin

[oracle@fusion bin]$ ./config.sh

Click Next

Select “Oracle HTTP Server” and click Next

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

Select “Specify Ports using Configuration File” and enter file name as /home/oracle/staticports.ini

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

cp /mnt/fusion/installers/webtier/Disk1/stage/Response/staticports.ini ~/staticports.ini

Now click on “View/Edit File” to edit this file.

Uncomment and set the following values. Click Save

OPMN Local Port = 6700

OHS Port = 7777

Click Next

Deselect email notification and click Next

Save summary if needed and click Configure to start configuration.

Important Note: 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.

Once installation finishes, click Next

Save installation summary if needed and click Finish to complete the installation.

It would have already started HTTP server now. We can verify the same.

[oracle@fusion instances]$ ps -ef | grep http

oracle 3521 3491 0 10:06 ? 00:00:00 /app/fusion/bea_default/Oracle_WT1/ohs/bin/httpd.worker -DSSL

oracle 3547 3521 0 10:06 ? 00:00:00 /app/fusion/bea_default/Oracle_WT1/ohs/bin/httpd.worker -DSSL

oracle 3548 3521 0 10:06 ? 00:00:00 /app/fusion/bea_default/Oracle_WT1/ohs/bin/httpd.worker -DSSL

oracle 3549 3521 0 10:06 ? 00:00:00 /app/fusion/bea_default/Oracle_WT1/ohs/bin/httpd.worker -DSSL

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

User oracle

Group oinstall

We can launch http://fusion:7777 (Homepage of Oracle HTTP server) now. It will look as follows.

Create Weblogic Domain for Identity Management

Start the configuration from <Middleware Home>/oracle_common/commin/bin

[oracle@fusion bin]$ /app/fusion/bea_default/oracle_common/common/bin/config.sh

Select “Create a new Weblogic domain” and click Next

Select “Oracle Enterprise Manager – 11.1.1.0 [oracle_common]” and “Oracle JRF – 11.1.1.0 [oracle_common]” and click Next

Enter details as above or accept default values and click Next.

Since it accepts minimum 8 characters set password again to
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

You would see option of Oracle JRockit here. So select that JDK in this list.

Select “Administration Server” and “Managed Servers, Clusters and Machines”. Click Next

Keep defaults but make a note of the port since this will be widely used during next part of installation. Click Next

Just click Next

Click Next again

Select Second Tab “Unix Machine” and enter the hostname as above. Click Next

Click on AdminServer and Click right arrow. Click Next

It will now look as above. Click Next

On Summary page click Create

Once installation finishes, click Done

Make sure that the encrypted username and password values are already in boot.properties

[oracle@fusion security]$ more /app/fusion/bea_default/user_projects/domains/IDM_domain/servers/AdminServer/security/boot.properties

# Generated by Configuration Wizard on Mon Jan 23 10:59:07 GST 2012

username={AES}zaXc3+4y2KGuxnK6WkI7ehKcliQDeandkjdTdu0vpuY=

password={AES}WZ6Zo+j6aGoCyE2nQmCCdboEkA8TDGRlagdSqFGRedo=

Set StartScriptEnabled=true in nodemanager.properties by running following script

[oracle@fusion bin]$ cd /app/fusion/bea_default/oracle_common/common/bin

[oracle@fusion bin]$ ./setNMProps.sh

Appending required nodemanager.properties

Verify the change.

[oracle@fusion bin]$ tail -f /app/fusion/bea_default/wlserver_10.3/common/nodemanager/nodemanager.properties

#Required NM Property overrides (append to existing nodemanager.properties)

StartScriptEnabled=true

Start Node manager

[oracle@fusion bin]$ cd /app/fusion/bea_default/wlserver_10.3/server/bin

[oracle@fusion bin]$ nohup ./startNodeManager.sh &

…

IDM_domain -> /app/fusion/bea_default/user_projects/domains/IDM_domain

…

INFO: Secure socket listener started on port 5556

Start Weblogic AdminServer

[oracle@fusion bin]$ nohup
/app/fusion/bea_default/user_projects/domains/IDM_domain/bin/startWebLogic.sh &

tail nohup.out file until it shows following message.

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

Open Weblogic Admin Console

Launch Weblogic Admin console through
http://fusion:7001/console

Note: Go to preferences and change “automatic acquire lock” settings to avoid accidental changes since we are in development mode.

Configuring HTTP server for the Administration Server

Create a new file admin.conf as follows.

[oracle@fusion moduleconf]$ more /app/fusion/bea_default/Oracle_WT1/instances/instance1/config/OHS/ohs1/moduleconf/admin.conf

<VirtualHost *:7777>

ServerName fusion:80

ServerAdmin you@your.address

RewriteEngine On

RewriteOptions inherit

RewriteRule ^/console/jsp/common/logout.jsp /oamsso/logout.html [PT]

RewriteRule ^/em/targetauth/emaslogout.jsp /oamsso/logout.html [PT]

# Admin Server and EM

<Location /console>

SetHandler weblogic-handler

WebLogicHost fusion

WeblogicPort 7001

</Location>

<Location /consolehelp>

SetHandler weblogic-handler

WebLogicHost fusion

WeblogicPort 7001

</Location>

<Location /em>

SetHandler weblogic-handler

WebLogicHost fusion

WeblogicPort 7001

</Location>

</VirtualHost>

Restart http server.

ORACLE_HOME=/app/fusion/bea_default/Oracle_WT1

export ORACLE_HOME

ORACLE_INSTANCE=/app/fusion/bea_default/Oracle_WT1/instances/instance1

export ORACLE_INSTANCE

PATH=$ORACLE_HOME/opmn/bin:$PATH

export PATH

opmnctl stopall

opmnctl startall

Now we need to Register HTTP server with Weblogic Server so that Enterprise Manager can monitor the instance.

[oracle@fusion ~]$ opmnctl registerinstance -adminHost fusion -adminport 7001 -adminUsername weblogic

Command requires login to weblogic admin server (fusion):

Username: weblogic

Password:

…

Done

Registering instance

Command succeeded.

Note: We will not enable load-balancer access since we have skipped load-balancing in this single node installation guide.

Enable Weblogic Plugin

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.

Scroll down and enable “Weblogic Plug-in Enabled”.

Click on Save and Activate the Changes.

Restart the Weblogic Administration Server.

Extending the Domain with Oracle Internet Directory

Start the configuration from <IDM Oracle Home/bin

[oracle@fusion bin]$ cd /app/fusion/bea_default/Oracle_IDM1/bin

[oracle@fusion bin]$ ./config.sh &

Click Next

Select “Configure Without A Domain” and click Next

Make sure to select any directory inside MW_HOME/instances. You can accept default for Instance Name. Click Next

Deselect email notification and click Next

Select only “Oracle Internet Directory” and click Next

Select “Specify Ports using Configuration File” and enter file name as /home/oracle/staticports.ini

In another terminal window copy the staticports.ini file to home directory.

[oracle@fusion bin]$ cp /app/fusion/provisioning/idm/idm/Disk1/stage/Response/staticports.ini ~/

Click on View/Edit file

VERY IMPORTANT:

As per Oracle Manual we should Change it to as follows.

#The Non-SSL port for OID

Oracle Internet Directory Port No = 389

#The SSL port for OID

Oracle Internet Directory (SSL) Port No = 636

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.

#The Non-SSL port for OID

Oracle Internet Directory Port No = 3060

#The SSL port for OID

Oracle Internet Directory (SSL) Port No = 3061

Click Save

Once saved, click Next

Enter oracle123 or any suitable password. If you are using different passwords then please make a note of all of them. Click Next

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” for Realm. Enter oracle123 or any suitable password. Click Next

Save summary if needed and click Configure to start configuration.

Once installation finishes, click Next

Save installation summary if needed and click Finish to complete the installation.

Validate the OID installation

[oracle@fusion ~]$ export ORACLE_HOME=/app/fusion/bea_default/Oracle_IDM1

[oracle@fusion ~]$ export ORACLE_INSTANCE=/app/fusion/bea_default/instances/oid_inst1

[oracle@fusion ~]$ export PATH=$ORACLE_HOME/opmn/bin:$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_HOME/ldap/admin:$PATH

[oracle@fusion ~]$ ldapbind -h fusion -p 3060 -D “cn=orcladmin” -q

Please enter bind password:

bind successful

[oracle@fusion ~]$ ldapbind -h fusion -p 3061 -D “cn=orcladmin” -q -U 1

Please enter bind password:

bind successful

[oracle@fusion ~]$ opmnctl status

Processes in Instance: oid_inst1

———————————+——————–+———+———

ias-component | process-type | pid | status

———————————+——————–+———+———

oid1 | oidldapd | 19810 | Alive

oid1 | oidldapd | 19798 | Alive

oid1 | oidmon | 19785 | Alive

EMAGENT | EMAGENT | 19325 | Alive

Registering Oracle Internet Directory with the WebLogic Server Domain

[oracle@fusion ~]$ echo $ORACLE_HOME

/app/fusion/bea_default/Oracle_IDM1

[oracle@fusion ~]$ echo $ORACLE_INSTANCE

/app/fusion/bea_default/instances/oid_inst1

[oracle@fusion ~]$ opmnctl registerinstance -adminHost fusion -adminPort 7001 -adminUsername weblogic

Command requires login to weblogic admin server (fusion):

Username: weblogic

Password:

Registering instance

Command succeeded.

Note: We have skipped next steps related to SSL since we are setting up non-SSL connections here.

Update the Enterprise Manager Repository URL

Next we will update the Enterprise Manager Repository URL using the emctl utility with the switchOMS flag. The emctl utility is located under the ORACLE_INSTANCE/EMAGENT/EMAGENT/bin directory.

[oracle@fusion ~]$ cd /app/fusion/bea_default/instances/oid_inst1/EMAGENT/EMAGENT/bin

[oracle@fusion bin]$ ./emctl switchOMS http://fusion:7001/em/upload

Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.

Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.

SwitchOMS succeeded.

We can now verify whether this instance is registered for monitoring agent.

Click on Farm->Agent monitored targets.

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.

Extending the Domain with Oracle Directory Service Manager (ODSM)

Start the configuration from <IDM Oracle Home>/bin

[oracle@fusion bin]$ cd /app/fusion/bea_default/Oracle_IDM1/bin

[oracle@fusion bin]$ ./config.sh &

Click Next

Select “Extend Existing Domain” and enter details of existing weblogic Server and AdminServer port. Click Next

You can ignore this error since we created this domain using the Identity Management installer. Click Yes to ignore.

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

Deselect email notification and click Next

Select Oracle “Directory Service Manager” and click Next

Select “Specify Ports using Configuration File” and enter file name as /home/oracle/staticports.ini

Meanwhile in another terminal window copy the staticports.ini to home directory.

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

Uncomment the ODS Server Port and keep it default 7006. Click Save.

Once Saved click Next.

Save summary if needed and click Configure to start configuration.

Once installation finishes, click Next

Save installation summary if needed and click Finish to complete the installation.

Password-less startup for ODS

cd /app/fusion/bea_default/user_projects/domains/IDM_domain/servers/wls_ods1/security

cp ../../AdminServer/security/boot.properties .

cd /app/fusion/bea_default/user_projects/domains/IDM_domain/bin

nohup ./startManagedWebLogic.sh wls_ods1

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

Register ODS with OID

Click on Connect to a directory -> Create A New Connection

Enter the details for OID.

Name: fusion-oid

Server: fusion

SSL Enabled: Unchecked

User Name: cn=orcladmin

Password: oracel123

Start Page: Home

Click Connect

Once connection is successful, you should be able to see OID page.

You can randomly check whether you are able to see details of any user, for example cn=orcladmin

Configuring Oracle HTTP Servers to Access the ODSM Console

[oracle@fusion moduleconf]$ cd /app/fusion/bea_default/Oracle_WT1/instances/instance1/config/OHS/ohs1/moduleconf

[oracle@fusion moduleconf]$ vi admin.conf

# Append following lines in admin.conf

<Location /odsm>

SetHandler weblogic-handler

WebLogicCluster fusion:7006

</Location>

Restart HTTP server.

Now we can access ODSM through http://fusion:7777/odsm/faces/odsm.jspx

Extending the Domain with Oracle Virtual Directory

Start the configuration from <IDM Oracle Home>/bin

[oracle@fusion ~]$ cd /app/fusion/bea_default/Oracle_IDM1/bin/

[oracle@fusion bin]$ ./config.sh &

Click Next

Select “Configure Without A Domain“. Click Next

Provide values for Oracle Virtual Directory (OVD) instance. You can accept default values. Click Next

Deselect email notification and click Next

Select “Oracle Virtual Directory” and click Next

Select “Specify Ports using Configuration File” and enter file name as /home/oracle/staticports.ini

Open a separate terminal/putty window and copy staticports.ini file to home directory.

[oracle@fusion ~]$ cp /app/fusion/provisioning/idm/idm/Disk1/stage/Response/staticports.ini ~/

Click on View/Edit.

Edit the staticports.ini file to assign ports 6501 and 7501, as follows.

# The non-SSL port for Oracle Virtual Directory

Oracle Virtual Directory port = 6501

# The SSL port for Oracle Virtual Directory

Oracle Virtual Directory (SSL) port = 7501

Click Save and then Next

Provide OID login details.

Uncheck “Configure Administrative Server in secure mode” since we are not using SSL anywhere in this installation. Click Next

Click Ok

Save summary if needed and click Configure to start configuration.

Once installation finishes, click Next

Save installation summary if needed and click Finish to complete the installation.

Registering OVD with the Oracle WebLogic Server Domain

[oracle@fusion bin]$ cd /app/fusion/bea_default/instances/ovd_inst1/bin

[oracle@fusion bin]$ ./opmnctl registerinstance -adminHost fusion -adminPort 7001 -adminUsername weblogic

Command requires login to weblogic admin server (fusion):

Username: weblogic

Password:

Registering instance

Command succeeded.

Update the Enterprise Manager Repository URL using the emctl utility with the switchOMS flag.

The emctl utility is located under the ORACLE_INSTANCE/EMAGENT/EMAGENT/bin directory.

[oracle@fusion bin]$ cd /app/fusion/bea_default/instances/ovd_inst1/EMAGENT/EMAGENT/bin

[oracle@fusion bin]$ ./emctl switchOMS http://fusion:7001/em/upload

Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.

Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.

SwitchOMS succeeded.

We can now verify whether this instance is registered for monitoring agent.

Click on Farm->Agent monitored targets.

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.

Validate the Oracle Virtual Directory Instances

[oracle@fusion ~]$ export ORACLE_HOME=/app/fusion/bea_default/Oracle_IDM1

[oracle@fusion ~]$ export ORACLE_INSTANCE=/app/fusion/bea_default/instances/ovd_inst1

[oracle@fusion ~]$ export PATH=$ORACLE_HOME/opmn/bin:$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_HOME/ldap/admin:$PATH

[oracle@fusion bin]$ ldapbind -h fusion -p 6501 -D “cn=orcladmin” –q

Please enter bind password:

bind successful

[oracle@fusion bin]$ ldapbind -h fusion -p 7501 -D “cn=orcladmin” -q -U 1

Please enter bind password:

SSL handshake failed

This is fine since we did not configure SSL mode.

Creating ODSM connections to Oracle Virtual Directory

Open http://fusion:7777/odsm/faces/odsm.jspx

Click Connect to a directory -> Create a new connection

Enter details of OVD here.

Name: fusion-ovd

Host: fusion

Port: 8899

SSL Enabled: Unchecked

User Name: cn=orcladmin

Password: oracle123

Start Page: Home

Click Connect

It will display OVD home page.

Note: We are skipping the adapter creation for now. We will create them later once needed.

Extending the Domain with Oracle Access Manager

Start the configuration from <Middleware Home/oracle_common/commin/bin

[oracle@fusion bin]$ cd /app/fusion/bea_default/oracle_common/common/bin

[oracle@fusion bin]$ ./config.sh

Click “Extend an existing WebLogic domain” and click Next

Scroll down and select user_projects->domains->IDM_domain. Click Next

Select only “Oracle Access Manager with Database Policy Store” and click on Next.

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

Now it will test the database connectivity through JDBC.

Once successful, click Next

Select “Managed Servers, Clusters and Machines” only and click Next

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

Just click Next

On the “Machines” tab make sure that correct hostname is entered. Click Next

Select wls_oam1 and click the right arrow.

Now it should look as above. Click Next

On the summary page Click Extend.

Click OK Since we are aware that these are correct ports being used by AdminServer and wls_ods1 instance.

Once configuration finishes, click Done.

You can start the managed server by using following command.

[oracle@fusion bin]$ cd /app/fusion/bea_default/user_projects/domains/IDM_domain/bin

[oracle@fusion bin]$ ./startManagedWebLogic.sh wls_oam1

This will create the directory /app/fusion/bea_default/user_projects/domains/IDM_domain/servers/wls_oam1

Press CTRL+C to stop the process since we will need to configure startup without password prompt.

[oracle@fusion wls_oam1]$ cd /app/fusion/bea_default/user_projects/domains/IDM_domain/servers/wls_oam1

[oracle@fusion wls_oam1]$ cp ../wls_ods1/security/ boot.properties .

Now we can start the managed server without prompting for password.

[oracle@fusion bin]$ cd /app/fusion/bea_default/user_projects/domains/IDM_domain/bin

[oracle@fusion bin]$ nohup ./startManagedWebLogic.sh wls_oam1 &

Configuring Oracle HTTP Servers to Display Login Page and Oracle Access Manager Console

Append following entries in /app/fusion/bea_default/Oracle_WT1/instances/instance1/config/OHS/ohs1/moduleconf/admin.conf

<Location /oam>

SetHandler weblogic-handler

WebLogicCluster fusion:14100

</Location>

<Location /oamconsole>

SetHandler weblogic-handler

WebLogicHost fusion

WebLogicPort 7001

</Location>

Restart HTTP Server to bring this to effect.

Note: There are few other steps as well as per Oracle documentation but we will skip them for now.

Extending the Domain to Configure Oracle Identity Manager and Oracle SOA Suite

Start the configuration from <Middleware Home/oracle_common/common/bin

[oracle@fusion bin]$ cd /app/fusion/bea_default/oracle_common/common/bin

[oracle@fusion bin]$ ./config.sh &

Select “Extend an existing WebLogic domain” and click Next

Scroll down and select user_projects->domains->IDM_domain and click Next

Select Oracle Identity Manager. It will automatically select Oracle SOA Suite and Oracle WSM. Click Next

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

Now it will test the database connectivity through JDBC.

Once JDBC test is successful, click Next

Select only “Managed Servers, Clusters and Machines” and click Next

Add entries for soa_server1 and oim_server1. As per Oracle documentation you can change them to wls_soa1 and wls_oim1 as well. But here we have kept them as default.

Note the ports and click Next.

Just click Next

Since we are using Linux/Unix machine, delete entry from above screen. And proceed to Unix Machine tab.

Make sure correct hostname is entered here. Click Next

Select oim_server1 and soa_server1 and click right arrow. (if you had renamed them to wls_oim1 and wls_soa1 then you will see those entries instead of this)

The screen will now look like above. Click Next

On Summary screen click Next

Click OK

Once configuration finishes, click Done

Configuring Oracle Identity Manager

Now we will configure the Identity Manager from <IAM Oracle Home>/bin

[oracle@fusion bin]$ cd /app/fusion/bea_default/Oracle_IAM/bin

[oracle@fusion bin]$ ./config.sh &

Click Next

Select only OIM Server and click Next

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

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

Important Note: 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.

INST-6180: Error while retrieving OIM Managed Server URL from the domain.

Click Next

Enter passwords as follows and keep a note of them since we will require them in provisioning wizard.

OIM Admin password: Oracle123

Keystore Password: oracle123

Enter OIM HTTP URL as http://fusion:14000 (based on port value in previous configuration step). Click Next

Deselect both and click Next

Save the summary if required and click Configure.

Once configuration finishes click Next

Save the configuration summary if needed and click Finish to complete the configuration.

Installing and Configuring WebGate

Start Webgate 10g installation from <repository_location>/installers/webgate

[oracle@fusion webgate]$ cd /mnt/fusion/installers/webgate

[oracle@fusion webgate]$ ./Oracle_Access_Manager10_1_4_3_0_linux64_OHS11g_WebGate –gui

Click Next

Enter the OS oracle user details. Click Next

Select a path where you want to install webgate. We have selected /app/fusion/webgate. Click Next

Click Next

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 to start the installation.

[oracle@fusion oam_lib]$ mkdir /app/fusion/oam_lib

[oracle@fusion oam_lib]$ ln -s /usr/lib64/libstdc++.so.5 /app/fusion/oam_lib/libstdc++.so.5

[oracle@fusion oam_lib]$ ln -s /lib64/libgcc_s.so.1 /app/fusion/oam_lib/libgcc_s.so.1

Now WebGate Configuration will start. Select “Open Mode” and click Next

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 or http://fusion:7777/oamconsole

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.

Once logged under SSO Agents, click on New “OAM 10g Webgate” (since we are installing 10g webgate).

Enter name: Webgate_sso or any name

Base URL: http://fusion:7777

Host Identifier: Webgate_sso

Security: Open

Uncheck all 3 options on right.

Click Apply

Now Edit the same Webgate Agent again. It will show following screen.

We did not put domain since we are using only http://fusion

Change Max Connections to 4

Logout URL: Enter following values.

/oamconsole/logout.html

/console/jsp/common/logout.jsp

/em/targetauth/eamlogout.jsp

Click Apply

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.

[oracle@fusion webgate]$ /app/fusion/webgate/access/oblix/tools/configureWebGate/start_configureWebGate -i /app/fusion/webgate/access -t WebGate

Please enter the Mode in which you want the Web Gate to run : 1(Open) 2(Simple) 3(Cert) : 1

Please enter the Web Gate ID : Webgate_sso

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

Please enter the Access Server ID : wls_oam1

Please enter the Access Server Host Machine Name : fusion

Please enter the Access Server Port : 5575

Preparing to connect to Access Server. Please wait.

Web Gate installed Successfully.

Press enter key to continue …

As per Oracle documentation there are a few steps to use the Webgate and validate but we will skip them for now.

Next step is to prepare Identity and Policy Stores by creating necessary users and groups for provisioning Fusion Applications.

Next: Preparing Identity and Policy Stores

Installing Oracle Fusion Applications – steps

Installing Fusion Applications Provisioning Framework
Installing Oracle 11g Database (Applications Transactional Database)
Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)
Creating another database for Oracle Identity Management Infrastructure (optional)
Running Repository Creation Utility (RCU) for Oracle Identity Management components
Installing Oracle Identity and Access Management Components
Configuring Oracle Identity and Access Management components
Preparing Identity and Policy Stores
Creating a New Provisioning Plan
Provisioning an Applications Environment

No comments

Feb 6th, 2012 | Filed under Fusion Applications Provisioning, Fusion Middleware, HTTP Server, Identity Management, Installing Oracle Applications, Linux/Unix/Solaris, Oracle, Oracle Applications, Oracle Applications DBA, Oracle DBA, Oracle Fusion Applications, Oracle Internet Directory, Webgate

Installing Oracle Identity and Access Management components

Oracle Fusion Applications Installation: Installing Oracle Identity and Access Management components

Previous: Running Repository Creation Utility (RCU) for Oracle Identity Management components

Installing Orace JRockit JDK

Installation of JRockit is very simple. Just unzip the file located at <repository_location>/installers/jdk to any location where we want to extract the JDK files.

We will extract the files at /app/fusion and it will create /app/fusion/jdk6 directory. So we can set JAVA_HOME to /app/fusion/jdk6

cd /app/fusion

unzip /mnt/fusion/installers/jdk/jdk6.zip

Installing Oracle HTTP Server 11.1.1.2.0

We will install Oracle HTTP Server 11.1.1.2.0. Next we will patch it to 11.1.1.5.0 to bring it to the required level for Fusion Applications 11.1.1.5.0

Start the installation by executing runInstaller from <repository_location>/installers/webtier/Disk1

[oracle@fusion Disk1]$ /mnt/fusion/installers/webtier/Disk1/runInstaller &

Click Next

Select “Install Software – Do Not Configure“. This is because we will configure all components later in next section. Click Next

This screen will check for prerequisites. Click Next once completed.

Provide the path for Oracle Middleware Home. Please note that this will be the parent directory for all other Oracle Homes and instances. This is generally called MW_HOME.

Provide details as above and Click Next

Deselect Email Notifications and click Next

Save the Summary if required. Click Install to begin the installation.

Once installation is finished click Next

Save installation summary if required. Click Finish to complete the installation of Oracle HTTP Server.

Install HTTP Server Patch 11.1.1.5.0

Start the installation by executing runInstaller from <repository_location>/installers/webtier_patchset/Disk1

[oracle@fusion webtier_patchset]$ /mnt/fusion/installers/webtier_patchset/Disk1/runInstaller &

Click Next

Since we are installing the patch, the above details must be same as previous steps in order to apply patch on already installed Web Home. Click Next

Deselect email notification and click Next

Save the summary if required and click Install to begin the patch installation.

Click Next once installation is finished.

Save the installation summary if needed. Click Finish to complete the patch installation.

Install Weblogic Server 10.3.5

Start the installation by executing following java command
from <repository_location>/installers/weblogic

[oracle@fusion weblogic]$ cd /mnt/fusion/installers/weblogic

[oracle@fusion weblogic]$ java -d64 -jar wls_generic.jar

Click Next

Select “Create a new Middleware Home” and make sure that the correct MW_HOME directory (as selected in HTTP server installation) is selected. Click Next

Click Yes

Deselect email notifications and Click Next

Select Typical and click Next

It will display the list of local JDK already available. Since I had not yet unzipped Oracle JRockit yet, this screen does not show that. For you it will display the new JDK. Select it and click Next

It will suggest the default directories. Accept the values and click Next

Click Next on the summary page.

Deselect Quickstart and click Done once installation finishes.

Install Oracle Identity Management 11.1.1.2

We will first install Oracle Identity Management 11.1.1.2 and later patch it to required version 11.1.1.5

We need to first unzip the installation files from <repository_location>/installers/idm directory.

[oracle@fusion provisioning]$ mkdir /app/fusion/provisioning/idm

[oracle@fusion provisioning]$ cd /app/fusion/provisioning/idm

[oracle@fusion idm]$ unzip /mnt/fusion/installers/idm/idm.zip

Start the installation by executing runInstaller from <provisioning_repository>/idm/idm/Disk1

[oracle@fusion Disk1]$ cd /app/fusion/provisioning/idm/idm/Disk1

[oracle@fusion Disk1]$ ./runInstaller

Click Next

Select “Install Software – Do Not Configure” since we will be configuring all components later. Click Next

Click Next once prerequisite checks finish successfully.

Make sure to keep same Middleware Home as earlier installations. Select Appropriate name for IDM Home directory. You can keep it unchanged and click Next

Deselect email notifications and click Next

Save summary if needed. Click Install to begin installation.

Once installation is finished click Next

It will prompt us to run /app/fusion/bea_default/Oracle_IDM1/oracleRoot.sh script as root user. Login in another terminal window as root user and run the script. Press OK once script is exected.

[root@fusion ~]# /app/fusion/bea_default/Oracle_IDM1/oracleRoot.sh

Save Installation summary if needed. Click Finish to complete the installation.

Install Identity management 11.1.1.5 patchset

We need to first unzip the installation files from <repository_location>/installers/idm directory.

[oracle@fusion idmpatchset]$ cd /app/fusion/provisioning/idm/idmpatchset

[oracle@fusion idmpatchset]$ unzip /mnt/fusion/installers/idm/idm_patchset.zip

Start the installation by executing runInstaller from <provisioning_repository>/idm/idmpatchset/idm_patchset/Disk1 directory

[oracle@fusion Disk1]$ cd /app/fusion/provisioning/idm/idmpatchset/idm_patchset/Disk1

[oracle@fusion Disk1]$ ./runInstaller

Click Next

Since we are installing patchset on existing Home keep the values same as previous step. Click Next

Deselect Email Notifications and click Next

Save summary if needed. Click Install to begin installation.

Once installation is finished click Next

It will prompt us to run /app/fusion/bea_default/Oracle_IDM1/oracleRoot.sh script as root user. Login in another terminal window as root user and run the script. Press OK once script is exected.

[root@fusion ~]# /app/fusion/bea_default/Oracle_IDM1/oracleRoot.sh

Do you want to run oidRoot.sh to configure OID for privileged ports? (yes/no)

yes

User selected for running OIDRoot.sh

/app/fusion/bea_default/Oracle_IDM1

Finished root actions for OID

Save installation summary if required. Click Finish to complete the installation.

Installation of SOA suite 11.1.1.5

Start the installation by executing runInstaller from <repository_location>/installers/soa/Disk1

[oracle@fusion Disk1]$ cd /mnt/fusion/installers/soa/Disk1

[oracle@fusion Disk1]$ ./runInstaller

…

Please specify JRE/JDK location ( Ex. /home/jre ), <location>/bin/java should exist :/app/fusion/jdk6

Click Next

Select “Skip Software Updates” and click Next

This screen will check for prerequisites. Click Next once completed.

Keep same Middleware Home. Select appropriate name for SOA Home. You can keep default values and click Next

Select “Weblogic Server” and click Next

Save summary if needed. Click Install to begin installation.

Once installation is finished click Next

Save installation summary if required. Click Finish to complete the installation.

Install Oracle Identity and Access Management 11.1.1.5

We need to first unzip the installation files from <repository_location>/installers/oam directory.

[oracle@fusion oam]$ cd /app/fusion/provisioning/oam

[oracle@fusion oam]$ unzip /mnt/fusion/installers/oam/iamsuite1.zip

[oracle@fusion oam]$ unzip /mnt/fusion/installers/oam/iamsuite2.zip

[oracle@fusion oam]$ unzip /mnt/fusion/installers/oam/iamsuite3.zip

[oracle@fusion oam]$ unzip /mnt/fusion/installers/oam/iamsuite4.zip

Start the installation by executing runInstaller from <provisioning_repository>/oam/iamsuite/Disk1

[oracle@fusion Disk1]$ cd /app/fusion/provisioning/oam/iamsuite/Disk1

[oracle@fusion Disk1]$ ./runInstaller

Click Next

Select “Skip Software Updates” and click Next

This screen will check for prerequisites. Click Next once completed.

It will suggest the default directories. Accept the values and click Next

Save summary if needed. Click Install to begin installation.

Once installation is finished click Next

Save installation summary if required. Click Finish to complete the installation.

Creating the wlfullclient.jar File

Oracle Identity Manager uses the wlfullclient.jar library for certain operations. Oracle does not ship this library, so you must create this library manually. We will see mention of this during provisioning.

[oracle@fusion lib]$ cd /app/fusion/bea_default/wlserver_10.3/server/lib

[oracle@fusion lib]$ java -jar wljarbuilder.jar

..

[oracle@fusion lib]$ ls -l wlfullclient.jar

-rw-r–r– 1 oracle oinstall 59480532 Jan 23 09:21 wlfullclient.jar

This concludes Installation of Oracle Identity and Access Management components required for Fusion Applications. Next we will configure these components.

Next: Configuring Oracle Identity and Access Management components

Installing Oracle Fusion Applications – steps

Installing Fusion Applications Provisioning Framework
Installing Oracle 11g Database (Applications Transactional Database)
Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)
Creating another database for Oracle Identity Management Infrastructure (optional)
Running Repository Creation Utility (RCU) for Oracle Identity Management components
Installing Oracle Identity and Access Management Components
Configuring Oracle Identity and Access Management components
Preparing Identity and Policy Stores
Creating a New Provisioning Plan
Provisioning an Applications Environment

No comments

Feb 5th, 2012 | Filed under Oracle

Preparing Identity and Policy Stores

Oracle Fusion Applications Installation: Preparing Identity and Policy Stores

Previous: Configuring Oracle Identity and Access Management components

Now we will prepare the Identity and Policy stores which will create the necessary users, groups etc. This will also generate a file called idmDomainConfig.param which we need to specify while creating a provisioning plan. This will automatically populate some of the required fields during the provisioning plan creation.

Important Note: Please make sure to run all these commands from same location since these commands will create/append into a file named idmDomainConfig.param in same directory. Running these commands from same directory will ensure that all the contents is appended into single file.

Change the directory to <IAM_ORACLE_HOME>/idmtools/bin. And export the required environment variables.

[oracle@fusion bin]$ cd /app/fusion/bea_default/Oracle_IAM/idmtools/bin

[oracle@fusion bin]$ export IDM_HOME=/app/fusion/bea_default/Oracle_IDM1

[oracle@fusion bin]$ export ORACLE_HOME=/app/fusion/bea_default/Oracle_IAM

[oracle@fusion bin]$ export MW_HOME=/app/fusion/bea_default

[oracle@fusion bin]$ export JAVA_HOME=/app/fusion/jdk6

Now create a file named policystore.props with following contents.

[oracle@fusion bin]$ more policystore.props

POLICYSTORE_HOST : fusion

POLICYSTORE_PORT : 3060

POLICYSTORE_BINDDN: cn=orcladmin

POLICYSTORE_READONLYUSER: PolicyROUser

POLICYSTORE_READWRITEUSER: PolicyRWUser

POLICYSTORE_SEARCHBASE: dc=localdomain

POLICYSTORE_CONTAINER: cn=jpsroot

Now run idmConfigTool.sh to configure the Policy store based on the above input file. Enter a password of choice whenever prompted. We will stick to “oracle123″ for now.

[oracle@fusion bin]$ ./idmConfigTool.sh -configPolicyStore input_file=policystore.props

Enter Policy Store Bind DN password :

…

Enter User Password for PolicyROUser:

Confirm User Password for PolicyROUser:

…

Enter User Password for PolicyRWUser:

Confirm User Password for PolicyRWUser:

…

The tool has completed its operation. Details have been logged to automation.log

Whenever you run this tool, it will append log to automation.log in same directory. You can check the same as follows.

[oracle@fusion bin]$ ls -ltr

total 60

-rwxr-x— 1 oracle oinstall 1169 Dec 2 2010 appidtool.sh

-rwxr-x— 1 oracle oinstall 1139 Dec 2 2010 appidtool.bat

-rwxr-x— 1 oracle oinstall 1593 Mar 28 2011 orclTenantManager.sh

-rwxr-x— 1 oracle oinstall 2287 May 2 2011 orclTenantManager.bat

-rwxr-x— 1 oracle oinstall 3005 May 3 2011 idmConfigTool.sh

-rwxr-x— 1 oracle oinstall 3096 May 3 2011 idmConfigTool.bat

-rw-r–r– 1 oracle oinstall 235 Jan 25 21:21 policystore.props

-rw-r—– 1 oracle oinstall 154 Jan 25 21:23 idmDomainConfig.param

-rw-r–r– 1 oracle oinstall 1497 Jan 25 21:23 automation.log

As you can see it has created 2 files. idmDomainConfig.param and automation.log

Next we need to re-associate the policy store. Follow the steps below for the same.

[oracle@fusion bin]$ cd /app/fusion/bea_default/ocracle_common/common/bin/

[oracle@fusion bin]$ ./wlst.sh

…

Initializing WebLogic Scripting Tool (WLST) …

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

This will take you to a prompt which looks as follows. Enter following command to connect to the weblogic AdminServer.

wls:/offline>
connect(“weblogic”,’ “oracle123″,”t3://fusion:7001″)

Connecting to t3://fusion:7001 with userid weblogic …

Successfully connected to Admin Server ‘AdminServer’ that belongs to domain ‘IDM_domain’.

Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead.

Once connected run the following reassociateSecurityStore command.

wls:/IDM_domain/serverConfig> reassociateSecurityStore(domain=”IDMDomain”,admin=”cn=orcladmin”,password=”oracle123″,ldapurl=”ldap://fusion:3060″,servertype=”OID”,jpsroot=”cn=jpsroot”)

Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.

For more help, use help(domainRuntime)

Starting policy store reassociation.

…

Jps Configuration has been changed. Please restart the application server.

Enter the command “exit()” to quit the tool now.

wls:/IDM_domain/serverConfig> exit()

Exiting WebLogic Scripting Tool.

Now restart the Weblogic Server. We will use the shell scripts which we have created to start/stop weblogic. You can do this manually as well.

[oracle@fusion bin]$ ~/scripts/stopwls.sh

Stopping Weblogic Server

…

Shutting down the server AdminServer with force=false while connected to AdminServer …

..

Stopping Derby Server…

[oracle@fusion bin]$ ~/scripts/startwls.sh

Starting Weblogic Server

Again change the directory to <IAM_ORACLE_HOME>/idmtools/bin and create a file named extend.props with following contents.

[oracle@fusion bin]$ cd /app/fusion/bea_default/ocracle_common/common/bin/

[oracle@fusion bin]$ more extend.props

IDSTORE_HOST : fusion

IDSTORE_PORT : 3060

IDSTORE_BINDDN : cn=orcladmin

IDSTORE_USERNAMEATTRIBUTE: cn

IDSTORE_LOGINATTRIBUTE: uid

IDSTORE_USERSEARCHBASE: cn=Users,dc=localdomain

IDSTORE_GROUPSEARCHBASE: cn=Groups,dc=localdomain

IDSTORE_SEARCHBASE: dc=localdomain

IDSTORE_SYSTEMIDBASE: cn=systemids,dc=localdomain

Make sure that all required environment variables are already set. No need to set again if you are in the same terminal/putty window.

[oracle@fusion bin]$ echo $IDM_HOME

/app/fusion/bea_default/Oracle_IDM1

[oracle@fusion bin]$ echo $ORACLE_HOME

/app/fusion/bea_default/Oracle_IAM