Migration Prerequisites

Before migrating data from CA Cohesion ACM, ensure the following prerequisites have been satisfied:

Install and license the CA Configuration Automation r12.6 server
Ensure you have database access to both the Cohesion Database and the CA Configuration Automation Database
If your CA Cohesion ACM implementation used a Sybase database, you must do the following:
- Copy the Sybase driver: sybase-jdbc4.2.jar (where 4.2 is the driver version, but may vary) from:
  <Cohesion_home>\Server\server\webapps\cohesion\WEB-INF\lib\ to:
  <CCA_r12.6_home>\tomcat\webapps\cca\WEB-INF\lib\
- Restart the r12.6 CA Configuration Automation Server
For importing security certificates, consider the following:
- Ensure the certificate authority was created in CA Configuration Automation r12.6
- You must know the server certificate password
- You need the CA Cohesion ACM keystore and truststore files

Consider the following limitations before migrating data:

Similar data that already exists in the CA Configuration Automation Database is not overwritten
Change Detection and compare options in CA Cohesion ACM Management Profiles with specific Snapshot information are not migrated
Only recurring scheduling options are migrated with Management Profiles
The start time for scheduled operations in Management Profiles is set to the starting time of the scheduling window
Proxy options in CA Cohesion ACM Access Profiles are not migrated
When migrating Snapshots, if a parameter directive and a configuration file do not exist in the Blueprint, the respective values are ignored and migration of the Snapshot continues with the remaining values