Version 9.5 SP1
 —  High Availability  —

Setting up Your EntireX Environment for High Availability with Other Clustering Technologies

This document covers the following topics:


Setting Broker Attributes

graphics/other-detail.png

Segmenting dynamic workload from static server and management topology is critically important. Using broker TCP/IP-specific attributes, define two separate connection points:

See TCP/IP-specific Attributes under Broker Attributes. Sample attribute file settings:

  Sample Attribute File Settings Note
graphics/no1.png
PORT=1972
In this example, the HOST is not defined, so the default setting will be used (localhost).
graphics/no2.png
HOST=10.20.74.103 (or DNS)
PORT=1811
In this example, the HOST stack is the virtual IP address. The PORT will be shared by other brokers in the cluster.

Top of page

Broker Cluster Considerations

We recommend the following:

Top of page

Configuring Redundant RPC Servers

In addition to broker redundancy, you also need to configure your RPC servers for redundant operations. We recommend the following best practices when setting up your RPC servers:

Top of page

Managing Brokers and RPC Servers

Using System Management Hub

Use the System Management Hub to monitor the status of the broker and RPC server instances using their respective address:port connections. Set up each connection with logical instance names.

graphics/other-detail_manage.png

The following screen shows two pairs of redundant RPC servers registered to the same broker from the Server view:

graphics/common_manage-smh.png

Lifecycle Management of Brokers

An important aspect of high availability is during planned maintenance events such as lifecycle management, applying software fixes, or modifying the number of runtime instances in the cluster. Using a virtual IP networking approach for broker clustering allows high availability to the overall working system while applying these tasks.

Broker administrators, notably on UNIX and Windows systems, have the need to start, ping (for Broker alive check) and stop Broker as well as RPC servers from a system command-line, prompt or from within batch or shell scripts. To control and manage the lifecycle of brokers, the following commands are available:

If only one user is to be permitted to execute commands, enter the command

etbsrv SECURITY ENABLE TRUSTED-USER=YES

The trusted user can then execute commands without any additional authentication. There can only be one trusted user. To change the trusted user, modify the property install.user in file entirex.config.

See Administration Service Commands under UNIX | Windows for more information.

Lifecycle Management of RPC Servers

Start of instruction setTo start an RPC server

Start of instruction setTo ping an RPC server

Start of instruction setTo stop an RPC server

Top of page