Wednesday, September 17, 2014

Getting Started with Oracle BPM 12c: Installation and domain creation

Oracle SOA 12c has been released! And this version includes new features, changes, and concepts.

I will show what's new on development domain creation.

This new version includes an installer called QuickStart. This installer includes SOA, OSB, BPM and JDeveloper installers. The goal of this installer is simplify the installation and configuration steps: No more SOA/BPM plugins installation, no more database configuration with RCU (Repository Creation Utility) and installations to run composite applications, or OEPE to develop OSB projects. Now, one installation is enough :-)



We will review how:

  • Install Oracle BPM QuickStart
  • Create domains using the new approaches: Integrated, Standalone, Compact.
Requirements


This distribution includes:
  • Oracle SOA Suite (BPEL, Human Workflow, Business Rules, Mediator)
  • Oracle Service Bus
  • Oracle Enterprise Scheduler
  • Oracle Event Processing 
  • Oracle BPM Suite (Oracle BPMN Engine, BPM Applications: Business Process Composer, Business Process Workspace)
  • Oracle Case Management
  • Oracle JDeveloper pre-configurado con los plugins de SOA y BPM
  • WebLogic pre-configurado con una base de datos Java DB

Installing Oracle BPM QuickStart

To start the installer, JDK7 must be installed and the JAVA_HOME environmental variable must be defined. 

Run the following command:

java -jar [Installer JAR]




Once the installer is running, the only input required is the Middleware Home location (where all the FMW products are installed to work together):



Now we can start the JDeveloper 12.1.3 with the SOA and BPM features integrated:


Domain Configuration Modes

This new release has include 3 types of domains for development purposes:
  • Integrated: 
    • Created to work directly from JDeveloper. Pre-configured with SOA and BPM. Works with Java DB.
    • Is the best option to run a demo or evaluate the product. The server execution is related with the JDeveloper session, so if you close your JDeveloper, the server process will be killed.
  • Standalone:
    • Created from command-line. Pre-configured with SOA and BPM. Works with Java DB.
    • Is the best option for developers. The main difference from Integrated mode is that the server process is not related with your JDeveloper session, so you will be able to restart you JDeveloper without affect your server.
  • Compact:
    • Is similar to the "Development" templates on 11g version.
    • Configured by the user, Works with Oracle Database, configured with RCU.
    • This is the best option to work with components that don't support Java DB as BAM, Managed File Transfer, B2B, and so on.

Creating an Integrated Domain

This is the easiest option. To create the domain we should only start the Integrated Domain on JDeveloper:


Tips: register your IP and hostname on the hosts file (Windows: c:\Windows\system32\drivers\etc\hosts Linux: /etc/hosts). Run the installer and JDeveloper as Administrator on Windows.

Creating a Standalone Domain

The benefit here is that the server process is standalone and independent from the JDeveloper session. This option does not include BAM, Managed File Transfer or B2B because these components don't support Java DB as repository. If developing Composite Applications in your requirement, this is the right domain option: less resources consuming environment, quick start.

To start the installtion, run the following commands (MW_HOME is your Oracle Middleware Home. e.g.: C:\oracle\fmw\bpm\12.1.3 or /u01/oracle/fmw/12.1.3/bpm_qs):

cd $MW_HOME/soa/common/bin
set QS_TEMPLATES=$MW_HOME/soa/common/templates/wls/oracle.bpm_template_12.1.3.jar
sh qs_config.sh


The information requested here is: Domain directory, applications directory, user, password and server ports.

Creating a Compact Domain

When we need to add BAM, and other components that require Oracle Database as a repository, we can use the Compact Domain option. This option is similar to the "for Developers" templates on 11g version, all products on the same server (Admin server).

Steps:

  1. Prepare the repository: Create the schemas with RCU on a database certified (e.g: 11.2.0.4)
  2. Create the domain using the wizard.

RCU Configuration

This RCU  release includes some improvements:
  • Is included within a new package called Oracle Fusion Middleware Infrastructure that includes: Oracle JRF (librerías ADF), RCU and other additional components. This package is included on the QuickStart installer.
  • RCU can generate the script to be executed by the DBA.
  • There is a new "management" schema created to map the other schemas configuration and avoid enter the same information on each schema.
  • There are database sizes depending on your environment: SMALL, MEDIUM, and LARGE. To more information about the sizes: Oracle Documentation
Run the following commands:

cd $MW_HOME/oracle_common/bin
sh rcu

And add your repository information:




Create the Domain

Now we can start the domain configuration:

cd $MW_HOME/soa/common/bin
export CONFIG_JVM_ARGS=-Dcom.oracle.cie.config.showProfile=true
sh config.sh

When the wizard started, 2 options are shown:

  • Create an extended domain: This option is recommended for production environments. Includes cluster and managed servers options.
  • Create a compact domain.


And that's it. The development environment is quite easy to prepare now :-)

2 comments:

  1. Thanks for the nice blog here.I was searching this one for a long time.This blog is very helpful for my studies..I got another one site also,which is same as yours Oracle OSB.Check this one also Oracle Fusion HCM Sure it will be helpful for you too..Once more iam thanking you for your creative blog.

    ReplyDelete