You can instruct the Symphony middleware to override the configured version of all application profiles currently registered in the system with another version and to run workload on that other version.
When the application version override is configured, the SD must be restarted for the change to take effect, The next time the SD starts an application, it substitutes the value of the version attribute in the application profile with the version configured globally before passing the profile to the SSM. The version override feature is enabled using the SOAM_OVERRIDE_APP_VERSION_WITH environment variable in the SD. The following diagram summarizes the behavior of this feature.
This global setting takes effect on all profiles and any specific versions specified in the application profile at run time are ignored.
This setting does not have any effect during the registration of a profile, i.e., the validation logic applied during the registration of a profile is still done with respect to the version configured in the profile; for example, if the global setting is version 5.0, a profile containing a version of 4.0 is still validated against a version 4.0 schema when it registered. However, the application will run on the version 5.0 middleware.
A key fact to be aware of when using this feature is that the SD does not change the profile on the disk when overriding the application version. This means that both the CLI and the PMC application editor will show the application profile as it is on disk, which may be different than the running instance of the application after a version override has occurred.