Before you begin the configuration process, ensure that you have completed installing the Oracle Service Bus software in the same Oracle home as Oracle Fusion Middleware Infrastructure. For more information, see Chapter 2.
By the end of this chapter, you would have created database schemas for Oracle Service Bus and configured an Oracle WebLogic domain with one cluster and two managed servers on a single host.
This chapter contains the following sections:
Before you can configure an Oracle Service Bus domain, you must install the required schemas on a certified database for use with this release of Oracle Fusion Middleware.
Follow the instructions in this section to install the schemas.
Ensure that you have installed and configured a certified database, and that the database is up and running.
For more information, see "Installing a Database and Database Schemas" in Planning an Installation of Oracle Fusion Middleware.
To start the Repository Creation Utility (RCU):
Navigate to the
/oracle_common/bin directory on your system.
Make sure that the
JAVA_HOME environment variable is set to the location of a certified JDK on your system. The location should be up to but not including the
bin directory. For example, if your JDK is located in in
On UNIX operating systems:
setenv JAVA_HOME /home/Oracle/JDK/jdk7_55/jdk1.7.0_55
On Windows operating systems:
On UNIX operating systems:
On Microsoft Windows operating systems:
Schema creation involves the following tasks:
This is the Welcome screen. Click Next.
If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have the necessary privileges.
If you do not have the necessary permission or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option will generate an SQL script, which can be provided to your database administrator. See "Understanding System Load and Product Load" in Creating Schemas with the Repository Creation Utility.
Provide the database connection details for RCU to connect to your database. You must provide the following information:
Click Next to proceed, then click OK on the dialog window confirming that connection to the database was successful.
Select Create new prefix, specify a custom prefix, then select the SOA Suite schema. This will automatically select SOA Infrastructure, along with the following schemas as dependencies:
Audit Services Append
Audit Services Viewer
Oracle Platform Security Services
User Messaging Service
A schema called Common Infrastructure Services is also automatically created; this schema is grayed out and cannot be selected or deselected. This schema enables you to retrieve information from RCU during domain configuration. For more information, see "Understanding the Service Table Schema" in Creating Schemas with the Repository Creation Utility.
The custom prefix is used to logically group these schemas together for use in this domain only; you must create a unique set of schemas for each domain as schema sharing across domains is not supported.
For more information about custom prefixes, see "Understanding Custom Prefixes" in Creating Schemas with the Repository Creation Utility.
For more information about how to organize your schemas in a multi-domain environment, see "Planning Your Schema Creation" in Creating Schemas with the Repository Creation Utility.
You must make a note of the custom prefix you choose to enter here; you will need this later on during the domain creation process.
Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.
Specify how you want to set the schema passwords on your database, then specify and confirm your passwords.
You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.
Specify the custom variables for the SOA Infrastructure schema. For the Oracle Service Bus standard installation topology, accept both default values for the Database Profile (SMALL) and Healthcare Integration (NO).
For more information about the options on this screen, see "Custom Variables" in Creating Schemas with the Repository Creation Utility.
Navigate through the remainder of the RCU screens to complete schema creation. When you reach the Completion Summary screen, click Close to dismiss RCU.
This section provides instructions for creating a WebLogic domain by using the configuration wizard. For more information on other methods available for domain creation, see "Additional Tools for Creating, Extending, and Managing WebLogic Domains" in Creating WebLogic Domains Using the Configuration Wizard.
Creating and configuring your domain includes the following:
To begin the domain configuration, navigate to the
/oracle_common/common/bin directory and start the WebLogic Server Configuration Wizard.
On UNIX operating systems:
On Microsoft Windows operating systems:
Follow the instructions in this section to create and configure the domain for the topology.
You can use the same procedure described in this section to extend an existing domain. If your needs do not match the instructions given in the procedure, be sure to make your selections accordingly, or refer to the supporting documentation for additional details.
Domain creation and configuration includes the following tasks:
On the Configuration Type screen, select Create a new domain.
In the Domain Location field, specify your Domain home directory.
It is recommended that you locate your Domain home in accordance with the directory structure summarized in "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware, where the Domain home is located outside the Oracle home directory. This directory structure will help you avoid issues when you need to upgrade or reinstall your software.
For more information about the options on this screen, see "Configuration Type" in Creating WebLogic Domains Using the Configuration Wizard.
On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:
Oracle Service Bus - 188.8.131.52 [osb]]
Selecting this template automatically selects the following as dependencies:
WebLogic Advanced Web Services for JAX-RPC Extension - 12.1.3 [oracle_common]
Oracle Enterprise Manager - 184.108.40.206 [em]
Oracle WSM Policy Manager - 220.127.116.11 [oracle_common]
Oracle JRF - 18.104.22.168 [oracle_common]
WebLogic Coherence Cluster Extension - 12 1.3.0 [wlserver]
ODSI XQuery 2004 Components - 22.214.171.124 [oracle_common]
For more information about the options on this screen, see "Templates" in Creating WebLogic Domains Using the Configuration Wizard.
On the Application Location screen, select the location in which you want to store your applications associated with your domain. This location is also referred to as the Application home directory.
It is recommended that you locate your Application home in accordance with the directory structure summarized in "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware, where the Application home is located outside the Oracle home directory. This directory structure will help you avoid issues when you need to upgrade or re-install your software.
On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain.
It is recommended that you make a note of the user name and password specified on this screen; you will need these credentials later to boot and connect to the domain's Administration Server.
On the Domain Mode and JDK screen:
Select Production in the Domain Mode field.
Select the Oracle HotSpot JDK in the JDK field.
For more information about the options on this screen, see "Domain Mode and JDK" in Creating WebLogic Domains Using the Configuration Wizard.
Select RCU Data to activate the fields on this screen. 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 JDBC Component Schema screen.
After selecting RCU Data, fill in the following fields:
Enter the database DBMS name, or service name if you selected a service type driver.
Enter the name of the server hosting the database.
Enter the port number on which the database listens.
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 RCU (see Task 5 in Section 3.1.3).
The default username is
Click Get RCU Configuration when you finish specifying the database connection information. The following output in the Connection Result Log indicates that the operating succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
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.
For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:
For more information about the options on this screen, see "JDBC Component Schema" in Creating WebLogic Domains Using the Configuration Wizard.
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.
By default, the schema password for each schema component is the password you have specified while creating your schemas. If you want different passwords for different schema components, manually edit them by entering the desired password in the Schema Password column, against each row. After specifying the passwords, select the check box corresponding to the schemas that you have changed the password in and test the connection again.
For more information about the options on this screen, see "Test Component Schema" in Creating WebLogic Domains Using the Configuration Wizard.
To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:
This is required to properly configure the listen address of the Administration Server.
This is required to configure Node Manager.
Managed Server, Clusters and Coherence
This is required to configure the Oracle Service Bus Managed Server.
On the Administration Server screen, select the drop-down list next to Listen Address and select the IP address on the host where the Administration Server will reside. Do not use "All Local Addresses."
Do not specify any server groups for the Administration Server.
The Node Manager screen can be used to select the type of Node Manager you want to configure, along with the Node Manager credentials.
Select Per Domain Default Location as the Node Manager type, then specify the Node Manager credentials.
On the Managed Servers screen, a new Managed Server named
osb_server1 is created:
In the Listen Address drop-down list, select the IP address of the host on which the Managed Server will reside. Do not use All Local Addresses. Verify that OSB-MGD-SVRS-COMBINED is selected in the Server Group.
If you want to have OWSMPM in a different server from the OSB server, select OSB-MGD-SVRS-ONLY. This targets only OSB but not OWSMPM to the server.
Click Add and repeat this process to create a second Managed Server named
Configuring a second Managed Server is one of the steps needed to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.
For more information about the high availability standard topology, see "Understanding the Fusion Middleware Standard HA Topology" in High Availability Guide.
For more information about the next steps to prepare for high availability after your domain is configured, see Section 4.3.
These server names will be referenced throughout this document; if you choose different names be sure to replace them as needed.
For more information about the options on this screen, see "Managed Servers" in Creating WebLogic Domains Using the Configuration Wizard.
Use the Clusters screen to create a new cluster:
osb_cluster1 in the Cluster Name field.
Leave the Cluster Address field blank.
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, see "Considerations for Choosing Unicast or Multicast" in Administering Clusters for Oracle WebLogic Server.
New clusters can also be created using Fusion Middleware Control. In such cases, cluster communication (unicast or multicast) can be configured when the new cluster is created. For more information, see "Create and configure clusters" in Oracle WebLogic Server Administration Console Online Help.
For more information about the options on this screen, see "Clusters" in Creating WebLogic Domains Using the Configuration Wizard.
Use the Assign Servers to Clusters screen to assign
osb_server2 to the new cluster
In the Clusters pane, select the cluster to which you want to assign the servers; in this case,
In the Servers pane, assign
osb_cluster1 by doing one of the following:
Click once on
osb_server1 to select it, then click on the right arrow to move it beneath the selected cluster (
osb_cluster1) in the Clusters pane.
osb_server1 to move it beneath the selected cluster (
osb_cluster1) in the clusters pane.
Repeat to assign
For more information about the options on this screen, see "Assign Servers to Clusters" in Creating WebLogic Domains Using the Configuration Wizard.
Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the default port number 0 as the Coherence cluster listen port.
Setting the unicast listen port to 0 creates an offset for the Managed Server port numbers. The offset is 5000, meaning the maximum allowed value that can be assigned to a Managed Server port number is 60535, instead of 65535.
See Table 4-2 for more information and next steps for configuring Coherence.
For Coherence licensing information, see "Oracle Coherence" in Licensing Information.
Use the Machines screen to create a new machine in the domain. A machine is required in order for the Node Manager to be able to start and stop the servers.
If you plan to create a high availability environment and know the list of machines required for your target topology, you can follow the directions in this section to create all of the machines at this time. For more information, see "Optional Scale Out Procedure" in High Availability Guide.
Click Add to create a new machine.
osb_machine1 in the Name field.
In the Node Manager Listen Address field, select the IP address of the machine where the Managed Servers are being configured.
You must select a specific interface and not "localhost." This allows Coherence cluster addresses to be dynamically calculated.
Verify the port in the Node Manager Listen Port field.
The port number
5556, shown in this example, may be referenced by other examples in the documentation. Replace this port number with your own port number as needed.
If you are extending an existing domain, you can assign servers to any existing machine. It is not necessary to create a new machine unless your situation requires it.
For more information about the options on this screen, see "Machines" in Creating WebLogic Domains Using the Configuration Wizard.
Use the Assign Servers to Machines screen to assign the Administration Server and Managed Servers to the new machine you just created:
In the Machines pane, select the machine to which you want to assign the servers; in this case,
In the Servers pane, assign
osb_machine1 by doing one of the following:
Click once on
AdminServer to select it, then click on the right arrow to move it beneath the selected machine (
osb_machine1) in the Machines pane.
AdminServer to move it beneath the selected machine (
osb_machine1) in the Machines pane.
Repeat to assign both
For more information about the options on this screen, see "Assign Servers to Machines" in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.
You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.
Domain creation will not begin until you click Create.
For more information about the options on this screen, see "Configuration Summary" in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Success screen will show the following items about the domain you just configured:
Administration Server URL
You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.
Click Finish to dismiss the configuration wizard.
After the configuration is complete, do the following to access the tools with which you can manage your domain:
For more information on additional tools you can use to manage your domain, see "Overview of Oracle Fusion Middleware Administration Tools" in Administering Oracle Fusion Middleware.
To start your per-domain Node Manager, go to the
On UNIX operating systems, start the Node Manager as shown below, using
nm.out as an example output file:
nohup ./startNodeManager.sh > $LOG_DIR/nm.out&
In the preceding command,
LOG_DIR is the location of directory in which you want to store the log files.
On Windows operating systems, run:
On Windows operating systems, it is recommended that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.
For more information, see "Running Node Manager as a Startup Service" in Administering Node Manager for Oracle WebLogic Server.
For more information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.
To start the Administration Server, go the
On UNIX operating systems, run:
On Windows operating systems, run:
If you have selected Production Mode on the Domain Mode and JDK screen in Task 5 (Section 3.2.2), you will be prompted for the login credentials of the Administrator user as provided on the Administrator Account screen in Task 4.
For more information about starting the Administration Server, see "Starting and Stopping Administration Servers" in Administering Oracle Fusion Middleware.
In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. For more information, see "Creating a Boot Identity File for an Administration Server" in Administering Server Startup and Shutdown for Oracle WebLogic Server.
You can verify that the Administration Server is up and running by accessing the Administration Server Console. The URL is provided on the Configuration Success screen in Task 19.
Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.
The default Administration Server port number is
For more information about how to use the Administration Console, see "Getting Started Using Oracle WebLogic Server Administration Console" in Administering Oracle Fusion Middleware.
To start the Managed Servers:
Log in to Oracle Fusion Middleware Control:
The Administration Server host and port number were in the URL on the Configuration Success screen (Task 19). The default Administration Server port number is
The login credentials were provided on the Administrator Account screen (Task 4).
From the "Target Navigation" pane, click the arrows to expand the domain until the Managed Servers (
osb_server2) are visible.
In the Target Navigation page, select your domain name to see that all the servers are up and running.
To verify that your domain is configured properly, see Section 4.1. You should familiarize yourself with the tasks described in the section and perform them to verify that your domain is properly configured.