The two main parts of the Ironstream Integration Components are:
- The Ironstream Agent for IBM i that runs on an IBM i (AS/400) LPAR (the agent).
- The Ironstream Proxy Server that runs on a Windows or Linux system (the Proxy Server).
An Ironstream Agent for IBM i will need to be installed on each LPAR that you want to monitor.
The Ironstream Proxy Server:
- Runs as a service.
- Can receive information from multiple agents.
- Includes the Ironstream for IBM i Configuration Tool for configuring which agents it receives messages from.
- Communicates with each agent via a separate, dedicated service that it creates on the Windows or Linux system. For example, if the proxy is receiving information from three agents then there will be three additional services on the Windows or Linux system.
Events and performance data that are forwarded from the agent to the proxy server can be sent to these destinations:
- Splunk (written to a file which is monitored by a standard Splunk forwarder).
- Kafka (acting as a Kafka producer to send the data to a Kafka broker).
This figure illustrates the data flow between the agent, the Proxy Server, and the supported destinations.