|Subject:||RE: [wsdm] Upcoming Spec comment/Open issue note|
|From:||Vambenepe, William N (vb...@hp.com)|
|Date:||Mar 19, 2004 4:33:33 pm|
If I understand what you are asking, the answer is that this is provided by the implied resource pattern described in the "modeling state" white paper which is part of WSRF (http://devresource.hp.com/drc/specifications/wsrf/ModelingState-1-1.pdf ).
The endpoint reference (EPR) contains the address of the manageability endpoint as well as (in the reference properties) any other info that is needed to specify which resource (in your example, which manageable endpoint) the request should be executed against.
-----Original Message----- From: Fred Carter [mailto:fred...@amberpoint.com] Sent: Friday, March 19, 2004 3:31 PM To: Wsdm (E-mail) Subject: [wsdm] Upcoming Spec comment/Open issue note
Greetings those of WSDM :-)
I'm not quite sure where this belongs -- it's either an oops, an open issue, or something we'll deal with later (which are probably all really the same thing :-)
In our MOWS (at least) model, a manageability endpoint can provide management for a number of manageable endpoints. (The converse is true as well but not terribly relevant to this missive.)
Thus, some manageability endpoint A can be managing B, C, and D. Section 2.3 of MOWS outlines the responsibilities of the manageability endpoint with respect to properly collecting information.
That said, how does one get, say, metrics for B from A? Our WSDL define a port with no operations, since they come from WS-RP. Which is fine.
The WSRP FW gives us the ability to query specific properties, but I don't know that we've provided a means to scope those to a particular managed endpoint. To do so, I think, we need to have some association between the properties & endpoints; at present, the properties appear to be associated solely with the manageability endpoint.
Our interop scenario's at this point don't require this at present -- the scenario's in question outline a 1:1 mapping between business endpoint and manageability endpoint, possibly in different services. So we can clearly punt for now.
But we will, I think, have to extend the specification to deal with this eventually. We will either have to add some affiliation between metrics and managed endpoints (or other classifications) to enable queryability, refine our manageability/managed endpoint relationships, define multiple property sheets, or something.
Food for thought...
(Or I might be missing the bleeding obvious! It's been a long week... :-/ )
-- Fred Carter / AmberPoint, Inc.
mailto:fred...@amberpoint.com tel:+1.510.433.6525 fax:+1.510.663.6301
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgrou p.php.