Friday, July 13, 2012

Orchestrator: Building an integration pack

systemcenter_2_2d9647a3Continuing from the last couple of posts, today I am going to look at what you need to do to build your own integration pack (once you have written and tested the code bits).

To build your integration pack, you will need:

  • your Compiled C# project – if you’re a noob like me, it will help to know that the files you need typically reside in %my documents%\Visual Studio 2010\Projects\%project name%\%project name%\bin\release folder – that is, if you used Visual Studio 2010 to write and compile.
  • the Orchestrator Integration toolkit

Launch the Integration Pack Wizard to get going.


On the product details screen, be sure to complete all detail. The Category Name field here relates to the Activities bar in the Runbook Designer. So, if you plan on distributing your IPs, be sure to categorise the IP in a way that would make sense to others too.


Next up, you need to add your compiled code and map out the classes.


Click Add and browse to the dll file, and then select the class from the drop down menu:


If you have created multiple classes, you will need to repeat this process for each of them that you want to be translated into tasks in the Activity bar.

Now, if you have used another assembly or code bit that is not compiled into your DLL but is required for successful task execution, you need to include it here:


Now you can finally save the IP:


Finally, you can import it using the Orchestrator Deployment Manager and distribute to your runbook designers.

Note: if you have made changes to your IP and recompiled it, you will first need to remove it from the runbook designers and unregister it before you import it again.


Happy Authoring!

No comments:

Related Posts with Thumbnails