Migrating › How to Migrate

How to Migrate

You migrate CA Service Catalog products and components from one system to another for several reasons. Examples include upgrades, test-to-production moves, best practices, governance, security, or resource-related reasons. To migrate from one system to another, for example, from test to production, perform these tasks:

1. Restore the MDB database backup of the test system into your production system. You backed up this system while performing the prerequisite tasks.

   During this process, select the option for overwriting the existing MDB database.

   For instructions to restore the database, see your DBMS documentation.

2. Unregister the CA EEM application used by the production system, as follows:
   1. Log in to the Global Application of CA EEM as the EiamAdmin user
   2. Select Configure, Applications, Service Catalog application.

      If your systems use a different name than Service Catalog for the CA Service Catalog application name, use that name instead.

   3. Click the UnRegister button.
3. Back up the CA EEM data on the Service View computer in your test system, as follows.

   If you have multiple Service View computers, perform this step on the first (formerly primary) Service View computer. You run this command once, regardless of how many Service View computers your system has.

   1. Open the CA Service Catalog command prompt by clicking Start, Programs, CA, Service Catalog, Service Catalog Command Prompt.
   2. Run the following command at the command prompt:

      ant backup-eem-app 
      

      This action generates a file named eem-backup.xml in the %USM_HOME% directory.

4. Copy the following files from the Service View computer in the test system to the Service View computer in the production system.

   If you have multiple Service View computers, perform this step on the first (formerly primary) Service View computer in each system. You copy these files once, regardless of how many Service View computers your system has.

   • %USM_HOME%\seeddata.properties
   • %USM_HOME%\filestore folder

     This folder may exist on a different computer than the current computer. To verify its location, select Administration, Configuration, Filestore Information. If no filestore location is specified, you do not need to copy this folder now. However, as a best practice, soon after the migration, set up a single location for shared files.

   • %USM_HOME%\eem-backup.xml
5. Open the %USM_HOME%\seeddata.properties file for editing and do the following:
   1. Update the value of the _USMHOME_ parameter with the complete folder name on the production computer of CA Service Catalog. For example:

      _USMHOME_=C:/Program Files/CA/Service Catalog

   2. Update the value of the _IMQVARHOME_ parameter with the complete folder name on the production computer of the Message Queue 4.1 Broker. For example:

      _IMQVARHOME_=C:/Program Files/CA/Service Catalog/view/conf/var

   3. Save your changes to the seeddata.properties file.

   Note: When entering the folder names for these parameters, use the forward slash (/) not the backslash (\) as the separator character.

6. Run the following commands–in the order shown–on all CA Service Catalog computers in the production system.

   Important! Run all the following commands on each computer, one computer at a time, until you have run them on all CA Service Catalog computers. For example: first, run all commands on computer1; next, run all commands on computer2; third, run all commands on computer3; and so on.

   1. ant update-db-user

      This command enables you to update the password of the database user. The command updates these password references globally to help ensure that CA Service Catalog continues to run efficiently throughout your environment.

      Verify that the password you specify adheres to your organizational standards.

   2. ant update-db-host

      This command enables you to update any or all of the following database settings: host name, port number, instance name, or service name. CA Service Catalog components use these settings to communicate with each other and the database.

      Important! The database host name that you specify must be different than the one used in the test system. Updating the other settings is optional.

      For details about this command, see How to Update the Database Host, Port, Instance, or Service Names.

   3. ant restore-eem-app

      This command restores the CA EEM database from the test system to the production system, using the eem-backup.xml that you copied earlier.

   4. ant update-usm-host

      This command enables you to change the host name and port number for a computer running Service View, CA Workflow, or both.

      Important! All host names for Service View and CA Workflow on the production system must be different from the ones in the test system. Updating the other settings is optional.

      For details about this command, see How to Update the Host Name and Port Number for Service View and CA Workflow.

7. Start all CA Service Catalog services on all computers in the production system. Using the Windows Control Panel, start these services: CA Service View, CA Service Accounting, CA Service Fulfillment, and Message Queue 4.1 Broker.
8. Log in to CA Service Catalog in the production system and do the following:
   1. Select Administration, Configuration, and update the configuration sections for the following:

      Important! If your post-migration environment does not include any option in the list, update the configuration settings accordingly to remove the integration! Similarly, if your post-migration environment does include any of these options, do the following: Verify that the host names, port numbers, and other configuration data are correct for your post-migration environment. Remember that setting up a filestore location is a best practice, as mentioned earlier.

      • Filestore
      • CA Service Desk Manager integration
      • CA CMDB integration
      • CA Workflow
   2. Select Administration, Configuration, Workflow, and click Configure.

      The actors are reconfigured to use the new environment.

9. Test by verifying that the same users, services, requests, and so forth that existed in the test system also exist in the production system.

You have migrated CA Service Catalog.