Upgrading HP Operations Orchestration included with Matrix OE to HP Operations Orchestration 9.00 (Full Version)

Introduction
This document describes the upgrade of Matrix infrastructure orchestration
Operations Orchestration 9.00 subset (embedded OO) hosted on the Central
Management Server (CMS) to full Operations Orchestration 9.00 (full OO)
hosted on a separate server.
Matrix OE infrastructure orchestration is a software package providing core automation of data center infrastructure
lifecycle operations to enable the creation of a selfservice 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.00 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.
Full OO 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.
Upgrading from infrastructure orchestration embedded OO 9.00 subset to full OO on a separate server requires the
following steps:
1. Install/Use full OO on a separate server.
2. Install infrastructure orchestration-OO JARs into full OO’s Remote Action Service
3. Migrate infrastructure orchestration repository to the full OO.
4. Copy infrastructure orchestration-OO XLS and HTML files to full OO.
5. Install (if needed) an SMTP service and configure infrastructure orchestration SMTP properties on the OO server
6. Copy customer-created OO Flows to full OO
7. Redirect OO server’s infrastructure orchestration Flows to infrastructure orchestration CMS.
8. Redirect infrastructure orchestration on the CMS to the OO server.
9. Confirm infrastructure orchestration is using the correct OO password.
The following literal 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 6.3 and above to upgrade to full OO 9.0. Note that ESA flows
will only work in this configuration from 6.2.1 version and above.
2