Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

COSMOS Archived Use Cases


COSMOS Archived Use Cases for 1.0


Led by: Ali Mehregani & Hubert Leung

Related components/technologies/standards:

  • Integration with Application Logs (Based on existing work)
  • Performance Data
  • Event subscription & publication
  • WS-BaseNotification, WS-NotificationBroker, WS-Topics
  • WSDM Event Format

Use Case: Client subscription to events

This use case is no longer valid for COSMOS 1.0. Archiving.

Description: This use case elaborates COSMOS efforts around WS-Notification. There will be a notification broker provided in COSMOS where notification producers and consumers can publish or subscribe to events in the context of web services.

  1. Client contacts the management domain
  2. Client queries for the notification broker associated with the management domain. Notice that an adopter can choose to replace COSMOS notification broker with a completely differently implementation that is based on WS-NotificationBroker
  3. Using the end point reference of the notification broker, the client queries for topics published by notification producers using WS-Resource Properties.
  4. Client subscribes to one or more published topics. Subscribing to a topic will cause a notification every time an event associated with the topic is raised.

Enhancements: 197868 (i6), 212293 (future)

Use Case: Report generation on incidents

This use case is no longer valid for COSMOS 1.0. Archiving.

Description: This use case elaborates on end user's ability to generate reports on any incident that a notification producer generates. The use case assumes the existence of a notification consumer that persists all events generated by notification producers.

  1. The user opens the COSMOS client and discovers the incident manager in the navigator
  2. The user expands the incident manager to display the set of configuration items associated with the MDR. In the background, a CMDBf query is submitted to retrieve all configuration items of the incident manager.
  3. The user selects a specific configuration item to generate report on the incidents that are associated with the selected item. A custom query API can be used in this case to retrieve incidents associated with the item.
  4. The user can also generate overall reports by selecting the incident manager instead of an individual configuration item

Enhancements: 212293 (future), 212297 (future), 209990 (future)

Back to the top