5 Configuring a Compact Domain for Oracle Business Process Management Suite Quick Start

This chapter will guide you through configuring a compact domain for an Oracle Business Process Management installation. By the end of the configuration, you will have created an external Oracle Database and configured a compact domain.

You should have already run the Oracle Business Process Management Quick Start installer as detailed in Chapter 4. You only need to proceed with this chapter if you want to enable or install components that are incompatible with Java DB. These components include Oracle Enterprise Scheduler, Oracle B2B, Oracle Healthcare, Oracle Business Activity Monitoring, and Oracle Managed File Transfer.

This chapter contains the following sections:

5.1 Preparing to Configure a Compact Domain for a Quick Start Installation

This section will help you prepare your system for configuring a compact domain.

A compact domain is a developer domain consisting of a single Administration server. Creating and targeting a compact domain will allow you to use an Oracle Database so that you can install additional components incompatible with the Java DB included by default in the Quick Start installation.

Please make sure you have verified that your Quick Start installation works before moving on to the following tasks:

Task 1   Closing Oracle JDeveloper, Extra Server Connections, or Java DB

Close any instance of Oracle JDeveloper.

To make sure there are no other server connections or instances of Java DB running in the background, use the following command:

Environment Run Command
ps -ef | grep java
Then kill -9 extra running servers or instances of Java DB.
Windows You can bring up the Task Manager and select the Processes tab.

You can also use:

wmic process where "name='java.exe'" get ProcessID, Commandline /format:list

Then use taskkill /f /pid <PID> to end extra running servers or Java DB.

Task 2   Downloading the Necessary Installers

Refer to the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files for the download locations of the following files:

  • A certified Oracle database installer.

  • The installer for Oracle Managed File Transfer

  • The installer for Oracle B2B and Healthcare


In Oracle® Fusion Middleware 12c (12.1.3), the Repository Creation Utility (RCU) is included in the Oracle SOA Suite install. You should not download or use a separate version.

5.2 Installing Required Schemas

This section will guide you through creating the Oracle Database schemas required for a Quick Start compact domain. You can use an existing database if you have one, but this guide assumes you want to create a new database.

You will be completing the following tasks:

Task 1   Installing a Supported Database

Reference the Oracle Fusion Middleware Supported System Configurations page to identify a certified database for Oracle Fusion Middleware 12c.

You should have identified and download a supported database for Oracle Fusion Middleware 12c from the Oracle Technology Network: http://www.oracle.com/technetwork/indexes/downloads/index.html.

Run the installer. The installation guide for your database of choice is linked on the same Oracle Technology Network page, under the Documentation tab next to Downloads.


During installation, take note of your service name and port number. You will need this information for schema creation in the Repository Creation Utility (RCU).


If you are using a 12c multitenant database, you must configure it to use the AL32UTF8 character set.

The Quick Start RCU will not be able to connect to a container database (CDB). You can choose not to create a container database on the "Global Database Creation" screen during database creation. If you create container database, you should also configure a pluggable database (PDB) and point the RCU to the PDB.

Task 2   Running Installers for Additional Components

If you know you want to add Managed File Transfer, B2B, or Healthcare to your Quick Start domain, you should run their installers now. You can refer to Section 6.2 for brief walkthroughs of these installations.

You do not need to run separate installers to add Enterprise Scheduler or Business Activity Monitoring.

If you are not sure which additional products you want yet, you can add any component after creating your compact domain. However, deciding now will minimize the number of times you have to restart your server and run the domain configuration wizard or RCU.

Task 3   Using the Repository Creation Utility to Create Schemas

Invoke the RCU packaged with your Quick Start installation to create schemas in your new database. Do not download or use any other version of RCU to configure a database with Quick Start.

If you have defined ORACLE_HOME and JAVA_HOME variables to point to your Oracle Home, you can use the following command to launch the RCU:

Environment Run Command
cd ORACLE_HOME/oracle_common/bin
cd ORACLE_HOME\oracle_common\bin

Navigate through the screens in Table 5-1. For more information about the options on a specific screen, click the screen's name or see "Understanding Repository Creation Utility Screens" in Creating Schemas with the Repository Creation Utility.

Table 5-1 RCU Schema Creation Screens

Screen Description


This screen provides an introduction to what RCU is and its purpose. Click Next.

Create Repository

Choose Create Repository and System Load and Product Load Concurrently.

If the second option doesn't appear for you, you do not have the necessary permissions or privileges to perform DBA activities.

Database Connection Details

Fill the Host Name, Username, and Password blanks with the credentials for your Oracle database. Your Service Name and Port number were created when you installed your database.

If you using a 12c multitenant database and are having connection issues, make sure you are not trying to connect to a container database (CDB). You should also make sure your database is configured to use the AL32UTF8 character set. See the 12c Database Administrator's Guide for how to configure a compatible PDB.

Click Next.

Checking Prerequisites

This screen will pop up with a progress indicator bar. When the prerequisites are checked off, click OK to continue.

Select Components

Specify an intuitive prefix for your new schemas, such as BPM, so you can target them easily when you are configuring a domain.

Select SOA Suite. This will automatically select all the schemas you need.

Description of bpmcreateschemas.gif follows
Description of the illustration ''bpmcreateschemas.gif''

If you are installing Oracle Managed File Transfer, select Managed File Transfer from the list. You will not see this option listed if you have not run the corresponding installer yet.

Click Next.

Checking Prerequisites

This screen will pop up with a progress indicator bar. When the prerequisites are checked off, click OK to continue.

Schema Passwords

Select Use same passwords for all schemas. Then create a password you will remember.

Custom Variables

This screen will show up because you are installing SOA Infrastructure. See "About the Custom Variables Required for the SOA Suite Schemas" in Installing and Configuring Oracle SOA Suite and Business Process Management for descriptions of these variables.

Press Next.

Map Tablespaces

This screen displays default and temporary tablespaces for the components you want to create schemas for. You can review this information and click Next

Click OK through the next two confirmation dialogues. Then click Next again to progress to the next screen.


This screen summarizes the component schemas that will be created. Take note of the Database details at the top. Then click Create to begin schema creation.

A new dialogue box will pop up and show you the progress of schema creation. Green checks will appear next to the names of successfully created schemas.

Completion Summary

This screen displays the log files created with the database schemas. You can open any of the log files to review information or to troubleshoot a creation issue.

If any operation failed, you can check the Cleanup for failed components box. Upon clicking Close, this option will drop failed schemas from your database.

When you click Close, schema creation is complete.

If you encountered any problems during schema creation, first make sure you are using the RCU included in your Quick Start installation. You should also make sure that the database server is running. You can then troubleshoot the issue using the log files generated on the Completion Summary screen.

For more information, see "Troubleshooting Repository Creation Utility" in Creating Schemas with the Repository Creation Utility.

5.3 Configuring a Compact Domain

This section provides instructions for creating a compact domain using the configuration wizard.

To launch the domain configuration wizard, complete the following tasks:

Task 1   Launching the Domain Configuration Wizard

Go to ORACLE_HOME/soa/common/bin.

In the command prompt, set the environment variable CONFIG_JVM_ARGS to -Dcom.oracle.cie.config.showProfile=true. This will activate the compact domain option in the configuration wizard. Then launch the configuration wizard.

The commands you would use for this task are as follows:

cd ORACLE_HOME/soa/common/bin
cd ORACLE_HOME\soa\common\bin
SET CONFIG_JVM_ARGS=-Dcom.oracle.cie.config.showProfile=true

Then navigate through the following configuration screens.

Task 2   Selecting the Domain Type and Domain Home Location

On the Configuration Type screen, select Create a new compact domain. If you do not see this option, you did not set the environment variable in Task 1 successfully.

Description of createcompactdomain.gif follows
Description of the illustration ''createcompactdomain.gif''

In the Domain Location field, specify your Domain home directory. If you already launched the Integrated WebLogic Server and generated the default domain, you should create a new domain outside of base_domain.

You should create your Domain home outside the Oracle home directory. See the location of Application Home relative to Oracle Home in Figure 5-1. This directory structure will help you avoid issues when you need to upgrade or re-install your software.

Figure 5-1 Recommended Oracle Fusion Middleware Directory Structure

Description of Figure 5-1 follows
Description of ''Figure 5-1 Recommended Oracle Fusion Middleware Directory Structure''

This directory structure will help you avoid issues when you need to upgrade or reinstall your software. See "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware for more information.

Task 3   Selecting the Configuration Template

On the Templates screen, make sure Create Domain Using Product Templates is selected, then select Oracle BPM Suite - [soa].

Selecting this template automatically selects the following as dependencies:

  • Oracle SOA Suite -[soa]

  • Oracle Enterprise Manager - [em]

  • Oracle WSM Policy Manager - [oracle_common]

  • Oracle JRF - [oracle_common]

  • WebLogic Coherence Cluster Extension - 12 1.3.0 [wlserver]

Description of bpmtemplates.gif follows
Description of the illustration ''bpmtemplates.gif''

Optionally, you can select any of the following:

  • Oracle Business Activity Monitoring -

  • Oracle Enterprise Scheduler Service Basic -

  • Oracle Enterprise Manager Plugin for ESS -

  • Oracle B2B -

  • Oracle Managed File Transfer -

Note for Healthcare Users:

The Healthcare Integration template and BPM Suite template are mutually exclusive. Do not include both of these templates in the same domain as this configuration is not supported by Oracle.

If you have not run the separate installers for Oracle B2B or Oracle Managed File Transfer, then you will not see the options to select those templates. See Chapter 6 for installation instructions for these components.

Task 4   Selecting the Application Home Location

On the Application Location screen, select the location where you want to store your applications associated with your domain. This location is also known as the Application home directory.

Your Application home should be created at the same location you specified for your Domain home in Task 2. See the location of Application Home relative to Oracle Home in Figure 5-1. This directory structure will help you avoid issues when you need to upgrade or re-install your software.

Task 5   Configuring the Administrator Account

On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain. You will use these credentials to connect to the domain's Administrator Server.

Task 6   Specifying the Domain Mode and JDK

On the Domain Mode and JDK screen:

  • Select Development in the Domain Mode field.

  • Select the Oracle HotSpot JDK in the JDK field.

Task 7   Specifying the Datasource Configuration Type

On the Database Configuration Type screen, select RCU Data to activate the fields. The RCU Data option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for the schemas needed to configure the domain.


If you choose to select Manual Configuration on this screen, you will have to manually fill in the parameters for your schema on the following screen.

After selecting RCU Data, fill in the following fields:

Field Description
DBMS/Service Enter the database DBMS name, or service name if you selected a service type driver. If you are using a 12c multitenant database, make sure you use the service name for a configured pluggable database (PDB) and not the container.
Host Name Enter the name of the server hosting the database.
Port Enter the port number on which the database listens.
Schema Owner

Schema Password

Enter the username and password for connecting to the database's Service Table schema. This is the schema username and password that was specified for the Service Table component on the "Schema Passwords" screen in the RCU.

The default username is prefix_STB, where prefix is the custom prefix that you defined in RCU.

Click Get RCU Configuration when you are finished specifying the database connection information. The following output in the Connection Result Log indicates that the operation succeeded:

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.


More information about the RCU Data option can be found in "Understanding the Service Table Schema" in Creating Schemas with the Repository Creation Utility.
Task 8   Specifying JDBC Component Schema Information

Verify that the values on the JDBC Component Schema screen are correct for all schemas. If you selected RCU Data on the previous screen, the schema table should already be populated appropriately.

Task 9   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the datasource connections you have just configured.

A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.

Task 10   Selecting Advanced Configuration

You do not need any advanced configuration for a compact domain. You can skip through the Advanced Configuration screen without selecting anything.

Task 11   Configuring the Domain

The Configuration Summary screen will show you the final directory structure and the components and extensions with which your compact domain will be configured. Review this information and click Create.

The configuration progress bar will appear on the Configuration Progress screen.

Task 12   Reviewing Your Domain Location

Upon successful configuration, the Configuration Success screen will give you the directory location of your domain and the URL for your administration console access. Take note of both and click Close.

Task 13   Start the Administrator Server

When the configuration wizard is done, start the administrator server with the following command:


If you want to use JDeveloper's Integrated WebLogic Server, on the same system in conjunction with your compact domain, add the flag -noderby to the end of the command. For example, the Linux launch command will look like the following:

./startWebLogic.sh noderby

The -noderby option will prevent the Derby Java Database from starting in the Java Virtual Machine. This will prevent any conflicts with the Integrated WebLogic Server, which needs to initialize the Derby Java Database to start up successfully.

You know that the administrator server is running when you see the following output:

Server state changed to RUNNING.

5.4 Connecting JDeveloper to the Compact Domain

This section will help you prepare JDeveloper to target your compact domain for launching applications. You will do the following tasks:

Task 1   Launching the Application Server Connection Wizard

Launch Oracle JDeveloper.

Select Window from the top menu, and then choose Application Server from the drop-down menu. Alternatively, use the keyboard shortcut Ctrl-Shift-G. This will open the Application Server Navigator in the left-hand pane.

Description of launchapplicationserver.gif follows
Description of the illustration ''launchapplicationserver.gif''

Right-click on Application Server in the Application Server Navigator. Select New Application Server from the drop-down menu to launch the Create Application Server Connection wizard.

Description of newapplicationserver.gif follows
Description of the illustration ''newapplicationserver.gif''

Task 2   Navigating through the Create Application Server Connection wizard.

Table 5-2 Application Server Connection Creation Screens

Screen Description


Make sure Standalone Server is selected.

Click Next.

Name and Type

Specify an intuitive Connection Name for your server.

Leave WebLogic 12.x selected as the Connection Type.

Click Next.


Input the Username and Password you created during Task 5 of domain configuration.

Click Next.


Input the compact domain's name if you specified something besides base_domain during Task 2 of domain configuration. If the compact domain is your base_domain, then you can click Next without changing anything on the screen.


Click the Test Connection button at the top. If any of the tests fail, you should press Back to the Connections or Authentication screens to make sure you inputted everything correctly.

If everything passes, click Next.


The Finish screen tells you how to launch your new connection, covered in the following task. Click Finish.

Task 3   Verifying Your Connection

Expand the connection node beside Application Servers in the Application Server Navigator. You should see your compact domain listed by the Connection Name you specified on the Name and Type screen.

Right-click on your compact domain's name and choose Launch Administrative Console.

Description of launchadminconsole.gif follows
Description of the illustration ''launchadminconsole.gif''

Log into your administrative console. If you can log in successfully and see that your servers are running, then you can begin creating applications in JDeveloper.


If you are curious about the options you see while connecting to the compact domain, see "Connecting and Working with Databases" and "How to Create a Connection to the Target Application Server" in Developing Applications with Oracle JDeveloper.

5.5 Next Steps

Once you have verified your Oracle Business Process Management Suite installation and compact domain connection, you can take any of the following actions:

Action Resource
Deploy a sample application. See Chapter 7 of this book.
Make or test an application of your own. See "Getting Started with Developing Applications with Oracle JDeveloper" in Developing Applications with Oracle JDeveloper.
Add Oracle Managed File Transfer, Oracle Event Processing, or Oracle B2B/Healthcare. See Chapter 6 of this book for instructions on adding components to a fully configured compact domain.
Delete your installation. If you have tested your installation out and are done, see Chapter 8 of this book.