5 Install HDR on a WebLogic Cluster

5.1 Install HDR Using the HDR Installer

Install HDR using the HDR installer, following the instructions given in Chapter 4.

5.2 Create and configure the HDR WebLogic machine and node manager

To create and configure WebLogic machine and node manager:

1. Log in to the WebLogic administration console.

2. In the left pane, click hdr_domain and expand Environment.

3. Click Machines and then click Lock & Edit.

4. Click New.

   The Create a New Machine screen is displayed.

   Figure 5-1 Create a New Machine

   
   Description of ''Figure 5-1 Create a New Machine''
   
   

5. Enter hdr_machine (or any other preferred name) in the Name field and click Next.

6. Specify the node manager properties.

   Typically, node manager runs on localhost with SSL port 5556.

7. Click Finish.

5.3 Create and configure the HDR cluster

To create and configure the HDR cluster:

1. Log in to the WebLogic administration console.

2. In the left pane, click hdr_domain and expand Environment.

3. Click Clusters and then click Lock & Edit.

4. Click New and then click Dynamic Cluster.

   The Create a New Dynamic Cluster screen is displayed.

   Figure 5-2 Create a New Dynamic Cluster

   
   Description of ''Figure 5-2 Create a New Dynamic Cluster''
   
   

5. Enter hdr_cluster in the Name field.

6. Select Unicast from the Messaging Mode drop-down list.

7. Click Next.

   Figure 5-3 Specify Dynamic Server Properties

   
   Description of ''Figure 5-3 Specify Dynamic Server Properties''
   
   

8. Enter the number of dynamic servers required during the peak load in the Number of Dynamic Servers field.

   Note:

   The number of dynamic servers configured depends on the available system resources and the scalability requirements.

9. Enter a prefix for the dynamic server in the Server Name Prefix field. For example, hdr_server-.

   Based on the number of dynamic servers configured, the number of corresponding managed servers are created. For example, if you have configured three dynamic servers, three corresponding managed servers (hdr_server-1, hdr_server-2, and hdr_server-3) are created.

10. Select Create a new server template using domain defaults.

    The server template contains configurations such as Protocol, Services, SSL, Tuning, and so on, which are configured at each managed server level.

11. Click Next.

    Figure 5-4 Specify Machine Bindings

    
    Description of ''Figure 5-4 Specify Machine Bindings''
    
    

12. Select Use a single machine for all dynamic servers.

13. Select hdr_machine from the Selected Machine drop-down list and click Next.

    Figure 5-5 Specify Listen Port Bindings

    
    

14. Enter a listen port in the Listen Port for First Server field. For example, 8001.

    The first server is assigned to the port specified, and each subsequent server is assigned to an incremental port.

15. Enter an SSL listen port in the SSL Listen Port for First Server field.

16. Click Finish.

5.4 Update the HDR deployment and dependent resources to target the HDR cluster

The existing hdr_server managed server created by the HDR installer can be targeted to hdr_cluster or can be deleted so that HDR can be deployed only on the dynamic cluster servers.

1. Stop the hdr_server managed server.

2. Delete HDR deployment.

3. Select the HDR EAR deployment from the $HDRHome/hdr_exploded_app folder and select deployment as application.

4. Target HDR deployment by selecting the HDR_Cluster and All servers in the cluster options.

   Figure 5-6 Install Application Assistant

   
   Description of ''Figure 5-6 Install Application Assistant''
   
   

5. Provide appropriate name for HDR and click Finish.

6. Click hdr_domain and expand Services.

   The Summary of JDBC Data Sources screen is displayed.

   Figure 5-7 Summary of JDBC Data Sources

   
   Description of ''Figure 5-7 Summary of JDBC Data Sources''
   
   

7. Click Configuration and then select HdrDataSource.

8. Change the targets of datasource HdrDataSource by selecting the HDR_Cluster and the All servers in the cluster options.

   Figure 5-8 Settings for HdrDataSource

   
   Description of ''Figure 5-8 Settings for HdrDataSource''
   
   

9. Click Save.

10. Click hdr_domain and expand Services.

11. Expand Messaging and select JMS Modules and note all the JMS queue names and jndi names in the JMS module HDRJMSSystemModule .

12. Recreate HDRConnectionFactory.

13. Delete all the JMS queues created in the JMS module HDRJMSSystemModule.

14. Recreate the queues again with same jndi names by selecting the Distributed Queue option.

    Figure 5-9 Create a New JMS System Module Resource

    
    Description of ''Figure 5-9 Create a New JMS System Module Resource''
    
    

15. Change the targets of HDRJMSSystemModule by selecting the HDR_Cluster and the All servers in the cluster options.

16. Click hdr_domain and expand Services.

17. Expand Messaging and select JMS Servers.

18. Change the targets of HDRJMSServer by selecting the HDR_Cluster and All servers in the cluster options.

19. Copy the HDR-specific JVM arguments configured in startManagedWebLogic.sh to setDomainEnv.sh.

    Figure 5-10 startManagedWebLogic.sh

    
    Description of ''Figure 5-10 startManagedWebLogic.sh''
    
    

    Figure 5-11 setDomainEnv.sh

    
    Description of ''Figure 5-11 setDomainEnv.sh''
    
    

20. Start the node manages using hdr_domain/bin/startNodeManager.sh

21. Start the dynamic servers in hdr_cluster using the WebLogic admin console.

5.5 Change client-side jndi.properties

To change client-side jndi.properties:

1. Update the HDR client application jndi.properties to use the new cluster provider URL.

2. List all host and port numbers for all managed servers in the cluster as a comma separated value.

   For example:

   java.naming.provider.url=t3://<host>:8001,<host>:8003,<host>:8003