The Verify tab

By simulating the DataPower Cast Iron® Operating System, the Verify tab allows you to test orchestrations within a project and resolve any issues before deploying the project to the Integration Appliance.

When initiating a test run, you can start a single orchestration or all the orchestrations in a project. Studio runs one orchestration job for each orchestration. You can start and stop orchestrations, and view orchestration monitoring logs from the Studio toolbar or from the Verify tab.

If the orchestration is invalid, a message dialog displays possible resolutions. In the workspace, Studio highlights each activity in the orchestration as the activity is processing the data. As Studio runs the orchestration, the Verify tab provides orchestration job details such as activity name, processing status, variable/parameter names, and variable/ parameter data in a tree view. If an error occurs, Studio highlights the node where the error occurred. Clicking the node takes you to the location of the error, where you can resolve any issues before running another instance of the orchestration.

When you click a node in the tree view, Studio displays in the Properties Pane the Checklist task that corresponds to the node. For example, when you click an activity node, Studio displays the Configure panel for the activity in the Properties Pane. When you click the Map Outputs node, Studio displays the Map Outputs panel in the Properties Pane. If you click a mapping variable or parameter, the data displays in the Variable/Parameter Message Data section of the Verify tab.

While Studio only runs one orchestration job for each orchestration, you can start the same orchestration multiple times. The Verify tab displays the results for each run of the same orchestration under a separate instance. For example, Instance #1 and Instance #2. You must allow an orchestration job to complete before you can run another instance of the same orchestration.

Note: Studio does not persist the results of the runtime test. When you close the orchestration tab, you lose runtime results for the orchestration.

Additional Requirements

Depending on the activities in the orchestration, Studio might require more input to run the orchestration job.

For example, an orchestration with a database activity requires that you generate database assets before running the orchestration in Studio, just as you must do in the WMC before running the orchestration on the Integration Appliance. If the orchestration contains an HTTP Receive Request activity, you must post a message to the specified URL. Studio provides an HTTP Post Utility to help you post a message. If the orchestration contains an FTP Poll activity, you must place a file in the specified location before Studio can run the orchestration. Studio prompts you for this information before it runs an orchestration.

Since the Verify tab allows you to simulate the runtime on the Integration Appliance, you can also specify Kerberos Protocol settings in Studio to test the settings before actually deploying to the Integration Appliance. Specifying these setting in Studio does not impact the runtime on the Integration Appliance. You must specify the Kerberos Protocol settings in the WMC to allow the Integration Appliance to authenticate the server that the Integration Appliance is communicating with. For more information about specifying Kerberos Protocol settings for the Integration Appliance, see the WMC Online Help.

Navigating the Verify Tab Toolbar

The following table describes the Verify tab toolbar:
Table 1.
Icon Description
Starts the open orchestration

Starts the open orchestration. The orchestration must be valid before Studio can run an orchestration job.

Stops the running orchestration job immediately

Stops the running orchestration job immediately. Studio does not allow the orchestration job to complete before stopping.

Starts all the valid orchestrations in the project that are not already running

Starts all the valid orchestrations in the project that are not already running. If an orchestration is already running when you click this icon, Studio does not rerun the orchestration.

Stops all running orchestration jobs immediately

Stops all running orchestration jobs immediately. Studio does not allow the orchestration jobs to complete before stopping.

Displays orchestration monitoring data in a table or text format

Displays orchestration monitoring data in a table or text format.

Highlights the activities in the execution path of the orchestration job

In the Workspace, highlights the activities in the execution path of the orchestration job, which allows you can follow the logic Studio used to complete the orchestration job. Different instances can have a different path depending on the inputs and orchestration logic. Click this icon to toggle between providing and not providing a highlighted path.

Assigns the results from the selected instance to the Map Inputs and Map Outputs

Assigns the results from the selected instance to the Map Inputs and Map Outputs, so that when you run a test from the Properties Pane, Studio populates the inputs and outputs with the results of the orchestration job.

Deletes one or more selected instances

Deletes one or more selected instances from the orchestration details tree. To delete multiple instances hold the Shift key or Ctrl key, select the instances you want to delete, and click the icon.

Expands all the nodes

Expands all the nodes under the selected node in the orchestration details tree.

Collapses all the nodes

Collapses all the nodes under the selected node in the orchestration details tree.

Expands a single node

Expands a single node under the selected node in the orchestration details tree.

Collapses a single node

Collapses a single node under the selected node in the orchestration details tree.




Feedback | Notices


Timestamp icon Last updated: Wednesday, February 17, 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.gettingstarted.doc/getstart_theverifytab.html