Follow the steps in this section to configure a compact domain for a Quick Start installation. By the end of the configuration, you will have created an external Oracle Database and configured a compact domain.

Follow these steps 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.

8.1 Orientation

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

Step

Description

Plan your installation.

You used 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 compact domain for your developed applications.

Develop or test an application.

You will develop or test an application.

8.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:

8.2.2.1 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 12cDatabase Administrator's Guide for how to configure a compatible PDB.

8.3 Installing Required Schemas

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

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

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 12cDatabase 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.

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.

8.4 Configuring a Compact Domain

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

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.

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

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

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

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

8.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:

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

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

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

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:

For more information about this screen, see Keystore in Creating WebLogic Domains Using the Configuration Wizard .

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

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

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

If you have set the DOMAIN_HOME environment variable to your domain home location, you can enter the following commands to start the domain’s Administration Server:

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

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

8.5.1 Launching the Application Server Connection Wizard

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

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.

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

If you have set the DOMAIN_HOME environment variable to your domain home location, you can enter the following commands to start the domain’s Administration Server:

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

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