1. Enterprise Deployment Guide for Oracle WebCenter Content
  2. Configuring the Enterprise Deployment
  3. Extending the Domain with Oracle SOA Suite

13 Extending the Domain with Oracle SOA Suite

You need to perform certain tasks in order to extend the enterprise deployment domain with the Oracle SOA Suite software.

Parent topic: Configuring the Enterprise Deployment

Variables Used When Configuring Oracle SOA Suite

While extending the domain with Oracle SOA Suite, you will be referencing the directory variables listed in this section.

The values for several directory variables are defined in File System and Directory Variables Used in This Guide.

  • ORACLE_HOME

  • ASERVER_HOME

  • MSERVER_HOME

  • APPLICATION_HOME

  • DEPLOY_PLAN_HOME

  • OHS_DOMAIN_HOME

  • JAVA_HOME

  • ORACLE_RUNTIME

In addition, you'll be referencing the following virtual IP (VIP) address defined in Reserving the Required IP Addresses for an Enterprise Deployment:

  • ADMINVHN

Actions in this chapter will be performed on the following host computers:

  • WCCHOST1

  • WCCHOST2

  • WEBHOST1

  • WEBHOST2

Parent topic: Extending the Domain with Oracle SOA Suite

Support for Dynamic Clusters in Oracle SOA Suite

SOA supports two different topologies: static clusters-based topology and dynamic clusters-based topology. When choosing the dynamic cluster topology, there are some differences with respect to the conventional static clusters configuration.

Static clusters, also called configured clusters, are conventional clusters where you manually configure and add each server instance. A dynamic cluster includes a new "server-template" object that is used to define a centralized configuration for all generated (dynamic) server instances. When you create a dynamic cluster, the dynamic servers are preconfigured and automatically generated for you. This feature enables you to scale up the number of server instances in the dynamic cluster when you need additional server capacity. You can simply start the dynamic servers without having to first manually configure and add them to the cluster.

The steps in this section include instructions to configure the domain for both static or dynamic topologies. The differences between the two types of configurations are listed below:

  • The Configuration Wizard process may differ for each case. For example, you should define server templates for dynamic clusters instead of servers.

  • For dynamic clusters, you should perform the server-specific configurations such as setting the listen address, configuring the upload and staging directories, or configuring the keystores in the server template instead of in the server.

  • Service migration is configured in a different way for dynamic clusters. Dynamic clusters do not use migratable targets, instead the JMS resources are targeted to the cluster. Specific procedure for configuring service migration for dynamic clusters is included in this guide.

Mixed clusters (clusters that contains both dynamic and configured server instances) are not supported in the Oracle WebCenter Content enterprise deployment.

Parent topic: Extending the Domain with Oracle SOA Suite

Synchronizing the System Clocks

Before you extend the domain to include Oracle SOA Suite, verify that the system clocks on each host computer are synchronized.

To verify the time synchronization, query the NTP service by running the ntpstat command on each host.

Sample output:

$ ntpstat
synchronised to NTP server (10.132.0.121) at stratum 3
 time correct to within 42 ms
 polling server every 16 s

Parent topic: Extending the Domain with Oracle SOA Suite

Installing the Software for an Enterprise Deployment

The procedure to install the software for an enterprise deployment is explained in this section.

Parent topic: Extending the Domain with Oracle SOA Suite

Starting the Oracle SOA Suite Installer on WCCHOST1

To start the installation program:

  1. Log in to WCCHOST1.
  2. Go to the directory where you downloaded the installation program.
  3. Launch the installation program by invoking the java executable from the JDK directory on your system, as shown in the following example:
    JAVA_HOME/bin/java -d64 -jar Installer File Name

    Be sure to replace the JDK location in these examples with the actual JDK location on your system.

    Replace Installer File Name with the name of the actual installer file for your product listed in Identifying and Obtaining Software Distributions for an Enterprise Deployment.

When the installation program appears, you are ready to begin the installation.

Parent topic: Installing the Software for an Enterprise Deployment

Navigating the Installation Screens

The installation program displays a series of screens, in the order listed in the following table.

If you need additional help with any of the installation screens, click the screen name.

Screen Description

Welcome

This screen introduces you to the product installer.

Auto Updates

Use this screen to automatically search My Oracle Support for available patches or automatically search a local directory for patches that you have already downloaded for your organization.

Installation Location

Use this screen to specify the location of your Oracle home directory.

For more information about Oracle Fusion Middleware directory structure, see Selecting Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.

Installation Type

Use this screen to select the type of installation and consequently, the products and feature sets you want to install.

  • Select SOA Suite

Prerequisite Checks

This screen verifies that your system meets the minimum necessary requirements.

If there are any warning or error messages, you can refer to one of the documents in the Roadmap for Verifying Your System Environment section in Oracle Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure.

Installation Summary

Use this screen to verify the installation options that you selected.

Click Install to begin the installation.

Installation Progress

This screen allows you to see the progress of the installation.

Click Next when the progress bar reaches 100% complete.

Installation Complete

Review the information on this screen, then click Finish to dismiss the installer.

Parent topic: Installing the Software for an Enterprise Deployment

Installing Oracle SOA Suite on the Other Host Computers

If you have configured a separate shared storage volume or partition for the products mount point and ORACLE_HOME on WCCHOST2, then you must also perform the product installation on WCCHOST2.

See Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.

To install the software on the other host computers in the topology, log in to each host, and use the instructions in Starting the Infrastructure Installer on WCCHOST1 and Navigating the Infrastructure Installation Screens to create the Oracle home on the appropriate storage device.

Parent topic: Installing the Software for an Enterprise Deployment

Verifying the Installation

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

Parent topic: Installing the Software for an Enterprise Deployment

Reviewing the Installation Log Files

Review the contents of the installation log files to make sure that no problems were encountered. For a description of the log files and where to find them, see Understanding Installation Log Files in Oracle Fusion Middleware Installing Software with the Oracle Universal Installer.

Checking the Directory Structure

The contents of your installation vary based on the options that you select during the installation.

The addition of Oracle SOA Suite adds the following directory and sub-directories. Use the ls --format=single-column command to verify the directory structure. 

ls --format=single-column /u01/oracle/products/fmw/soa

bam
bin
bpm
common
integration
jlib
modules
plugins
readme.txt
reports
soa

For more information about the directory structure you should see after installation, see What are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware.

Viewing the Contents of Your Oracle Home

You can also view the contents of your Oracle home by using the viewInventory script. See Viewing the contents of an Oracle home in Installing Software with the Oracle Universal Installer.

Creating the Oracle SOA Suite Database Schemas

Before you can configure an Oracle SOA Suite domain, you must install the required schemas in a certified database for use with this release of Oracle Fusion Middleware.

Parent topic: Extending the Domain with Oracle SOA Suite

Starting the Repository Creation Utility (RCU)

To start the Repository Creation Utility (RCU):

  1. Navigate to the ORACLE_HOME/oracle_common/bin directory on your system.
  2. 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 /u01/oracle/products/jdk:

    On UNIX operating systems:

    export JAVA_HOME=/u01/oracle/products/jdk
  3. Start RCU:

    On UNIX operating systems:

    ./rcu

    Note:

    If your database has Transparent Data Encryption (TDE) enabled, and you want to encrypt your tablespaces that are created by the RCU, provide the -encryptTablespace true option when you start RCU.

    This defaults the appropriate RCU GUI Encrypt Tablespace checkbox selection on the Map Tablespaces screen without further effort during the RCU execution. See Encrypting Tablespaces in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

Parent topic: Creating the Oracle SOA Suite Database Schemas

Navigating the RCU Screens to Create the Schemas

Schema creation involves the following tasks:

Task 1   Introducing RCU

Click Next.

Task 2   Selecting a Method of Schema Creation

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 generates a SQL script, which can be provided to your database administrator to create the required schema. See Understanding System Load and Product Load in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

Click Next.

Task 3   Providing Database Connection Details

Provide the database connection details for RCU to connect to your database.

  1. In the Host Name field, enter the SCAN address of the Oracle RAC Database.

  2. Enter the Port number of the RAC database scan listener, for example 1521.

  3. Enter the RAC Service Name of the database.

  4. Enter the User Name of a user that has permissions to create schemas and schema objects, for example SYS.

  5. Enter the Password of the user name that you provided in step 4.

  6. If you have selected the SYS user, ensure that you set the role to SYSDBA.

  7. Click Next to proceed, then click OK on the dialog window confirming that connection to the database was successful.

Task 4   Specifying a Custom Prefix and Selecting Schemas

Choose Select existing prefix, and then select the prefix you used when you created the initial domain.

From the list of schemas, select the SOA Suite schema. This automatically selects SOA Infrastructure. In addition, the following dependent schemas have already been installed with the Infrastructure and are grayed out:

  • Common infrastructure Services

  • Oracle Platform Security Services

  • User Messaging Service

  • Audit Services

  • Audit Services Append

  • Audit Services Viewer

  • Metadata Services

  • Weblogic Services

  • Oracle WebCenter Content Server - Complete

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.

Tip:

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.

Click Next to proceed, then click OK on the dialog window to confirm that prerequisite checking for schema creation was successful.

Task 5   Specifying Schema Passwords

Specify how you want to set the schema passwords on your database, then specify and confirm your passwords. Ensure that the complexity of the passwords meet the database security requirements before you continue. RCU proceeds at this point even if you do not meet the password polices. Hence, perform this check outside RCU itself.

Tip:

You must make a note of the passwords that you set on this screen; you need them later on during the domain creation process.

Click Next.

Task 6   Specifying Custom Variables

Specify the custom variables for the SOA Infrastructure schema.

For the enterprise deployment topology, enter MEDIUM for the Database Profile custom variable; enter NO for the Healthcare Integration variable. See About the Custom Variables Required for the SOA Suite Schemas in Installing and Configuring Oracle SOA Suite and Business Process Management.

Click Next.

Task 7   Verifying the Tablespaces for the Required Schemas

On the Map Tablespaces screen, review the information, and then click Next to accept the default values.

Click OK in the confirmation dialog box.

Click Next.

Task 8   Creating Schemas

Review the summary of the schemas to be loaded, and click Create to complete schema creation.

Note:

If failures occurred, review the listed log files to identify the root cause, resolve the defects, and then use RCU to drop and recreate the schemas before you continue.

Task 9   Reviewing Completion Summary and Completing RCU Execution

When you reach the Completion Summary screen, verify that all schema creations have been completed successfully, and then click Close to dismiss RCU.

Parent topic: Creating the Oracle SOA Suite Database Schemas

Verifying Schema Access

Verify schema access by connecting to the database as the new schema users created by the RCU. Use SQL*Plus or another utility to connect, and provide the appropriate schema names and passwords entered in the RCU.

For example:

./sqlplus

SQL*Plus: Release 12.1.0.2.0 Production on Wed Aug 31 05:41:31 2016

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Enter user-name: FMW1221_SOAINFRA
Enter password: soainfra_password

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production 
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options 

SQL>

Parent topic: Creating the Oracle SOA Suite Database Schemas

Configuring SOA Schemas for Transactional Recovery

After you have installed the Oracle SOA Suite schemas successfully, use the procedure in this section to configure the schemas for transactional recovery.

This procedure sets the appropriate database privileges so that the Oracle WebLogic Server transaction manager can query the schemas for transaction state information and issue the appropriate commands, such as commit and rollback, during recovery of in-flight transactions after a WebLogic Server is unexpectedly unavailable.

These privileges should be granted to the owner of the SOAINFRA schema, which you defined when you created the schemas with the RCU.

To configure the SOA schemas for transactional recovery privileges:

  1. Log on to SQL*Plus as a user with sysdba privileges. For example: 
    sqlplus "/ as sysdba"
  2. Enter the following commands:
    SQL> Grant select on sys.dba_pending_transactions to soa_schema_prefix_soainfra;

Grant succeeded.
 
SQL> Grant force any transaction to soa_schema_prefix_soainfra;
 
Grant succeeded.
 
SQL>

Parent topic: Creating the Oracle SOA Suite Database Schemas

Extending the Enterprise Deployment Domain with Oracle SOA Suite

Perform the following tasks to extend the existing enterprise deployment domain with the Oracle SOA Suite software.

Note:

For an improved footprint and to optimize startup, only core adapters are targeted to the SOA cluster (MFT Cluster if you are configuring MFT) after the Configuration Wizard session. You must target the second-tier adapters manually, if required. See Targeting Adapters Manually.

Extending the domain involves the following tasks:

Parent topic: Extending the Domain with Oracle SOA Suite

Starting the Configuration Wizard

Start the Configuration Wizard as the first step to extend the existing enterprise deployment domain.

Note:

If you added any customizations directly to the start scripts in the domain, those are overwritten by the configuration wizard. To customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverridesLate.sh and configure it, for example, add custom libraries to the WebLogic Server classpath, specify Additional JAVA command line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when using the pack and unpack commands.

To start the Configuration Wizard:

  1. From the WebLogic Server Console, stop any managed servers that are modified by this domain extension. Managed Servers that are not effected can remain on-line.
  2. For any managed servers to be modified, verify that the managed server shutdown has completed.
  3. Stop the Administration Server once all managed servers are in a steady state.
  4. Navigate to the following directory and start the WebLogic Server Configuration Wizard.
    cd ORACLE_HOME/oracle_common/common/bin
./config.sh

Parent topic: Extending the Enterprise Deployment Domain with Oracle SOA Suite

Navigating the Configuration Wizard Screens to Extend the Domain with Oracle SOA Suite

Follow the instructions in these sections to extend the domain for Oracle SOA Suite, with static or dynamic clusters.

Parent topic: Extending the Enterprise Deployment Domain with Oracle SOA Suite

Extending the Domain with Static Clusters

Follow the instructions in this section to extend the domain for Oracle SOA Suite, with static clusters.

Note:

This procedure assumes that you are extending an existing domain. If your needs do not match the instructions given in the procedure, ensure that you make your selections accordingly, or refer to the supporting documentation for additional details.

Domain creation and configuration includes the following tasks:

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 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 Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Task 2   Selecting the Configuration Template

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

  • Oracle SOA Suite - 12.2.1.3.0 [soa]

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

    • Oracle Enterprise Manager - 12.2.1.3.0[em]

    • Oracle WSM Policy Manager - 12.2.1.3.0[oracle_common]

    • Oracle JRF - 12.2.1.3.0[oracle_common]

    • WebLogic Coherence Cluster Extension - 12.2.1.3.0[wlserver]

    And the following template should also be selected, because you already configured WebCenter Content:

    • Oracle Universal Content Management - Content Server - 12.2.1.3.0[wccontent]

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

Task 3   Configuring High Availability Options

This screen appears for the first time when you create a cluster that uses Automatic Service Migration or JDBC stores or both. After you select HA Options for a cluster, all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply HA options (that is, the Configuration Wizard creates the JDBC stores and configures ASM for them).

On the High Availability Options screen:

  • Select Enable Automatic Service Migration with Database Basis.

  • Set JTA Transaction Log Persistence to JDBC TLog Store.

  • Set JMS Server Persistence to JMS JDBC Store.

Note:

Oracle recommends that you use JDBC stores, which leverage the consistency, data protection, and high availability features of an oracle database and makes resources available for all the servers in the cluster. So, the Configuration Wizard steps assume that the JDBC persistent stores are used along with Automatic Service Migration.

When you choose JDBC persistent stores, additional unused File Stores are automatically created but are not targeted to your clusters. Ignore these File Stores.

If, for any reason, you want to use Files Stores, you can retain the default values for TLOGs and JMS persistent store options in this screen and configure them in a shared location later. See Task 9, "Selecting Advanced Configuration". Shared location is required to resume JMS and JTA in a failover scenario.

You can also configure TLOGs and JMS persistent stores manually in a post step. For information about the differences between JDBC and Files Stores, and for specific instructions to configure them manually, see Using Persistent Stores for TLOGs and JMS in an Enterprise Deployment.

Click Next.

Task 4   Specifying the Database Configuration Type

On the Database Configuration Type screen, select RCU Data.

All fields are prepopulated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain. In the RCU Data screen:

  • Verify that Vendor is Oracle and 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 operation is successful. 

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.

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

Task 5   Specifying JDBC Component Schema Information

On the JDBC Component Schema screen, select all the SOA schemas in the table.

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

Element Description and Recommended Value

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

In the ONS Host field, enter the SCAN address for the Oracle RAC database.

In the Port field, enter the ONS Remote port (typically, 6200).

These values are required when connecting to Oracle 11g databases but optional when connecting to Oracle database 12c and higher. If you are using an Oracle 12c database, the ONS list is automatically provided from the database to the driver.

Enable Fan

Verify that the Enable Fan check box is selected, so that the database can receive and process FAN events.

Task 7   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 Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Task 8   Keystore

Use this screen to specify details about the keystore to be used in the domain.

For a typical enterprise deployment, you can leave the default values.

See Keystore in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Task 9   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/SOA_Cluster/jms. Shared location is required to resume JMS and JTA in a failover scenario.

Task 10   Configuring Managed Servers

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

Perform the following tasks to modify the default Oracle SOA Suite Managed Server and create a second Oracle SOA Suite Managed Server:

  1. Rename the default Oracle SOA Suite Managed Server to WLS_SOA1.

  2. Click Add to create a new Oracle SOA Suite Managed Server, and name it WLS_SOA2.

    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 the following table to fill in the rest of the columns for each Oracle SOA Suite Managed Server.

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

Server Name Listen Address Listen Port Enable SSL SSL Listen Port Server Groups

WLS_SOA1

WCCHOST1

8001

No

Disabled

SOA-MGD-SVRS-ONLY, WSMPM-MAN-SVR, WSM-CACHE-SVR, JRF-MAN-SVR

WLS_SOA2

WCCHOST2

8001

No

Disabled

SOA-MGD-SVRS-ONLY, WSMPM-MAN-SVR, WSM-CACHE-SVR, JRF-MAN-SVR
Task 11   Configuring a Cluster

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

Use the Clusters screen to create a new cluster:

  1. Click the Add button.

  2. Specify SOA_Cluster in the Cluster Name field.

  3. From the Dynamic Server Groups drop-down list, select Unspecified.

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 Oracle Fusion Middleware Administering Clusters for Oracle WebLogic Server.

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

Task 12   Assigning Server Templates

Click Next to continue.

Task 13   Configuring Dynamic Servers

Verify that all dynamic server options are disabled for clusters that are to remain as static clusters. To configure dynamic servers:

  1. Confirm that the Dynamic Cluster, Calculated Listen Port, and Calculated Machine Names checkboxes on this screen are unchecked.

  2. Confirm the Server Template selection is Unspecified.

  3. Click Next.

Task 14   Assigning Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign WLS_SOA1 and WLS_SOA2 to the new cluster SOA_Cluster:

  1. In the Clusters pane, select the cluster to which you want to assign the servers; in this case, SOA_Cluster.

  2. In the Servers pane, assign WLS_SOA1 to SOA_Cluster by doing one of the following:

    • Click WLS_SOA1 Managed Server once to select it, and then click on the right arrow to move it beneath the selected cluster in the Clusters pane.

    • Double-click WLS_SOA1 to move it beneath the selected cluster in the clusters pane.

  3. Repeat to assign WLS_SOA2 to SOA_Cluster.

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

Task 15   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 16   Verifying the Existing Machines

Under the Unix Machine tab, verify the names of the machines you created when creating the initial Infrastructure domain.

Click Next to proceed.

Task 17   Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign the Oracle SOA Suite Managed Servers you just created to the corresponding machines in the domain.

Assign WLS_SOA1 to WCCHOST1, and assign WLS_SOA2 to WCCHOST2.

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

Task 18   Configuring Virtual Targets

Click Next.

Task 19   Configuring Partitions

Click Next.

Task 20   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains 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 if you need to make any changes, 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 Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Task 21   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen shows the following items about the domain that 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 Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control.

Click Finish to dismiss the Configuration Wizard.

If the Admin Server was running during the domain extension process, restart the server before you continue.

Task 22   Start the Administration Server

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

After you complete extending the domain with static clusters, go to Targeting Adapters Manually.

Extending the Domain with Dynamic Clusters

Follow the instructions in this section to extend the domain for Oracle SOA Suite, with dynamic clusters.

Note:

This procedure assumes that you are extending an existing domain. If your needs do not match the instructions given in the procedure, ensure that you make your selections accordingly, or refer to the supporting documentation for additional details.

Domain creation and configuration includes the following tasks.

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 you created when you created the initial domain.

Do not enter the value of the MSERVER_HOME variable, which represents the location of the Managed Servers domain directory.

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

Tip:

More information about the other options on this screen can be found in Configuration Type in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Task 2   Selecting the Configuration Template

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

  • Oracle SOA Suite - 12.2.1.3.0 [soa]

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

    • Oracle Enterprise Manager - 12.2.1.3.0 [em]

    • Oracle WSM Policy Manager - 12.2.1.3.0 [oracle_common]

    • Oracle JRF - 12.2.1.3.0 [oracle_common]

    • WebLogic Coherence Cluster Extension - 12.2.1.3.0 [wlserver]

    And the following template should also be selected, because you already configured WebCenter Content:

    • Oracle Universal Content Management - Content Server - 12.2.1.3.0 [wccontent]

Tip:

More information about the options on this screen can be found in Templates in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Task 3   Specifying the Database Configuration Type

On the Database Configuration Type screen, select RCU Data.

All fields are prepopulated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain. On the RCU Data screen:

  • Verify that Vendor is Oracle and 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 operation is successful: 

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.

Click Next.

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.

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

Task 4   Specifying JDBC Component Schema Information

On the JDBC Component Schema screen, select all the SOA schemas in the table.

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

Element Description and Recommended Value

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

In the ONS Host field, enter the SCAN address for the Oracle RAC database.

In the Port field, enter the ONS Remote port (typically, 6200).

These values are required when connecting to Oracle 11g databases but optional when connecting to Oracle database 12c and higher. If you are using an Oracle 12c database, 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 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.

Tip:

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

Task 7   Keystore

Use this screen to specify details about the keystore to be used in the domain.

For a typical enterprise deployment, you can leave the default values.

See Keystore in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Task 8   Selecting Advanced Configuration

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

Task 9   Configuring Managed Servers

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

SOA Static Managed Server definitions are not needed for dynamic cluster configuration. To remove the default Managed Server, complete the following steps:

  1. Click the soa_server1 managed server and click Delete.

  2. Click Next.

Task 10   Configuring a Cluster

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

Use the Clusters screen to create a new cluster:

  1. Click the Add button.

  2. Specify SOA_Cluster in the Cluster Name field.

  3. From the Dynamic Server Groups drop-down list, select SOA-DYN-CLUSTER-ONLY.

Note:

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

Tip:

More information about the options on this screen can be found in Clusters in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Task 11   Assigning Server Templates

To configure a template, complete the following steps:

  1. Verify that soa-server-template is selected in the Name field.

  2. Specify 8000 in the Listen Port field.

  3. Leave the Enable SSL option unchecked.

  4. Click Next.

Task 12   Configuring Dynamic Servers

Use the Dynamic Clusters screen to configure the required clusters:

  1. Verify SOA_Cluster is listed in the Cluster Name field.

  2. Specify WLS_SOA in the Server Name Prefix field.

  3. From the Server Template drop-down list, select soa-server-template.

  4. Specify 2 in the Dynamic Cluster Size field.

  5. Specify WCCHOST* in the Machine Name Match Expression field and select Calculated Machine Names.

    Note:

    The dynamic cluster Calculated Machine Names and Machine Name Match Expression attributes control how server instances in a dynamic cluster are assigned to a machine. If the Calculated Machine Names attribute is set to False, the dynamic servers are not assigned to a machine. If the Calculated Machine Names attribute is set to True, the Machine Name Match Expression attribute is used to select the set of machines that is used for the dynamic servers. If the Machine Name Match Expression attribute is not set, all the machines in the domain are selected. Assignments are made by using a round robin algorithm.

  6. Select Calculated Listen Ports and Dynamic Cluster fields.

    Note:

    Dynamic clusters with the Calculated Listen Port option selected have incremental port numbers for each dynamic managed server that is created automatically: dynamic server 1 will use Listen Port+1, dynamic server 2 will use Listen Port+2.

    Since the Listen Port configured is 8000 and calculated ports is checked, SOA dynamic servers use the following port numbers:

    • WLS_SOA1 server listens in 8001 port

    • WLS_SOA2 server listens in 8002 port

  7. Click Next.

Note:

The Configuration Wizard does not allow you to specify a specific listen address for dynamic servers. For information about setting a specific listen address for WebLogic servers that are members of a dynamic cluster, see Configuring Listen Addresses in Dynamic Cluster Server Templates.

Task 13   Assign Servers to Clusters

This screen appears during dynamic cluster configurations when static configured clusters and managed servers exist, even if the current extension does not include any new static servers.

For the SOA extension with dynamic clusters, no changes are needed.

Click Next.

Task 14   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.

Note:

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

Task 15   Verifying the Existing Machines

Under the Unix Machine tab, verify the names of the machines that you created when creating the initial Infrastructure domain.

Click Next.

Task 16   Assigning Servers to Machines

Click Next.

Task 17   Virtual Targets

Click Next.

Task 18   Partitions

Click Next.

Task 19   Reviewing Your Configuration Specifications and Configuring the Domain

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

Tip:

More information about the options on this screen can be found in Configuration Summary in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Task 20   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen shows the following items about the domain that 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 Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control.

Click Finish to dismiss the configuration wizard.

If the Admin Server was running during the domain extension process, restart the server before you continue.

Task 21   Start the Administration Server

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

Targeting Adapters Manually

Only core adapters are targeted to the SOA cluster after you run the Configuration Wizard. You must target second-tier adapters manually, on a need basis.

The following second-tier adapters have to be targeted manually:

Note:

Some of these adapters may not be available with the default installation. See Oracle Technology Network for Adapter availability.

  • MSMQAdapter

  • SocketAdapter

  • OracleBamAdapter

  • CoherenceAdapter

  • SAPAdapter

  • SiebelAdapter

  • ERPAdapter

  • Oracle SalesCloudAdapter

  • RightNowAdapter

  • EloquaAdapter

  • NetSuiteAdapter

  • LdapAdapter

  • JDEWorldAdapter

To target a second-tier adapter manually:

  1. Navigate to and log into the Oracle WebLogic Server Administration Console. For example: http://ADMINVHN:7001/console.

    Note:

    If you have already configured web tier, use http://admin.example.com/console.

  2. In the left pane of the console, click Deployments.
  3. Locate and click the name of the adapter in the Summary of the Deployments table.
  4. Click Lock & Edit.
  5. In the Targets tab, select SOA_Cluster.

    Note:

    If you are deploying MFT, select MFT_Cluster as the target.

  6. Click Save.
  7. Activate the changes.
  8. In the left pane of the console, click Deployments and verify that the adapter is in the Active state.

Parent topic: Extending the Enterprise Deployment Domain with Oracle SOA Suite

Propagating the Extended Domain to the Domain Directories and Machines

After you have extended the domain with the Oracle WebCenter Content instances, and you have restarted the Administration Server on WCCHOST1, you must then propagate the domain changes to the domain directories and machines.

Table 13-1 summarizes the steps required to propagate the changes to all the domain directories and machines.

Note that there is no need to propagate the updated domain to the WEBHOST1 and WEBHOST2 machines because there are no changes to the Oracle HTTP Server instances on those host computers.

Table 13-1 Summary of Tasks Required to Propagate the Domain Changes to Domain Directories and Machines

Task Description More Information

Pack up the Extended Domain on WCCHOST1

Use the pack command to create a new template JAR file that contains the new Oracle SOA Suite Managed Servers configuration.

When you pack up the domain, create a template JAR file called wccdomaintemplateExtSOA.jar.

Packing Up the Extended Domain on WCCHOST1

Unpack the Domain in the Managed Servers directory on WCCHOST1

Unpack the template JAR file in the Managed Servers directory on WCCHOST1 local storage.

Unpacking the Domain in the Managed Servers Domain Directory on WCCHOST1

Unpack the Domain on WCCHOST2

Unpack the template JAR file in the Managed Servers directory on the WCCHOST2local storage.

Unpacking the Domain on WCCHOST2

Parent topic: Extending the Domain with Oracle SOA Suite

Packing Up the Extended Domain on WCCHOST1

Use the following steps to create a template JAR file that contains the domain configuration information:

  1. Log in to WCCHOST1 and run the pack command to create a template JAR file as follows:
    cd ORACLE_COMMON_HOME/common/bin
 
./pack.sh -managed=true \ 
          -domain=ASERVER_HOME \ 
          -template=full_path/wccdomaintemplateExtSOA.jar \
          -template_name=wcc_domain_template_extension_soa \
	  -log=/tmp/pack_soa.log \
	  -log_priority=debug

    In this example:

    • Replace ASERVER_HOME with the actual path to the domain directory that you created on the shared storage device.

    • Replace full_path with the complete path to the directory where you want the template jar file saved.

    • wccdomaintemplateExtSOA.jar is a sample name for the JAR file that you are creating, which contains the domain configuration files, including the configuration files for the Oracle HTTP Server instances.

    • wcc_domain_template_extension_soa is the name assigned to the domain template file.

  2. Make a note of the location of the template JAR file that you just created with the pack command.

    Tip:

    For more information about the pack and unpack commands, see Overview of the Pack and Unpack Commands in Oracle Fusion Middleware Creating Templates and Domains Using the Pack and Unpack Commands.

Parent topic: Propagating the Extended Domain to the Domain Directories and Machines

Unpacking the Domain in the Managed Servers Domain Directory on WCCHOST1

To copy the updated domain configuration information from the Administration Server domain directory to the Managed Servers domain directory:

  1. Log in to WCCHOST1 if you haven't already.
  2. If you haven't already, create the recommended directory structure for the Managed Server domain on the WCCHOST1 local storage device.
  3. Run the unpack command to unpack the template in the domain directory onto the local storage, as follows:
    cd ORACLE_COMMON_HOME/common/bin

./unpack.sh -domain=MSERVER_HOME \
    -overwrite_domain=true \
    -template=/full_path/wccdomaintemplateExtSOA.jar \
    -log_priority=DEBUG \
    -log=/tmp/unpack.log \
    -app_dir=APPLICATION_HOME

    Note:

    The -overwrite_domain option in the unpack command allows you to unpack a managed server template into an existing domain and existing applications directories. For any file that is overwritten, a backup copy of the original is created. If any modifications had been applied to the start scripts and ear files in the managed server domain directory, they must be restored after this unpack operation.

    Additionally, to customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverridesLate.sh and configure it to, for example, add custom libraries to the WebLogic Server classpath, specify additional JAVA command-line options for running the servers, or specify additional environment variables. Any customizations that you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when you use the pack and unpack commands.

    In this example:

    • Replace MSERVER_HOME with the complete path to the domain home to be created on the local storage disk. This is the location where the copy of the domain is unpacked.

    • Replace /full_path/wccdomaintemplateExtSOA.jar with the complete path and file name of the domain template jar file that you created when you ran the pack command to pack up the domain on the shared storage device.

    • Replace APPLICATION_HOME with the complete path to the applications directory for the domain on shared storage. See File System and Directory Variables Used in This Guide

    Tip:

    For more information about the pack and unpack commands, see Overview of the Pack and Unpack Commands in Oracle Fusion Middleware Creating Templates and Domains Using the Pack and Unpack Commands.

  4. Change directory to the newly created MSERVER_HOME directory and verify that the domain configuration files were copied to the correct location on the WCCHOST1 local storage device.

Parent topic: Propagating the Extended Domain to the Domain Directories and Machines

Unpacking the Domain on WCCHOST2

This procedure assumes you have copied the file that you created earlier in a location that is accessible from both WCCHOST1 and WCCHOST2; such as the ASERVER_HOME directory, which is located on the shared storage filer:

  1. Log in to WCCHOST2

  2. If you haven't already, create the recommended directory structure for the Managed Server domain on the WCCHOST2 storage device.

    Use the examples in File System and Directory Variables Used in This Guide as a guide.

  3. Make sure the wccdomaintemplateExtSOA.jar accessible to WCCHOST2.

    For example, if you are using a separate shared storage volume or partition for WCCHOST2, then copy the template to the volume or partition mounted to WCCHOST2.

  4. Run the unpack command to unpack the template in the domain directory onto the local storage, as follows: 

    cd ORACLE_COMMON_HOME/common/bin

./unpack.sh -domain=MSERVER_HOME \
            -overwrite_domain=true \
            -template=/full_path/wccdomaintemplateExtSOA.jar \ 
            -log_priority=DEBUG \
            -log=/tmp/unpack.log \
            -app_dir=APPLICATION_HOME

    Note:

    The -overwrite_domain option in the unpack command allows unpacking a managed server template into an existing domain and existing applications directories. For any file that is overwritten, a backup copy of the original is created. If any modifications had been applied to the start scripts and ear files in the managed server domain directory, they must be restored after this unpack operation.

    Additionally, to customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverridesLate.sh and configure it to, for example, add custom libraries to the WebLogic Server classpath, specify additional JAVA command line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when using the pack and unpack commands.

    In this example:

    • Replace MSERVER_HOME with the complete path to the domain home to be created on the local storage disk. This is the location where the copy of the domain will be unpacked.

    • Replace /full_path/wccdomaintemplateExtSOA.jar with the complete path and file name of the domain template jar file that you created when you ran the pack command to pack up the domain on the shared storage device.

    • Replace APPLICATION_HOME with the complete path to the Application directory for the domain on shared storage. See File System and Directory Variables Used in This Guide.

    Tip:

    For more information about the pack and unpack commands, see Overview of the Pack and Unpack Commands in Oracle Fusion Middleware Creating Templates and Domains Using the Pack and Unpack Commands.

  5. Change directory to the newly created MSERVER_HOME directory and verify that the domain configuration files were copied to the correct location on the WCCHOST2 local storage device.

Parent topic: Propagating the Extended Domain to the Domain Directories and Machines

Updating the NodeManager Configuration After Unpacking the Domain

When extending a domain, the nodemanager.properties file in MSERVER_HOME may be overwritten with some values from the nodemanager.properties file for ASERVER_HOME. Specifically, the ListenAddress and/or CustomIdentityAlias values can be reset.

Notes::

For the MSERVER_HOME/nodemanager/nodemanager.properties file on each host:
  1. Verify the correct ListenAddress parameter value and reset it, if required.
    grep ListenAddress MSERVER_HOME/nodemanager/nodemanager.properties
  2. Confirm the list of configured Identity Aliases from the domain configuration file as a reference for the next command.
    grep server-private-key-alias ASERVER_HOME/config/config.xml | sort | uniq

    Note:

    When using Dynamic Clusters, this listing will present only the ADMINVHN and wildcard certificate identity aliases.

    Use the appropriate host-specific certificate identity aliases when updating the nodemanger.properties CustomIdentityAlias property in the next instruction.

  3. Verify the current nodemanager.properties CustomIdentityAlias parameter value matches the alias for the host.
    grep CustomIdentityAlias MSERVER_HOME/nodemanager/nodemanager.properties
  4. Reset the CustomIdentityAlias parameter value to the correct alias string appropriate for the current host, if required.
  5. Restart the nodemanager process:
    kill `ps -eaf | grep weblogic.NodeManager | grep MSERVER_HOME | grep -v grep | awk '{print $2}' `
nohup MSERVER_HOME/bin/startNodeManager.sh > MSERVER_HOME/nodemanager/nodemanager.out 2>&1 &
  6. Stop and restart the AdminServer once all node managers are appropriately configured and online.

Note:

For more information about the CustomIdentityAlias parameter, see Configuring Node Manager to Use the Custom Keystores.

Parent topic: Extending the Domain with Oracle SOA Suite

Modifying the Upload and Stage Directories to an Absolute Path in an Enterprise Deployment

After you configure the domain and unpack it to the Managed Server domain directories on all the hosts, verify and update the upload and stage directories for Managed Servers in the new clusters. Also, update the upload directory for the AdminServer to have the same absolute path instead of relative, otherwise deployment issues can occur. If you implement dynamic clusters, the configuration of the server template assigned to each newly added cluster should be verified and updated, otherwise, verify and update every statically-defined Managed Server for the newly added clusters.

Note:

This option is applicable only for static clusters.

This step is necessary to avoid potential issues when you perform remote deployments and for deployments that require the stage mode.

To update the directory paths for the Deployment Stage and Upload locations, complete the following steps:

  1. Log in to the Oracle WebLogic Server Administration Console.

  2. In the left navigation tree, expand Domain, and then Environment.

  3. Click Lock & Edit.

  4. Navigate to and edit the appropriate objects for your cluster type.

    1. For Static Clusters, navigate to Servers and click the name of the Managed Server you want to edit.

    2. For Dynamic Clusters, navigate to Clusters > Server Templates, and click on the name of the server template to be edited.

  5. For each new Managed Server or Server Template to be edited:

    1. Click the Configuration tab, and then click the Deployment tab.

    2. Verify that the Staging Directory Name is set to the following: 

      MSERVER_HOME/servers/server_or_template_name/stage

      Replace MSERVER_HOME with the full path for the MSERVER_HOME directory.

      If you use static clusters, update with the correct name of the Managed Server that you are editing.

      If you use dynamic clusters, leave the template name intact. For example: /u02/oracle/config/domains/wccedg_domain/servers/XYZ-server-template/stage

    3. Update the Upload Directory Name to the following value: 

      ASERVER_HOME/servers/AdminServer/upload

      Replace ASERVER_HOME with the directory path for the ASERVER_HOME directory.

    4. Click Save.

    5. Return to the Summary of Servers or Summary of Server Templates screen as applicable.

  6. Repeat the previous steps for each of the new managed servers or dynamic cluster server templates.

  7. Navigate to and update the Upload Directory Name value for the AdminServer:

    1. Navigate to Servers, and select the AdminServer.

    2. Click the Configuration tab, and then click the Deployment Tab.

    3. Verify that the Staging Directory Name is set to the following absolute path:

      ASERVER_HOME/servers/AdminServer/stage

    4. Update the Upload Directory Name to the following absolute path:

      ASERVER_HOME/servers/AdminServer/upload

      Replace ASERVER_HOME with the directory path for the ASERVER_HOME directory.

    5. Click Save.

  8. When you have modified all the appropriate objects, click Activate Changes.

  9. Restart all Managed Servers for the changes to take effect.

Note:

If you continue directly with further domain configurations, a restart to enable the stage and upload directory changes is not strictly necessary at this time.

Parent topic: Extending the Domain with Oracle SOA Suite

Configuring Listen Addresses When Using Dynamic Clusters

The default configuration for dynamic managed servers in dynamic clusters is to listen on all available network interfaces. In most cases, the default configuration may be undesirable. To limit the listen address to a specific address when you use dynamic clusters, see Configuring Listen Addresses in Dynamic Cluster Server Templates. Reverify the test URLs that are provided in the previous sections after you change the listen address and restart the clustered managed servers.

Parent topic: Extending the Domain with Oracle SOA Suite

Starting and Validating the WLS_SOA1 Managed Server

Now that you have extended the domain, started the Administration Server, and propagated the domain to the other hosts, you can start the newly configured Oracle SOA Suite Managed Servers.

This process involves three tasks as described in the following sections.

Parent topic: Extending the Domain with Oracle SOA Suite

Starting the WLS_SOA1 Managed Server

To start the WLS_SOA1 Managed Server:

  1. Enter the following URL into a browser to display the Fusion Middleware Control login screen:
    http://ADMINVHN:7001/em

    Note:

    If you have already configured web tier, use http://admin.example.com/console.

  2. Sign in to the Fusion Middleware Control by using the administrator's account. For example: weblogic_wcc.
  3. In the Target Navigation pane, expand the domain to view the Managed Servers in the domain.
  4. Select only the WLS_SOA1 Managed Server and click Start Up on the Oracle WebLogic Server toolbar.

    Note:

    SOA Servers depend on the policy access service to be functional. This implies that the WSM-PM Managed Servers in the domain need to be up and running and reachable before the SOA servers are started.

  5. When the startup operation is complete, navigate to the Domain home page and verify that the WLS_SOA1 Managed Server is up and running.

Parent topic: Starting and Validating the WLS_SOA1 Managed Server

Adding the SOAAdmin Role to the Administrators Group

Before you validate the Oracle SOA Suite configuration on the WLS_SOA1 Managed Server, add the SOAAdmin administration role to the enterprise deployment administration group (WCCAdministrators).

To perform this task, refer to Configuring Roles for Administration of an Enterprise Deployment.

Parent topic: Starting and Validating the WLS_SOA1 Managed Server

Validating the Managed Server by Logging in to the SOA Infrastructure

After you add the SOAAdmin role to the SOA Administrators group, you can then validate the configuration of the Oracle SOA Suite software on the WLS_SOA1 Managed Server as follows:

  1. Use your web browser to navigate to the following URL:
    http://WCCHOST1:8001/soa-infra/
  2. Log in by using the enterprise deployment administrator user credentials (weblogic_wcc).

    You should see a web page with the following title:

    Welcome to the Oracle SOA Platform on WebLogic

Parent topic: Starting and Validating the WLS_SOA1 Managed Server

Starting and Validating the WLS_SOA2 Managed Server

After you validate the successful configuration and startup of the WLS_SOA1 Managed Server, you can start and validate the WLS_SOA2 Managed Server.

To start and validate the WLS_SOA2 Managed Server, use the procedure in Starting and Validating the WLS_SOA1 Managed Serverfor WLS_SOA2 Managed Server.

For validation of the URL, enter the following URL in your web browser and log in by using the enterprise deployment administrator user (weblogic_soa):

For Static cluster:
http://WCCHOST2:8001/soa-infra/
For Dynamic cluster:
http://WCCHOST2:8002/soa-infra/

Parent topic: Extending the Domain with Oracle SOA Suite

Configuring Oracle HTTP Server for the Extended Domain

The following sections describe how to configure the Oracle HTTP Server instances so they route requests for both public and internal URLs to the proper clusters in the enterprise topology.

Parent topic: Extending the Domain with Oracle SOA Suite

Configuring Oracle HTTP Server for SOA in an Oracle WebCenter Content Enterprise Deployment

Configure the virtual host configuration files so that requests are routed properly to the Oracle SOA Suite clusters:

  1. Log in to WEBHOST1 and change directory to the configuration directory for the first Oracle HTTP Server instance (ohs1):
    cd WEB_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/moduleconf/
  2. Edit the wccinternal_vh.conf file and add the following directives inside the <VirtualHost> tags:

    Note:

    • The URL entry for /workflow is optional. It is for workflow tasks associated with Oracle ADF task forms. The /workflow URL itself can be a different value, depending on the form.

    • Configure the port numbers appropriately as assigned for your static or dynamic cluster. Dynamic clusters with the Calculate Listen Port option selected will have incremental port numbers for each dynamic managed server created.

    • The WebLogicCluster directive needs only a sufficient number of redundant server:port combinations to guarantee initial contact in case of a partial outage. The actual total list of cluster members is retrieve automatically upon first contact with any given node. 

    # soa-infra
<Location /soa-infra>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# SOA inspection.wsil
<Location /inspection.wsil>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# Worklist
<Location /integration>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# UMS prefs
<Location /sdpmessaging/userprefs-ui>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# Default to-do taskflow
<Location /DefaultToDoTaskFlow>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# Workflow
<Location /workflow>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

#Required if attachments are added for workflow tasks
 <Location /ADFAttachmentHelper> 
    WLSRequest ON 
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001 
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# SOA composer application 
 <Location /soa/composer> 
    WLSRequest ON 
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001 
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

 <Location /frevvo> 
    WLSRequest ON 
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001 
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>
</VirtualHost>
  3. Copy the wccinternal_vh.conf to the configuration directory for the second Oracle HTTP Server instance (ohs2):
    WEB_DOMAIN_HOME/config/fmwconfig/components/ohs2/moduleconf/
  4. Edit the wccinternal_vh.conf to change any references to WEBHOST1 to WEBHOST2 in the <VirtualHost> directives.
  5. Restart both Oracle HTTP servers.

Example 13-1 Sample Content for the wccinternal_vh.conf File 

<VirtualHost WEBHOST1:7777>
    ServerName http://wccinternal.example.com:80
    ServerAdmin you@your.address
    RewriteEngine On
    RewriteOptions inherit

# WSM-PM 
<Location /wsm-pm>
     WebLogicCluster WCPHOST1:7010,WCPHOST2:7010
     WLSRequest ON
     WLProxySSL OFF
     WLProxySSLPassThrough OFF
</Location>

#soa-infra
<Location /soa-infra>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# SOA inspection.wsil
<Location /inspection.wsil>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# Worklist
<Location /integration>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# UMS prefs
<Location /sdpmessaging/userprefs-ui>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# Default to-do taskflow
<Location /DefaultToDoTaskFlow>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# Workflow
<Location /workflow>
    WLSRequest ON
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

#Required if attachments are added for workflow tasks
 <Location /ADFAttachmentHelper> 
    WLSRequest ON 
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001 
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

# SOA composer application 
 <Location /soa/composer> 
    WLSRequest ON 
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001 
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>

 <Location /frevvo> 
    WLSRequest ON 
    WebLogicCluster WCCHOST1:8001,WCCHOST2:8001 
    WLProxySSL OFF
    WLProxySSLPassThrough OFF
</Location>
</VirtualHost>

Parent topic: Configuring Oracle HTTP Server for the Extended Domain

Validating the Oracle SOA Suite URLs Through the Load Balancer

To validate the configuration of the Oracle HTTP Server virtual hosts and to verify that the hardware load balancer can route requests through the Oracle HTTP Server instances to the application tier:

  1. Verify that the server status is reported as Running in the Administration Console.

    If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported (such as Admin or Failed), check the server output log files for errors.

  2. Verify that you can access these URLs:

    • http://wccinternal.example.com/soa-infra

    • http://wccinternal.example.com/integration/worklistapp

    • http://wccinternal.example.com/sdpmessaging/userprefs-ui

    • http://wccinternal.example.com/soa/composer

    • http://wccinternal.example.com/wsm-pm

Parent topic: Configuring Oracle HTTP Server for the Extended Domain

Post-Configuration Steps for Oracle SOA Suite

After you install and configure Oracle SOA Suite, consider the following post-configuration tasks.

Parent topic: Extending the Domain with Oracle SOA Suite

Configuring Oracle Adapters for Oracle SOA Suite

If the Oracle SOA Suite applications that you are developing take advantage of any of the Oracle adapters for Oracle SOA Suite, then you should make sure that the adapters are configured to work efficiently and securely in the enterprise topology.

See the following topics for more information.

Parent topic: Post-Configuration Steps for Oracle SOA Suite

Enabling High Availability for Oracle File and FTP Adapters

If the Oracle SOA Suite applications that you are developing or deploying require the Oracle File and FTP Adapters, you must configure the adapters for high availability in the enterprise deployment topology.

Use the following sections to complete this task.

Understanding the Oracle File and FTP Adapter Configuration

The Oracle File and FTP adapters enable a BPEL process or an Oracle Mediator to read and write files on private file systems and on remote file systems through the File Transfer Protocol (FTP).

When configured properly, these adapters support high availability for an active-active topology with Oracle BPEL Process Manager and Oracle Mediator service engines for both inbound and outbound operations.

For general information about this task, see Configuring Oracle File and FTP Adapters in Oracle Fusion Middleware Understanding Technology Adapters. The instructions provided here are specific to the Oracle SOA Suite enterprise deployment.

Note:

The File Adapter picks up a file from the inbound directory, processes it, and then outputs a file to the output directory. Because the File Adapter is non-transactional, files can be processed twice. As a result, it is possible to get duplicate files when there is failover in the RAC backend or in the SOA managed servers.

Configuring the Oracle File Adapter in the Administration Console

To make the Oracle File Adapter highly available, first modify the Oracle File Adapter deployment descriptor for the connection-instance that corresponds to eis/HAFileAdapter.

You can perform this task from the Oracle WebLogic Server console:

  1. Navigate to and log into the Oracle WebLogic Server Administration Console.

    For example:

    http://ADMINVHN:7001/console

    Note:

    If you have already configured web tier, use http://admin.example.com/console.

  2. In the left pane of the console, click Deployments.

  3. Locate the FileAdapter resource adapter in the Summary of Deployments table.

  4. Click FileAdapter to display the Settings for FileAdapter page.

  5. Click Configuration.

  6. Click Outbound Connection Pools.

  7. Expand javax.resource.cci.ConnectionFactory to see the configured connection factories.

  8. Click eis/HAFileAdapter.

    The Outbound Connection Properties for the connection factory appears.

  9. Click Lock & Edit.

    The property value column becomes editable (you can click on any of the rows in the Property Value column and modify the value).

  10. Enter the values as shown in Table 13-2.

    Note:

    Update controlDir and check other values against the default values as mentioned in Table 13-2.

    Table 13-2 Values to Provide for the javax.resource.cci.Connectionfactory

    Parameter Description

    controlDir

    Enter the directory where you want the control files to be stored. You must set it to a shared location if multiple WebLogic Server instances run in a cluster. Structure the directory for shared storage as follows:

    ORACLE_RUNTIME/domain_name/cluster_name/fadapter

    inboundDataSource

    Set the value to jdbc/SOADataSource.

    outboundDataSource

    Set the value to jdbc/SOADataSource.

    outboundDataSourceLocal

    Set the value to jdbc/SOALocalTxDataSource. This is the data source where the schemas that corresponds to high availability are precreated.

    outboundLockTypeForWrite

    Set the value to oracle if you are using Oracle Database. By default the Oracle File and FTP Adapters use an in-memory mutex to lock outbound write operations. You must choose from the following values for synchronizing write operations:

    • memory: The Oracle File and FTP Adapters use an in-memory mutex to synchronize access to the file system.

    • oracle: The adapter uses Oracle Database sequence.

    • db: The adapter uses a pre-created database table (FILEADAPTER_MUTEX) as the locking mechanism. You must use this option only if you are using a schema other than the Oracle Database schema.

    • user-defined: The adapter uses a user-defined mutex. To configure the user-defined mutex, you must implement the mutex interface: oracle.tip.adapter.file.Mutex and then configure a new binding-property with the name oracle.tip.adapter.file.mutex and value as the fully qualified class name for the mutex for the outbound reference.

    workingDirectory

    Retain the default value.

  11. Click Save after you update the properties. The Save Deployment Plan page appears.

  12. Create DEPLOY_PLAN_HOME directory.

    mkdir -p DEPLOY_PLAN_HOME/wccedg_domain

    In this example, replace DEPLOY_PLAN_HOME with the actual path to the deployment plan directory that is defined in File System and Directory Variables Used in This Guide.

  13. Enter a shared storage location for the deployment plan path value. The directory structure is as follows: 

    DEPLOY_PLAN_HOME/wccedg_domain/FileAdapterPlan.xml

  14. Click OK to save the storage location.

  15. Click Save to save and then click Activate Changes to apply your changes to the File Adapter.

  16. Update the deployment in the console:

    1. Click Deployments.

    2. Click Lock & Edit.

    3. Select the checkbox for the File Adapter deployment.

    4. Click Update.

    5. Select the option: Update this application in place with new deployment plan changes (A deployment plan must be specified for this option.)

    6. Click the Change Path button and select the FileAdapterPlan.xml file from the path to the shared storage location.

    7. Click Finish.

    8. Activate the changes.

  17. Verify that the FileAdapter deployment is activated and running:

    1. In the Administration Console, click Deployments in the left pane.

    2. Locate the FileAdapter deployment in the Deployments table.

    3. If it is not in the active state, click the Control tab under Summary of Deployments, and then select FileAdapter under Deployments. Select Start, and then Servicing All Requests.

    4. Click Yes.

Editing the JCA File Within the Composite Application

After you have configured the FileAdapter deployment in the Administration Console, you can edit the .jca file that is included in the composite applications to be deployed so that they can use the connection factory that was configured in the previous steps, as shown in Example 13-2.

Note:

The location attribute is set to eis/HAFileAdapter for the connection factory.

Example 13-2 Example of the File Adapter .JCA File Modifications for an Enterprise Deployment

<adapter-config name="FlatStructureOut"
                adapter="File Adapter"
                xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
     <connection-factory location="eis/HAFileAdapter" adapterRef=""/>
     <endpoint-interaction portType="Write_ptt" 
                           operation="Write">
          <interaction-spec className="oracle.tip.adapter.file.outbound.FileInteractionSpec">
                <property../>
                <property../>
          </interaction-spec>
     </endpoint-interaction>
</adapter-config>
Configuring the Oracle FTP Adapter

If your application requires an FTP Adapter, then repeat the procedures Configuring the Oracle File Adapter in the Administration Console and Editing the JCA File Within the Composite Application, with the following differences:

  • Locate the FtpAdapter deployment in the list of deployments in the Administration Console.

  • Click FtpAdapter to display the Settings for the FtpAdapter page.

  • Click Configuration.

  • Click Outbound Connection Pools.

  • Expand javax.resource.cci.ConnectionFactory to see the configured connection factories.

  • Click eis/Ftp/HAFtpAdapter.

    The Outbound Connection Properties for the connection factory appears.

  • Click Lock & Edit.

  • Modify the adapter properties for high availability. See Table 13-2.

  • Update the ControlDir property so it points to the following location:

    ORACLE_RUNTIME/domain_name/cluster_name/ftpadapter
  • Enter a shared storage location for the deployment plan. The directory structure is as follows:
    DEPLOY_PLAN_HOME/wccedg_domain/FtpAdapterPlan.xml
Enabling High Availability for Oracle JMS Adapters

When the Oracle JMS adapter communicates with multiple servers in a cluster, the adapter's connection factory property FactoryProperties must list available servers. If it does not list servers, the connection establishes to only one random server. If that particular server goes down, no further messages are processed.

To verify the adapter's JCA connection factory:

  1. Log into your Oracle WebLogic Server Administration Console using the following URL:

    http://ADMINVHN:7001/console

    Note:

    If you have already configured Web tier, use http://admin.example.com/console.

  2. Click Deployments in the left pane for Domain Structure.

  3. Click JmsAdapter under Summary of Deployments on the right pane.

  4. Click the Configuration tab.

  5. Click the Outbound Connection Pools tab and expand oracle.tip.adapter.jms.IJmsConnectionFactory to see the configured connection factories.

  6. Click Lock & Edit.

  7. Click the specific instance you are using (for example, eis/wls/Queue). The Outbound Connection Properties for the connection factory opens.

  8. In the FactoryProperties field (click on the corresponding cell under Property value), enter the following, all on one line, separated by semicolons: 

    java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;
java.naming.provider.url=cluster:t3://SOA_Cluster;
java.naming.security.principal=weblogic;
java.naming.security.credentials=mypassword

  9. Click Save after you update the properties. The Save Deployment Plan page appears.

  10. (First time only) Enter a shared storage location for the deployment plan. The directory structure is as follows:

    DEPLOY_PLAN_HOME/soaedg_domain/JMSAdapterPlan.xml

  11. Click OK to commit the updated storage path.

  12. Click Save.

  13. Repeat steps 7 through 9 for all required connection factories.

  14. Click Activate Changes.

  15. Update the deployment in the console:

    1. Click Deployments.

    2. Click Lock & Edit.

    3. Select the checkbox for the JMS Adapater.

    4. Click Update.

    5. Select Update this application in place with new deployment plan changes (A deployment plan must be specified for this option.) and select the deployment plan saved in a shared storage location; all servers in the cluster must be able to access the plan.

    6. Click Finish.

    7. Activate the changes.

Enabling High Availability for the Oracle Database Adapter

To ensure High Availability while leveraging the Oracle Database Adapter, the Logical Delete Polling Strategy is used normally as it performs better than a physical delete. However, when you have a clustered environment where multiple nodes are polling for the same data, a single record might get processed more than once. To avoid this problem, Oracle Database Adapter uses a distributed polling technique that uses an Oracle Database feature called skip locking.

If you were using the Logical Delete Polling Strategy approach previously, you can remove (in db.jca) or clear (Logical Delete Page of wizard) the MarkReservedValue, and you automatically get skip locking.

The benefits of using skip locking over a reserved value include:

  • Skip locking scales better in a cluster and under load.

  • All work is in one transaction (as opposed to update/reserve, then commit, then select in a new transaction), so the risk of facing a non-recoverable situation in a high availability environment is minimized.

  • No unique MarkReservedValue must be specified. Previously, for this to work you would have to configure a complex variable, such as R${weblogic.Name-2}-${IP-2}-${instance}.

If you are using Logical Delete polling, and you set MarkReservedValue, skip locking is not used.

For more information, see "Scalability" and "Polling Strategies" in the Oracle Fusion Middleware User's Guide for Technology Adapters.

Enabling SSL Communication Between the SOA Servers and the Hardware Load Balancer

After you extend the domain with Oracle SOA Suite, you should also ensure that the Administration Server and Managed Servers can access the front-end SSL URL of the hardware load balancer.

This allows SOA Composite applications and web services to invoke callbacks and other communications with the front-end secure URL. See Enabling SSL Communication Between the Middle Tier and the Hardware Load Balancer.

Parent topic: Post-Configuration Steps for Oracle SOA Suite

Considerations for Sync-Async Interactions in a SOA Cluster

In a SOA cluster, the following scenarios are not supported:

  • Synchronous BPEL process with mid-process receive.

  • Synchronous BPEL process calling asynchronous services.

  • Callback from synchronous processes.

Parent topic: Post-Configuration Steps for Oracle SOA Suite

Updating FusionAppsFrontendHostUrl

You must configure Oracle Workflow with the appropriate URL so that the default-to-do tasks and custom tasks' details use the front-end load balancer to create task-display URLs.

To configure the appropriate URLs:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control with the username and password that you specified in the boot.properties file. See Creating the boot.properties File.
  2. In the left navigation tree, expand WebLogic Domain, and then click System MBean Browser.
  3. Navigate to Application Defined Mbean> oracle.as.soainfra.config.
    1. If you are configuring a static cluster, navigate to Server: WLS_SOA1>WorkflowConfig.
    2. If you are configuring a dynamic cluster, navigate to Domain: wccedg_domain >WorkflowConfig.
  4. Click human-workflow.

    Note:

    In a clustered environment, there are multiple human-workflow Mbeans, one for every server in the cluster. Modify any one of them to update the property centrally in MDS for the entire cluster.

  5. On the right panel, look for the FusionAppsFrontendHostUrl attribute.
  6. For the FusionAppsFrontendHostUrl attribute, specify the value *=https://wcc.example.com:443.
  7. Click Apply.

Parent topic: Post-Configuration Steps for Oracle SOA Suite

Enabling JDBC Persistent Stores

Oracle recommends that you use JDBC stores, which leverage the consistency, data protection, and high availability features of an oracle database and makes resources available for all the servers in the cluster.

Follow these guidelines to ensure that you use JDBC stores, when you use static or dynamic clusters:

  • For static clusters

    If you have made the following selections in the High Availability Options screen, as recommended in this guide for static clusters, then JDBC persistent stores are already configured for both JMS and TLOGS:

    • Set JTA Transaction Log Persistence to JDBC TLog Store.

    • Set JMS Server Persistence to JMS JDBC Store.

  • For dynamic clusters

    You can configure only JMS Server persistence for dynamic clusters by using the Configuration Wizard. JTA Transaction Logs Persistence must be configure manually, if required. If you have made the following selections in the High Availability Options screen, as recommended in this guide for dynamic clusters, then JDBC persistent stores are already configured for JMS.

    • Set JMS Server Persistence to JMS JDBC Store.

    • Verify that JTA Transaction Log Persistence is set to Default Persistent Store.

    Additional steps are needed to configure JTA Transaction Log with JDBC store. See Roadmap for Configuring a JDBC Persistent Store for TLOGs.

In case you did not select JDBC for JMS and TLOGS persistent in the High Availability Options screen, you can still configure JDBC stores manually in a post step. For specific instructions to configure them manually, see Using JDBC Persistent Stores for TLOGs and JMS in an Enterprise Deployment.

Note:

The High Availability Options screen appears during the Configuration Wizard session for the first time when you create a cluster that uses Automatic Service Migration or JDBC stores or both. All subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply the selected HA options.

Parent topic: Extending the Domain with Oracle SOA Suite

Enabling Automatic Service Migration

To ensure high availability for the product installed in this chapter, you must configure service migration appropriately.

Follow these guidelines to ensure that you provide the required high availability for Weblogic services when you use static or dynamic clusters:

  • For static clusters

    Automatic Service Migration is already configured if you select Enable Automatic Service Migration with Database Basis in the High Availability Options screen.

    The Database Leasing is already configured and the migratable targets are created with the appropriate policies for the cluster. If you have implemented these settings, validate the configuration, as described in Validating Automatic Service Migration in Static Clusters.

    In case you do not select this option during the Configuration Wizard session, you can configure automatic migration manually in a post step. For instructions to complete the steps for static clusters, see Configuring Automatic Service Migration in an Enterprise Deployment.

  • For dynamic clusters

    You cannot configure Service Migration for dynamic clusters by using the Configuration Wizard, it needs to be configured manually. The following steps are needed:

    • Configure the database leasing for the cluster.

    • Set the appropriate migration policies for JTA Service and JMS Persistent Stores.

    For instructions to complete the steps for dynamic clusters, see Configuring Automatic Service Migration in an Enterprise Deployment.

Note:

The High Availability Options screen appears during the Configuration Wizard session for the first time when you create a cluster that uses Automatic Service Migration or JDBC stores or both. All subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply the selected HA options.

Parent topic: Extending the Domain with Oracle SOA Suite