Important! The CA Compliance Manager repositories and data were not changed from CA Chorus r2.5. Do not delete, redefine, or reload any of your existing repositories unless you are changing your implementation of CA Compliance Manager. For more information about migrating CA Compliance Manager from CA Chorus r2.5 to r3 see Migrating CA Chorus for Security and Compliance Management from CA Chorus r2.5 to r3.
Existing CA Compliance Manager CA Datacom/AD repositories must be deleted so that they can be redefined. The CMGRIDCD job deletes existing repositories.
Follow these steps:
Modify the job to conform to your installation standards. Follow the instructions in the Notes and the Customization sections of the job to customize the job for your environment.
The job runs and completes.
The existing CA Compliance Manager repositories are successfully deleted.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|