This presentation focuses on the significance of the CMDB to your organization and offers practical guidelines for successful population of the CMDB utilizing the Tivoli Netcool suite of products. Specific products discussed include Precision for IP Networks, Tivoli Application Dependency Discovery Manager (TADDM), Tivoli Business Service Manager (TBSM) and Maximo.
Cloud Computing 2010 - IBM Italia - Mariano Ammirabile
A Practical Guide to CMDB Deployment in a Tivoli Environment
1. A Practical Guide to CMDB Deployment in a Tivoli Environment Presented by: Antonio Rolle VP of Professional Services One Step Ahead of IT. IN STEP With Your Business .
2.
3.
4.
5.
6.
7.
8.
9.
10. The CMDB should - ... (1.) Hold the (a.)relationships between all system components, including incidents, problems, known errors, changes and releases… (b.) information about incidents, known errors and problems, and corporate data about employees, locations and business units... often… (c.) details of services and to (2.) relate them to the underlying IT components …and (3.) store inventory details … such as suppliers, cost, purchase date, and renewal date for a license.. SOURCE: Office of Government Commerce “ ”
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23. The CMDB – What’s In It CMDB Open and published interfaces, Federation, Reconciliation architecture CSV/Text Files SQL DB’s 3 rd party Apps XML Files Documents TADDM Precision
24. Clarke’s Third Law Any sufficiently advanced technology is indistinguishable from magic. Source: Arthur C. Clarke “ ”
25.
26.
27.
28. Audit Configuration Items via Comparison Dissimilar attribute values are highlighted Enables easy comparison of like CIs to a ‘master’ copy
29. Identify changes to assist problem resolution 1) Select change history window to identify changed components in any application 2) Changed CIs are easily identified 3) View detailed history of the changes by attribute
39. BMC Atrium CMDB 2.0 Overview Business Process Data People Data BMC Atrium CMDB Relationships Relationships Drift Tracking Status Accounting Discovery CI Viewer CI Browser Analytics Management Console Infrastructure Data Mainframes Batch Processes SOA
42. Populating Atrium – The Common Data Model BMC_ComputerSystem HostName TotalPhysicalMemory BMC_System BMC_BaseElement BMC_ApplicationSystem Build Number PatchNumber ServicePack DatasetID, Description, ManufacturerName, Model, Name, VersionNumber
43.
44. Populating Atrium – Process Overview Policy Engine Impact Web Services XML Extract TADDM Discovery
45. The CMDB – What’s In It Discovery/Data Integration Engine CMDB Open and published interfaces, Federation, Reconciliation architecture TADDM
53. The CMDB – What’s In It Discovery/Data Integration Engine CMDB Open and published interfaces, Federation, Reconciliation architecture TADDM Precision
54. Populating the CMDB with Precision IP Data Policy Engine Impact DSA XML Extract Precision Discovery CMDB
55.
56.
57.
58.
59.
60.
61.
62. The CMDB – What’s In It Discovery/Data Integration Engine CMDB Open and published interfaces, Federation, Reconciliation architecture CSV/Text Files SQL DB’s 3 rd party Apps XML Files Documents TADDM Precision CSV/Text Files XML Files SQL DB’s 3 rd party Apps Documents
63.
64.
65.
66.
67. The CMDB – What’s In It CSV/Text Files SQL DB’s 3 rd party Apps XML Files Documents TADDM Precision Discovery/Data Integration Engine CMDB Open and published interfaces, Visualization Federation, Reconciliation architecture CSV/Text Files XML Files SQL DB’s 3 rd party Apps Documents
68.
69.
70.
71. Manage the Change Process with CCMDB View and claim assigned tasks View RFC details and complete task Refer to previously completed tasks, including SME documentation
72. The CMDB – What’s In It CSV/Text Files SQL DB’s 3 rd party Apps XML Files Documents TADDM Precision Discovery/Data Integration Engine Open and published interfaces, Visualization Federation, Reconciliation architecture CSV/Text Files XML Files SQL DB’s 3 rd party Apps Documents Configuration Change
Stands for: Information Technology Infrastructure Library Is a non-proprietary set of best practices – public domain developed and maintained by the Government of the United Kingdom, i.e. Office of Government Commerce – OCG Aims at aligning IT services with business requirements Is a set of “best practices”, not a methodology Provides guidance, not a step-by-step how-to manual; the implementation of ITIL processes will vary from organization to organization based on parameters such as IS organization size Helps IS organizations in the provision of optimal IT service at a justifiable cost Background Origin - U.K. government initiative to create a standard for IT processes within its departments. Administered - U.K. government's Office of Government Commerce (OGC; www.ogc.gov.uk) Own ITIL Work with organizations internationally on world-class best-practice framework. Review content Promoted - IT Service Management Forum , or itSMF Separate nonprofit foundation and review board organization 15 member organizations that test, modify and promote ITIL Partner with OGC Published a series of 7 books on ITIL covering various areas of focus. Current Adoption Greatest popularity in the UK and in Northern Europe Quickly gaining popularity among leading-edge Enterprises & SPs in NA Benefits of ITIL include: Improved quality service provision; Cost justifiable service quality; Services that meet Business, Customer and User demands; Integrated centralized processes; Individual roles and responsibilities in service provision; Learning from previous experience; Demonstrable performance indicators.
What is the CMDB? The Configuration Management Database (CMDB) is at the heart of aligning business with IT The CMDB is NOT… An Asset Management Database An Inventory Database A Silver Bullet
At the heart of BSM and ITIL is the Configuration Management Database (CMDB) which provides a single view of configurable IT assets like servers, desktops, routers and their relationships to each other and to IT processes. As a centralized approach to managing everything from customer-specific data, to changes in infrastructure and incident and problem management, the CMDB strives to deliver a common, consistent and standardized point around which to drive all critical IT processes and functions. Central to the ITIL concept of a CMDB is the requirement for a common data schema applied across all local data stores, to allow data to be passed to one central CMDB. The CMDB is like a data warehouse in that it can be viewed as a way to get disparate data from disparate management tools. In effect, the CMDB becomes the home for all relevant data across all areas of the IT service delivery process.
The three key differentiators of our solution are: Complete application visibility The value of the solution is only realized if you have support all the components within the data center. So Collation provides the widest breadth in terms of components we support – we offer support to over 200 components via our sensors today (body of knowledge that understands how to identify and model a discovered components) out of the box today. Breath is only as good as depth. We offer the most depth in terms of discovering and modeling all the configurations of the components we discover. For example, we will provide visibility into All the EJB’s deployed within an application server as well as their changes over time All the configurations of a load balancer that allows you to identify how the LB supports its back end systems We support over 95% of the commonly found data center elements today; for the 5% we don’t, we have built in extensibility with our product to help us do it quickly in the field. The only solution built for integration We realized very early on that the application maps are critical to supporting a lot of other initiatives and projects within the IT organizations – for example Governance, compliance. We are the only vendors who provides you an open and published API/SDK to easily share this data with other applications For example at the WB, we have been integrated to a wide variety of products (Remedy for ITIL CMDB, Managed Objects for BSM dashboard, Tivoli for event correlation etc.). The WB integration has been done by our integration partner and has been concluded in a couple of months – a testament to how easy is it to integrate our solution to a wide variety of solutions in the field Rapid Time to Value Lastly, our discovery solution is agent-less, which means that we require no installation of agents in order to discover your application infrastructure. Since we require no instrumentation of your environment allows us to install and provide you application maps in a matter of days and not months. So to recap, the three key differentiators of Confignia are: Comprehensive breadth and depth which provides comprehensive and accurate visibility Openness of our interfaces, which allows you to integrate our maps easily into your initiatives Our agent-free solution that provides rapid time to value
At the heart of BSM and ITIL is the Configuration Management Database (CMDB) which provides a single view of configurable IT assets like servers, desktops, routers and their relationships to each other and to IT processes. As a centralized approach to managing everything from customer-specific data, to changes in infrastructure and incident and problem management, the CMDB strives to deliver a common, consistent and standardized point around which to drive all critical IT processes and functions. Central to the ITIL concept of a CMDB is the requirement for a common data schema applied across all local data stores, to allow data to be passed to one central CMDB. The CMDB is like a data warehouse in that it can be viewed as a way to get disparate data from disparate management tools. In effect, the CMDB becomes the home for all relevant data across all areas of the IT service delivery process.
Now assume that you have identified a degradation in the application performance (thru 3 rd party transaction monitoring solutions). As you know, 50% of application performance. Issues are typically change related (Gartner). Using the Confignia change engine, you can quickly identify what has changed in this app between any two time periods. The components in yellow identify the changed components We also identify all the changes in the component configuration, which allows you to quickly narrow down and isolate the configuration changes that may be causing the problem. That’s the power of Confignia – this would have taken days if not weeks if done manually.
At the heart of BSM and ITIL is the Configuration Management Database (CMDB) which provides a single view of configurable IT assets like servers, desktops, routers and their relationships to each other and to IT processes. As a centralized approach to managing everything from customer-specific data, to changes in infrastructure and incident and problem management, the CMDB strives to deliver a common, consistent and standardized point around which to drive all critical IT processes and functions. Central to the ITIL concept of a CMDB is the requirement for a common data schema applied across all local data stores, to allow data to be passed to one central CMDB. The CMDB is like a data warehouse in that it can be viewed as a way to get disparate data from disparate management tools. In effect, the CMDB becomes the home for all relevant data across all areas of the IT service delivery process.
TADDM discovers configurations and interdependencies across the following environment entities: Application components, such as Web servers, application servers, and databases System components, such as hosts, operating systems, load balancers, and database servers Network components, such as routers, switches, and firewalls Services, such as DNS and LDAP services
TADDM discovers configurations and interdependencies across the following environment entities: Application components, such as Web servers, application servers, and databases System components, such as hosts, operating systems, load balancers, and database servers Network components, such as routers, switches, and firewalls Services, such as DNS and LDAP services
TADDM discovers configurations and interdependencies across the following environment entities: Application components, such as Web servers, application servers, and databases System components, such as hosts, operating systems, load balancers, and database servers Network components, such as routers, switches, and firewalls Services, such as DNS and LDAP services
TADDM discovers configurations and interdependencies across the following environment entities: Application components, such as Web servers, application servers, and databases System components, such as hosts, operating systems, load balancers, and database servers Network components, such as routers, switches, and firewalls Services, such as DNS and LDAP services
TADDM discovers configurations and interdependencies across the following environment entities: Application components, such as Web servers, application servers, and databases System components, such as hosts, operating systems, load balancers, and database servers Network components, such as routers, switches, and firewalls Services, such as DNS and LDAP services
Situation: “Where do put my data?” Customers had a hard time getting started with the Common Data Model (CDM) 1.0 and they didn’t know where to put their CI data from existing sources. Too many classes CDM 1.0: 120 CI Classes CDM 2.0: 75 Classes CDM 1.0: 60 relationship classes CDM 2.0: 16 Classes Classes names weren’t always obvious Too many relationship types What did we do different in 2.0? Reduced the “clutter” in the data model Leverage namespaces to partition the data model Created the concept of “extension classes” Benefits Easier to use, customize and migrate data to/from the Atrium CMDB.
TADDM Common Data Model Definition of data center infrastructure components Extensive support for common data center components Software applications (web, application, DB servers) Host/OS Network Elements (routers, switches, load balancers, firewalls) Software services (DNS/NIS, LDAP, NFS, AD) Extracted to XML Data Schema
At the heart of BSM and ITIL is the Configuration Management Database (CMDB) which provides a single view of configurable IT assets like servers, desktops, routers and their relationships to each other and to IT processes. As a centralized approach to managing everything from customer-specific data, to changes in infrastructure and incident and problem management, the CMDB strives to deliver a common, consistent and standardized point around which to drive all critical IT processes and functions. Central to the ITIL concept of a CMDB is the requirement for a common data schema applied across all local data stores, to allow data to be passed to one central CMDB. The CMDB is like a data warehouse in that it can be viewed as a way to get disparate data from disparate management tools. In effect, the CMDB becomes the home for all relevant data across all areas of the IT service delivery process.
Discuss…. Please turn to the next slide.
At the heart of BSM and ITIL is the Configuration Management Database (CMDB) which provides a single view of configurable IT assets like servers, desktops, routers and their relationships to each other and to IT processes. As a centralized approach to managing everything from customer-specific data, to changes in infrastructure and incident and problem management, the CMDB strives to deliver a common, consistent and standardized point around which to drive all critical IT processes and functions. Central to the ITIL concept of a CMDB is the requirement for a common data schema applied across all local data stores, to allow data to be passed to one central CMDB. The CMDB is like a data warehouse in that it can be viewed as a way to get disparate data from disparate management tools. In effect, the CMDB becomes the home for all relevant data across all areas of the IT service delivery process.
At the heart of BSM and ITIL is the Configuration Management Database (CMDB) which provides a single view of configurable IT assets like servers, desktops, routers and their relationships to each other and to IT processes. As a centralized approach to managing everything from customer-specific data, to changes in infrastructure and incident and problem management, the CMDB strives to deliver a common, consistent and standardized point around which to drive all critical IT processes and functions. Central to the ITIL concept of a CMDB is the requirement for a common data schema applied across all local data stores, to allow data to be passed to one central CMDB. The CMDB is like a data warehouse in that it can be viewed as a way to get disparate data from disparate management tools. In effect, the CMDB becomes the home for all relevant data across all areas of the IT service delivery process.
. The goal of Configuration Management is to provide a logical model of the infrastructure and services by identifying, controlling and maintaining the versions of the Configuration Items in existence and their relationships to each other Configuration Management manages the relationships between assets or CIs – it sets up configuration structures for all CIs and documentation about them. This information is stored in the Configuration Management Database. Account for all the IT assets and configurations Accurate information about the configurations Audits by checking CIs against actual live environment and checks they are recorded in the CMDB