An Information Technology Management Reference Architecture Implementation
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
This article is the fifth in a series of articles by Edward Wustenhoff on the data center management infrastructure. The focus of this article is on the implementation of the management infrastructure.
It is a follow-up article on the "An information Technology Management Reference Architecture" article published earlier by Edward Wustenhoff and the Sun BluePrints_ group. It describes the implementation of IT management reference architecture in the Authorized iForceSM Ready Center (iFRC) program that displays an IDC Mail and Messaging Architecture. The iFRC program is a Sun program that provides reference implementations and proof of concepts to assist our customers in avoiding common pitfalls.
This article describes the technical aspects and details of the management and organization (M&O) architecture deployment. Conceptually, the IDC Mail and Messaging Reference Architecture implementation consists of two major components. The first component of the implementation is the Message Server (Sun_ ONE) that represents the mission-critical business application. The second major component of this implementation is the systems management tools that are implemented to monitor, maintain, and report on availability and SLA adherence of the business application. This is the M&O architecture.
This article describes the implementation of these tools and their interactions, and discusses how they are combined into a systems management and Service Level Agreement (SLA) reporting solution. This article provides topological views of the management implementation, individual tool implementations, combined tools implementations, and details of the essential integration points between the tools.
Limitations
This article does not describe the people and process aspects of IT management. Further, this article is not intended to be a detailed implementation reference. It is to be viewed as a proof of concept, showing the structure and essential functionality to be addressed in an M&O architecture. Also, the M&O architecture is not designed with a focus on availability and performance.