IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Pre-deployment phase
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Mainframe users
Mainframe environments have some unique considerations. There are features that are available only when running a z/OS hub monitoring server and features that are available only when running a distributed hub monitoring server.
This section outlines those considerations so that you can make the best choice for your environment.
- Unique z/OS hub monitoring server features
- The z/OS hub monitoring server allows you to take advantage of RACF authentication. However, the OMEGAMON for MQ Configuration product has some specific integration with RACF that requires a z/OS hub in order to take advantage of RACF authentication within the OMEGAMON for MQ Configuration product.
The z/OS hub does not provide the Hot Standby feature. High availability is achieved using a movable hub solution.
- Unique distributed hub monitoring server features
- Three features that are provided on a distributed hub monitoring server environment are not available on z/OS hub monitoring server environments.
- Remote deployment
- Tivoli Enterprise Monitoring Automation Server and its Performance Monitoring service provider
- Hot Standby
The distributed hub monitoring server has a feature called Hot Standby to assist with high availability and disaster recovery scenarios. Many users choose not to use the Hot Standby feature and instead deploy OS Clusters for high availability and disaster recovery.
- Linux on z/VM systems
- Many mainframe users run Linux on their z/VM systems. Many different Tivoli Monitoring components can be installed in Linux on z/VM environments, including the monitoring server, portal server, monitoring agent and warehouse-related components. Each Linux environment can be configured with monitoring server or portal server software, or both.
Parent topic:
Pre-deployment phase