From the first day the stack of Oracle SOA Suite 12c was released, I’ve been writing about how to install the different components.
I remember the first article I wrote during that fatidic day of June 29th, 2014 when Mexico was defeated by Netherlands in round of 16 of the Brazilian Soccer World Cup of 2014.
In the SOA Community an activity was coordinated to make the Quick start installation of SOA Suite 12c and from that moment I have been writing about such stack.
In this article, I simply consolidate the different guides I have generated. Please click in the link of your interest:
Oracle Stream Explorer 12c
Oracle API Manager 12c
Oracle MFT 12c
Oracle API Catalog 12c
Oracle SOA Suite 12c standalone installation
Oracle SOA Suite 12c quickstart installation
There are no excuses for you not to be testing and using the 12c components.
By default, when you install a Fusion Middleware domain, the Policy Store (part of the Java Platform Service) it is based on files. For sure you remember the system- jazn – data.xml, or the same jps -config.xml.
It is somewhat normal to leave the default settings until the need arises to generate users, connect to an LDAP, etc. Even in a productive environment, Oracle does not suggest (and do not support) this type of configuration.
Especially if you are in a cluster environment where you have a series of distributed machines, depending on the file-based Policy Store, can be risky because if these files are damaged, your WebLogic domain is on risk of being damaged.
There are three options for your Policy Store. This applies to an environment of 11g, and for sure 12c is equivalent, but everything in this article is discussed for 11g . We are also using the example of Oracle[...]