Why does the apps/plugins active list differ between instances after an upgrade?

[Dipu Joy]

With each upgrade, both app and plugin versions are updated, leading to variations in the dependency list, which get auto-activated based on the selected war file. Consequently, these apps and plugins will be automatically activated or upgraded during the process, ensuring compatibility with the selected war version.

The discrepancies in the active plugins and app lists between SUBPROD and PROD instances are primarily attributed to the clone parent of the instance. If all SUBPROD instances are recent clones of PROD, the upgrade behaviour will be consistent. However, if any changes, such as new plugin or app activations or upgrades, were made to the SUBPROD instance before the upgrade, or if it underwent a different war version upgrade cycle prior to the SUBPROD upgrade, the behaviour will vary. This is because each war version has its own set of plugins and applications that are active by default out-of-the-box (OOB).

It is essential to compare similar environments to ensure accurate benchmarking. Therefore, if you wish to conduct a dry run of the upgrade, please ensure that the PROD instance is cloned to SUBPROD and perform the upgrade as soon as possible to benchmark the behaviour effectively.

The Out-of-the-Box (OOB) Plugin/App Active list will differ for instances in Zurich if they have undergone the following cycles:

- Instance provisioned as Zurich

- Instance provisioned as Vancouver ⇒ Xanadu ⇒ Zurich

- Instance provisioned as Vancouver ⇒ Yokohama ⇒ Zurich

- Instance provisioned as Xanadu ⇒ Zurich

This is due to each family version having a distinct active plugin/app list, which includes newly introduced and deprecated items compared to the previous release. For instance, a deprecated version on Vancouver will not be active on an instance provisioned on Xanadu.

These differences should not pose an issue for customers. Even if a customer acquires a new instance on the latest release, it will be cloned from PROD, ensuring consistency with the PROD instance. However, discrepancies may arise when comparing a Zurich instance PDI with one linked to the customer.