HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

Copying keystore file after upgrading Operations Orchestration
After upgrading Operations Orchestration from version 7.51 to 9.0, Operations Orchestration
Central and Studio have different certificate keys. Operations Orchestration Studio cannot access
the URL https://<cms-name-or-ip>:16443.
1. Make a backup of the rc_keystore file on the CMS.
2. Copy the rc_keystore file installed on the CMS (..\Program Files\HP\Operations
Orchestration\Central\conf\rc_keystore) to the same path on the remote or
upgraded Operations Orchestration Studio system (..\Program Files\HP\Operations
Orchestration\Studio\conf\rc_keystore).
3. Restart Operations Orchestration Studio.
Pruning history data for Operations Orchestration Central systems
The Operations Orchestration Central database stores information about every flow execution
step. This data is used for OO reporting purposes. The database administrator can prune historical
data from the database to keep the database at a reasonable size. Regular database pruning will
minimize the disruption of disk space depletion or pruning large databases. Note that data about
the flows that is deleted from the database will no longer be visible in any reports.
SQL query based scripts allow the database administrator to specify how many days of run history
to be kept in the database.
For more information, see Purging OO Run Histories from MSSQL Databaseson the following
website (HP Passport required):
support.openview.hp.com/selfsolve/document/KM906017/binary/
OO9.00_PurgeRunHistories_MSSQL_DB.pdf?
searchIdentifier=56546fde%3a137b88edec5%3a-55e3&resultType=document
Configuring deployment servers
Matrix infrastructure orchestration supports the following server deployment platforms for
provisioning:
• Insight Control server deployment (physical provisioning)
• Ignite-UX (physical and virtual provisioning)
• HP Server Automation (SA) (physical and virtual provisioning)
• Insight Control server provisioning (physical provisioning)
NOTE:
• Only one of each type of deployment server is supported on a CMS.
• An HP Server Automation (SA) server and an Insight Control server provisioning server cannot
be registered at the same time.
NOTE: HP Insight Control server provisioning is a new feature that is replacing HP Insight Control
server deployment. Insight Control server deployment is still available for installation and upgrade.
For more information, see the HP Insight Control server provisioning Administrator Guide and the
HP Insight Control server provisioning Installation Guide at http://www.hp.com/go/insightcontrol/
docs.
Registering deployment servers
The host IP address and credentials for the deployment servers used by infrastructure orchestration
must be entered during infrastructure orchestration installation.
The Insight Management Installer does not allow selection of either Insight Control server deployment
or Insight Control server provisioning and HP Server Automation (SA) when configuring infrastructure
Configuring deployment servers 31