Using the Outline view

The Outline view allows you to do a number of things described in the following sections:

Figure 77 shows the Outline view.

Figure 77. Outline view showing User Artifacts


Working with dependents using the Outline view

As described in Dependencies and references, IBM WebSphere InterChange Server components depend on other components to function properly. To test an interface, you must make sure that all of its dependencies are resolved.

The Outline view in Integrated Test Environment lists the component dependencies that must be resolved to test the interface. The system is able to determine many dependencies among components, and lists them under the Dependents node beneath the Artifacts node in the Outline view.

Dependencies that cannot be detected by the system describes the situations in which some components cannot be automatically detected by the system. If you use Integrated Test Environment views to deploy components when testing an interface then you must make sure that even the dependencies that cannot be detected by the system are resolved. To do this, you can specify those undetectable dependencies yourself. After you do so, the components are listed under the User Artifacts node beneath the Artifacts node in the Outline view.

Adding user dependents

Do one of the following to add a component to a test unit as a user dependent:

  1. In the Outline view, expand the Artifacts node.
  2. Right-click the User Artifacts node and select Add User Artifacts from the context menu.
  3. At the User Dependents window select the components you want to add. You can use standard multiple-selection techniques, such as holding down Shift to select contiguous rows and holding down Ctrl to select non-contiguous rows. Figure 78 shows the "User Dependents" dialog:

    Figure 78. Adding user dependents


  4. Click OK.
Note:
Only components that are not already registered as dependents are displayed in the list.

Deleting user dependents

Expand the Artifacts node in the Outline view and do one of the following to remove components from the list of user artifacts:

Storing user dependents

You can store the user dependents that you add to a test unit so that you do not have to add them each time. Do one of the following to store the user dependents:

  1. Expand the Artifacts node in the Outline view.
  2. Right-click the User Artifacts node and select Save User Dependents from the context menu.

Managing the repository using the Outline view

All of the components required for an interface must be deployed to the server repository to test the interface. The Outline view provides a way to work with the InterChange Server repository to ensure that it contains the required components.

When you deploy components, you can either use the Deploy option, which deploys the component, or the Deploy with overwrite option, which will deploy the component even if it already exists in the server repository. If the selected components already exist in the server repository and you use the Deploy option then the deployment will fail.

Do one of the following and choose either Deploy or Deploy with overwrite from the context menu to deploy the desired components:

To remove a component from the server repository using the Outline view, right-click the component in the view and choose Remove from server from the context menu.

Note:
You can use standard Windows selection techniques to affect multiple components at the same time, such as the following:

Entries are written to the Integrated Test Environment Console and InterChange Server Console indicating whether the deployment was successful or not.

Managing component states using the Outline view

You can change the state of a component within Integrated Test Environment. This allows you to resolve problems you discover during testing--you can deactivate the component, modify it, re-deploy it, and re-activate it without using System Manager, repos_copy, or System Monitor.

To change the state of a component, right-click it in the Outline view and choose the desired state operation--Start, Pause, or Stop. Not all component types have all state operations available.

For information on component states, see the System Administration Guide.

Executing tasks using the Outline view

You can execute some of the tasks that are part of performing a test using the Outline view. For more information on tasks and task groups, see Table 25.

To execute all of the tasks in the "Start Server" task group, right-click either the "InterChange Server" or "Running State" nodes in the Outline view and choose Start Server from the context menu.

To execute the "Shutdown Server" task, right-click either the "InterChange Server" or "Running State" nodes in the Outline view and choose Stop Server from the context menu.

To execute the "Connect To Server" task, right-click the "Connection State" node in the Outline view and choose Connect To Server from the context menu.

To execute the "Disconnect Server" task, right-click the "Connection State" node in the Outline view and choose Disconnect Server from the context menu.

To execute all of the tasks in the "Start Client Simulators" task group, right-click the "Client Simulators" node in the Outline view and choose Start client simulators from the context menu.

To execute all of the tasks in the "Start BO Trace" task group, right-click the "BO Inspection Markers" node in the Outline view and choose Start BO Trace from the context menu.

To execute the "Stop BO Trace" task, right-click the "BO Inspection Markers" node in the Outline view and choose Stop BO Trace from the context menu.

Verifying test readiness using the Outline view

The Outline view gives a visual indicator of the state of several conditions that must be satisfied to perform a test. This allows you to quickly confirm if you are ready to perform tests in Integrated Test Environment without having to search for indicators in log text. Each condition that must be satisfied has a green background if it has been satisfied and has a red background if it has not been satisfied. Each condition also has a phrase that indicates its status. The following are the different nodes whose conditions must be satisfied, along with descriptions of the requirements and the phrases displayed when the conditions have been satisfied:

Showing and closing Client Simulator views using the Outline view

You use Client Simulator views to emulate connectors and access clients when testing an interface. Client Simulator views provide interfaces to create business object instances with test data, send them as business object requests, and reply to them as business object responses.

To load the profile for a connector into a particular Client Simulator view, right-click the desired port under the "Client Simulators" node and select Use Client Simulator x, where x is the number of the Client Simulator view position you want to use for that connector.

Table 29 shows the default interface positions in which the different Client Simulator views are displayed.

Views in Integrated Test Environment can be concealed by other views during different stages of a test; for example, a Client Simulator view might be concealed by a BO Inspector view. To reveal a Client Simulator view that is concealed, right-click the desired port under the "Client Simulators" node and select Show Client Simulator to give focus to the Client Simulator view.

To close a Client Simulator view, right-click the desired port under the "Client Simulators" node and select Close Client Simulator.

Note:
This option not only closes the Client Simulator view, but also causes the Client Simulator view to stop emulating the connector.

For more information on working with Client Simulator views, see Using the Client Simulator view.

Showing and closing BO Inspector views using the Outline view

If you use business object tracing, Integrated Test Environment records business object data at certain points during the execution of the interface.

To show BO Inspector views for all the business object markers in the interface, right-click the "BO Inspection Markers" node in the Outline view and select Show All BO Viewers from the context menu. BO Marker icons are identified in Figure 81.

To close all the displayed BO Inspector views in the interface, right-click the "BO Inspection Markers" node in the Outline view and select Close All BO Viewers from the context menu.

Table 31 shows the default interface positions in which the different BO Inspector views are displayed.

For more information on using business object tracing, see Table 25.

For more information on working with BO Inspector views, see Using the BO Inspector view.

Refreshing BO Markers using the Outline view

If you are using business object tracing but have disabled auto-update of the trace information then you must explicitly refresh the BO Markers to update them.

To update BO Markers, right-click the "BO Inspection Markers" node in the Outline view and select Refresh BO Markers from the context menu.

Copyright IBM Corp. 1997, 2004