Browse Prior Art Database

Process for Dynamic Discovery of Managed Resource and Autonomic Manager Instances Through a Well Defined Common Base Event

IP.com Disclosure Number: IPCOM000147302D
Original Publication Date: 2007-Mar-09
Included in the Prior Art Database: 2007-Mar-09
Document File: 3 page(s) / 88K

Publishing Venue

IBM

Abstract

Process for dynamic discovery of Managed Resource and Autonomic Manager instances through a well defined Common Base Event

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 44% of the total text.

Page 1 of 3

Process for Dynamic Discovery of Managed Resource and Autonomic Manager Process for Dynamic Discovery of Managed Resource and Autonomic ManagerProcess for Dynamic Discovery of Managed Resource and Autonomic Manager Process for Dynamic Discovery of Managed Resource and Autonomic Manager

Instances Through a Well Defined Common Base Event Instances Through a Well Defined Common Base EventInstances Through a Well Defined Common Base Event Instances Through a Well Defined Common Base Event

An autonomic manager is a component in a policy -enabled system that selects policies, evaluates policies, and provides decisions to the managed resource in order to manage its behavior. A managed resource is a controlled system component that receives the decision guidance from the autonomic manager . An example of a managed resource includes a server, database server, router, or a business application. An autonomic manager communicates with a managed resource through a management interface of sensor and effector operations. Sensors help the autonomic manager understand the state of the managed resource. Effectors are typically used to cause some sort of change in a managed resource, such as altering state data or setting property values. The sensors and effectors that define a managed resource 's interface are typically defined in one or more properties file (typically a WSDL, WS-RP, or MRP document).

The following figure details the management interface styles defined for a managed resource:

Managed Resource

Sensors provide access to state through one of two styles: Retriev e-State or Receive- Notification.

Retrieve-state is an interaction style in which an external entity polls an element for some details.

Receive-Notification is an interaction style in which an element sends an unsolicited message.

Sensors Sensors

Effectors prov ide ways to change state through one of two styles: Perform-Command or Call-out-Request.

Perform-Operation is an interaction style in which an external entity issues a command against a n element.

Call-Out-Request is an interaction style in which the elements asks another capability for some details.

Effectors

These are "request-response" flows that return some information or data.

They can be either synchronous or asynchronous.

These are single directional flows
that do not return any information
or data.

They can be synchronous or
asynchronous. They can return details about the
success or failure of the flow.

In one scenario of Autonomic Management , a Managed Resource may "Notify" Autonomic Managers of their current state . Notification occurs in the form of a Common Base Event (CBE) as defined in the ACAB.BO0301 Specification. The CBE used in this context contains information regarding the Managed Resource and the Managed Resource State such that the Autonomic Manager can identify the Managed Resource as one it has been configured for and can subsequently perform additional monito...