When you upgrade Service Virtualization to a new version, you must also migrate your virtual services. Migration updates your projects and services, enabling them to work with the new version. You cannot use the projects until they are migrated.
There are two methods for migrating virtualization projects:
From the Designer. When you open a project in the Designer after installing a new Service Virtualization version, you are prompted to allow Service Virtualization to migrate the project.
This is useful, for example, if you are going to work on a specific project in the new version of the Designer, and the project is not yet migrated. For details, see the Service Virtualization User Guide or the Service Virtualization Help Center (http://admhelp.microfocus.com/sv/en/latest).
Using the Resource Manager migration tool. After installing a new version of Service Virtualization, you can use the Resource Manager command line migration tool to migrate projects.
You can migrate projects and services stored in the file system or in HPE Application Lifecycle Management (ALM). This is especially useful, for example, if you have a number of projects stored in the file system or ALM, and want to migrate them without opening each one in the Designer.
Note: Installation of the ALM client is not a prerequisite for working with the Resource Manager. The ALM client is downloaded automatically if it is required.
The Resource Manager migration tool enables you to migrate the following:
- A virtualization project (.vproj files). The .vproj file includes information on all project entities (virtual services, service descriptions, simulation models, etc.) included in the project.
- A project archive (.vproja files). A .vproja archive file is created when you export a project from within the Service Virtualization Designer.
You can also specify a folder to migrate. If you specify a folder, all relevant project entities inside the folder are migrated. For example, you may have a folder that contains multiple archived projects.
For details on using the Resource Manager migration tool, see How to Migrate Virtualization Projects.