Ora Training Blog

Previous: Create new Response File

 

Let us do a quick verification of everything before we start actual provisioning.

 

Copy the required libraries to webgate installer directory. This is required since the webgate creates soft links to this directory.

-bash-3.2$ cp -pr /app/fusion/oam_lib/lib* /u03/stage/installers/webgate/

 

Make sure that the project memory is set correctly.

root@ad002aph01 # /usr/sbin/ndd -get /dev/tcp tcp_smallest_anon_port

32768

root@ad002aph01 # /usr/sbin/ndd -get /dev/tcp tcp_largest_anon_port

65535

root@ad002aph01 # /usr/sbin/ndd -set /dev/tcp tcp_largest_anon_port 61000

root@ad002aph01 # /usr/sbin/ndd -get /dev/tcp tcp_largest_anon_port

61000

 

root@ad002aph01 # projmod -U fusion -K “project.max-shm-memory=(privileged,68719476736,deny)” user.fusion

root@ad002aph01 # more /etc/project

…

user.fusion:100::fusion::project.max-shm-memory=(privileged,68719476736,deny)

 

Make sure that the IDM infrastructure is started. (only if not already started)

 

1. Source profile

more ~/.bash_profile

ORACLE_HOME=/app/fusion/database/product/11.2.0/dbhome_1

export ORACLE_HOME

ORACLE_SID=fusiondb

export ORACLE_SID

JAVA_HOME=/app/fusion/jdk6

export JAVA_HOME

PATH=$PATH:$ORACLE_HOME/bin

export PATH

 

2. Start Listener

lsnrctl start LISTENER_FUSIONDB

 

3. Start Database

sqlplus / as sysdba

SQL> startup

 

4. Start OID

/app/fusion/admin/oid1/bin/opmnctl startall

 

5. Start Web

/app/fusion/admin/web1/bin/opmnctl startall

 

6. Start Weblogic Admin Server for IDMDomain

cd /app/fusion/admin/IDMDomain/aserver/IDMDomain/bin/

nohup ./startWebLogic.sh &

(Wait till you see RUNNING in nohup.out log file)

 

7. Start Node Manager

cd /app/fusion/fmw/wlserver_10.3/server/bin/

nohup ./startNodeManager.sh &

(Wait till you see “started on port 5556” in nohup.out log file)

 

8. Start OAM managed server for IDMDomain (since we cannot login to console without OAM)

cd /app/fusion/admin/IDMDomain/aserver/IDMDomain/bin/

nohup ./startManagedWebLogic.sh wls_oam1 &

(Wait till you see RUNNING in nohup.out log file)

 

9. Start remaining managed servers

Either from command prompt

cd /app/fusion/admin/IDMDomain/aserver/IDMDomain/bin/

nohup ./startManagedWebLogic.sh wls_ods1 &

nohup ./startManagedWebLogic.sh wls_oim1 &

nohup ./startManagedWebLogic.sh wls_soa1 &

 

(Wait till you see RUNNING in nohup.out log file for each of them. You can start them in in parallel, just make sure all start fine)

 

Or by logging into Weblogic Console->Servers->Control screen.

 

10. ONLY In case if restarting from postconfigure phase

 

For 11.1.4 and earlier versions

cd /app/fusion/fusionapps/wlserver_10.3/common/nodemanager/ad002aph01

nohup ./startNodeManagerWrapper.sh &

 

For 11.1.5 onwards releases

cd /app/fusion/instance/nodemanager/ad002aph01

nohup ./startNodeManagerWrapper.sh &

 

-bash-3.2$ /app/fusion/instance/CommonDomain_webtier/bin/opmnctl startall

 

 

Start Fusion Applications Provisioning

 

Launch the installer from <provisioning_repository>/bin

 

-bash-3.2$ cd /app/fusion/provisioning/bin/

 

It is important to start it with “-ignoreSysPrereqs true” switch as mentioned in the release notes.

 

-bash-3.2$ ./provisioningWizard.sh -ignoreSysPrereqs true &

 

Click Next

 

Select “Provision an Applications Environment” and browse for the response file created in last step. Click Next

 

 

 

Review and click Next

 

 

Validate the information and click Next

 

 

In case if you want to revisit some of the section in the Response File then you can do so here. Click Next

 

Review the summary and click Next to begin.

 

Expect 1 error here. The only error we have is as following. This can be skipped as mentioned on the release notes.

 

2012-12-25 11:55:50.628 NOTIFICATION [logStatus] STATE=BUILD_ERROR!TIMESTAMP=2012-12-25 11:55:50 GST!TARGET=common-preverify-security!CATEGORY=BUILD_ERROR!DOMAIN=CommonDomain!HOSTNAME=ad002aph01!PRODUCTFAMILY=fs!PRODUCT=Functional-Setup!TASK=validateOim!TASKID=fs.Functional-Setup.BUILD_ERROR.common-preverify-security.validateOim!MESSAGE=List of failed Validation in OIM 1. OVD : Cannot perform OVD validations as Cannot bind to OVD with URL : 2. OAM_Validation : Cannot perform OAM Validation as null !DETAIL=List of failed Validation in OIM||1. OVD : Cannot perform OVD validations as Cannot bind to OVD with URL : ||2. OAM_Validation : Cannot perform OAM Validation as null||!BUILDFILE=/app/fusion/provisioning/provisioning-build/common-preverify-build.xml!LINENUMBER=345!

 

 

Please note that we will see the Next button activated here since we have specified “ignoreSysPrereqs true” switch to begin the provisioning. Click Next

 

 

Once the Installation phase finishes, click Next

 

 

Once Preconfigure phase completes, click Next

 

Important Notes:

 

You may see a lag between 100% completion of the phase and “Next” button being enabled. This is the time where the status changes from COMPLETED to ENDED. Here it takes backup of the instance directory at /app/fusion/provisioning/restart so that it can cleanup and restore from next step if it fails.

 

The installation logs are being created at /app/fusion/logs/provisioning/plan<timestamp>/<hostname> directory. This is the most useful place to troubleshoot.

 

The status flags like STARTED, COMPLETED, FAILED, ENDED are stored in /app/fusion/provisioning/phaseguards directory. Please be careful while removing, renaming or creating flag files here since it will change the current status of the provisioning.

 

And for status of each domain within the particular phase, the flag files are written at /app/fusion/provisioning/phaseguards/pf directory

 

Good thing in new Fusion applications setup is that when you retry it only performs the actions for failed products but those actions of completed products are not repeated. This saves a lot of time compared to our last installation of 11.1.1.5

 

 

Click Next when Configure completes.

 

Note: The name of next phase has changed to “Configure Primary/Secondary” instead of “Configure Secondary” as in 11.1.1.5 release since it was misleading.

 

 

Click Next once Configure Primary/Secondary phase completes.

 

If due to some issue a stage fails then you would see above screen. You need to click retry to cleanup and restore to previous state in order to start again.

 

Check the logs in /app/fusion/logs directory and fix the errors before proceeding.

 

Note: If OIM is not reachable then HCM postconfigure might fail after seeding the OID entries (at private-configure-oim-callback) so please make sure OID is running and port 14000 is reachable, or else restart OIM before you run postconfigure.

 

 

Once cleanup and restore completes, click OK to proceed with rerunning the same phase.

 

 

The above errors related to flexfield are actually warnings and even FA provisioning does not stop installation due to this since it is known bug as it does not have any data at the moment to seed. This is for future releases.

 

Despite these errors, the phase will be successful as you can see above. Click Next

 

Note: In case if To manually clear FAILED_NOT_RESTARTABLE status for any server, you can edit the following file ONLY AFTER YOU ARE SURE that this is cleanly shutdown.

 

<Domain>/servers/AdminServer/data/nodemanager/AdminServer.state

 

Change FAILED_NOT_RESTARTABLE to SHUTDOWN and N to Y

 

 

 

Once startup completes, click Next. (we skipped others since they were manually started)

 

 

After Validation completes, installation concludes.

 

 

Help Portal Home Page

 

Fusion Applications “Getting started” guide in Help Portal. Must watch this.

 

 

Once you log in you will see this home page.

 

 

Couple of components are having some issue. Will fix this and update the post later.

This concludes the basic installation of Fusion Applications. Next we need to configure and implement the selected product which includes Functional setup, scaling out etc. We will cover these in other posts.

Hope you liked our Fusion Applications installations guide. We would be really glad to see your suggestions and just to let you know; from 2013 onwards we will start Fusion Application Trainings in India and other countries on request.

God bless you all.

Installing Oracle Fusion Applications – steps

1. Install Fusion Applications Provisioning Framework
2. Install Oracle 11g Database (Applications Transactional Database)
3. Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)
4. Create another database for Oracle Identity Management Infrastructure (optional)
5. Run Repository Creation Utility (RCU) for Oracle Identity Management components
6. Install Oracle Identity and Access Management Components
7. Apply mandatory Patches
8. Configure Oracle Identity and Access Management components
9. Integrate Oracle Identity Manager (OIM) and Oracle Access Manager (OAM)
10. Create new Response File
11. Provision an Applications Environment

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

JDK installation

Installation of JDK is very simple. Just unzip the jdk6.zip 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

bash-3.2$ cd /app/fusion

bash-3.2$ unzip /u02/stage/installers/jdk/jdk6.zip

Install Web tier 11.1.1.6.0 (HTTP server 2.0)

Start runInstaller script from <REPOSITORY_LOCATION>/installers/Webiter/Disk1

(Please note that we do not need to upgrade it as we did in earlier installation since this is already at the required version level)

-bash-3.2$ cd /u02/stage/installers/webtier/Disk1/

-bash-3.2$ ./runInstaller

Click Next

“Skip Software Updates” and click Next

Select “Install Software – Do Not Configure” and click Next

Once Prerequisites check completes, click Next

Enter following values and click Next

Oracle Middleware Home: /app/fusion/fmw

Oracle Home Directory: web

Deselect the checkbox and click Next

Click Yes

Review Summary and click Install

Once installation completes, click Next

Review and click Finish

Install Weblogic Server

Start Weblogic Server installation from <REPOSITORY_LOCATION>/installers/weblogic direcotry

-bash-3.2$ cd /u02/stage/installers/weblogic

-bash-3.2$ java -d64 -jar wls_generic.jar

(Please note that we need to provide -d64 flag since we are installing on 64bit Solaris OS)

Click Next

Provide location of Middleware Home directory “/app/fusion/fmw” and click Next

Click Yes

Deselect the checkbox and click Next

Due to a bug in Solaris installation of Weblogic, following screen will keep on coming despite you click Yes. (only for Solaris installation)

If click Next and following will appear.

So click No now

Deselect the checkbox here and click continue J

Select Custom and click Next

Click Next

Browse for our SDK from /app/fusion/jdk6 and select that. Click Next

Make sure the values are as above and click Next

Review the summary and click Next

This starts the weblogic installation

Deselect Quickstart and click Done

Install Oracle Identity Management 11.1.1.6.0

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

-bash-3.2$ cd /app/fusion/provisioning

-bash-3.2$ unzip /app/stage/installers/idm/idm.zip

-bash-3.2$ cd /app/fusion/provisioning/idm/Disk1

-bash-3.2$ ./runInstaller

(Please note that we don’t need to upgrade this as well like last installation since it is already at the required version level.)

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

-bash-3.2$ cd /app/fusion/provisioning/idm/Disk1

-bash-3.2$ ./runInstaller

Click Next

Select “Skip software upgrade” and click Next

Select “Install Software – Do Not Configure” and click Next

Once prerequisites check completes, click Next

Select value “/app/fusion/fmw” as Middleware home and “idm” as Home directory. Click Next

Deselect the checkbox and click Next

Click Yes

Review the Summary and click Install

Once installation completes, click Next

The above dialog box will appear. Open another window and execute following as root.

root@ad002aph01 # /app/fusion/fmw/idm/oracleRoot.sh

Review the summary and click Finish

Install SOA suite 11.1.1.6.0

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

-bash-3.2$ cd /u02/stage/installers/soa/Disk1/

-bash-3.2$ ./runInstaller

…

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

Click Next

Select “Skip software update” and click Next

Once prerequisites check completes, click Next

Select “/app/fusion/fmw” as Middleware home and “soa” as Home Directory. Click Next

Weblogic Server will be detected. Click Next

Review the summary and click Install

Once completed, click Next

Review the summary and click Finish

Install Identity and Access Management

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

-bash-3.2$ mkdir /app/fusion/oam

-bash-3.2$ cd /app/fusion/oam/

-bash-3.2$ unzip ‘/u02/stage/installers/oam/iamsuite*.zip’

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

-bash-3.2$ cd /app/fusion/oam/iamsuite/Disk1/

-bash-3.2$ ./runInstaller

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

Click Next

Select “Skip software update” and click Next

Once prerequisites check finishes, click Next

Enter “/app/fusion/fmw” as Middleware home and “iam” as Home directory. Click Next

Review the summary and click Install

Once installation completes click Next

Review the summary and click Finish to complete the installation.

Provisioning the OIM Login Modules Under the WebLogic Server Library Directory

Due to issues with versions of the configuration wizard, some environmental variables are not added to the DOMAIN_HOME/bin/setDomainenv.sh script. This causes certain install sequences to fail. This is a temporary workaround for that problem.

1. Copy the files located under the IAM_ORACLE_HOME/server/loginmodule/wls directory to the MW_HOME/wlserver_10.3/server/lib/mbeantypes directory.

-bash-3.2$ cp -pr /app/fusion/fmw/iam/server/loginmodule/wls/*
/app/fusion/fmw/wlserver_10.3/server/lib/mbeantypes/

2. Change directory to MW_HOME/wlserver_10.3/server/lib/mbeantypes/

-bash-3.2$ cd /app/fusion/fmw/wlserver_10.3/server/lib/mbeantypes/

3. Change the permissions on these files to 750 by using the chmod command.

-bash-3.2$ chmod 750 *

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.

-bash-3.2$ cd /app/fusion/fmw/wlserver_10.3/server/lib

-bash-3.2$ ls -l wlfullclient.jar

wlfullclient.jar: No such file or directory

-bash-3.2$ java -jar wljarbuilder.jar

…

Created new jar file: /app/fusion/fmw/wlserver_10.3/server/lib/wlfullclient.jar

-bash-3.2$ ls -l wlfullclient.jar

-rw-r–r– 1 fusion dba 55004433 Dec 19 15:29 wlfullclient.jar

This concludes the installation of Oracle Identity Management components. Instead of directly configuring these components, we need to apply the mandatory patches first. These patches are listed in the latest release notes. Please refer to the latest release notes for the list of updated patches when you are installing.

Installing Oracle Fusion Applications – steps

1. Install Fusion Applications Provisioning Framework
2. Install Oracle 11g Database (Applications Transactional Database)
3. Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)
4. Create another database for Oracle Identity Management Infrastructure (optional)
5. Run Repository Creation Utility (RCU) for Oracle Identity Management components
6. Install Oracle Identity and Access Management Components
7. Apply mandatory Patches
8. Configure Oracle Identity and Access Management components
9. Integrate Oracle Identity Manager (OIM) and Oracle Access Manager (OAM)
10. Create new Response File
11. Provision an Applications Environment

Next: Apply mandatory Patches

Previous: Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)

 

Please note that we are not creating a separate database here for Oracle Identity Management components, though it is recommended but not mandatory to have a separate database for this. But since we are doing single node installation for Fusion Applications, we have to manage memory properly and hence we are not creating separate database instance.

 

Set following DB parameter before running the RCU in our existing database “fusiondb”.

 

SQL> alter system set open_cursors=800 scope=both sid=’*’;

System altered.

 

As we mentioned in the previous post, RCU for Oracle Identity Management components is only available for Linux and Windows platforms and the Fusion Application setup ships with Linux only RCU for Identity Management components.

 

Since we are using Windows RCU this time, we have downloaded the Fusion Middleware RCU from Oracle support website. You can either download ofm_rcu_win_11.1.1.6.0_disk1_1of1.zip or V29675-01.zip file which includes Repository Creation Utility for 11.1.1.6.0 Fusion Middleware Components.

 

Run rcu.bat from D:\fusion\fmw_rcu\rcuHome\BIN

 

 

Click Next

 

 

Select Create and click Next

 

 

Enter details of our existing database and click Next

 

 

Once prerequisites check completes, click OK

 

 

Mention any prefix for Identity Management related schemas. The default value is DEV while we have changed it to PROD. As per fusion applications documentations, they have given example as EDG or ISA. You can use whichever you want but please make a note of this since at many places you will need to mention the schema name.

Select all “Identity Management” components and click Next

 

 

Once prerequisites check is completed, click OK

 

We have specified single password for all users i.e. Oracle123. Click Next

 

 

Review the information and click Next

 

 

Click OK to create the tablespaces.

 

 

Once tablespaces creation is complete, click OK

 

 

Click Create to create users and start import.

 

 

Once import completes, above script appears. Click Close to finish RCU.

Installing Oracle Fusion Applications – steps

1. Install Fusion Applications Provisioning Framework
2. Install Oracle 11g Database (Applications Transactional Database)
3. Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)
4. Create another database for Oracle Identity Management Infrastructure (optional)
5. Run Repository Creation Utility (RCU) for Oracle Identity Management components
6. Install Oracle Identity and Access Management Components
7. Apply mandatory Patches
8. Configure Oracle Identity and Access Management components
9. Integrate Oracle Identity Manager (OIM) and Oracle Access Manager (OAM)
10. Create new Response File
11. Provision an Applications Environment

 

Next: Install Oracle Identity and Access Management Components