5 Configuring a Compact Domain

After configuring a compact domain for a Quick Start installation, you will have created an external Oracle Database.

Follow the steps in this section only if you want create applications with components that are incompatible with the Integrated WebLogic Server's Java DB. These components include Oracle Enterprise Scheduler, Oracle B2B, Oracle Healthcare, Oracle Business Activity Monitoring, and Oracle Managed File Transfer.

5.1 Orientation

This is where you are in the Quick Start installation and configuration roadmap.

Step Description

Plan your installation.

Use Chapter 1 to decide which distribution and configuration path suits your goals.

Download and install a Quick Start distribution

You downloaded and installed Quick Start for Oracle SOA Suite or Oracle Business Process Management Suite.

Configure a compact domain.

You are configuring a default domain, a standalone domain, or compact domain for your developed applications.

Develop or test an application.

You will develop or test an application.

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

You will need to prepare your system for configuring a compact domain.

A compact domain is a developer domain consisting of a single Administration server and no managed servers. Configuring 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.

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

5.2.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

UNIX

ps -ef | grep java

Then kill -9 extra running servers or instances of Java DB.

Windows

Bring up the Task Manager and select the Processes tab. Kill any running instances of JDeveloper, Java DB, or running servers.

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.

5.2.2 Downloading and Installing a Supported Database

To download and install a supported database:
  1. Refer to the Oracle Fusion Middleware Download, Installation, and Configuration Readme Files for the download location of a supported database for Oracle Fusion Middleware 12c.
  2. 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, make note of your service name and port number. You will need this information for schema creation.

5.2.3 Configuring a 12c Database for Quick Start

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

Quick Start's Repository Creation Utility 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 do create container database, you can create a pluggable database (PDB) within the CDB. Then point the RCU to the PDB. See the 12c Database Administrator's Guide for how to configure a compatible PDB.

5.3 Installing Required Schemas

You will need to create the schemas required for a Quick Start compact domain.

5.3.1 Running Installers for Additional Components

If you know you want to add Oracle Managed File Transfer, Oracle B2B, or Oracle SOA Suite for healthcare integration, you should download and run their installers before running the RCU for the first time. Refer to Installing Oracle B2B, Oracle SOA Suite for Healthcare Integration, or Oracle Managed File Transfer for Quick Start for brief walkthroughs of these installations.

You do not need to run separate installers to add Oracle Enterprise Scheduler or Oracle 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.

Note:

In 12c, the Repository Creation Utility (RCU) is included in the Oracle SOA Suite install. Do not download or use a separate version.

If you have finished configuring a compact domain but want to add new schemas, see Updating a Compact Domain for how to update a compact domain.

5.3.2 Creating Schemas for Quick Start with the Repository Creation Utility

To create schemas with the Repository Creation Utility (RCU):
  1. Launch 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 set the ORACLE_HOME environment variable to your Oracle home, you can enter commands similar to the following examples:

    Environment Run Command

    UNIX

    cd $ORACLE_HOME/oracle_common/bin
    ./rcu
    

    Windows

    cd %ORACLE_HOME\oracle_common\bin
    rcu.bat
    
  2. Navigate through the following screens. For more information about the options on a specific screen, click Help or see Understanding Repository Creation Utility Screens in Creating Schemas with the Repository Creation Utility.

    Table 5-1 RCU Schema Creation Screens

    Screen Description

    Welcome

    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 have configured your database properly.

    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 SOAQS or BPMQS, so you can target them easily when you are configuring a domain.

    Select AS Common Schemes and SOA Suite to select all of their dependencies.

    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.

    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.

    If you are a healthcare provider and want the Healthcare Integration user interface, change the Value field for Healthcare Integration to Yes. If you do not set this value now, the Healthcare Integration user interface will not function properly. See Activating the Oracle SOA Suite for Healthcare Integration User Interface for more information.

    Otherwise, accept the defaults and 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.

    Summary

    This screen summarizes the component schemas that will be created. Take note of the Database details at the top of this screen.

    Click Create to begin schema creation.

    A progress dialog shows 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, verify the following:

    • You are using the RCU included in your Quick Start installation.

    • Your database server and listeners are running.

    • If you are using a 12c database, you have configured your database properly.

    You can also 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.4 Configuring a Compact Domain

In a developer environment, you can create a compact domain using the Configuration Wizard.

5.4.1 Starting the Configuration Wizard

To start the configuration wizard to create a compact domain:
  1. Go to the bin directory.

  2. Set the environment variable CONFIG_JVM_ARGS to -Dcom.oracle.cie.config.showProfile=true. This enables the compact domain option in the configuration wizard.

  3. Launch the configuration wizard.

If you have set the ORACLE_HOME environment variable to your Oracle home, you can enter commands similar to the following examples:

Operating System Command

UNIX

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

Windows

cd %ORACLE_HOME\oracle_common\common\bin
SET CONFIG_JVM_ARGS=-Dcom.oracle.cie.config.showProfile=true
config.cmd

5.4.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 CONFIG_JVM_ARGS environment variable successfully.

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 the following figure.

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.

5.4.3 Selecting Configuration Templates for Oracle SOA Suite Quick Start

On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:

  • Oracle SOA Suite - 12.2.1.1.0 [soa]

    Selecting this template automatically selects the following as dependencies:

    • Oracle Enterprise Manager

    • Oracle WSM Policy Manager

    • Oracle JRF

    • WebLogic Coherence Cluster Extension

  • Oracle Service Bus - 12.2.1.1.0 [osb]

    Selecting this template automatically selects the following as a dependency:

    • WebLogic Advanced Web Services for JAX-RPC Extension

  • Oracle Enterprise Scheduler Service Basic - 12.2.1.1.0 [oracle_common]

  • Oracle Enterprise Manager Plugin for ESS - 12.2.1.1.0 [em]

Optionally, you can select the following:

  • Oracle SOA Suite for healthcare integration -12.2.1.1.0 [soa]

    Note:

    For HIPAA documents, select both the Oracle SOA Suite for healthcare integration - 12.2.1.1.0 [soa] template and Oracle B2B - 12.2.1.1.0 [soa] template.

    For HL7 documents, select Oracle SOA Suite for healthcare integration - 12.2.1.1.0 [soa] only.

  • Oracle Business Activity Monitoring - 12.2.1.1.0 [soa]

  • Oracle B2B - 12.2.1.1.0 [soa]

  • Oracle Managed File Transfer -12.2.1.1.0 [mft]

If you have not run the installers for Oracle B2B, Oracle Healthcare Integration, or Oracle Managed File Transfer, you will not see the options to select those templates. See About Adding Components to a Quick Start Installation for installation instructions for these components.

5.4.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 above.

5.4.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.

5.4.6 Specifying the Domain Mode and JDK

On the Domain Mode and JDK screen:

  • In the Domain Mode field, select Development.

  • In the JDK field, select Oracle HotSpot JDK.

5.4.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.

Note:

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.

Tip:

For more information about the RCU Data option, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

5.4.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.

5.4.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.

5.4.10 Specifying the Path to the Keystore Certificate or Key

Use the Keystore screen to specify either the path to the trusted certificate for each keystore, or the path to each keystore’s private key and other private key information.

Use the screen to specify either the path to the trusted certificate for each keystore, or the path to each keystore’s private key and other private key information.

When you click in the Trusted Certificate, Private Key, or Identity Certificate fields, a browse icon appears to the right of the field. Click this icon to browse to the appropriate file.

Tip:

See Keystore in Creating WebLogic Domains Using the Configuration Wizard for more information about other options on this screen.

5.4.11 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.

5.4.12 Configuring the Domain

The Configuration Summary screen shows 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.

5.4.13 Reviewing Your Domain Location

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

When the configuration wizard is done, navigate to your compact domain's home and start the administrator server with the following command:

Operating System Command

UNIX

cd DOMAIN_HOME/bin
./startWebLogic.sh

Windows

cd DOMAIN_HOME\bin
startWebLogic.cmd

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.5 Connecting JDeveloper to the Compact Domain

After configuring a compact domain, you need to prepare JDeveloper to target the new compact domain for launching applications.

5.5.1 Launching the Application Server Connection Wizard

Launch Oracle JDeveloper with the appropriate command.

If you have set the ORACLE_HOME environment variable to your Oracle home, you can enter commands similar to the following examples:

Environment Run Command

UNIX

cd $ORACLE_HOME/jdeveloper/jdev/bin
./jdev

Windows

CD %ORACLE_HOME%\jdeveloper
jdeveloper.exe

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.

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.

5.5.2 Reviewing Your Domain Location

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

When the configuration wizard is done, navigate to your compact domain's home and start the administrator server with the following command:

Operating System Command

UNIX

cd DOMAIN_HOME/bin
./startWebLogic.sh

Windows

cd DOMAIN_HOME\bin
startWebLogic.cmd

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.5.3 Verifying Your Connection

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

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

Log into your administrative console. If you log in successfully, then you can begin creating applications.

5.6 Next Steps

Once you have verified your Quick start installation and compact domain connection, you can take any of the following actions:

Action Resource

Deploy a sample application for Oracle SOA Suite Quick Start.

See Running a Sample Application.

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 Stream Analytics, or Oracle B2B/Healthcare.

See Adding Components to a Quick Start Installation 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 Deinstalling Oracle Quick Start.