Why do I lose my module configuration when I activate a module in TrueSight Orchestration?

Version 2

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Atrium Orchestrator Platform


    BMC Atrium Orchestrator Platform 7.x.xx BMC Atrium Orchestrator Platform 8.x.xx TrueSight Orchestration Platform 8.x.x


    When I activate a newer version of a module in TrueSight Orchestration (TSO), that module's configuration items return to an older version. I lose all of the changes I made to the configuration since I activated the last version of the module. What causes this, and can I prevent it?


    TSO stores module configurations in two locations: each module has a list of its configuration items within the module file itself, and each peer has a file with a list of all module configurations for all active modules. Workflows you run on the grid use the values in the peer's file and ignore the values in the module. When you activate a module on the grid, TSO automatically deactivates the older version of that module, which removes that module's configuration from the peer's file. Activating the module adds the module configuration back to the peer's file, but the values in those configurations item are lost. Instead, TSO uses the values you have in the module itself, which are the values you had in Development Studio when you export the module to the Repository.

    In effect, any changes you make to your module configuration items via Grid Manager do not persist through module activation. If you want to make a permanent change to the value of a module configuration item, you must make that change in Development Studio, export the modified module to the Repository, and activate it on the grid.

    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles