Automation–Orchestrating Service Manager Orchestrating Orchestrator

Automation–Orchestrating Service Manager Orchestrating Orchestrator

  • Comments 3
  • Likes

Hello Readers/Viewers!

Today I have a special treat for you…well some of you, specifically the folks that are starting to dig deeper into the integration between Service Manager and Orchestrator.

Background

Many of you know this integration is not just a one-way street. It is completely bi-directional. Service Manager can invoke Orchestrator Runbooks and Orchestrator can update Service Manager Objects. There is an Orchestrator Integration Pack for Service Manager and there is an Service Manager Connector for Orchestrator. So much integration, so little time to learn…until now!

Demo Specifics

Many times I put the “useful timestamps” after I embed the video – that will not be the case  this time – since the timestamps also coincide with the main topics for the demonstration(s), I figured I would give them to you here, up front and personal…before the video embed:

  • 00:00:00 - Intro Slides
  • 00:01:10 - Part 1 - Create the Runbooks (Orchestrator)
  • 00:06:17 - Part 1a - Workaround for Orchestrator Runbooks NOT showing up via the Web Service (SQL)
  • 00:07:23 - Part 2 - Sync Service Manager and Orchestrator, verify Runbook exists in Service Manager Library (Service Manager)
  • 00:08:55 - Part 3 - Create the Runbook Automation Activity Template (Service Manager)
  • 00:12:43 - Part 4 - Create the Service Request Template (Service Manager)
  • 00:16:44 - Part 5 - Create the Request Offering (Service Manager)
  • 00:21:05 - Part 6 - Create the Service Offering (Service Manager)
  • 00:23:23 - Part 7 - Initial Test of the Integration between SM and OR (Service Manager, Orchestrator)
  • 00:27:01 - Bonus Demo! Part 1 - Linking back from Runbook to Service Request (Service Manager, Orchestrator)
  • 00:34:40 - Bonus Demo! Part 2 - Final Test of the End-to-End Demo (Service Manager, Orchestrator)
  • 00:38:48 - Summary

 

Oh wow, that is a lot of minutes!

Yes, you are correct. This video has a duration of 00:39:16. But it is chock full of useful information for this very important set of tasks. And hey, it even includes a Bonus Demo! And if nothing else, the timestamps can be leveraged to jump to specific portions of the video that interest you the most.

NOTE: If you watch the video from YouTube itself, the timestamps within the video description are clickable and can be used as a source of navigation (much like a hyperlink enabled table of contents).

Where is this VIDEO DEMO already?

Right here – Roll tape!

 

Related Info

As you will see in the video, I reference a few things…

First, is the SQL I used as a workaround for Orchestrator Runbooks NOT showing up via the Web Service (timestamp range from 00:06:17 to 00:07:23):

TRUNCATE TABLE [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache
EXEC [Microsoft.SystemCenter.Orchestrator.Maintenance].[EnqueueRecurrentTask] @taskName = 'ClearAuthorizationCache'

Second, and last, is the blog post I referenced which was written by Kath McBride: Service Manager: Runbook to Service Offering and Part 2 here!

 

enJOY!

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hey Charles,

    Sometimes simply clearing the authorization doesn't work, the calculation can time out. Check out opalis.wordpress.com/.../runbooks-not-showing-up for more details

  • I was lucky enough to have that SQL work for the specific issue that came up during my demonstration. Instead of cutting all of that "workaround" out of the video, I figured I would leave it in to show one of the options.

    Thanks for sharing more details Ryan -

    People should be aware the it is not normally advised to open/manipulate the Orchestrator DB. Please only do so after the advice provided by support and only implement supported workarounds/solutions in production.