4 Creating a Domain

This chapter describes how to create a domain using the Configuration Wizard, Oracle WebLogic Server Administration Console, Oracle Enterprise Manager, and Oracle WSM Policy Manager. You can extend the domain to add WebCenter components.

Important:

Oracle strongly recommends that you read the release notes for any additional installation and deployment considerations prior to starting the setup process.

In the Installation Complete screen, unselect Run QuickStart, and click Done.

4.1.2Installing Oracle Fusion Middleware for WebCenter

Perform these steps to install Oracle Fusion Middleware for WebCenter on SOAHOST1, SOAHOST2, WCHOST1, and WCHOST2.

On Linux platforms, if the /etc/oraInst.loc file exists, check that its contents are correct. Specifically, check that the inventory directory is correct and that you have write permissions for that directory.

If the /etc/oraInst.loc file does not exist, you can skip this step.

Start the installer for Oracle Fusion Middleware for WebCenter.

SOAHOST1> runInstaller

When the installer prompts you for a JRE/JDK location, enter the Oracle SDK location created in the Oracle WebLogic Server installation, for example, MW_HOME/jrockit_160_14_R27.6.4-18.

In the Specify Inventory Directory screen, do the following:

Enter HOME/oraInventory, where HOME is the home directory of the user performing the installation (this is the recommended location).

Enter the OS group for the user performing the installation.

Click Next.

Follow the instructions on screen to execute /createCentralInventory.sh as root. Click OK.

In the Welcome screen, click Next.

In the Prerequisite Check screen, verify that the checks complete successfully, and click Next.

Specify the installation location. Select the previously installed Middleware Home from the drop-down list. For the Oracle Home directory, enter the directory name (wc).

Click Next.

In the Specify UCM Configuration Options screen, clear the "Install and Configure Universal Content Management" check box. You will install Oracle Content Server (OCS) separately at a later stage.

Click Next.

In the Installation Summary screen, click Install.

In the Installation Complete screen, click Finish.

4.2Backing Up the Installation

The Fusion Middleware Home should be backed up now (make sure that you stop the server first):

SOAHOST1> tar -cvpf fmwhomeback.tar MW_HOME

This creates a backup of the installation files for both Oracle WebLogic Server and Oracle Fusion Middleware for WebCenter.

4.3Enabling VIP1 in SOAHOST1

Please note that this step is required for failover of the Administration Server, regardless of whether SOA is installed or not.

You are associating the Administration Server with a virtual hostname (SOAHOST1VHN1). This Virtual Host Name must be mapped to the appropriate VIP (VIP1) either by a DNS Server or by a custom /etc/host entry. Check that SOAHOST1VHN1 is available per your name resolution system, (DNS server, /etc/hosts), in the required nodes in your SOA topology. The VIP (VIP1) that is associated to this Virtual Host Name (SOAHOST1VHN11) must be enabled in SOAHOST1.

Enable your network to register the new location of the virtual IP, for example:

/sbin/arping -q -U -c 3 -I ethX 100.200.140.206

Validate that the address is available by pinging it from another node, for example:

/bin/ping 100.200.140.206

In this example 'ethX' is the ethernet interface (eth0 or eth1) and Y is the index (0, 1, 2, etc.).

4.4Running the Configuration Wizard on SOAHOST1 to Create a Domain

Run the Configuration Wizard from the WebCenter home directory to create a domain containing the Administration Server and Oracle Web Services Manager. Later, you will extend the domain to contain WebCenter components.

Ensure that the database where you installed the repository is running. For RAC databases, it is recommended that all instances are running, so that the validation check later on becomes more reliable.

Change directory to the location of the Configuration Wizard. This is within the WebCenter home directory.

SOAHOST1> cd MW_HOME/wc/common/bin

Start the Oracle Fusion Middleware Configuration Wizard:

SOAHOST1> ./config.sh

In the Welcome screen, select Create a New WebLogic Domain, and click Next.

If you accidentally deselect some of the targets, make sure that the following selections are made in this screen:

Oracle Enterprise Manager

Oracle WSM Policy Manager

Oracle JRF

Click Next.

Note:

If multiple Oracle Homes are installed (for example a WebCenter Home and a SOA Home), available products will show up for both homes. In this step, select only products from the WebCenter home (wc). This is indicated by brackets at the end of the product name; for example, "Oracle JRF - 11.1.1.0 [wc]."

In the Specify Domain Name and Location screen, enter the domain name (wcedg_domain).

Make sure that the domain directory matches the directory and shared storage mount point recommended in Chapter 2, "Database and Environment Preconfiguration": enter ORACLE_BASE/admin/<domain_name>/aserver/ for the domain directory and ORACLE_BASE/admin/<domain_name>/apps for the application directory. This directory should be in shared storage.

Click Next.

In the Configure Administrator Username and Password screen, enter the username and password to be used for the domain's administrator.

Service Name: Enter the service name of the database, for example, wcedg.mycompany.com.

Username: Enter the complete user name (including the prefix) for the schemas.

Password: Enter the password to use to access the schemas.

Enter the host name, instance name, and port.

Click Add.

Repeat this for each RAC instance.

Click Next.

In the Test JDBC Data Sources screen, the connections should be tested automatically. The Status column displays the results. Ensure that all connections were successful. If not, click Previous to return to the previous screen and correct your entries.

Click Next when all the connections are successful.

In the Select Advanced Configuration screen, select the following:

Administration Server

Managed Servers, Clusters and Machines

Deployment and Services

Click Next.

In the Configure the Administration Server screen, enter the following values:

Name: AdminServer

Listen Address: enter SOAHOST1VHN1.

Listen Port: 7001

SSL listen port: N/A

SSL enabled: unchecked

Click Next.

In the Configure Managed Servers screen, click Add to add the following managed servers:

Table 4-1 Managed Servers

Name

Listen Address

Listen Port

SSL Listen Port

SSL Enabled

WLS_WSM1

SOAHOST1

7010

n/a

No

WLS_WSM2

SOAHOST2

7010

n/a

No

Click Next.

In the Configure Clusters screen, Click Add to add the following clusters:

Table 4-2 Clusters

Name

Cluster Messaging Mode

Multicast Address

Multicast Port

Cluster Address

WSM-PM_Cluster

unicast

n/a

n/a

Leave it empty.

Click Next.

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

WSM-PM_Cluster:

WLS_WSM1

WLS_WSM2

Click Next.

In the Configure Machines screen, do the following:

Click the Unix Machine tab and then click Add to add the following machines:

Table 4-3 Machines

Name

Node Manager Listen Address

SOAHOST1

SOAHOST1

SOAHOST2

SOAHOST2

Leave all other fields to their default values.

Click Next.

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

SOAHOST1:

AdminServer

WLS_WSM1

SOAHOST2:

WLS_WSM2

Click Next.

In the Target Deployments to Clusters or Servers screen, make sure that the wsm-pm application and the oracle.wsm.seedpolicies library is targeted to the WSM-PM_Cluster only. Make sure that all other deployments are targeted to the AdminServer. Click Next.

In the Target Services to Clusters or Servers screen, select the following:

On the left, select WSM-PM_Cluster. On the right, select JDBC System Resource (this automatically selects all the wsm datasources (mds-owsm)).

On the left, select Admin Server. On the right, select JDBC System Resource (this automatically selects all the wsm datasources (mds-owsm)).

All JDBC system resources should be targeted to both the Admin Server and WSM-PM_Cluster.

On the left, select WSM-PM_Cluster. On the right, select JOC-Shutdown, JOC-Startup, and OWSM Startup Class.

On the left, select Admin Server. On the right, deselect JOC-Shutdown and JOC-Startup. Make sure these services are not targeted to the Admin Server.

JOC-Shutdown, JOC-Startup, and OWSM Startup Class should be targeted only to the WSM-PM_Cluster.

Make sure that all the remaining services are targeted to the Admin Server.

In the Configuration Summary screen, click Create.

In the Create Domain screen, click Done.

4.5Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server

4.6Creating boot.properties for the Administration Server on SOAHOST1

Create a boot.properties file for the Administration Server on SOAHOST1. The boot.properties file enables the Administration Server to start without prompting you for the administrator username and password.

For security reasons, you want to minimize the time the entries in the file are left unencrypted: after you edit the file, you should start the server as soon as possible so that the entries get encrypted.

On the navigation tree on the left, expand Farm_<domain_name>, WebLogic Domain, and then <domain_name>, and select WSM_PM_Cluster.

Click Apply JRF Template on the right.

Wait for the confirmation message to appear on the screen.

This message should confirm that the JRF Template has been successfully applied to the WSM-PM_Cluster cluster.

4.10Disabling Host Name Verification for the Oracle WebLogic Administration Server and the WLS_WSM1 Managed Server

This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server (see Chapter 7, "Setting Up Node Manager"). If you have not configured the server certificates, you will receive errors when managing the different WebLogic Servers. To avoid these errors, disable host name verification while setting up and validating the topology, and enable it again once the EDG topology configuration is complete as described in Chapter 7, "Setting Up Node Manager."

Perform these steps to disable host name verification:

Log in to Oracle WebLogic Server Administration Console.

Click Lock and Edit.

Expand the Environment node in the Domain Structure window.

Click Servers. The Summary of Servers page appears.

Select AdminServer(admin) in the Names column of the table. The Settings page for AdminServer(admin) appear.

Click the SSL tab.

Click Advanced.

Set Hostname Verification to None.

Click Save.

Repeat steps 4 to 8 for the WLS_WSM1 server.

Save and activate the changes.

The change requires restart of the Administration Server to be effective. To do this, complete these steps:

In the Summary of Servers screen, select the Control tab.

Select AdminServer(admin) in the table and then click Shutdown.

Start the Administration Server again from the command line as follows:

Verify that the server status is reported as "Running" in the Admin Console. If the server is shown as "Starting" or "Resuming," wait for the server status to change to "Started." If another status is reported (such as "Admin" or "Failed"), check the server output log files for errors. See Section 11.5, "Troubleshooting" for possible causes.

Access http://SOAHOST1:7010/wsm-pm.

Click Validate Policy Manager. A list of policies and assertion templates available in the data store appear.

Note:

The configuration is incorrect if no policies or assertion templates appear.

4.13Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility

Perform these steps to propagate the domain configuration:

Run the following command on SOAHOST1 to copy the template file created previously.

The ORACLE_BASE/admin/<domain_name>/mserver directory must exist before running unpack.

4.14Disabling Host Name Verification for the WLS_WSM2 Managed Server

This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server (see Chapter 7, "Setting Up Node Manager"). If you have not configured the server certificates, you will receive errors when managing the different WebLogic Servers. To avoid these errors, disable host name verification while setting up and validating the topology, and enable it again once the EDG topology configuration is complete as described in Chapter 7, "Setting Up Node Manager."

Perform these steps to disable host name verification:

Log in to Oracle WebLogic Server Administration Console.

Click Lock and Edit.

Expand the Environment node in the Domain Structure window.

Click Servers. The Summary of Servers page appears.

Select WLS_WSM2 in the Names column of the table. The Settings page for AdminServer(admin) appear.

Click the SSL tab.

Click Advanced.

Set Hostname Verification to None.

Save and activate the changes.

4.15Starting Node Manager on SOAHOST2

Perform these steps to start Node Manager on SOAHOST2:

Run the setNMProps.sh script, which is located in the ORACLE_COMMON_HOME/common/bin directory, to set the StartScriptEnabled property to 'true' before starting Node Manager:

SOAHOST2> cd ORACLE_COMMON_HOME/common/bin
SOAHOST2> ./setNMProps.sh

Note:

You must use the StartScriptEnabled property to avoid class loading failures and other problems.

Start Node Manager:

SOAHOST2> cd WL_HOME/server/bin
SOAHOST2> ./startNodeManager.sh

4.16Starting and Validating the WLS_WSM2 Managed Server

Perform these steps to start the WLS_WSM2 managed server and check that it is configured correctly:

Start the WLS_WSM2 managed server using the Administration Console.

Verify that the server status is reported as "Running" in the Admin Console. If the server is shown as "Starting" or "Resuming," wait for the server status to change to "Started." If another status is reported (such as "Admin" or "Failed"), check the server output log files for errors. See Section 11.5, "Troubleshooting" for possible causes.

Access http://SOAHOST2:7010/wsm-pm.

Click validate policy manager.

4.17 Configuring the Java Object Cache for Oracle WSM

The Java Object Cache (JOC) should be configured among all the servers running Oracle WSM. This local cache is provided to increase the performance of Oracle WSM.

The Java Object Cache can be configured using the MW_HOME/oracle_common/bin/configure-joc.py script. This is a Python script which can be used to configure JOC in the managed servers. The script runs in WLST online mode and expects the Administration Server to be up and running.

When configuring JOC ports for Oracle products, Oracle recommends using ports in the 9988 to 9998 range.

Note:

After configuring the Java Object Cache using the wlst commands or configure-joc.py script, all affected managed servers should be restarted for the configurations to take effect.

Usage

Connect to the Administration Server using the command-line Oracle WebLogic Scripting Tool (WLST), for example:

MW_HOME/soa/common/bin/wlst.sh
$ connect()

Enter the Oracle WebLogic Administration user name and password when prompted.

After connecting to the Administration Server using wlst, start the script using the execfile command, for example:

Enter 'y' when the script prompts whether you want to specify a cluster name, and also specify the cluster name and discover port, when prompted. This discovers all the managed servers for the given cluster and configure the JOC. The discover port is common for the entire JOC configuration across the cluster. For example:

Do you want to specify a cluster name (y/n) <y>
Enter Cluster Name : WSM_Cluster
Enter Discover Port : 9991

The script allows you to specify the list of managed servers for which the JOC configuration "DistributeMode" will be set to 'false'. Enter 'y' when the script prompts whether you want to exclude any servers from JOC configuration, and enter the managed server names to be excluded, when prompted. For example:

The script allows you to disable the distribution to all the managed servers for a specified cluster. Specify 'false' when the script prompts for the distribution mode. By default, the distribution mode is set to 'true'.

4.18Configuring Oracle HTTP Server for the Administration Server and the WLS_WSM-PMn Managed Servers

To enable Oracle HTTP Server to route to the Administration Server and the WSM-PM_Cluster, which contain the WLS_WSM-PMn managed servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster:

On WEBHOST1 and WEBHOST2, add the following lines to the ORACLE_BASE/admin/<instance_name>/config/OHS/<component_name>/mod_wl_ohs.conf file:

The servers specified in the WebLogicCluster parameter are only important at startup time for the plug-in. The list needs to provide at least one running cluster member for the plug-in to discover other members of the cluster. Note that the listed cluster member must be running when Oracle HTTP Server is started. Oracle WebLogic Server and the plug-in work together to update the server list automatically with new, failed, and recovered cluster members.

Some example scenarios:

Example 1: If you have a two-node cluster and then add a third member, you do not need to update the configuration to add the third member. The third member will be discovered on the fly at runtime.

Example 2: You have a three-node cluster but only two nodes are listed in the configuration. However, if both listed nodes are down when you start Oracle HTTP Server, then the plug-in would fail to route to the cluster. You must ensure that at least one of the listed nodes is running when you start Oracle HTTP Server.

If you list all members of the cluster, then you guarantee you can route to the cluster, assuming at least one member is running when Oracle HTTP Server is started.

4.20Setting the Frontend URL for the Administration Console and Setting Redirection Preferences

When you access the Oracle WebLogic Server Administration Console using an LRB, changing the Administration Server's frontend URL is required so that the user's browser is redirected to the appropriate LRB address. To change the Administration Server's frontend URL, complete these steps:

Log in to Oracle WebLogic Server Administration Console.

Click Lock and Edit.

Expand the Environment node in the Domain Structure window.

Click Servers to open the Summary of Servers page.

Select Admin Server in the Names column of the table. The Settings page for AdminServer(admin) appear.

Click the Protocols tab.

Click the HTTP tab.

Set the Front End Hist field to soa.mycompany.com (your LBR address).

Save and activate the changes.

Oracle also recommends disabling tracking on configuration changes in the Oracle WebLogic Server Administration Console so that the console does not trigger the reload of configuration pages when activation of changes occurs. To disable the reload, log in to the Oracle WebLogic Server Administration Console, click the preferences link in the banner, and then the shared preferences tab. Deselect the follow configuration changes checkbox.

4.21Validating Access Through Oracle HTTP Server

Verify that the server status is reported as "Running" in the Admin Console. If the server is shown as "Starting" or "Resuming," wait for the server status to change to "Started." If another status is reported (such as "Admin" or "Failed"), check the server output log files for errors. See Section 11.5, "Troubleshooting" for possible causes.

Validate WSM_Cluster through both Oracle HTTP Server using the following URLs:

After the registering Oracle HTTP Server as described in Section 4.19, "Registering Oracle HTTP Server With WebLogic Server," the Oracle HTTP Server should appear as a manageable target in the Oracle Enterprise Manager Console. To verify this, log into the Enterprise Manager Console. The WebTier item in the navigation tree should show that Oracle HTTP Server has been registered.

4.22Manually Failing Over the Administration Server to SOAHOST2

In case a node fails, you can fail over the Administration Server to another node. This section describes how to fail over the Administration Server from SOAHOST1 to SOAHOST2.

These procedures assume that the two nodes use two individual domain directories, and that the directories reside in local storage or in shared storage in different volumes.

The Administration Server is failed over from SOAHOST1 to SOAHOST2, and the two nodes have these IPs:

SOAHOST1: 100.200.140.165

SOAHOST2: 100.200.140.205

VIPHOST1: 100.200.140.206. This is the VIP where the Administration Server is running, assigned to ethX:Y, available in SOAHOST1 and SOAHOST2.

The domain directory where the Administration Server is running in SOAHOST1 is on a shared storage and is mounted also from SOAHOST2.

The following procedure shows how to fail over the Administration Server to a different node (SOAHOST2), but the Administration Server will still use the same WebLogic Server machine (which is a logical machine, not a physical machine).

Stop the Administration Server.

Migrate IP to the second node.

Run the following command as root on SOAHOST1 (where X:Y is the current interface used by SOAHOST1VHN1):

Test that you can access the Administration Server on SOAHOST2 as follows:

Ensure that you can access the Oracle WebLogic Server Administration Console at http://SOAHOST1VHN1:7001/console.

Check that you can access and verify the status of components in the Oracle Enterprise Manager at http://SOAHOST1VHN1:7001/em.

Note:

The Administration Server does not use Node Manager for failing over. After a manual failover, the machine name that appears in the Current Machine field in the Administration Console for the server is SOAHOST1, and not the failover machine, SOAHOST2. Since Node Manager does not monitor the Administration Server, the machine name that appears in the Current Machine field, is not relevant and you can ignored it.