Tivoli OMEGAVIEW

The architecture of Tivoli OMEGAVIEW comprised several key components designed to aggregate and present monitoring data from various Candle-based products. The central component was the OMEGAVIEW server, responsible for collecting and processing data. This server communicated with the underlying monitoring agents, such as those for Omegamon for MVS and Omegamon II for CICS, using proprietary protocols.

The 3270 client provided the user interface, allowing operators to view system status, application performance, and other metrics. Data was stored in datasets, and configuration was managed through ISPF panels. The system's communication relied on TCP/IP for network connectivity.

The OMEGAVIEW server would receive data from the monitoring agents, process it, and make it available for display on the 3270 client. The system did not use a relational database for data storage; instead, it relied on datasets. The lack of a modern database and API-driven architecture is a key difference from contemporary monitoring solutions.

For example, the system did not support REST APIs or other standard integration methods. The architecture was optimized for the mainframe environment, with a focus on providing a centralized monitoring console. The system's design reflects the limitations of the mainframe environment at the time of its development.