MR2 / COSMOS DC Roadmap and Features October 24, 2007 In cooperation with:

2 Problem statement Management data cannot easily be shared across product silos or multiple vendors within todays enterprise management space Customers are very interested in the potential for lowering costs thru integration Standards to facilitate and drive this product and vendor data sharing are required Such standards and data sharing are the future platform for better management process integration and orchestration 10/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License

3 Our solution… MR2 MR2 has been designed to enable data sharing across products MR2 will enable both CA and non-CA products to share data MR2 will contribute to the design, development and delivery of an industry standard for data sharing …thru its participation and contribution to the Eclipse COSMOS Data Collection project

410/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License MR2 formally defined The Management Repository (MR2) is: a SOA-based data access service for CA (and later non-CA) products to integrate their enterprise management data independent of the underlying data handling technology of enterprise management products

510/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License MR2 Development stages & timeline Stage 1 - COSMOS DC M2 – 1H08 MR2 is currently working with the COSMOS Data Collection team to deliver Milestone 2 in the first half of 2008 This milestone will enable customers to read data from CA and non-CA products via a standard paradigm Stage 2 - Federating CMDB – 2H08 The MR2 team will continue to develop the infrastructure and building blocks as part of the COSMOS DC; these can be used for the implementation of CA's CMDBf This deliverable will enable customers to read and build correlations across data from CA and non-CA products; it is planned for the latter half of 2008

610/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License Which CA products can use MR2? Important Considerations Applications choose when to adopt MR2 Applications inherit MR 2 capabilities from MDB 1.x once it has a Data Manager MR 2 will initially support READ (2008) Future releases will support READ, WRITE, UPDATE and DELETE (2009) Any project that chooses to publish a Data Manager MR2 will provide guidelines & reference implementation for Data Ma nagers

710/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License So how does MR2 differ from MDB? MDB 1.xMR2 Is a physical store for specified CA products Is an API that provides standardized access to product data Has dependencies on underlying database technology Independent of underlying database technologies Cannot interoperate with non-CA stores Can interoperate with any store, as long as it is SOA-based Higher cost of inducting new acquisitions Lower cost of inducting new acquisitions, provided there is an API for data-sharing Has data redundanciesAPI will provide the ability to restrict further data redundancies

810/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License The COSMOS DC / MR2 architecture…

910/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License MR2 Architecture Glossary TermDefinition Data ManagerIs a component that is implemented by each product to share its data; the design of this component is driven by the Eclipse COSMOS DC Data BrokerIs a wholly Eclipse COSMOS DC component where all the web services that share data register themselves Management DomainIs a wholly Eclipse COSMOS DC component used to bootstrap the MR2 system Client (APIs & GUIs)Is a CA component used to visualize or access data from multiple applications; part of the design / implementation of this component will come from the Eclipse COSMOS DC

1010/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License Architecture and Implementation The Client / User Interface is specific to this PoC In future versions, the User Interface will be inherited from the COSMOS DC project The Data Managers were designed under the purview of the COSMOS DC project In future, the Data Manager implementation will shift more and more towards the COSMOS DC project The Management Domain and the Data Broker for this PoC were wholly designed and implemented in the COSMOS DC project

1110/24/2007 Copyright © 2007 CA DEMO PoC

1210/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License Participants in the COSMOS DC effort Active Participants CA Cisco Compuware IBM Aware participants HP Novell SAS

1310/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License Where are we today - COSMOS i6 ReleaseDescription COSMOS i6 1.Has an initial release of Management Domain & Broker 2.Has a corporate implementation of two Data Managers 3.Has an extensible GUI framework

1410/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License What is COSMOS Milestone 2? The COSMOS Data Collection Milestone 2 (hereinafter M2) includes iterations i7, i8, and i9 that will: Fulfill the leveraging CMDBf use case Provide a production-class implementation of a Management Domain and Broker Provide Managed Data Repositories that support generic & CMDBf queries Provide a GUI that allows a user to traverse the Management Domain / Broker / Managed Data Repositories & Data Manager hierarchy

1510/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License The COSMOS M2 Big Picture

1610/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License COSMOS M2– Benefits & Challenges Benefits Unified approach and infrastructure for handling Asset, Configuration, and Performance data Uses WS-RC & provides reference implementation along with GUIs Provides the tools for building a Federating CMDB Challenges Adoptability / Installer capabilities & experience Security Standardized SQA process

1710/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License COSMOS M2– Exclusions We will NOT Build a Federating CMDB; this is defined as ANY query that spans more than one MDR Implement a Security infrastructure; however, we will provide hooks to plug one in Provide localized version

1810/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License Release Description - COSMOS M2 ERs ReleaseDescription COSMOS i7, i8 & i9 Management Domain (contd.) Broker (contd.) MDRs (contd.) GUI Adoptability Security

1910/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License COSMOS M2 Release Timeline I6 (GA) 2007 Fiscal 2008 Nov Oct Jan i7 1.Broker complete 2.Management Domain complete 3.MDR support Sept i8 1.Fulfill the Leveraging CMDBf use case 2. Rich UI capabilities DC CAPABILITIES Dec 2008 Leveraging CMDBf

2010/24/2007 Copyright © 2007 CA, made available under the Eclipse Public License Next Steps Establish how / when we will be able to use cross-MDR queries Define touch-points with the CMDBf effort Identify the exact CMDBf deliverables Facilitation of Adoption Package should be easy to install / adopt Package should be easy to extend Enhance our SQA processes

Questions?