Upgrading and Migration Considerations › Phase 1: Upgrade the DSM Enterprise Manager

Phase 1: Upgrade the DSM Enterprise Manager

In phase 1 of the upgrade process you upgrade the DSM enterprise manager. Enterprise managers are usually installed only in very large or very distributed companies. If you have not previously installed a DSM enterprise manager, jump to upgrade phase 2.

To upgrade the enterprise manager, perform the following steps:

1. Close down all services and applications that may have a connection to the DSM enterprise MDB.

   In a pure Client Automation implementation this would include the DSM enterprise manager itself, remote engines for both enterprises and domains, and running instances of the DSM Reporter. If other CA applications or third-party products are installed on your network that share the MDB and hence may have an outstanding connection to it, these will need to be shut down as well.

2. Upgrade the MDB using the DVD (if appropriate).

   If the MDB is installed on a computer remote from the DSM enterprise manager, upgrade the MDB using the Client Automation DVD. Select either “Install MDB” or “Install CCS including MDB”.

   With Client Automation 12.9, you can also upgrade the MDB and the Manager in a single step using the installer. The installer identifies the MDB machine and upgrades the MDB first and then upgrades the Manager. This feature is not supported if MDB is installed using Install CCS including MDB option.

3. Upgrade the DSM enterprise manager itself using the DVD.
4. Upgrade all remote DSM enterprise engines using the DVD (if appropriate).

   If you have previously installed any enterprise level engines on remote computers, upgrade them now using the Client Automation DVD.

5. Upgrade any remote DSM Explorers or DSM Reporters using the DVD or software delivery package (if appropriate).

   Any standalone instances of DSM Explorer, DSM Reporter, Web Services, or Web Console that are used to connect to the DSM enterprise manager and that have not been upgraded as a result of the preceding steps should be upgraded now. Instances that are installed on computers that also include a DSM scalability server or DSM agent should be upgraded after Phase 3 and Phase 4 respectively.

Note: Client Automation Release 12.9 is compatible only with CA Asset Intelligence Release 12.9 or CA Patch Manager Release 12.9. When you upgrade to Client Automation Release 12.9, you must also upgrade CA Asset Intelligence or CA Patch Manager to Release 12.9.

Note: When you upgrade from Client Automation r12.5 SP1 or r12.5 SP1 C1, CCS is not upgraded. The current release contains additional CCS patches that are  required to support Windows Server 2012 and SQL Server 2012. If you plan to upgrade the Manager machines to Windows Server 2012 or SQL Server 2012, contact CA technical support for the list of patches to be applied.

While you upgrade from R12.5 SP1 and R12.5 SP1C1 to Client Automation Release 12.9, do not run caf kill all before upgrade. Run caf stop, when required.