Continuing our series on System Center 2012 SP1 – Orchestrator! If you have being following the previous posts in this series:
I am sure you have taken the opportunity to get acquainted with these new tools, connecting to your Runbook servers, and maybe even attempted to create your first Runbook. As you being to find your way around the designer, which we will cover in greater detail in another post, you will no doubt have located the “Activities” panel docked to the right of the window. Here you will find a vast collection of different activities available to drop on your design canvas, ready for building your runbooks. However, as you spend some time studying the available options, you might be disappointed to find that an activity for a specific technology or action you expected to see is not present. In this post I will show you how to locate activities and install the System Center 2012 SP1 – Orchestrator Integration Pack.
The first thing we are going to learn is that these activities are delivered in bundles that are officially called Integration Management Packs, or integration packs (IPs) for short. These packs are generally available from three primary sources, namely Microsoft, third-party vendors, and the wider public orchestrator user community. Your favorite search engine is going to come in useful in helping you to track down the relevant source for your desired integration packs.
To serve as an example, let’s assume you are looking for an integration pack for Microsoft Exchange. After a quick search, you will find that there are many hits, all of which are looking quite positive. After some additional scrutiny, you determine that there are essentially two possible solutions for our objective:
After taking a closer look at the list of Microsoft Exchange integration packs, you choose to try one or more of these for your project, since the collection of activities offered are very comprehensive when all the packs are considered. You go ahead and decide to download them.
After downloading the integration packs, you may need to first extract the content (depending on the source). Integration packs end with the file extension of .OIP (short for Orchestrator Integration Pack). Once you have the .OIP files ready, we can begin to process of installing the packs.
Installation of Integration packs is a two-step process:
On the Orchestrator Server, launch the Deployment Manager tool.
The wizard will then complete its process and register these new Integration Packs with the management server. The Deployment Manager log entry pane will be updated with any status messages.
With the Integration Packs registered, in order for us to utilize the actives stored within the packs, we must now deploy these packs to the servers which will execute our runbooks, namely the “Runbook Servers”, and also to the systems we will design the runbooks on, namely systems with the “Runbook Designer”. At any time we chose to add additional servers or designers, we can return to this step and deploy these integration packs to the newly added systems.
From the console of the Deployment Manager tool.
The wizard will then complete its process to deploy the new Integration Packs, and as before a progress log will be presented in log entry pane of the deployment manager.
If you now launch the Runbook Designer on one of the systems you just chosen to deploy your new integration pack, you will see that the Activities pane has been updated with a new group per integration pack, each containing a set of new activities ready for your use on the design surface.
In the next post, we will use the designer to create a runbook, to demonstrate just how easy this amazing tool is to use.