WSDM MUWS 1.0 Part 2

2Web Services Distributed 3Management: Management Using 4Web Services (MUWS 1.0) Part 2

th st 5Working Draft, November 26 1 2004

8Location: 9 http://docs.oasis-open.org/wsdm/2004/12/wd-wsdm-muws-part2-1.0.pdf

10Editors: 11 William Vambenepe, Hewlett-Packard 12Abstract: 13 There are two specifications produced by the Web services Distributed Management 14 technical committee: Management Using Web services (MUWS) and Management of 15 Web services (MOWS, see [MOWS]). This document is part of the formerMUWS. 16 MUWS defines how an Information Technology resource connected to a network 17 provides the manageability interfaces such that it the IT resource can be managed 18 remotely from remote locations using Web services technologies. 19 MUWS is composed of two parts. This document represents is MUWS part 2. It and 20 provides specific messaging formats used to allow enable the interoperability ofle MUWS 21 implementations of the MUWS specification. Part MUWS part 1 [MUWS Part 1] provides 22 the fundamentaloundational concepts for management using Web services. MUWS pPart 23 2 depends on MUWS part 1 but while part 1 is independent from of part 2.

24Status: 25 This document is a working draft of version 1.0. There is no guarantee that any part of its 26 the content in this document will appear in the final, released MUWS 1.0 specification. 27 Committee members should send comments on this specification to the 28 [email protected] list. Others should subscribe to and send comments to the 29 [email protected] list. To subscribe, send an email message to 30 [email protected] , with the word “subscribe” as the body of 31 the message. 32 For information on whether any patents have been disclosed that may be essential to 33 implementing this specification, and any offers of patent licensing terms, please refer to 34 the Intellectual Property Rights section of the WSDM TC web page (http://www.oasis- 35 open.org/committees/wsdm/). 36 The errata document for this specification is maintained at: 37 http://docs.oasis-open.org/wsdm/2004/12/wd-wsdm-muws-part2-1.0-errata.pdf

391 Introduction ...... 4 402 Use of the Web Services Platform ...... 5 41 2.1 Use of WS-Resource Properties ...... 5 42 2.2 Use of WS-Notification ...... 6 43 2.3 Metadata ...... 6 44 2.3.1 Metadata applicable to all aspects of manageability interfaces ...... 6 45 2.3.2 Metadata applicable to properties ...... 7 46 2.3.3 Operations ...... 8 47 2.4 Events ...... 8 48 2.4.1 Event Format ...... 8 49 2.4.2 Topics for capabilities ...... 11 50 2.5 Representation of Categorization Taxonomies in XML ...... 12 513 Capabilities applicable to manageable resources ...... 14 52 3.1 Description ...... 14 53 3.1.1 Definition ...... 14 54 3.1.2 Properties ...... 14 55 3.2 State ...... 15 56 3.2.1 Definition ...... 15 57 3.2.2 Describing State Models ...... 15 58 3.2.3 Information Markup Declarations ...... 17 59 3.2.4 Properties ...... 18 60 3.2.5 Operations ...... 19 61 3.2.6 Events ...... 19 62 3.3 Operational Status ...... 19 63 3.3.1 Definition ...... 20 64 3.3.2 Properties ...... 20 65 3.4 Metrics ...... 20 66 3.4.1 Definition ...... 21 67 3.4.2 Information Markup Declarations ...... 21 68 3.4.3 Metadata ...... 22 69 3.4.4 Properties ...... 23 70 3.4.5 Events ...... 23 71 3.5 Configuration ...... 24 72 3.5.1 Definition ...... 24 7wd-wsdm-muws-part2-1.0 8Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 3 of 67 9 734 Capabilities applicable to management in general ...... 25 74 4.1 Relationships ...... 25 75 4.1.1 Definition ...... 25 76 4.1.2 Information Markup Declarations ...... 26 77 4.1.3 Properties ...... 28 78 4.1.4 Operations ...... 29 79 4.1.5 Events ...... 29 80 4.2 Relationship Access Capability ...... 30 81 4.2.1 Definition ...... 30 82 4.3 Relationship Resource Capability ...... 31 83 4.3.1 Definition ...... 31 84 4.3.2 Properties ...... 31 85 4.4 Advertisement ...... 32 86 4.4.1 Definition ...... 32 87 4.4.2 Events ...... 32 885 Discovery ...... 35 89 5.1 Discovery using Relationships ...... 35 90 5.2 Discovery using Registries ...... 35 916 References ...... 37 92 6.1 Normative ...... 37 93 6.2 Non-normative ...... 38 94Appendix A. Acknowledgements ...... 39 95Appendix B. Notices ...... 40 96Appendix C. Schemas ...... 41 97Appendix D. WSDL elements ...... 46 98Appendix E. Topics ...... 48 99Appendix F. Description of situation types ...... 50 1001 Introduction ...... 4 1012 Usage of the Web Services Platform ...... 5 102 2.1 Use of WS-Resource Properties ...... 5 103 2.2 Use of WS-Notification ...... 5 104 2.3 Metadata ...... 6 105 2.3.1 Metadata applicable to all aspects of manageability interfaces ...... 6 106 2.3.2 Metadata applicable to properties ...... 7 107 2.3.3 Operations ...... 9 108 2.4 Events ...... 9 109 2.4.1 Event Format ...... 9

10wd-wsdm-muws-part2-1.0 11Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 4 of 67 12 110 2.4.2 Topics for capabilities ...... 12 111 2.5 Security ...... 13 112 2.6 Representation of Categorization Taxonomies in XML ...... 13 1133 Capabilities applicable to manageable resources ...... 15 114 3.1 Description ...... 15 115 3.1.1 Definition ...... 15 116 3.1.2 Properties ...... 15 117 3.2 State ...... 16 118 3.2.1 Definition ...... 16 119 3.2.2 Describing State Models ...... 16 120 3.2.3 Information Markup Declarations ...... 18 121 3.2.4 Properties ...... 19 122 3.2.5 Operations ...... 20 123 3.2.6 Events ...... 20 124 3.3 Operational Status ...... 20 125 3.3.1 Definition ...... 21 126 3.3.2 Properties ...... 21 127 3.4 Metrics ...... 21 128 3.4.1 Definition ...... 22 129 3.4.2 Information Markup Declarations ...... 22 130 3.4.3 Metadata ...... 23 131 3.4.4 Properties ...... 23 132 3.4.5 Events ...... 23 133 3.5 Configuration ...... 24 134 3.5.1 Definition ...... 24 1354 Capabilities applicable to management in general ...... 25 136 4.1 Relationships ...... 25 137 4.1.1 Definition ...... 25 138 4.1.2 Information Markup Declarations ...... 26 139 4.1.3 Properties ...... 28 140 4.1.4 Operations ...... 29 141 4.1.5 Events ...... 29 142 4.2 Relationship Access Capability ...... 30 143 4.2.1 Definition ...... 30 144 4.3 Relationship Resource Capability ...... 30 145 4.3.1 Definition ...... 30 146 4.3.2 Properties ...... 31

13wd-wsdm-muws-part2-1.0 14Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 5 of 67 15 147 4.4 Advertisement ...... 31 148 4.4.1 Definition ...... 31 149 4.4.2 Events ...... 32 1505 Discovery ...... 34 151 5.1 Discovery using Relationships ...... 34 152 5.2 Discovery using Registries ...... 34 1536 References ...... 36 154 6.1 Normative ...... 36 155 6.2 Non-normative ...... 37 156Appendix A. Acknowledgements ...... 38 157Appendix B. Notices ...... 39 158Appendix C. Schemas ...... 40 159Appendix D. WSDL elements ...... 46 160Appendix E. Topics ...... 48 161Appendix F. Description of situation types ...... 51

164Muws This document, MUWS Ppart 2, (this document) builds upon the foundation provided by 165[MUWS Part 1]. All of the normative content text presented in MUWS Ppart 1 is considered 166normative text for MUWS Ppart 2. All informational content text presented in MUWS Ppart 1 is 167relevant informational content text for MUWS part Part 2. Compliance with MUWS Ppart 1 is 168REQUIRED in for all every aspects of MUWS Ppart 2. 169The text of this specification along with C (Schemas), D (WSDL elements), E (Topics) and F 170(Description of situation types) is considered are normative with the following exceptions: the 171abstract, the examples, the UML diagrams, and any section explicitly marked as non-normative 172are is considered non-normative text. 173The terminology and notational conventions defined in [MUWS Part 1] apply to this document. 174The following namespaces will beare used, unless specified otherwise.

Prefix Namespace

muws-p1-xs http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd muws-p2-xs http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd muws-p2-wsdl http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.wsdl muws-events http://docs.oasis-open.org/wsdm/2004/12/muws/ wd-wsdm-muws-events- 1.0.xml wssg http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ServiceGroup-1.2-draft-01.xsd wsdl http://www.w3.org/2002/07/wsdl soap http://schemas.xmlsoap.org/wsdl/soap/ xs http://www.w3.org/2001/XMLSchema

175XML elements ([XML1.0 3rd Edition]) and schema ([XML Schema Part 1] and [XML Schema Part 1762]) types introduced in this section belong to the namespace mapped to “muws-p2-xs”. 177WSDL ([WSDL 1.1]) elements introduced in this section belong to the namespace mapped to 178“muws-p2-wsdl”.

180In additionAs a complement to the usage of the Web services platform described in [MUWS Part 1811], MUWS part Part 2 makes usepresents of an additional set of specifications. for tThe purpose 182MUWS Part 2 specification of provides a means to acheieve ing interoperability among disparate 183implementations of MUWS. This goal is acheived by the precisely specification ofying the format 184of for each management messages exchanged.

1852.1 Use of WS-Resource Properties

186MUWS leverages and builds upon the concepts presented in the Web Services Resources 187Framework ([WSRF]). , in which,A the MUWS "manageable resource"s are is a refinement of a 188WSRF represented by Web services as “resources”., in the WSRF sense of the term. TheBy 189composingtion of a manageability endpoint and with a manageable resource, made accessible 190through this endpoint, MUWS creates a WS-Resource, as defined by [WS-Resource]. References 191In MUWS, a reference to a manageability endpoints in MUWS relies uponuse the reference 192mechanisms as defined by in [WS--Resource], and more specifically, leverage and refine the 193endpoint references (EPR) concept, as defined by in [WS-Addressing]. 194If the a manageability endpoint corresponds to a zero or morevariable number (zero or more) of 195manageable resources, then the “WS--Addressing Using Reference Properties Embodiment” of 196[WSs-Resource] MUST be followed. This means thatIn other words, the each element(s) listed in 197the ReferenceProperties of a WS-Resource qualified EPR must MUST be included in the header 198of each messages sent to such each corresponding manageability endpoints. The MUWSis 199specification does not currently define how to obtain the an EPR. Currently, to obtain an EPR, 200There there may be be an some out-of-band agreement between a service provider and a 201manageability consumer. on how to obtain EPRs orPossibly, some future versions of this the 202MUWS specification would might clarify and standardize this subjectan approach to obtain an 203EPR. 204In the specific case where a manageability endpoint corresponds to one and only one 205manageable resource, then either the “WS-Addressing Using Reference Properties Embodiment” 206concept, as above, or the “WS-Addressing Without Using Reference Properties Embodiment” 207concept MUST be usedfollowed. If the “WS-Addressing Without Using Reference Properties 208Embodiment” is usedfollowed, this means thatthen the manageability endpoint does not expect to 209receive the a list of elements listed in the ReferenceProperties section of WS-Resource qualified 210EPR s inincluded in the message header. 211s to indicate which resource is being managed. A manageability consumer who does not 212havewithout an EPR for a manageability endpoint MAY try to invoke manageability operations 213without including reference properties information. If such an invocation succeeds, the 214manageability consumer can infer it is talking about a manageable resource through a 215manageability provider. 216Furthermore, management properties as defined in MUWS are represented as WSRF 217“properties”, in the WSRF sense of the term, using and use the mechanisms defined in WS- 218ResourceProperties ([WS-RP]). This means thatIn other words, each manageable resource 219exposes a resource properties document (containing, as children of the document root, all the 220properties of the manageable resource. The manageable resource then makes) and makes this 221document available, as specified described in WS-ResourceProperties. 222Supporting WS-ResourceProperties means that any implementation of an interface that includes 223properties MUST include access methods to these properties as defined by

22wd-wsdm-muws-part2-1.0 23Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 8 of 67 24 224WS-ResourceProperties. Specifically, the interface MUST include the GetResourceProperty 225operation defined by [WS-RP] and MAY include the GetMultipleProperties, 226SetResourceProperties and QueryResourceProperties operations. If the 227QueryResourceProperties operation is provided, then the QueryResourceProperties operation it 228SHOULD support the XPath 1.0 query expression dialect, represented by URI 229http://www.w3.org/TR/1999/REC-xpath-19991116.

2302.2 Use of WS-Notification

231MUWS uses the notification mechanism described by WS-BaseNotification ([WSN]). When If a 232manageability capability includes the an ability to offer events to a consumer, then the definition 233of the capability will SHALL include a WS-Topics ([WST]) topic space, as described in WS-Topics 234([WST]). The topic space SHALL containing the an appropriate set of topics appropriate for the 235events offered by the capability. As described in part MUWS Part 1, an event is defined by a URI 236and a “content” element. The URI corresponds to the “topic” of the event, as defined by [WST]. 237Note that as WS-BaseNotification does not currently support a way means to specify that only 238some of the information contained in the notification message should be sent to the consumer. 239MUWS does not define a way means to specify this either. Manageability The manageability 240consumers and the implementers of a manageability endpoints should be aware of there is a the 241performance cost of for processing a large number ofmany, large notification messages.

2422.3 Metadata

243MUWS defines a set of base schema for metadata elements. These metadata elements can be 244to be represented as XML Schema elements. whose The purpose of a metadata element is to 245supplement the information available in the WSDL [WSDL 1.1] and the WS-ResourceProperties 246[WS-RP] declaration for a manageability interface. A metadata element to provides additional 247description relevant to the managed resource. In particular, a metadata element it allowsenables 248a tools and or management applications, to perform detailed be able to reasoning and make 249specialized inferences in detail about the a manageable resource both at runtime, and, within 250during development tools , when no instance is available for a manageable resource. instances 251are available. 252These characteristics are needed necessary, both at runtime, and, at build timeduring 253development. Metadata elements need to , which means that they must be available when no 254instance is available for a manageable resource e without having a running instance of the 255resource. 256If metadata is required, then an XML document containing metadata can beis defined and 257associated with the a WS-ResourceProperties document and WSDL. Document processing, like 258an XPath queryies, of the document can beis used to extract all or part of the metadata. 259Currently, WSDM does not define the format of, or how to associate, or, how to access the 260document metadata document at this timecontent. Although some mechanism is necessary, The 261scope of thisis MUWS specification does not includeexcludesdoes not provide the any 262functionmechanism required tofor accessing the metadata from an instance of a manageable 263resource instance. 264, aAlso,lthough it is necessary for such a mechanism to exist. This this MUWS specification also 265does notexcludesdoes not provide any description ofbe how the metadata is for associated with 266a type of manageable resource, types is are stored, and or made available to tooling at this time. 267The MUWS specification defines a set of metadata elements that apply to the basic 268manageability specific metadata of a manageable resource. The MUWS specification usess and 269Global Element Declarations to represent thema metadata element.

271MUWS defines a metadata elements applicable to all aspects of a manageability interface 272(operations, properties, events…). These capabilities elements are:

273 274xs:anyURI * 275The muws-p2-xs:Capability metadata element SHOULD be provided for any MUWS aspect of a 276manageability interface. This enables discovery of aspects of an interface associated with a 277capability. This element contains a URI identifying the capability. 278This metadata element indicates the classification of an aspect of an interface according to its an 279intended capability, (or capabilities. ), for For example, as aan aspect may be classified as a 280metric, or, as a piece of configuration and so onproperty. A property may be relevant to more 281than one capability. For example, a configuration property, such as the IP address of a computer 282system contains the IP address. This property, could also be used for identification purposes. 283Some of the known capabilities are listed below for illustration. This is not an exhaustive list. For a 284detailed explanation,s see the relevant MUWS manageability capability specification. Additional 285capabilities are expected to be added as extensions to MUWS. 286  http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Identity 287 Identity capability. See [MUWS Part 1]. 288  http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Configuation 289 Configuration property. See section 3.5. 290  http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/CorrelatableProperties 291 ”Correlatable Properties” capability. See [MUWS Part 1]. 292  http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/State 293 State capability. See section 3.2. 294  http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Metrics 295 Metrics capability. See section 3.4. 296  User defined 297 A uUser defined, capability that extends, or, is different from, the a standard capabilityies 298 defined in MUWS. 299The capabilities defined in this document specify that a property or operation has a certain value 300represented as one instance of muws:p2-xs:Capability by stating “its Capability is ”. 301 302 303 {any} * 304muws-p2-xs:ValidWhile contains a statement that, when true, asserts that the interface aspect 305to which this metadata element is related is valid. This is used, for example, to express the fact 306that an operation can only be invoked when certain properties have certain values. 307muws-p2-xs:ValidWhile/@Dialect is a URI identifying how the statement in muws-p2- 308xs:ValidWhile is built and what rules govern its evaluation. MUWS defines one possible value for 309this element. Other values can also be defined. 310The value defined by MUWS is http://www.w3.org/TR/1999/REC-xpath-19991116. When this 311dialect is used, the content of muws-p2-xs:ValidWhile is an [Xpath 1.0] expression. This 312expression is to be evaluated against the resource properties document of the manageable 313resource. If the XPath expression evaluates to a Boolean value of “true”, or if it evaluates to a 314non-empty non-boolean value without any errors, then the statement is considered “true”.

316General purpose metadata that is not management specific is defined in the MUWS specification, 317but not specified in schema. General purpose metadata that can be defined for any property 318includes: 319  Mutability – indicates if the property value will can change over time 320  Modifiability – indicates if the property can be set directly (not as a side-effect) 321  Valid Values – the a set of valid values for the property 322  Valid Range – the a range of valid values for the property 323  Static Values – the a set of initial values for the property 324  Notifiability – indicates if a notification will beis sent when there is a change to the value 325 of theis property changes value 326Schema to represent general purpose metadata should be composed in from a metadata 327specification, such asfor example, the WS-Resource Metadata Descriptor [WSRMD], as 328developed in the WS-RF OASIS technical committee. 329In addition, MUWS defines a set of metadata related to management. Any property element may 330have the following manageability metadata elements:

331 332xs:string 333muws-p2-xs:Units indicates the default unit for this property as a string.

334 335Other metadata elements, applicable for metric-type properties, are defined in section 3.4.3. 336Counter|Gauge|Unknown 337muws-p2-xs:ChangeType is an enumeration which describesfor indicating how changes to that 338the associated metric value should be interpreted by the consumer. A property that representings 339a metric MUST include a single instance of ChangeType in its metadata description. EachThe 340ChangeType following values may be used for ChangeTypeis interpreted as follows: 341  Counter - the value of the metric increments over successive counts, collections, or 342 measurements. 343  Gauge - the value of the metric varies between a range of values. 344  Unknown - the change behavior is not known or cannot be described. 345 346Interval|PointInTime|SinceReset 347muws-p2-xs:TimeScope is an enumeration that for indicatinges whether if there is some 348interval, over which the data is collected, counted, or measured. A property that is a metric MUST 349include a single instance of TimeScope in its metadata description. The following values may be 350used forEach TimeScope value is interpreted as follows: 351  Interval - the value of the metric was is collected over some time interval. In this case the 352 Duration attribute MUST be reported with the metric property. The value of the Duration 353 attribute is the time, from the beginning of the interval, to the end of the interval. The 354 Duration and is usually remains the same for every reading of the metric. 355  PointInTime - the value of the metric was is counted, collected, or measured at a single 356 instant in time. The Duration attribute MUST NOT be reported with metrics having a 357 PointInTime TimeScope value of PointInTime. Metrics with a TimeScope value of 358 PointInTime do not support the reset capability and MUST NOT include the ResetAt 359 attribute.

31wd-wsdm-muws-part2-1.0 32Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 11 of 67 33 360  SinceReset - the value of the metric was is collected since reset, or since the 361 manageable resource started collecting metrics data. In this case the Duration attribute 362 MUST be reported with the metric property. The value of the Duration attribute is the time 363 since the metric was reset, or since the resource started collecting metrics data, if no 364 reset has occurred. Thus the value of Duration willmay be report a different value for 365 every each retrievalading of the property. 366 367 368 OnChange|Periodic|OnDemand|Unknown 369 370muws-p2-xs:GatheringTime is an enumeration that indicatinges at what times the value of the 371metric is counted, collected, or measured. A property that is a metric MUST include a single 372instance of GatheringTime in its metadata description. The following values may be used forEach 373GatheringTime value is interpreted as follows: 374  OnChange - the value of the metric is updated as soon as there is whenever a change in 375 occurs to the quantity measured. 376  Periodic - the value of the metric is updated on a regular basis. 377  OnDemand - the value of the metric is updated when there is a request for the metric 378 value. 379  Unknown - it is unknown when the metric value is updated. 380 381xs:duration 382muws-xs-p2:CalculationInterval represents the interval at which the metric will beis gathered or 383calculated by the resource. The value of the metric is not updated during a calculation intervals. 384 385xs:anyURI 386muws-p2-xs:MetricGroup indicates that the metric property is a member of a group of metrics. 387A metric property MAY be a member of zero or more metric groups. A metric group is identified 388by a URI. All Each property includedies in a metric group will includeSHALL have a MetricGroup 389element with thecontaining an identical same URI. A property that is a metric MUST include zero 390or more MetricGroup elements in its metadata description. Each MetricGroup element to 391represents a membership in a all of the metric groups to which it belongs.

3922.3.3 Operations

393General purpose metadata, that is not management specific, is defined in the MUWS 394specification, but not specified in schema. General purpose metadata that can be defined for any 395operation includes: 396  Idempotency – indicates if invoking the operation twice is equivalent to invoking it once 397Schema to represent general purpose metadata should be composed in from a metadata 398specification, such for example, as the WS-Resource Metadata Descriptor [WSRMD], as 399developed in the WS-RF OASIS technical committee. 400In addition, MUWS defines metadata related to management. Any operation element may have 401the following manageability metadata element:

402 403 404 {any} *

34wd-wsdm-muws-part2-1.0 35Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 12 of 67 36 405 406muws-p2-xs:PostCondition contains a statement that is assertsed "to be true" right immediately 407after the corresponding operation is completes. 408muws-p2-xs:PostCondition/@Dialect is a URI identifying how the statement in muws-p2- 409xs:PostCondition is built, and what rules govern its evaluation. MUWS defines one possible value 410for this element. Other values can be defined. 411The value defined by MUWS is http://www.w3.org/TR/1999/REC-xpath-19991116. When this 412dialect is used, the content of muws-p2-xs:PostCondition is an [Xpath 1.0] expression. This 413expression is to be evaluated against the resource properties document of the manageable 414resource. If the XPath expression evaluates to a Boolean value of “true”, or, if it evaluates to a 415non-empty non-boolean value without any errors, then the statement is considered “true”.

4162.4 Events

4172.4.1 Event Format

418[MUWS Part 1] defines the muws-p1-xs:ManagementEvent Global Element Declaration to beas a 419container for management events. muws-p1-xs:ManagementEvent allows for information to be 420added using via extensibility elements. The muws-p2-xs:Situation element defined below MUST 421be present as a child of the muws-p1-xs:ManagementEvent element in notifications. 422The As a result, resulting the event format has ais flexible and extensible format and permitsting 423virtually free-form expression of events., while aAt the same time, automated analysis is 424possible, as the event format provides a means to classify the an event into one of a limited set of 425classifications and subclassifications. 426MUWS so that automated analysis is possible. Theevent classifications are based on a thorough 427analysis of event types, as produced by a wide range of IT equipment, and grouped according to 428the a general nature of the events. For example, virtually all manageable resources have a 429means of being started. butHowever, almost all managed resources express this a start event in 430some unique, and or imaginative, ways. The basic knowledge that the resource has been started 431is all that is necessary, for even for fairly sophisticated, automated management. 432To support these event classifications, the MUWS adds specification defines the 433SituationCategoryType element, which is a specialization of a muws-p2-xs:CategoryType. 434MUWS defines the top level of classifications., leaving open eExtensions to these classifications 435to allow for enable a refinedfiner-grained definitionevent classifications. Through the use of the 436extensible muws-p2-xs:CategoryType mechanism, WSDM event consumers can comprehend an 437the situation for an event’s situation to a degree commensurate with their capabilityability. 438 439 440 muws:-p2-xs:SituationCategoryType 441 442 443 Succesful|Unsuccesful 444 ? 445 xs:dateTime ? 446 xs:short ? 447 xs:short ? 448 muws:LangString ? 449 450 xs:anySimpleType* 451 ? 452

37wd-wsdm-muws-part2-1.0 38Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 13 of 67 39 453muws-p2-xs:Situation/muws-p2-xs:SituationCategory categorizes the type of the situation 454that caused the event to be reported. The values, listed below, represent the names of elements 455in the muws-p2-xs namespace. The categories are listed in precedence order. so that iIn a cases 456where there may be some ambiguity about which category to use, the higher precedent category 457SHOULD be chosenused. The ordering of situation categories is based on experiential data 458showing relative importance of various types of events., choosing The use of a higher precedent 459categoryies permits more effective and timely correlation and analysis of events that may lead 460toindicate the presence of a serious problems. Details and examples of for use of the following 461valuesage are documented in F. This element is REQUIRED. 462  AvailabilitySituation 463  CapabilitySituation 464  ConfigureSituation 465  StopSituation 466  StartSituation 467  RequestSituation 468  DestroySituation 469  CreateSituation 470  DependencySituation 471  ConnectSituation 472  ReportSituation 473  OtherSituation 474 475muws-p2-xs:Situation/muws-p2-xs:SuccessDisposition in the case where this situation was 476is triggered by a command, this value specifies the a successful disposition of the command that 477causinged a reoirt of this the situation to be reported. This element is OPTIONAL and should not 478be included if the situation was notis not the result of a command. It The element is a restriction of 479string with allowing the following set of values: 480  Successful 481  Unsuccessful 482 483muws-p2-xs:Situation/muws-p2-xs:SituationTime represents the date and time that thean 484event was is observed. If the value does not include a time zone designation, (or, if the value 485does not use ‘Z’ for UCT), then the value MUST be interpreted as having a time zone of UCT. 486The value of the SituationTime MUST provide granularity as precisely as supported by the 487generating platform allows. This is a REQUIRED element and MUST be provided by the 488component that iacting as the originator of the an event. 489muws-p2-xs:Situation/muws-p2-xs:Priority representsdefines the importance of the an event. 490This field element is provided forsupports management functions that requiringe an event to have 491abe associated with a priority. This is an OPTIONAL element. Values are constrained to a range 492from 0 through 100. The predefined priorities are: 493  The range of values is from 0 to 100. The reserved value for Low is (10), for 494  Medium is (50), and for 495  High is (70). 496Other priorities MAY be used but MUST NOT be less than 0 or greater than exceed 100. 497muws-p2-xs:Situation/muws-p2-xs:Severity represents the perceived severity of the status the 498event is describing with respect to the application that reports the event. This element is provided 499forsupports management functions that requiringe an event to havebe associated with a severity. 500This is an OPTIONAL element. The Spredefined severity levels, are based upon the DMTF CIM 501Alert Indications Perceived Severity, and are as follows:

40wd-wsdm-muws-part2-1.0 41Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 14 of 67 42 502  6 (Fatal): Condition a condition is unrecoverable and the service is no longer available. 503  5 (Critical): Ca condition that affecting thes service has occurred. Immediate corrective 504 action is required. 505  4 (Major): a pProblem with of a relatively high severity level has occurred. It is likely that 506 normal use of the object will beservice is impeded. 507  3 (Minor): a pProblem with ofa relatively low severity level has occurred. It is unlikely that 508 normal use of the object will beservice is impeded. 509  2 (Warning): a pProblem that affecting thes service will or couldmay occur. Diagnostic 510 and corrective action is recommended. 511  1 (Information): a Message message output is considered as normal (that is, what was 512 and expected). For example, a process begins, a process finishes, or status information 513 is displayed. 514  0 (Unknown): a sSeverity level cannot be determined. 515 516muws-p2-xs:Situation/muws-p2-xs:Message represents the text accompanying the an event. 517This is typically the resolved message string in a human-readable format, as rendered for a 518specific locale, and is of type muws-p2-xs:LangString. This type is (an extension of xs:string that 519requiringes the xml:lang attribute). This is an OPTIONAL property. The While the string length for 520Message is unbounded,. However, it is RECOMMENDED that it the string length for Message 521does not exceed 1024 characters. 522muws-p2-xs:Situation/muws-p2-xs:SubstitutableMsg – Contains represents the message 523data in a substitutable form. The attributes MsgId and MsgIdType indentify the base message 524type and text. The element value contains the data that will be formatted according to the 525formatting rules defined by the MsgId. This is an OPTIONAL element. However, but, if this 526element is used, it must contain all the attributes and elements specified below. 527muws-p2-xs:Situation/muws-p2-xs:SubstitutableMsg/@MsgId specifies the message 528identifier of the an event. This identifier SHOULD be a unique value string, consisting of 529alphanumeric or numeric characters. The valueIt can be as simple as a string of numeric 530characters that identify a message in a message catalog. As an alternative, orthe value can be a 531multipart string of alphanumeric characters, (for example, DBT1234E). This is a REQUIRED 532attribute. The maximum string length for MsgId MUST NOT exceed 256 characters. The 533MsgIdType attribute indicates the formatting type of the MsgId. 534muws-p2-xs:Situation/muws-p2-xs:SubstitutableMsg/@MsgIdType specifies the meaning 535and format of the MsgId. This is a REQUIRED attribute. The type of the MsgIdType attribute is a 536URI. 537muws-p2-xs:Situation/muws-p2-xs:SubstitutableMsg/muws-p2-xs:Value can be of any 538simple type. There are one or more occurrences of this element with each occurrence containing 539an xsi:type attribute defining the type of the contained data. This element is used to pass data 540values which will bethat are substituted whenas the a message is formatted. This element is 541OPTIONAL. Each A MsgId and MsgIdType defines in its rules how to map parameters into a 542composed the message, based upon the order of the Value elements.

543 Figure 1 represents a UML description of the Situation element.

43wd-wsdm-muws-part2-1.0 44Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 15 of 67 45 MUWS::Situation MUWS::Situation SituationCategory[1] -SituationCategory SuccessDisposition [0..1] MUWS::SubstitutableMsg -SuccessDisposition MUWS::SubstitutableMsg SituationTime[0..1] MsgId[1] -SituationTime -MsgId Priority[0..1] MsgIdType[1] -Priority -MsgIdType Severity[0..1] Value[0..*] -Severity -Value Message[0..1] -Message SubstitutableMsg[0..1] -SubstitutableMsg 544

545 546 Figure 1: Situation Element

547As an example, a minimal SituationType report for the initiation of a requested restart (at 6:06PM 548in Greenwich on Nov 11, 2004) would be as follows. 549 550 551 552 553 554 555 Succesful 556 2004-11-11T18:06:00Z 557 558 559 Managed Thing XXX: restart processing begun 560 561 562It is worth notingPlease note, that, as outlined in the description of muws-p2-xs:CategoryType, 563the most general situation classification is appears as the innermost (in terms ofelement within 564the XML nesting).

5652.4.2 Topics for capabilities

566For each capability defined by MUWS, a topic is defined to that encompasses all every events 567related to that capability. For example, if a property related to a capability “foo” defined by MUWS 568changes, then a notification is sent to subscribers to of the topic that correspondings to a change 569events on this specific eventproperty, (as described by [WS-RP]). At the same timeConcurrently, 570since this property is related associated to with the “foo” capability, a notification is also sent to 571subscribers to of the topic that encompassinges change all events related toassociated with 572capability foo. 573E is contains the XML description of all the topics defined by in the MUWS specification. The 574following It MUWS topics includes the following topics, that encompass all every events related 575toassociated with a the given capability: 576  IdentityCapability corresponds to the Identity capability defined in [MUWS Part 1]. 577  ManageabilityCharacteristicsCapability corresponds to the Manageability Characteristics 578 capability defined in [MUWS Part 1] 579  CorrelatablePropertiesCapability corresponds to the Correlatable Properties capability 580 defined in [MUWS Part 1] 581  DescriptionCapability corresponds to the Description capability defined in section 3.1. 582  OperationalStatusCapability corresponds to the Operation Status capability defined in 583 section 3.3. 584  MetricsCapability corresponds to the Metrics capability defined in section 3.4. 585  RelationshipsCapability corresponds to the Relationships capability defined in section 586 4.1. 46wd-wsdm-muws-part2-1.0 47Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 16 of 67 48 586  RelationshipResourceCapability corresponds to the Relationship Resource capability 587 defined in section 4.3.

5882.5 Security

589For security, MUWS relies on generic Web services security mechanisms, including 590transport-level security, for example (e.g. HTTP over SSL), and, OASIS Web Services Security 591message-level security [WSS], etc.. The composition of appropriate security specifications and 592this specification provides a for secure management using Web services, as realized by 593implementations of manageability endpoint implementations. The choice of a concrete security 594mechanisms should be madecarried out by the implementers of athe manageability endpoints,

5952.6 Representation of Categorization Taxonomies in XML

596In the description of several manageability capabilities, categories of information are organized in 597taxonomies. For example, the categories of relationships between manageable resources, 598operational states of resources, etc. In order to convey the category information, including the 599taxonomy lineage, to the a manageability consumers, and, in order to represent it in XML 600information instances, the following convention is used: 601MUWS defines an XML Schema complex type called CategoryType. The content of XML 602elements of this type is any XML element. When an element is defined of this type, it MUST obey 603the following rules: 604  The element and alleach its of its descendant hasve, at most, one child element., 605  The top-level element and each of its descendants each represent one category in a the 606 taxonomytaxonomy., 607  The top level element represents the most specialized category. and eEach element 608 represents a more specialized category than the category represented by the element it 609 contains, if any. 610The CategoryType XML Schema type is declared as follows: 611 612 613 614 615 616The CategoryType type is used to either to declare an XML elements which containing instances 617of general, or (unqualified,) category information. The CategoryType type is also used to or to 618derive an XML Schema types to representing a specific category, for example,ies such as ofa 619relationships between among resources, or of among operational states.

620 621The cCategory information MUST be declared as follows:. 622  An XML element is declaringed which QName identifies the semantics of a the category. 623  The XML element MUST be declaringed with the an XML Schema type which is a 624 restriction of Category, or a specialized XML Schema type derived from the Csome other 625 Category refinement (e.g., for example, RelationshipType). 626  The contents of the XML element MUST be either:

49wd-wsdm-muws-part2-1.0 50Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 17 of 67 51 627  The only one XML element which correspondings to the generalization of the 628 currently declared category 629  Or The empty sequence., if This case occurs if the currently declared category does 630 not have any generalizations. For example, the declared category might be the (top 631 of thea taxonomy). 632For example, let’s assume that information about a maintenance state needs to beis represented 633in XML, using the approach described above abovedescribed approach. In this example, “off-for- 634maintenance” is a substate of “offline”, which is a substate of a resource being a resource being 635generally “unavailable”. Following would be the The XML representation in XML for this example 636follows:. 637 638 639 640 641 642By processing the XML information, a manageability consumer may understand learn that a 643resource is in the a state identified by the mydomain:Off-for-Maintenance element. However, at 644the same time, if the manageability consumer is not aware of definitions and semantics 645associated with the mydomain namespace, it the consumer may safely assume that the resource 646is in the commonly known state identified by anyresource:Unavailable.

649This section defines capabilities applicable to manageable resources. The capabilities defined in 650this section complementIn addition to the capabilities defined in MUWS part Part 1, this document 651defines additional capabilities applicable to manageable resources..

6523.1 Description

653The manageability capability URI for this the description capability is 654http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Description

6553.1.1 Definition

656Figure 2 shows the a UML representation of the Description capability.

MUWS::Description MUWS::Description Caption[0..*] -Caption Description[0..*] -Description Version[0..1] -Version 657

658 Figure 2: MUWS Description

6593.1.2 Properties

660This capability defines the following properties: 661muws-p2-xs:LangString * 662muws-p2-xs:Caption contains a descriptive name for the manageable resource. being 663managed. The CCaption property is intended for human consumption. and A caption is expected 664to be short and is suitable for display next to a graphical icon. It Caption is a read-write, optional 665property that haswith a cardinality of 0 to many. Caption is of type muws-p2-xs:LangType, which 666is a restriction of xs:string carrying an xml:lang attribute. This attribute contains a language 667identifier as defined by [RFC3066]. There can not be more than one Caption perfor the same 668language identifier. 669Metadata for Caption: 670It is Mutable = True 671It is Modifiable = True 672Its Capability = is "hhttp://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Description”

673 674muws-p2-xs:LangString * 675muws-p2-xs:Description is a string containing a description for the resource being managed. 676The Description property is intended for human consumption. A description and is expected to be 677longer and more detailed than a Captioncaption. It Description is a read-write optional property 678that haswith a cardinality of 0 to many. Description is of type muws-p2-xs:LangType, which is a 679restriction of xs:string carrying an xml:lang attribute. This attribute contains a language identifier 55wd-wsdm-muws-part2-1.0 56Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 19 of 67 57 680as defined by [RFC3066]. There cannot be more than one Description for the sameper language 681identifier. 682Metadata for Description: 683It is Mutable = True 684It is Modifiable = True 685Its Capability = is "http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Description”

686 687 xs:string ? 688muws-p2-xs:Version is a string representing the version of the resource being managed. MUWS 689does not specify how this string is constructed. The version string can be specified by any 690domain-specific specification that uses MUWS. Version is a an optional property with a cardinality 691of 0 to1. 692Metadata for Version: 693It is Mutable = True 694It is Modifiable = True 695Its Capability = is "http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Description”

6963.2 State

697The manageability capability URI for this the State capability is 698http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/State

6993.2.1 Definition

700A resource may exhibit behavior according to one or more state models. The state capability 701provides a way in which theseto expose the states of a manageable resource are exposed. This 702is a pattern that can be applied to any type of state models that a resource can exhibitmight 703employ. The example used in this section is for themodels the operational states of a 704manageable resource. 705A single definition of an operational state model will not be sufficient for all types of resource., and 706tThise State capability is a means to allow different various state models to be used by 707differentamong manageable resources. To promote interoperability, it is a goal that there should 708be a very limited set of well defined state models. These state models themselves are not defined 709in the MUWSis specification. Each state model is identified by a URI, and the URI of the state 710model used by the resource is available exposed through via a some resource property. 711This capability does not define any specific property, operation or event. A manageability 712endpoint is said to provide this capability if the endpoint exposes at least one property exposes 713state information, and, that follows the pattern described in section 3.2.3.2 for exposing state 714information of the resource.

7153.2.2 Describing State Models

716Each state in a state-machine has a well-defined meaning. and Iit is possible to reuse state 717definitions in different state machines. States are identified by an element with a particular 718QName, using the taxonomy scheme defined in section 2.6. 719States in the state model may have duration. Transitions between states are considered to be 720instantaneous.

58wd-wsdm-muws-part2-1.0 59Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 20 of 67 60 721States can have sub-states that must MUST be wholly contained within a higher-level state. 722A state model may also define an operations that can be used to affect some of the transitions in 723the model. Note that a transitions may also occur as a result of some internal or external event on 724the resource. 725Each state machine has an associated resource property element that exposingprovides a read- 726only view of the current state of the state machine. Therefore, a client cannot change a resource 727state by modifying a state resource property. 728There may be more than one possible transition between two states in the state model. The 729individual transitions between states are identified by a URI to and allow, for example, to send a 730notifications of state transitions, or, to , for example, to identify which transition occurred. 731Figure 3 shows a simple state model that is used as an example in this section – it does not 732constitute the specification of a recommended state model.

Stopped stop() start()

Failed stop() Up

[failed]

734 Figure 3: Example Operational State Model

735In tThis example, the state machine is identified by URI 736http://example.com/StateModels/SimpleOperationalState, bound to namespace prefix exns. 737The state model has four states, represented by elements with a particular QName, as follows: 738  exns:Down 739 This QName corresponds to the “Down” state in the UML diagram. A resource in this 740 state is unable to perform any of its functional tasks. 741  exns:Stopped 742 This element QName corresponds to the “Stopped” sub-state of the “Down” state in the 743 UML diagram. Since this state is a sub-state of the “Down” state, it follows that aA 744 resource in the this "Stopped" sub-state is unable to perform any of its functional tasks 745 (since this state is a sub-state of the “Down” state). The A manageable resource 746 exposing this state model can be started from this statethe "Stopped" sub-state. 747  exns:Failed

61wd-wsdm-muws-part2-1.0 62Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 21 of 67 63 748 This element QName corresponds to the “Failed” sub-state of the Down state in the UML 749 diagram. Since this state is a sub-state of the “Down” state, it follows that aThe resource 750 has failed and (since this is a sub-state of the “Down” state) a resource in thisin the 751 "Failed" sub-state is unable to perform any of its functional tasks. The A manageable 752 resource exposing this state model can not be started directly from the “Failed” sub-state. 753 – itSuch a resource must first be movedtransition to the “Stopped” sub-state. 754  exns:Up 755 This QName corresponds to the “Up” state in the UML diagram. A resource in this state is 756 able to perform at least some of its functional tasks.

7573.2.3 Information Markup Declarations

7583.2.3.1 Representation of States

759A Sstate, ass in represented in a state model may be a top level state, or nested within another 760state,s in some defined taxonomy. MUWS defines a way to represent a type/category and its 761taxonomy lineage, but actual definition of the categories is resource management model specific 762and therefore not defined by MUWS. In other words, MUWS specifies only the mechanism to 763convey a type or /category in XML. The MUWS mechanism applied to states is defined as 764follows. 765StateType XML Schema type is declared as follows 766 767 768 769 770 771The StateType is used to declare XML elements which containing instances of states. 772The A states MUST be declared as follows:. 773  An XML element is declaring ed the which QName of which identifies the semantics of a 774 the state. 775  The XML element MUST be declared withhas an XML Schema type which is StateType, 776 or a restriction of StateType. 777  The contents of the XML element MUST be either: 778  The only one XML element which correspondings to the state that contains the 779 currently declared state. , iIn other words, the currently declaredthis state is a sub- 780 state of another state. 781  Or anThe empty sequence. , if This case occurs if this currently declared state is not 782 a sub-state of another state. 783For example, the “Failed” state in the example above is a sub-state of the “Down” state. An 784instance of the “Failed” state may be represented, using the rules described above, in by the 785following XML fragment by using the rules described above.: 786 787 788 789 790

792MUWS defines the following Global Element Declaration (GED) to represent an instance of a 793state: 794muws-p2-xs:StateType 795The State element provides a representation of the state of the a manageable resource. It The 796State element follows the convention for the muws-p2-xs:CategoryType type described in section 7972.6. which This convention allows the rendering of for a hierarchy of states and sub-states to be 798rendered. The state values are defined in the operational state model for the resource. This 799specification does not define the operational state model for any resource.

8003.2.3.3 Representation of last state transition

801MUWS defines the following Global Element Declaration (GED) to which contains an XML 802representation of the most recenta change of state in a state model. 803 805 muws-p2-xs:StateType 806 muws-p2-xs:StateType? 807 808 xs:anyURI 809 ? 810 {any} * 811 812muws-p2-xs:StateTransition is used for representing information about a state change. 813muws-p2-xs:StateTransitionChangeNotification/@Time attribute indicates the time at which 814the transition occurred (transitions are assumed to be instantaneous). It This attribute is 815REQUIRED. 816muws-p2-xs:StateTransition/@TransitionIdentifier attribute indicates the actual transition that 817occurred. This element is OPTIONAL and may be omitted where, for example, there is only one 818transition between the EnteredState and the PreviousState. 819muws-p2-xs:StateTransitionChangeNotification/muws-p2-xs:EnteredState element indicates 820which state has been entered during the transition. It This element is REQUIRED. 821muws-p2-xs:StateTransitionChangeNotification/muws-p2-xs:PreviousState element 822indicates the state that the resource was in immediately prior to the state change occurring. This 823element is OPTIONAL to allow for the time between the state model being created in some initial 824state (for example when the resource is created) and the time of the transition from that initial 825state. 826StateChangeNotification/TransitionIdentifier element indicates the actual transition that 827occurred. This element is optional and may be omitted where, for example, there is only one 828transition between the EnteredState and the PreviousState.

8293.2.4 Properties

830This capability does not define any property of its own. 831A capability that defines a state model should define a resource property through which the state 832is exposed, and it is recommended to also define a resource property for the last state transition.

67wd-wsdm-muws-part2-1.0 68Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 23 of 67 69 833The property used to expose the state must contain the muws-p2-xs:State complex element. The 834name of the property can be any name meaningful to the state model defined in the capability. 835There may be multiple state capabilities, and therefore multiple state properties for a resource. 836The metadata for this property should include the possible values, i.e. it provides a listing of the 837states that exist in the state model. 838The property to represent the last transition, if such a property is provided, must contain the 839complex element muws-p2-xs:StateTransition. The name of the last transition property can be 840any name meaningful to the state model. There may be multiple state capabilities and multiple 841properties showing the last transition.

8423.2.4.1 Example

843Examples of these resource properties for an operational state capability could be specified as 844follows: 845 846 ... 847 848 849 ... 850? 851The following fragment provides an example from a resource properties instance document 852containing the properties defined in this example: 853 854 855 856 857 858 Time=”2004-03-11T11:30:56Z”> 859 > 861 862 863 864 865 866 867 868 http://example.com/SimpleOperationalState/Transition/UpToFailed 869 870 871 872In this example, the foo:OperationalState property contains the current operational state of the 873resource, using the muws-p2-xs:State element defined in section 3.2.3.2. The 874foo:LastOperationalStateTransition property contains a description of the most recent operational 875state transition for the resource, using the muws-p2-xs:StateTransition element defined in section 8763.2.3.2.

8773.2.5 Operations

878A capability that defines a state model will usually define operations that can be used to cause 879some of the transitions within the state model. These operations are specific to the resource and 880its state model.

882It is recommended that resources send notifications on transitions between states. If they do 883then the notification message must contain at least the XML element for the new value of the 884state (muws-p2-xs:EnteredState). 885To obtain events about certain state transitions, subscribers can use a Selector on the notification 886subscription to select only those events which contain the required “muws-p2- 887xs:TransitionIdentifier” element or combination of “muws-p2-xs:EnteredState” and “muws-p2- 888xs:PreviousState” elements in the notification content. The Selector mechanism is described in 889[WSN]. 890To filter for events about entry into a particular state or set of states, a Selector expression based 891on the “muws-p2-xs:EnteredState” element can be used. To filter for events about exit from a 892particular state or set of states a Selector expression based on the “muws-p2-xs:PreviousState” 893element can be used.

8943.3 Operational Status

895The manageability capability URI for this capability is 896http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/OperationalStatus

8973.3.1 Definition

898The operational status capability defines a simple representation of the availability of the resource 899independent of the specific state model used. For this purpose an operational status property is 900defined which reflects whether the resource is available, unavailable or degraded. The status 901does not conform to a specific state model: each value may correspond to more than one state in 902the operational state model, and conversely more than one status value may correspond to a 903single state in the operational state model. 904Figure 4 shows the UML representation of the Operational Status capability.

MUWS:OperationalStatus MUWS:OperationalStatus OperationalStatus[1] -OperationalStatus 905

906 Figure 4: Operational Status

9073.3.2 Properties

908The resource state properties, or elements, are specified as follows: 909 910 Available|PartiallyAvailable|Unavailable|Unknown 911 912The following fragment provides an example from a resource properties instance document 913containing this property: 914Available 915The OperationalStatus property is of type OperationStatusType. The type is a restriction of 916xs:string that gives a simple indication of the availability of the resource, independent of the 917potentially complex operational state model. This property is read-only, mutable and mandatory 918with a cardinality of 1. The valid values are:

73wd-wsdm-muws-part2-1.0 74Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 25 of 67 75 919  Available: This value indicates that the resource is operating normally within any 920 configured operating parameters, and is able to perform all of its functional tasks. 921  PartiallyAvailable: This value indicates that the resource is operating, but it is outside 922 normal operating parameters. A resource with this operational status is able to perform 923 some, but not all, of its functional tasks. The resource may, for example, be in the 924 process of starting, or lacking resources. 925  Unavailable: This value indicates that the resource is not operating, and is not able to 926 perform any of its functional tasks. The resource may have been stopped, or may have 927 failed. 928  Unknown: This value indicates that the resource is unable to report its status at this time. 929Metadata for OperationalStatus: 930It is Mutable = True 931It is not Modifiable = False 932Its Capability = is "http://docs.oasis- 933open.org/wsdm/2004/12/muws/capabilities/OperationalStatus”

9343.4 Metrics

935The manageability capability URI for this capability is 936http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Metrics

9373.4.1 Definition

938Metrics are a specific type of property. Metrics represent collected values and have a related 939collection period. 940The goal of this section is to describe the characteristics of a typical property used to represent 941collected numerical data, called Metrics. A common characteristic of metrics is that they change 942over time. 943Figure 5 presents the Metrics capability in context.

MUWS::Metrics MUWS::Metrics CurrentTime[1] -CurrentTime 944

945 Figure 5: MUWS metrics

946As a simple example, consider a toll bridge with two properties; the length of the bridge and the 947number of cars that have passed over the bridge. The length of the bridge, while numeric is not a 948metric; it represents the current configuration of the bridge. You can not reset the length of the 949bridge. By contrast, the number of cars that have passed over the bridge is a metric. It requires 950collecting, counting, or measuring the number of cars typically for some duration of time, such as 951the last hour, the last day or even since the bridge was constructed. You can reset the number of 952cars, for example, at the start of a new interval.

954The following schema fragment declares the (reusable) data type used to expose the metrics of 955the resource. All attributes defined in the MetricAttributes attribute group are optional. 956 957 958

76wd-wsdm-muws-part2-1.0 77Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 26 of 67 78 959 960 961(MetricAttributes) attribute group MUST be included in every metric type or metric property 962element declaration. 963(MetricAttributes)/ResetAt indicates the time when a particular metric was reset. If a reset 964capability is supported for the metric, this attribute MUST be included with the metric property. If 965this metric can not be reset or a reset capability is not supported, this attribute MUST NOT be 966present. Properties having a TimeScope of PointInTime MUST NOT include this attribute. If the 967attribute value does not include a time zone indication (or Z for UTC), the value MUST be 968interpreted as UTC. 969(MetricAttributes)/LastUpdated indicates the last update time of a metric value. If the value 970does not include a time zone indication (or Z for UTC), the value MUST be interpreted as UTC. 971(MetricAttributes)/Duration indicates the time over which the metric value was collected, 972counted, or measured. The Duration attribute MUST be included for metrics having a TimeScope 973of Interval or SinceReset, and MUST NOT be included for metrics having a TimeScope of 974PointInTime. 975The following metric type definition is an example of how the metrics attributes are incorporated 976into a metric type. All metric types MUST incorporate the MetricAttributes attribute group. 977 978 979 980 981 982 983 984 985The following shows an example instance of this example metric type. 986 989 12345 990

9913.4.3 Metadata

992The following metadata is applicable to all properties that are metrics: 993They are Mutable = True 994They are not Modifiable = False 995Their Capability = is "http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Metrics" 996Other metadata elements applicable for metrics are : Units, ChangeType, TimeScope, 997GatheringTime, CalculationInterval. See section 2.3.2 for a description of these metadata 998elements.The following metadata elements are defined for metric-type properties : 999Counter|Gauge|Unknown 1000muws-p2-xs:ChangeType is an enumeration for indicating how changes to the associated 1001metric value should be interpreted by the consumer. A property representing a metric MUST 1002include a single instance of ChangeType in its metadata description. Each ChangeType value is 1003interpreted as follows:

79wd-wsdm-muws-part2-1.0 80Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 27 of 67 81 1004  Counter - the value of the metric increments over successive counts, collections, or 1005 measurements. 1006  Gauge - the value of the metric varies between a range of values. 1007  Unknown - the change behavior is not known or cannot be described. 1008 1009Interval|PointInTime|SinceReset 1010muws-p2-xs:TimeScope is an enumeration for indicating if there is some interval, over which the 1011data is collected, counted, or measured. A property that is a metric MUST include a single 1012instance of TimeScope in its metadata description. Each TimeScope value is interpreted as 1013follows: 1014  Interval - the value of the metric is collected over some time interval. In this case the 1015 Duration attribute MUST be reported with the metric property. The value of the Duration 1016 attribute is the time, from the beginning of the interval, to the end of the interval. The 1017 Duration is usually remains the same for every reading of the metric. 1018  PointInTime - the value of the metric is counted, collected, or measured at a single 1019 instant in time. The Duration attribute MUST NOT be reported with metrics having a 1020 TimeScope value of PointInTime. Metrics with a TimeScope value of PointInTime do not 1021 support the reset capability and MUST NOT include the ResetAt attribute. 1022  SinceReset - the value of the metric is collected since reset, or since the manageable 1023 resource started collecting metrics data. In this case the Duration attribute MUST be 1024 reported with the metric property. The value of the Duration attribute is the time since the 1025 metric was reset, or since the resource started collecting metrics data, if no reset has 1026 occurred. Thus the value of Duration may report a different value for each retrieval of the 1027 property. 1028 1029 1030 OnChange|Periodic|OnDemand|Unknown 1031 1032muws-p2-xs:GatheringTime is an enumeration indicating at what times the value of the metric is 1033counted, collected, or measured. A property that is a metric MUST include a single instance of 1034GatheringTime in its metadata description. Each GatheringTime value is interpreted as follows: 1035  OnChange - the value of the metric is updated whenever a change occurs to the quantity 1036 measured. 1037  Periodic - the value of the metric is updated on a regular basis. 1038  OnDemand - the value of the metric is updated when there is a request for the metric 1039 value. 1040  Unknown - it is unknown when the metric value is updated. 1041 1042xs:duration 1043muws-xs-p2:CalculationInterval represents the interval at which the metric is gathered or 1044calculated by the resource. The value of the metric is not updated during a calculation interval. 1045 1046xs:anyURI 1047muws-p2-xs:MetricGroup indicates that the metric property is a member of a group of metrics. 1048A metric property MAY be a member of zero or more metric groups. A metric group is identified 1049by a URI. Each property included in a metric group SHALL have a MetricGroup element 1050containing an identical URI. A property that is a metric MUST include zero or more MetricGroup

82wd-wsdm-muws-part2-1.0 83Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 28 of 67 84 1051elements in its metadata description. Each MetricGroup element represents a membership in a 1052metric group.

10533.4.4 Properties

1054The following provides the specification of a resource metrics property. 1055xs:dateTime 1056Muws-p2-xs:CurrentTime contains the time the property was retrieved from the manageable 1057resource. This property is useful to manageability consumers when analyzing time values 1058received from a manageability endpoint in the absence of a time synchronization mechanism. It is 1059a read-only mandatory property that has a resource cardinality of 1. 1060The Metrics capability requires the CurrentTime property to be present in the resource properties, 1061and provides a reference point for time-based attributes as defined by metric data types. Note 1062that CurrentTime is not a metric. Rather, it is a property of type xs:dateTime defined as part of the 1063“Metrics” capability, consequently, reset operations, if any, have no effect on CurrentTime.

10643.4.5 Events

1065No specific notification topics are defined by the Metrics capability. WS-ResourceProperties 1066specifies the ability to optionally define topics for resource properties that can emit notifications 1067when their value changes. These topics allow a client to request notifications for the update of 1068individual metrics properties 1069This document defines notification topics for every manageability capability. Subscribing to the 1070topic for a resource-specific metrics manageability capability allows a client to receive all 1071notifications associated with that manageability capability, including property value change 1072notifications.

10733.5 Configuration

1074The manageability capability URI for this capability is 1075http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Configuration

10763.5.1 Definition

1077Configuration properties are those whose values impact the behavior of the resource. 1078Configuration property values may be changed directly by a set or changed as a side effect of 1079another operation.

1082Section 3 (Capabilities applicable to manageable resources) contains, when merged with the 1083capabilities defined in [MUWS Part 1], the list of manageability capabilities defined by MUWS. 1084This section (section 4, Capabilities applicable to management in general) contains management- 1085related capabilities, which are different from manageability capabilities. A manageability capability 1086is offered by a manageability representation and applies to the resource represented by the 1087manageability representation. A management-related capability can be offered by any Web 1088service, not only manageability endpoints. Its function is related to the field of management, but 1089not necessarily to the direct management of a resource through its manageability endpoint. For 1090example, the capability to help a manager discover new manageable resources can be provided 1091by a registry and not necessarily a management representation of a specific resource.

10924.1 Relationships

1093The manageability capability URI for this capability is 1094http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Relationships

1096A relationship is an N-ary association between resources. A relationship may have properties and 1097other characteristics. One of these properties is a type that conveys the semantic of the 1098relationship. The resources involved in the relationship are called participants. Each participant 1099has a role in the relationship. The participants may or may not be manageable resources in the 1100MUWS sense. The notion of “direction” of a relationship is a semantic interpretation based on role 1101definitions. There could be many instances of relationships between many instances of 1102resources. The arrows in Figure 6 depict navigability, which means that by following the arrow 1103one could resolve what the end points to (reference).

1105 Figure 6: Relationship conceptual model

1106Note that this capability is not limited to manageable resources and can be exposed by any 1107resource that wants to expose relationships that it knows about. 1108Figure 7 is a UML representation of the relationship capability.

88wd-wsdm-muws-part2-1.0 89Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 30 of 67 90 MUWS::Relationship MUWS::Relationship Relationship[1] -Relationship <> RelationshipCreated[0..1] -<> RelationshipCreated <> RelationshipDeleted[0..1] -<> RelationshipDeleted 1109 QueryRelationshipsByType () +QueryRelationshipsByType()

1110 Figure 7: Relationship capability

1111 There is an assumption that the resources are well behaved and creating relationships in good 1112 faith. Relationships may also be out of date. Before relationships are relied upon, they should be 1113 validated either manually or automatically. It should also be considered if the resource being 1114 related should be visible for security reasons.

11164.1.2.1 Representation of Categories of Relationships

1117Relationships could be categorized. That is each relationship is of certain type/category which 1118describes the semantics of the relationship. One type/category may be a specialization or 1119generalization of another type/category. This defines taxonomy of relationship categories. WSDM 1120defines a way to represent a type/category and its taxonomy lineage, but actual definition of the 1121categories is resource management model specific and therefore not defined by WSDM. In other 1122words, WSDM specifies only the mechanism to convey a type/category in XML. The WSDM 1123mechanism applied to relationship types/categories is defined as follows. 1124RelationshipTypeType XML Schema type is declared as follows 1125 1126 1127 1128 1129 1130The RelationshipType is used to declare XML elements which contain instances of relationship 1131type/category information. 1132The relationship type/category information MUST be declared as follows. 1133  An XML element is declared which QName identifies the semantics of a relationship 1134 type/category. 1135  The XML element MUST be declared with the XML Schema type which is a restriction of 1136 RelationshipType. 1137  The contents of the XML element MUST be either 1138  The only one XML element which corresponds to the generalization of the currently 1139 declared relationship type/category 1140  Or empty sequence, if currently declared relationship type/category does not have 1141 any generalizations (top of the taxonomy). 1142For example, the “USB attached” relationship type/category may be generalized to the “Bus 1143connected” which, in turn, may be generalized to the “Generally linked”. An instance of the “USB 1144attached” relationship type/category information may be represented in the following XML 1145fragment by using the rules described above. 1146

11534.1.2.2 Representation of an Instance of a Relationship

1154MUWS defines the following Global Element Declaration (GED) to represent an instance of a 1155relationship. 1156 1157 xs:string ? 1158 muws-p2-xs:RelationshipTypeType 1159 1160 xs:anyURI 1161 * 1162 ? 1163 xs:anyURI 1164 {any} * 1165 1166 + 1167 1168 wsa:EndpointReferenceType 1169 ? 1170 {any} * 1171 1172muws-p2-xs:Relationship/muws-p2-xs:Name is a human readable name of the relationship. 1173Name should not be used for machine reasoning about the semantics of the relationship. Type 1174should be used instead. This element is OPTIONAL. 1175muws-p2-xs:Relationship/muws-p2-xs:Type is a type/category which this relationship belongs 1176to. Such as linkage, containment, dependency, etc. MUWS does not define any specific 1177relationship type. This is left to domain-specific models. MUWS only defines a way to convey the 1178type as part of the representation of a relationship. In order to allow relationships to be defined as 1179part of a taxonomy, the mechanism used by MUWS to represent relationship types leverages the 1180muws-muws-p2-xs:CategoryType type defined in section 2.6. This element is REQUIRED. 1181muws-p2-xs:Relationship/muws-p2-xs:Participant contains information about the participant 1182in the relationship. There MUST be at least two participants, but MAY be more. 1183muws-p2-xs:Relationship/Participant/Role is a URI which identifies the role that the participant 1184plays in the relationship. A participant role MUST be unique within a given instance of the 1185relationship. The set of valid roles is defined by the relationship type. This attribute is REQUIRED. 1186Relationship/muws-p2-xs:Participant/muws-p1-xs:ManageabilityEndpointReference is a 1187reference to a WSDM manageability endpoint. This GED is defined in part 1. It MAY be included 1188if the participant is WSDM manageable and the provider of this information knows and wishes to 1189indicate that. If more than one manageability endpoint is known, more than one instances of this 1190element may be present. 1191muws-p2-xs:Relationship/muws-p2-xs:Participant/muws-p1-xs:ResourceID is a WSDM 1192manageable resource identifier which MAY be reported by the provider of the relationship 1193information. This GED is defined in part 1. This information may be used to locate manageability 1194endpoints for this participant or may be used for other purposes. For example, the resource 1195identifier SHOULD be used to express that the provider of the relationship information is also a 1196participant of the relationship (by returning its own resource identifier for one of the participants).

94wd-wsdm-muws-part2-1.0 95Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 32 of 67 96 1197Obviously, in order for this assertion to work, the provider of the relationship information has to be 1198a WSDM manageable resource. 1199muws-p2-xs:Relationship/muws-p2-xs:Participant/muws-p2-xs:Role is a URI which identifies 1200the role that the participant plays in the relationship. A participant role MUST be unique within a 1201given instance of the relationship. The set of valid roles is defined by the relationship type. This 1202attribute is REQUIRED. 1203muws-p2-xs:Relationship/muws-p2-xs:Participant/{any}* is an XML extensibility content 1204which MAY contain elements that further or otherwise describe the participant. For example, 1205when a participant is a Web service endpoint, an EndpointReference element as defined by 1206MOWS MAY be included in the extensibility content to indicate reference to the 1207functional/operational Web service endpoint participant of the relationship. 1208muws-p2-xs:Relationship/muws-p2-xs:AccessEndpoint is a reference to the Web service 1209endpoint which provides access to this relationship (if available). The endpoint MUST implement 1210the relationship access capability (see section 4.2). 1211Following is an example of a relationship information instance. The relationship is that a WSDM 1212manageable network host myhost.myorg.org contains an attached SCSI disk which is not 1213manageable by itself, but is exposed as a functional/operational Web service endpoint (e.g. to 1214read/write from the disk). The “containment” is represented by the relationship below: 1215 1216 SCSI disk attached to the host computer 1217 1218 1219 1220 1221 1222 1223 1224 1225 urn:role:bus:host 1226 1227 ...EPR1... 1228 1229 urn:uuid:123 1230 urn:role:bus:host 1231 myhost.myorg.org 1232 1233 1234 urn:role:bus:device 1235 2 1236 0 1237 5 1238 0 1239 1240 ...EPR2... 1241 1242 1243

1245This capability defines the following property: 1246 *

97wd-wsdm-muws-part2-1.0 98Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 33 of 67 99 1247muws-p2-xs:Relationship is a representation of a relationship of which provider of this capability 1248is aware. See section 4.1.2 for the definition of the Relationship element. The provider of this 1249capability is not necessarily a participant in the relationships represented by this property. 1250It is not recommended to request all values of the Relationship property with either 1251wsrp:GetResourceProperty or wsrp:GetMultipleResourceProperties operations as there may be 1252too many relationships. It is RECOMMENDED to use wsrp:QueryResourceProperties operation 1253when retrieving the Relationships property. Provider of this manageability capability SHOULD, in 1254general, support wsrp:QueryResourceProperties operation. However, if the provider of this 1255capability knows of just a few relationships, it MAY choose not to support 1256wsrp:QueryResourceProperties operation. 1257For example, the following request may be sent to retrieve all “Bus connected” relationships 1258which point to devices exposed as Web services. 1259 1260 1261 ... 1262 1263 1264 1265 1267boolean(/*/muws-p2-xs:Relationship/muws-p2-xs:Type/*/bus:Connected and 1268/*/muws-p2-xs:Relationship/muws-p2- 1269xs:Participant[Role=”urn:role:bus:device”]/mows-xs:EndpointReference) 1270 1271 1272 1273

12744.1.4 Operations

1275This capability defines the following message exchanges.

12764.1.4.1 QueryRelationshipsByType

1277This operation is optional and is a shortcut to query the relationships of the same type. The 1278request to perform this operation has the following payload: 1279 1280 muws-p2-xs:RelationshipTypeType + 1281 1282muws-p2-xs:QueryRelationshipsByType is a Global Element Declaration (GED) which 1283identifies the operation requested. 1284muws-p2-xs:QueryRelationshipsByType/muws-p2-xs:Type is a category which the 1285relationship belongs to. Such as containment, dependency, etc. The actual markup of the value of 1286this element is described in section 4.1.2.2. 1287The response to the above request is either a fault (any fault) or the following message. 1288 1289 * 1290 1291muws-p2-xs:QueryRelationshipsByTypeResponse is a GED which identifies response to the 1292requested operation.

100wd-wsdm-muws-part2-1.0 101Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 34 of 67 102 1293muws-p2-xs:QueryRelationshipByTypeResponse/muws-p2-xs:Relationship is a relationship 1294representation matching one of the requested types (categories). See section 4.1.2.2 for the 1295definition of the relationship element.

12964.1.5 Events

1297To obtain notifications of changes in relationships, the following notification topics are defined in 1298the manageable relationships capability. 1299 1301 1303 //muws-p1- 1305xs:ManagementEvent[count(muws-p2-xs:RelationshipCreatedNotification)=1] 1306 1307 1308 1310 //muws-p1- 1312xs:ManagementEvent[count(muws-p2-xs:RelationshipDeletedNotification)=1] 1313 1314 1315 1316muws-events:ManageableRelationships/muws-events:RelationshipCreated indicates 1317addition of a new relationship. It is recommended to subscribe to this notification with appropriate 1318selector against the contents of the notification message to reduce the notification message 1319volume. The notification message contains at least the following information. 1320 1321 1322 1323muws-events:ManageableRelationships/muws-events:RelationshipDeleted indicates 1324removal of an existing relationship. It is recommended to subscribe to this notification with 1325appropriate selector against the contents of the notification message to reduce the notification 1326message volume. The notification message contains at least the following information. 1327 1328 1329

13304.2 Relationship Access Capability

1331The manageability capability URI for this capability is 1332http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/RelationshipAccess

1334The capability to access a relationship is defined here. The provider of the Web service endpoint 1335that supports this capability also provides access to the relationship. If this capability is supported, 1336the endpoint reference for the service implementing it MUST contain sufficient information to 1337allow the provider of this capability to disambiguate which relationship is being accessed by the 1338message exchanges. The endpoint reference could be obtained from the 1339Relationship/acccessEndpointReference in relationship element defined in section 4.1.2.2.

103wd-wsdm-muws-part2-1.0 104Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 35 of 67 105 1340In general, this capability is not more specific than what is described above. That is, an endpoint 1341MAY support any message exchanges it needs to provide access to the relationship. The 1342message exchanges may entirely be management model specific. 1343The only other normative requirement is that if the relationship lifecycle is to be exposed by the 1344provider of this capability, then the Web service endpoint MUST implement WS-ResourceLifetime 1345specification [WS-RL].

13464.3 Relationship Resource Capability

1347The manageability capability URI for this capability is 1348http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/RelationshipResource

1350A Web service endpoint, in addition to providing access to the relationship as described in section 13514.2, may also represent the relationship. Representing the relationship means that an endpoint is 1352able to provide relationship information as described in section 4.1.2.2. In this case, the Web 1353service endpoint MUST be a WS-Resource, as defined by the WSRF, and one such WS- 1354Resource provides information about one relationship instance. Representing relationships as 1355WS-Resources is useful when a manageability model defines additional properties, operations 1356and/or events for a given relationship. 1357In order to represent a relationship as a WS-Resource, a set of properties is normatively required. 1358The rest is up to the relationship manageability model and the discretion of the provider of the 1359WS-Resource and the relationship. 1360Figure 8 is a UML representation of the Relationship Resource capability.

MUWS::RelationshipResource MUWS::RelationshipResource MUWS::Participant Name[0..1] -Name -Role Type[1] -Type -ManageabilityEndpointReference Participant[2..*] -Participant -ResourceId 1361

1362 Figure 8: Relationship Resource capability

1364This capability defines the following properties. 1365xs:string ? 1366muws-p2-xs:Name is an element as defined by the Relationship/Name in section 4.1.2.2. It is 1367optional.

1368 1369muws-p2-xs:RelationshipTypeType 1370muws-p2-xs:Type is an element as defined by the Relationship/Type in section 4.1.2.2. It is 1371required and can only appear once.

1372 1373 1374 xs:anyURI 1375 *

106wd-wsdm-muws-part2-1.0 107Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 36 of 67 108 1376 ? 1377 xs:anyURI 1378 {any} * 1379 1380muws-p2-xs:Participant is an element as defined by the Relationship/Participant in section 13814.1.2.2. It appears at least twice (one per participant in the relationship).

13824.4 Advertisement

1383The manageability capability URI for this capability is 1384http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Advertisement

1386The “advertisement” capability is exposed by Web services that are able to provide notification on 1387creation and/or destruction of manageable resources. Since one cannot register for notification on 1388a resource before the resource is created, the creation events reported by the implementer of the 1389“lifetime notification” capability necessarily apply to other resources than those represented by the 1390Web service on which the registration was done. 1391Note that this capability is not only implementable by manageable resources (see the distinction 1392between “manageability capability” and “management-related capability” in section 4). A service 1393might offer the capability to notify on creation/destruction of resources even though the service 1394itself is not manageable. For example, if a system included a registry to which resources are 1395added as soon as they are created and from which they are removed when they are destroyed, 1396this registry could expose the “advertisement” capability and use it to share the information about 1397resource creation/destruction with managers. 1398This capability does not define any property or operation, but it defines four topics used for 1399notification. 1400An example of use of this capability would be for a container (e.g. a J2EE server, a business 1401process execution engine, etc) to expose it to advertise the fact that it can notify a manager when 1402a resource (in this example a resource contained by the container) is created. 1403Figure 9 is a UML representation of the Advertisement capability.

MUWS::Advertisement MUWS::Advertisement <> ManageabilityEndpointCreation[0..1] -<> ManageabilityEndpointCreation <> ManageableResourceCreation[0..1] -<> ManageableResourceCreation <> ManageabilityEndpointDestruction[0..1] -<> ManageabilityEndpointDestruction <> ManageableResourceDestruction[0..1] -<> ManageableResourceDestruction 1404

1405 Figure 9: Advertisement capability

14064.4.2 Events

1407This capability defines a topic space containing four notification topics: 1408 1411 1413

109wd-wsdm-muws-part2-1.0 110Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 37 of 67 111 1414 Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116">//muws-p1- 1415xs:ManagementEvent[count(muws-p2-xs:CreationNotification)=1] 1416 1417 1419 //muws-p1- 1421xs:ManagementEvent[count(muws-p2-xs:CreationNotification)=1] 1422 1423 1424 1425 1427 //muws-p1- 1429xs:ManagementEvent[count(muws-p2-xs:DestructionNotification)=1] 1430 1431 1433 //muws-p1- 1435xs:ManagementEvent[count(muws-p2-xs:DestructionNotification)=1] 1436 1437 1438 1439 1440The “muws-events:ManageabilityEndpointCreation” topic corresponds to notification on 1441creation of a new manageability endpoint for a resource. This could be because the resource was 1442just created along with a manageability endpoint or the resource itself could have been creating 1443some time in the past. In this case, this notification means that a new manageability endpoint for 1444the resource was created. This new manageability endpoint could be the first one for the resource 1445or be in addition to existing ones. The associated muws-p2-xs:CreationNotification message 1446contains the EPR of the newly created manageability endpoint. 1447The “muws-events:ManageableResourceCreation” topic is a specialization of the 1448“Manageability EndpointCreation” topic. This topic corresponds to the case where the resource 1449itself is newly created. Note that if a resource is created that is not manageable (i.e. which does 1450not have a manageability endpoint) no notification on this topic will be returned. But if, along with 1451the resource being created, a manageability endpoint for the resource is created then a 1452notification will be sent to subscribers on this topic. 1453The “muws-events:ManageabilityEndpointDestruction” topic corresponds to notification on 1454destruction of a manageability endpoint. It does not imply that the associated resource was 1455destroyed. The associated muws-p2-xs:DestructionNotification message contains the muws-p2- 1456xs:ResourceId that the newly destroyed manageability endpoint was providing for the resource 1457before being destroyed. 1458The “muws-events:ManageableResourceDestruction” topic is a specialization of the 1459“ManageabilityEndpointDestruction” topic. This topic corresponds to the case where the resource 1460itself is being destroyed at the same time as the manageability endpoint. Note that if a resource is 1461being destroyed that was not manageable (that didn’t have a manageability endpoint) no 1462notification on this topic will be sent. The associated muws-p2-xs:DestructionNotification 1463message contains the muws-p2-xs:ResourceId that the newly destroyed manageability endpoint 1464was providing for the resource before being destroyed. 1465The content elements for these topics are so described: 1466 1467 *

112wd-wsdm-muws-part2-1.0 113Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 38 of 67 114 1468 1469Muws-p2-xs:CreationNotification/muws-p1-xs:ManageabilityEndpointReference is a 1470reference to the manageability endpoint of the newly created resource. There can be more than 1471one such reference if there is more than one known manageability endpoint.

1472 1473 1474 ? 1475 1476Muws-p2-xs:DestructionNotification/muws-p1-xs:ResourceId is the ResourceId of the newly 1477destroyed resource.

1480Many forms of discovery are supported by Web services. This specification does not prescribe a 1481normative method for discovering manageability services. It is expected that discovery methods 1482commonly used for Web services will be used as discovery methods for manageability services. 1483The goal of discovery is to obtain the EPR of a manageability endpoint. The Advertisement 1484capability (section 4.4), when supported, provides ways to facilitate discovery. This section also 1485describe two other ways to discover manageable resources. These are just some of the discovery 1486methods that can be used. 1487There exists but one normative requirement relative to discovering manageability services, as 1488follows: A manageability service MUST provide the Identity capability as defined by MUWS. As a 1489result of this requirement, a consumer can inspect the WSDL description for a Web service or 1490attempt to use the Identity capability of the Web service and determine if the discovered service 1491acts as a manageability service. If the discovered service provides the Identity capability defined 1492by MUWS, then it is a manageability service.

14935.1 Discovery using Relationships

1494There are at least two scenarios in which relationships are used in discovering manageable 1495resources. 1496One approach is when manageable resources point to other manageable resources throught 1497relationships: manageable resources that support the Relationship capability enable discovery of 1498the EPRs of manageable resources that are participants in the relationship. This is done by using 1499the “Relationship” property defined in section 4.1.3 or invoking the operations defined in section 15004.1.4 that may provide as part of the response message EPRs of other resources. 1501The second scenario is when the consumer has access to WS-Resources representing 1502relationships and these relationships have manageable resources as members. The consumer 1503can then use the properties of the Relationship Resource capability to retrieve the EPRs of the 1504member manageable resources.

15055.2 Discovery using Registries

1506In addition to emitting the notifications on creation and destruction defined as part of the 1507Advertisement capability (section 4.4), resources can be advertised actively to specific registries 1508by invoking a registration interface. They can then be discovered by consumers invoking the 1509query interface of these registries. 1510The WSRF WS-Service Group specification [WS-SG] defines a type of registry, along with the 1511message exchanges used to interact with registries of this type. It is RECOMMENDED that 1512registries used to discover manageable resources conform to the WS-Service Group specification 1513and to the following additional constraints: 1514The service group SHOULD include as properties the following two elements: 1515 1518

118wd-wsdm-muws-part2-1.0 119Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 40 of 67 120 1521The service group MAY also have any other “MembershipContentRule”, including the rule with an 1522empty value for both MemberInterface and ContentElements, in effect lifting any constraint on the 1523members of the service group. The two membership content rules defined above are useful even 1524in a service group with no effective constraint because they allow querying the service group on 1525the “ResourceId” and “ManageabilityCapability” properties. 1526When adding a manageability endpoint for a resource to the membership of a service group using 1527the “Add” operation, the requestor SHOULD include the muws-p1-xs:ResourceId element of the 1528manageable resource in the wssg:Add/wssg:Content element of the request, even if the service 1529group supports additional membership content rules that would have permitted registration of the 1530manageability endpoint in the service group without providing this content element. Similarly, if 1531the manageable resource supports the Manageability Characteristics capability, the requestor 1532SHOULD include all the muws-p1-xs:ManageabilityCapability elements of the manageable 1533resource in the wssg:Add/wssg:Content element of the request, even if the service group 1534supports additional membership content rules that would have permitted registration of the 1535manageability endpoint in the service group without providing this content element 1536Like all manageability endpoints, the manageability endpoints registered in a resource registry 1537MUST implement the Identity capability defined in [MUWS Part 1]. In addition, in order to facilitate 1538discovery, they SHOULD implement the Manageability Characteristics capability also defined in 1539[MUWS Part 1].

15426.1 Normative 1543 [MUWS Part 1] William Vambenepe, Web Services Distributed 1544 Management:Management using Web Services (MUWS 1.0) Part 1, 1545 OASIS Committee Draft, December 2004, http://docs.oasis- 1546 open.org/wsdm/2004/12/cd-wsdm-muws-part1-1.0.pdf 1547 1548 [XML1.0 3rd Edition] 1549 Tim Bray, et al., Extensible Markup Language (XML) 1.0 (Third Edition), 1550 W3C Recommendation, February 2004, http://www.w3.org/TR/REC-xml 1551 1552 [XML Schema Part 1] 1553 Henry S. Thompson, et al. XML Schema Part 1: Structures, W3C 1554 Recommendation, May 2001, http://www.w3.org/TR/xmlschema-1/ 1555 1556 [XML Schema Part 2] 1557 Paul V. Biron, et al. XML Schema Part 2: Datatypes, W3C 1558 Recommendation, May 2001, http://www.w3.org/TR/xmlschema-2/ 1559 1560 [WSDL1.1] Erik Christensen, et al., Web services Description Language (WSDL) 1.1, 1561 W3C Note, March 2001, http://www.w3.org/TR/wsdl 1562 1563 [WS-Resource] Steve Graham, et al. Web Service Resource 1.2 (WS-Resource), OASIS 1564 Working Draft, October 2004, http://www.oasis- 1565 open.org/apps/org/workgroup/wsrf/download.php/9547/wsrf-WS- 1566 Resource-1.2-draft-01.doc 1567 1568 [WS-Addressing] Don Box, et al., Web services Addressing (WS-Addressing), W3C 1569 Member Submission, August 2004, 1570 http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/ 1571 1572 [WS-RP] Steve Graham, et al., Web Services Resource Properties 1.2 (WS- 1573 ResourceProperties), OASIS Working Draft, June 2004, 1574 http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties- 1575 1.2-draft-04.pdf 1576 1577 [XPath 1.0] James Clark, et al., XML Path Language (XPath) Version 1.0, W3C 1578 Recommendation, November 1999, http://www.w3.org/TR/1999/REC- 1579 xpath-19991116 1580

124wd-wsdm-muws-part2-1.0 125Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 42 of 67 126 1581 [WSN] Steve Graham, et al., Web Services Base Notification 1.2 (WS- 1582 BaseNotification), OASIS Working Draft, June 2004, http://docs.oasis- 1583 open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-03.pdf 1584 1585 [WST] William Vambenepe, Web Services Topics 1.2 (WS-Topics), OASIS 1586 Working Draft, Jully 2004, http://docs.oasis-open.org/wsn/2004/06/wsn- 1587 WS-Topics-1.2-draft-01.pdf 1588 1589 [RFC3066] IETF (Internet Engineering Task Force). RFC 3066: Tags for the 1590 Identification of Languages, ed. H. Alvestrand. 2001, 1591 http://www.ietf.org/rfc/rfc3066.txt 1592 1593 [WS-RL] Latha Srinivasan, et al., Web Services Resource Lifetime 1.2 (WS- 1594 ResourceLifetime), OASIS Working Draft, June 2004, http://docs.oasis- 1595 open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-03.pdf 1596 1597 [WS-SG] Tom Maguire, et al., Web Services Service Group 1.2 (WS- 1598 ServiceGroup), OASIS Working Draft, June 2004, http://docs.oasis- 1599 open.org/wsrf/2004/06/wsrf-WS-ServiceGroup-1.2-draft-02.pdf 1600

16016.2 Non-normative 1602 [WS-RF] WSRF OASIS technical committee, http://www.oasis- 1603 open.org/committees/tc_home.php?wg_abbrev=wsrf 1604 1605 [WSRMD] Steve Graham, et al., Web Services Resource Metadata 1.0 (WS- 1606 ResourceMetadataDescriptor), OASIS Working Draft, October 2004, 1607 http://www.oasis-open.org/committees/download.php/9758/wsrf-WS- 1608 ResourceMetadataDescriptor-1.0-draft-01.PDF 1609

1611The following individuals were members of the committee when the specification was approved 1612by the technical committee 1613Guru Bhat, Jeff Bohren, Winston Bumpus, Nick Butler, Brian Carroll, Fred Carter, Michael 1614Clements, David Cox, John DeCarlo, Andreas Dharmawan, Mark Ellison, John Fuller, Paul 1615Lipton, Heather Kreger, Hal Lockhart, Frederico Maciel, Tom Maguire, Bryan Murray, Richard 1616Nikula, Mark Peel, Richard Pelavin, Homayoun Pourheidari, Warren Roberts, Karl Schopmeyer, 1617Igor Sedukhin, David Snelling, Thomas Studwell, William Vambenepe, Andrea Westerinen, Jim 1618Willits, Zhili Zhang.

1620OASIS takes no position regarding the validity or scope of any intellectual property or other rights 1621that might be claimed to pertain to the implementation or use of the technology described in this 1622document or the extent to which any license under such rights might or might not be available; 1623neither does it represent that it has made any effort to identify any such rights. Information on 1624OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS 1625website. Copies of claims of rights made available for publication and any assurances of licenses 1626to be made available, or the result of an attempt made to obtain a general license or permission 1627for the use of such proprietary rights by implementors or users of this specification, can be 1628obtained from the OASIS Executive Director. 1629OASIS invites any interested party to bring to its attention any copyrights, patents or patent 1630applications, or other proprietary rights which may cover technology that may be required to 1631implement this specification. Please address the information to the OASIS Executive Director. 1632Copyright © OASIS Open 2003-2004. All Rights Reserved. 1633This document and translations of it may be copied and furnished to others, and derivative works 1634that comment on or otherwise explain it or assist in its implementation may be prepared, copied, 1635published and distributed, in whole or in part, without restriction of any kind, provided that the 1636above copyright notice and this paragraph are included on all such copies and derivative works. 1637However, this document itself does not be modified in any way, such as by removing the 1638copyright notice or references to OASIS, except as needed for the purpose of developing OASIS 1639specifications, in which case the procedures for copyrights defined in the OASIS Intellectual 1640Property Rights document must be followed, or as required to translate it into languages other 1641than English. 1642The limited permissions granted above are perpetual and will not be revoked by OASIS or its 1643successors or assigns. 1644This document and the information contained herein is provided on an “AS IS” basis and OASIS 1645DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO 1646ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE 1647ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1648PARTICULAR PURPOSE.

1649 1650 1651 1652 1653

1655 1656 1666 1667 1674 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713

136wd-wsdm-muws-part2-1.0 137Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 46 of 67 138 1714 1715 1716 1718 1720 1721 1722 1723 1724 1725 1726 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1765 1767 1768 1770 1771 1772 1773 1774 1775

139wd-wsdm-muws-part2-1.0 140Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 47 of 67 141 1776 1777 1779 1780 1781 1782 1783 1785 1786 1788 1791 1793 1794 1795 1796 1797 1798 1800 1801 1802 1803 1804 1805 1806 1807 1809 1810 1811 1812 1813 1814 1815 1816 1817 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1836 1837

142wd-wsdm-muws-part2-1.0 143Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 48 of 67 144 1838 1839 1840 1841 1842 1843 1845 1846 1847 1848 1849 1850 1851 1852 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1868 1869 1871 1873 1874 1875 1876 1877 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1890 1892 1894 1897 1898 1899

145wd-wsdm-muws-part2-1.0 146Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 49 of 67 147 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1912 1913 1914 1915 1916 1917 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1959

148wd-wsdm-muws-part2-1.0 149Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 50 of 67 150 1961 1962 1972 1973 1977 1981 1984 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2004 2006 2008 2009 2010 2011 2013 2014 2015 2016 2017 2019 2020 2021 2022

151wd-wsdm-muws-part2-1.0 152Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 51 of 67 153 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2039 2041 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084

154wd-wsdm-muws-part2-1.0 155Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 52 of 67 156 2085 type="muws-p2-xs:MetricsPropertiesType"/> 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2099 2101 2103 2104 2105 2106 2107 2108 2109 2111 2112 2113 2114 2116 2117 2119 2122 2124 2125 2126 2127 2128 2130 2131 2132 2133 2135 2136 2137 2138 2140 2141 2142 2143 2144 2145

157wd-wsdm-muws-part2-1.0 158Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 53 of 67 159 2147 2148 2149 2150 2151 2152 2153 2154 2155 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2168 2169 2170 2171 2173 2174 2175 2176 2177 2178 2180 2181 2182 2183 2184 2185 2186 2187 2188 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2204 2205 2206 2207 2208

160wd-wsdm-muws-part2-1.0 161Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 54 of 67 162 2209 2210 2211 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2224 2226 2227 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270

163wd-wsdm-muws-part2-1.0 164Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 55 of 67 165 2271 2272 2273 2274 2275 2276 2277 2279 2280 2282 2283 2285 2286 2288 2289 2290 2291 2292 2294 2296 2298 2300 2302 2304 2306 2307 2308 2309 2310

2312 2313 2326 2327 2328 2331 2332 2336 2337 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2370

169wd-wsdm-muws-part2-1.0 170Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 57 of 67 171 2371 2372 2373 2375 2376 2377 2380 2381 2382 2385 2386 2387 2389 2390 2391 2393 2394 2395 2397 2398 2399 2401 2402 2403 2405 2407 2408 2409 2410 2411 2414 2415 2416

2418 2429 2430 2432 2433 2434 2436 2437 2438 2440 2441 2442 2444 2445 2446 2448 2449 2450 2452 2453 2454 2456 2457 2459 2461 //muws-p1-xs:ManagementEvent[count(muws-p2- 2462 xs:RelationshipCreatedNotification)=1] 2463 2464 2465 2466 2468 2470 //muws-p1-xs:ManagementEvent[count(muws-p2- 2471 xs:RelationshipDeletedNotification)=1] 2472 2473 2474 2475 2476 175wd-wsdm-muws-part2-1.0 176Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 59 of 67 177 2477 2479 2480 2481 2483 2485 //muws-p1-xs:ManagementEvent[count(muws-p2- 2486 xs:CreationNotification)=1] 2487 2488 2489 2491 2493 //muws-p1-xs:ManagementEvent[count(muws-p2- 2494 xs:CreationNotification)=1] 2495 2496 2497 2498 2499 2500 2502 2504 //muws-p1-xs:ManagementEvent[count(muws-p2- 2505 xs:DestructionNotification)=1] 2506 2507 2508 2510 2512 //muws-p1-xs:ManagementEvent[count(muws-p2- 2513 xs:DestructionNotification)=1] 2514 2515 2516 2517 2518 2519 2526 2527 2529 2531 boolean(//ManagementEvent[ 2532 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2533 wsdm-muws-part1-1.0.xsd' 2534 and count(ResourcePropertyValueChangeNotification[ 2535 namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS- 2536 ResourceProperties-1.2-draft-01.xsd"])=1]) 2537 2538

178wd-wsdm-muws-part2-1.0 179Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 60 of 67 180 2539 2540 2542 2544 boolean(//ManagementEvent[ 2545 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2546 wsdm-muws-part1-1.0.xsd' 2547 and count(ResourcePropertyValueChangeNotification[ 2548 namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS- 2549 ResourceProperties-1.2-draft-01.xsd"])=1]) 2550 2551 2552 2553 2555 2557 boolean(//ManagementEvent[ 2558 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2559 wsdm-muws-part1-1.0.xsd' 2560 and count(ResourcePropertyValueChangeNotification[ 2561 namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS- 2562 ResourceProperties-1.2-draft-01.xsd"])=1]) 2563 2564 2565 2566 2568 2570 boolean(//ManagementEvent[ 2571 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2572 wsdm-muws-part1-1.0.xsd' 2573 and count(ResourcePropertyValueChangeNotification[ 2574 namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS- 2575 ResourceProperties-1.2-draft-01.xsd"])=1]) 2576 2577 2578 2579 2581 2583 boolean(//ManagementEvent[ 2584 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2585 wsdm-muws-part1-1.0.xsd' 2586 and count(ResourcePropertyValueChangeNotification[ 2587 namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS- 2588 ResourceProperties-1.2-draft-01.xsd"])=1]) 2589 2590 2591 2592 2594 2596 boolean(//ManagementEvent[ 2597 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2598 wsdm-muws-part1-1.0.xsd' 2599 and count(ResourcePropertyValueChangeNotification[

181wd-wsdm-muws-part2-1.0 182Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 61 of 67 183 2600 namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS- 2601 ResourceProperties-1.2-draft-01.xsd"])=1]) 2602 2603 2604 2605 2607 2609 boolean(//ManagementEvent[ 2610 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2611 wsdm-muws-part1-1.0.xsd' 2612 and count(ResourcePropertyValueChangeNotification[ 2613 namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS- 2614 ResourceProperties-1.2-draft-01.xsd"])=1]) 2615 2616 2617 2619 2621 boolean(//ManagementEvent[ 2622 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2623 wsdm-muws-part1-1.0.xsd' 2624 and count(RelationshipCreatedNotification[ 2625 namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2626 wsdm-muws-part2-1.0.xsd"])=1]) 2627 2628 2629 2630 2632 2634 boolean(//ManagementEvent[ 2635 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2636 wsdm-muws-part1-1.0.xsd' 2637 and count(RelationshipDeletedNotification[ 2638 namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2639 wsdm-muws-part2-1.0.xsd"])=1]) 2640 2641 2642 2643 2644 2645 2647 2649 boolean(//ManagementEvent[ 2650 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2651 wsdm-muws-part1-1.0.xsd' 2652 and count(ResourcePropertyValueChangeNotification[ 2653 namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS- 2654 ResourceProperties-1.2-draft-01.xsd"])=1]) 2655 2656 2657 2658 2660

184wd-wsdm-muws-part2-1.0 185Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 62 of 67 186 2662 boolean(//ManagementEvent[ 2663 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2664 wsdm-muws-part1-1.0.xsd' 2665 and count(CreationNotification[ 2666 namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2667 wsdm-muws-part2-1.0.xsd"])=1]) 2668 2669 2670 2672 2674 boolean(//ManagementEvent[ 2675 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2676 wsdm-muws-part1-1.0.xsd' 2677 and count(CreationNotification[ 2678 namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2679 wsdm-muws-part2-1.0.xsd"])=1]) 2680 2681 2682 2683 2684 2685 2687 2689 boolean(//ManagementEvent[ 2690 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2691 wsdm-muws-part1-1.0.xsd' 2692 and count(DestructionNotification[ 2693 namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2694 wsdm-muws-part2-1.0.xsd"])=1]) 2695 2696 2697 2699 2701 boolean(//ManagementEvent[ 2702 namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2703 wsdm-muws-part1-1.0.xsd' 2704 and count(DestructionNotification[ 2705 namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd- 2706 wsdm-muws-part2-1.0.xsd"])=1]) 2707 2708 2709 2710 2711 2712

2714This appendix defines in more details the situation types introduced in section 2.4.1. 2715AvailabilitySituation 2716This category deals with the situations reported from the component, regarding its operational 2717state and availability. This situation provides a context for operations that can be performed by 2718the component to establish if a product is installed, operational and ready to process functional 2719requests, or operational and ready or not ready to process management requests. Existing 2720message include words like “now ready to take requests”, “online”, and “offline”, for 2721example:Deals with the situations reported from the component, regarding its operational state 2722and availability. This situation provides a context for operations that can be performed by the 2723component to establish if a product is installed, operational and ready to process functional 2724requests, or operational and ready or not ready to process management requests. Existing 2725message include words like now ready to take requests, online, and offline, for example: 2726  “SOAP connector available at port 8888” 2727 2728CapabilitySituation 2729This category is specified when a change in capability of a resource occurs. For example, a 2730printer has an envelope tray attached to it so that the printer is now has additional paper choices. 2731The same category would be used if the envelope tray is removed from the printer. 2732XXXX 2733 2734ConfigurationSituation 2735This category deals with the components identifying configuration changes. Any changes that a 2736component makes to its configuration should be logged using this category. Existing message 2737include words like “port number is”, “address is”, and “process id”, for exampleDeals with the 2738components identifying their configuration. Any changes that a component makes to its 2739configuration should be logged using this category. Additionally, messages that describe the 2740current configuration state fall into this category. Existing message include words like port number 2741is, address is, and process id, for example: 2742  “File transfer configured with host=’9.27.11.13’, port=’9090’, securityEnabled=’false’” 2743 2744StopSituation 2745This category deals with the shutdown process for a component. Messages that indicate that a 2746component has begun to stop, that it has stopped, or that the stopping process has failed all fall 2747into this category. Existing messages include words like “stop”, “stopping”, “stopped”, 2748“completed”, and “exiting”, for exampleDeals with the shutdown process for a component. 2749Messages that indicate that a component has begun to stop, that it has stopped, or that the 2750stopping process has failed all fall into this category. Existing messages include words like stop, 2751stopping, stopped, completed, and exiting, for example: 2752  “Application stopped: myApp.exe” 2753  “An error occurred while stopping myApp.exe” 2754  “Stopping the JMS provider” 2755 2756StartSituation

190wd-wsdm-muws-part2-1.0 191Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 64 of 67 192 2757This category deals with the startup process for a component. Messages that indicate that a 2758component has begun the startup process, that it has finished the startup process, or that it has 2759aborted the startup process all fall into this category. Existing messages include words like 2760“starting”, “started”, “initializing”, and “initialized”, for exampleDeals with the startup process for a 2761component. Messages that indicate that a component has begun the startup process, that it has 2762finished the startup process, or that it has aborted the startup process all fall into this category. 2763Existing messages include words like starting, started, initializing, and initialized, for example: 2764  “XYZ protocol support was successfully started” 2765  “XYZ protocol support failed to start” 2766  “Starting EJB: myEjb.jar” 2767 2768RequestSituation 2769This category is used in situations that a component uses to identify the completion status of a 2770request. Typically, these requests are complex management tasks or transactions that a 2771component undertakes on behalf of a requestor and not the mainline simple requests or 2772transactions. Existing messages are of the form “request started” or “request completed” as in 2773phrases like “configuration synchronization started”, and “backup procedure complete”, for 2774exampleHandles the situations that a component uses to identify the completion status of a 2775request. Typically, these requests are complex management tasks or transactions that a 2776component undertakes on behalf of a requestor and not the mainline simple requests or 2777transactions. Existing messages include words like configuration synchronization started, and 2778backup procedure complete, for example: 2779  “Configuration synchronization completed” 2780Note that events generated from requests that start up or stop a resource would be categorized 2781as StartSituation or StopSituation respectively because they are higher precedent than 2782RequestSituation. 2783 2784DestroySituation 2785This category deals with the situations occurring when an entity or component was removed or 2786destroyed. Messages telling that a document was destroyed or a file was deleted all fall into this 2787category. Existing messages include phrases like “was destroyed”, “about to remove”, and “no 2788longer exists”, for exampleDeals with the situations documenting when an entity or component 2789was removed or destroyed. Messages telling that a document was destroyed or a file was deleted 2790all fall into this category. Existing messages include words like was deleted, about to delete, and 2791now deleted, for example: 2792  “The connection pool was destroyed for data source foo” 2793 2794CreateSituation 2795This category deals with the situations occurring when a component creates an entity. Messages 2796telling that a document was created, or a file was created, or an Enterprise JavaBean (EJB) was 2797created all fall into this category. Existing message include words like was created, about to 2798create, and now exists, for exampleDeals with the situations documenting when a component 2799creates an entity. Messages telling that a document was created, or a file was created, or an 2800Enterprise JavaBean (EJB) was created all fall into this category. Existing message include words 2801like was created, about to create, and now exists, for example: 2802  “New log file was created” 2803 2804DependencySituation 193wd-wsdm-muws-part2-1.0 194Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 65 of 67 195 2805This category deals with the situations where components cannot find some component or 2806feature that they require. This category includes messages about not finding the ”version” of the 2807component that was expected. Messages that say a resource was not found, or that an 2808application or subsystem that was unavailable, also fall into this category. Existing messages 2809include words like “could not find”, and “no such component”, for exampleDeals with the 2810situations that components produce to indicate that they cannot find some component or feature 2811that they require. This category includes messages about not finding the “version” of the 2812component that was expected. Messages that say a resource was not found, or that an 2813application or subsystem that was unavailable, also fall into this category. Existing messages 2814include words like could not find, and no such component, for example: 2815  “Error encountered while deploying database schema: no database found” 2816 2817 2818ConnectSituation 2819This category deals with the situations related to aspects about a connection attempt from one 2820component to another component. Messages that say a connection failed, that a connection was 2821created, or that a connection was ended all fall into this category. Existing messages include 2822words like “connection reset”, “connection failed”, and “failed to get a connection”, for 2823exampleDeals with the situations that identify aspects about a connection attempt from one 2824component to another component. Messages that say a connection failed, that a connection was 2825created, or that a connection was ended all fall into this category. Existing messages include 2826words like connection reset, connection failed, and failed to get a connection, for example: 2827  “Connection creation failed” 2828  “Connection with http://foo.com created” 2829  “Failed to close a connection” 2830 2831ReportSituation 2832This category deals with situations that occur as a result of some setting or occurrence that 2833causes the resource to asynchronously report various types of data. Types of information that 2834falls into this category are: 2835 2836  Exception related – some exception has occurred within the resource and it not covered 2837 by any other category. 2838  Performance related – some event occurs, that does not fall into any other category, 2839 that has affected performance in some way. For example, weather conditions may be 2840 affected line quality and network speeds are affected. 2841  Security related – some security issue has been detected, like the cabinet door to a 2842 secure piece of equipment has been opened or an attack of some sort has been 2843 detected. 2844  Heartbeat related – the resource has been configured to periodically report a ‘heartbeat’. 2845  Status related – some change of status that does not affect availability or capability of 2846 the resource has been detected. For example, printer ink cartridge is low. 2847  Log related – the resource has been configured to generate a log entry based on some 2848 event or at a fixed interval. This category identifies this event as a requested log entry. 2849  Debug related – the resource has been enabled to turn on diagnostic information flow 2850 and will report the information within this category. 2851  Trace related – the resource has been enabled to run trace information and reports this 2852 information using this category 2853XXXXX

2854 2855OtherSituation 196wd-wsdm-muws-part2-1.0 197Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 66 of 67 198 2856 2857This category is for those events that do not fall into any other category. Note that this category 2858is defined for syntactic completeness but any events placed in this category will not be able to be 2859effectively correlated and its use is therefore discouraged unless absolutely necessary. 2860Deals with any situation not covered by the other situation types.