COSMOS Design 197868

Management Domain for COSMOS DC framework

This design document addresses COSMOS Bugzilla enhancement request 197868.

Change History:

Name: Date: Revised Sections:

Jimmy Mohsin 8/25/2007 Initial version

Overview

The Management Domain is the highest level lookup registry to find the address of the Brokers. The Management Domain can be considered a "Broker of Brokers".

The above is the class diagram for the Management Domain.

The purpose of the Management Domain (referred to as domain for short) is to provide a mechanism to faciliate the initialization of the management system. The domain has a stereotype of <<WSDM>>, indicating it will expose its public interface as a stateful Web service in conformance with the WSDM MUWS specification.

The properties of the domain are made available via WS-RF, i.e. getResourceProperties()

Implementation Stages and Corporate Use Cases

The Management Domain will evolve over time to accommodate the needs of the corporate use cases as follows:

Version 1 will satisfy the initial CA use cases.

Version ? will support the data source types requirements of the IBM use cases.

Version ? will support the CMDBf use cases from CA and IBM.

Version ? will support the CMDBf use cases from Compuware.

Terminologies/Acronyms

The terminologies/acronyms below are commonly used throughout this document. The list below defines each term:

Term Definition

Data Broker This is the component where all the web services that share data register themselves Data Store This is a physical software artifact that stores data, e.g. Oracle, a File System, etc Data Manager Largely corporate implementation component that implements the SOA API for data exchange. A Data Manager can be an MDR. Service Broker This is the component where all the web services that share functional behavior register themselves Management Domain A "Broker of Brokers"

Management Domain Use Cases

---

Use Case 1. Data Broker Initialization'

---

Use Case 2. Date Broker Restart

---

Use Case 3. Data Broker Shutdown

Notes

Note: When designing the management domain, one of the well defined entries needs to be the endpoint of the repository where we get the information about the resources. In the current web.xml for the data visualization, the repository is assumed to be a simple file based access. It's encoded as follows.

       <context-param>
               <param-name>SML_REPOSITORY</param-name>
               <param-value>sml</param-value>          
       </context-param>        

Going forward, this should be an EPR that we get via the domain. The only thing in the web.xml that would then be required is an epr for the mangaement domain.

---