13 Extending the Domain with Oracle SOA Suite
- Variables Used When Configuring Oracle SOA Suite
While extending the domain with Oracle SOA Suite, you are referencing the directory variables listed in this section. - 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. - 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. - Installing the Software for an Enterprise Deployment
The procedure to install the software for an enterprise deployment is explained in this section. - 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. - 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. - Propagating the Extended Domain to the Domain Directories and Machines
After you have extended the domain with the Oracle SOA Suite instances, and you have restarted the Administration Server on SOAHOST1, you must then propagate the domain changes to the domain directories and machines. - 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. - 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. - Modifying the Upload and Stage Directories to an Absolute Path
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. - 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. - Configuring the Web Tier for the Extended Domain
Configure the web server instances on the web tier so that the instances route requests for both public and internal URLs to the proper clusters in the extended domain. - Post-Configuration Steps for Oracle SOA Suite
After you install and configure Oracle SOA Suite, consider the following post-configuration tasks. - Enabling JDBC Persistent Stores for Oracle SOA Suite
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. - Enabling Automatic Service Migration for Oracle SOA Suite
To ensure high availability for the product installed in this chapter, you must configure service migration appropriately. - Backing Up the Configuration
It is an Oracle best practices recommendation to create a backup after you successfully extended a domain or at another logical point. Create a backup after you verify that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.
Parent topic: Configuring the Enterprise Deployment
Variables Used When Configuring Oracle SOA Suite
While extending the domain with Oracle SOA Suite, you are 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
-
WEB_DOMAIN_HOME
-
JAVA_HOME
-
ORACLE_RUNTIME
In addition, you reference the following virtual IP (VIP) address that are defined in Reserving the Required IP Addresses for an Enterprise Deployment:
-
ADMINVHN
Actions in this chapter are performed on the following host computers:
-
SOAHOST1
-
SOAHOST2
-
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 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, and use migration policies. For dynamic and static cluster, all the configuration related with Service Migration can be automatically performed by the Configuration Wizard and this is the approach used in this guide.
Mixed clusters (clusters that contains both dynamic and configured server instances) are not supported in the Oracle SOA Suite 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.
Oracle recommends the use of the Network Time Protocol (NTP). See Configuring a Host to Use an NTP (time) Server.
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.
- Starting the Oracle SOA Suite Installer on SOAHOST1
- Navigating the Installation Screens
- Installing Oracle SOA Suite on the Other Host Computers
- Verifying the Installation
Parent topic: Extending the Domain with Oracle SOA Suite
Starting the Oracle SOA Suite Installer on SOAHOST1
To start the installation program:
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 |
---|---|
This screen introduces you to the product installer. |
|
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. |
|
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. |
|
Use this screen to select the type of installation and consequently, the products and feature sets you want to install.
|
|
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 Installing and Configuring the Oracle Fusion Middleware Infrastructure. |
|
Use this screen to verify the installation options that you selected. Click Install to begin the installation. |
|
This screen allows you to see the progress of the installation. Click Next when the progress bar reaches 100% 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 SOAHOST2, then you must also perform the product installation on SOAHOST2.
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 SOAHOST1 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.
- Reviewing the Installation Log Files
- Checking the Directory Structure
- Viewing the Contents of Your Oracle Home
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 Installing Software with the Oracle Universal Installer.
Parent topic: Verifying the Installation
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.
Parent topic: Verifying the Installation
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.
Parent topic: Verifying the Installation
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.
- Starting the Repository Creation Utility (RCU)
- Navigating the RCU Screens to Create the Schemas
- Verifying Schema Access
- Configuring SOA Schemas for Transactional Recovery
Parent topic: Extending the Domain with Oracle SOA Suite
Starting the Repository Creation Utility (RCU)
To start the Repository Creation Utility (RCU):
Parent topic: Creating the Oracle SOA Suite Database Schemas
Navigating the RCU Screens to Create the Schemas
Schema creation involves the following tasks:
-
Task 7, "Verifying the Tablespaces for the Required Schemas"
-
Task 9, "Reviewing Completion Summary and Completing RCU Execution"
- 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 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.
-
In the Host Name field, enter the SCAN address of the Oracle RAC Database.
-
Enter the Port number of the RAC database scan listener, for example 1521.
-
Enter the RAC Service Name of the database.
-
Enter the User Name of a user that has permissions to create schemas and schema objects, for example SYS.
-
Enter the Password of the user name that you provided in step 4.
-
If you have selected the SYS user, ensure that you set the role to SYSDBA.
-
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
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
LARGE
for the Database Profile custom 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:
Note:
If the database is a plugable database (PDB), the apropriate tns alias that points to the PDB must be used in the sqlplus command../sqlplus FMW12214_SOAINFRA/<soainfra_password>
SQL*Plus: Release 19.0.0.0.0 - Production on Tue May 26 06:04:29 2020
Version 19.6.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Last Successful login time: Tue Apr 07 2020 01:04:10 -07:00
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - 64bit Production
Version 19.6.0.0.0
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:
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:
- Starting the Configuration Wizard
Start the Configuration Wizard as the first step to extend the existing enterprise deployment domain. - 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. - 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.
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:
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.
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"
-
Task 6, "Providing the GridLink Oracle RAC Database Connection Details"
-
Task 20, "Reviewing Your Configuration Specifications and Configuring the Domain"
-
Task 21, "Writing Down Your Domain Home and Administration Server URL"
- 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 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 Reference Configuration [soa]
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), the domain must be updated using the SOA classic template.
The classic SOA templates, which do not implement the optimizations included in Reference Configuration are not shown in the Configuration Wizard, but are available and located at:$ORACLE_HOME/soa/common/templates/wls
(the SOA and B2B classic templates)$ORACLE_HOME/osb/common/templates/wls
(the OSB classic template)
To select the SOA classic extension template for SOA, in the Configuration Wizard Templates screen:- Select Update Domain Using Custom Template.
- Browse to
$ORACLE_HOME/soa/common/templates/wls
. - Select
oracle.soa_template.jar
.Important:
Do not useoracle.soa.classic.domain_template.jar
to extend the infra domain. This SOA classic template should be used to only create domains from zero, not to extend an existing infra domain. To extend an infra domain to add SOA classic, useoracle.soa_template.jar
.
Subsequent extensions on a Classic SOA domain for B2B or OSB must be done with Classic extension templates and not with Reference Configuration templates.
If you do not plan to add any component that do not support Reference Configuration, Oracle recommends you to use the Oracle SOA Suite Reference Configuration template.
-
- 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 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 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
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.
Complete these values only if you are using Oracle 11g database:- 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
).
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 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 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:
-
Rename the default Oracle SOA Suite Managed Server to
WLS_SOA1
. -
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.
-
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 Creating WebLogic Domains Using the Configuration Wizard.
Table 13-1 Lists the Information to Provide for Each SOA Managed Server on the Configuration Wizard Managed Servers Screen
Server Name Listen Address Listen Port Enable SSL SSL Listen Port Server Groups WLS_WSM1
SOAHOST1
7010
No
Disabled
WSMPM-MAN-SVR and JRF-MAN-SVR
WLS_WSM2
SOAHOST2
7010
No
Disabled
WSMPM-MAN-SVR and JRF-MAN-SVR
WLS_SOA1
SOAHOST1
8001
No
Disabled
SOA-MGD-SVRS-ONLY
WLS_SOA2
SOAHOST2
8001
No
Disabled
SOA-MGD-SVRS-ONLY
-
- 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.
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
on the load balancer rather than the address in the HOST header of each request.soa.example.com
For more information about the
soa.example.com
virtual server address, see Configuring Virtual Hosts on the Hardware Load Balancer.Use the Clusters screen to create a new cluster:
-
Click the Add button.
-
Specify
SOA_Cluster
in the Cluster Name field. -
Specify
soa.example.com
in the Frontend Host field. -
Specify
80
as the Frontend HTTP Port and443
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 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.
-
Confirm that Calculated Machine Names and Calculated Listen Port checkboxes on this screen are unchecked.
-
Confirm the Server Template and Dynamic Server Groups selections are Unspecified.
-
Click Next.
-
- Task 14 Assigning Managed Servers to the Cluster
-
Use the Assign Servers to Clusters screen to assign
WLS_SOA1
andWLS_SOA2
to the new clusterSOA_Cluster
:-
In the Clusters pane, select the cluster to which you want to assign the servers; in this case,
SOA_Cluster
. -
In the Servers pane, assign
WLS_SOA1
toSOA_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.
-
-
Repeat to assign
WLS_SOA2
toSOA_Cluster
.
For more information about the options on this screen, see Assign Servers to Clusters in 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
-
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
toSOAHOST1
, and assignWLS_SOA2
to SOAHOST2.For more information about the options on this screen, see Assign Servers to Machines in 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 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"
-
Task 6, "Providing the GridLink Oracle RAC Database Connection Details"
-
Task 19, "Reviewing Your Configuration Specifications and Configuring the Domain"
-
Task 20, "Writing Down Your Domain Home and Administration Server URL"
- 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 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 Reference Configuration [soa]
Tip:
More information about the options on this screen can be found in 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), the domain must be updated using the SOA classic template.
The classic SOA templates, which do not implement the optimizations included in Reference Configuration are not shown in the Configuration Wizard, but are available and located at:$ORACLE_HOME/soa/common/templates/wls
(the SOA and B2B classic templates)$ORACLE_HOME/osb/common/templates/wls
(the OSB classic template)
To select the SOA classic extension template for SOA, in the Configuration Wizard Templates screen:- Select Update Domain Using Custom Template.
- Browse to
$ORACLE_HOME/soa/common/templates/wls
. - Select
oracle.soa_template.jar
.Important:
Do not useoracle.soa.classic.domain_template.jar
to extend the infra domain. This SOA classic template should be used only to create domains from zero, not to extend an existing infra domain. To extend an infra domain to add SOA classic, useoracle.soa_template.jar
.
Subsequent extensions on a Classic SOA domain for B2B or OSB must be done with Classic extension templates and not with Reference Configuration templates.
If you do not plan to add any component that do not support Reference Configuration, Oracle recommends you to use the Oracle SOA Suite Reference Configuration template.
-
- 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 these HA options.
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. 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 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 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 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
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.
Complete these values only if you are using Oracle 11g database:- 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
).
Enable Fan
Verify that the Enable Fan check box is selected, so 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 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 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 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:
JMS 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 JMS File Stores in Task 3, "Configuring High Availability Options", you have to select the File Stores option 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".
SOA Static Managed Server definitions are not needed for dynamic cluster configuration. To remove the default Managed Server, complete the following steps:
-
Click the Managed Server and click Delete.
-
Click Next.
-
- 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.
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
on the load balancer rather than the address in the HOST header of each request.soa.example.com
For more information about the
soa.example.com
virtual server address, see Configuring Virtual Hosts on the Hardware Load Balancer.Use the Clusters screen to create a new cluster:
-
Click the Add button.
-
Specify
SOA_Cluster
in the Cluster Name field. -
Specify
soa.example.com
in the Frontend Host field. -
Specify
80
as the Frontend HTTP Port and443
as the Frontend HTTPS port.
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 Administering Clusters for Oracle WebLogic Server.
Tip:
More information about the options on this screen can be found in Clusters in Creating WebLogic Domains Using the Configuration Wizard.
-
- Task 12 Assigning Server Templates
-
To configure a template, complete the following steps:
-
Verify that
soa-server-template
is selected in the Name field. -
Specify
8000
in the Listen Port field. -
Leave the Enable SSL option unchecked.
-
Click Next.
-
- Task 13 Configuring Dynamic Servers
-
Use the Dynamic Clusters screen to configure the required clusters:
-
Verify
SOA_Cluster
is listed in the Cluster Name field. -
From the Server Template drop-down list, select
soa-server-template
. -
Specify
WLS_SOA
in the Server Name Prefix field. -
Specify
2
in the Dynamic Cluster Size field. -
Specify
SOAHOST*
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.
To make things easier regardless of your actual physical hostname, Oracle recommends that you use SOAHOSTn as your WebLogic machine names, where n is a sequential number. This is explained in Task 18, "Creating Machines" of configuring the infrastructure domain. This convention makes it easy for dynamic clusters to determine where to start each cluster member. If you want to follow this convention, in the Machine Match Expression field, enter
SOAHOST*
.If you do not adopt this convention, the cluster members are started on each machine that you define in Task 18, "Creating Machines", including that of ADMINHOST. This situation is undesirable as you would end up with two cluster members that run on the same physical server but are attached to two different domain homes.
-
Select Calculated Listen Ports.
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
-
-
Select the Dynamic Server Groups SOA-DYN-CLUSTER-ONLY.
-
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 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
-
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 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.
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:
Propagating the Extended Domain to the Domain Directories and Machines
After you have extended the domain with the Oracle SOA Suite instances, and you have restarted the Administration Server on SOAHOST1, you must then propagate the domain changes to the domain directories and machines.
Table 13-2 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-2 Summary of Tasks Required to Propagate the Domain Changes to Domain Directories and Machines
Task | Description | More Information |
---|---|---|
Pack up the Extended Domain on SOAHOST1 |
Use the When you pack up the domain, create a template JAR file called |
|
Unpack the Domain in the Managed Servers directory on SOAHOST1 |
Unpack the template JAR file in the Managed Servers directory on SOAHOST1 local storage. |
Unpacking the Domain in the Managed Servers Domain Directory on SOAHOST1 |
Unpack the Domain on SOAHOST2 |
Unpack the template JAR file in the Managed Servers directory on the SOAHOST2local storage. |
- Packing Up the Extended Domain on SOAHOST1
- Unpacking the Domain in the Managed Servers Domain Directory on SOAHOST1
- Unpacking the Domain on SOAHOST2
Parent topic: Extending the Domain with Oracle SOA Suite
Packing Up the Extended Domain on SOAHOST1
Use the following steps to create a template JAR file that contains the domain configuration information:
Unpacking the Domain in the Managed Servers Domain Directory on SOAHOST1
To copy the updated domain configuration information from the Administration Server domain directory to the Managed Servers domain directory:
Unpacking the Domain on SOAHOST2
This procedure assumes you have copied the file that you created earlier in a location that is accessible from both SOAHOST1 and SOAHOST2; such as the ASERVER_HOME directory, which is located on the shared storage filer:
-
Log in to SOAHOST2
-
If you haven't already, create the recommended directory structure for the Managed Server domain on the SOAHOST2 storage device.
Use the examples in File System and Directory Variables Used in This Guide as a guide.
-
Make sure the
soadomaintemplate.jar
accessible to SOAHOST2.For example, if you are using a separate shared storage volume or partition for SOAHOST2, then copy the template to the volume or partition mounted to SOAHOST2.
-
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/
soadomaintemplate.jar
\ -log_priority=DEBUG \ -log=/tmp/unpack.log \ -app_dir=APPLICATION_HOMENote:
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/
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.soadomaintemplate.jar
-
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 Creating Templates and Domains Using the Pack and Unpack Commands.
-
-
Change directory to the newly created MSERVER_HOME directory and verify that the domain configuration files were copied to the correct location on the SOAHOST2 local storage device.
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.
- Starting the WLS_SOA1 Managed Server
- Adding the SOAAdmin Role to the Administrators Group
- Validating the Managed Server by Logging in to the SOA Infrastructure
Parent topic: Extending the Domain with Oracle SOA Suite
Starting the WLS_SOA1 Managed Server
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.
To start the WLS_SOA1 Managed Server:
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 (SOA Administrators
).
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:
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
):
http://SOAHOST2:8001/soa-infra/
http://SOAHOST2:8002/soa-infra/
Parent topic: Extending the Domain with Oracle SOA Suite
Modifying the Upload and Stage Directories to an Absolute Path
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
Configuring the Web Tier for the Extended Domain
Configure the web server instances on the web tier so that the instances route requests for both public and internal URLs to the proper clusters in the extended domain.
For additional steps in preparation for possible scale-out scenarios, see Updating Cross Component Wiring Information.
- Configuring Oracle HTTP Server for the WLS_SOA Managed Servers
- Configuring the WebLogic Proxy Plug-In
- Validating the Oracle SOA Suite URLs Through the Load Balancer
Parent topic: Extending the Domain with Oracle SOA Suite
Configuring Oracle HTTP Server for the WLS_SOA Managed Servers
To configure the Oracle HTTP Server instances in the web tier so that they route requests correctly to the Oracle SOA Suite cluster, use the following procedure to create an additional Oracle HTTP Server configuration file that creates and defines the parameters of the soa.example.com
virtual server.
This procedure assumes that you performed the Oracle HTTP Server configuration tasks described in Configuring Oracle HTTP Server to Route Requests to the Application Tier.
To create the virtual host configuration file so that requests are routed properly to the Oracle SOA Suite clusters:
Example 13-1 soa_vh.conf
file
<VirtualHost WEBHOST1:7777>
ServerName https://soa.example.com
:443
ServerAdmin you@your.address
RewriteEngine On
RewriteOptions inherit
<Location /soa-infra>
WLSRequest ON
WebLogicCluster SOAHOST1:8001,SOAHOST2:8001
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
# SOA inspection.wsil
<Location /inspection.wsil>
WLSRequest ON
WebLogicCluster SOAHOST1:8001,SOAHOST2:8001
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
# Worklist
<Location /integration>
WLSRequest ON
WebLogicCluster SOAHOST1:8001,SOAHOST2:8001
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
# UMS prefs
<Location /sdpmessaging/userprefs-ui>
WLSRequest ON
WebLogicCluster SOAHOST1:8001,SOAHOST2:8001
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
# Default to-do taskflow
<Location /DefaultToDoTaskFlow>
WLSRequest ON
WebLogicCluster SSOAHOST1:8001,SOAHOST2:8001
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
# Workflow
<Location /workflow>
WLSRequest ON
WebLogicCluster SOAHOST1:8001,SOAHOST2:8001
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
#Required if attachments are added for workflow tasks
<Location /ADFAttachmentHelper>
WLSRequest ON
WebLogicCluster SOAHOST1:8001,SOAHOST2:8001
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
# SOA composer application
<Location /soa/composer>
WLSRequest ON
WebLogicCluster SOAHOST1:8001,SOAHOST2:8001
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
</VirtualHost>
Note:
If internal invocations are going to be used in the system, add the appropriate locations to the soainternal virtual host.
Parent topic: Configuring the Web Tier for the Extended Domain
Configuring the WebLogic Proxy Plug-In
Before you can validate that requests that are routed correctly through the Oracle HTTP Server or Oracle Traffic Director instances, you must set the WebLogic Plug-In Enabled
parameter for the clusters that you just configured. To configure the WebLogic Proxy Plug-in:
Parent topic: Configuring the Web Tier 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:
Parent topic: Configuring the Web Tier 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.
- Configuring Oracle Adapters for Oracle SOA Suite
- Enabling SSL Communication Between the SOA Servers and the Hardware Load Balancer
- Considerations for Sync-Async Interactions in a SOA Cluster
- Updating FusionAppsFrontendHostUrl
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.
- Enabling High Availability for Oracle File and FTP Adapters
- Enabling High Availability for Oracle JMS Adapters
- Enabling High Availability for the Oracle Database Adapter
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
- Configuring the Oracle File Adapter in the Administration Console
- Editing the JCA File Within the Composite Application
- Configuring the Oracle FTP Adapter
Parent topic: Configuring Oracle Adapters for Oracle SOA Suite
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 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:
-
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
. -
In the left pane of the console, click Deployments.
-
Locate the FileAdapter resource adapter in the Summary of Deployments table.
-
Click FileAdapter to display the Settings for FileAdapter page.
-
Click Configuration.
-
Click Outbound Connection Pools.
-
Expand javax.resource.cci.ConnectionFactory to see the configured connection factories.
-
Click eis/HAFileAdapter.
The Outbound Connection Properties for the connection factory appears.
-
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).
-
Enter the values as shown in Table 13-3.
Note:
Update controlDir and check other values against the default values as mentioned in Table 13-3.
Table 13-3 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 nameoracle.tip.adapter.file.mutex
and value as the fully qualified class name for the mutex for the outbound reference.
workingDirectory
Retain the default value.
-
-
Click Save after you update the properties. The Save Deployment Plan page appears.
-
Create DEPLOY_PLAN_HOME directory.
mkdir -p DEPLOY_PLAN_HOME/
soaedg_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.
-
Enter a shared storage location for the deployment plan path value. The directory structure is as follows:
DEPLOY_PLAN_HOME/
soaedg_domain
/FileAdapterPlan.xml -
Click OK to save the storage location.
-
Click Save to save and then click Activate Changes to apply your changes to the File Adapter.
-
Update the deployment in the console:
-
Click Deployments.
-
Click Lock & Edit.
-
Select the checkbox for the FileAdapter deployment.
-
Click Update.
-
Select the option: Update this application in place with new deployment plan changes (A deployment plan must be specified for this option.)
-
Click the Change Path button and select the FileAdapterPlan.xml file from the path to the shared storage location.
-
Click Finish.
-
Activate the changes.
-
-
Verify that the FileAdapter deployment is activated and running:
-
In the Administration Console, click Deployments in the left pane.
-
Locate the FileAdapter deployment in the Deployments table.
-
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.
-
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-3.
-
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/
soaedg_domain
/FtpAdapterPlan.xml -
Update the FTPAdapter deployment in the console. See Configuring the Oracle File Adapter in the Administration Console.
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 is established to only one random server. If that particular server goes down, no further messages are processed.
To avoid this issue, you can use the “cluster name” syntax in the FactoryProperties
of the adapter instead of using the static list of members. The cluster name syntax is as follows:
cluster:t3://cluster_name
When you use cluster:t3://cluster_name
, the invocation fetches the complete list of members in the cluster at any given time, thus avoiding any dependencies on the initial servers and accounting for every member that is alive in the cluster at that point of time. Note that you can use this cluster syntax only when the cluster is in the same domain.
To modify the adapter's JCA connection factory:
-
Log into your Oracle WebLogic Server Administration Console by using the following URL:
http://ADMINVHN:7001/console
Note:
If you have already configured web tier, use
http://admin.example.com/console
. -
Click Deployments in the left pane for Domain Structure.
-
Click JmsAdapter under Summary of Deployments on the right pane.
-
Click the Configuration tab.
-
Click the Outbound Connection Pools tab and expand
oracle.tip.adapter.jms.IJmsConnectionFactory
to see the configured connection factories. -
Click Lock & Edit.
-
Click the specific instance that you are using (for example,
eis/wls/Queue
). The Outbound Connection Properties for the connection factory opens. -
In the FactoryProperties field (click 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=<password>
-
Click Save after you update the properties. The Save Deployment Plan page appears.
-
(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 -
Click OK to commit the updated storage path.
-
Click Save.
-
Repeat steps 7 through 9 for all required connection factories.
-
Click Activate Changes.
-
Update the deployment in the console:
-
Click Deployments.
-
Click Lock & Edit.
-
Select the checkbox for the JMS Adapater.
-
Click Update.
-
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.
-
Click Finish.
-
Activate the changes.
-
Parent topic: Configuring Oracle Adapters for Oracle SOA Suite
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.
Parent topic: Configuring Oracle Adapters for Oracle SOA Suite
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
To configure the appropriate URLs:
Parent topic: Post-Configuration Steps for Oracle SOA Suite
Enabling JDBC Persistent Stores for Oracle SOA Suite
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.
If you have made the following selections in the High Availability Options screen, as recommended in this guide both for static and 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.
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 for Oracle SOA Suite
To ensure high availability for the product installed in this chapter, you must configure service migration appropriately.
Automatic Service Migration is already configured if you have selected Enable Automatic Service Migration with Database Leasing in the High Availability Options screen, as recommended in this guide for both static and dynamic clusters. When that option is selected, Database Leasing is configured and the migratable targets (when using static cluster) or the persistent stores (when using dynamic clusters) are created with the appropriate migration policies for the cluster.
If you have implemented this setting, 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, 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
Backing Up the Configuration
It is an Oracle best practices recommendation to create a backup after you successfully extended a domain or at another logical point. Create a backup after you verify that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.
The backup destination is the local disk. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process.
For information about backing up your configuration, see Performing Backups and Recoveries for an Enterprise Deployment.
Parent topic: Extending the Domain with Oracle SOA Suite