When you upgrade from 2.0.2 or 2.1 to 2.5, the core components are not upgraded or redeployed. Instead, the old core components are replaced with new core PlateSpin Orchestrate components. If, however, you made any changes to the core components, those changes are saved and you can manually re-enter the configuration you want after the upgrade.
For example, suppose you have deployed the xen provisioning adapter job and you made custom changes to the xen30 policy file. When the PlateSpin Orchestrate Server prepares for an upgrade, it repackages the xen provisioning adapter by creating a .sar archive and then stores it in /Orchestrate_instance_directory/snapshot/deployment/core/xen.sar. This xen.sar archive contains the current state of the Xen provisioning adapter, including your custom changes.
Later, when the PlateSpin Orchestrate Server is upgraded, the new xen provisioning adapter for the new server is deployed, but the changes you made previously are not applied. To apply these changes to the new server, you have two choices:
Use the PlateSpin Orchestrate Development Client to manually apply the changes to the new server’s core component. (You can review what these changes were by looking at the snapshot files in the xen.sar archive.)
(Conditional) If you are migrating between servers of the same version whose core components have not changed, you can use the zosadmin redeploy command to manually redeploy the snapshotted core component.
NOTE:After the upgrade to 2.5, some earlier-version provisioning adapter jobs (esx, vcenter2x, vmserver) and the VMs provisioned by those jobs are not redeployed for use. Any resource or other objects previously managed by these provisioning adapters are no longer manageable, even though they still exist in PlateSpin Orchestrate.