| Copy Solution Registry to Derived Update VRC (ttpmc2290m000) |  |
| use.session.to copy the solution registry from one update VRC, which is the source VRC, to another update VRC, the target VRC, that is directly derived from that source VRC. The following figure shows the form of the session: The session is specifically written for ERP LN customization partners who want to install the subsequent PMC patches for a particular release in separate update VRCs that are directly derived from each other. Infor does not recommend that you use this session to copy the registry of Feature Packs. The reason is because Infor also does not recommend that you install subsequent Feature Packs in derived VRCs. You must enter the source VRC and the target VRC. Both VRCs must exist in PMC and must have the same base VRC. The VRC entered as target VRC must be derived from the source VRC in the Package VRCs (ttadv1511m000) session. The current session copies the Solution Registry (table: ttpmc201) of the installed solutions of the source VRC to the target VRC. The following is an example of a VRC structure at an ERP LN customization partner: The VRCs Product(x)U_pa3 and Product(x)U_pa4 are defined as update VRCs. The solutions of Patch 3 are installed in Product(x)U_pa3. Customizations in Product(x)U_cus3 are upgraded with the fixes of Patch 3. Now, when Patch 4 is released, you must install this patch in a separate VRC, because the customer who owns customization Product(x)U_cus3 cannot upgrade to Patch 4, whereas another customer, who owns customization Product(x)U_cus4, must upgrade to Patch 4. Before you can install the solutions of Patch 4 in the new update VRC Product(x)U_pa4, the registry of Patch 3 VRC Product(x)U_pa3 must be copied to this new update VRC Product(x)U_pa4, because the dependencies between solutions of Patch 4 and solutions of Patch 3 are only checked in the update VRC in which the solutions are installed. Important! If you use this session to copy the solution registry, you can no longer uninstall the solutions in the source VRC. Related topics PMC introduction PMC overview PMC recipient procedure
Fields | Description
Source VRC | A physical VRC at the PMC recipient side in which updates are installed. Every update VRC has a base VRC linked.
Target VRC | A physical VRC at the PMC recipient side in which updates are installed. Every update VRC has a base VRC linked.
Commands | Description
Continue | Copies the solution registry from the source VRC to the target VRC.