Activity and IP Compatibility with Orchestrator

System Center 2012 Orchestrator Integration Toolkit has undergone some significant changes in the underlying framework since the previous release as the Opalis Quick Integration Kit. These changes make activities created using the CLI Wizard and activities developed using the Opalis API, as well as Integration Packs packed by the QIK Wizard incompatible with Orchestrator. In order to utilize these activities in Orchestrator, they must be converted to use the new framework. The manner in which these activities were created determines the process required to convert them:

  • Activities created using the QIK CLI Wizard and used in workflows via the “Invoke .NET” activity need simply to be loaded and regenerated using the new Command-Line Activity Wizard. The required process is defined in the section QIK CLI Activity Migration.
  • Activities created using the QIK CLI Wizard and then packaged into an Integration Pack using the QIK Wizard require a two-step process. This includes regenerating the assembly or assemblies for the activities using the process defined in QIK CLI Activity Migration and then repackaging the IP using the new Integration Pack Wizard using the process defined in QIK Integration Pack Migration.
  • Activities developed using the Opalis API and then packaged into an Integration Pack using the QIK Wizard also require a two-step process which involves modifying the source code using the process defined in Migrating QIK API Custom Activities, and repackaging the IP using the new Integration Pack Wizard using the process defined in QIK Integration Pack Migration.

Last edited Sep 21, 2011 at 4:26 PM by rhearn, version 2

Comments

No comments yet.