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

16 Extending the Domain with Oracle Enterprise Scheduler

The procedures explained in this chapter guide you through the process of extending the enterprise deployment domain with the Oracle Enterprise Scheduler software.

Parent topic: Configuring the Enterprise Deployment

About Adding Oracle Enterprise Scheduler

Before you add Oracle Enterprise Scheduler to a SOA domain, familiarize yourself with the high-level steps that you have to perform to complete the extension process.

Table 16-1 lists and describes the high-level steps to extend a SOA domain with Oracle Enterprise Scheduler.

Table 16-1 Steps for Extending a SOA Domain to Include Oracle Enterprise Scheduler

Step Description More Information

Create Database Schemas for ESS

Navigate the RCU screens to create the database schemas.

Creating the Database Schemas for ESS

Run the Configuration Wizard to Extend the Domain

Extend the SOA/OSB domain to contain Oracle Enterprise Scheduler components.

Extending the SOA Domain to Include Oracle Enterprise Scheduler

Propagate the Domain Configuration to the Managed Server Directory in SOAHOST1 and to SOAHOST2

Oracle Enterprise Scheduler requires some updates to the WebLogic Server start scripts. Propagate these changes by using the pack and unpack commands.

Propagating the Extended Domain to the Domain Directories and Machines

Start the Oracle Enterprise Scheduler Servers

Oracle Enterprise Scheduler servers extend an already existing domain. As a result, the Administration Server and respective Node Managers are already running in SOAHOST1 and SOAHOST2.

Starting WLS_ESS1 Managed Server

Validate the WLS_ESS Managed Servers

Verify that the server status is reported as Running in the Admin Console and access URLs to verify status of servers.

Starting and Validating the WLS_ESS2 Managed Server

Configuring Oracle HTTP Server for the WLS_ESSn Managed Servers

To enable Oracle HTTP Server to route to Oracle Enterprise Scheduler console and service, set the WebLogicCluster parameter to the list of nodes in the cluster.

Configuring Oracle HTTP Server for the WLS_ESS Managed Servers

Validating Access Through Oracle HTTP Server

Verify that the server status is reported as Running.

Validating Access to Oracle Enterprise Scheduler Through the Hardware Load Balancer

Backing up the Oracle Enterprise Scheduler

To back up the domain configuration for immediate restoration in case of failures in future procedures.

Backing Up the Oracle Enterprise Scheduler Configuration

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

Variables Used When Configuring Oracle Enterprise Scheduler

As you perform the tasks in this chapter, you reference the directory variables that are 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

  • WEB_DOMAIN_HOME

In addition, you reference the following virtual IP (VIP) addresses that are defined in Physical and Virtual IP Addresses Required by the Enterprise Topology:

  • ADMINVHN

Actions in this chapter are performed on the following host computers:

  • SOAHOST1

  • SOAHOST2

  • WEBHOST1

  • WEBHOST2

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

Support for Dynamic Clusters in Oracle Enterprise Scheduler

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

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

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

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

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

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

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

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

Creating the Database Schemas for ESS

Before you can configure an Oracle ESS server, you must install the required schemas on a certified database for use with this release of Oracle Fusion Middleware.

Follow the instructions in these sections to install the schemas.

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

Starting the Repository Creation Utility (RCU)

To start the Repository Creation Utility (RCU):

  1. Navigate to the ORACLE_HOME/oracle_common/bin directory on your system.
  2. Make sure that the JAVA_HOME environment variable is set to the location of a certified JDK on your system. The location should be up to but not including the bin directory. For example, if your JDK is located in /u01/oracle/products/jdk:

    On UNIX operating systems:

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

    On UNIX operating systems:

    ./rcu

    Note:

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

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

Parent topic: Creating the Database Schemas for ESS

Navigating the RCU Screens to Create the Enterprise Scheduler Schemas

Schema creation involves the following tasks:

Task 1   Introducing RCU

Click Next.

Task 2   Selecting a Method of Schema Creation

If you have the necessary permission and privileges to perform DBA activities on your database, select Create Repository > 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. 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 Host Name field, enter the SCAN address of the Oracle RAC Database.

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

  3. Enter the RAC Service Name of the database.

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

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

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

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

Task 4   Specifying a Custom Prefix and Selecting Schemas

Select Select existing prefix and specify the prefix you used for the original domain creation schemas.

Expand the Oracle AS Common Schemas and then select the Oracle Enterprise Scheduler in the component list.

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.

Tip:

You must make a note of the custom prefix you choose to enter here; you need this later on during the domain creation process.

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

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 you set on this screen; you need them later on during the domain creation process.

Click Next.

Task 6   Verifying the Tablespaces for the Required Schemas

Click Next in the Default and temporary tablespaces selection (accept defaults), and click in the confirmation Pop-up window that warns about tablespaces that are being created.

Task 7   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 8   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 Database Schemas for ESS

Verifying Schema Access

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

For example:

./sqlplus

SQL*Plus: Release 12.1.0.2.0 Production on Wed Mar 15 03:17:54 2017

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

Enter user-name: FMW1221_ESS
Enter password: ess_password
Last Successful login time: Tue Feb 28 2017 09:37:25 -07:00

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

SQL>

Parent topic: Creating the Database Schemas for ESS

Extending the SOA Domain to Include Oracle Enterprise Scheduler

You can use the Configuration Wizard to configure and extend the existing enterprise deployment SOA domain with Oracle Enterprise Scheduler. You also need to perform additional tasks to complete the extension.

Extending the domain involves the following tasks.

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

Starting the Configuration Wizard

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 you use the pack and unpack commands.

To begin domain configuration:

  1. Shut down the Administration Server to prevent any configuration locks, saves, or activations from occurring during the configuration of the domain.
  2. Navigate to the following directory and start the WebLogic Server Configuration Wizard.
    ORACLE_HOME/oracle_common/common/bin
./config.sh

Parent topic: Extending the SOA Domain to Include Oracle Enterprise Scheduler

Navigating the Configuration Wizard Screens to Extend the Domain with Oracle Enterprise Scheduler

Follow the instructions in the following sections to extend the domain for Oracle Enterprise Scheduler, with static or dynamic clusters.

Parent topic: Extending the SOA Domain to Include Oracle Enterprise Scheduler

Extending the Domain with Static Clusters

In this step, you extend the domain created in Extending the Domain with Oracle SOA Suite to contain Oracle Enterprise Scheduler components.

The steps reflected in this section are very similar to the steps required to extend an Oracle Fusion Middleware Infrastructure domain directly, but some of the options, libraries, and components shown in the screens will vary.

Domain creation and configuration includes the following tasks:

Task 1   Selecting the Domain Type and Domain Home Location

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

In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the Administration Server domain home you created 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

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 Enterprise Scheduler Service Basic - 12.2.1.3.0 [oracle_common]

Oracle Enterprise Manager Plugin for ESS - 12.2.1.3.0 [em]

Click Next.

Task 3   Specifying the Database Configuration Type

On the Database Configuration Type screen, select RCU Data.

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

  • Verify that 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.

Note:

Any custom datasources that were created before the extension (such as LEASING datasources) will show up before this screen. Check the Datasources row and click Next. The test datasource screen will verify its validity. Click Next.

Click Get RCU Configuration after you finish verifying the database connection information. The following output in the Connection Result Log indicates that the operation succeeded: 

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

Tip:

More information about the RCU Data option can be found in Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

More information about the other options on this screen can be found in Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard.

Task 4   Specifying JDBC Component Schema Information

Select the ESS Schema and ESS MDS Schema.

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

Click Convert to GridLink and click Next.

Task 5   Providing the GridLink Oracle RAC Database Connection Details

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

Element Description and Recommended Value

SCAN, Host Name, and Port

Select the SCAN check box.

In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database.

In the Port field, enter the SCAN listening port for the database (for example, 1521)

ONS Host and Port

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

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

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

Enable Fan

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

Task 6   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source connections you have just configured.

A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.

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

Task 7   Selecting Advanced Configuration

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

Task 8   Configuring Managed Servers

On the Managed Servers screen, add the required managed servers for Enterprise Scheduler.

  • Select the automatically created server and click Rename to change the name to WLS_ESS1.

  • Click Add to add another new server and enter WLS_ESS2 as the server name.

  • Give servers WLS_ESS1 and WLS_ESS2 the attributes listed in Table 16-2.

Click Next.

Table 16-2 Managed Servers

Name Listen Address Listen Port SSL Listen Port SSL Enabled Server Groups

WLS_SOA1

SOAHOST1

8001

n/a

No

SOA-MGD-SVRS-ONLY

WLS_SOA2

SOAHOST2

8001

n/a

No

SOA-MGD-SVRS-ONLY

WLS_WSM1

SOAHOST1

7010

n/a

No

JRF-MAN-SVR

WSMPM-MAN-SVR

WLS_WSM2

SOAHOST2

7010

n/a

No

JRF-MAN-SVR

WSMPM-MAN-SVR

WLS_OSB1

SOAHOST1

8011

n/a

No

OSB-MGD-SVRS-ONLY

WLS_OSB2

SOAHOST2

8011

n/a

No

OSB-MGD-SVRS-ONLY

WLS_ESS1

SOAHOST1

8021

n/a

No

ESS-MGD-SVRS

WLS_ESS2

SOAHOST2

8021

n/a

No

ESS-MGD-SVRS

Note:

  • The WLS_SOA Managed Servers appear only if you are extending a domain where Oracle SOA Suite has been configured.

  • The WLS_OSB Managed Servers appear only if you are extending a domain where Oracle Service Bus has been configured.

Task 9   Configuring a Cluster

On the Configure Clusters screen, add the ESS_Cluster cluster, by using the values for each cluster as shown in Table 22-1.

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

Click Next.

Task 10   Assigning Server Templates

Click Next.

Task 11   Configuring Dynamic Servers

Click Next.

Task 12   Assigning Managed Servers to the Cluster

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

  • SOA_Cluster - If you are extending a SOA domain.

    • WLS_SOA1

    • WLS_SOA2

  • WSM-PM_Cluster:

    • WLS_WSM1

    • WLS_WSM2

  • OSB_Cluster - If you are extending an OSB domain:

    • WLS_OSB1

    • WLS_OSB2

  • ESS_Cluster:

    • WLS_ESS1

    • WLS_ESS2

Click Next.

Task 13   Configuring Coherence Clusters

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

Task 14   Verifying the Existing Machines

On the Unix Machines tab, confirm that the following entries appear:

Name Node Manager Listen Address

SOAHOST1

SOAHOST1

SOAHOST2

SOAHOST2

ADMINHOST

ADMINVHN

Leave all other fields to their default values.

Click Next.

Task 15   Assigning Servers to Machines

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

  • ADMINHOST:

    • AdminServer

  • SOAHOST1

    • WLS_SOA1 (if extending a SOA domain)

    • WLS_WSM1

    • WLS_OSB1 (if extending an OSB domain)

    • WLS_ESS1

  • SOAHOST2

    • WLS_SOA2 (if extending a SOA domain)

    • WLS_WSM2

    • WLS_OSB2 (if extending an OSB domain)

    • WLS_ESS2

Click Next..

Task 16   Configuring Virtual Targets

Click Next to continue.

Task 17   Configuring Partitions

Click Next to continue.

Task 18   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain 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 will show the following items about the domain you just configured, including:

  • Domain Location

  • Administration Server URL

Make a note of both these items, because you will need them later; you will need the domain location to access the scripts used to start the Administration Server, and you will 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 20   Start the Administration Server

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

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

Extending the Domain with Dynamic Clusters

In this step, you extend the domain that were created in Extending the Domain with Oracle SOA Suite to contain Oracle Enterprise Scheduler components.

The steps reflected in this section are very similar to the steps required to extend an Oracle Fusion Middleware Infrastructure domain directly, but some of the options, libraries, and components shown in the screens vary.

Domain creation and configuration includes the following tasks:

Task 1   Selecting the Domain Type and Domain Home Location

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

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

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

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 that the Update Domain Using Product Templates is selected, and then select the following templates:

  • Oracle Enterprise Scheduler Service Basic - 12.2.1.3.0 [oracle_common]

  • Oracle Enterprise Manager Plugin for ESS - 12.2.1.3.0 [em]

Click Next.

Task 3   Specifying the Database Configuration Type

On the Database Configuration Type screen, select RCU Data.

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

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

  • Verify that Connection Parameters is selected.

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

Note:

Any custom datasources that were created before the extension (such as LEASING datasources) shows up before this screen. Check the Datasources row and click Next. The test datasource screen verifies its validity. Click Next.

Click Get RCU Configuration after you finish verifying the database connection information. The following output in the Connection Result Log indicates that the operation succeeded: 

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

Tip:

More information about the RCU Data option can be found in Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

More information about the other options on this screen can be found in Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard.

Task 4   Specifying JDBC Component Schema Information

Select the ESS Schema and ESS MDS Schema.

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

Click Convert to GridLink, and then click Next.

Task 5   Providing the GridLink Oracle RAC Database Connection Details

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

Element Description and Recommended Value

SCAN, Host Name, and Port

Select the SCAN check box.

In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database.

In the Port field, enter the SCAN listening port for the database (for example, 1521).

ONS Host and Port

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

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

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

Enable Fan

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

Task 6   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source connections you have just configured.

A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.

Tip:

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

Task 7   Selecting Advanced Configuration

To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:

  • Topology

    Add, Delete, or Modify Settings for Server Templates, Managed Servers, Clusters, Virtual Targets, and Coherence.

Task 8   Configuring Managed Servers

On the Managed Servers screen, a new Managed Server for Oracle Enterprise Scheduler appears in the list of servers.

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

  1. Delete the default Managed Server.

  2. Click Next to proceed to the next screen.

Task 9   Configuring a Cluster

On the Configure Clusters screen, add the ESS_Cluster cluster by using the values for each property shown in the following table.

Name Cluster Address Frontend Host Frontend HTTP Port Frontend HTTPs

SOA_Cluster

Leave it empty

soa.example.com

80

443

WSM-PM_Cluster

Leave it empty

Leave it empty

Leave it empty

Leave it empty

OSB_Cluster

Leave it empty

osb.example.com

80

443

ESS_Cluster

Leave it empty

soa.example.com

80

443

From the Dynamic Server Groups drop-down list, select ESS-DYN-CLUSTER.

Click Next.

Note:

  • The SOA_Cluster cluster appears only if you are extending a domain where Oracle SOA Suite has been configured.

  • The OSB_Cluster cluster appears only if you are extending a domain where Oracle Service Bus has been configured.

Task 10   Assigning Server Templates

Use the Server Templates screen to configure the template:

  1. Verify that ESS-server-template in selected in Name field.

  2. Specify 8020 in the Listen Port field.

  3. Leave the Enable SSL option unchecked.

  4. Click Next.

Task 11   Configuring Dynamic Servers

Use the Dynamic Clusters screen to configure the required clusters:

  1. Specify ESS_Cluster in the Cluster Name field.

  2. Specify WLS_ESS in the Server Name Prefix field.

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

  4. Specify 2 in the Dynamic Cluster Size field.

  5. 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 you with two cluster members that run on the same physical server but are attached to two different domain homes.

  6. Select the Calculated Listen Ports and Dynamic Cluster fields.

    Note:

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

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

    • WLS_ESS1 server listens in 8021 port

    • WLS_ESS2 server listens in 8022 port

  7. Click Next.

Note:

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

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

Task 13   Verifying the Existing Machines

On the Unix Machines tab, confirm that the following entries appear:

Name Node Manager Listen Address

SOAHOST1

SOAHOST1

SOAHOST2

SOAHOST2

ADMINHOST

ADMINVHN

Leave all other fields with their default values.

Click Next.

Task 14   Assigning Servers to Machines

Click Next.

Task 15   Configuring Virtual Targets

Click Next.

Task 16   Configuring Partitions

Click Next.

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

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

Task 18   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 19   Start the Administration Server

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

Propagating the Extended Domain to the Domain Directories and Machines

After you have extended the domain with the ESS instances, and you have restarted the Administration Server on SOAHOST1, you must then propagate the domain changes to the domain directories and machines.

The following table summarizes the steps that are required to propagate the changes to all the domain directories and machines.

Task Description More Information

Pack up the Extended Domain on SOAHOST1

Use the pack command to create a new template jar file that contains the new ESS Servers configuration.

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

Packing Up the Extended Domain on SOAHOST1

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 SOAHOST2 local storage.

Unpacking the Domain on SOAHOST2

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

Adding the ESSAdmin Role to the SOA Administrators Group

Before you validate the Oracle Enterprise Scheduler configuration on the WLS_ESS1 Managed Server, add the ESSAdmin role to the enterprise deployment administration group (SOA Administrators).

To perform this task, refer to Configuring Roles for Administration of Oracle SOA Suite Products.

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

Starting and Validating the WLS_ESS1 Managed Server

Now that you have extended the domain, restarted the Administration Server, and propagated the domain to the other hosts, you can start the newly configured ESS servers.

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

    In this example:

    • Replace ADMINVHN with the host name assigned to the ADMINVHN Virtual IP address in Identifying and Obtaining Software Downloads for an Enterprise Deployment.

    • Port 7001 is the typical port used for the Administration Server console and Fusion Middleware Control. However, you should use the actual URL that was displayed at the end of the Configuration Wizard session when you created the domain.

  2. Log in to Fusion Middleware Control by using the Administration Server credentials.
  3. In the Target Navigation pane, expand the domain to view the Managed Servers in the domain.
  4. Select only the WLS_ESS1 Managed Server, and click Start Up on the Oracle WebLogic Server tool bar.

    Note:

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

  5. When the startup operation is complete, navigate to the Domain home page and verify that the WLS_ESS1 Managed Server is up and running.
  6. To verify the ESS software is configured, enter the following URL in the browser:
    http://SOAHOST1:8021/EssHealthCheck/

    With the default installation, this should be the HTTP response, as shown in the following image.

    Description of ess_httpresponse.gif follows
    Description of the illustration ess_httpresponse.gif

    Click on the Check Health button, and then log in by using the welogic_soa administration credentials.

    The reply should report that Oracle Enterprise Schedule (ESS) is up and running.

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

Starting and Validating the WLS_ESS2 Managed Server

After you start the WLS_ESS2 managed server, you must verify that the server status is reported as Running in the Admin Console and access the URLs to verify the status of servers.

Perform the same steps that you used to start WLS_ESS1, to start WLS_ESS2.

  1. Log in to Fusion Middleware Control by using the Administration Server credentials.
  2. In the Target Navigation pane, expand the domain to view the Managed Servers in the domain.
  3. Select only the WLS_ESS2 Managed Server, and click Start Up on the Oracle WebLogic Server tool bar.
  4. When the startup operation is complete, navigate to the Domain home page and verify that the WLS_ESS2 Managed Server is up and running, access the equivalent URLs for the WLS_ESS2:

    For static clusters: 

    http://SOAHOST2:8021/EssHealthCheck/

    For dynamic clusters: 

    http://SOAHOST2:8022/EssHealthCheck/

    Click the Check Health button, and then log in by using the welogic_soa administration credentials.

    The reply reports that Oracle Enterprise Scheduler is up and running.

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

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. See Modifying the Upload and Stage Directories to an Absolute Path in an Enterprise Deployment.

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

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 Enterprise Scheduler

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.

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

Configuring Oracle Traffic Director for the Extended Domain

If you have configured Oracle Traffic Director for this domain, you might be required to add additional origin server pools, virtual servers, or routes to the Oracle Traffic Director configuration. To understand the Oracle Traffic Director requirements for each Oracle Fusion Middleware product and for instructions on adding origin server pools, virtual servers, and routes, see Defining Oracle Traffic Director Virtual Servers for an Enterprise Deployment.

Parent topic: Configuring the Web Tier for the Extended Domain

Configuring Oracle HTTP Server for the WLS_ESS Managed Servers

Make the following modifications to the Oracle HTTP Server instance configuration files to ensure that the Oracle HTTP Server instances in the web tier can route Oracle Enterprise Scheduler requests correctly to the WLS_ESS Managed Servers on SOHOST1 and SOAHOST2.

To enable Oracle HTTP Server to route Oracle Enterprise Scheduler requests to the application tier:

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

    Note:

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

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

    <Location /ess >
  WLSRequest ON
  WebLogicCluster SOAHOST1:8021,SOAHOST2:8021
  WLProxySSL ON
  WLProxySSLPassThrough ON
</Location>

<Location /EssHealthCheck >
  WLSRequest ON
  WebLogicCluster SOAHOST1:8021,SOAHOST2:8021
  WLProxySSL ON
  WLProxySSLPassThrough ON
</Location>

<Location /ess-async >
    WLSRequest ON
    WebLogicCluster SOAHOST1:8021,SOAHOST2:8021
    WLProxySSL ON
    WLProxySSLPassThrough ON  
</Location>

<Location /ess-wsjob >
    WLSRequest ON
    WebLogicCluster SOAHOST1:8021,SOAHOST2:8021
    WLProxySSL ON
    WLProxySSLPassThrough ON
</Location>
  3. Log in to SOAHOST2 and change directory to the following location so you can update the configuration file for the second Oracle HTTP Server instance (ohs2):
    cd WEB_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs2/moduleconf
  4. Open the soa_vh.conf file and add the Oracle Business Process Management directives to the <VirualHost> tag.
  5. Restart Oracle HTTP Servers on WEBHOST1 and WEBHOST2.

Parent topic: Configuring the Web Tier for the Extended Domain

Configuring the WebLogic Proxy Plug-In

Set the WebLogic Plug-In Enabled parameter for the ESS cluster.

  1. Log in to the Oracle WebLogic Server Administration console.
  2. In the Domain Structure pane, expand the Environment node.
  3. Click on Clusters.
  4. Select the ESS_Cluster cluster to which you want to proxy requests from Oracle HTTP Server.

    The Configuration: General tab is displayed.

  5. Scroll down to the Advanced section, expand it.
  6. Click Lock and Edit.
  7. Set the WebLogic Plug-In Enabled to yes.
  8. Click Save, and then click Activate Changes.
  9. Restart the ESS servers for the changes to be effective.

Parent topic: Configuring the Web Tier for the Extended Domain

Validating Access to Oracle Enterprise Scheduler Through the Hardware Load Balancer

Verify the URLs to ensure that appropriate routing and failover is working from the HTTP Server to the Oracle ESS components.

To verify the URLs:

  1. While WLS_ESS1 is running, stop WLS_ESS2 by using the Oracle WebLogic Server Administration Console.
  2. Access the following URL from your web browser, and verify the HTTP response as indicated in Starting and Validating the WLS_ESS2 Managed Server:
    https://soa.example.com/EssHealthCheck
  3. Start WLS_ESS2 from the Oracle WebLogic Server Administration console.
  4. Stop WLS_ESS1 from the Oracle WebLogic Server Administration console.
  5. Verify these URLs by using your load balancer address:
    https://soa.example.com:443/EssHealthCheck
https://soa.example.com/ess

Parent topic: Extending the Domain with Oracle Enterprise Scheduler

Backing Up the Configuration

It is an Oracle best practices recommendation to create a backup after you successfully extend 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 in the SOA Enterprise Deployments.

Parent topic: Extending the Domain with Oracle Enterprise Scheduler