IBM E02HMLL-I Implementation Guide - Page 178

Table 16. System trace levels (continued) System trace level 5 - And detailed message contents Reported information Prints messages for levels 1 through 4, as well as printing the structure of the business object being processed, with the value of each attribute Collaboration trace level Collaboration developers can code collaboration templates with template-specific tracing. While system tracing (described in "System trace level" on page 165) offers tracing information about the collaboration runtime in general, collaboration tracing provides information about the specific collaboration; for instance: v The developer might design the collaboration to report business decisions that are made based on the data in the business object being processed by the collaboration. v The developer can provide system-type tracing but only do so at certain points in the execution of the collaboration. For instance, system trace level 5 provides full dumps of the business object data in the server output, which can be very helpful for debugging problems, but can also be very cumbersome to read through when it occurs several times during the course of a single collaboration execution. A collaboration developer can provide a full business object dump that is executed during a level of collaboration tracing, and only do it at one particularly problematic point in the flow of the collaboration, so that there is only one business object dump the user must find and read in the server output. To set the collaboration trace level, select the desired value in the range of 0 through 5 in the Collaboration trace level drop-down menu. To find out what kind of information is reported at the different trace levels for a particular collaboration, reference the documentation for that collaboration template. For more information about making changes to collaboration templates to implement collaboration tracing, see the Collaboration Development Guide. Email notification address You can configure a collaboration object so that e-mail notifications are sent in the event of errors related to that specific object. This facilitates interface-specific administration if that is desired. For instance, a site might have one administrator responsible for errors related to InterChange Server Express itself, another administrator specifically for a customer account synchronization interface, and another administrator specifically for an order processing interface. Type the SMTP-compliant e-mail addresses to which you want error notifications sent into the Email notification address field. You can type multiple addresses as long as they are separated by commas. For more information on enabling the system to send e-mail notifications, see "Configuring e-mail notification properties using System Manager" on page 106 and the System Administration Guide. Many collaboration templates feature greater configurability with regard to when e-mail notifications are sent, above and beyond the setting of the value of the Email notification address field. The level of configurability depends entirely on 166 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide