HP Matrix Operating Environment 7.3 and 7.3 Update 1 Infrastructure Orchestration User Guide

Migrating from one CMS to another using Operations Orchestration
If you are using Matrix with Operations Orchestration (OO) workflows, you may experience workflow
failures after migrating from one CMS to another CMS. These failures have two sets of possible
causes and actions:
Issue
Possible causes
and Actions
1. Duplication of values
The Run ID values from one CMS are not migrated via the DMT (Data Migration Tool) when
moving from one CMS to another. The new CMS will start the values over rather than resuming
from a previous value, resulting in duplicate values.
Suggested action
Run the SQL script provided in the Data Migration of an Existing Microsoft Windows CMS to a
New Insight Management 7.3 System white paper available at http://www.hp.com/go/
matrixoe/docs.
2. Lack of necessary information
The logic of the OO workflow is dependent on remote information or some state information
that is not available or appropriate on the new CMS. If you are using the Custom Hostnames
feature, for example, and have modified the sample OO workflows to support your specific
server naming strategy, the migration tool will not handle workflow-customized server-naming
strategies. If your workflow stored state information on the CMS, it was probably not migrated
to the new CMS.
Suggested action
Modify the OO workflows on the new CMS as appropriate. You must ensure that the workflows
and any external resources are manually updated to run properly on the new CMS (for example,
to provide necessary connectivity information to a remote server with a database of custom
hostnames, or to provide suitable state information based on previous work done on the prior
CMS). For more information, see the Data Migration of an Existing Microsoft Windows CMS to
a New Insight Management 7.3 System white paper available at http://www.hp.com/go/
matrixoe/docs.
The browser requires acceptance of a self-signed certificate to access Matrix
infrastructure orchestration
Matrix infrastructure orchestration is configured to use a self-signed certificate, which might cause
your browser to display one of the following messages:
Issue
• Google Chrome displays:
The site's security certificate is not trusted! or a blank page with
the icon.
• Internet Explorer 11 displays:
There is a problem with this website’s security certificate or Content
was blocked because it was not signed by a valid security certificate.
• Mozilla Firefox 17 displays:
This Connection is Untrusted.
To resolve this issue, perform the following:Possible causes
and Actions
1. Open a new tab or a new browser window.
2. Type the address of the IO self-service portal:
https://[you-CMS-name-or-IP]:51443
3. When your browser displays the message, perform one of the following depending on your
browser:
• Chrome: Click Proceed anyway.
• Internet Explorer 11: Click Continue to this website (not recommended).
• Firefox 17:
a. Click I understand the risks.
b. Click Add Exception.
Miscellaneous issues 231