This article contains the following topics:
Planning well ensures upgrade readiness before starting the actual upgrade process. Before proceeding with the actual upgrade process, review, consider, and plan for the following tasks:
|Download CA Service Management 17.1 Installer from CA Support.||For more information, see CA Support.|
|Review the Release Notes||For more information, see CA Service Management 17.1 Release Notes.|
|Operating Systems and Database Compatability||For more information, see Supportability Matrix.|
|Ensure that your environment meets all minimum version requirements||For more information, see Supported Upgrade Paths.|
|Backing up the Operating Systems and database||For more information, see CA SDM Database Backup and CA SDM Database Restore.|
|Backing up all customizations.||
|New Features/Enhancements from Latest Release||
|Which Applications must be upgraded first?||
Plan to take a full backup of your database and ensure it is validated. Plan to take multiple snapshots or a backup of the entire installation folder during the course of the upgrade procedure. This saves time, in case, you need to revert to a certain point while upgrading. Temporarily allocate additional disk space for backups.
For more information, see Upgrade Tools.
Plan for at least two environments: Development and Production environments. If a test or development environment is not available, consider Swing Box as the development environment. For more information about Swing Box Migration Method, see Use the Swing Box Method for Upgrading.
In case of CA SDM Conventional Configuration, limit the number of components installed on a Primary Server for a better upgrade experience, scalability, and better application performance. For more information, see CA Service Management Deployment Architecture.