Do I need one connector for each TAG MCS and TAG MCM, or just one for the MCS and the MCS does the polling of MCM?
Also, if I have 3 MCMs and single MCS, how many elements do I need?
Hi Bruno,
A single MCS element should be sufficient for your example. The MCS will retrieve all the data from the MCMs attached to it, so there is no need to create MCM elements in the system.
We have also seen that some MCM functionalities are limited when attached to the MCS, so it is preferable to rely on the MCS. For example, if you create a scan in the MCM, it will eventually disappear and be shown only in the MCS.
By the way, there is a LowCodeApp available in the catalog to monitor MCS and/or MCMs in a given DMS: https://catalog.dataminer.services/details/0ef8f78a-beeb-4ec0-b321-e79b26b393ce
Hi Victoria, the current version of the MCS only supports modifications to UMD per tile in layout.
However, if the tally configuration is available in the TAG API, we should be able to include that into the driver.
Out of curiosity, which parameters/tables/columns are you using in your automation scripts and correlation rules?
With this we can quickly review how easy it would be to include that information in the MCS too
Hi Sebastian,
Currently, we make changes to TAG element > Tally Layouts > Tally Layout Channel Tiles. We make changes to UMD settings, UMD text, and tally colour.
-Victoria
Hi Victoria, we have a UMD Editor available in the TAG Management app (see the example here: https://community.dataminer.services/wp-content/uploads/2024/04/TAG-Input-UMD-configuration.gif)
I wonder if your use case is similar to the one presented in the example. If so, then the MCS connector already contains what you need
Hi Sebastian,
Thanks for the information. Within the MCS element, will I still have access to each individual MCM’s tally layout configuration so that I can tie automation and correlation rules to certain PIP UMDs?
Thank you!