To start the installation program:

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

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.

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.

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

To start the Repository Creation Utility (RCU):

Schema creation involves the following tasks:

• Task 1, "Introducing RCU"

• Task 2, "Selecting a Method of Schema Creation"

• Task 3, "Providing Database Connection Details"

• Task 4, "Specifying a Custom Prefix and Selecting Schemas"

• Task 5, "Specifying Schema Passwords"

• Task 6, "Specifying Custom Variables"

• Task 7, "Verifying the Tablespaces for the Required Schemas"

• Task 8, "Creating 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.

1. In the Database Type, select Oracle Database enabled for edition-based redefinition.

   Note:

   Oracle Database enabled for edition-based redefinition (EBR) is recommended to support Zero Down Time upgrades. For more information, see https://www.oracle.com/database/technologies/high-availability/ebr.html.

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

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

4. Enter the RAC Service Name of the database.

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

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

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

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

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:

To start the Configuration Wizard:

Domain creation and configuration includes the following tasks:

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

• Task 2, "Selecting the Configuration Template"

• Task 3, "Configuring High Availability Options"

• Task 4, "Specifying the Database Configuration Type"

• Task 5, "Specifying JDBC Component Schema Information"

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

• Task 7, "Testing the JDBC Connections"

• Task 8, "Keystore"

• Task 9, "Selecting Advanced Configuration"

• Task 10, "Configuring Managed Servers"

• Task 11, "Configuring a Cluster"

• Task 12, "Assigning Server Templates"

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

• Task 15, "Configuring Coherence Clusters"

• Task 16, "Verifying the Existing Machines"

• Task 17, "Assigning Servers to Machines"

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

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

• Task 20, "Start the Administration Server"

Task 1   Selecting the Domain Type and Domain Home Location

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

In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the Administration Server domain home that you created 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 template, which does not implement the optimizations included in Reference Configuration is as follows:

• Oracle SOA Suite - 14.1.2.0.0. [soa]

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

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:

1. Select Enable Automatic Service Migration with Database Basis.

2. Set JTA Transaction Log Persistence to JDBC TLog Store.

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

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
Service Name	Verify that the service name for the Oracle RAC database is appropriate. For example, soaedg.example.com.
SCAN, Host Name, and Port	Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, 1521).
ONS Host and Port	These values are not required when you are using an Oracle 12c database or higher versions because the ONS list is automatically provided from the database to the driver.
Enable Fan	Verify that the Enable Fan check box is selected, so 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.

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

Table 12-1 Lists the Information to Provide for Each SOA Managed Server on the Configuration Wizard Managed Servers Screen

Server Name	Listen Address	Enable Listen Port	Listen Port	Enable SSL Port	SSL Listen Port	Administration Port	Server Groups
WLS_WSM1	SOAHOST1	Unchecked	Disabled	Checked	7010	9003	WSMPM-MAN-SVR and JRF-MAN-SVR
WLS_WSM2	SOAHOST2	Unchecked	Disabled	Checked	7010	9003	WSMPM-MAN-SVR and JRF-MAN-SVR
WLS_SOA1	SOAHOST1	Unchecked	Disabled	Checked	7004	9004	SOA-MGD-SVRS-ONLY
WLS_SOA2	SOAHOST2	Unchecked	Disabled	Checked	7004	9004	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 soa.example.com on the load balancer rather than the address in the HOST header of each request.

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:

1. Click the Add button.

2. Specify SOA_Cluster in the Cluster Name field.

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

4. Leave the Frontend HTTP Port blank and use 443 (or your precise LBS listeners port for app requests) 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.

1. Ensure that Calculated Machine Names and Calculated Listen Port checkboxes on this screen are unchecked.

2. Ensure the Server Template and Dynamic Server Groups selections are 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 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 to SOAHOST1, and assign WLS_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   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 19   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 Remote Console and Oracle Enterprise Manager Fusion Middleware Control.

Click Finish to dismiss the Configuration Wizard.

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

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

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

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:

To start the WLS_SOA1 Managed Server:

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.

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:

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.