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 Business Activity Monitoring, Oracle B2B, Oracle Enterprise Scheduler, Oracle Managed File Transfer, Oracle Real-Time Integration Business Insight, Oracle SOA Suite for Healthcare Integration, and Oracle Stream Analytics.
Parent topic: Quick Start for Oracle Business Process Management Suite
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. |
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:
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 |
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 |
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.
You will need to create the schemas required for a Quick Start compact domain.
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 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.
In a developer environment, you can create a compact domain using the Configuration Wizard.
Go to the bin
directory.
Set the environment variable CONFIG_JVM_ARGS
to -Dcom.oracle.cie.config.showProfile=true
. This enables the Create a new compact domain option in the Configuration Wizard.
Launch the Configuration Wizard.
If you have set the ORACLE_HOME
environment variable to your Oracle home, you can enter the following commands:
Operating System | Command |
---|---|
UNIX |
cd $ORACLE_HOME/oracle_common/common/bin setenv 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 |
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 8-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 Oracle Fusion Middleware Understanding Oracle Fusion Middleware for more information.
On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following template:
Oracle BPM Suite - 12.2.1.2.0 [soa]
Selecting this template automatically selects the following as dependencies:
Oracle SOA Suite
Oracle Enterprise Manager
Oracle WSM Policy Manager
Oracle JRF
WebLogic Coherence Cluster Extension
Optionally, select the following to install additional components:
Insight SOA Agent 12.2.1.2.0 [soa]
Insight Service Bus Agent 12.2.1.2.0 [osb]
Insight 12.2.1.2.0 [soa]
Oracle SOA Suite for healthcare integration - 12.2.1.2.0 [soa]
Note:
For HIPAA documents, select both the Oracle SOA Suite for healthcare integration - 12.2.1.2.0 [soa] template and Oracle B2B - 12.2.1.2.0 [soa] template.
For HL7 documents, select the Oracle SOA Suite for healthcare integration - 12.2.1.2.0 [soa] template only.
Oracle Business Activity Monitoring - 12.2.1.2.0 [soa]
Oracle Enterprise Scheduler Service Basic - 12.2.1.2.0 [oracle_common]
Oracle Enterprise Manager Plugin for ESS - 12.2.1.2.0 [em]
Oracle B2B - 12.2.1.2.0 [soa]
Oracle Managed File Transfer - 12.2.1.2.0 [mft]
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.
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.
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.
On the Domain Mode and JDK screen:
In the Domain Mode field, select Development.
In the JDK field, select Oracle HotSpot JDK.
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 |
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 Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.
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.
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.
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 Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard .
You do not need any advanced configuration for a compact domain. You can skip through the Advanced Configuration screen without selecting anything.
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 screen shows the configuration progress bar.
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.
After configuring a compact domain, you need to prepare JDeveloper to target the new compact domain for launching applications.
Start Oracle JDeveloper with the appropriate command.
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.
Right-click on Application Server in the Application Server Navigator. Select New Application Server from the drop-down menu to start the Create Application Server Connection wizard.
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.
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.
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. |
|
Make or test an application of your own. |
See Getting Started with Developing Applications with Oracle JDeveloper in Oracle Fusion Middleware 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. |