Transformation Hub supporting multiple different ESM topics and consumers

Idea ID 2705606

Transformation Hub supporting multiple different ESM topics and consumers

There is quite a few scenarios in which multiple ESM's are in use, being able to utilize one Transformation Hub cluster to deliver data from multiple connectors towards multiple ESM's without all of them having to consume all data would be great.

This could be done by supporting the creation of multiple ESM topics, and support ESM consuming more than one hardcoded topic name.

This would depend on another idea for routing binary data located here:

https://community.microfocus.com/t5/ArcSight-Idea-Exchange/Support-routing-on-binary-data/idi-p/2705145

1 Comment
Micro Focus Contributor
Micro Focus Contributor
Status changed to: Accepted

Yes, the ability for a centralized THub to manage multiple destinations is a requirement and we will be addressing this in the next couple of releases of THub.

There are several architectural foundational features that we must address to support this and these are also being implemented in the next release and one or two more releases thereafter.

The transformation hub was renamed precisely to handle event format transformations and to allow routing to multiple kafka topics as needed.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.