To start the installation program, perform the following steps.

Table 13-2 provides description of each installation program screen.

If you have configured a separate shared storage volume or partition for SOAHOST2, then you must also install the software on SOAHOST2. For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.

Note that the location where you install the Oracle home (which contains the software binaries) varies, depending upon the host. To identify the proper location for your Oracle home directories, refer to the guidelines in File System and Directory Variables Used in This Guide.

After you complete the installation, you can verify it by successfully completing the following tasks.

To begin domain configuration:

In this step, you extend the domain created in Extending the Domain with Oracle SOA Suite , and add the Oracle Service Bus software components and Managed Servers.

The steps reflected in this section would be very similar if Oracle Service Bus was extending a domain containing only an Administration Server and a WSM-PM Cluster, but some of the options, libraries, and components shown in the screens could vary.

Follow the instructions in this section to extend the domain for Oracle Service Bus.

Domain creation and configuration includes the following tasks.

• Task 1, "Selecting the Domain Type and Domain Home Location"

• Task 2, "Selecting the Configuration Template"

• Task 3, "Specifying the Database Configuration Type"

• Task 4, "Specifying JDBC Component Schema Information"

• Task 5, "Providing the GridLink Oracle RAC Database Connection Details"

• Task 6, "Testing the JDBC Connections"

• Task 7, "Selecting Advanced Configuration"

• Task 8, "Configuring Managed Servers"

• Task 9, "Configuring a Cluster"

• Task 10, "Assigning Server Templates"

• Task 11, "Configuring Dynamic Servers"

• Task 12, "Assigning Managed Servers to the Cluster"

• Task 13, "Configuring Coherence Clusters"

• Task 14, "Verifying the Existing Machines"

• Task 15, "Assigning Servers to Machines"

• Task 16, "Reviewing Your Configuration Specifications and Configuring the Domain"

• Task 17, "Writing Down Your Domain Home and Administration Server URL"

• Task 18, "Start the Administration Server"

Task 1   Selecting the Domain Type and Domain Home Location

On the Configuration Type screen, select Update an existing domain.

In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the Administration Server domain home that you created when you created in Creating the Initial Infrastructure Domain for an Enterprise Deployment.

For more information about the directory location variables, see File System and Directory Variables Used in This Guide.

For more information about the other options on this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

Task 2   Selecting the Configuration Template

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

• Oracle Service Bus Reference Configuration [osb]

  The following additional templates should already be selected, because they were used to create the initial domain:

  • Oracle SOA Suite Reference Configuration [soa] (if you are extending a SOA domain)

  • Oracle Enterprise Manager [em]

  • Oracle WSM Policy Manager [oracle_common]

  • Oracle JRF [oracle_common]

  • WebLogic Coherence Cluster Extension [wlserver]

  The ODSI XQuery 2004 Components [oracle_common] template is also automatically selected when you select Oracle Service Bus template.

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

Note:

If you plan to extend the domain to add a component that does not support Reference Configuration, such as BPM and BAM (Reference Configuration is supported only in SOA, OSB, B2B, and ESS), or if you are extending a classic SOA domain with OSB, the OSB classic domain templates must be used.

The classic OSB template, which does not implement the optimizations included in Reference Configuration is as follows:

Oracle Service Bus - 14.1.2.0.0 [osb]

Subsequent extensions on a classic domain for B2B or SOA must be done with Classic extension templates and not with Reference Configuration templates.

Task 3   Specifying the Database Configuration Type

On the Database Configuration Type screen, select RCU Data.

All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain.

• Verify that the Vendor is Oracle and the Driver is *Oracle's Driver (Thin) for Service Connections; Versions: Any.

• Verify that Connection Parameters is selected.

• Verify and ensure that credentials in all the fields are the same as those provided during the configuration of Oracle Fusion Middleware Infrastructure.

Click Get RCU Configuration after you finish verifying 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.

Tip:

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

For more information about the other options on this screen, see Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard.

Task 4   Specifying JDBC Component Schema Information

On the JDBC Component Schema screen, select OSB JMS Reporting Provider component schema.

When you select the schemas, the fields on the page are activated and the database connection fields are populated automatically.

Click Convert to GridLink, and then click Next.

Task 5   Providing the GridLink Oracle RAC Database Connection Details

On the GridLink Oracle RAC Component Schema screen, provide the information that is required to connect to the RAC database and component schemas, as shown in the following table.

Table 13-3 Providing the GridLink Oracle RAC Database Connection Details

Element	Description and Recommended Value
Service Name	Verify that the service name for the Oracle RAC database is appropriate. For example, soaedg.example.com.
SCAN, Host Name, and Port	Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, 1521).
ONS Host and Port	These values are not required when you are using an Oracle 12c database or higher versions because the ONS list is automatically provided from the database to the driver.
Enable Fan	Verify that the Enable Fan check box is selected, so the database can receive and process FAN events.

Task 6   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source connections that 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.

For more information about the other options on this screen, see Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard.

Task 7   Selecting Advanced Configuration

To complete domain configuration for the topology, select Topology on the Advanced Configuration screen.

Note:

JDBC stores are recommended and selected in Task 3, "Configuring High Availability Options" so there is no need to configure File Stores.

If you choose File Stores in Task 3, "Configuring High Availability Options", you have to select the File Stores option here to configure them in a shared location in ORACLE_RUNTIME/domain_name/OSB_Cluster/jms. Shared location is required to resume JMS and JTA in a failover scenario.

Task 8   Configuring Managed Servers

On the Managed Servers screen, a new Managed Server for Oracle Service Bus appears in the list of servers. This server was created automatically by the Oracle Service Bus configuration template that you selected in Task 2, "Selecting the Configuration Template".

Perform the following tasks to modify the default Oracle Service Bus Managed Server and create a second Oracle Service Bus Managed Server:

1. Rename the default OSB Managed Server to WLS_OSB1.

2. Click Add to create a new Managed Server, and name it WLS_OSB2.

   Tip:

   The server names recommended here are used throughout this document; if you choose different names, be sure to replace them as needed.

3. Use the information in Table 13-4 to fill in the rest of the columns for each Managed Server.

4. Select OSB-MGD-SVRS-ONLY as the server group for the OSB Servers. Deselect OSB-MGD-SVRS-COMBINED that is selected by default.

5. Click Next.

For more information about the options on the Managed Server screen, see Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.

Table 13-4 Configuring the Oracle Service Bus Managed Servers in the Configuration Wizard

Name	Listen Address	Enable Listen	Listen Port	SSL Listen Port	Enable SSL Port	Administration Port	Server Groups
WLS_SOA1	SOAHOST1	Unchecked	Disabled	7004	Checked	9004	SOA-MGD-SVRS-ONLY
WLS_SOA2	SOAHOST2	Unchecked	Disabled	7004	Checked	9004	SOA-MGD-SVRS-ONLY
WLS_WSM1	SOAHOST1	Unchecked	Disabled	7010	Checked	9003	JRF-MAN-SVR WSMPM-MAN-SVR
WLS_WSM2	SOAHOST2	Unchecked	Disabled	7010	Checked	9003	JRF-MAN-SVR WSMPM-MAN-SVR
WLS_OSB1	SOAHOST1	Unchecked	Disabled	8003	Checked	9007	OSB-MGD-SVRS-ONLY
WLS_OSB2	SOAHOST2	Unchecked	Disabled	8003	Checked	9007	OSB-MGD-SVRS-ONLY

The WLS_SOA Managed Servers appear if you extend an existing Oracle SOA Suite domain with Oracle Service Bus.

Task 9   Configuring a Cluster

In this task, you create a cluster of Managed Servers to which you can target the Oracle Service Bus software.

You also set the Frontend Host property for the cluster, which ensures that, when necessary, WebLogic Server redirects web services callbacks and other redirects to osb.example.com on the load balancer rather than the address in the HOST header of each request.

For more information about the osb.example.com virtual server address, see Configuring Virtual Hosts on the Hardware Load Balancer.

Use the Clusters screen to create a new cluster:

1. Click the Add button.

2. Specify OSB_Cluster in the Cluster Name field.

3. Specify osb.example.com in the Frontend Host field.

4. Specify 0 as the Frontend HTTP Port and 443 as the Frontend HTTPS port.

Note:

By default, server instances in a cluster communicate with one another by using unicast. If you want to change your cluster communications to use multicast, refer to Considerations for Choosing Unicast or Multicast in Administering Clusters for Oracle WebLogic Server.

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

Task 10   Assigning Server Templates

Click Next to continue.

Task 11   Configuring Dynamic Servers

Click Next to continue.

Task 12   Assigning Managed Servers to the Cluster

On the Assign Servers to Clusters screen, assign servers to clusters as follows:

Note that the WLS_SOA Managed Servers appear only if you extend an existing Oracle SOA Suite domain with Oracle Service Bus.

• SOA_Cluster (If you are extending a SOA domain):

  • WLS_SOA1

  • WLS_SOA2

• WSM-PM_Cluster:

  • WLS_WSM1

  • WLS_WSM2

• OSB_Cluster:

  • WLS_OSB1

  • WLS_OSB2

Click Next.

For more information about the options on this screen, see Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Task 13   Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the port number value at 9991, as it was defined during the initial Infrastructure domain creation.

For Coherence licensing information, see Oracle Coherence Products in Oracle Fusion Middleware Licensing Information User Manual.

Task 14   Verifying the Existing Machines

Confirm that the following entries appear:

Name	Node Manager Listen Address
SOAHOST1	SOAHOST1
SOAHOST2	SOAHOST2
ADMINHOST	ADMINVHN

Leave all other fields to their default values.

Click Next.

Task 15   Assigning Servers to Machines

On the Assign Servers to Machines screen, assign servers to machines as follows:

• ADMINHOST:

  • AdminServer

• SOAHOST1

  • WLS_SOA1 (if extending a SOA domain)

  • WLS_WSM1

  • WLS_OSB1

• SOAHOST2:

  • WLS_SOA2 (if extending a SOA domain)

  • WLS_WSM2

  • WLS_OSB2

For more information about the options on this screen, see Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.

Task 16   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain that you are about to extend. Review the details of each item on the screen and verify that the information is correct.

If you need to make any changes, you can go back to any previous screen, either by using the Back button or by selecting the screen in the navigation pane.

Click Update to execute the domain extension.

In the Configuration Progress screen, click Next when it finishes.

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

Task 17   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen shows the following items about the domain you just configured, including:

• Domain Location

• Administration Server URL

Make a note of both these items, because you need them later; you need the domain location to access the scripts used to start the Administration Server, and you need the Administration Server URL to access the WebLogic Remote Console and Oracle Enterprise Manager Fusion Middleware Control.

Click Finish to dismiss the Configuration Wizard.

Task 18   Start the Administration Server

Start the Administration Server to ensure the changes that you have made to the domain have been applied.

After you have completed extending the domain, go to Propagating the Extended Domain to the Domain Directories and Machines.

Table 13-5 summarizes the steps required to propagate the changes to all the domain directories and systems.

After you extend the domain, restart the Administration Server, and propagate the domain to the other hosts, use the following procedure to start the WLS_OSB1 server and validate if the server is configured successfully:

Follow similar steps as in the previous section for WLS_OSB2:

This is controlled by the global property OSB Singleton Components Automatic Migration, which exposed in Enterprise Manager, in the Global Settings section of the Service Bus configuration. When activated, it uses the WebLogic Singleton Framework to guarantee the singleton behavior and automatic migration of these OSB singleton services.

Similar to server or service migration, a database leasing is a requirement for the OSB Singleton Components Automatic Migration to work properly. The OSB Singleton Components Automatic Migration checkbox does not automatically define the leasing datasource, it just marks these applications as singletons.

This OSB global property and the Database Leasing are checked by default for the SOA Enterprise Deployment topologies as long as Enable Automatic Service Migration was selected during the configuration wizard as recommended in this guide.

For cases where Automatic Service Migration was not enabled using the Configuration Wizard, and you define it manually afterwards, you must also check OSB Singleton Components Automatic Migration manually.

To guarantee the appropriate Singleton behavior for OSB:

Verify that the OSB Singleton Components Automatic Migration option is checked:

Verify that the appropriate targeting exists by following these steps:

1. Log into the WebLogic Remote Console.

2. In the Edit Tree, and then click App Deployments.

3. Find the Aggregator Singleton Marker Application. Verify that the value in the Targets column of the table is OSB_Cluster.

Verify that the leasing datasource is defined for the OSB_Cluster:

1. Log into the WebLogic Remote Console.

2. In the Edit Tree, expand Environment, and then click Clusters.

3. Click OSB_Cluster.

4. Click the Migration tab.

5. Verify that Database is selected in the Migration Basis drop-down menu and the leasing datasource Data Source For Automatic Migration is defined.

   If database leasing is not defined, see Setting the Leasing Mechanism and Data Source for an Enterprise Deployment Cluster for instructions to configure it.

Oracle SOA Suite and Oracle Service Bus use the same database, file, and FTP JCA adapters.

You create the required database schemas for these adapters when you use the Oracle Repository Creation Utility before you configure Oracle SOA Suite. The database adapter does not require any configuration at the WebLogic Server resource level.

The required configuration for the other adapters is described in section Enabling High Availability for Oracle File and FTP Adapters.

If you configure Oracle Service Bus as an extension of a SOA domain, you do not need to add to the configuration already performed for the adapters.

If you deploy Oracle Service Bus as an extension to an Oracle Fusion Middleware Infrastructure domain (without Oracle SOA Suite), perform the steps as described in Enabling High Availability for Oracle File and FTP Adapters.

To use IBM WebSphere MQ Connection resources and the MQ Transport in Oracle Service Bus, you must add the MQ client libraries to the classpath.

One option is to copy the required MQ libraries to the following location in the domain home directory:

DOMAIN_HOME/lib

This is also the case for custom assertions and JBoss integration services:

• When you use JBoss initial context factory classes, make sure to include the class and any dependent classes in the DOMAIN_HOME/lib directory.

• Similarly, for custom assertions, create the required jar file with the assertion and add the jar to the DOMAIN_HOME/lib directory.

Further, to use these services in an enterprise deployment, you must add the required libraries to the Administration Server domain home (ASERVER_HOME/lib) and the Managed Server domain home (MSERVER_HOME/lib).

For more information about configuring and developing services for Oracle Service Bus, see Getting Started with the Oracle Service Bus Console in Developing Services with Oracle Service Bus.