Integration Server 10.5 | Audit Logging Guide | Setting Up IS Core Audit Logging | Set Up Additional Service Logging | Write User-Defined Messages to the IS Core Audit Log
 
Write User-Defined Messages to the IS Core Audit Log
If you are storing service audit data in an external RDBMS, and you have installed the Process Engine, you can have services post user-defined progress messages to the IS Core Audit Log. For example, you might have a service post messages to indicate that certain pieces of code ran successfully, or to record run-time values for variables so you can see how the values changed as the service ran. To do so, you make the service call the Integration Server built-in service pub.prt.log:logActivityMessages.
Note:
You view these messages in Monitor.
The pub.prt.log:logActivityMessages service is stored in the WmPRT package. Its input and output parameters are described below.
Input Parameters
FullMessage
String Optional. Complete message to record in the IS Core Audit Log. The message can be up to 1024 bytes.
Note:
If messages recorded in the IS Core Audit Log require more than 1024 characters, you can modify the length of the FULLMESSAGE column in the WMSERVICEACTIVITYLOG table to accommodate a larger value. Keep the following points in mind when increasing the column length:
*If the data written to the FULLMESSAGE column contains multibyte characters, data can be truncated in the middle of a character. To avoid this, Integration Server truncates the last character boundary before the maximum length of the field, which could result in the data contained in the column being slightly smaller than the maximum value set in the audit logging database. To ensure that characters are not truncated, use the watt.server.audit.dbEncoding server configuration parameter to specify the character set used by the audit logging database. For more information about watt.server.audit.dbEncoding, see webMethods Integration Server Administrator’s Guide.
*Integration Server checks the database for column width by obtaining the metadata and examining the CHAR_OCTET_LENGTH field of the column. If the database vendor does not supply a CHAR_OCTET_LENGTH value for the column, Integration Server uses the default length of 1024 characters for the FULLMESSAGE column.
You must restart Integration Server for the new length to take effect.
BriefMessage
String Optional. Shortened version of the full message. The message can be up to 240 bytes.
EntryType
String Type of message.
Message Type
Description
Message
Informational. No action is needed.
Warning
A warning message. The service can complete successfully even if the circumstance causing the warning is not addressed.
Error
An error message. An error message will not stop the service or put it in an error state. However, the service cannot complete successfully until the circumstance causing the error is resolved.
Output Parameters
None.