Verifying orchestrations
Studio can simulate the Cast Iron® operating system (CIOS) runtime so that you can to test orchestrations within a project and resolve any issues before deploying the project to the Integration Appliance.
Before you begin
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 is displayed showing 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 shows a tree-view of the orchestration job details including; activity name, processing status, variable/parameter names, and variable/parameter data. If an error occurs, Studio highlights the node where the error occurred. Clicking the node links 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, the Configure panel for the activity is displayed in the Properties Pane. When you click the Map Outputs node, the Map Outputs panel is displayed in the Properties Pane. If you click a mapping variable or parameter, the data is displayed in the Variable/Parameter Message Data section of the Verify tab.
Although Studio only runs one orchestration job for each orchestration, you can start the same orchestration multiple times. The Verify tab shows the results for each run of the same orchestration under a separate instance. For example, Instance #1 and Instance #2. An orchestration job must be complete before you can run another instance of the same orchestration.
About this task
Depending on the activities in the orchestration, Studio may 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 activities in the orchestration use the Secure Sockets Layer (SSL), you may need to understand SSL concepts and you may need to import certificates before verifying the orchestration. See Using SSL in Studio for more information.
If the orchestration contains an HTTP Receive Request activity, you must post a message to the specified URL. Use theHTTP Post Utility to post a message. If the orchestration contains an FTP Poll activity, you must place a file in the specified location, as prompted by Studio, before the orchestration can run.
Since you can use the Verify tab to simulate the runtime on the Integration Appliance, you can also specify Kerberos Protocol settings in Studio to test the settings before 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.
Procedure
To specify Kerberos Protocol settings in Studio:
- In Studio, select The . Preferences dialog is displayed.
- In the navigation pane, select .
- Specify the Kerberos Server Name.
- Specify the Kerberos Realm.
- Click OK.
Example
You can now test the orchestration, using the Kerberos Protocol, within Studio.
Icon | Description |
---|---|
![]() |
Starts the open orchestration. The orchestration must be valid before Studio can run an orchestration job. |
![]() |
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 the running orchestration job immediately. Studio does not allow the orchestration job to complete before stopping. |
![]() |
Stops all running orchestration jobs immediately. Studio does not allow the orchestration jobs to complete before stopping. |
![]() |
Shows orchestration monitoring data in a table or text format. For more information about the Log Viewer, see Using the Log Viewer. |
![]() |
In the Workspace, highlights the activities in the execution path of the orchestration job, so 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, so that when you run a test from the Properties Pane, Studio populates the inputs and outputs with the results of the completed orchestration job. |
![]() |
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 under the selected node in the orchestration details tree. |
![]() |
Collapses all the nodes under the selected node in the orchestration details tree. |
![]() |
Expands a single node under the selected node in the orchestration details tree. |
![]() |
Collapses a single node under the selected node in the orchestration details tree. |