Logging and Exception Handling

The following sections describe message logging and exception handling for the Adapter for PeopleSoft. A list of error codes and supporting information appears in Adapter for PeopleSoft Error Codes.

The Adapter for PeopleSoft uses the Integration Server logging mechanism to log messages. You can configure and view the Integration Server logs to monitor and troubleshoot the Adapter for PeopleSoft. For detailed information about logging in the Integration Server, including instructions for configuring and viewing the different kinds of logs supported by the server, see the IBM webMethods Integration Server Administrator’s Guide for your release.

Beginning with Integration Server 7.1, you can configure different logging levels for the Adapter for PeopleSoft.

The Integration Server maintains several types of logs; however, the Adapter for PeopleSoft only logs messages to the audit, error and server logs. Because the Adapter for PeopleSoft works in conjunction with the WmART package, the adapter's messages and exceptions typically appear within log messages for the WmART package.

The logging levels are different depending on which version of the Integration Server you are running the adapter on, as shown in the following table.

The Adapter for PeopleSoft's log messages appear in the following format: ADA.0336.nnnnc, where:

• ADA is the facility code that indicates that the message is from an adapter.
• 0336 (or 336) is the Adapter for PeopleSoft major code, which indicates that the error is generated by the Adapter for PeopleSoft.
• nnnn represents the error's minor code. For detailed descriptions of the Adapter for PeopleSoft's minor codes, see Adapter for PeopleSoft Error Codes.
• c represents the message's severity level (optional).

Because the Adapter for PeopleSoft works in conjunction with the WmART package, the adapter's messages and exceptions typically appear within log messages for the WmART package, although that is not necessarily true for verbose-level messages.

To monitor the Adapter for PeopleSoft's log messages in the Server log, ensure that your server log's logging settings are configured to monitor the following facilities:

• 0113 Adapter Runtime (Managed Object)
• 0114 Adapter Runtime
• 0115 Adapter Runtime (Listener)
• 0116 Adapter Runtime (Notification)
• 0117 Adapter Runtime (Adapter Service)
• 0118 Adapter Runtime (Connection)
• 0121 Adapter Runtime (SCC Transaction Manager)
• 0126 Adapter Runtime (SCC Connection Manager)

If a Adapter for PeopleSoft object (for example, a connection or service) encounters an error with the PeopleSoft system, it will throw an adapter error coupled with the PeopleSoft error, exactly as it was thrown by PeopleSoft. The PeopleSoft errors will be in an IData format.

For example, if a Get service fails on the PeopleSoft system at run time because its input fields contain invalid key values, you will receive an adapter error that indicates that the Get service failed, and the adapter error will contain the specific error generated on the PeopleSoft system indicating why the service failed. In this case, you would receive a PeopleSoft error specifying that the input key field values are invalid.