PlateSpin Transformation Manager 2 Release Notes

1.0 Version

PlateSpin Transformation Manager 2 includes PlateSpin Migrate Connector 2. Files for PlateSpin Transformation Manager 2 or PlateSpin Migrate Connector 2 are numbered 2.0.0 or 2.0.0-x.x, where x.x is the build number.

2.0 What’s New

PlateSpin Transformation Manager 2 introduces several new features and enhancements.

2.1 Migration to Azure Cloud

PlateSpin Transformation Manager 2 adds support for the automated migration of workloads to the following Microsoft Azure environments:

  • Azure Global (default)

  • Azure China

  • Azure Germany

  • Azure US Government

PTM discovers details about the Azure account and its available locations and other resources.

2.2 Migration to VMware vCenter Server

PlateSpin Transformation Manager 2 adds support for the automated migration of workloads to VMware vCenter Server environments. PTM discovers details about all VMware Clusters managed by the vCenter Server, their member hosts, and their related resources.

2.3 Migration to VMware Cloud on AWS Platforms

PlateSpin Transformation Manager 2 adds support for the automated migration of workloads to VMware vCenter Server environments in VMware Cloud (VMC) on Amazon Web Services (AWS). PTM discovers details about all VMware Clusters managed by the vCenter Server, their member hosts, and their related resources.

2.4 Discovery of Target Platforms and Resources

PlateSpin Transformation Manager 2 automatically discovers details about target platforms and their associated resources. PTM updates the information every 6 hours and on demand. Discovered resources include the following:

  • Azure Cloud platform resources

    • Locations

    • Networks

      • Virtual Networks

      • Subnets

    • Datastores

    • Resource Groups

  • VMware vCenter Server platform resources

    • Clusters

    • Hosts (member nodes of VMware Clusters)

    • Networks

    • Datastores

    • Resource Pools

The Platform dialog and each of its Resources’ dialog lists associated workloads as you configure them for migration to the target platform. You can quickly see which workloads are using any resource.

For more information, see Target Platforms the User Guide.

2.5 Tracking of External Migrations

PlateSpin Transformation Manager 2 tracks migrations that you perform externally on your PlateSpin Migrate servers. You can track migration to any target platform, even those not supported for automated migration in PTM.

PTM looks for workloads on the project’s Migrate servers that match imported workloads, and sets matches to Manual (Tracking) mode. PTM displays details about workloads and target platforms as well as migration events from the Migrate server. The Dashboard metrics include statistics for tracked migrations.

2.6 Migrate Agent Support

PTM can automate the use of the Migrate Agent utility to register source workloads with Migrate servers located in remote target platform environments. No VPN is required between the source location and the target location.

2.7 Bulk Edit

Bulk Edit has been redesigned to make it easier and more intuitive to apply bulk edits to multiple workloads at a time. It groups parameters to match options in the Workload dialog:

  • Transformation Plan

  • Location

  • Migration Settings

  • Workload

  • Network Interfaces

  • Storage

  • Test Settings

  • Custom Fields (when Global Project Selector is set)

  • Applications

  • Transformation History

Bulk Edit also performs a pre-check of the intended changes. The Bulk Edit Results dialog reports workloads where changes will be fully modified, partially modified, or with no changes. The report provides warnings that help you understand implications of the requested changes, particularly for changes that might be difficult to undo after they are applied.

See Bulk Edit for Multiple Target Workloads the User Guide.

2.8 Import Progress

Import Progress provides a role-based view of the discovery status for workload imports initiated by any Migrate user during the past 24 hours. The report displays Import Results for workloads by status: All, Success, In Progress, Failed, and Not Found.

You can optionally apply the list of workloads on any tab as an Advanced Search for the Workloads list. For example, the Success report provides a useful first step in identifying candidate workloads for bulk edit configuration. You can select the appropriate workloads from the resultant list or use Advanced Search to further refine the list. The Failed report provides an easy way to identify workloads that failed because of bad credentials.

See Viewing Import Progress the User Guide.

2.9 PlateSpin Migration Factory

You can use PlateSpin Transformation Manager 2 and PlateSpin Migrate Connector 2 in a PlateSpin Migration Factory deployment with PlateSpin Migrate 2018.11.

  • Run a centralized PTM across multiple environments: You can deploy Migrate Connector instances in remote premises or the Azure Cloud where you have deployed PlateSpin Migrate servers. Use PTM to execute automated migrations and track external migrations for the Migrate servers in those locations.

  • Run multiple Connectors for a single project: Deploy Connector instances where you need them in different source networks. Add multiple Connector instances in the same large networks for improved performance.

2.10 Web Interface Enhancements

PlateSpin Transformation Manager 2 provides numerous enhancements to the Web Interface.


  • Date Range selector: In the What’s Happening panel, you can select from the following predefined periods, or set custom start and end dates:

    • Today

    • Yesterday

    • Tomorrow

    • This week (default)

    • Last week

    • Next week

    • This month

    • Last month

    • Next month


  • Default project: PTM automatically creates one default project. You can customize this project or create you own projects. The default Project objects are:

    • My Organization

    • My Project

    • My Wave

    • My Batch

    If there is only a single batch and wave when you import workloads, the workloads are automatically assigned to My Wave and My Batch.

  • Workload dialog

    • Credential for retrying workload discovery: A Credential option appears in the Transformation Plan panel if discovery has failed for the workload. You can specify a different Credential resource or create a new Workload Admin (Windows and Linux) or Domain Admin (Windows) Credential resource to use.

      NOTE:You can modify a Credential resource for the undiscovered workload without consuming a license.

    • Platform-based options and resources: After you select a target platform for the workload migration, the Workload dialog is refreshed to present only appropriate options and resources for workload configuration.

    • Install Migrate Agent option: You can configure the auto-install of the Migrate Agent utility on a source workload. PTM configures it to begin communications with a designated PlateSpin Migrate server.

    • Disable services or daemons before cutover: You can select from a list of Windows services or Linux daemons running on a source workload that you want PTM to stop prior to performing cutover.

    • Default configuration settings:


      Default Setting

      Pause for manual cutover


      Replication with test cutover


      Perform daily incremental replication

      Enabled, default time is 9:00 PM (based on PTM Server time)

      Compression type

      • Azure: Optimal

      • VMware: None

      Disk copy method

      Block with driver (for Windows and Linux)

    • Print option: Use the Print icon in the Workload dialog toolbar to print a well-formatted run book for the workload.

    • Terminology:

      PTM 1.1.1 and Earlier

      PTM 2

      Original workload

      Source workload

      Proposed workload

      Target workload

      Target container

      Target Platform

  • Advanced Search: Advanced Search has been expanded to include Platforms and to provide relevant options based on a selected platform. For example, Azure Cloud platforms have Cloud Location, Resource Group, Storage Account, and Subnet options, while vCenter Server platforms have Cluster, Cluster Host, and Datastore options.


PlateSpin Transformation Manager now manages target migration environments as platforms.

  • Add, view, and remove platforms and resources: See Discovery of Target Platforms and Resources.

  • Exclude or include resources in menus: PTM includes discovered resources in menus for workload transformation planning. You can optionally exclude specific resources to hide them in menus. Settings apply project-wide.


  • Migration Server resources:

    • Connector: Ability to specify which PlateSpin Migrate Connector to use for executing migrations and tracking external migrations performed on the resource’s assigned PlateSpin Migrate server.

    • Status: Ability to view the status of Migrate servers, including the time stamp of the last successful contact between PTM and the Migrate server.

    • Retry: Ability to retry a connection if the Migrate server has been down.

  • Credential resources:

    • Azure credential type: Added the Microsoft Azure credential type in the Credentials dialog. You create Azure Credentials for your Azure accounts that you will use as target Azure Cloud platforms.

    • Credential creation: Ability to create Credential resources from dialogs where they are needed, including Import, Migration Tool, Platform, and Workload. The newly created Credential is automatically selected in the open dialog.


  • Connectors list: Users with Administrator permissions can view a list of the Migrate Connectors associated with the PTM Server. Information includes the Connector’s name, IP address, project assignment, the name of the PTM user identity the connector uses to log in to the PTM Server, and status.

  • Edit Connector dialog:

    • View or delete Workload associations: Use the Edit Connector dialog to view a list of associated workloads. Delete a workload association to initiate the reachability assessment of the workload for other available Connectors.

    • View, add, modify, or remove Migrate server associations: Use the Edit Connector dialog to view a list of associated Migrate servers and information about them, including their project and connection status. You can add associations for Migrate servers that are reachable by the Connector based on its project assignment.

2.11 Security Enhancements

PlateSpin Migrate Connector 2 uses industry-standard strong encryption to secure passwords in the PTM database for the Credentials resources used to access source machines and target hosts.

PlateSpin Migration Connector uses industry-standard strong encryption to securely store the Connector User password in the Connector configuration file.

2.12 PlateSpin Migrate Connector Enhancements

PlateSpin Migrate Connector 2 provides several new features and enhancements:

  • Multiple Connectors: You can use multiple Connectors in a single project.

    • Use any number of source networks in a single project, each with its own Connector.

    • Use Connectors for target platform discovery.

    • Add multiple Connectors as needed in the same network for performance scaling.

  • Workload associations: A project’s Connectors negotiate the discovery for a workload based on reachability. The winning Connector assumes responsibility for subsequent actions performed for that workload.

  • Migration Server associations: You can specify which Connector to use for communications with your PlateSpin Migrate server. You can associate multiple Migration Server resources to a single Connector.

  • Connector heartbeat poller: Each Migrate Connector sends status information about all Connectors and Migrate servers to the PTM Server every 5 minutes.

For more information, see the PlateSpin Migrate Connector in the Administrator Guide.

2.13 PTM REST API Enhancements

The PlateSpin Transformation Manager REST API has been expanded to support create, read, update, and delete operations for a variety of PTM objects by using your custom client. The PTM REST API interactive console uses the open source Swagger UI tool to provide documentation about its APIs. You can learn about the APIs and interact with the REST service to try them.

You can use the open source Swagger Editor to generate a PTM client in your language of choice. For information about accessing and using the PTM REST API, see the PTM 2 REST API Reference.

The Python client used by PlateSpin Migrate Connector is available as an example on your Connector host server at <Connector-path>resources\ Other example files in Python and Java are included this resources folder.

2.14 PTM Appliance Enhancements

PlateSpin Transformation Manager 2 Appliance runs SUSE Linux Enterprise Server (SLES) 12 Service Pack 3.

3.0 Known Issues

Micro Focus strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched.

If you need assistance with any issue, please contact Micro Focus Technical Support.

3.1 If Host Name Is Invalid for Azure (Contains an Underscore), PTM Does Not Show an Error in Location for VM Name and in Storage for Path on Storage Account

Issue: When you select Azure as the target platform, PTM uses the source workload host name to suggest values for the target workload host name, the VM resource name, and the path on the storage account. If the source workload host name contains an underscore (_) character, the suggested names are invalid in Azure because Azure does not permit underscores for host names and resources with derivative names.

In the Workload dialog, PTM shows an error (red asterisk) in the Workload panel for the target workload Hostname. However, it does not show an error in the Location panel for the VM Name and in the Storage panel for the Path on Storage Account. (Bug 1118560)

Workaround: For migration to target Azure platforms, if the source workload host name contains an underscore, do either of the following:

  • Modify the source workload’s host name to comply with Azure naming conventions for host names, then re-import the workload.


  • Open the Workload dialog for the source workload, then modify the following fields to comply with Azure host name and VM resource naming conventions:

    • Workload panel > Hostname

      Example: Change prv-win2k16_dev to prv-win2k16-dev.

    • Location panel > VM Name

      Example: Change PRV-WIN2K16_DEV to PRV-WIN2K16-DEV.

      The VM resource name can differ from the host name; however, it must comply with Azure VM resource naming conventions.

    • Storage panel > Path on Storage Account

      Example: Change /PRV-WIN2K16_DEV/PRV-WIN2K16_DEV.vhd to /PRV-WIN2K16-DEV/PRV-WIN2K16-DEV.vhd, where the path format is /<vm-name>/<target-hostname>.vhd.

In Azure, valid host names and VM resource names can contain letters (ASCII characters a to z), numbers (0 to 9), and hyphens (-). The name should not begin or end with a hyphen. The host name length can be 1 to 15 characters for Windows or 1 to 64 characters for Linux. The VM resource name is case-insensitive and its length can be up to 64 characters. See Compute in Naming Conventions in the Microsoft Azure documentation.

3.2 Rediscovering a Not-Found Workload Stays in Workload not found (Rediscover requested) Sub Status

Issue: If you import a workload with an undiscoverable IP address, the workload is in a Ready to Import/Workload not found sub status. After you perform a rediscovery on the workload, the workload becomes stuck in Workload not found (Rediscovery requested) sub status. (Bug 1117554)

Workaround: Try these troubleshooting measures:

  • Verify that the IP address that you provided to import the workload is correct.

  • Ensure that the workload is reachable by at least one of the PlateSpin Migrate Connector instances that are associated with the project. That is, you must deploy a Connector in the same source network as the source workload.

  • Ensure that both the Connector and source workload are up and running and that the required network ports are open for communications between them.

After you verify the workload is reachable, delete the not-found workload, then repeat the import process using the correct IP address.

3.3 Changes Made to a Workload in PlateSpin Migrate Do Not Come to PTM Until a Poll Takes Place

Issue: In PTM, you submit workloads for migration to a PlateSpin Migrate server, and pause them for manual configuration. You modify the workload configuration by using the Migrate Web Interface. The changes appear inconsistently in the PTM Web Interface. Sometimes the configuration changes are synchronized immediately back to the PTM Server. Other times, the changes do not appear until after a poll occurs from the Connector to retrieve messages for all migration events for the past 5 minutes.

In this PlateSpin Migration Factory environment, two PlateSpin Migrate Connectors in different projects are associated to the same PlateSpin Migrate server. Both Connectors listen for migration events. For the Migrate server, after any one Connector gets the STOMP message, Migrate deletes the message from the queue. If the retrieving Connector does not know about the workloads, it discards the message. No other Connector will be able to get that message from the queue. A later poll of the Migrate Server retrieves all messages for the past 5 minutes. The migration event might be missed completely by the second Connector if the first Connector polls the Migrate server for messages before the second Connector’s next scheduled poll. (Bug 1118687)

Workaround: Using a single Migrate server across multiple projects can cause inconsistent results with synchronization of configuration changes from PlateSpin Migrate to the PTM Server. Ensure that a PlateSpin Migrate server has only one PlateSpin Migrate Connector listening for migration events. In your PlateSpin Migration Factory environment, each Migrate server should be dedicated to perform migrations for a single source network in a single project. Do not add the Migrate server to multiple projects on the same or different PTM Server.

4.0 Installing PlateSpin Transformation Manager

4.1 System Requirements

For information about requirements to deploy the Appliance on your VMware host, see PTM Appliance Requirements in the Appliance Guide.

4.2 Download

To download this product, see PlateSpin Transformation Manager on the Micro Focus Downloads website. A public Internet connection is required for download. Use your Micro Focus Customer Center account credentials when you are prompted to log in for the download.

PlateSpin Transformation Manager 2 and PlateSpin Migrate Connector 2 files include the following:

Download File Name


Where xxxx is the build number

An OVF file that you use to deploy the PlateSpin Transformation Manager Appliance in your virtualization environment.

Where xxx is the build number

Contains the files to install a new instance of PlateSpin Migrate Connector 2 on your intended Migrate Connector host.


Contains a PlateSpin Transformation Manager Public Key for new installs of remote instances of PlateSpin Migrate Connector on your intended Migrate Connector hosts.

NOTE:To install the Migrate Connector RPM without warnings, you must import the PTM Public Key file to your keyring on the intended Migrate Connector host before you install the Connector RPM.

4.3 Deploying the PlateSpin Transformation Manager Appliance

The PlateSpin Transformation Manager Appliance is a virtual machine that hosts PlateSpin Transformation Manager server software and the database for your transformation projects. You can use the downloaded OVF file to deploy a new Appliance VM.

See Installing PTM Appliance in the Appliance Guide.

4.4 Installing and Configuring PlateSpin Migrate Connector

An instance of PlateSpin Migrate Connector is installed automatically on the PlateSpin Transformation Appliance when you deploy the Appliance VM. This Connector instance is preconfigured to work with all projects on the PlateSpin Transformation Manager server. See Configuring PlateSpin Migrate Connector in the Appliance Guide.

You can install additional instances of Migrate Connector on your Linux servers. For information about installing and configuring Connectors, see PlateSpin Migrate Connector in the Administrator Guide.

5.0 Licensing Information

An Evaluation License for 100 workloads is automatically available when you deploy the PlateSpin Transformation Manager Appliance. The evaluation period of 90 days begins when you first edit a workload to plan its transformation. You can configure users, projects, platforms, resources, and configuration settings without consuming a workload license. See Evaluation License in the Administrator Guide.

Visit the Customer Center to purchase a Full License. See Full License and Adding a License Key in the Administrator Guide.

6.0 Additional Documentation

For the most recent version of this document and other PlateSpin Transformation Manager documentation resources, visit the PlateSpin Transformation Manager 2 Documentation website.

7.0 Previous Releases

For documentation that accompanied earlier releases, visit the PlateSpin Documentation website and scroll to the release that you are looking for.

8.0 Contacting Micro Focus

We want to hear your comments and suggestions about this book and the other documentation included with this product. You can use the comment on this topic link at the bottom of any HTML page of the English documentation.

For specific product issues, contact Micro Focus Support at

Additional technical information or advice is available from several sources: