Ora Training Blog

While we are waiting for Oracle Support’s confirmation on a couple of queries related to bugs, let us see what are the differences you will notice while provisioning Fusion Apps 11.1.7 if you have done installation of 11.1.6 or earlier release in past.

Architecture

• Earlier we used to host both Identity Management and Fusion Apps schemas in single database. But seems Oracle now wants us to keep both of them on separate database. Though single database was working fine but it was always recommended to keep separate DBs even earlier. Now it is mandatory.

• Identity Management release is 11.1.1.7 instead of 11.1.1.6

• For HCM now a directory named /mnt/hwrrepo mandatory since it is required for Workforce Development/Deployment  later

• Disk space requirement has slightly increased

• XA views are mandatory to be created in IDM database. We will cover this in our installation steps.

• OAM security mode is now restricted to simple for non-AIX systems. I am checking with Oracle to see if there is a workaround or not.
• The default Application Super user is FAADMIN instead of Weblogic_fa and this is already created.
• The JPS Root Node in OPSS Policy Store is also already created so no need to create it during FA provisioning

Installation

• Now we no longer need to install, configure and integrate identity management separately. Oracle has provided Identity Management LCM (Lifecycle Management) or Identity Management provisioning framework. So we just need to create response file like we did for Fusion Apps and run through various phases of preverify, install, configure, configure-secondary, postconfigure, startup and validate.

• The provisioning framework for IDM eliminates errors while doing manual configuration and also keeps managed servers, names, locations, cluster names etc streamlined. This is indeed a good change.

• Most of the required patches are already installed as part of IDM provisioning so this is also a good news.

• There is a limitation though in Identity Management Provisioning framework yet. It does not allow you to cleanup-restore automatically like we can do in Fusion Applications provisioning. It is going to be enabled in next releases.

• Also there is a grayed out option of “Create Identity Management database” which suggests that in future we can create IDM database directly through this wizard. Though currently it is not available.

• SMTP host name is mandatory now so we cannot skip email server details. We can give local host name though if you have SMTP running.

• There is no option to specify OAM Security mode in Fusion Applications provisioning response file creation.

• There is a missing directory <repository_location>/provisioning/ant in the installer. We have a workaround for this for now and we have informed Oracle support to include this in next update.

I will keep updating this list this week. You also share your installation experience and here in comments section.

Happy learning !
Tushar