Watson Marketing Ideas

Submit new product ideas for Campaign, Interact, Marketing Operations, Marketing Platform, Campaign Managed Hosted, interact Managed Hosted, Marketing Operations Managed Hosted, Digital Analytics, Tealeaf, Universal Behavior Exchange, Watson Customer Experience Analytics, Watson Marketing Insights, Watson Content Hub, Web Content Manager and WebSphere Portal solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

Submit ideas for other Watson Customer Engagement Products:

•  Watson Campaign Automation
Watson Commerce
Watson Supply Chain

File Sync - TMS Controls, ability to monitor and sync CFG files

When you have a larger Tealeaf system (>5 servers), juggling and keeping track of multiple configs, privacy, etc can be a daunting task.  Rolling them out can be even more so.  Let's say you want to roll out a new Privacy.cfg file for all your servers?  Or one of the files is out of sync for some reason?

I propose a new function of TMS that can sync and monitor DIFFs of files we set.  One time we can say which file on which servers should be "watched".  One is a the "master" and the others are "clones".  TMS will periodically check the files on the servers and see if DIFFs, size and DateMod.  The watch would have two modes: Alert or Auto-Clone.  If Auto-Clone, then it will just propagate the new file across all the servers.  If Alert, it will flag a DIFF alert to the Alert tab, maybe a red number showing there is a value in the tab (like Facebook).  Alert we'd use if we need to be careful about rolling services, like Canisters.  Auto-Clone might be fine for Privacy.cfg, etc.  Then we can go into TMS and schedule our service rolls on each server (Transport service for example).

NOTE: Need this BADLY for PCAs as well!!!  PLEASE PLEASE be able to sync privacy.cfg across all the PCAs!!

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jul 31 2018
  • Needs More Information
How will this idea be used?

Use to monitor privacy.cfg, tealeafcapturesocket.cfg, and other configuration files across the PCA, HBR and Canister tiers.

What is your industry? Banking
What is the idea priority? Urgent
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Admin
    ROB HAIN commented
    October 17, 2018 16:56

    Some follow-up questions for comment:

    • More clarity on the actual difference between auto-clone and alert would be helpful. Auto-clone would actually update the config file on other servers, but does it also restart the services?  If not, then is alert mode necessary?
      Alternative:  A combination of the two - automatically update the config on the other servers and let the users know those servers need services to be restarted

    • TMS currently has an option to assign a config to multiple servers. When changes are made via the TMS UI it will push the updated config out to all servers that use that config. This isn't as helpful if someone makes changes to the files directly though.

    • Regarding PCA - TMS for Linux is not currently available, so it's not running on the PCA.  Alternative:  Make TMS work on the PCA vs. adding config syncing code to the PCA.  Sizing would be required on the difference in development effort.  With TMS running on the PCA, there may be the potential for more value (e.g. show running processes)
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    October 17, 2018 18:58

    Agreed, as this might take a bit of thought as each service and configs are different.

    I'd say use the same controls, give the user the options that TMS already has: Push only or Push & restart service.  I often use the first option, as TLTMaint daily cycle usually is a good time to do those restarts all at once.  Push and Restart option is do to it when I'm actually watching.

    For the second point: It does have this option, but this monitoring option enables those teams that can't use TMS for more complicated config files, or customized files like nested pipelines, extra privacy files, etc. Also, offering extra options like offering to "check" DIFFs of things like the Scheduler XML (for Canister Maint cycles) would be very useful.

    TMS on PCA: Creating a service that can interface with Windows TMS might be a good stepping stone to eventually porting portions of the system over to Linux (eg, the HBRs/transport boxes).  Additionally, alerts when the PCA goes down and STAYS down - right now the only monitor we have for this is Tealeaf Status report which is just a comprehensive list.