{"id":1510,"date":"2012-12-27T09:48:15","date_gmt":"2012-12-27T09:48:15","guid":{"rendered":"http:\/\/www.oratraining.com\/blog\/?p=1510"},"modified":"2013-04-07T20:58:21","modified_gmt":"2013-04-07T20:58:21","slug":"provision-an-applications-environment","status":"publish","type":"post","link":"https:\/\/www.oratraining.com\/blog\/2012\/12\/provision-an-applications-environment\/","title":{"rendered":"Oracle Fusion Applications Installation: Provision an Applications Environment"},"content":{"rendered":"

Previous: Create new Response File<\/a><\/p>\n

 <\/p>\n

Let us do a quick verification of everything before we start actual provisioning.<\/p>\n

 <\/p>\n

Copy the required libraries to webgate installer directory. This is required since the webgate creates soft links to this directory.<\/p>\n

-bash-3.2$ cp -pr \/app\/fusion\/oam_lib\/lib* \/u03\/stage\/installers\/webgate\/<\/p>\n

 <\/p>\n

Make sure that the project memory is set correctly.
\n<\/strong><\/p>\n

root@ad002aph01 # \/usr\/sbin\/ndd -get \/dev\/tcp tcp_smallest_anon_port<\/p>\n

32768<\/p>\n

root@ad002aph01 # \/usr\/sbin\/ndd -get \/dev\/tcp tcp_largest_anon_port<\/p>\n

65535<\/p>\n

root@ad002aph01 # \/usr\/sbin\/ndd -set \/dev\/tcp tcp_largest_anon_port 61000<\/p>\n

root@ad002aph01 # \/usr\/sbin\/ndd -get \/dev\/tcp tcp_largest_anon_port<\/p>\n

61000<\/p>\n

 <\/p>\n

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

root@ad002aph01 # more \/etc\/project<\/p>\n

\u2026<\/p>\n

user.fusion:100::fusion::project.max-shm-memory=(privileged,68719476736,deny)<\/p>\n

 <\/p>\n

Make sure that the IDM infrastructure is started. (only if not already started)
\n<\/strong><\/p>\n

 <\/p>\n

1. Source profile
\n<\/strong><\/p>\n

more ~\/.bash_profile<\/p>\n

ORACLE_HOME=\/app\/fusion\/database\/product\/11.2.0\/dbhome_1<\/p>\n

export ORACLE_HOME<\/p>\n

ORACLE_SID=fusiondb<\/p>\n

export ORACLE_SID<\/p>\n

JAVA_HOME=\/app\/fusion\/jdk6<\/p>\n

export JAVA_HOME<\/p>\n

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

export PATH<\/p>\n

 <\/p>\n

2. Start Listener
\n<\/strong><\/p>\n

lsnrctl start LISTENER_FUSIONDB<\/p>\n

 <\/p>\n

3. Start Database
\n<\/strong><\/p>\n

sqlplus \/ as sysdba<\/p>\n

SQL> startup<\/p>\n

 <\/p>\n

4. Start OID
\n<\/strong><\/p>\n

\/app\/fusion\/admin\/oid1\/bin\/opmnctl startall<\/p>\n

 <\/p>\n

5. Start Web
\n<\/strong><\/p>\n

\/app\/fusion\/admin\/web1\/bin\/opmnctl startall<\/p>\n

 <\/p>\n

6. Start Weblogic Admin Server for IDMDomain
\n<\/strong><\/p>\n

cd \/app\/fusion\/admin\/IDMDomain\/aserver\/IDMDomain\/bin\/<\/p>\n

nohup .\/startWebLogic.sh &<\/p>\n

(Wait till you see RUNNING in nohup.out log file)<\/p>\n

 <\/p>\n

7. Start Node Manager
\n<\/strong><\/p>\n

cd \/app\/fusion\/fmw\/wlserver_10.3\/server\/bin\/<\/p>\n

nohup .\/startNodeManager.sh &<\/p>\n

(Wait till you see “started on port 5556” in nohup.out log file)<\/p>\n

 <\/p>\n

8. Start OAM managed server for IDMDomain (since we cannot login to console without OAM)
\n<\/strong><\/p>\n

cd \/app\/fusion\/admin\/IDMDomain\/aserver\/IDMDomain\/bin\/<\/p>\n

nohup .\/startManagedWebLogic.sh wls_oam1 &<\/p>\n

(Wait till you see RUNNING in nohup.out log file)<\/p>\n

 <\/p>\n

9. Start remaining managed servers
\n<\/strong><\/p>\n

Either from command prompt<\/p>\n

cd \/app\/fusion\/admin\/IDMDomain\/aserver\/IDMDomain\/bin\/<\/p>\n

nohup .\/startManagedWebLogic.sh wls_ods1 &<\/p>\n

nohup .\/startManagedWebLogic.sh wls_oim1 &<\/p>\n

nohup .\/startManagedWebLogic.sh wls_soa1 &<\/p>\n

 <\/p>\n

(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)<\/p>\n

 <\/p>\n

Or by logging into Weblogic Console->Servers->Control screen.<\/p>\n

 <\/p>\n

10. ONLY In case if restarting from postconfigure phase
\n<\/strong><\/p>\n

 <\/p>\n

For 11.1.4 and earlier versions
\n<\/strong><\/p>\n

cd \/app\/fusion\/fusionapps\/wlserver_10.3\/common\/nodemanager\/ad002aph01<\/p>\n

nohup .\/startNodeManagerWrapper.sh &<\/p>\n

 <\/p>\n

For 11.1.5 onwards releases
\n<\/strong><\/p>\n

cd \/app\/fusion\/instance\/nodemanager\/ad002aph01<\/p>\n

nohup .\/startNodeManagerWrapper.sh &<\/p>\n

 <\/p>\n

-bash-3.2$ \/app\/fusion\/instance\/CommonDomain_webtier\/bin\/opmnctl startall<\/p>\n

 <\/p>\n

 <\/p>\n

Start Fusion Applications Provisioning
\n<\/strong><\/p>\n

 <\/p>\n

Launch the installer from <provisioning_repository>\/bin<\/p>\n

 <\/p>\n

-bash-3.2$ cd \/app\/fusion\/provisioning\/bin\/<\/p>\n

 <\/p>\n

It is important to start it with “-ignoreSysPrereqs true” switch as mentioned in the release notes.<\/p>\n

 <\/p>\n

-bash-3.2$ .\/provisioningWizard.sh -ignoreSysPrereqs true &<\/p>\n

\"\"<\/p>\n

 <\/p>\n

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

\"\"<\/p>\n

 <\/p>\n

Select “Provision an Applications Environment” and browse for the response file created in last step. Click Next<\/strong><\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Review and click Next<\/strong><\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Validate the information and click Next<\/strong><\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

In case if you want to revisit some of the section in the Response File then you can do so here. Click Next<\/strong><\/p>\n

\"\"<\/p>\n

 <\/p>\n

Review the summary and click Next<\/strong> to begin.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Expect 1 error here. The only error we have is as following. This can be skipped<\/strong> as mentioned on the release notes<\/strong>.<\/p>\n

 <\/p>\n

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!<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Please note that we will see the Next button activated here since we have specified “ignoreSysPrereqs true” switch to begin the provisioning. Click Next<\/strong><\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Once the Installation phase finishes, click Next<\/strong><\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Once Preconfigure phase completes, click Next<\/strong><\/p>\n

 <\/p>\n

Important Notes:<\/strong><\/p>\n

 <\/p>\n

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.<\/p>\n

 <\/p>\n

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

 <\/p>\n

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

 <\/p>\n

And for status of each domain within the particular phase, the flag files are written at \/app\/fusion\/provisioning\/phaseguards\/pf<\/strong> directory<\/p>\n

 <\/p>\n

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<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Click Next<\/strong> when Configure completes.<\/p>\n

 <\/p>\n

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.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Click Next<\/strong> once Configure Primary\/Secondary phase completes.
\n\"\"<\/p>\n

\"\"<\/p>\n

 <\/p>\n

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.<\/p>\n

 <\/p>\n

Check the logs in \/app\/fusion\/logs directory and fix the errors before proceeding.<\/p>\n

 <\/p>\n

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.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Once cleanup and restore completes, click OK to proceed with rerunning the same phase.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

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.<\/p>\n

 <\/p>\n

Despite these errors, the phase will be successful as you can see above. Click Next<\/strong><\/p>\n

 <\/p>\n

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.<\/p>\n

 <\/p>\n

<Domain>\/servers\/AdminServer\/data\/nodemanager\/AdminServer.state<\/p>\n

 <\/p>\n

Change FAILED_NOT_RESTARTABLE to SHUTDOWN and N to Y<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Once startup completes, click Next<\/strong>. (we skipped others since they were manually started)<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

After Validation completes, installation concludes.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Help Portal Home Page<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Fusion Applications “Getting started” guide in Help Portal. Must watch this.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Once you log in you will see this home page.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Couple of components are having some issue. Will fix this and update the post later.<\/p>\n

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.<\/p>\n

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.<\/p>\n

God bless you all.<\/p>\n

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

    \n
  1. \n
  2. \n
  3. \n
  4. \n
    Create another database for Oracle Identity Management Infrastructure (optional)<\/div>\n<\/li>\n
  5. \n
  6. \n
  7. \n
  8. \n
  9. \n
  10. \n
  11. \n
    Provision an Applications Environment<\/a><\/div>\n<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

    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. […]<\/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":[25,32,33,34,35,36,4,5,6,7,12,150,37,1,39],"tags":[40,42,66,70,72,74,87,198,108,109,163],"class_list":["post-1510","post","type-post","status-publish","format-standard","hentry","category-oracle-application-server","category-fusion-applications-provisioning","category-fusion-middleware-oracle","category-http-server","category-identity-management","category-installing-oracle-applications","category-oracle","category-applications","category-oracle-applications-dba","category-oracle-applications-issues","category-oracle-fusion-applications","category-oracle-fusion-applications-installation-fusion-applications-provisioning","category-oracle-internet-directory","category-uncategorized","category-webgate","tag-installing-fusion-applications","tag-oracle-fusion-applications-installation","tag-fusion-11g","tag-fusion-applications-installation","tag-guide","tag-identity-management-2","tag-installing-oracle-fusion-applications","tag-oracle-applications-dba","tag-provisioning","tag-provisioning-plan","tag-response-file"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/posts\/1510","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=1510"}],"version-history":[{"count":0,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/posts\/1510\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/media?parent=1510"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/categories?post=1510"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oratraining.com\/blog\/wp-json\/wp\/v2\/tags?post=1510"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}