Record alarm request message. This message contains information about the alarm being recorded. The implementation of this interface may suppress (i.e., perform a no-op) repeated alarms. Repeated alarms are defined as requests that have the same tuple (service, host, code). Default values will be provided for empty parameters since this method is intended to record alarm information, and an exception can not be returned.
![]() ![]() |
|
Record alarm request message. This message contains information about the alarm being recorded. The implementation of this interface may suppress (i.e., perform a no-op) repeated alarms. Repeated alarms are defined as requests that have the same tuple (service, host, code). Default values will be provided for empty parameters since this method is intended to record alarm information, and an exception can not be returned. The global transaction ID for the Web Service transaction. The length of this identifier should be less than 128 is CEI is enabled. The service implementation that originated the fault. The service name is specific to each service implementation and should be chosen to avoid conflicts with other service implementations. The source of the fault. The suggested format is: <server_name>:<ear_name>:<class_name> The code describing the alarm. This code should match the message code used to output the logging message associated with the alarm. This provides synchronization between documented message codes and alarm information. The suggested action to take to resolve the alarm. End Sequence |
![]() |
|||||||
|
![]() |
|
![]() |
![]() |
![]() |
|