Server registry in Sterling Order Management System Software

Sterling Order Management System Software maintains information on how to locate each of the server instances (e.g., the application server, agent and integration server instances) for system management purposes.

For example, a server that changes cached reference data must notify its peers to update their cache.

When a server instances starts, it stores its server name and the URL to itself in a registry. In Sterling Order Management System Software, Release 9.1, the registry resides in the YFS_HEARTBEAT database table.

Any server instance can query the YFS_HEARTBEAT to find all the other server instances.

Sterling Order Management System Software uses the JNDI information for the following events:

• Reference data cache refresh – Sterling Order Management System Software implements a mid-tier data cache to cache commonly used reference data. If a server instance changes a cacheable record, that instance needs to broadcast that change to instruct all the other server instances to refresh their cache.
• The System Management Console uses the registry to discover all the application instances. The SMC uses that list to build a list of instances to monitor.

In addition to the initial registration on start up, every server has to periodically update its registry record to indicate that it is still alive.

In past releases, if the JNDI service was unavailable, you would not be able to start servers or notify peers of system management changes. In this release, the registry's availability posture is the same as the database service. If the database service is down, the application would be down therefore, there would be no need for the registry.