2.1 Downloading the PTM Software

Installation files for PlateSpin Transformation Manager Appliance and PlateSpin Migrate Connector are available on the Micro Focus Downloads website. Select PlateSpin Transformation Manager, then follow the Download link for PlateSpin Transformation Manager 2019.2 in the results. Use your Micro Focus Customer Center account credentials to log in to this site.

Table 2-1 describes the installation files needed for PlateSpin Transformation Manager and PlateSpin Migrate Connector.

Table 2-1 PTM Download Files

Download File Name	Description
PlateSpinTransformationManager-2019_2.xx.ovf.zip Where xx is the build number.	PlateSpin Transformation Manager 2019.2 Appliance Contains the OVF file that you use to deploy the PlateSpin Transformation Manager Appliance in your virtualization environment. You can also use the OVF file to deploy a replacement PTM Appliance for upgrades from version 2 to version 2019.2, re-using the existing Disk 2 (/vastorage) that contains all essential configuration files and the PTM database.
platespin-migrate-connector-2019.2-xx.x.x86_64.rpm Where xx.x is the build number.	PlateSpin Migrate Connector 2019.2 Contains files to install PlateSpin Migrate Connector on Linux servers that you deploy in your migration environment. You can also use the RPM file to upgrade PlateSpin Migrate Connector from version 2 to version 2019.2. NOTE:The Connector host server must meet software prerequisites. See Supported Connector Host OS and Dependent Software in the PTM 2019.2 Administrator Guide. An instance of the Migrate Connector is automatically installed on the Appliance when you deploy the Appliance VM.
ptm_public-key.key	Contains the public key used for signing the PlateSpin Migrate Connector for new installations. 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. The key is not required for Migrate Connector upgrades from version 2 to version 2019.2 if you previously imported the key on the Connector host before you installed PlateSpin Migrate Connector 2.

Download File Name

Description

PlateSpinTransformationManager-2019_2.xx.ovf.zip

Where xx is the build number.

PlateSpin Transformation Manager 2019.2 Appliance

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

You can also use the OVF file to deploy a replacement PTM Appliance for upgrades from version 2 to version 2019.2, re-using the existing Disk 2 (/vastorage) that contains all essential configuration files and the PTM database.

platespin-migrate-connector-2019.2-xx.x.x86_64.rpm

Where xx.x is the build number.

PlateSpin Migrate Connector 2019.2

Contains files to install PlateSpin Migrate Connector on Linux servers that you deploy in your migration environment. You can also use the RPM file to upgrade PlateSpin Migrate Connector from version 2 to version 2019.2.

NOTE:The Connector host server must meet software prerequisites. See Supported Connector Host OS and Dependent Software in the PTM 2019.2 Administrator Guide.

An instance of the Migrate Connector is automatically installed on the Appliance when you deploy the Appliance VM.

ptm_public-key.key

Contains the public key used for signing the PlateSpin Migrate Connector for new installations.

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.

The key is not required for Migrate Connector upgrades from version 2 to version 2019.2 if you previously imported the key on the Connector host before you installed PlateSpin Migrate Connector 2.

To extract the OVF file:

Extract the <ptm-ovf-file-name>.zip file on your management workstation so that the PlateSpinTM-version file folder appears.

Extract the file by using a third-party extractor; do not use the default Windows extractor.
Continue with Section 2.2, Deploying the Appliance on Your Virtualization Host.