UBR_SRV_COMP_START


The event is generated when the Broker starts a server component. A Broker server component is typically started at the request of a Universal Agent Manager; however, there are times when the Broker starts a server component on its own behalf.

UBR_SRV_COMP_START Event Header

Field Name

Description

eventCategory

Start

eventSeverity

Informational

eventTopic

Component

eventType

302

(Source Fields)

Server component that started.

(Reporter Fields)

Universal Broker that started the component.

UBR_SRV_COMP_START Event Body

Field Name

Notes

Description

applProperties


Application-specific properties used for event correlation by UEC.

certId


Certificate map identifier that the client certificate was mapped to by the Universal Access Control List cert_map entries.

clientCertIssuer

1, 2

Issuer field of the digital certificate provided by the client.

clientCertSerialNo

1, 2

Serial number of the digital certificate provided by the client.

clientCertSubject

1, 2

Subject field of the digital certificate provided by the client.

clientIpAddr

1

IP address from which the client's socket connection was established.

clientPort

1

TCP port number from which the client's socket connection was established.

clientUserId

1, 3, 4

User identifier of the client.

clientWorkId

1

Work identifier of the client.

commandId


Command identifier, specified by the Manager, that is used to identify the unit of work.

comment


User-provided comment associated with the unit of work.

componentId


Component identifier the Broker assigns to the component.

compRestart


Whether or not the component is being restarted.

managerFaultTolerant


Specification for whether or not the server component is manager fault tolerant.

Possible values are:

  • 0 - Job did not execute in Manager Fault Tolerant mode.
  • 1 - Job executed in Manager Fault Tolerant mode.

startDateTime


UTC date and time the component started.

Notes

  1. The client information identifies the entity that requested the Broker to start the component. The Broker may have started the component on its own behalf, in which case, the client information identifies the Broker.
  2. Client digital certificate information is provided only if the client provided a digital certificate.
  3. A case-dependent value.
  4. A case-dependent value, but for pre-3.2 clients, the value is always considered case sensitive.