Skip to main content
Version: OpCon (Cloud - Current)

Relays reference

This page provides field definitions, status values, and action requirements for the Relays / NetComs page in Solution Manager. The page displays two grids: the Relays grid in the upper pane and the NetComs grid in the lower pane.

For procedures, see Managing relays. For an overview of relay architecture, see Relays overview.

Relay grid columns

The Relays grid displays all registered relay instances. You can search by name and filter by status.

ColumnDescription
NameThe name of the relay
StatusThe current communication status of the relay. See Status values
PriorityThe relay's failover priority. See Priority values
Client NameThe name of the client associated with the relay
Relay MachineThe machine where the relay is running
VersionThe installed version of the relay software
Upgrade DateThe date and time the relay was last upgraded

NetCom grid columns

The NetComs grid displays all registered NetCom instances. You can search by name and filter by status. The NetCom grid is read-only — you cannot select rows or perform actions on NetCom entries.

ColumnDescription
NameThe name of the NetCom instance
StatusThe current communication status of the NetCom. See Status values
Client NameThe name of the client associated with the NetCom
NetCom MachineThe machine where the NetCom is running
VersionThe installed version of the NetCom software
Upgrade DateThe date and time the NetCom was last upgraded

Status values

The following status values apply to both relay and NetCom entries.

StatusDescription
CommunicatingThe relay or NetCom is actively communicating with the OpCon server
StandbyThe relay or NetCom is available but not actively communicating
StoppedThe relay or NetCom is not running

Priority values

Priority values appear in the Relays grid only. They indicate the relay's role in the failover hierarchy.

ValueMeaning
PrimaryThe relay is the active primary relay (priority 0)
1, 2, 3...The relay is a standby relay. Lower numbers indicate higher failover priority

Relay actions

The following actions are available in the Relays grid toolbar. These actions apply to relays only — no actions are available for NetCom entries.

ActionAvailability
RestartAvailable when a relay with a status of Communicating or Standby is selected
UpgradeAvailable when a relay in Communicating or Standby status is selected and an upgrade is available for that relay version
LogsAvailable when any relay in Communicating or Standby status is selected
Choose FailoverAvailable when all failover requirements are met. See Failover requirements

Failover requirements

The Choose Failover button is available only when all of the following conditions are met:

  • You have the OCADM role
  • Exactly one Primary relay is selected
  • The selected relay has a status of Communicating
  • A Standby relay with the same name exists

Failover transition steps

The Relay Failover dialog displays a static transition process with six steps.

Primary relay steps

StepNameDescription
1Stopping new messagingStops accepting new messages on the primary relay
2Draining message queuesDrains in-flight messages before handoff
3Closing primary relayTerminates all agent connections on the primary relay

Failover relay steps

StepNameDescription
4Reloading agent configurationReloads agent configuration on the failover relay
5Establishing failover relay connectionsEstablishes agent connections from the failover relay
6Starting send/receive from failover relayBegins message send and receive on the failover relay

Relay log file types

The Relay Logs dialog displays three log files, each on a separate tab.

Log fileDescription
SMANetComRelay.logThe main relay log with configuration and communication information
SMANetComRelayAPI.logThe API communication log for relay operations
SMANetComTrace.logA detailed trace log with TCP/IP and socket connection information

Timeouts

OperationTimeout behavior
FailoverPolls for progress every 5 seconds. The operation times out after several minutes if the transition does not complete
RestartPolls for the relay to return to Communicating status. Times out after 2 minutes

Relay API reference

This section documents the REST API endpoints used by Solution Manager to manage relays. These endpoints are useful when automating relay management or integrating relay status into external tooling.

Relay list endpoints

Two endpoints return relay information. Use the one that matches your data source requirement.

EndpointDescription
GET /api/relay/listReturns relays from the static data manager (StaticDataManager.NetcomRelays). Use this endpoint when you need the configured relay definitions.
GET /api/relay/registrationsReturns relays from the NetComRegistrations database table. Use this endpoint when you need live registration data, including current connection state.

The two endpoints return different response shapes. GET /api/relay/list wraps the results in an object:

{
"relays": [ ... ],
"count": number
}

GET /api/relay/registrations returns a JSON array of registration objects directly, without the relays/count wrapper.

Relay response fields

The two endpoints do not return the same set of fields. GET /api/relay/list returns the 7 base fields below. GET /api/relay/registrations returns those 7 fields plus id, upgradeDate, priority, and four capability flags (canRestart, canUpgrade, canGetLogs, canFailover) that indicate which actions each relay supports.

The following table lists every field and indicates which endpoints include it.

FieldType/list/registrationsDescription
relayNamestringYesYesThe name of the relay
clientNamestringYesYesThe name of the client associated with the relay
machineIdstringYesYesThe identifier of the machine where the relay runs
versionstringYesYesThe installed version of the relay software
connectionStatusstringYesYesThe current connection status of the relay
isRelaybooleanYesYesIndicates whether the entry is a relay (true) or a NetCom (false)
activebooleanYesYesIndicates whether the relay is currently active
idintegerNoYesThe registration identifier. Returned only by /registrations
upgradeDatestringNoYesThe date and time the relay was last upgraded. Returned only by /registrations
priorityintegerNoYesThe relay's failover priority (0 = Primary). Returned only by /registrations
canRestartbooleanNoYesIndicates whether the relay supports the restart action. Returned only by /registrations
canUpgradebooleanNoYesIndicates whether the relay supports the upgrade action. Returned only by /registrations
canGetLogsbooleanNoYesIndicates whether the relay supports retrieving logs. Returned only by /registrations
canFailoverbooleanNoYesIndicates whether the relay supports failover. Returned only by /registrations