4 Installing and Configuring Oracle WebLogic Server

Server Cluster Example

See Table 4-2 and Table 4-3 for information on setting up the cluster arrangement.

WL_Home/user_projects/domains/cluster01

Figure 4-1 shows the servers in a sample server cluster.

Figure 4-1 Servers in a Sample Cluster

Server Cluster Prerequisites

The prerequisites for setting up a server cluster are:

• Oracle WebLogic administration experience.

• A hardware load balancer. Refer to the server load balancer configuration for details.

• A DNS entry containing all of the cluster-managed servers' listening addresses, serves as the UIM cluster address.

• A machine hosting multiple cluster-managed servers. The machine must be multi-homed.

  Note:

  UIM recommends using Multicast for Cluster messaging mode. For more information, see "Communications In a Cluster" in Oracle Fusion Middleware Administering Clusters for Oracle WebLogic Server.

Overview of Steps for Setting Up a Server Cluster

Installing an Oracle WebLogic Server cluster arrangement involves:

• Installing Oracle WebLogic Server in a Clustered Environment

• Creating a Domain

• Starting the WebLogic Server

• Starting the Cluster Servers

• Configuring the WebLogic Server StuckThreadMaxTime Value

• Configuring the WebLogic Server Proxy Timeout Value

Installing Oracle WebLogic Server in a Clustered Environment

Install WebLogic Server on the shared disk storage by following the procedures in "Downloading and Installing Oracle WebLogic Server".

Creating a Domain

To create a domain:

1. Navigate to the WL_Home/common/bin directory and run the following command:

   ./config.sh
   

   The Configuration Type screen of the Fusion Middleware Configuration Wizard appears.

2. Select the Create a new domain option and in the Domain Location field, enter the full path for the domain or click Browse to navigate to the directory in which your domains are located, and then click Next.

   The Templates screen appears.

3. Select the Create Domain Using Product Templates option and from the provided list, select the following products:

   • Basic WebLogic Server Domain (This product is selected by default and you cannot deselect it.)

   • Oracle Enterprise Manager - 12.2.1.3.0 [em]

   • Oracle JRF - 12.2.1.3.0 [oracle_common]

   • WebLogic Coherence Cluster Extension - 12.2.1.3.0 [wlserver]

   • Oracle MapViewer - 12.2.1.3.0 [oracle_common] (This product is only available if you chose to install MapViewer.)

   Note:

   The selection of the WebLogic Coherence Cluster Extension template for this step does not imply or require the use of the Oracle Coherence product.

4. Click Next.

   The Application Location screen appears.

5. Do the following:

   1. In the Domain name field, enter an appropriate domain name as per your requirements or standards.

   2. In the Domain location field, enter the path and directory where the domain files will be created. For example, enter the value: WLServer_Home/user_projects/domains/base_domains.

   3. In the Application location field, enter the path and directory for the application files. For example, enter the value:

      WLServer_Home/user_projects/domains/application_name
      

   4. Click Next.

      The Administrator Account screen appears.

6. In the Name field, enter the administrator user name.

7. In the Password field, enter the administrator user password. The password must be a minimum of 8 alphanumeric characters, and must contain at least one number or special character.

   In the Confirm Password field, reenter your password.

8. Click Next.

   The Domain Mode and JDK screen appears.

9. In the Domain Mode section, select the Production option.

   In the JDK section, select the required JDK (Oracle JDK 1.8.0_patch where patch is the latest critical update) by doing the following:

   • Select Available JDKs and select a JDK from the list provided.
     
     or

   • Select Other JDK and browse to the location of another JDK. Ensure that this JDK is supported. See Table 2-2, "Required Server-Side Software" for details.

10. Click Next.

    The Database Configuration Type screen appears.

11. Select the RCU Data option and enter the connection information that you specified for the Service Table (STB) schema component in the Repository Creation Utility (RCU):

    1. In the Vendor field, select the vendor name for the component schema.

    2. In the DBMS/Service field, enter the database management system or service name for the component schema.

    3. In the Driver field, select the driver used by the component schema.

    4. In the Host Name field, enter the host name/IP address for the component schema.

    5. In the Port field, enter the port number used by the schema component.

    6. In the Schema Owner field, enter the owner name for the schema component.

       Note:

       The default schema owner name is prefix_STB, where prefix is the prefix that you defined in RCU for the Service Table schema.

    7. In the Schema Password field, enter the password for the schema component.

    8. Click Get RCU Configuration, which retrieves the schema information.

    9. After the schema information is retrieved successfully, click Next.

       The Component Datasources screen appears.

12. Do one of the following:

    • For single-instance database: Verify the values in the fields and click Next, the JDBC Test screen appears. Continue with step 13.

    • For Oracle Real Application Clusters (RAC) database: Select the Convert to RAC multi data source check box and click Next.

      The Oracle RAC Multi Data Source Component Schema screen appears.

      1. From the Driver list, select Oracle's Driver (Thin) for RAC Service-Instance connections; Versions:10 and later.

      2. In the Service Name field, enter the service name for the RAC database.

      3. In the Username field, enter the owner name of the schema component.

      4. In the Password field, enter the password for the schema component.

      5. In the Host Name field, enter the host name/IP address of the machine configured for RAC database.

      6. In the Instance Name field, enter the SID of the host.

      7. In the Port field, enter the configured port of the host.

      8. Add additional hosts by clicking Add Host and repeat steps e through g for each new host added.

      9. Click Next.

         The JDBC Test screen appears, which enables you to test the configurations for the schemas.

13. Select the check boxes beside the schemas you want to test and click Test Selected Connections.

14. Verify that all the JDBC component connections pass the validation test and click Next.

    The Advanced Configuration screen appears.

15. Select the following:

    • Administration Server

    • Topology

    • Deployments and Services

      Note:

      Oracle recommends that production environments for UIM use a minimum of an Administration Server and one or more Managed Servers or Clusters. Lab environments can be installed on an Administration Server only, if desired.

      If you select only Administration Server, the Domain Creation wizard does not display some dialog boxes pertaining to managed servers or clusters.

16. Click Next.

    The Administration Server screen appears.

17. Do the following:

    1. In the Server Name field, enter your Administration Server name.

    2. In the Listen Address field, select a DNS or an IP address.

       Note:

       Use listener addresses that are equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.

    3. In the Listen Port field, accept the default.

    4. Select Enable SSL if you are enabling SSL.

       It is not a requirement to either enable or disable SSL.

       If you decide to enable SSL, ensure that you configure SSL for WebLogic Server using correct cipher suites.

       For more information, see ”Cipher Suites” in Fusion Middleware Securing Oracle WebLogic Server at:

       http://docs.oracle.com/middleware/1212/core/ASADM/sslconfig.htm

    5. In the SSL Listen Port field, enter a port that is not used by another domain.

       This field is enabled only if you selected the Enable SSL check box.

    6. In the Server Groups list, accept the provided default value.

    7. Click Next.

       The Managed Servers screen appears.

18. Do the following:

    1. Click Add to add a managed server to the cluster.

    2. In the Server Name field, enter a name for the managed server.

    3. In the Listen Address field, enter the host, or IP address of the machine where the managed server is running.

       Note:

       Use listener addresses that are equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.

    4. In the Listen Port field, enter the number of the port where the managed server will listen for incoming messages.

    5. Select Enable SSL as required.

    6. In the SSL Listen Port field, enter the appropriate value only if SSL is selected.

    7. In the Server Groups list, select the MAPVIEWER-MAN-SVR and JRF-MAN-SVR groups.

       The Server Groups list may not display both the groups if you did not install MapViewer.

    8. (Optional) Click Add to add more managed servers as required on your UIM deployment.

    9. Click Next.

       The Clusters screen appears.

19. Do the following:

    1. Click Add to start configuring the cluster.

    2. In the Cluster Name field, enter the name for the cluster.

    3. In the Cluster Address field, provide the cluster address information.

       The cluster address contains each managed server along with the managed server's port separated by a comma. Separate the managed server and the port number by a colon.

    4. Click Next.

       The Server Template screen appears.

20. Click Next.

    The Dynamic Servers screen appears.

21. Click Next.

    The Assign Servers to Clusters screen appears.

22. Assign the servers to the cluster by moving the managed servers in the left pane to the required cluster in the right pane.

23. Click Next.

    The HTTP Proxy Applications screen appears.

24. (Optional) Select Create HTTP Proxy for any proxy servers in the list.

    Click Next.

    The Coherence Clusters screen appears, displaying the Coherence cluster that is automatically added to the domain.

    This screen appears only if you included Coherence in the WebLogic Server installation.

25. Do the following:

    1. In the Name field, accept the default cluster name or type a new name for the Coherence cluster.

    2. In the Coherence Listen Port field, enter the port number to use as the Coherence cluster listen port.

26. Click Next.

    The Machines screen appears. Use this screen to change the configuration information for the machines. A machine is the logical expression of the system that hosts one or more WebLogic Server instances. The Administration Server and the Node Manager application use the machine definition to start remote servers.

27. (Optional) Add the machines by doing one of the following:

    • Select the Machine tab, and do the following:

      1. Click Add to create the first machine.

      2. In the Name field, enter a name for the machine.

      3. In the Node Manager Listen Address field, enter the host, or IP address of the node manager.

      4. In the Node Manager Listen Port, enter the port number for the node manager.

      5. (Optional) Create further machines as required on your UIM deployment.

      6. Click Next.

         The Deployments Targeting screen appears.

    • Select the Unix Machine tab, and do the following:

      1. Click Add to create the first UNIX machine.

      2. If required, select Enable Post Bind GID. The default state is unselected.

      3. In the Post Bind GID field, enter a value or select the default.

      4. If required, select Enable Post Bind UID. The default state is unselected.

      5. In the Post Bind UID field, enter a value or select the default.

      6. In the Node Manager Listen Address field, enter the host, or IP address of the node manager.

      7. In the Node Manager Listen Port field, enter the port number of the node manager.

      8. (Optional) Create further machines or UNIX machines as required on your UIM deployment.

      9. Click Next.

         The Assign Servers to Machines screen appears.

28. Assign the servers to the machines by moving the servers in the left pane to the required machine in the right pane.

29. Click Next.

    The Virtual Targets screen appears.

30. Click Next.

    The Partition screen appears.

31. Click Next.

    The Deployments Targeting screen appears.

32. Under Targets, select the Administration Server; under Deployments, select all the applications; and then click the right arrow, which moves the applications to the Administration Server for deployment.

    Caution:

    Do not deploy Enterprise Manager to the managed servers in the WebLogic domain for a server cluster installation. Only deploy Enterprise Manager on the Administration Server.

    Refer to Chapter 8, "Troubleshooting the Unified Inventory Management Installation" under the section "Problem: Deploying Enterprise Manager Error on Managed Servers" for more information on the error you encounter if this occurs.

33. Repeat step 32 to target applications for deployment on the cluster.

34. Click Next.

    The Services Targeting screen appears.

35. Under Targets, select the Administration Server, under Services, select all the services; and then click the right arrow, which moves the services to the Administration Server.

36. Repeat step 35 to target services (libraries) to the cluster.

37. Click Next.

    The Configuration Summary screen appears.

38. Review the summary to verify the contents of your domain and click Create to create the domain.

    The Configuration Progress screen appears, which displays the progress of the domain creation process.

    After the domain is created successfully, the Configuration Success screen appears.

39. Click Finish.

    See Oracle Fusion Middleware documentation for more information.

40. To set memory requirements, see "Setting Memory Requirements for UIM".

41. Start the WebLogic server. See "Starting the WebLogic Server".

    You can now log in to the WebLogic Server Administration Console and start the Administration Server manually.

Starting the WebLogic Server

You start the WebLogic server in a clustered environment in the same way that you start the WebLogic server in single server environment. See "Starting the WebLogic Server".

Starting the Cluster Servers

Depending on whether you have configured the node manager, you can start the UIM cluster servers one of two ways:

• If you have not configured the node manager, you must start the cluster servers through a command prompt on the first cluster server.

  See "Starting the Cluster Servers from the First Cluster Server".

• If you have configured the node manager, you can start the cluster servers through the WebLogic Server Administration Console.

  See "Starting the Cluster Servers from the WebLogic Server".

Starting the Cluster Servers from the First Cluster Server

To start the cluster servers from the first cluster server:

1. Log in to the first cluster server machine.

2. Navigate to the Domain_Home/bin directory.

3. Start the cluster server by running the following command from the machine where the managed server is defined:

   ./startManagedWebLogic.sh cluster_server_name admin_server_URL
   

4. Repeat steps 1 through 3 for each cluster server.

5. Verify that the server started:

   1. Log in to the WebLogic Server Administration Console.

   2. In the Domain Structure tree, expand Environment, and click Servers.

      The Summary of Servers page appears.

   3. View the State of the cluster servers and see RUNNING.

      If the State is not RUNNING, you may need to wait a short period and refresh the page.

Starting the Cluster Servers from the WebLogic Server

To start the cluster servers from the WebLogic server:

1. Log in to the WebLogic Server Administration Console.

2. In the Domain Structure tree, expand Environment, and click Servers.

   The Summary of Servers page appears.

3. Click the link for the managed server.

   The Settings for the selected server page appears.

4. Click the Server Start tab.

5. In Class Path, enter the following. (These are the classpaths defined in the setUIMEnv.sh and startUIM.sh files, which you must also define for the node manager.)

   UIM_Home/lib/aspectjrt.jar: 
   UIM_Home/lib/aspectjtools.jar 
   

   where UIM_Home is the UIM directory under domain. For example, /opt/Weblogic/user_projects/domains/UIM_Rel/UIM.

   And where MODULES_HOME is the modules directory under Middleware. For example, /opt/Weblogic/modules.

6. In Arguments, enter the following. (These are the arguments defined in the setUIMEnv.sh and startUIM.sh files, which you must also define for the node manager.)

   -Duim.home=UIM_Home
   -Dweblogic.log.Log4jLoggingEnabled_uim=true 
   -Dlog4j.configuration_uim=loggingconfig.xml 
   -Duim.logging.watchdog.timer=5000 
   -Djava.io.tmpdir=UIM_Home/tmp 
   -Dweblogic.management.discover.retries=6 
   -javaagent:UIM_Home/lib/aspectjweaver.jar -Daj.weaving.verbose=false 
   -Dsun.lang.ClassLoader.allowArraySyntax=true 
   -XX:-UseSSE42Intrinsics 
   -DUSE_JAAS=false -Djps.policystore.hybrid.mode=false 
   -Djps.combiner.optimize.lazyeval=true -Djps.combiner.optimize=true 
   -Djps.authz=ACC 
   -DUIMMaster=ManagedServer 
   

   where UIM_Home is the UIM directory under domain. For example, /opt/Weblogic/user_projects/domains/UIM_Rel/UIM.

   And where ManagedServer is the managed server name. For example, ManagedServer1.

7. Click Save.

Configuring the WebLogic Server StuckThreadMaxTime Value

During the installation of Oracle WebLogic Server and UIM in a clustered environment, if the execute thread takes more time than the Stuck Thread Max Time: declared in WebLogic, a Stuck Thread Max Time: error is displayed.

Stuck Thread Max Time: is a configurable property in WebLogic for performance tuning. It is defined as ”The number of seconds that a thread must be continually working before this server considers the thread stuck”. The minimum value is 0 seconds; the default value is 600 seconds.

Consider setting Stuck Thread Max Time: from its default 600 seconds to a larger value such as 3600 seconds.

Use the WebLogic Server Administration Console to change this value:

1. Log in to the WebLogic Server Administration Console.

2. In the left section, under Domain Structure, expand Environment.

3. Click Servers, and then click the link for each managed server.

4. For each managed server, click the Configuration tab and then click the Tuning tab.

5. Increase the value of Stuck Thread Max Time to 3600.

6. Restart your domain. Your changes will take effect only after a restart.

Configuring the WebLogic Server Proxy Timeout Value

When you install UIM in a clustered environment using WebLogic HttpClusterServlet, long-running transactions time out from the proxy, which logs you out of UIM. To avoid this situation, configure the WebLogic Server proxy timeout value.

To configure the WebLogic Server proxy timeout value:

1. Navigate to and open the Domain­­_Home/apps/OracleProxy4_cluster1_uim_proxy/WEB-INF/web.xml file.

2. Add the following parameter to the web.xml file:

   <init-param>
       <param-name>WLIOTimeoutSecs</param-name>
       <param-value>1800</param-value>
   </init-param>
   

3. Save and close the web.xml file.

4. Restart the WebLogic server.