Logging and Error Handling

Message handling functionality provides a consistent view of what is happening internally with the engine and the resources used by the engine. The output is in the form of informational and error messages within log files. The following log files provide informational and error information relevant to runtime management.

You can view instance logs using the Show Instance Log option available for each runtime instance in the Server Explorer.

For some logging mechanisms, runtime configuration properties can be set to define the level of activity logged.

 

Log File

Description

agent.log

This file at the root of the <server> directory logs activity on the Agent.

The location of this file as specified in the agent.properties file can be user-defined.

NNSYMessageLog.nml

This file in the <server>\instances\<instance name>\runtime directory logs business process activity as it flows through the runtime engine. The Engine Logging Level and Engine Logging Threads configuration properties define the level of detail logged. See NNSYMessageLog.nml Message Contents.

psengine.log

This file in the <server>\instances\<instance name>\runtime directory logs engine activity and displays 'print to console' information that is defined in a business process. The Services Console Logging Level configuration property defines the activity logged. See Runtime Instance Configuration Properties and Services Error Handling and Logging.

sybesp.log

This file in the <server>\instances\<instance name>\runtime directory logs plugin activity used to connect  to Web services, databases, messaging transports, probe transport, and XSLT transformation. If an error occurs, the information is also presented in the NNSYMessageLog.nml file.

The Services Log File configuration property defaults to name sybesp.log as the file and the Services Log Level configuration property defines the level of activity logged.

.log

This file in the <client>\eclipse\workspace\.metadata directory logs activity and error messages that occur in the Unwired Orchestrator GUI.