Message Codes Naming Convention

Product execution errors, warnings, and information are reported through detailed log messages that can help trace the cause of the issue. These messages follow a naming convention that indicates the component and log level for each message. The log levels allow you to capture different granularity of messages for different loggers.

Messages returned by the software consist of a code and an associated message.

The message code consists of two parts, a component ID and a 6-digit number, separated by a hyphen (-). The component ID indicates the component that reported the message and the 6-digit number is a numerical range that indicates the logger level.

Note: The Engine layers with component IDs BX and PVM do not follow this convention.

The message describes the issue. Sometimes, the message can contain parameters shown as ({N}), where N is an integer. For example, consider the message for error code TIBCO-BW-ADMIN-500300: The AppNode [{0}] does not exist in AppSpace [{1}] and Domain [{2}]. These parameters are substituted with appropriate values at runtime.