Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.3 system

8
HP Insight Orchestration support matrix
From 6.3, federated CMS is enabled by default in every new installation. Even a single CMS is installed and configured, federation may
be enabled. Thus, when planning the migration of IO data, make sure to review table 7 carefully.
In order to check whether Federated CMS is enabled in your environment:
• In CMS, open hpio.properties file located at <Insight_Orchestration_install_directory>\conf
and search for federated.io property.
• If this property is set to true, environment is configured as Federated CMS.
• If this property is set to false, environment is configured for Non-Federated CMS.
Table 7 : Insight Software 6.3 DMT support matrix for Non-Federated CMS/Federated CMS
Source CMS System Target CMS System Supported Remarks
Non Federated CMS Non Federated CMS Yes
Non Federated CMS Federated CMS No
It is possible to manually disable federated CMS
on the target in order to proceed with migration
(Non-federated to non-
federated scenario). To do
so, open hpio.properties located at C:\
Program
Files\HP\Insight Orchestration\
conf and update the
property federated.io to false.
Federated CMS Federated CMS Yes
Requires source and target CMS to be configured
with the same FDQN.
Federated CMS Non Federated CMS No
If federation does not have secondary CMS’s
registered and only the primary CMS is part of the
federation, federation may be disabled but this
requires HP support to help turn an existing
federated CMS into a non-federated CMS.
Contact HP support for this EA- PI 45268
.This
will be the case when m
igrating to an HA
environment.
IMPORTANT:
If the source CMS is an upgrade to CMS 6.3 then the source CMS in “ Non
Federated (Source CMS) to Federated CMS (Target CMS) ” scenario during
migration. In such case manually disable Federated CMS on the target as
mentioned below. Open hpio.properties located
at C:\Program Files\HP\Insight Orchestration\conf and update the property
federated.io to false.
Scenarios not supported
• The source CMS and target CMS with different locales. For more details refer notes at “Migration support
matrix”
• The Source CMS credential and its database server credential are different from Target CMS credential and
its database server credential