Operating Environment Software Instruction Manual

Orchestration\Studio\conf\rc_keystore), overwriting the existing instance of that
file.
3. Restart Operations Orchestration Studio.
4. In that same directory, open studio.properties and change the value in
dharma.studio.ui.input.constant.max.chars to 65536.
5. When launching Operations Orchestration Studio, enter “admin” as the user name and enter
your CMS password.
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 Databases (HP Passport required).
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)
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 both Insight Control server deployment
and HP Server Automation (SA) when configuring infrastructure orchestration with server deployment
options. However, infrastructure orchestration can be configured to use both deployment servers,
but this configuration must be done after installation is complete.
If you want to add a deployment server after infrastructure orchestration is installed, enter the
following commands on the CMS.
Configuring deployment servers 29