Configuring a Clustered Business Services Server Instance for Consumer Business Services

You can use Server Manager to create a clustered business services server instance to support clustering for consumer business services. This clustering feature enables scalability, load balancing, and high availability for consumer business services by providing multiple incoming ports so that multiple servers in the cluster can open socket connection to different ports to receive incoming JDENet messages from the Enterprise Server, and the Enterprise Server can send JDENet messages to multiple clustered business services server ports.

See "Configuring a Clustered Business Services Server Instance for Consumer Business Services" in the JD Edwards EnterpriseOne Tools Server Manager Guide.

When you use Server Manager to create the business services server instance, you enter host/port information for all of the servers in the cluster in the Cluster Listen Host/Port field in the Miscellaneous area of the Configuration section. This information is stored with the property clusterHostPort under the CLUSTEROUTBOUND section of the JDEINTEROP.ini of the Busienss Services server instance. When the Business Services Server instance is started, the configuration information is read, and the host/port information is written to the Cluster Server Info table (F986102). Table F986102 includes a status for each business services service in the cluster. A status of AV indicates that the server is active and available. A status of NA indicates the server is stopped. When a business services server has a status of NA, the Enterprise Server does not attempt to send the JDENet message to that particular server.

When a consumer business service runs, the business service calls a business function that is running on the Enterprise Server. The business function reads the clustered business services server host/port information from the F986102 table and identifies only those business services servers in the cluster that have a status of AV and stores the host/port information for the available business services servers in a list. To minimize database calls, the business function does not read from the table if data already exists in the list. To ensure there is update-to-date information in the list, the business function reads and stores the information from the table and refreshes the list.

The business function tries to send the JDENet message to the first host/port item in the list. For subsequent requests, the business function tries to send the JDENet message to the next host/port item in the list in a round-robin fashion. Before sending the JDENet message, the business function pings the host/port. If the ping is successful, the message is sent; if the ping is not successful, the business function tries to send the message to the next active host/port in a round-robin fashion.

When a stopped business services server is started, this business services server is added to the list within 15 minutes, due to the database refresh for Table F986102. This enables load balancing and failover to be achieved effectively.