Installing and Upgrading › How to Upgrade Using a Traditional Model
How to Upgrade Using a Traditional Model
Important! If you are running CA Service Catalog r12 or CA Service Catalog r11.2 Service Pack 2 or Service Pack 3 (r11.2), and you want to upgrade to CA Service Catalog 12.6 using a traditional model, you must first upgrade to CA Service Catalog r12.5 as a prerequisite. If applicable, contact Technical Support to obtain the CA Service Catalog r12.5 installation media, including its documentation. After you upgrade to CA Service Catalog r12.5, follow the instructions in this topic.
If you are running CA Service Catalog r12.5, you can upgrade to CA Service Catalog 12.6 using either a migration model or a traditional model. In a traditional model, you run the upgrade program only on existing CA Service Catalog computers. In contrast, in a migration model, you install CA Service Catalog 12.6 products and components on new computers.
To upgrade CA Service Catalog using a traditional model, do the following:
- Review the scope and limitations of an upgrade for requirements regarding upgrades from specific earlier releases of CA Service Catalog.
Important! Read and understand the scope and limitations of the upgrade before performing the upgrade!
- Upgrade the database management system you are using for CA Service Catalog, if necessary.
- Find and list all computers in their environment that have one or more CA Service Catalog components installed. Use this list to help verify that you upgrade all required computers efficiently and in the correct sequence. If necessary, work with other CA Service Catalog administrators and users to verify that your list is accurate and complete.
- In your current implementation, do the following:
- Log in to each business unit under the root (highest level) business unit and click Service Builder, Configuration, Catalog Configuration.
- For each of these business units, record whether the Use Service Provider Catalog Only option is set to Yes or No.
- Using the recorded values for reference, decide which value to use as a system-wide setting to meet the requirements of your organization.
In releases earlier than CA Service Catalog 12.6, the Use Service Provider Catalog Only option in the Service Builder configuration was available for both the root (highest level) business unit and all sub business units. However, beginning with CA Service Catalog 12.6, the Use Service Provider Catalog Only option becomes a System Configuration option available for the root business unit only, not any sub business units. You set this system-wide value later at the end of the upgrade process.
- Shut down all CA Service Catalog services on all computers.
The services are named Message Queue 4.1 Broker, CA Service View, CA Service Accounting, and CA Service Fulfillment.
- Check whether you have shared any of the folders under CA Service Catalog and Shared Components. If the folders are shared, unshare them before the upgrade and restore the share after the upgrade is finished. For details about sharing and unsharing, see your Windows documentation.
- Turn off replication in your DBMS.
Important! When replication is turned on, the database tables are locked from any schema changes. As a result, the upgrade cannot run successfully.
For instructions to turn off replication, see your DBMS documentation.
- Upgrade CA EEM.
- When you attempt to upgrade the first (formerly primary) Service View computer, the installation checks to see if the MDB must be updated. If necessary, the MDB upgrade is then started automatically.
If the MDB installation or upgrade is started, you are prompted during it to supply the required parameter values, such as the server name, logon credentials, and port numbers, for your DBMS:
Record the data and have it ready when you upgrade the first Service View server. This data is the same data required for a new installation of the MDB. Even if you do not need to upgrade the MDB, verify the MDB version and the related parameter values to help ensure that the database configuration is correct.
If the MDB upgrade is not needed, it is not started, and you proceed directly to the next step.
- Upgrade Service View and other products and components, as directed by the installation program. The installation program guides you through this entire process on all computers.
- Compare each customized file that you backed up earlier with the new version supplied by the upgrade. Update the new file with your customizations from the backup file.
Important! You may be able to replace certain new files with your backup files; however, before doing so, contact Technical Support and verify each file that you want to replace. For details, contact Technical Support.
- Verify that you and other users can log in to these components.
As a best practice, upgrade all components before you log in to any component.
- If you have installed CA Workflow as part of the upgrade process, do the following:
- Click Administration, Configuration, CA Workflow and verify the CA Workflow configuration parameters.
- Configure the CA Workflow actors and process definitions.
- If you integrated CA Service Catalog with CA Service Desk Manager in the previous release, reconfigure the connection and configuration details between the two products. For instructions, see the chapter "Integrating with CA Service Desk Manager" in the Integration Guide.
- The CA Service Repository Agent (also known as Data Mediation Data Repository Agent) automates the process of importing usage data stored in Delimiter Separated File or Fixed Length File format. During the upgrade, the repository agent folders and files from the previous release are backed up automatically. If you customized the repository agent in the previous release and you want to use the same customizations for the new release, do the following:
- Find the files from the previous release that were automatically backed up during the upgrade. These files are located in folders named for the previous release. For example, in the following folders, "r11_2" denotes the previous r11.2 release:
- %USM_HOME%\Repagent\r11_2 \data
- %USM_HOME%\Repagent\r11_2\config
- Open each backed up file, find the customizations that you want to continue using, and make the same or equivalent customizations to the new folders. The new folders are as follows:
- %USM_HOME%\Repagent\data
- %USM_HOME%\Repagent\config
Important! Do not simply overwrite the new files with the old files! Doing so does not work!
- Complete these updates for the first (formerly primary) Service View server.
- Complete these updates for any additional (formerly secondary) Service View servers.
- Log in to the root business unit of CA Service Catalog 12.6 as a Service Delivery administrator and do the following:
- Click Service Builder, Configuration, System Configuration.
- The System Configuration options appear.
- Set the value of the Use Service Provider Catalog Only option to Yes or No; you decided the value at the beginning of this upgrade process.
The value you set applies to the entire Catalog system, in other words, to all business units.
- Review any CA Service Catalog files that you customized, such as custom.xml or requestshared.xml. Verify that your customizations are intact and are applicable for this release.
The upgade program automatically backed up those files before the upgrade and restored them after the upgrade.
You are now ready to configure CA Service Catalog before using it. Also, optionally consider implementing clustering for Service View, CA Workflow, or both.
Note: If you are using CA Workflow, for best results, including more efficient process automation, after you upgrade your existing CA Workflow implementation, install and use CA IT PAM rather than CA Workflow. For details about installing and using CA IT PAM, see the CA IT PAM documentation and installation media, which are included with the CA Service Catalog installation media.
More information:
Choose New Installation, Upgrade, or Migration