An Oracle Fusion Applications environment requires a transaction database. You can install a single-instance Oracle Database Enterprise Edition by using the Provisioning Wizard, or you can install Oracle Real Application Clusters (Oracle RAC) by using the standard installation instructions. The database templates shipped with Oracle Fusion Applications describe the structure and features of the database, but do not contain any data. You can place the Transaction database either on IdM database server host or Fusion Applications node, however, it is strongly recommended to separate it from other components. We will install the database using Provisioning Wizard since it also automatically applies all the required patches.
As it was mentioned in my previous post, Identity and Access Management is the main prerequisite of Fusion Applications provisioning – therefore it is the first thing to start with in overall process. Prepare at least two servers, one for Identity and Access Management and second for Fusion Applications as currently it is not supported to have both products sharing the same machine. However, my recommendation is to split components between four servers in order to gain more performance and manageability. The easiest way of course is to leverage virtualisation for that purpose, but please be ready for large amounts of RAM and disk space. Here is what official documentation states for typical HW requirements (or minimum, meant not for a production case):
I’ve decided to release a series of blog posts related to Fusion Applications bare metal provisioning. Get ready! The provisioning process (the replacement for “installation” term in Fusion Apps) is not so fast and straight forward as you would see it in Oracle Applications (e-Business Suite), for example. So expect to see a lot of blog posts broken in multiple parts with several sections. I will try to document the deployment as clear and detailed as I can to help others with the same.