Upgrading HP Operations Orchestration included with Matrix OE to HP Operations Orchestration 10.x

2
Introduction
This document describes the upgrade of Matrix infrastructure orchestration
Operations Orchestration 9.x subset (embedded OO) hosted on the Central
Management Server (CMS) to full Operations Orchestration 10.x (full OO)
hosted on a separate server.
Matrix Operating Environment (Matrix OE) infrastructure orchestration is a software package providing core automation of
data center infrastructure lifecycle operations to enable the creation of a self–service datacenter. HP Operations
Orchestration is an IT workflow product, originally created to enable IT operations staff to turn manual IT run books into
automated IT process flows. This accelerates triage, troubleshooting and repair of IT incidents and alerts. Infrastructure
orchestration includes a subset of the OO product.
Overview
On the CMS, infrastructure orchestration integrates with embedded OO. Infrastructure orchestration includes the following
OO 9.x components:
1. OO workflow engine.
2. OO workflow designer.
3. OO remote execution.
4. A subset of OO-supplied flows.
5. Infrastructure orchestration-supplied and invoked OO flows.
OO 10.x includes the following OO components:
1. OO workflow engine.
2. OO workflow designer.
3. OO remote execution.
4. All OO-supplied flows.
The OO installation differences are above in bold typeface.
OO 10.x does not allow updating system properties in OO Central. Since infrastructure orchestration and Extensible Server
Adapter (ESA) flows depend on customized system properties, it is necessary to load the infrastructure orchestration and
ESA project into OO Studio, fulfill the system properties, create the customized content pack, and deploy it to OO Central.
Upgrading from infrastructure orchestration embedded OO 9.x subset to OO 10.x on a separate server requires the
following steps:
1. Install and use OO 10.x on a separate server.
2. Import infrastructure orchestration and ESA project into OO Studio.
3. Customize infrastructure orchestration and ESA system properties.
4. Create infrastructure orchestration and ESA customized content pack.
5. Copy XSL, XML, and HTML files to the OO server.
6. Deploy the customized content pack to OO Central.
7. Redirect infrastructure orchestration and Matrix OE on the CMS to the OO server.
8. Confirm infrastructure orchestration is using the correct OO password.
The following step-by-step instructions were validated with both the CMS and OO server running Windows Server 2008 R2
Enterprise edition.
These instructions are valid for infrastructure orchestration 7.3 and above to upgrade to OO 10.x.