Multiple Instance Patching Support in Middleware

Managing multiple instances of the Middleware applications requires a structured approach to ensure seamless patching.

The multiple instances patching of the software consists of two key steps:
  1. Discovery
  2. Patching

Discovery

The software's installed path and versions are identified through Discovery tasks. These tasks consider:
  • Default installation locations of the software
  • Running instances
  • Configured custom paths

Once the Discovery tasks are executed, the results are stored as a JSON file in <BESClient path>/middleware/<Software>. These JSON files are utilized by patching Fixlets and the analysis to show the installed version and the path. Therefore, it is recommended to run the Discovery task before patching or whenever analyzing the results.

Patching

All the discovered paths are patched to the relevant version in a single execution of the patching task.
Note: Since the patching task relies on Discovery results, it is advisable to run the Discovery Fixlet before patching. After patching, the Discovery Fixlets should be executed again to verify the updated results.