H Clustering for the JD Edwards Transaction Server on WebLogic Server

This appendix discusses these topics:

• Section H.1, "Understanding WebLogic Clustering"

• Section H.2, "Creating a Cluster on WebLogic Server"

• Section H.3, "Creating the Servers"

• Section H.4, "Creating Machines"

• Section H.5, "Associate Machines with Servers"

• Section H.6, "Cluster the Servers"

• Section H.7, "Setup the Cluster for Load Balancing"

• Section H.8, "Setup the Cluster for Failover"

• Section H.9, "Installing the Transaction Server RTE Component on WebLogic Server using Server Manager"

• Section H.10, "Using JDBC Persistent Stores"

• Section H.11, "Create JDBC Datasources"

• Section H.12, "Create JDBC Persistent Stores"

• Section H.13, "Associate a JMS Server with a Persistent Store"

• Section H.14, "Additional Configuration for Using Horizontal Cluster"

H.1 Understanding WebLogic Clustering

Clustering permits the deployment of application components and services to several machines with a single face to the client. When a client requests a service, it should make no difference if the service runs on a single server or across a number of servers. The clustering abstraction provides you with a clear route to improving the performance and scalability of the applications with increased administration of hardware and network resources. WebLogic clustering provides these benefits:

• Scalability

  A clustered solution allows you to create additional capacity by introducing more

  servers to the cluster, thereby reducing the load on existing servers. For the JD Edwards EnterpriseOne Transaction Server with the Real Time (RTE) Application, you can add as many servers and messaging engines as you like to meet the performance requirement. The RTE application on WebLogic achieves scalability with the implementation of a messaging engine policy.

• Load balancing

  The ability to distribute requests across all members of the cluster, according to the workload on each server. WebLogic handles load balancing as defined by the Load Balancing Algorithm that you configure on cluster setup. The Transaction Server with RTE on WebLogic only supports round-robin load balancing policy for the RTE application.

• High availability

  A mix of features that ensure applications and services are available even if a server or machine fails. Clients can continue to work with little or no disruption in a highly available environment. RTE on WebLogic achieves high availability with the implementation of a messaging engine policy.

H.2 Creating a Cluster on WebLogic Server

For advanced configuration of the Oracle WebLogic Server refer to this link:

http://download.oracle.com/docs/cd/E15523_01/web.1111/e13709/setup.htm

The section discusses these topics:

• Creating the Servers

• Creating Machines

• Associate Machines with Servers

• Cluster the Servers

• Setup the Cluster for Load Balancing

• Setup the Cluster for Failover

H.3 Creating the Servers

1. On Summary of Servers, click the Lock and Edit button at the bottom of the page.

   
   

2. On Summary of Servers, click the New Button.

   
   

3. On Create a New Server, complete these fields:

   • Server Name

     Enter the name of the new server.

   • Server Listen Address

     Enter the IP address of the physical machine on which this instance will run.

     Note:

     If you want to setup a horizontal Cluster, you should create a server with the remote Server Listen Address.

   • Server Listen Port

     Enter a valid unused port on which this server will listen.

     Note:

     If you want to setup a horizontal Cluster, you should create a server with a Remote Server Listen Port.

4. On Create a New Server, with the entered values accepted, click the Finish button.

   
   

5. On Create a New Server, click the Activate Changes button at the bottom of the screen.

6. Repeat the steps this procedure for any additional servers you want to make part of the cluster.

7. If you want to setup a horizontal Cluster, you should create a server with the remote Server listen Address and Remote Server Listen Port.

   When you complete this procedure, your list of server will be similar to this:

   
   

H.4 Creating Machines

Use this procedure to create the machines:

1. Click Environment > Machines > Lock & Edit.

   
   

2. On Summary of Machines, click the New button.

   
   

3. On Create a New Machine, complete these fields:

   • Name

     Enter the machine name of the host for this clustered server.

   • Machine OS

     Use the pulldown to select the operating system. Choose Other for all non-UNIX operating systems.

4. On Create a New Machine, click the OK button.

5. Click Activate Changes.

6. Repeat the steps in this procedure if your cluster spans multiple machines or if multiple server instances will run on individual machines in the cluster.

   When you complete this procedure, your list of server will be similar to this:

   
   

   Note:

   For the Horizontal Node ensure that the listen address for the server and the machine are exactly the same. This should be the ip of the physical machine, not "localhost" or 127.0.0.1.

H.5 Associate Machines with Servers

Use this procedure to associate machines with Servers:

1. Go to Environment > Machines.

   
   

2. On Summary of Machines, click the Lock & Edit button at the bottom of the screen.

   
   

3. In the Machines list, select the machine for the vertical nodes. If setting up horizontal cluster, select the machine for the horizontal node.

   
   

4. In Settings for <machine>, click on the Servers tab.

   
   

5. In Customize this table, click the Add button.

   
   

6. On Identify Server, complete these fields:

   • Check this radio button:

     Select an existing server, and associate it with this machine

   • Select a server:

     Use the pulldown to select an existing server.

7. Repeat the steps in this procedure if your cluster spans multiple machines or if multiple server instances will run on individual machines in the cluster.

8. Click the Finish button.

9. Click the Activate Changes button.

   When you complete this procedure, your list of server will be similar to this:

   
   

H.6 Cluster the Servers

Use this procedure to cluster the servers.

1. Go to Environment > Clusters.

   
   

2. On Summary of Clusters, click the Lock & Edit button at the bottom of the screen.

3. Click the New button.

   
   

4. On Cluster Properties, complete these fields:

   • Name

     Enter a name for the cluster.

   • Messaging Mode

     Use the pulldown to select Unicast.

   • Unicast Broadcast Channel

     Leave this field blank.

   • Multicast Address

     Accept the default value.

   • Multicast Port

     Accept the default value.

5. Click the OK button.

   
   

6. On Summary of Clusters, click on the newly-defined cluster name.

   
   

7. On Settings for <cluster>, click the Servers tab.

8. Click on the Add button.

9. Select the server.

10. Click next.

11. Repeat the preceding two steps for any additional servers.

12. Click the Activate Changes button.

    When you complete this procedure, your list of server will be similar to this:

    
    

13. Restart the admin server and all node managers.

H.7 Setup the Cluster for Load Balancing

A cluster is setup with load balancing feature with round-robin algorithm by default. However the algorithm to be used can be changed based on requirement.

1. Go to click Environment > Clusters.

2. Click on the cluster name.

3. Go to General tab.

   
   

4. Click the Lock & Edit button.

5. Default Load Algorithm field contains several algorithms in the dropdown. Select the one you want to use. Different load balancing algorithms are round-robin, weight-based and random.

6. Click the Save button.

7. Click the Activate Changes button.

H.8 Setup the Cluster for Failover

A cluster is setup with load balancing feature with round-robin algorithm by default. However the algorithm to be used can be changed based on requirement.

1. Go to Environment > Clusters.

2. Click on the cluster name.

3. Go to Migration tab

4. Click the Lock & Edit button.

5. In the Candidate Machines For Migratable Servers field, move the machines Available to Choose.

   
   

6. On Settings for VC, with the Configuration tab selected, complete this field:

   • Migration Basis

     Use the pulldown to select Consensus.

     Note:

     You can also select database as Migration Basis with additional setup.

7. Click Environment, Migratable Targets.

8. Click on the migratable target.

9. Go to Migration tab.

   
   

10. On Settings for <machine> (migratable), with the Migration tab selected, complete this field:

    • Server Migration Policy

      Use the pulldown to select between these available policies:

      • Manual Service Migration Only

      • Auto-Migrate Exactly-Once Services

      • Auto-Migrate Failure-Recovery Services

11. Click the Save button.

12. Click the Activate Changes button.

H.9 Installing the Transaction Server RTE Component on WebLogic Server using Server Manager

Use this procedure to install the RTE application to the cluster via Server Manager.

1. Install the JD Edwards EnterpriseOne product Server Manager on a machine with the Microsoft Windows operating system.

2. Install the Server Manager agent on the machine that is running the Oracle WebLogic Administration Console.

3. Register the WebLogic server through Server Manager.

4. Logon to the Server Manager console.

   
   

5. On Managed Homes and Managed Instances, click on the machine running the registered Oracle WebLogic Server.

   
   

6. Click the Create New Managed Instance button.

   
   

7. On Create/Register A Managed Instance, Instance Type, click this radio button:

   EnterpriseOne Transaction Server

8. Click the Continue button.

   
   

9. On Create/Register A Managed Instance, Instance Properties, complete the fields:

   • Server Group

     Accept the default value.

   • Instance Name

     Enter an instance name.

   • J2EE Server/Cluster

     Use the pulldown to select the Oracle WebLogic cluster.

   • HTTP Port

     Accept the auto populated value.

     Note:

     You should not manually change this value.

   • Software Component

     Use the pulldown to select a valid JD Edwards RTE application software component for your installation.

10. Click the Continue button.

    
    

11. On Create/Register A Managed Instance, Confirmation, complete these fields:

    • Bootstrap User

      Enter any value that you will use for this user.

    • Bootstrap User Password

      Enter a password.

    • Bootstrap Role

      Enter the JD Edwards EnterpriseOne role for the bootstrap user. For example, *ALL is a valid role.

    • Sequencing Behavior

      Use the pulldown to select the desired behavior.

    • Processing Concurrency

      Use the pulldown to select the desired processing concurrency value. This defines the number of concurrent event processing threads to run.

    • WebSphereMQ Initial Root

      Leave this value blank; it is not applicable to WebLogic installations.

12. Click the Continue button.

    
    

13. On Create/Register A Managed Instance, Finish, click the Create Instance button.

    
    

    Server Manager displays a processing message.

    
    

    The instance screen for the RTE application displays.

    Caution:

    Do not attempt to start the instance at this time. You must continue with the setup instructions in this guide until you are explicitly instructed to start the instance.
    
    

14. In the Configuration section, click Network Settings and complete the fields as applicable for your environment.

    
    

15. In the Configuration section, click JDBJ Database Configuration and complete the fields as applicable for your environment.

    
    

16. In the Configuration section, click Event Processor Configuration settings and confirm the fields are valid for your installation.

    Caution:

    Do not attempt to start the instance at this time. You must continue with the setup instructions in this guide until you are explicitly instructed to start the instance.

H.10 Using JDBC Persistent Stores

Follow the steps below to modify the installed configuration for using JDBC Persistent Stores instead of FileStore. In order to use horizontal clusters, it is mandatory to use JDBC Persistent Stores for JMS Servers.

Caution:

Do not attempt to start the Transaction Server RTE instance or any other managed servers at this time. You must continue with the setup instructions in this guide until you are explicitly instructed to start an instance or managed server.

These instructions assume that you've already created a database to serve as a persistent store.

This chapter discusses these topics:

• Section H.11, "Create JDBC Datasources"

• Section H.12, "Create JDBC Persistent Stores"

• Section H.13, "Associate a JMS Server with a Persistent Store"

H.11 Create JDBC Datasources

Use this procedure to create JDBC Datasources.

1. Logon to the WebLogic Administration Console.

2. Go to Services > Data Sources.

   
   

3. On Summary of JDBC Data Sources, click the Lock & Edit button.

   
   

4. On Summary of JDBC Data Sources, in the Customize this table section, use the New pulldown to select Generic Data Source.

   
   

5. On Create a New JDBC Data Source, JDBC Data Source Properties, complete these fields:

   • Name

     Enter a name for the JDBC data source.

   • JNDI Name

     Enter a name for the JNDI.

   • Database Type

     Use the pulldown to select your database type.

6. Click the Next button.

   
   

7. On Create a New JDBC Data Source, use the pulldown to select the driver appropriate for your database.

   Note:

   For Oracle databases, you must select the thin driver. You cannot use an XA driver.

8. Click the Next button.

   
   

9. On Create a New JDBC Data Source, Transaction Options, deselect this checkbox:

   Supports Global Transactions

10. Click the Next button.

    
    

11. On Create a New JDBC Data Source, Connection Properties, complete these fields:

    • Database Name

      Enter a name for the database to which you want to connect.

    • Host Name

      Enter the name or IP address of the database server.

    • Port

      Enter the port on the database server which is used to connect.

    • Database User Name

      Enter the database account you want to use to create the database connections.

    • Password

      Enter the database account password to use to create database connections.

    • Confirm Password

      Confirm the database account password.

12. Click the Next button.

    
    

13. On Create a New JDBC Data Source, Test Database Connection, click the Test Configuration button.

14. Ensure you receive this message: connection test succeeded

15. Click the Next button.

    
    

16. On Summary of JDBC Data Sources, in the list of Data Sources (Filtered - More Columns Exist), select the checkboxes for all servers in the cluster.

    
    

17. Click the Finish button at the bottom of the page.

18. Repeat the applicable steps in this procedure to add additional JDBC data sources.

19. Click Activate changes.

H.12 Create JDBC Persistent Stores

Server Manager deploys the RTE solution with file persistent stores already created. This works for vertical clusters, but should be changed to JDBC type persistent stores for horizontal clusters.

Use this procedure to create the necessary JDBC persistent stores.

1. Go to Services > Persistent Stores.

   
   

2. On Summary of Persistent Stores, click the Lock & Edit Button.

   
   

3. On Summary of Persistent Stores, in the Customize this table section, click the New pulldown and on the flyout choose Create JDBCStore.

   
   

4. On Settings for JDBCStore, complete these fields:

   • Name

     Enter a name for the JDBC store. The name must be unique within the WebLogic Server instance or its cluster.

   • Target

     Use the pulldown to select the migratable server. The list will show of all WebLogic Server instances that have been defined in the current domain and are therefore candidates for hosting this JDBC store.

   • Data Source

     Use the pulldown to select the JDBC data source used by this JDBC store to access its backing table.

     Caution:

     The list will only show JDBC datasources that:

     • Do not use global transactions.

     • Do not use a non XA JDBC driver.

     • Are not configured to enable Logging Last Resource

     • Are not configured to Emulate Two-Phase Commit

   • Prefix Name

     Leave this field blank.

5. Click the Save button.

6. Click the OK button.

7. Repeat the applicable steps to add additional persistent stores for additional JMS servers.

8. Click the Activate Changes button.

   When you complete this procedure, your list of server will be similar to this:

   
   

H.13 Associate a JMS Server with a Persistent Store

Server Manager by default associates the JMS Servers with file persistent stores. For using JDBC store or using horizontal cluster, you must associate the JMS Servers with JDBC persistent stores.

Use this procedure to associate a JMS Server with a persistent store:

1. Go to Services > Messaging > JMS Servers.

   
   

2. On Summary of JMS Server, click the Lock & Edit button at the bottom of the page.

   
   

3. On Summary of JMS Server, in the JMS Servers (Filtered - More Columsn Exist), click on the JMS Server that you want to associate with a persistent store.

   
   

4. Click on the General Tab and complete these fields:

   • Persistent Store

     Use the pulldown to select the JDBC Store to which you want to associate.

   • Paging Directory

     Accept the default value.

   • Message Buffer Size

     Accept the default value.

   • Hosting Temporary Destinations

     Ensure the checkbox for this option is selected.

   • Module Containing Temporary Templates

     Accept the default value.

   • Temporary Template Name

     Accept the default value.

   • Expiration Scan Interval

     Accept the default value.

5. Click the Save button.

6. Click the Activate Changes button.

7. Repeat the applicable steps to add JMS Servers and persistent stores.

   When you complete this procedure, your list of server will be similar to this:

   
   

H.14 Additional Configuration for Using Horizontal Cluster

Server Manager creates the necessary file structure on the node that the WebLogic Administration Console resides on. However, for any horizontal cluster nodes, these files should be transferred manually. On Windows Machines, this should be done through Windows Explorer. For Unix or Linux machines, this should be done through FTP. The steps below use Linux/FTP as an example.

1. Use these steps to determine where the RTE installation is looking for the requisite ini files:

   1. Go to Servers > Server_Name.

   2. Click on the Server Start tab.

      
      

   3. In the Arguments section, note the -Ddefault_path structure.

      For example, in the above example the structure is:

      /u01/JDEdwards/JDE_AGENT/targets/RTEInst/config

      This is the directory that is created on the horizontal node and where the necessary files must be copied.

   4. On the target machine, you must pre-create the necessary directory structure.

      For example:

      
      

   5. Copy the config files from the vertical node machine to the horizontal node machine.

      In the below example, the vertical node machine is dendell03 and the horizontal node machine is dnhpbl12.

      Note:

      If you are using UNIX or Linux machines, ensure you have the correct permissions for the new directory. For example:

      chmod 777 -R JDEdwards