Comparing Integrated, Standalone and Compact domain for BPM/SOA Suite 12c

Integrated WebLogic Server domain
This domain uses a JavaDB to support the SOA Infrastructure. You can create through JDeveloper by clicking the run application button when you have a SOA project active. In this case, it is tethered to your JDeveloper session and it is shuts down when you shut down JDeveloper. Its preferable use is to be created per developer on each own workstation for development and testing.

Pros:

• It is the most lightweight domain you can create.

Cons:

• On JDeveloper shut down, server shuts down.
• Healthcare, ESS, MFT , B2B, BAM components not supported.

Standalone domain
This domain uses a JavaDB to support the SOA Infrastructure. On this case, the domain does not shut down when JDeveloper shuts down. It will save startup time since it is not dependent on JDeveloper and can be used as a development environment. Moreover, if you plan to develop oracle service bus applications from the browser based console, without never having to launch JDeveloper, then this is definitely your choice.

Pros:

• Reduced startup time, since it's not dependent to JDeveloper
• Enables you to develop service bus services without having to launch JDeveloper.

Cons:

• Healthcare, ESS, MFT , B2B, BAM components not supported.

Compact domain
Finally, if you plan to use Managed File Transfer, Enterprise Scheduler Service, B2B, BAM or Healthecare then you should create a compact domain.