Share your ideas

Enable customizing TMS to manage other configuration files

Recently we migrated our Tealeaf to a new environment, with lots more servers (VM). To manage, more easily, the various configurations on the various servers we are looking into using TMS. This seems like a great option for many of the IBM standard configuration files. However, there are some files we cannot (yet) manage via TMS:

- Other IBM standard configuration files, ex. ReplayRulesProfile.xml

- Custom configuration files (we created a few custom Pipeline Session Agents, which have their own config files)

See also case 00166404.

  • Walter Van Geffen
  • May 26 2020
How will this idea be used?

Use TMS for centralized management of configuration files, and minimize having to log in to each Tealeaf server, or manually use "put file" for each Tealeaf server.

What is your industry? Banking
What is the idea priority? Medium