| Tivoli Finds Its Way In P&A | |||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||
|
A Nod To Standards James Governor |
Examples of the kind of standards discussed above include the Common Information Model (CIM), Java Management Extensions (JMX), and Windows Management Interface (WMI). CIM is a set of standards-based resource and instrumentation models under the auspices of the Distributed Management Task Force (DMTF); currently CIM models cover technologies such as relational databases and desktops, though the DMTF is working with the Storage Networking Industry Association (SNIA) to define common standards for interoperable storage management as well. JMX is Java's standard instrumentation model for J2EE and Java-based applications. It works by establishing an M-Bean (management bean) to manage interactions between an organization's Java infrastructure and a management console. JMX has not yet been widely adopted, but BEA has been a keen supporter.1 As J2EE becomes more widely adopted, JMX is also likely to become more accepted. For now though, proprietary app server instrumentations, such as WebSphere's Performance Management Interface (PMI) are more common. Meanwhile in the Microsoft world, what Redmond says goes. Thus WMI is a de facto standard that Tivoli and other systems management companies must support. 1. See Illuminata Research Note, "App Server Manageability", (February 2002).
| ||||||||||||||||||||||||||||||||||||||