Skip Headers
Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite
11g Release 1 (11.1.1)

Part Number E12036-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

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 SOA components and, optionally, Oracle Business Activity Monitoring.

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

Install Oracle WebLogic Server on SOAHOST1 and SOAHOST2.

For information about running the generic installer for installing WebLogic Server on 64-bit platforms uing a 64-bit JDK, see the section "Installing WebLogic Server on 64-Bit Platforms Using a 64-Bit JDK" in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

Oracle WebLogic Server on SOAHOST1 and SOAHOST2.

To install Oracle WebLogic Server:

  1. Start the Oracle WebLogic Server installer.

    Note:

    For information about the correct WebLogic Server installation program file name, see the section "Starting the Installation Program in Graphical Mode," in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

    For UNIX (Linux used in this example):

    SOAHOST1> wls_linux34.bin
    

    For Windows operating systems:

    SOAHOST1> wls_win34.exe
    
  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_<version> SDK, and click Next.

  8. In the Choose Product Installation Directories screen, accept the directory WL_HOME, 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 SOA

Perform these steps to install Oracle Fusion Middleware for SOA on SOAHOST1 and SOAHOST2.

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

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

  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 (soa).

    Click Next.

  7. In the Application Server screen, select WebLogic.

    Click Next.

  8. In the Installation Summary screen, click Install.

  9. In the Installation Complete screen, click Finish.

    Note:

    This Enterprise Deployment Guide assumes that the binary installation for both Oracle Fusion Middleware Components and Oracle HTTP Server are patched to the latest patch set available. The Enterprise Deployment Guide does not take into consideration running systems and rolling patches, but instead assumes the system is created from scratch and patched to the latest available patch set before the Configuration Wizard and domain operations are started. Follow the documentation included with each patch set to properly patch an existing installation. Specifically for Oracle BPM, Oracle requires the WL_HOME and ORACLE_HOME to be patched to the latest Oracle Fusion Middleware patch set level before the WebLogic Configuration Wizard steps are performed to extend a domain. For information about the latest versions and patching procedures for Oracle Fusion Middleware, see the Oracle Fusion Middleware Patching Guide.

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 MW_HOME

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

4.3 Enabling VIP1 in SOAHOST1

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

You are associating the Administration Server with a virtual hostname (ADMINVHN). 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 ADMINVHN is available per your name resolution system, (DNS server, /etc/host), in the required nodes in your SOA topology. The VIP (VIP1) that is associated to this Virtual Host Name (ADMINVHN1) must be enabled in 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 SOA home directory to create a domain containing the Administration Server and Oracle Web Services Manager. Later, you will extend the domain to contain SOA components.

  1. Ensure that the database where you installed the repository is running. For Oracle 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 SOA home directory.

    SOAHOST1> cd ORACLE_COMMON_HOME/common/bin
    
  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:

      • Basic WebLogic Server Domain - 10.3.1.0 [wlserver_10.3] (this should be selected automatically)

      • Oracle Enterprise Manager - 11.1.1.0 [oracle_common]

      • Oracle WSM Policy Manager 11.1.1.0 [oracle_common]

      • Oracle JRF - 11.1.1.0 [oracle_common] (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

    • Oracle WSM Policy Manager

    • Oracle JRF

    Click Next.

  6. In the Specify Domain Name and Location screen, enter the domain name (soaedg_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>/aserver/applications 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_<version>.

    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 Oracle 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, soaedg.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 Oracle 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 ADMINVHN.

    • 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

      ADMINHOST

      LOCALHOST


      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:

      • WLS_WSM1

    • SOAHOST2:

      • WLS_WSM2

    • ADMINHOST

      • AdminServer

    Click Next.

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

  21. 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, and JOC-Startup.

    • 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, and JOC-Startup, should be targeted only to the WSM-PM_Cluster.

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

    • Click Next.

  22. In the Configuration Summary screen, click Create.

  23. In the Create Domain screen, click Done.

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

For the Administration Server:

  1. Create the following directory structure:

    mkdir -p 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.6 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_COMMON_HOME/common/bin directory, to set the StartScriptEnabled property to 'true' before starting Node Manager:

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

    Note:

    You must use the StartScriptEnabled property to avoid class loading failures and other problems. See also Section 10.7.5, "Incomplete Policy Migration After Failed Restart of SOA Server."
  2. Start Node Manager:

    SOAHOST1> cd WL_HOME/server/bin
    SOAHOST1> export JAVA_OPTIONS="-DDomainRegistrationEnabled=true"
    SOAHOST1> ./startNodeManager.sh
    

    Note:

    It is important that you set -DDomainRegistrationEnabled=true whenever a Node Manager is started, that must manage the AdminServer. If there is no AdminServer on this machine and this machine is not an AdminServer failover node, you can start the Node Manager as:
    SOAHOST1> ./startNodeManager.sh
    

4.7 Starting the Administration Server on SOAHOST1

The Administration Server is started and stopped using Node Manager. However, the first start of the Administration Server with Node Manager, requires changing the defaulted username and password that are set for Node Manager by the Configuration Wizard. Therefore, use the start script for the Administration Server for the first start.

Follow these steps to start the Administration Server using Node Manager (steps 1-4 are required for the first start operation, subsequent starts require only step 4):

  1. Start the Administration Server using the start script in the domain directory

    SOAHOST1> cd ORACLE_BASE/admin/domain_name/aserver/domain_name/bin
    SOAHOST1> ./startWebLogic.sh
    
  2. Use the Administration Console to update the Node Manager credentials.

    1. In a browser, go to the following URL;

      http://ADMINVHN:7001/console

    2. Log in as the administrator.

    3. Click Lock and Edit.

    4. Click domain_name, Security, General, and then expand the Advanced options at the bottom.

    5. Enter a new username for Node Manager, or make a note of the existing one and update the Node Manager password.

    6. Save and activate the changes.

  3. Stop the Administration Server process by using CTRl-C in the shell where it was started, or by process identification and kill in the OS.

  4. Start WLST and connect to Node Manager with nmconnect and the credentials set in the previous steps and start the Administration Server using nmstart.

    SOAHOST1> cd ORACLE_COMMON_HOME/common/bin
    SOAHOST1> ./wlst.sh
    

    Once you are in the WLST shell:

    wls:/offline>nmConnect('Admin_User','Admin_Password',
    'SOAHOST1','5556','domain_name','/u01/app/oracle/admin/domain_name/aserver/domain_name')
     
    wls:/nm/domain_name> nmStart('AdminServer')
    

    Note:

    This username and password are used only to authenticate connections between Node Manager and clients. They are independent of the server admin ID and password and are stored in the ORACLE_BASE/admin/domain_name/aserver/domain_name/config/nodemanager/nm_password.properties file.

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://ADMINVHN: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://ADMINVHN:7001/em.

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

4.9 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_COMMON_HOME/common/bin
     
    SOAHOST1> ./pack.sh -managed=true -domain=ORACLE_BASE/admin/domain_name/aserver/domain_name -template=soadomaintemplate.jar -template_name=soa_domain_template
    
  2. Run the unpack command on SOAHOST1 to unpack the template in the managed server domain directory as follows:

    SOAHOST1> cd ORACLE_COMMON_HOME/common/bin
    
    SOAHOST1> ./unpack.sh -domain=ORACLE_BASE/admin/domain_name/mserver/domain_name 
    -template=soadomaintemplate.jar -app_dir=ORACLE_BASE/admin/domain_name/mserver/applications
    

4.10 Applying the Java Required Files (JRF) Template to the WSM-PM_Cluster

After the domain is created with the Configuration Wizard, you must target a number of resources not included in the WebLogic server installation to the WSM-PM Cluster.

To target these resources:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control with the username and password you specified in Section 4.5, "Creating boot.properties for the Administration Server on SOAHOST1."

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

  3. Click Apply JRF Template on the right.

  4. 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.11 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 8, "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 8, "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 using the procedure in Section 4.7, "Starting the Administration Server on SOAHOST1."

4.12 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 10.7, "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.13 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_COMMON_HOME/common/bin
    
    SOAHOST1> scp soadomaintemplate.jar oracle@SOAHOST2:/ORACLE_COMMON_HOME/common/bin
    
  2. Run the unpack command on SOAHOST2 to unpack the propagated template.

    Note:

    Run unpack from the ORACLE_COMMON_HOME/common/bin directory, not from the WL_HOME/common/bin directory.
    SOAHOST2> cd ORACLE_COMMON_HOME/common/bin
    
    SOAHOST2> ./unpack.sh -domain=ORACLE_BASE/admin/domain_name/mserver/domain_name
    -template=soadomaintemplate.jar -app_dir=ORACLE_BASE/admin/domain_name/mserver/applications
    

    Note:

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

4.14 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 8, "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 8, "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.15 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_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. See also Section 10.7.5, "Incomplete Policy Migration After Failed Restart of SOA Server."
  2. Start Node Manager:

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

4.16 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 10.7, "Troubleshooting" for possible causes.

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

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

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

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

    wls:/mydomain/serverConfig>execfile('MW_HOME/oracle_common/bin/configure-joc.py')
    
  3. Configure JOC for all the managed servers for a given cluster.

    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-pm_cluster
    Enter Discover Port : 9991
    

    Here is a walkthrough for using configure-joc.py for HA environments:

    execfile('MW_HOME/oracle_common/bin/configure-joc.py')
    .
    Enter Hostnames (eg host1,host2) : SOAHOST1, SOAHOST2
    .
    Do you want to specify a cluster name (y/n) <y>y
    .
    Enter Cluster Name : wsm-pm_cluster
    .
    Enter Discover Port : 9991
    .
    Enter Distribute Mode (true|false) <true> : true
    .
    Do you want to exclude any server(s) from JOC configuration (y/n) <n> n
    

The script can also be used to perform the following JOC configurations:

Verify JOC configuration using the CacheWatcher utility. See Oracle Fusion Middleware High Availability Guide.

You can configure the Java Object Cache (JOC) using the HA Power Tools tab in the Oracle WebLogic Administration Console as described in the Oracle Fusion Middleware High Availability Guide.

4.18 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
        WLProxySSL ON
        WLProxySSLPassThrough ON
    </Location>
    
    # Admin Server and EM
    <Location /console>
        SetHandler weblogic-handler
        WebLogicHost ADMINVHN
        WeblogicPort 7001
        WLProxySSL ON
        WLProxySSLPassThrough ON
    </Location>
    
    <Location /consolehelp>
        SetHandler weblogic-handler
         WebLogicHost ADMINVHN
        WeblogicPort 7001
        WLProxySSL ON
        WLProxySSLPassThrough ON
    </Location>
    
    <Location /em>
        SetHandler weblogic-handler
        WebLogicHost ADMINVHN
        WeblogicPort 7001
        WLProxySSL ON
        WLProxySSLPassThrough ON
    </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://soa.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 soa.mycompany.com:443, 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:

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.

Important Security Consideration

For security purposes, and since the load balancer terminates SSL request (Oracle HTTP Server routes the requests as non-SSL to WebLogic Server), once SSL is configured for the load balancer, turn on the WebLogic plug-in enabled flag2 for the domain. To do this, follow these steps:

  1. Log on to the Administration Console.

  2. Click on the domain name in the navigation tree on the left.

  3. Click on the Web Applications tab.

  4. Click Lock and Edit.

  5. Select the WebLogic Plugin Enabled check box

  6. Save and activate the changes.

4.19 Registering Oracle HTTP Server With WebLogic Server

Once an Oracle WebLogic domain is created, the Oracle Web Tier can be linked to the domain. The advantages of doing this is that the Oracle Web Tier can be managed and monitored using the Oracle Fusion Middleware Console.

To associate the Oracle Web Tier with the WebLogic domain use the following commands:

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

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

You must also run this command from WEBHOST2 for OHS2.

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

When you access the Oracle WebLogic Server Administration Console using a load balancer, changing the Administration Server's frontend URL is required so that the user's browser is redirected to the appropriate load balancer address. To change the Administration Server's frontend URL, 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 Frontend Host to admin.mycompany.com and the Frontend HTTP Port to 80 (modify accordingly if HTTPS is used for the admin URL).

  9. Save and activate the changes.

Note:

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.

Note:

If you have any issues activating any configuration changes after modifying the Frontend Host and Port settings, then refer to Section 10.7.14, "Redirecting of Users to Login Screen After Activating Changes in Administration Console."

4.21 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 10.7, "Troubleshooting" for possible causes.

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

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.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.22 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 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 ADMINVHN):

      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 using the procedure in Section 4.7, "Starting the Administration Server on SOAHOST1.".

  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://ADMINVHN:7001/console.

    2. Check that you can access and verify the status of components in the Oracle Enterprise Manager at http://ADMINVHN: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.

4.23 Validating Access to SOAHOST2 Through Oracle HTTP Server

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

4.24 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 ADMINVHN 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 using the procedure in Section 4.7, "Starting the Administration Server 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://ADMINVHN:7001/console.

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

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

Back up the Instance Home on the web tier using the following command:

tar -cvpf BACKUP_LOCATION/web_instance_name.tar ORACLE_INSTANCE