You can migrate CA Service Catalog from one system to another system, to replicate your environment. Typically, you perform such a migration to move from a test system to a production system or as part of disaster recovery procedures. You can also perform such a migration as part of upgrading using a migration model.
For clarity, this documentation uses these terms:
Thus, this documentation uses these terms to describe a typical scenario, migrating from a test system to a production system. If you are migrating for other reasons, the test system is the source system and the production system is the target or destination system.
This documentation assumes a multicomputer setup. For example, the "medium architecture" system referenced in System Architecture consists of three computers: one computer for the DBMS (including the MDB), one computer for CA Service Catalog and CA Service Accounting and one computer for CA Workflow. Unless indicated otherwise, system refers to all CA Service Catalog computers in your test or production system, including the DBMS computer. If you are migrating one stand-alone CA Service Catalog system to another stand-alone system, ignore references to multiple computers.
Note: For information about migrating a product that integrates with CA Service Catalog, see its documentation. For example, for information about migrating CA Process Automation, see the CA Process Automation documentation. Similarly, for information about migrating CA Service Desk Manager, see the CA Service Desk Manager documentation.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |