Architecture and Data Flow - ironstream_for_micro_focus_omi - 7.2

Ironstream for Micro Focus® OMi for IBM Z® Concepts

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Micro Focus® OMi
Version
7.2
Language
English
Product name
Ironstream for Micro Focus OMi for IBM Z
Title
Ironstream for Micro Focus® OMi for IBM Z® Concepts
Copyright
2021
First publish date
2007

Ironstream for Micro Focus OMi for IBM Z consists of two main components:

  • The Ironstream Agent component that runs on the z/OS mainframe

  • Ironstream Proxy Server component that runs on a Ironstream Proxy Server.

Ironstream for IBM Z differs from OMi Management Packs in that message templates are not distributed to anIBM Z Agent. Instead, collected messages are forwarded from the agent to the Ironstream Proxy Server and template processing is done within the Micro Focus Operations Agent portion on the Ironstream Proxy Server. This pulls most of the message processing work off of the mainframe, where CPU time is a more valued resource.

The diagram below shows the data flow between the IBM Z Agent, the Ironstream Proxy Server and the Micro Focus OMi server.

Similar to other Micro Focus Operations agents, Ironstream enables you to respond to critical z/OS events and messages through pre-defined automatic actions and resolution instructions, or by creating trouble tickets to notify your operations staff. Messages coming from the z/OS system are routed to the OMi server and associated with the related configuration item which be default is the z/OS node. After a critical situation is resolved, the automation can be set up to close in OMi.