Update policy

This section describes a procedure to install, test and make a new Feature Pack operational in your live environment. The procedure minimizes the effect in terms of system downtime for the operational environment.

Scenario

The master product in VRC B61_a and Feature Pack 1 is installed. It includes several individual solutions on top of Feature Pack 1 in update VRC B61U_a_stnd. This update VRC is linked to package combination b61au. Customizations are available in the B61U_a_cus VRC that is linked to the b61cus package combination. Various operational companies are linked to package combination b61cus.

Now you can install Feature Pack 2. But first you want to explore the new Feature Pack in a separate environment without disturbing the operational business.

Two methods are available to explore the new Feature Pack in a test environment:

  • Method 1

    Switch companies between VRC branches.

  • Method 2

    Have a permanent separate test VRC branch.

This diagram shows the recommended update procedure for Feature Packs:

Procedure

Steps 1 through 7 are identical in both methods. Step 8 contains different instructions for method 1 and method 2.

  1. Install Feature Pack 2 in the new Update VRC, for example, B61U_a_std2. The new update VRC must be derived from the master product VRC B61_a. In addition, create a new package combination, for example, b61au2. If you install the Feature Pack using the Infor Installation Wizard, you can have the Infor Installation Wizard create the new update VRC and package combination automatically. The PMC tool guarantees that all individual solutions that were installed on top of Feature Pack 1 in the B61U_a_stnd VRC are also installed in the B61U_a_std2 VRC. Unless these solutions are already included in Feature Pack 2. Therefore, from a maintenance perspective, the B61U_a_stnd and B61U_a_std2 VRCs are synchronous after installation of Feature Pack 2.
  2. Companies that are linked to the b61au2 package combination enable you to investigate on runtime the behavior of the standard product without customizations. To achieve this, link one or more test companies to the new package combination b61au2. You can do this in various ways:
    • If you have existing test companies linked to the b61au package combination, you can relink these companies to the b61au2 package combination. Use the session.
    • Copy an existing company that is linked to package combination b61au with the Copy Company Data (tccom0214m000) session. Next, relink the newly copied company to the b61au2 package combination with the session.
  3. You can now explore the Feature Pack 2 that is installed in the B61U_a_std2 VRC.
  4. Create package VRCs B61U_a_cus2 and the related package combination b61cus2.
  5. Copy the contents of the B61U_a_cus VRC to the B61U_a_cus2 VRC using the session. Make the b61cus2 package combination runtime using the Create Runtime Data Dictionary (ttadv5210m000) session. Note that, at this point, the customizations are still not synchronized with Feature Pack 2.
  6. Copy one or more companies that are linked to package combination b61cus with the Copy Company Data (tccom0214m000) session. Next relink the newly copied company to the b61cus2 package combination using the session.
  7. After you explore the new Feature Pack, upgrade customizations in the B61U_a_cus2 VRC, and prepare your organization to use the new Feature Pack. Verify whether additional solutions were installed in the B61U_a_stnd VRC after you performed Step 1. To perform this verification, use the session. Install the missing solutions in the B61U_a_std2 VRC as well. Synchronize the customizations again if required.
  8. Depending on the method, method 1 or method 2, perform one of these procedures:
    • Method 1: Switch companies between VRC branches:
      1. Transfer the operational companies from the b61cus to the b61cus2 package combination. To perform this transfer, use the session.
      2. After completing the previous steps, all operational companies and users are linked to the b61au2 package combination. To install the subsequent Feature Pack 3, you must repeat the process, but now in the opposite direction: you install Feature Pack 3 in the B61U_a_stnd update VRC. Again, you can create an additional VRC branch for Feature Pack 3. This process requires more installation time and disk space. The test companies are relinked to the b61au package combination. Feature Pack 3 is explored and finally the operational companies are linked to the b61au package combination.

      In theory you can apply the same mechanism for patches. One important difference applies. Patches are not cumulative. Installation of a patch requires that you at least have installed the preceding patch. Therefore, you cannot directly install Patch 2 in the B61U_a_std2 update VRC. You first must install Patch 1, followed by the installation of Patch 2. In the same way, you first must install Patch 2 in update VRC B61U_a_stnd before you can install Patch 3.

    • Method 2: Have a permanent separate test VRC branch:
      1. Install Feature Pack 2 in the B61U_a_stnd VRC. Copy the contents of the B61U_a_cus2 VRC to the B61U_a_cus VRC using the session. Make the b61cus2 package combination runtime using the Create Runtime Data Dictionary (ttadv5210m000) session.
      2. To install the subsequent Feature Pack 3, repeat the process.

      You can apply the same procedure for patches when you use Method 2.

Advantages and disadvantages of both methods

Method 2 has the disadvantage that you must install Feature Pack 2 twice. Therefore the system downtime is greater than if you use Method 2.

The system downtime for Method 1 requires time to reconfigure the application database and relink the company and users.

The system downtime for Method 2 requires time for these processes:

  • Install and make the Feature Pack runtime.
  • Reconfigure the application database.