14.2 Workload Transformation Modes

PlateSpin Transformation Manager supports planning for the following workload migration methods:

Automated

Workloads are set to Automated mode by default. You can plan workload migrations and automate execution of supported migrations on PlateSpin Migrate servers in your PlateSpin Migration Factory environment. You can begin planning without setting up the entire migration environment.

PlateSpin Migrate servers must be deployed in the network before you execute the automated migration tasks.

Automated migration supports automated execution for supported source workloads and target platforms.

Manual (tracking)

Manual migration supports tracking of external migration efforts for supported source workloads that you perform on one or multiple PlateSpin Migrate servers associated with the project. If an imported workload matches a workload on one the project’s Migration Server resources, PTM tracks the workload details and migration workflow. The Workload dialog displays the source workload configuration plus the project, wave, batch, and schedule information. You can set custom fields and add notes to the Transformation History.

Manual

Manual migration supports scheduling of external migration efforts for source workloads. The Workload dialog displays the source workload configuration plus the project, wave, batch, and schedule information. You can set custom fields and add notes to the Transformation History.

Decommission (Decom)

For Decommission, the Workload dialog displays the source workload configuration, project, wave, batch, and schedule. You can also view and add notes to the Transformation History.

PTM does not display the target workload configuration, but it stores the values in the PTM database. It includes proposed values in Advanced Search, Bulk Edit, and Bulk Status Change actions and tracks indirect edits. Thus, you can move a workload in and out of a decommission state.

For manual and decommission methods, PTM does not display the Target workload configuration, but it stores the same-as-source target workload values in the PTM database. It includes proposed values in Advanced Search, Bulk Edit, and Bulk Status Change actions and tracks indirect edits.