Ironstream Modernization Guide

Ironstream collects z/OS data, transforms it, and forwards it to platforms like Splunk, ServiceNow, and Elastic. It supports various z/OS data sources, including SMF, SYSLOG, and log4j.

Ironstream uses configuration files to define data sources, transformations, and destinations. These files specify parameters for data collection, filtering, and forwarding.

Ironstream supports protocols such as TCP and UDP for data transmission. It can also use secure protocols like TLS/SSL for encrypted communication.

Ironstream provides logging capabilities to monitor its operations. Logs capture information about data collection, transformation, and forwarding processes, aiding in troubleshooting and auditing.

Ironstream uses configuration files, typically in a text-based format, to define data sources, transformations, and destinations. These files are edited directly or through a provided interface.

Ironstream does not expose a public-facing API in the traditional sense (REST, SOAP). Instead, it relies on configuration files and internal mechanisms for integration with other systems.

The main system components include the Data Collector, Transformation Engine, and Forwarder. The Data Collector retrieves data from z/OS sources. The Transformation Engine processes and formats the data. The Forwarder sends the data to external platforms.

Ironstream supports authentication methods such as LDAP and Kerberos for secure access. It also uses TLS/SSL for encrypting data in transit.

Configuration parameters include data source definitions, transformation rules, destination settings, and security configurations. These parameters are set in the configuration files.

Ironstream provides real-time visibility into z/OS data, enabling faster problem resolution and improved decision-making. By forwarding data to platforms like Splunk, it allows organizations to leverage their existing analytics tools.

By centralizing z/OS data with other enterprise data, Ironstream enables a holistic view of IT operations. This helps organizations identify and address issues that span multiple platforms.

Ironstream helps organizations meet compliance requirements by providing a secure and auditable way to access and analyze z/OS data. It supports encryption and access controls to protect sensitive information.

Ironstream supports authentication methods such as LDAP, Kerberos, and X.509 certificates. These methods ensure that only authorized users can access the system.

Ironstream uses an access control model based on user roles and permissions. This allows administrators to define granular access controls for different users and groups.

Ironstream uses TLS/SSL encryption to protect data in transit. This ensures that sensitive information is not exposed during transmission between components.

Ironstream provides audit logging capabilities to track user activity and system events. These logs can be used to monitor security and compliance.

Ironstream provides a command-line interface (CLI) and web console for administrative tasks. The CLI is used for scripting and automation, while the web console provides a graphical interface for configuration and monitoring.

User management is handled through the administrative interfaces, where administrators can create, modify, and delete user accounts. Access controls are defined based on user roles and permissions.

Ironstream provides monitoring and logging capabilities to track system performance and identify potential issues. Logs capture information about data collection, transformation, and forwarding processes.

To configure Ironstream, you typically modify configuration files to define data sources, transformations, and destinations. These files are usually in a text-based format and can be edited directly.