What is the Tivoli OMEGAMON Manager (TOM)?
JoeWinterton 110000BXHR Visits (1457)
We get asked many questions about the Tivoli OMEGAMON Manager (TOM) as it is a relatively new technology that runs on the zOS operating system to provide the Enhanced 3270 User Interface (e3270ui) capability. Let’s address a few of these questions.
Q) Why do we need the Tivoli OMEGAMON Manager (TOM)?
A) The TOM is designed to provide the capability of a single 3270 panel of glass view for all OMEGAMON information and navigation that spans your Sysplexes, zOS’s, CICS’s, IMS’s, DB2’s, MQ’s, Mainframe Networks, and Storage. This allows a user to LOGON once and is able (if allowed by local managed security rules setup by the site) to view any of the systems and subsystems OMEGAMON information.
Q) What is the TOM?
A) The TOM is a function that runs in a zOS address space. This address space runs as a native 64 bit mode address space. In its simplest form the TOM takes from a zOS input dataset the Workspace files that define what metrics to put on the 3270. Then the TOM goes gets the metrics from OMEGAMON XE agents and formats them per the workspace request and paints the 3270 screen. The TOM also allows users to Take Actions (if allowed by local security) like KILL, CANCEL, ENABLE, DISABLE, etc.
Q) How many TOM’s do I need to run in my complex?
A) There only needs to be a single TOM address space in any Sysplex. You can also run a backup TOM in the Sysplex on another LPAR from the primary TOM LPAR for enhanced availability. The TOM is a stand-alone component. There is a communication part of the TOM and e3270ui called the Data Retrieval Agent (DRA). This DRA code runs in the OMEGAMON XE Agent address spaces, and this DRA code can also run in any z/OS-based Hub Tivoli Enterprise Monitor Server (HTEMS) , Or Remote Tivoli Enterprise Monitoring Server( RTEMS), or other zOS agents. There is no requirement that the DRA code run in multiple address spaces (although that is typically what is done), as long as it is running in at least one z/OS address space (TEMS or agent) that connects to the Hub TEMS of interest. The TOM communicates to the DRA’s with TCP/IP protocols. A site could also if they wish setup a TOM focused only on a specific subsystem like CICS for their CICS domain experts to use.
Q) How does the Tivoli Enterprise Portal Server (TEPS) and TOM relate to each other?
A) If you understand the functionally of the TEPS then you can think of the TOM as providing similar functions on zOS as TEPS does on other platforms. The TOM administers users for OMEGAMON on zOS to allow them access to OMEGAMON information they are authorized to view. As the TEPS allows users to build their own views on a workstation, the TOM allows customer built workspaces too for 3270. The TOM provided the Extended 3270 User Interface (e3270ui). The e3270ui makes the 3270 a little like a PC with push –buttons, pull downs, basic icons, minimize, expand and collape functions. So the user has a 3270 session that is easy to drive with a emulator setup to use the mouse.
I hope this helps as an introduction into the OMEGAMON TOM.