Upgrading individual CA DataMinder machines is simple. In principle, we recommend that you upgrade all your CA DataMinder servers (gateways, Event Import machines, policy engines, and so on) at the same time as the CMS. Do this during a period of minimal user activity, beginning with the CMS and then working down the machine hierarchy to each server successively.
In practice, we recognize that this is not always possible. In very large organizations, the upgrade rollout can easily take several weeks. Likewise, unforeseen complications may force you to upgrade child machines before their parent server has been upgraded.
For these reasons, you will inevitably have different version machines operating alongside each other during the upgrade rollout. Any compatibility issues involved with running a new CMS with older versions of other components (for example, the Administration console or Data Management console), are covered in their own sections.
Before starting the rollout, you need to understand how CA DataMinder handles data transfers (policy changes and captured data) between machines running different versions of the product.
Note: CA DataMinder does not support different versions of the product running on the same machine.
This section contains the following topics:
|
Copyright © 2014 CA.
All rights reserved.
|
|