In a PlateSpin Migration Factory environment, PlateSpin Transformation Manager and PlateSpin Migrate Connector work together to execute planned migrations or to track manual migrations on your PlateSpin Migrate servers
Ensure that your environment meets the deployment requirements for PlateSpin Migration Factory.
Ensure that network communications are properly configured and operational.
Configure the global migration settings that apply to all Migrate Connector instances.
PlateSpin Migrate servers are represented in a project by Migration Server resources. Communications with the Migrate Server require that the resource have the Migrate Server URL and valid login credentials for Migrate.
Planning actions in PTM do not require access to the related PlateSpin Migrate server. Users can set up Migration Server resources with minimal information for planning purposes.
Automation and tracking actions require access to the Migrate server.
A Project Manager or Project Architect typically performs the following tasks for the project.
Configure a Migration Server resource for each Migrate server that is available to the project.
For each workload, use auto-assignment of Migration Server resources, or associate a specific Migration Server resource with the workload.
Ensure that associated Credential resources are valid before you submit the workload for automated execution:
Source workload
Target Platform resource
Target Migration Server resource
Ensure that the workload Transformation Plan is in Automated Mode.
The Mode setting in the workload Transformation Plan must be set to Automated.
Configure required information for the proposed workload.
Automated workload discovery is required prior to submitting the workload for execution. Information added from the Import Spreadsheet is not sufficient for automation.
Ensure that the workload is up and running.
Ensure that the target platform is up and running.
Ensure that the assigned PlateSpin Migrate Server is up and running.
All Migrate Connectors use the global Migrate Connector settings that the Administrator user configures for the PTM application.
Deploy a Migrate Connector instance in the same network as the source workloads.
You need the Project ID to configure a dedicated Migrate Connector for a project.
The Migrate Connector must be up and running.
PlateSpin Transformation Manager supports automated migration to target platforms meets the PlateSpin Migrate requirements. See the following resources in the PlateSpin Migrate 2018.11 User Guide:
Migration to Microsoft Azure
Migration to VMware vCenter Clusters
Before you submit a workload for automated migration:
Ensure that the Credentials resource associated with the target platform contains valid credentials for the target. Credentials are needed for the setup of the target VM on the platform.
Ensure that the target platform is up and running.
Ensure that the network connections are working between the assigned PlateSpin Migrate Server and the target platform.
Before you begin to submit a workload for automated migration:
Deploy PlateSpin Migrate servers in your environment. See the PlateSpin Migrate 2018.11 Installation and Upgrade Guide.
PlateSpin Migrate servers must be accessible for network communications.
Ensure that the Event Messaging port is open on the Migrate Server.
In PTM, configure a Migration Server resource for each Migrate server that you plan to use for your project.
You can create Migration Server resources without the detailed information for initial planning. Select Automated Migration in the workload’s Transformation Plan to allow the PlateSpin Migrate Connector to manage PlateSpin Migrate server assignments from among the Migration Server resources that you create for the project.
Before you submit the workload for automated execution, ensure that associated Credential resource is valid for each Migrate server.
Ensure that the assigned Migrate server is up and running.
PlateSpin Transformation Manager can track the status of migration jobs on your PlateSpin Migrate server
Deploy PlateSpin Migrate servers in your environment. See the PlateSpin Migrate 2018.11 Installation and Upgrade Guide.
PlateSpin Migrate servers must be accessible for network communications.
Ensure that the Event Messaging port is open on the Migrate Server.
In PTM, configure a Migration Server resource for each Migrate server that you plan to use for your project.
You can create Migration Server resources without the detailed information for initial planning. Select Automated Migration in the workload’s Transformation Plan to allow the PlateSpin Migrate Connector to manage PlateSpin Migrate server assignments from among the Migration Server resources that you create for the project.
Before you submit the workload for automated execution, ensure that associated Credential resource is valid for each Migrate server.
Ensure that the assigned Migrate server is up and running.