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.

This chapter contains the following sections:

4.1 Installing Oracle Fusion Middleware Home

As described in Section 2.3, "Shared Storage and Recommended Directory Structure," you install Oracle Fusion Middleware in at least two storage locations for redundancy.

You must install the following components of Oracle Fusion Middleware:

4.1.1 Installing Oracle WebLogic Server

Perform these steps to install Oracle WebLogic Server on SOAHOST1, SOAHOST2, WCHOST1,and WCHOST2.

  1. Start the Oracle WebLogic Server installer.

  2. In the Welcome screen, click Next.

  3. In the Choose Middleware Home Directory screen, do the following:

    Click Next.

  4. In the Register for Security Updates screen, enter your contact information so that you can be notified of security updates, and click Next.

  5. In the Choose Install Type screen, select Custom, and click Next.

  6. In the Choose Products and Components screen, click Next.

  7. In the JDK Selection screen, select only Oracle JRockit 1.6.0_05 SDK, and click Next.

  8. In the Choose Product Installation Directories screen, accept the directory ORACLE_BASE/product/fmw/wlserver_10.3, and click Next.

  9. In the Installation Summary screen, click Next.

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

4.1.2 Installing Oracle Fusion Middleware for WebCenter

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

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

  2. 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, ORACLE_BASE/product/fmw/jrockit_160_05_R27.6.2-20.

  3. In the Specify Inventory Directory screen, do the following:

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

    2. Enter the OS group for the user performing the installation.

    3. Click Next.

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

  4. In the Welcome screen, click Next.

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

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

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

  8. In the Installation Summary screen, click Install.

  9. In the Installation Complete screen, click Finish.

4.2 Backing 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 ORACLE_BASE/product/fmw

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

4.3 Enabling SOAHOST1VHN1 on SOAHOST1

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

You will associate the Administration Server with a virtual IP (SOAHOST1VHN1). Check that SOAHOST1VHN1 is enabled on SOAHOST1.

To enable the virtual IP on Linux, run the ifconfig command as root:

/sbin/ifconfig <interface:index> <IPAddress> netmask <netmask>
/sbin/arping -q -U -c 3 -I <interface< <IPAddress>

For example:

/sbin/ifconfig ethX:Y 100.200.140.206 netmask 255.255.255.0

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

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

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

    SOAHOST1> cd ORACLE_BASE/product/fmw/wc/common/bin

    Note:

    The Oracle WSM Policy Manager and JRF (Java Required Files) do not display by default in the Oracle Fusion Middleware Configuration Wizard. You must enable the display of these products. To accomplish this, pass the following JVM property to the config.sh script:

    -DTemplateCatalog.enable.selectable.all=true

    To pass this property to the script, set the CONFIG_JVM_ARGS environment variable to -DTemplateCatalog.enable.selectable.all=true. The script takes this property when you start the Oracle Fusion Middleware Configuration Wizard using./config.sh .

  3. Start the Oracle Fusion Middleware Configuration Wizard:

    SOAHOST1> ./config.sh

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

  5. The Select Domain Source screen is displayed (Figure 4-1).

    Figure 4-1 Select Domain Source Screen

    Description of Figure 4-1 follows
    Description of "Figure 4-1 Select Domain Source Screen"

    In the Select Domain Source screen, do the following:

    • Select Generate a domain configured automatically to support the following products.

    • Select the following products:

      • Oracle WSM Policy Manager - 11.1.1.0 [wc]

      • Oracle Enterprise Manager (selecting this option will auto-select some other templates.)

      • Oracle JRF (this should be selected automatically)

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

    • Oracle Enterprise Manager

    • emasTemplate

    • emaiTemplate

    • Oracle SOA Management Extension

    • Oracle WebCenterEM

    • Oracle JRF

    • Oracle WSM Policy Manager

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

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

  7. Click Next.

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

    Click Next.

  9. In the Configure Server Start Mode and JDK screen, do the following:

    • For WebLogic Domain Startup Mode, select Production Mode.

    • For JDK Selection, select JROCKIT SDK1.6.0_05.

    Click Next.

  10. In the Configure JDBC Components Schema screen, do the following:

    1. Select the OWSM MDS schema.

    2. Select Configure selected component schemas as RAC multi data source schemas in the next panel.

    3. Click Next.

  11. The Configure RAC Multi Data Sources Component Schema screen is displayed (Figure 4-2).

    Figure 4-2 Configure RAC Multi Data Source Component Schema Screen

    Configure RAC Multi Data Source Component Schema screen

    In this screen, do the following:

    1. Enter values for the following fields, specifying the connect information for the RAC database that was seeded with RCU.

      • Driver: Select Oracle driver (Thin) for RAC Service-Instance connections, Versions:10, 11.

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

    2. Enter the host name, instance name, and port.

    3. Click Add.

    4. Repeat this for each RAC instance.

    5. Click Next.

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

  13. In the Select Advanced Configuration screen, select the following:

    • Administration Server

    • Managed Servers, Clusters and Machines

    • Deployment and Services

    Click Next.

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

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

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

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

    • WSM-PM_Cluster:

      • WLS_WSM1

      • WLS_WSM2

    Click Next.

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

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

    • SOAHOST1:

      • AdminServer

      • WLS_WSM1

    • SOAHOST2:

      • WLS_WSM2

    Click Next.

  20. In the Target Deployments to Clusters or Servers screen, make sure that oracle.wsm.seedpolicies is targeted to the WSM-PM_Cluster. In addition, make sure that the DMS Application is targeted to the WSM_Cluster and the Admin Server. Click Next.

  21. In the Target Services to Clusters or Servers screen, make the following selections:

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

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

    You should make sure in this screen that all services and JDBC system resources are targeted to the AdminServer except the OWSM Startup Class. You should make sure that the OWSM Startup Class and all the JDBC system resources are targeted to the WSM-PM_Cluster.

  22. In the Configuration Summary screen, click Create.

  23. In the Create Domain screen, click Done.

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

Use the pack and unpack commands to separate the domain directory used by the Administration Server from the domain directory used by the managed server in SOAHOST1as recommended in Chapter 2, "Database and Environment Preconfiguration."

  1. Run the pack command on SOAHOST1 to create a template pack as follows:

    SOAHOST1> cd ORACLE_BASE/product/fmw/wc/common/bin
 
SOAHOST1> ./pack.sh -managed=true -domain=ORACLE_BASE/admin/<domain_name>/aserver/<domain_name> -template=wcdomaintemplate.jar -template_name=wc_domain_template

  2. Run the unpack command on SOAHOST1 to unpack the template in the managed server domain directory as follows:

    SOAHOST1> cd ORACLE_BASE/product/fmw/wc/common/bin

SOAHOST1> ./unpack.sh -domain=ORACLE_BASE/admin/<domain_name>/mserver/<domain_name> -template=wcdomaintemplate.jar

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

  1. Create the following directory structure:

    mkdir ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/servers

mkdir ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/servers/AdminServer

mkdir ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/servers/AdminServer/security

  2. In a text editor, create a file called boot.properties in the last directory created in the previous step, and enter the following lines in the file:

    username=<adminuser>
password=<password>

    Note:

    When you start the Administration Server, the username and password entries in the file get encrypted. You start the Administration Server in Section 4.7, "Starting the Administration Server on SOAHOST1."

    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.

4.7 Starting the Administration Server on SOAHOST1

Start the Administration Server:

SOAHOST1> cd ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/bin
SOAHOST1> ./startWebLogic.sh

4.8 Validating the Administration Server

Perform these steps to ensure that the Administration Server is properly configured:

  1. In a browser, go to http://SOAHOST1VHN1:7001/console.

  2. Log in as the administrator.

  3. Verify that the WLS_WSM1 and WLS_WSM2 managed servers are listed.

  4. Verify that the WSM-PM_Cluster cluster is listed.

  5. Check that you can access Oracle Enterprise Manager at http://SOAHOST1VHN1:7001/em.

  6. Log in to EM Console with the username and password you specified in Section 4.6, "Creating boot.properties for the Administration Server on SOAHOST1."

4.9 Disabling 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:

  1. Log in to Oracle WebLogic Server Administration Console.

  2. Click Lock and Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers. The Summary of Servers page appears.

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

  6. Click the SSL tab.

  7. Click Advanced.

  8. Set Hostname Verification to None.

  9. Click Save.

  10. Repeat steps 4 to 8 for the WLS_WSM1 server.

  11. Save and activate the changes.

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

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

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

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

      SOAHOST1> cd ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/bin
SOAHOST1> ./startWebLogic.sh

4.10 Starting Node Manager on SOAHOST1

Perform these steps to start Node Manager on SOAHOST1:

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

    SOAHOST1> cd ORACLE_BASE/product/fmw/soa/common/bin
SOAHOST1> ./setNMProps.sh

    Note:

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

  2. Start Node Manager:

    SOAHOST1> cd ORACLE_BASE/product/fmw/wlserver_10.3/server/bin
SOAHOST1> ./startNodeManager.sh

4.11 Starting and Validating the WLS_WSM1 Managed Server

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

  1. Start the WLS_WSM1 managed server using the Oracle WebLogic Server Administration Console as follows:

    1. Expand the Environment node in the Domain Structure window.

    2. Choose Servers. The Summary of Servers page appears.

    3. Click the Control tab.

    4. Select WLS_WSM1 and then click Start.

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

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

  4. 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.12 Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility

Perform these steps to propagate the domain configuration:

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

    SOAHOST1> cd ORACLE_BASE/product/fmw/wc/common/bin
SOAHOST1> scp wcdomaintemplate.jar oracle@SOAHOST2:/ORACLE_BASE/product/fmw/wc/common/bin

  2. Run the unpack command on SOAHOST2 to unpack the propagated template.

    Note:

    Run unpack from the ORACLE_HOME/common/bin directory, not from the WL_HOME/common/bin directory.
    SOAHOST2> cd ORACLE_BASE/product/fmw/wc/common/bin
SOAHOST2> ./unpack.sh -domain=ORACLE_BASE/admin/<domain_name>/mserver/<domain_name> -template=wcdomaintemplate.jar

    Note:

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

4.13 Disabling 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:

  1. Log in to Oracle WebLogic Server Administration Console.

  2. Click Lock and Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers. The Summary of Servers page appears.

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

  6. Click the SSL tab.

  7. Click Advanced.

  8. Set Hostname Verification to None.

  9. Save and activate the changes.

4.14 Starting Node Manager on SOAHOST2

Perform these steps to start Node Manager on SOAHOST2:

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

    SOAHOST2> cd ORACLE_BASE/product/fmw/soa/common/bin
SOAHOST2> ./setNMProps.sh

    Note:

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

  2. Start Node Manager:

    SOAHOST2> cd ORACLE_BASE/product/fmw/wlserver_10.3/server/bin
SOAHOST2> ./startNodeManager.sh

4.15 Starting and Validating the WLS_WSM2 Managed Server

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

  1. Start the WLS_WSM2 managed server using the Administration Console.

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

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

  4. Click validate policy manager.

4.16 Configuring 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:

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

    # WSM-PM
<Location /wsm-pm>
    SetHandler weblogic-handler
    WebLogicCluster SOAHOST1:7010,SOAHOST2:7010
</Location>

# Admin Server and EM
<Location /console>
    SetHandler weblogic-handler
    WebLogicHost SOAHOST1VHN1
    WeblogicPort 7001
</Location>
<Location /consolehelp>
    SetHandler weblogic-handler
     WebLogicHost SOAHOST1VHN1
    WeblogicPort 7001
 </Location>
<Location /em>
    SetHandler weblogic-handler
    WebLogicHost SOAHOST1VHN1
    WeblogicPort 7001
</Location>

  2. Make sure the httpd.conf file located in the same directory as the mod_wl_ohs file contains the following lines:

    NameVirtualHost *:7777
<VirtualHost *:7777>
    ServerName https://wc.mycompany.com:443
    ServerAdmin you@your.address
    RewriteEngine On
    RewriteOptions inherit
</VirtualHost>

NameVirtualHost *:7777
<VirtualHost *:7777>
    ServerName admin.mycompany.com:80
    ServerAdmin you@your.address
    RewriteEngine On
    RewriteOptions inherit
</VirtualHost>

    Note:

    Values such as , 7777, admin.mycompany:80, and you@youraddress that are noted in this document serve as examples only. Enter values based on the actual environment.

  3. Restart Oracle HTTP Server on both WEBHOST1 and WEBHOST2.

    WEBHOST1> ORACLE_BASE/admin/<instance_name>/bin/opmnctl restartproc ias-component=ohs1

WEBHOST2> ORACLE_BASE/admin/<instance_name>/bin/opmnctl restartproc ias-component=ohs2

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.

For more information on configuring the WebLogic Server plug-in, see the Oracle Fusion Middleware Using Web Server Plug-Ins With Oracle WebLogic Server guide.

4.17 Registering Oracle HTTP Server With WebLogic Server

Oracle HTTP Server must forward requests to WebLogic Server. To do this, you must register Oracle HTTP Server with WebLogic Server using the following command:

WEBHOST1> cd ORACLE_BASE/admin/<instance_name>/bin

WEBHOST1> ./opmnctl registerinstance -adminHost SOAHOST1VHN1 -adminPort 7001 -adminUsername weblogic

You must also run this command from WEBHOST2 for OHS2.

4.18 Setting the Frontend URL for the Administration Console

Oracle WLS Admin Console application tracks changes made to ports, channels and security using the console. When changes made through the console are activated, the console validates its current listen address, port and protocol. If the listen address, port and protocol are still valid, the console redirects the HTTP request replacing the host and port information with the Admin Server's listen address and port. When the Admin Console is accessed using an LBR, it is required to change the Adminsitration Server's frontend URL so that the user's browser is redirected to the appropriate LBR address. To do this, complete these steps:

  1. Log in to Oracle WebLogic Server Administration Console.

  2. Click Lock and Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers to open the Summary of Servers page.

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

  6. Click the Protocols tab.

  7. Click the HTTP tab.

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

  9. Save and activate the changes.

4.19 Validating 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:

  • http://Webtier_node1:7777/wsm-pm

  • http://Webtier_node2:7777/wsm-pm

  • http://Webtier_node1:7777/console

  • http://Webtier_node2:7777/console

  • http://Webtier_node1:7777/em

  • http://Webtier_node2:7777/em

  • http://admin.mycompany.com/console

  • http://admin.mycompany.com/em

For information on configuring system access through the load balancer, see Section 2.2.2, "Load Balancers."

Note:

After the registering Oracle HTTP Server as described in Section 4.17, "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.20 Manually 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.

Assumptions:

  • The Administration Server is configured to listen on SOAHOST1VHN1, and not on ANY address. See step 14 in Section 4.4, "Running the Configuration Wizard on SOAHOST1 to Create a Domain".

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

  1. Stop the Administration Server.

  2. Migrate IP to the second node.

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

      SOAHOST1> /sbin/ifconfig ethX:Y down

    2. Run the following command on SOAHOST2:

      SOAHOST2> /sbin/ifconfig <interface:index> <IP_Address> netmask <netmask>

      For example:

      /sbin/ifconfig eth0:1 10.0.0.1 netmask 255.255.255.0

      Note:

      Ensure that the netmask and interface to be used to match the available network configuration in SOAHOST2.

  3. Update routing tables through arping, for example:

    SOAHOST2> /sbin/arping -b -A -c 3 -I eth0 10.0.0.1

  4. Start the Administration Server on SOAHOST2.

    SOAHOST2> cd ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/bin

SOAHOST2> ./startWebLogic.sh

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

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

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

4.21 Validating Access to SOAHOST2 Through Oracle HTTP Server

Perform the same steps as in Section 4.19, "Validating Access Through Oracle HTTP Server". This is to check that you can access the Administration Server when it is running on SOAHOST2.

4.22 Failing the Administration Server Back to SOAHOST1

This step checks that you can fail back the Administration Server, that is, stop it on SOAHOST2 and run it on SOAHOST1. To do this, migrate SOAHOST1VHN1 back to SOAHOST1 node as follows:

  1. Run the following command on SOAHOST2.

    SOAHOST2> /sbin/ifconfig ethZ:N down

  2. Run the following command on SOAHOST1:

    SOAHOST1> /sbin/ifconfig ethX:Y 100.200.140.206 netmask 255.255.255.0

    Note:

    Ensure that the netmask and interface to be used match the available network configuration in SOAHOST1

  3. Update routing tables through arping. Run the following command from SOAHOST1.

    SOAHOST1> /sbin/arping -b -A -c 3 -I ethZ 100.200.140.206

  4. Start the Administration Server again on SOAHOST1.

    SOAHOST1> cd ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/bin
SOAHOST1> ./startWebLogic.sh

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

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

4.23 Backing Up the Installation

Perform a backup to save your domain configuration (make sure that you stop the server first). The configuration files all exist under the ORACLE_BASE/admin/<domain_name> directory.

SOAHOST1> tar -cvpf edgdomainback.tar ORACLE_BASE/admin/<domain_name>