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, "Verifying the Tablespaces for the Required Schemas"

• Task 7, "Creating Schemas"

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

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.

To begin domain configuration:

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:

• "Selecting the Domain Type and Domain Home Location"

• "Selecting the Configuration Template"

• "Specifying the Database Configuration Type"

• "Specifying JDBC Component Schema Information"

• "Providing the GridLink Oracle RAC Database Connection Details"

• "Testing the JDBC Connections"

• "Selecting Advanced Configuration"

• "Configuring Managed Servers"

• "Configuring a Cluster"

• "Assigning Server Templates"

• "Configuring Dynamic Servers"

• "Assigning Managed Servers to the Cluster"

• "Configuring Coherence Clusters"

• "Verifying the Existing Machines"

• "Assigning Servers to Machines"

• "Reviewing Your Configuration Specifications and Configuring the Domain"

• "Writing Down Your Domain Home and Administration Server URL"

• "Start the Administration Server"

Task

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.

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 [oracle_common]

• Oracle Enterprise Manager Plugin for ESS [em]

Click Next.

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.

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.

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

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.

Selecting Advanced Configuration

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

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

Click Next.

Table 15-2 Managed Servers

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

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.

Configuring a Cluster

On the Configure Clusters screen, add the ESS_Cluster cluster, by using the values for each cluster as shown in Table 19-1 in Setting the Front End Host and Port for a WebLogic Cluster.

Click Next.

Assigning Server Templates

Click Next.

Configuring Dynamic Servers

Click Next.

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.

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.

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.

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.

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.

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

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, go to Propagating the Extended Domain to the Domain Directories and Machines.

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