Test Migrated Runbooks
After you migrate your Opalis workflows, test the imported runbooks to verify they function properly. If your imported runbook satisfies ALL of the following criteria, you can test it in the System Center 2012 - Orchestrator Runbook Tester:
The runbook does not produce any warnings when checked in.
The runbook does not use any legacy or missing Opalis Integration Server 6.3 workflow objects.
The runbook does not contain an Invoke Runbook activity that needs to be run as part of the testing. Note this only applies to the beta release as the result of a known issue with the Runbook Tester. To work around this issue, you can use the runbook server to test the runbook. Start the runbook by using the Run button in the Runbook Designer or by using the Start button in the Orchestration console.
Observe the runtime characteristics of the runbook. In most cases the behavior will be unchanged from the behavior in Opalis Integration Server 6.3. If there are differences in behavior, these are almost always associated with differences in behavior of “legacy” mode workflows and “pipeline” mode workflows in Opalis Integration Server 6.3. These two workflow modes in Opalis Integration Server 6.3 provided slightly different results at runtime. Most behavior differences are the result of runbooks created through import of legacy Opalis Integration server 6.3 workflows. This is because Orchestrator runbooks are largely compatible with Opalis Integration Server 6.3 pipeline-mode workflows.
See Also
Tasks
Concepts
-----
For additional resources, see Information and Support for System Center 2012.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----