SCO 2012 Tricks: Change Integration Pack Connection name when transferring runbooks between environments

 

One trick that I always recommended for everyone who is designing Orchestrator runbooks, is to name their Connections properly.

If you have 2 environments, one test and one production, the easiest way to transfer runbooks is the name the connection configurations in the 2 environments exactly the same name.

but in some cases this is not possible to have them named the same.

One scenario could be when transferring from one customer to another.

 

Luckily it is easy to fix!

Since all exports are XML files, you can change the name of the connections in a couple of easy steps.

  1. Using the Runbook designer, export the runbook or folder to an ois_export file.
  2. Open the file in text editor or in XML notepad (get xml notepad http://www.microsoft.com/en-us/download/details.aspx?id=7973)
  3. Search for <Connection datatype="string">SCSM</Connection> (replace SCSM with your connection name)
  4. Replace any instances of the connection name by the new connection name.

That’s it! Smile

By | 2012-07-02T11:13:00+00:00 July 2nd, 2012|Automation|3 Comments

About the Author:

Jakob Gottlieb Svendsen

Twitter: @JakobGSvendsen

Jakob Gottlieb Svendsen is a Microsoft Cloud and Data Center Management MVP (http://mvp.microsoft.com/en-us/default.aspx), Working as Global Lead Developer, Senior Consultant and Trainer at CTGlobal, where he is one of the driving forces in keeping CTGlobal a System Center Gold Partner and member of the System Center Alliance.

Since he started at Coretech in 2007, he has focused on Scripting and Development, primarily developing tools, extensions and scripts for the System Center Suite. His main area is Automation (including OMS/Azure Automation, Service Management Automation, PowerShell and Orchestrator). Another area is Windows Azure Pack / Azure Stack, where he does implementation, development, workshops and presentations. He is a world-wide renowned voice in the Automation field.

He is passionately devoted to the community, to which he contributes by being a moderator at TechNet and sharing his knowledge at https://blog.ctglobalservices.com/jgs

  • Co-founder: PowerShell User Group Denmark
  • Speaker at MMS 2016, Minneapolis (www.mmsmoa.com)
  • SCU Europe 2014, 2015, 2016 (www.systemcenteruniverse.ch)
  • Microsoft TechEd North America 2014, Houston
  • NIC 2012,2013,2014,2015, Oslo (www.nic.com)
  • Microsoft CampusDays 2011, 2013, Copenhagen
  • Microsoft TechDays 2015, Sweden (www.techdays.se)
  • Microsoft Partner Event: New in SC2012 SP1
  • User group meetings (PSUG.DK , SCUG.DK/BE/NO, AZMUG + more)
  • Microsoft Certified Trainer.
  • Microsoft Scripting Guys Forum Moderator

Main working areas:

  • Automation (Azure Automation, SMA, SCO)
  • Windows Azure Pack / Azure Stack
  • System CenterVisual Studio Team Services / Team Foundation Server
  • Development:C#.Net, VB.NET, VBScript, PowerShell, Service Manager, OpsMgr, ConfigMgr
  • Orchestrator
  • Windows Azure Pack / Azure Stack

Training:

  • Azure Automation
  • Service Management Automation
  • System Center Orchestrator
  • PowerShell, VBScript, C#.Net, VB.Net
  • Windows Azure Pack / Azure Stack Development Workshops

3 Comments

  1. HD August 9, 2012 at 13:56 - Reply

    thanks for your interesting Post.
    I use the Microsoft AD IP and i would like to switch the create User connection from my Test Domain to the production environment.
    If I export the runbook and modify Configuration datatype in the XML File i can’t import the modified ois_export file.

    Do you have any ideas?

  2. Jakob Gottlieb Svendsen
    Jakob Gottlieb Svendsen August 9, 2012 at 16:09 - Reply

    It is hard for me to guess what could be wrong since you do not provide an error message.

    do you get an error message?

    Maybe you have replaced the name in too many places, I mean if some other object has the same name, and you accidently replaced that name too.

  3. […] « SCO 2012 Tricks: Change Integration Pack Connection name when transferring runbooks between environm… SCO 2012 – SCOM 2012: Best Practice – Monitor alert and restart a service […]

Leave A Comment