If you use business object tracing, Integrated Test Environment gathers information about a business object while the system processes the business object. Integrated Test Environment captures an image of the business object after it has been processed by a map and after it has been processed by a collaboration.
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:
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.
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:
You can show the BO Inspector view for this BO Marker at this point and see the generic business object produced by the inbound map. It is identified with a prefix of "in" in the drop-down menu in the upper-left of the BO Inspector view.
When this occurs the BO Marker attached to the destination connector icon in the Server Context Overlay is filled with green and the number 1 is displayed above the magnifying glass illustration in the BO Marker, indicating that it, too, has processed the business object.
You can show the BO Inspector view for this BO Marker at this point and see the generic business object that was processed by the outbound map. It is identified with a prefix of "out" in the drop-down menu in the upper-left of the BO Inspector view.
At this point you can view the generic business object in the first BO Inspector view. It is identified with a prefix of "result" in the drop-down menu in the upper-left of the BO Inspector view. Because the same BO Inspector view also contains data for the "in" business object instance, you must select the "result" instance from the drop-down menu.
The following sections describe the numerous ways you can show and close BO Inspector views.
The "Default interface position" column in Table 31 lists the views whose default positions in the interface are overlaid with the BO Inspector views in the "BO Viewer number" column.
Table 31. Default BO Inspector view positions
BO Viewer number | Default interface position |
---|---|
BO Viewer 1 | Outline |
BO Viewer 2 | Properties |
BO Viewer 3 | Dependency |
Use one of the following techniques to show BO Inspector views:
Use one of the following techniques to close all BO Inspector views:
As the components of an interface process a business object, the counters of the BO Markers in the Test Unit editor get updated. This indicates that you can update the business object data in the BO Inspector view associated with that BO Marker to view the most recently produced business object.
Do one of the following to update the business object data in a BO Inspector view:
After the business object data is refreshed, you can select the most current business object instance from the drop-down menu in the upper-left-hand corner of the BO Inspector view.
For information on refreshing BO Markers in the Server Context Overlay, see Refreshing BO Markers.
There are several view styles you can use with the BO Inspector view.
The Table view style presents the business object data in a table, as it appears in the Input Pane of the Client Simulator view or in the "Response BO" window.
Figure 75 shows the BO Inspector view with the Table view style.
Do one of the following to use the Table view style:
The Text view style presents the business object data in the text markup format in which it is stored when exported from the Client Simulator view or "Response BO" window.
Figure 76 shows the BO Inspector view with the Text view style.
Figure 76. BO Inspector view with business object data in text view style
To view an exception message in a BO Inspector view, you must change it to the Text view style; the BO Inspector view cannot display an exception message in the Table view style.
Figure 77 shows an exception message in the BO Inspector view with the Text view style.
Figure 77. BO Inspector view with exception information in text view style
Do one of the following to use the Text view style:
You can arrange a BO Inspector view so that it displays the Text view beneath the Table view at the same time.
To arrange the BO Inspector view panes vertically, click the down arrow in the right-hand corner of the title bar of the BO Inspector view and select Arrange Vertical from the menu.
Figure 78 shows the BO Inspector view panes when they have been arranged vertically.
Figure 78. BO Inspector view panes arranged vertically
You can arrange a BO Inspector view so that it displays the Text view to the right of the Table view at the same time.
To arrange the BO Inspector view panes horizontally, click the down arrow in the right-hand corner of the title bar of the BO Inspector view and select Arrange Horizontal from the menu.
Figure 79 shows the BO Inspector view panes when they have been arranged horizontally.
Figure 79. BO Inspector view panes arranged horizontally
Although there is no built-in mechanism for saving test data in a BO Inspector view, you can use the following workaround:
You can use the saved text file in Map Designer Express, Test Connector, and Integrated Test Environment.
Business object tracing can be a very resource intensive task. By default it is configured to turn off after two hours, though you can change this timeout value. Furthermore, you can configure Integrated Test Environment so that it does not automatically update the counters of BO Markers as business objects are processed, which can be a resource-intensive task in high-volume transactions. Do the following to configure preferences related to business object tracing: