PMC recipient procedure

For multi-tenant cloud, the PMC recipient is fully configured by Infor and all PMC sessions are available.

Setup

The setup includes these parts:

Parameters

For details, see the session.

Note: 
  • Because parameter definition is a one-time step, you must be aware of the impact if you change the parameters afterwards.
  • If you change the operating system paths, you must move the directories and files according to the new path specifications.
Update VRCs

PMC uses update VRCs. The software of an initial standard master product is installed in a root VRC that is predefined by the software supplier. The update VRC is created on top of this root VRC. The update VRCs are created automatically during the installation of the master product.

In addition, you can define update VRCs using the session.

In general, the VRC structure for standard LN resembles this diagram:

B61_a is the VRC that contains the baseline, which is the first shipment of LN 6.1. From this point on, Individual solutions and Service Packs are installed in the B61U_a_stnd VRC.

For the Infor Enterprise Server, packages tt, tl, tm, da and nt, no new update VRCs are created and used.

This table shows the update VRCs that are present in PMC, after a fresh installation of LN:

Pack Update VRC Base VRC
da 3.3U b stnd 3.3 b da
tt 7.6 b 7.6 a tt
tf B61U a stnd B61 a

The heading of the first column in the table, Pack., refers to the package to determine the VRC structure.

Installation of software updates

To install software updates through PMC:

  1. Scan updates.

    The first step to make the solutions available to the PMC registry is to scan the solution files with the session. The solutions receive the status Available in the update VRC for which the scan is carried out. All the relevant PMC data is stored in the PMC registry.

  2. Check update to install.

    All the following functionality is controlled by the session.

    The solutions with the status Available that are connected to the update VRCs must be checked with the session. The related solutions are checked as well. The solutions, including the related solutions which must be installed, receive the status To Install. Optionally, detailed information is given on customized components and components that exist in non-supported languages.

  3. Install update.

    You can install the solutions with status To Install in the session. If the PMC registry was changed after the solution received the To Install status, the solution must be checked again before the solution can be installed. The related solutions are installed as well. After the solutions are installed, the status of the solutions is Installed.

Uninstallation of software updates

To uninstall software updates through PMC.

  1. Check the update to uninstall.

    All functionality is controlled by the session and the session.

    If a solution must be uninstalled, for example, because the solution was a bad fix, use the session. The solution status and the status of related solutions becomes To Uninstall.

    Note: You can use Check to uninstall from the session to uninstall all solutions that were installed together in one run. For example, a solution including all prerequisite solutions or solutions of a collection that were installed in a range.
  2. Uninstall the update.

    Run the session to set the status of the solution, including the related solutions, back to Available.

    Note: If during installation or uninstallation the process is stopped, for example, due to a system crash, or process kill, and the solution that was being processed still has the Installing or Uninstalling status, with the next start of a processing session from the session, PMC recognizes this situation and starts the stopped process again for the interrupted solution. If a sequence of solutions was to be installed or uninstalled, you must restart the process for the remaining solutions.