The Migration Server resource enables you to track the following information for a migration server that resides in your transformation project:
A name for the migration server that is unique to your transformation project.The name must begin with a letter or number. It can contain only letters, numbers, and the following special characters: space, hyphen, underscore, apostrophe, percent, ampersand, comma, and period.
The name of the parent organization for the project.
The name of the parent project for the migration server.
(Optional) A brief description of the migration server. This text appears by default in the Migration Servers list.
Select one of the following:
PlateSpin Migrate: Select this option to identify the migration server as a PlateSpin Migrate Server, and to allow integration with your PlateSpin Migrate Server.
Others: Select this option to identify that the migration server runs any other type of migration software. PTM does not provide integration.
The URL of the login page for the migration tool hosted on the migration server. The URL must conform to all syntax rules and can be up to 1024 characters. For example:
https://psmigrate.example.com/Migrate
Expand the Credential list, then locate and select the Credentials resource to use to log in to the migration server’s web-based management tool. You can scroll the list or type a sequence of characters in the Filter to locate the Credentials resource of interest. You can alternatively create a new credential.
Migration Server resources can be saved in an incomplete state. The Migration Server field displays the value Not Configured in the Workload dialog. When you later deploy the server, you can update the Migration Server resource. The status is updated automatically for all of its associated workloads.
Expand the Connector list to select the PlateSpin Migrate Connector in the source network that this Migrate server will use to execute automated migrations or to track external migrations. The Connector list presents only Connectors that are available to all projects or are assigned to this specific project. A Connector association is required before the Migrate server can be used for migration. Each Migration Server resource is associated to only one Connector instance.
NOTE:A Migrate Connector can be associated with multiple Migration Server resources. The resources can be in the same or different projects, depending on the Connector configuration to serve all projects or a single project.
The Workload associations are populated as you begin to plan workload transformations. You can view or delete workload associations.