Version Phase Out

This section describes the consideration for phasing out old version agents.

Once the Rollout is complete for a new version, the older version should be phased out. Older version agents will be shutdown during these scenarios and the next higher version agent will process the older version jobs.

The solution design here is as follows:
  • Among all the OMS enterprise server deployments, the lowest rollout version is identified as the base version.
  • This means any agent running in base version mode(IsBaseVersion=Y) looks for data which is created from same version or lower.
  • Agent servers belonging to Rollout Version greater than base version(IsBaseVersion=N) would look for transaction data only with the same version as the agent’s Rollout Version.

The IsBaseVersion flag is passed in the agent Criteria parameter.

Note: When the older version is about to be phased out, ensure that newer version Agents can process older version transactional data
The agent would follow this logic:
  • EnableMultiVersionSupport=Y: Enables the multiversion support for the agent.
  • EnableMultiVersionSupport=N: Disables the multiversion support for the agent.
  • IsBaseVersion=Y: Process all transaction data with rollout version same as or lower than the agent Server’s rollout version. This would also process transaction data that is not version tagged.
  • IsBaseVersion=N: Process all transaction data with rollout version same as the agent Server’s rollout version.