IBM E02HMLL-I Implementation Guide - Page 260
Business, object, trace, behavior
View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 260 highlights
For example, if you are testing an interface in which a connector sends a business object request to a collaboration object which sends it to a destination connector, which processes it and then returns a response, then Integrated Test Environment captures the following business object data: v The generic business object produced by the map that is called by the source connector when sending the business object request to InterChange Server Express. v The generic business object supplied as input to the map that is called by the destination connector. v The generic business object produced by the map that is called by the destination connector when returning the business object response to InterChange Server Express. v Exception messages related to failed flows. Figure 75 shows a BO Inspector view that has captured three input business objects, two result business objects, and an exception message. Figure 75. Business object inspector view This section describes how to use business object tracing and BO Inspector views. Business object trace behavior The following statements describe the behavior related to BO Markers in the Test Unit editor and BO Inspector views as a business object is processed by an interface: v When you send a business object request from a source connector, the BO Marker attached to the connector icon in the Test Unit editor is filled with green 248 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide