Hello,
Is there any ideas or someone who knows how to get all event suppressions moved into OBM 2023.05 from our other OpenText tools?
Any information greatly appreciated.
Thanks,
Freddie
Thanks for feedback.
Freddie
Cybersecurity
DevOps Cloud
IT Operations Cloud
If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more
Hello,
Is there any ideas or someone who knows how to get all event suppressions moved into OBM 2023.05 from our other OpenText tools?
Any information greatly appreciated.
Thanks,
Freddie
Thanks for feedback.
Freddie
I have read your post several times, but I cannot understand what you are asking for. Please clarify or even elaborate with screenshots to explain what you are trying to do.
moreover, there isnt OBM 2024.05, maybe you meant 2023.05?
I edited my question. thanks.
Thanks for feedback.
Freddie
Can you list the other tools and also perhaps some screenshots of the configuration/rules that you want to be able to transfer to OBM?
Hello,
I don't think there is anything out of the box that is going to give you all the event suppression you need from other Opentext software applications.
I think this question is difficult to answer as there are many different Opentext software integrations and the methods depend: integrations are generally split into Management Packs, Connectors (the new type and the older OpsCx/BSMC), REST APIs (via OA12's opcgeni/policy configuration), directly to OBMs event REST APIs and then there are Connected Servers (Connectors, ArcSight, SiteScope, APM, External) and so on. Connected Server integration methods use similar methods - either REST or a groovy script.
OBM itself has SBEC, TBEC Correlation and Event and Event Storm Suppression. EPI scripts which can also be used for event suppression.
In terms of event suppression I feel it's always better to suppress events as close to the source as possible. Why send something if it's not needed or has been marked as a duplicate? However, I do understand this is less appropriate these days with event streaming concepts. OA12 can suppress events based on the same input, generated by the same rule or identical event related to their attributes and with message keys. While this is not event suppression on the server, it is controlled, configured and deployed on the server.
I know this isn't answering your question but it's the best I can do. Happy to answer anything specific.