Creating an orchestration
There are three steps to creating a completed orchestration:
Create the new orchestration, rename the orchestration, and build
the orchestration.
Renaming an orchestration
Orchestrations are given default names when they are created.
You can rename it from the Project tab.
Building an orchestration
Studio provides visual cues in the workspace so that it
is easier to see and control the placement of activities in an orchestration.
When you drag-and-drop activities from the Studio Toolbox to the workspace,
a green circle icon displays the target location in the orchestration
where the activity is to be placed. When adding activities to the
branches of logic activities, Studio highlights the target branch.
Verifying orchestrations
Studio can simulate the WebSphere® 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.
Using the Log Viewer
Orchestration monitoring data is displayed in the Log Viewer
in a table or text format.
Viewing an orchestration
You can use orchestration view icons on the workspace,
and View options from the Studio toolbar menu
to manipulate your orchestration view in the workspace.
Validating an orchestration
An orchestration must be valid (complete and correct) before
you can publish it to the Integration Appliance. Use the validation
feature in Studio to validate your orchestration.
Printing an orchestration
You can print an orchestration directly or view a print
preview of an orchestration.
Processing orchestration jobs sequentially
You can use the Process Orchestration Jobs Sequentially
option when an orchestration contains activities that can conflict
with each other when multiple instances of the orchestration are running.
An instance of an orchestration is also known as an orchestration
job.
Enabling persistence
The Orchestration pane contains an Enable Persistence check
box that by default is selected. The setting of the Enable Persistence
check box affects the way orchestration jobs are restarted after a
failure.
Adding a global exception handler to an orchestration
During run time if any of the activities of the orchestration
throws an exception, and a global exception handler has been enabled,
the global CatchAll branch is run.