To support continuous operation, OpenEdge databases log secondary broker parameters, keep secondary brokers running during recovery transitions, and let you disconnect secondary brokers without a process kill signal.

Secondary brokers let you manage the configuration for a specific group of end users such as ABL clients, SQL clients, or both.

OpenEdge features like these help you manage brokers to support continuous operation:

  • Brokers keep running during recovery transitions—To finish transitions faster, database brokers continue running on single targets and replication sets. This improves both manual and automatic recovery transitions. For more information, see Plan for transition in Use Database Replication.

  • You can disconnect secondary brokers from PROMON—A PROMON option lets you disconnect secondary brokers without issuing a process kill signal.

    This option reduces potential database downtime. For details, see Server Options in Manage the OpenEdge Database.

  • The database log file (.lg) logs secondary broker parameters—The database log file captures information that helps you understand the circumstances surrounding a failure. The log now records startup parameters for secondary brokers.

    Although you can list broker parameters for running servers by using PROMON R&D Status or Virtual System Tables, the database log file lets you troubleshoot landscape or connection issues after server failure. You can easily determine which brokers were active during an event.

    For an example, see Find connected brokers and servers in Manage the OpenEdge Database.