PlateSpin Migrate Connector performs discovery for source workloads and target platforms. Ensure that your environment meets the deployment requirements in this section to take advantage of discovery features.
PlateSpin Transformation Manager uses PlateSpin Migrate Connector to discover details about source Windows and Linux Workloads. You must deploy an instance of Migrate Connector in the same network as the source workloads. If workloads reside in multiple networks, you must deploy at least one Connector instance in each source network.
PlateSpin Transformation Manager uses PlateSpin Migrate Connector to discover details about VMware vCenter Clusters. If the target platform is in a different network than the source workloads, you must deploy an instance of PlateSpin Migrate Connector in the same network as the platform.
PlateSpin Transformation Manager discovers target platforms in Microsoft Azure by using HTTPS connections. A Connector instance is not required for Azure discovery.
Contact your PTM Administrator to request Migrate Connector instances to be deployed in your migration environment. See Planning for PlateSpin Migrate Connector
in the PTM 2019.5 Administrator Guide.
PlateSpin Transformation Manager supports discovery of details for Windows workloads and Linux workloads running on x86 and x64 architectures. It first attempts automated discovery when you import a workload to a project. You can retry discovery or rediscover workloads as needed. For port information, see Section 1.6.2, Ports and Protocols: Workload Discovery.
The following information is required for discovery of source workloads:
FQDN or IP address, or range of IP addresses
Administrator-level or domain-level credentials for the source workloads
Domain-level credentials are required for the source workloads in a domain environment.
Open ports on the network as required for workload discovery
When you add a platform to the project, PTM attempts automated discovery of resources on the target platform, such as networks and storage. Resources are automatically created and associated with the parent platform. For port information, see Section 1.6.3, Ports and Protocols: Target Platform Resource Discovery.
The following information is required for discovery of platform resources:
VMware vCenter Cluster
FQDN or IP address of the VMware vCenter Cluster
Administrator-level credentials for the VMware vCenter Cluster
Open ports on the network as required for VMware platform discovery
Microsoft Azure
Azure Subscription ID
Credentials for the Azure subscription
Open ports on the network as required for Azure platform discovery
Amazon Web Services
Access Key ID
Secure Access Key
Open ports on the network as required for AWS platform discovery