[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsdm] Primer text
Thanks Zhili, I now understand what this section is about. I had interpreted it to be about sending notifications to alert managers of changes in the WSDL of the resource which had me puzzled. Based on your explanation and the example you provide I can put together a proposal for that section. Thanks, William -----Original Message----- From: Zhili Zhang [mailto:zhili@tibco.com] Sent: Wednesday, August 10, 2005 6:04 PM To: Vambenepe, William N; wsdm@lists.oasis-open.org Subject: RE: [wsdm] Primer text William, In order to support WS-BaseNotification, the endpoint has to implement "Subscribe" operation at least. In other word, the developer for MyPdaDevice manageability endpoint has to copy/paste "Subscribe" operation from WS-BaseNotification WSDL document portType definition into MyPdaDevice WSDL portType and do necessary SOAP binding. There are simlimar text written about modifying WSDL document for supporting WS-ResourceProperties in section 2.5.1. You may take a look. Hope this help. Thanks -Zhili -----Original Message----- From: Vambenepe, William N [mailto:vbp@hp.com] Sent: Wednesday, August 10, 2005 5:16 PM To: wsdm@lists.oasis-open.org Subject: [wsdm] Primer text Hi all, Here is some proposed text for the primer sections I signed up for. I appear to be also signed up for a section 2.7.2 titled "changes to the WSDL document" but AFAIK we don't do anything to support notification on such an event so I am not sure what I am supposed to write about. Anyone remembers what this is about? Regards, William 2.7 Notifications In addition to allowing consumer to retrieve information from manageability endpoints, WSDM MUWS allows consumers to register for notification when events occur that apply to the manageable resource. For example, when a threshold is reached in a particular metric or when a new dependency is created for that resource. WSDM MUWS makes use of the mechanism defined by the WS-Notification family of specifications. The WS-BaseNotification specification describes SOAP messages used to create a new subscription and to manage a subscription. The subscription messages cans be sent to manageability endpoints and the subscription is then scoped to events related to the resource(s) managed by the manageability endpoint. WS-Topics provides a way to create a semantic model (composed of topics) to represent a hierarchical view of potential topics of interest. The WSDM MUWS specification, like other specifications, defines specific topics (by using the WS-Topics specification) that corresponds to the domain of interest of the specification, management in the case of WSDM MUWS. Examples of such topics correspond to the following events: - creation of a new relationship - creation/destruction of a manageable resource and/or a manageability endpoint These topics are meant to be used in conjunction with other topics defined by other specifications and/or domain-specific topics. Finally, the third specification in the WS-Notification family is WS-BrokeredNotification which provides support for the case, often needed for scalable systems, when the event producer needs to be relieved of the task of even propagation, delegating it to a broker instead. WSDM MUWS allows this mechanism to be used when appropriate but does not require it. For more details on the WS-Notification family of specifications, the reader is invited to consult specifications and documentation from the WS-Notification technical committee. 2.7.1 Changes to the resource properties document One common use case for notification in systems management is monitoring for changes in the state of the resource as represented by the resource properties document. This is supported through the a mechanism defined in the WS-ResourceProperties specification: for each property in the resource properties document, a topic is created based on the name of the property. To signal that it is able to provide notification when that property is modified, a manageability endpoint includes the corresponding topic to the list of topics it supports. (...) 7.6 Accessing a model consisting of more than one resource WSDM MUWS provides ways to interact with directly-addressable manageable resource through manageability endpoints, but it is not limited to the case where a manageability endpoint provides access to just one resource. A manageability endpoint can provide access to a system of resources and still make use of the mechanisms defined by WSDM MUWS. One example is through the use of the WS-ServiceGroup specification. That specification describes how to create a group of resources. Some or all of the resources in a service group can be manageable resources, in which case the service group is a manageability endpoint for a system composed of several resources. The resources should still follow the WSDM MUWS specification in terms of exposing properties such as identity and others. These properties can be accessed by addressing the resources directly, but in some cases they can also be accessed through the service group itself. Similarly, subscribing for notification on a management topic on a service group (if the service group supports such topics) is equivalent to subscribing for notification on that same topic on the resources that are part of the system represented by the service group. In that sense, WSDM MUWS allows management of not just individual services but entire systems. Service groups are just one of several ways to represent such a system. These system representation can contain not just a the state of the resources but also additional metadata and information about how the resources relate to one another. Resource models such as CIM can define ways to serialize a representation of a system into an XML document and this XML document is then made available through the mechanisms defined in WS-ResourceProperties. RDF is another example of a potential format for representing a system. In a sense, one can think of the "normal" case of a manageability endpoint providing access to one manageable resource as a special case of manageability endpoints providing access to a system of resources, the special case being that the system is composed of only one resource. --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]