WSDM MUWS 1.0 Part 2 - OASIS · Web viewWeb Services Distributed Management: Management Using Web Services (MUWS 1.0) Part 2

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

Working Draft, November 26th 1st 2004

wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 1 of 68

1

2

3

4

5

12

3

Document identifier:wd-wsdm-muws-part2-1.0

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

Editors:William Vambenepe, Hewlett-Packard <[email protected]>

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

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


67

89

1011

121314151617181920212223

2425262728293031323334353637

45

6

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

mailto:[email protected]

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

Table of Contents

1 Introduction ........................................................................................................................ 4

2 Use of the Web Services Platform ......................................................................................5

2.1 Use of WS-Resource Properties .................................................................................5

2.2 Use of WS-Notification ...............................................................................................6

2.3 Metadata ...................................................................................................................6

2.3.1 Metadata applicable to all aspects of manageability interfaces ................................6

2.3.2 Metadata applicable to properties ...........................................................................7

2.3.3 Operations .............................................................................................................8

2.4 Events ....................................................................................................................... 8

2.4.1 Event Format .........................................................................................................8

2.4.2 Topics for capabilities ...........................................................................................11

2.5 Representation of Categorization Taxonomies in XML ..............................................12

3 Capabilities applicable to manageable resources ..............................................................14

3.1 Description ...............................................................................................................14

3.1.1 Definition .............................................................................................................14

3.1.2 Properties ............................................................................................................14

3.2 State ........................................................................................................................ 15

3.2.1 Definition .............................................................................................................15

3.2.2 Describing State Models ......................................................................................15

3.2.3 Information Markup Declarations ..........................................................................17

3.2.4 Properties ............................................................................................................18

3.2.5 Operations ...........................................................................................................19

3.2.6 Events ................................................................................................................. 19

3.3 Operational Status ...................................................................................................19

3.3.1 Definition .............................................................................................................20

3.3.2 Properties ............................................................................................................20

3.4 Metrics ..................................................................................................................... 20

3.4.1 Definition .............................................................................................................21


3.4.3 Metadata .............................................................................................................22

3.4.4 Properties ............................................................................................................23

3.4.5 Events ................................................................................................................. 23

3.5 Configuration ...........................................................................................................24

3.5.1 Definition .............................................................................................................24wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 3 of 68

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

7278

9

4 Capabilities applicable to management in general .............................................................25

4.1 Relationships ...........................................................................................................25

4.1.1 Definition .............................................................................................................25


4.1.3 Properties ............................................................................................................28

4.1.4 Operations ...........................................................................................................29

4.1.5 Events ................................................................................................................. 29

4.2 Relationship Access Capability .................................................................................30

4.2.1 Definition .............................................................................................................30

4.3 Relationship Resource Capability .............................................................................31

4.3.1 Definition .............................................................................................................31

4.3.2 Properties ............................................................................................................31

4.4 Advertisement ..........................................................................................................32

4.4.1 Definition .............................................................................................................32

4.4.2 Events ................................................................................................................. 32

5 Discovery ......................................................................................................................... 35

5.1 Discovery using Relationships ..................................................................................35

5.2 Discovery using Registries .......................................................................................35

6 References ....................................................................................................................... 37

6.1 Normative ................................................................................................................37

6.2 Non-normative .........................................................................................................38

Appendix A. Acknowledgements ..........................................................................................39

Appendix B. Notices ............................................................................................................40

Appendix C. Schemas .........................................................................................................41

Appendix D. WSDL elements ...............................................................................................46

Appendix E. Topics .............................................................................................................48

Appendix F. Description of situation types ...........................................................................50

1 Introduction ........................................................................................................................ 4

2 Usage of the Web Services Platform ..................................................................................5

2.1 Use of WS-Resource Properties .................................................................................5

2.2 Use of WS-Notification ...............................................................................................5

2.3 Metadata ...................................................................................................................6

2.3.1 Metadata applicable to all aspects of manageability interfaces ................................6

2.3.2 Metadata applicable to properties ...........................................................................7

2.3.3 Operations .............................................................................................................9

2.4 Events ....................................................................................................................... 9

2.4.1 Event Format .........................................................................................................9wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 4 of 68

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

100

101

102

103

104

105

106

107

108

1091011

12

2.4.2 Topics for capabilities ...........................................................................................12

2.5 Security ................................................................................................................... 13

2.6 Representation of Categorization Taxonomies in XML ..............................................13

3 Capabilities applicable to manageable resources ..............................................................15

3.1 Description ...............................................................................................................15

3.1.1 Definition .............................................................................................................15

3.1.2 Properties ............................................................................................................15

3.2 State ........................................................................................................................ 16

3.2.1 Definition .............................................................................................................16

3.2.2 Describing State Models ......................................................................................16


3.2.4 Properties ............................................................................................................19

3.2.5 Operations ...........................................................................................................20

3.2.6 Events ................................................................................................................. 20

3.3 Operational Status ...................................................................................................20

3.3.1 Definition .............................................................................................................21

3.3.2 Properties ............................................................................................................21

3.4 Metrics ..................................................................................................................... 21

3.4.1 Definition .............................................................................................................22


3.4.3 Metadata .............................................................................................................23

3.4.4 Properties ............................................................................................................23

3.4.5 Events ................................................................................................................. 23

3.5 Configuration ...........................................................................................................24

3.5.1 Definition .............................................................................................................24

4 Capabilities applicable to management in general .............................................................25

4.1 Relationships ...........................................................................................................25

4.1.1 Definition .............................................................................................................25


4.1.3 Properties ............................................................................................................28

4.1.4 Operations ...........................................................................................................29

4.1.5 Events ................................................................................................................. 29

4.2 Relationship Access Capability .................................................................................30

4.2.1 Definition .............................................................................................................30

4.3 Relationship Resource Capability .............................................................................30

4.3.1 Definition .............................................................................................................30

4.3.2 Properties ............................................................................................................31wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 5 of 68

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

1461314

15

4.4 Advertisement ..........................................................................................................31

4.4.1 Definition .............................................................................................................31

4.4.2 Events ................................................................................................................. 32

5 Discovery ......................................................................................................................... 34

5.1 Discovery using Relationships ..................................................................................34

5.2 Discovery using Registries .......................................................................................34

6 References ....................................................................................................................... 36

6.1 Normative ................................................................................................................36

6.2 Non-normative .........................................................................................................37

Appendix A. Acknowledgements ..........................................................................................38

Appendix B. Notices ............................................................................................................39

Appendix C. Schemas .........................................................................................................40

Appendix D. WSDL elements ...............................................................................................46

Appendix E. Topics .............................................................................................................48

Appendix F. Description of situation types ...........................................................................51


147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

1617

18

1 IntroductionMuws This document, MUWS Ppart 2, (this document) builds upon the foundation provided by [MUWS Part 1]. All of the normative content text presented in MUWS Ppart 1 is considered normative text for MUWS Ppart 2. All informational content text presented in MUWS Ppart 1 is relevant informational content text for MUWS part Part 2. Compliance with MUWS Ppart 1 is REQUIRED in for all every aspects of MUWS Ppart 2.

The text of this specification along with Appendix C (Schemas), Appendix D (WSDL elements), Appendix E (Topics) and Appendix F (Description of situation types) is considered are normative with the following exceptions: the abstract, the examples, the UML diagrams, and any section explicitly marked as non-normative are is considered non-normative text.

The terminology and notational conventions defined in [MUWS Part 1] apply to this document.

The 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

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

WSDL ([WSDL 1.1]) elements introduced in this section belong to the namespace mapped to “muws-p2-wsdl”.


163

164165166167168

169170171172

173

174

175176

177178

1920

21

http://schemas/

http://www/

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

2.1 Use of WS-Resource PropertiesMUWS leverages and builds upon the concepts presented in the Web Services Resources Framework ([WSRF]). , in which,A the MUWS "manageable resource"s are is a refinement of a WSRF represented by Web services as “resources”., in the WSRF sense of the term. TheBy composingtion of a manageability endpoint and with a manageable resource, made accessible through this endpoint, MUWS creates a WS-Resource, as defined by [WS-Resource]. References In MUWS, a reference to a manageability endpoints in MUWS relies uponuse the reference mechanisms as defined by in [WS--Resource], and more specifically, leverage and refine the endpoint references (EPR) concept, as defined by in [WS-Addressing].

If the a manageability endpoint corresponds to a zero or morevariable number (zero or more) of manageable resources, then the “WS--Addressing Using Reference Properties Embodiment” of [WSs-Resource] MUST be followed. This means thatIn other words, the each element(s) listed in the ReferenceProperties of a WS-Resource qualified EPR must MUST be included in the header of each messages sent to such each corresponding manageability endpoints. The MUWSis specification does not currently define how to obtain the an EPR. Currently, to obtain an EPR, There there may be be an some out-of-band agreement between a service provider and a manageability consumer. on how to obtain EPRs orPossibly, some future versions of this the MUWS specification would might clarify and standardize this subjectan approach to obtain an EPR.

In the specific case where a manageability endpoint corresponds to one and only one manageable resource, then either the “WS-Addressing Using Reference Properties Embodiment” concept, as above, or the “WS-Addressing Without Using Reference Properties Embodiment” concept MUST be usedfollowed. If the “WS-Addressing Without Using Reference Properties Embodiment” is usedfollowed, this means thatthen the manageability endpoint does not expect to receive the a list of elements listed in the ReferenceProperties section of WS-Resource qualified EPR s inincluded in the message header.

s to indicate which resource is being managed. A manageability consumer who does not havewithout an EPR for a manageability endpoint MAY try to invoke manageability operations without including reference properties information. If such an invocation succeeds, the manageability consumer can infer it is talking about a manageable resource through a manageability provider.

Furthermore, management properties as defined in MUWS are represented as WSRF “properties”, in the WSRF sense of the term, using and use the mechanisms defined in WS-ResourceProperties ([WS-RP]). This means thatIn other words, each manageable resource exposes a resource properties document (containing, as children of the document root, all the properties of the manageable resource. The manageable resource then makes) and makes this document available, as specified described in WS-ResourceProperties.

Supporting WS-ResourceProperties means that any implementation of an interface that includes properties MUST include access methods to these properties as defined by wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 8 of 68

179

180181182183184

185

186187188189190191192193

194195196197198199200201202203

204205206207208209210

211212213214215

216217218219220221

222223

2223

24

Homayoun Pourheidari, 11/29/04,

Shouldn’t this be “to” instead of “about”? I would use “communicating” instead of “talking”.

WS-ResourceProperties. Specifically, the interface MUST include the GetResourceProperty operation defined by [WS-RP] and MAY include the GetMultipleProperties, SetResourceProperties and QueryResourceProperties operations. If the QueryResourceProperties operation is provided, then the QueryResourceProperties operation it SHOULD support the XPath 1.0 query expression dialect, represented by URI http://www.w3.org/TR/1999/REC-xpath-19991116.

2.2 Use of WS-NotificationMUWS uses the notification mechanism described by WS-BaseNotification ([WSN]). When If a manageability capability includes the an ability to offer events to a consumer, then the definition of the capability will SHALL include a WS-Topics ([WST]) topic space, as described in WS-Topics ([WST]). The topic space SHALL containing the an appropriate set of topics appropriate for the events offered by the capability. As described in part MUWS Part 1, an event is defined by a URI and a “content” element. The URI corresponds to the “topic” of the event, as defined by [WST].

Note that as WS-BaseNotification does not currently support a way means to specify that only some of the information contained in the notification message should be sent to the consumer. MUWS does not define a way means to specify this either. Manageability The manageability consumers and the implementers of a manageability endpoints should be aware of there is a the performance cost of for processing a large number ofmany, large notification messages.

2.3 MetadataMUWS defines a set of base schema for metadata elements. These metadata elements can be to be represented as XML Schema elements. whose The purpose of a metadata element is to supplement the information available in the WSDL [WSDL 1.1] and the WS-ResourceProperties [WS-RP] declaration for a manageability interface. A metadata element to provides additional description relevant to the managed resource. In particular, a metadata element it allowsenables a tools and or management applications, to perform detailed be able to reasoning and make specialized inferences in detail about the a manageable resource both at runtime, and, within during development tools , when no instance is available for a manageable resource. instances are available.

These characteristics are needed necessary, both at runtime, and, at build timeduring development. Metadata elements need to , which means that they must be available when no instance is available for a manageable resource e without having a running instance of the resource.

If metadata is required, then an XML document containing metadata can beis defined and associated with the a WS-ResourceProperties document and WSDL. Document processing, like an XPath queryies, of the document can beis used to extract all or part of the metadata. Currently, WSDM does not define the format of, or how to associate, or, how to access the document metadata document at this timecontent. Although some mechanism is necessary, The scope of thisis MUWS specification does not includeexcludesdoes not provide the any functionmechanism required tofor accessing the metadata from an instance of a manageable resource instance.

, aAlso,lthough it is necessary for such a mechanism to exist. This this MUWS specification also does notexcludesdoes not provide any description ofbe how the metadata is for associated with a type of manageable resource, types is are stored, and or made available to tooling at this time.

The MUWS specification defines a set of metadata elements that apply to the basic manageability specific metadata of a manageable resource. The MUWS specification usess and Global Element Declarations to represent thema metadata element.


224225226227228229

230

231232233234235236

237238239240241

242

243244245246247248249250251

252253254255

256257258259260261262263

264265266

267268269

2526

27


Add “that” before “there”.

2.3.1 Metadata applicable to all aspects of manageability interfacesMUWS defines a metadata elements applicable to all aspects of a manageability interface (operations, properties, events…). These capabilities elements are:

<muws-p2-xs:Capability>xs:anyURI</muws-p2-xs:Capability> *

The muws-p2-xs:Capability metadata element SHOULD be provided for any MUWS aspect of a manageability interface. This enables discovery of aspects of an interface associated with a capability. This element contains a URI identifying the capability.

This metadata element indicates the classification of an aspect of an interface according to its an intended capability, (or capabilities. ), for For example, as aan aspect may be classified as a metric, or, as a piece of configuration and so onproperty. A property may be relevant to more than one capability. For example, a configuration property, such as the IP address of a computer system contains the IP address. This property, could also be used for identification purposes.

Some of the known capabilities are listed below for illustration. This is not an exhaustive list. For a detailed explanation,s see the relevant MUWS manageability capability specification. Additional capabilities are expected to be added as extensions to MUWS.

http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/IdentityIdentity capability. See [MUWS Part 1].

http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/ConfiguationConfiguration property. See section 3.5.

http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/CorrelatableProperties”Correlatable Properties” capability. See [MUWS Part 1].

http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/StateState capability. See section 3.2.

http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/MetricsMetrics capability. See section 3.4.

User definedA uUser defined, capability that extends, or, is different from, the a standard capabilityies defined in MUWS.

The capabilities defined in this document specify that a property or operation has a certain value represented as one instance of muws:p2-xs:Capability by stating “its Capability is <some URI>”.

<muws-p2-xs:ValidWhile Dialect=”xs:anyURI”> {any} * </muws-p2-xs:ValidWhile>

muws-p2-xs:ValidWhile contains a statement that, when true, asserts that the interface aspect to which this metadata element is related is valid. This is used, for example, to express the fact that an operation can only be invoked when certain properties have certain values.

muws-p2-xs:ValidWhile/@Dialect is a URI identifying how the statement in muws-p2-xs:ValidWhile is built and what rules govern its evaluation. MUWS defines one possible value for this element. Other values can also be defined.

The value defined by MUWS is http://www.w3.org/TR/1999/REC-xpath-19991116. When this dialect is used, the content of muws-p2-xs:ValidWhile is an [Xpath 1.0] expression. This expression is to be evaluated against the resource properties document of the manageable resource. If the XPath expression evaluates to a Boolean value of “true”, or if it evaluates to a non-empty non-boolean value without any errors, then the statement is considered “true”.


270

271272

273

274

275276277

278279280281282

283284285286287288289290291292293294295296297298299300301302303304

305306307

308309310

311312313314315

2829

30

2.3.2 Metadata applicable to propertiesGeneral purpose metadata that is not management specific is defined in the MUWS specification, but not specified in schema. General purpose metadata that can be defined for any property includes:

Mutability – indicates if the property value will can change over time Modifiability – indicates if the property can be set directly (not as a side-effect) Valid Values – the a set of valid values for the property Valid Range – the a range of valid values for the property Static Values – the a set of initial values for the property Notifiability – indicates if a notification will beis sent when there is a change to the value

of theis property changes valueSchema to represent general purpose metadata should be composed in from a metadata specification, such asfor example, the WS-Resource Metadata Descriptor [WSRMD], as developed in the WS-RF OASIS technical committee.

In addition, MUWS defines a set of metadata related to management. Any property element may have the following manageability metadata elements:

<muws-p2-xs:Units>xs:string</muws-p2-xs:Units>

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

Other metadata elements, applicable for metric-type properties, are defined in section 3.4.3.

<ChangeType>Counter|Gauge|Unknown</ChangeType>

muws-p2-xs:ChangeType is an enumeration which describesfor indicating how changes to that the associated metric value should be interpreted by the consumer. A property that representings a metric MUST include a single instance of ChangeType in its metadata description. EachThe ChangeType following values may be used for ChangeTypeis interpreted as follows:

Counter - the value of the metric increments over successive counts, collections, or measurements.

Gauge - the value of the metric varies between a range of values.

Unknown - the change behavior is not known or cannot be described.

<muws-p2-xs:TimeScope>Interval|PointInTime|SinceReset</muws-p2-xs:TimeScope>

muws-p2-xs:TimeScope is an enumeration that for indicatinges whether if there is some interval, over which the data is collected, counted, or measured. A property that is a metric MUST include a single instance of TimeScope in its metadata description. The following values may be used forEach TimeScope value is interpreted as follows:

Interval - the value of the metric was is collected over some time interval. In this case the Duration attribute MUST be reported with the metric property. The value of the Duration attribute is the time, from the beginning of the interval, to the end of the interval. The Duration and is usually remains the same for every reading of the metric.

PointInTime - the value of the metric was is counted, collected, or measured at a single instant in time. The Duration attribute MUST NOT be reported with metrics having a PointInTime


316

317318319320321322323324325326327328329

330331

332

333

334

335

336

337

338339340341

342343

344

345

346

347

348349350351

352353354355

356357

3132

33

TimeScope value of PointInTime. Metrics with a TimeScope value of PointInTime do not support the reset capability and MUST NOT include the ResetAt attribute.

SinceReset - the value of the metric was is collected since reset, or since the manageable resource started collecting metrics data. In this case the Duration attribute MUST be reported with the metric property. The value of the Duration attribute is the time since the metric was reset, or since the resource started collecting metrics data, if no reset has occurred. Thus the value of Duration willmay be report a different value for every each retrievalading of the property.

<muws-p2-xs:gatheringTime>

OnChange|Periodic|OnDemand|Unknown

</muws-p2-xs:gatheringTime>

muws-p2-xs:GatheringTime is an enumeration that indicatinges at what times the value of the metric is counted, collected, or measured. A property that is a metric MUST include a single instance of GatheringTime in its metadata description. The following values may be used forEach GatheringTime value is interpreted as follows:

OnChange - the value of the metric is updated as soon as there is whenever a change in occurs to the quantity measured.

Periodic - the value of the metric is updated on a regular basis.

OnDemand - the value of the metric is updated when there is a request for the metric value.

Unknown - it is unknown when the metric value is updated.

<muws-p2-xs:CalculationInterval>xs:duration</muws-p2-xs:CalculationInterval>

muws-xs-p2:CalculationInterval represents the interval at which the metric will beis gathered or calculated by the resource. The value of the metric is not updated during a calculation intervals.

<muws-p2-xs:MetricGroup>xs:anyURI</muws-p2-xs:MetricGroup>

muws-p2-xs:MetricGroup indicates that the metric property is a member of a group of metrics. A metric property MAY be a member of zero or more metric groups. A metric group is identified by a URI. All Each property includedies in a metric group will includeSHALL have a MetricGroup element with thecontaining an identical same URI. A property that is a metric MUST include zero or more MetricGroup elements in its metadata description. Each MetricGroup element to represents a membership in a all of the metric groups to which it belongs.

Operations

General purpose metadata, that is not management specific, is defined in the MUWS specification, but not specified in schema. General purpose metadata that can be defined for any operation includes:

Idempotency – indicates if invoking the operation twice is equivalent to invoking it onceSchema to represent general purpose metadata should be composed in from a metadata specification, such for example, as the WS-Resource Metadata Descriptor [WSRMD], as developed in the WS-RF OASIS technical committee.

In addition, MUWS defines metadata related to management. Any operation element may have the following manageability metadata element:wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 12 of 68

358359

360361362363364

365

366

367

368

369370371372

373374

375

376

377

378

379

380381

382

383

384385386387388389

390

391392393394395396397

398399

3435

36

<muws-p2-xs:PostCondition Dialect=”xs:anyURI”>{any} *

</muws-p2-xs:PostCondition>

muws-p2-xs:PostCondition contains a statement that is assertsed "to be true" right immediately after the corresponding operation is completes.

muws-p2-xs:PostCondition/@Dialect is a URI identifying how the statement in muws-p2-xs:PostCondition is built, and what rules govern its evaluation. MUWS defines one possible value for this element. Other values can be defined.

The value defined by MUWS is http://www.w3.org/TR/1999/REC-xpath-19991116. When this dialect is used, the content of muws-p2-xs:PostCondition is an [Xpath 1.0] expression. This expression is to be evaluated against the resource properties document of the manageable resource. If the XPath expression evaluates to a Boolean value of “true”, or, if it evaluates to a non-empty non-boolean value without any errors, then the statement is considered “true”.

2.4 Events

2.4.1 Event Format[MUWS Part 1] defines the muws-p1-xs:ManagementEvent Global Element Declaration to beas a container for management events. muws-p1-xs:ManagementEvent allows for information to be added using via extensibility elements. The muws-p2-xs:Situation element defined below MUST be present as a child of the muws-p1-xs:ManagementEvent element in notifications.

The As a result, resulting the event format has ais flexible and extensible format and permitsting virtually free-form expression of events., while aAt the same time, automated analysis is possible, as the event format provides a means to classify the an event into one of a limited set of classifications and subclassifications.

MUWS so that automated analysis is possible. Theevent classifications are based on a thorough analysis of event types, as produced by a wide range of IT equipment, and grouped according to the a general nature of the events. For example, virtually all manageable resources have a means of being started. butHowever, almost all managed resources express this a start event in some unique, and or imaginative, ways. The basic knowledge that the resource has been started is all that is necessary, for even for fairly sophisticated, automated management.

To support these event classifications, the MUWS adds specification defines the SituationCategoryType element, which is a specialization of a muws-p2-xs:CategoryType. MUWS defines the top level of classifications., leaving open eExtensions to these classifications to allow for enable a refinedfiner-grained definitionevent classifications. Through the use of the extensible muws-p2-xs:CategoryType mechanism, WSDM event consumers can comprehend an the situation for an event’s situation to a degree commensurate with their capabilityability.

<muws-p2-xs:Situation><muws-p2-xs:SituationCategory> muws:-p2-xs:SituationCategoryType</muws-p2-xs:SituationCategory><muws-p2-xs:SuccessDisposition> Succesful|Unsuccesful</muws-p2-xs:SuccessDisposition> ?

<muws-p2-xs:SituationTime>xs:dateTime</muws-p2-xs:SituationTime> ? <muws-p2-xs:Priority>xs:short</muws-p2-xs:Priority> ? <muws-p2-xs:Severity>xs:short</muws-p2-xs:Severity> ? <muws-p2-xs:Message>muws:LangString</muws-p2-xs:Message> ?


400

401402403

404405

406407408

409410411412413

414

415

416417418419

420421422423

424425426427428429

430431432433434435

436437438439440441442443444445446

3738

39


With “their” ability.


“imaginative”? I would use “inferred”.


Use “the” instead.


Add a “-“ here.

<muws-p2-xs:SubstitutableMsg MsgId=”xs:string” MsgIdType=”xs:anyURI”?> <muws-p2-xs:Value>xs:anySimpleType</muws-p2-xs:Value>* </muws-p2-xs:SubstitutableMsg> ?</muws-p2-xs:Situation>

muws-p2-xs:Situation/muws-p2-xs:SituationCategory categorizes the type of the situation that caused the event to be reported. The values, listed below, represent the names of elements in the muws-p2-xs namespace. The categories are listed in precedence order. so that iIn a cases where there may be some ambiguity about which category to use, the higher precedent category SHOULD be chosenused. The ordering of situation categories is based on experiential data showing relative importance of various types of events., choosing The use of a higher precedent categoryies permits more effective and timely correlation and analysis of events that may lead toindicate the presence of a serious problems. Details and examples of for use of the following valuesage are documented in Appendix F. This element is REQUIRED.

AvailabilitySituation CapabilitySituation ConfigureSituation StopSituation StartSituation RequestSituation DestroySituation CreateSituation DependencySituation ConnectSituation ReportSituation OtherSituation

muws-p2-xs:Situation/muws-p2-xs:SuccessDisposition in the case where this situation was is triggered by a command, this value specifies the a successful disposition of the command that causinged a reoirt of this the situation to be reported. This element is OPTIONAL and should not be included if the situation was notis not the result of a command. It The element is a restriction of string with allowing the following set of values:

Successful Unsuccessful

muws-p2-xs:Situation/muws-p2-xs:SituationTime represents the date and time that thean event was is observed. If the value does not include a time zone designation, (or, if the value does not use ‘Z’ for UCT), then the value MUST be interpreted as having a time zone of UCT. The value of the SituationTime MUST provide granularity as precisely as supported by the generating platform allows. This is a REQUIRED element and MUST be provided by the component that iacting as the originator of the an event.

muws-p2-xs:Situation/muws-p2-xs:Priority representsdefines the importance of the an event. This field element is provided forsupports management functions that requiringe an event to have abe associated with a priority. This is an OPTIONAL element. Values are constrained to a range from 0 through 100. The predefined priorities are:

The range of values is from 0 to 100. The reserved value for Low is (10), for

Medium is (50), and for

High is (70).

Other priorities MAY be used but MUST NOT be less than 0 or greater than exceed 100.


447448449450

451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486

487488489490

491

492

493

494

4041

42


Of “a” or “the” string?


?


Typo - experimental


In the order of precedence.

muws-p2-xs:Situation/muws-p2-xs:Severity represents the perceived severity of the status the event is describing with respect to the application that reports the event. This element is provided forsupports management functions that requiringe an event to havebe associated with a severity. This is an OPTIONAL element. The Spredefined severity levels, are based upon the DMTF CIM Alert Indications Perceived Severity, and are as follows:

6 (Fatal): Condition a condition is unrecoverable and the service is no longer available. 5 (Critical): Ca condition that affecting thes service has occurred. Immediate corrective

action is required. 4 (Major): a pProblem with of a relatively high severity level has occurred. It is likely that

normal use of the object will beservice is impeded. 3 (Minor): a pProblem with ofa relatively low severity level has occurred. It is unlikely that

normal use of the object will beservice is impeded. 2 (Warning): a pProblem that affecting thes service will or couldmay occur. Diagnostic

and corrective action is recommended. 1 (Information): a Message message output is considered as normal (that is, what was

and expected). For example, a process begins, a process finishes, or status information is displayed.

0 (Unknown): a sSeverity level cannot be determined.

muws-p2-xs:Situation/muws-p2-xs:Message represents the text accompanying the an event. This is typically the resolved message string in a human-readable format, as rendered for a specific locale, and is of type muws-p2-xs:LangString. This type is (an extension of xs:string that requiringes the xml:lang attribute). This is an OPTIONAL property. The While the string length for Message is unbounded,. However, it is RECOMMENDED that it the string length for Message does not exceed 1024 characters.

muws-p2-xs:Situation/muws-p2-xs:SubstitutableMsg – Contains represents the message data in a substitutable form. The attributes MsgId and MsgIdType indentify the base message type and text. The element value contains the data that will be formatted according to the formatting rules defined by the MsgId. This is an OPTIONAL element. However, but, if this element is used, it must contain all the attributes and elements specified below.

muws-p2-xs:Situation/muws-p2-xs:SubstitutableMsg/@MsgId specifies the message identifier of the an event. This identifier SHOULD be a unique value string, consisting of alphanumeric or numeric characters. The valueIt can be as simple as a string of numeric characters that identify a message in a message catalog. As an alternative, orthe value can be a multipart string of alphanumeric characters, (for example, DBT1234E). This is a REQUIRED attribute. The maximum string length for MsgId MUST NOT exceed 256 characters. The MsgIdType attribute indicates the formatting type of the MsgId.

muws-p2-xs:Situation/muws-p2-xs:SubstitutableMsg/@MsgIdType specifies the meaning and format of the MsgId. This is a REQUIRED attribute. The type of the MsgIdType attribute is a URI.

muws-p2-xs:Situation/muws-p2-xs:SubstitutableMsg/muws-p2-xs:Value can be of any simple type. There are one or more occurrences of this element with each occurrence containing an xsi:type attribute defining the type of the contained data. This element is used to pass data values which will bethat are substituted whenas the a message is formatted. This element is OPTIONAL. Each A MsgId and MsgIdType defines in its rules how to map parameters into a composed the message, based upon the order of the Value elements.

Figure 1 represents a UML description of the Situation element.


495496497498499500501502503504505506507508509510511512

513

514515516517518519

520521522523524

525526527528529530531

532533534

535536537538539540

541

4344

45


Why are we making this recommendation?


? This doesn’t read well. We are not talking about a type here…

SituationCategory[1]SuccessDisposition[0..1]SituationTime[0..1]Priority[0..1]Severity[0..1]Message[0..1]SubstitutableMsg[0..1]

MUWS::Situation

MsgId[1]MsgIdType[1]Value[0..*]

MUWS::SubstitutableMsg-SituationCategory-SuccessDisposition-SituationTime-Priority-Severity-Message-SubstitutableMsg

MUWS::Situation

-MsgId-MsgIdType-Value

MUWS::SubstitutableMsg

Figure 1: Situation Element

As an example, a minimal SituationType report for the initiation of a requested restart (at 6:06PM in Greenwich on Nov 11, 2004) would be as follows.

<muws-p2-xs:SituationType> <muws-p2-xs:SituationCategory> <foo:RestartInitiated> <muws-p2-xs:StartSituation/> </foo:RestartInitiated> </muws-p2-xs:SituationCategory> <muws-p2-xs:SuccessDisposition>Succesful</muws-p2-xs:SuccessDisposition> <muws-p2-xs:SituationTime>2004-11-11T18:06:00Z </muws-p2-xs:SituationTime><muws-p2-xs:Message xml:lang=”en”> Managed Thing XXX: restart processing begun</muws-p2-xs:Message>

</muws-p2-xs:SituationType>

It is worth notingPlease note, that, as outlined in the description of muws-p2-xs:CategoryType, the most general situation classification is appears as the innermost (in terms ofelement within the XML nesting).

2.4.2 Topics for capabilitiesFor each capability defined by MUWS, a topic is defined to that encompasses all every events related to that capability. For example, if a property related to a capability “foo” defined by MUWS changes, then a notification is sent to subscribers to of the topic that correspondings to a change events on this specific eventproperty, (as described by [WS-RP]). At the same timeConcurrently, since this property is related associated to with the “foo” capability, a notification is also sent to subscribers to of the topic that encompassinges change all events related toassociated with capability foo.

Appendix E is contains the XML description of all the topics defined by in the MUWS specification. The following It MUWS topics includes the following topics, that encompass all every events related toassociated with a the given capability:

IdentityCapability corresponds to the Identity capability defined in [MUWS Part 1]. ManageabilityCharacteristicsCapability corresponds to the Manageability Characteristics

capability defined in [MUWS Part 1] CorrelatablePropertiesCapability corresponds to the Correlatable Properties capability

defined in [MUWS Part 1] DescriptionCapability corresponds to the Description capability defined in section 3.1. OperationalStatusCapability corresponds to the Operation Status capability defined in

section 3.3. MetricsCapability corresponds to the Metrics capability defined in section 3.4. RelationshipsCapability corresponds to the Relationships capability defined in section

4.1.wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 16 of 68

542543544

545546

547548549550551552553554555556557558559

560561562

563

564565566567568569570

571572573574575576577578579580581582583584

4647

48

RelationshipResourceCapability corresponds to the Relationship Resource capability defined in section 4.3.

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

Representation of Categorization Taxonomies in XML

In the description of several manageability capabilities, categories of information are organized in taxonomies. For example, the categories of relationships between manageable resources, operational states of resources, etc. In order to convey the category information, including the taxonomy lineage, to the a manageability consumers, and, in order to represent it in XML information instances, the following convention is used:

MUWS defines an XML Schema complex type called CategoryType. The content of XML elements of this type is any XML element. When an element is defined of this type, it MUST obey the following rules:

The element and alleach its of its descendant hasve, at most, one child element.,

The top-level element and each of its descendants each represent one category in a the taxonomytaxonomy.,

The top level element represents the most specialized category. and eEach element represents a more specialized category than the category represented by the element it contains, if any.

The CategoryType XML Schema type is declared as follows:

<xs:complexType name=”CategoryType”><xs:sequence> <xs:any namespace=”##any” minOccurs="0" processContents=”lax”/></xs:sequence></xs:complexType>

The CategoryType type is used to either to declare an XML elements which containing instances of general, or (unqualified,) category information. The CategoryType type is also used to or to derive an XML Schema types to representing a specific category, for example,ies such as ofa relationships between among resources, or of among operational states.

The cCategory information MUST be declared as follows:.

An XML element is declaringed which QName identifies the semantics of a the category.

The XML element MUST be declaringed with the an XML Schema type which is a restriction of Category, or a specialized XML Schema type derived from the Csome other Category refinement (e.g., for example, RelationshipType).

The contents of the XML element MUST be either:

The only one XML element which correspondings to the generalization of the currently declared category


584585

586

587588589590591592

593

594595596597598

599600601

602

603604

605606607

608

609610611612613

614615616617

618

619

620

621622623

624

625626

4950

51


Delete this.


Delete this.

Or The empty sequence., if This case occurs if the currently declared category does not have any generalizations. For example, the declared category might be the (top of thea taxonomy).

For example, let’s assume that information about a maintenance state needs to beis represented in XML, using the approach described above abovedescribed approach. In this example, “off-for-maintenance” is a substate of “offline”, which is a substate of a resource being a resource being generally “unavailable”. Following would be the The XML representation in XML for this example follows:.

<mydomain:Off-for-Maintenance> <mydomain:Offline> <anyresource:Unavailable/> </mydomain:Offline></mydomain:Off-for-Maintenance>

By processing the XML information, a manageability consumer may understand learn that a resource is in the a state identified by the mydomain:Off-for-Maintenance element. However, at the same time, if the manageability consumer is not aware of definitions and semantics associated with the mydomain namespace, it the consumer may safely assume that the resource is in the commonly known state identified by anyresource:Unavailable.


627628629

630631632633634

635636637638639

640641642643644

5253

54

3 Capabilities applicable to manageable resources

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

3.1 DescriptionThe manageability capability URI for this the description capability ishttp://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Description

3.1.1 DefinitionFigure 2 shows the a UML representation of the Description capability.

Caption[0..*]Description[0..*]Version[0..1]

MUWS::Description-Caption-Description-Version

MUWS::Description

Figure 2: MUWS Description

3.1.2 PropertiesThis capability defines the following properties:

<muws-p2-xs:Caption>muws-p2-xs:LangString</muws-p2-xs:Caption> *

muws-p2-xs:Caption contains a descriptive name for the manageable resource. being managed. The CCaption property is intended for human consumption. and A caption is expected to be short and is suitable for display next to a graphical icon. It Caption is a read-write, optional property that haswith a cardinality of 0 to many. Caption is of type muws-p2-xs:LangType, which is a restriction of xs:string carrying an xml:lang attribute. This attribute contains a language identifier as defined by [RFC3066]. There can not be more than one Caption perfor the same language identifier.

Metadata for Caption:

It is Mutable = TrueIt is Modifiable = TrueIts Capability = is "hhttp://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Description”

<muws-p2-xs:Description>muws-p2-xs:LangString</muws-p2-xs:Description> *

muws-p2-xs:Description is a string containing a description for the resource being managed. The Description property is intended for human consumption. A description and is expected to be longer and more detailed than a Captioncaption. It Description is a read-write optional property that haswith a cardinality of 0 to many. Description is of type muws-p2-xs:LangType, which is a


645

646

647648649

650

651652

653

654

655656

657

658

659

660661662663664665666

667

668669670

671

672

673674675676

5556

57


Same comment as section 1. Why a list here?

restriction of xs:string carrying an xml:lang attribute. This attribute contains a language identifier as defined by [RFC3066]. There cannot be more than one Description for the sameper language identifier.

Metadata for Description:

It is Mutable = TrueIt is Modifiable = TrueIts Capability = is "http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Description”

<muws-p2-xs:Version> xs:string</muws-p2-xs:Version> ?

muws-p2-xs:Version is a string representing the version of the resource being managed. MUWS does not specify how this string is constructed. The version string can be specified by any domain-specific specification that uses MUWS. Version is a an optional property with a cardinality of 0 to1.

Metadata for Version:

It is Mutable = TrueIt is Modifiable = TrueIts Capability = is "http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Description”

3.2 StateThe manageability capability URI for this the State capability ishttp://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/State

3.2.1 DefinitionA resource may exhibit behavior according to one or more state models. The state capability provides a way in which theseto expose the states of a manageable resource are exposed. This is a pattern that can be applied to any type of state models that a resource can exhibitmight employ. The example used in this section is for themodels the operational states of a manageable resource.

A single definition of an operational state model will not be sufficient for all types of resource., and tThise State capability is a means to allow different various state models to be used by differentamong manageable resources. To promote interoperability, it is a goal that there should be a very limited set of well defined state models. These state models themselves are not defined in the MUWSis specification. Each state model is identified by a URI, and the URI of the state model used by the resource is available exposed through via a some resource property.

This capability does not define any specific property, operation or event. A manageability endpoint is said to provide this capability if the endpoint exposes at least one property exposes state information, and, that follows the pattern described in section 3.2.3.2 for exposing state information of the resource.

3.2.2 Describing State ModelsEach state in a state-machine has a well-defined meaning. and Iit is possible to reuse state definitions in different state machines. States are identified by an element with a particular QName, using the taxonomy scheme defined in section .


677678679

680

681682683

684

685

686687688689

690

691692693

694

695696

697

698699700701702

703704705706707708

709710711712

713

714715716

5859

60

States in the state model may have duration. Transitions between states are considered to be instantaneous.

States can have sub-states that must MUST be wholly contained within a higher-level state.

A state model may also define an operations that can be used to affect some of the transitions in the model. Note that a transitions may also occur as a result of some internal or external event on the resource.

Each state machine has an associated resource property element that exposingprovides a read-only view of the current state of the state machine. Therefore, a client cannot change a resource state by modifying a state resource property.

There may be more than one possible transition between two states in the state model. The individual transitions between states are identified by a URI to and allow, for example, to send a notifications of state transitions, or, to , for example, to identify which transition occurred.

Figure 3 shows a simple state model that is used as an example in this section – it does not constitute the specification of a recommended state model.

Down

Stopped

Failed Up

Stopped

Failed stop()

start()

[failed]

stop()

Figure 3: Example Operational State Model

In tThis example, the state machine is identified by URI http://example.com/StateModels/SimpleOperationalState, bound to namespace prefix exns.

The state model has four states, represented by elements with a particular QName, as follows: exns:Down

This QName corresponds to the “Down” state in the UML diagram. A resource in this state is unable to perform any of its functional tasks.

exns:Stopped

This element QName corresponds to the “Stopped” sub-state of the “Down” state in the UML diagram. Since this state is a sub-state of the “Down” state, it follows that aA resource in the this "Stopped" sub-state is unable to perform any of its functional tasks (since this state is a sub-state of the “Down” state). The A manageable resource exposing this state model can be started from this statethe "Stopped" sub-state.


717718

719

720721722

723724725

726727728

729730

731732

733734

735736737738

739

740741742743744

6162

63

exns:Failed

This element QName corresponds to the “Failed” sub-state of the Down state in the UML diagram. Since this state is a sub-state of the “Down” state, it follows that aThe resource has failed and (since this is a sub-state of the “Down” state) a resource in thisin the "Failed" sub-state is unable to perform any of its functional tasks. The A manageable resource exposing this state model can not be started directly from the “Failed” sub-state. – itSuch a resource must first be movedtransition to the “Stopped” sub-state.

exns:UpThis QName corresponds to the “Up” state in the UML diagram. A resource in this state is able to perform at least some of its functional tasks.

3.2.3 Information Markup Declarations

3.2.3.1 Representation of States

A Sstate, ass in represented in a state model may be a top level state, or nested within another state,s in some defined taxonomy. MUWS defines a way to represent a type/category and its taxonomy lineage, but actual definition of the categories is resource management model specific and therefore not defined by MUWS. In other words, MUWS specifies only the mechanism to convey a type or /category in XML. The MUWS mechanism applied to states is defined as follows.

StateType XML Schema type is declared as follows

<xs:complexType name=”StateType”> <xs:complexContent> <xs:extension base=”muws-p2-xs:CategoryType”/> </xs:complexContent></xs:complexType>

The StateType is used to declare XML elements which containing instances of states.

The A states MUST be declared as follows:.

An XML element is declaring ed the which QName of which identifies the semantics of a the state.

The XML element MUST be declared withhas an XML Schema type which is StateType, or a restriction of StateType.

The contents of the XML element MUST be either:

The only one XML element which correspondings to the state that contains the currently declared state. , iIn other words, the currently declaredthis state is a sub-state of another state.

Or anThe empty sequence. , if This case occurs if this currently declared state is not a sub-state of another state.

For example, the “Failed” state in the example above is a sub-state of the “Down” state. An instance of the “Failed” state may be represented, using the rules described above, in by the following XML fragment by using the rules described above.:

<my:StateTypeInstanceElement xsi:type=”StateType”> <exns:Failed> <exns:Down/> </exns:Failed></my:StateTypeInstanceElement>


745

746747748749750751752753754

755

756

757758759760761762

763

764765766767768

769

770

771772

773774

775

776777778

779780

781782783

784785786787788

6465

66

3.2.3.2 Representation of current state

MUWS defines the following Global Element Declaration (GED) to represent an instance of a state:

<muws-p2-xs:State>muws-p2-xs:StateType</muws-p2-xs:State>

The State element provides a representation of the state of the a manageable resource. It The State element follows the convention for the muws-p2-xs:CategoryType type described in section . which This convention allows the rendering of for a hierarchy of states and sub-states to be rendered. The state values are defined in the operational state model for the resource. This specification does not define the operational state model for any resource.

3.2.3.3 Representation of last state transition

MUWS defines the following Global Element Declaration (GED) to which contains an XML representation of the most recenta change of state in a state model.

<muws-p2-xs:StateTransition Time“xs:dateTime” TransitionIdentifier=” xs:anyURI”?> <muws-p2-xs:EnteredState>muws-p2-xs:StateType</muws-p2-xs:EnteredState> <muws-p2-xs:PreviousState>muws-p2-xs:StateType</muws-p2-xs:PreviousState>? <muws-p2-xs:TransitionIdentifier> xs:anyURI </muws-p2-xs:TransitionIdentifier>? {any} *</muws-p2-xs:StateTransition>

muws-p2-xs:StateTransition is used for representing information about a state change.

muws-p2-xs:StateTransitionChangeNotification/@Time attribute indicates the time at which the transition occurred (transitions are assumed to be instantaneous). It This attribute is REQUIRED.

muws-p2-xs:StateTransition/@TransitionIdentifier attribute indicates the actual transition that occurred. This element is OPTIONAL and may be omitted where, for example, there is only one transition between the EnteredState and the PreviousState.

muws-p2-xs:StateTransitionChangeNotification/muws-p2-xs:EnteredState element indicates which state has been entered during the transition. It This element is REQUIRED.

muws-p2-xs:StateTransitionChangeNotification/muws-p2-xs:PreviousState element indicates the state that the resource was in immediately prior to the state change occurring. This element is OPTIONAL to allow for the time between the state model being created in some initial state (for example when the resource is created) and the time of the transition from that initial state.

StateChangeNotification/TransitionIdentifier element indicates the actual transition that occurred. This element is optional and may be omitted where, for example, there is only one transition between the EnteredState and the PreviousState.

Properties

This capability does not define any property of its own.

A capability that defines a state model should define a resource property through which the state is exposed, and it is recommended to also define a resource property for the last state transition.


789

790791

792

793794795796797

798

799800

801802803804805806807808809810811

812

813814815

816817818

819820

821822823824825

826827828

829

830

831832

6768

69


I don’t understand what you’re suggesting here? We have a capability that has not properties in it? What about the 2 that you just defined – state and statetransition? I agree that the state values should be defined by the managed resource owner. But how would the manager know where to go to get the state information if it doesn’t know what it should ask for? We have to agree on a normative operation name to get the state information.

The property used to expose the state must contain the muws-p2-xs:State complex element. The name of the property can be any name meaningful to the state model defined in the capability. There may be multiple state capabilities, and therefore multiple state properties for a resource. The metadata for this property should include the possible values, i.e. it provides a listing of the states that exist in the state model.

The property to represent the last transition, if such a property is provided, must contain the complex element muws-p2-xs:StateTransition. The name of the last transition property can be any name meaningful to the state model. There may be multiple state capabilities and multiple properties showing the last transition.

3.2.3.4 Example

Examples of these resource properties for an operational state capability could be specified as follows:

<foo:OperationalState><muws-p2-xs:State>...</muws-p2-xs:State>

</foo:OperationalState><foo:LastOperationalStateTransition><muws-p2-xs:StateTransition>...</muws-p2-xs:StateTransition>

</foo:LastOperationalStateTransition>?

The following fragment provides an example from a resource properties instance document containing the properties defined in this example:

<foo:OperationalState> <muws-p2-xs:State> <exns:Failed><exns:Down/></exns:Failed> </muws-p2-xs:State></foo:OperationalState><foo:LastOperationalStateTransition> Time=”2004-03-11T11:30:56Z”> <muws-p2-xs:StateTransition Time=”2004-03-11T11:30:56Z”TransitionIdentifier=”http://example.com/SimpleOperationalState/T/Failed”>> <muws-p2-xs:EnteredState> <exns:Failed><exns:Down/></exns:Failed> </muws-p2-xs:EnteredState> <muws-p2-xs:PreviousState> <exns:Up/> </muws-p2-xs:PreviousState> <muws-p2-xs:Transition> http://example.com/SimpleOperationalState/Transition/UpToFailed </muws-p2-xs:Transition> </muws-p2-xs:StateTransition></foo:LastOperationalStateTransition>

In this example, the foo:OperationalState property contains the current operational state of the resource, using the muws-p2-xs:State element defined in section 3.2.3.2. The foo:LastOperationalStateTransition property contains a description of the most recent operational state transition for the resource, using the muws-p2-xs:StateTransition element defined in section 3.2.3.2.

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


833834835836837

838839840841

842

843844

845846847848849850

851852

853854855856857858859860861862863864865866867868869870871872

873874875876877

878

879880881

7071

72

3.2.5 EventsIt is recommended that resources send notifications on transitions between states. If they do then the notification message must contain at least the XML element for the new value of the state (muws-p2-xs:EnteredState).

To obtain events about certain state transitions, subscribers can use a Selector on the notification subscription to select only those events which contain the required “muws-p2-xs:TransitionIdentifier” element or combination of “muws-p2-xs:EnteredState” and “muws-p2-xs:PreviousState” elements in the notification content. The Selector mechanism is described in [WSN].

To filter for events about entry into a particular state or set of states, a Selector expression based on the “muws-p2-xs:EnteredState” element can be used. To filter for events about exit from a particular state or set of states a Selector expression based on the “muws-p2-xs:PreviousState” element can be used.

3.3 Operational StatusThe manageability capability URI for this capability ishttp://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/OperationalStatus

3.3.1 DefinitionThe operational status capability defines a simple representation of the availability of the resource independent of the specific state model used. For this purpose an operational status property is defined which reflects whether the resource is available, unavailable or degraded. The status does not conform to a specific state model: each value may correspond to more than one state in the operational state model, and conversely more than one status value may correspond to a single state in the operational state model.

Figure 4 shows the UML representation of the Operational Status capability.

OperationalStatus[1]

MUWS:OperationalStatus-OperationalStatus

MUWS:OperationalStatus

Figure 4: Operational Status

3.3.2 PropertiesThe resource state properties, or elements, are specified as follows:

<muws-p2-xs:OperationalStatus> Available|PartiallyAvailable|Unavailable|Unknown</muws-p2-xs:OperationalStatus>

The following fragment provides an example from a resource properties instance document containing this property:

<muws-p2-xs:OperationalStatus>Available</muws-p2-xs:OperationalStatus>

The OperationalStatus property is of type OperationStatusType. The type is a restriction of xs:string that gives a simple indication of the availability of the resource, independent of the potentially complex operational state model. This property is read-only, mutable and mandatory with a cardinality of 1. The valid values are:wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 25 of 68

882

883884885

886887888889890

891892893894

895

896897

898

899900901902903904

905

906907

908

909

910911912

913914

915

916917918919

7374

75


I disagree that this would be independent. I think it would be dependent but not a direct mapping to the state value.


Capitalize this.

Available: This value indicates that the resource is operating normally within any configured operating parameters, and is able to perform all of its functional tasks.

PartiallyAvailable: This value indicates that the resource is operating, but it is outside normal operating parameters. A resource with this operational status is able to perform some, but not all, of its functional tasks. The resource may, for example, be in the process of starting, or lacking resources.

Unavailable: This value indicates that the resource is not operating, and is not able to perform any of its functional tasks. The resource may have been stopped, or may have failed.

Unknown: This value indicates that the resource is unable to report its status at this time.Metadata for OperationalStatus:

It is Mutable = TrueIt is not Modifiable = FalseIts Capability = is "http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/OperationalStatus”

3.4 MetricsThe manageability capability URI for this capability ishttp://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Metrics

3.4.1 DefinitionMetrics are a specific type of property. Metrics represent collected values and have a related collection period.

The goal of this section is to describe the characteristics of a typical property used to represent collected numerical data, called Metrics. A common characteristic of metrics is that they change over time.

Figure 5 presents the Metrics capability in context.

CurrentTime[1]

MUWS::Metrics-CurrentTime

MUWS::Metrics

Figure 5: MUWS metrics

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

3.4.2 Information Markup DeclarationsThe following schema fragment declares the (reusable) data type used to expose the metrics of the resource. All attributes defined in the MetricAttributes attribute group are optional.

<xs:attributeGroup name="MetricAttributes"><xs:attribute name="ResetAt" type="xs:dateTime"/><xs:attribute name="LastUpdated" type="xs:dateTime"/>


920921922923924925926927928929930

931932933934

935

936937

938

939940

941942943

944

945946

947948949950951952953

954

955956

957958959

7677

78

<xs:attribute name="Duration" type="xs:duration"/></xs:attributeGroup>

(MetricAttributes) attribute group MUST be included in every metric type or metric property element declaration.

(MetricAttributes)/ResetAt indicates the time when a particular metric was reset. If a reset capability is supported for the metric, this attribute MUST be included with the metric property. If this metric can not be reset or a reset capability is not supported, this attribute MUST NOT be present. Properties having a TimeScope of PointInTime MUST NOT include this attribute. If the attribute value does not include a time zone indication (or Z for UTC), the value MUST be interpreted as UTC.

(MetricAttributes)/LastUpdated indicates the last update time of a metric value. If the value does not include a time zone indication (or Z for UTC), the value MUST be interpreted as UTC.

(MetricAttributes)/Duration indicates the time over which the metric value was collected, counted, or measured. The Duration attribute MUST be included for metrics having a TimeScope of Interval or SinceReset, and MUST NOT be included for metrics having a TimeScope of PointInTime.

The following metric type definition is an example of how the metrics attributes are incorporated into a metric type. All metric types MUST incorporate the MetricAttributes attribute group.

<xs:complexType name="MyExampleIntegerMetricType"> <xs:simpleContent> <xs:extension base="xs:integer"> <xs:attributeGroup ref="muws-p2-xs:MetricAttributes"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:extension> </xs:simpleContent> </xs:complexType>

The following shows an example instance of this example metric type.

<MyIntegerMetric LastUpdated=”2004-03-11T11:30:56Z” Duration=”PT1H”> 12345</MyIntegerMetric>

3.4.3 MetadataThe following metadata is applicable to all properties that are metrics:

They are Mutable = TrueThey are not Modifiable = FalseTheir Capability = is "http://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Metrics"

Other metadata elements applicable for metrics are : Units, ChangeType, TimeScope, GatheringTime, CalculationInterval. See section 2.3.2 for a description of these metadata elements.The following metadata elements are defined for metric-type properties :

<muws-p2-xs:ChangeType>Counter|Gauge|Unknown</muws-p2-xs:ChangeType>

muws-p2-xs:ChangeType is an enumeration for indicating how changes to the associated metric value should be interpreted by the consumer. A property representing a metric MUST include a single instance of ChangeType in its metadata description. Each ChangeType value is interpreted as follows:


960961

962963

964965966967968969

970971

972973974975

976977

978979980981982983984985

986

987988989990991

992

993

994995996

997998999

1000

1001100210031004

7980

81

Counter - the value of the metric increments over successive counts, collections, or measurements.

Gauge - the value of the metric varies between a range of values. Unknown - the change behavior is not known or cannot be described.

<muws-p2-xs:TimeScope>Interval|PointInTime|SinceReset</muws-p2-xs:TimeScope>

muws-p2-xs:TimeScope is an enumeration for indicating if there is some interval, over which the data is collected, counted, or measured. A property that is a metric MUST include a single instance of TimeScope in its metadata description. Each TimeScope value is interpreted as follows:

Interval - the value of the metric is collected over some time interval. In this case the Duration attribute MUST be reported with the metric property. The value of the Duration attribute is the time, from the beginning of the interval, to the end of the interval. The Duration is usually remains the same for every reading of the metric.

PointInTime - the value of the metric is counted, collected, or measured at a single instant in time. The Duration attribute MUST NOT be reported with metrics having a TimeScope value of PointInTime. Metrics with a TimeScope value of PointInTime do not support the reset capability and MUST NOT include the ResetAt attribute.

SinceReset - the value of the metric is collected since reset, or since the manageable resource started collecting metrics data. In this case the Duration attribute MUST be reported with the metric property. The value of the Duration attribute is the time since the metric was reset, or since the resource started collecting metrics data, if no reset has occurred. Thus the value of Duration may report a different value for each retrieval of the property.

<muws-p2-xs:gatheringTime>OnChange|Periodic|OnDemand|Unknown

</muws-p2-xs:gatheringTime>

muws-p2-xs:GatheringTime is an enumeration indicating at what times the value of the metric is counted, collected, or measured. A property that is a metric MUST include a single instance of GatheringTime in its metadata description. Each GatheringTime value is interpreted as follows:

OnChange - the value of the metric is updated whenever a change occurs to the quantity measured.

Periodic - the value of the metric is updated on a regular basis. OnDemand - the value of the metric is updated when there is a request for the metric

value. Unknown - it is unknown when the metric value is updated.

<muws-p2-xs:CalculationInterval>xs:duration</muws-p2-xs:CalculationInterval>

muws-xs-p2:CalculationInterval represents the interval at which the metric is gathered or calculated by the resource. The value of the metric is not updated during a calculation interval.

<muws-p2-xs:MetricGroup>xs:anyURI</muws-p2-xs:MetricGroup>

muws-p2-xs:MetricGroup indicates that the metric property is a member of a group of metrics. A metric property MAY be a member of zero or more metric groups. A metric group is identified by a URI. Each property included in a metric group SHALL have a MetricGroup element containing an identical URI. A property that is a metric MUST include zero or more MetricGroup wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 28 of 68

1005100610071008

1009

10101011

101210131014101510161017101810191020102110221023102410251026102710281029

1030

103110321033

103410351036103710381039104010411042

1043

10441045

10461047

1048

1049

1050105110521053

8283

84


Delete this..


Change to “in a”

elements in its metadata description. Each MetricGroup element represents a membership in a metric group.

3.4.4 PropertiesThe following provides the specification of a resource metrics property.

<muws-p2-xs:CurrentTime>xs:dateTime</muws-p2-xs:CurrentTime>

Muws-p2-xs:CurrentTime contains the time the property was retrieved from the manageable resource. This property is useful to manageability consumers when analyzing time values received from a manageability endpoint in the absence of a time synchronization mechanism. It is a read-only mandatory property that has a resource cardinality of 1.

The Metrics capability requires the CurrentTime property to be present in the resource properties, and provides a reference point for time-based attributes as defined by metric data types. Note that CurrentTime is not a metric. Rather, it is a property of type xs:dateTime defined as part of the “Metrics” capability, consequently, reset operations, if any, have no effect on CurrentTime.

3.4.5 EventsNo specific notification topics are defined by the Metrics capability. WS-ResourceProperties specifies the ability to optionally define topics for resource properties that can emit notifications when their value changes. These topics allow a client to request notifications for the update of individual metrics properties

This document defines notification topics for every manageability capability. Subscribing to the topic for a resource-specific metrics manageability capability allows a client to receive all notifications associated with that manageability capability, including property value change notifications.

3.5 ConfigurationThe manageability capability URI for this capability ishttp://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Configuration

3.5.1 DefinitionConfiguration properties are those whose values impact the behavior of the resource.

Configuration property values may be changed directly by a set or changed as a side effect of another operation.


10541055

1056

1057

1058

1059106010611062

1063106410651066

1067

1068106910701071

1072107310741075

1076

10771078

1079

1080

10811082

8586

87


Where is the rest?

4 Capabilities applicable to management in general

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

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

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

Figure 6: Relationship conceptual model

Note that this capability is not limited to manageable resources and can be exposed by any resource that wants to expose relationships that it knows about.

Figure 7 is a UML representation of the relationship capability.


1083

1084

1085108610871088108910901091109210931094

1095

10961097

1098

10991100110111021103110411051106

11071108

11091110

1111

8889

90

QueryRelationshipsByType()

Relationship[1]<<event>> RelationshipCreated[0..1]<<event>> RelationshipDeleted[0..1]

MUWS::Relationship

+QueryRelationshipsByType()

-Relationship-<<event>> RelationshipCreated-<<event>> RelationshipDeleted

MUWS::Relationship

Figure 7: Relationship capability

There is an assumption that the resources are well behaved and creating relationships in good faith. Relationships may also be out of date. Before relationships are relied upon, they should be

validated either manually or automatically. It should also be considered if the resource being related should be visible for security reasons.

4.1.2 Information Markup Declarations

4.1.2.1 Representation of Categories of Relationships

Relationships could be categorized. That is each relationship is of certain type/category which describes the semantics of the relationship. One type/category may be a specialization or generalization of another type/category. This defines taxonomy of relationship categories. WSDM defines a way to represent a type/category and its taxonomy lineage, but actual definition of the categories is resource management model specific and therefore not defined by WSDM. In other words, WSDM specifies only the mechanism to convey a type/category in XML. The WSDM mechanism applied to relationship types/categories is defined as follows.

RelationshipTypeType XML Schema type is declared as follows

<xs:complexType name=”RelationshipTypeType”> <xs:complexContent> <xs:extension base=”muws-p2-xs:CategoryType”/> </xs:complexContent></xs:complexType>

The RelationshipType is used to declare XML elements which contain instances of relationship type/category information.

The relationship type/category information MUST be declared as follows.

An XML element is declared which QName identifies the semantics of a relationship type/category.

The XML element MUST be declared with the XML Schema type which is a restriction of RelationshipType.

The contents of the XML element MUST be either

The only one XML element which corresponds to the generalization of the currently declared relationship type/category

Or empty sequence, if currently declared relationship type/category does not have any generalizations (top of the taxonomy).

For example, the “USB attached” relationship type/category may be generalized to the “Bus connected” which, in turn, may be generalized to the “Generally linked”. An instance of the “USB attached” relationship type/category information may be represented in the following XML fragment by using the rules described above.

<my:RelationshipTypeInstanceElement xsi:type=”RelationshipType”>


11121113

1114111511161117

1118

1119

1120112111221123112411251126

1127

11281129113011311132

11331134

1135

11361137

11381139

1140

11411142

11431144

1145114611471148

1149

9192

93


Are creating or create

<usb:Attached> <bus:Connected> <generally:Linked/> <bus:Connected> </usb:Attached></my:RelationshipTypeInstanceElement>

4.1.2.2 Representation of an Instance of a Relationship

MUWS defines the following Global Element Declaration (GED) to represent an instance of a relationship.

<muws-p2-xs:Relationship> <muws-p2-xs:Name>xs:string</muws-p2-xs:Name> ? <muws-p2-xs:Type>muws-p2-xs:RelationshipTypeType</muws-p2-xs:Type><muws-p2-xs:Participant> <muws-p2-xs:Role>xs:anyURI</muws-p2-xs:Role>

<muws-p1-xs:ManageabilityEndpointReference/> * <muws-p1-xs:ResourceId/> ? <muws-p2-xs:Role>xs:anyURI</muws-p2-xs:Role>

{any} * </muws-p2-xs:Participant> <muws-p2-xs:Participant/>+ <muws-p2-xs:AccessEndpointReference> wsa:EndpointReferenceType </muws-p2-xs:AccessEndpointReference>? {any} *</muws-p2-xs:Relationship>

muws-p2-xs:Relationship/muws-p2-xs:Name is a human readable name of the relationship. Name should not be used for machine reasoning about the semantics of the relationship. Type should be used instead. This element is OPTIONAL.

muws-p2-xs:Relationship/muws-p2-xs:Type is a type/category which this relationship belongs to. Such as linkage, containment, dependency, etc. MUWS does not define any specific relationship type. This is left to domain-specific models. MUWS only defines a way to convey the type as part of the representation of a relationship. In order to allow relationships to be defined as part of a taxonomy, the mechanism used by MUWS to represent relationship types leverages the muws-muws-p2-xs:CategoryType type defined in section . This element is REQUIRED.

muws-p2-xs:Relationship/muws-p2-xs:Participant contains information about the participant in the relationship. There MUST be at least two participants, but MAY be more.

muws-p2-xs:Relationship/Participant/Role is a URI which identifies the role that the participant plays in the relationship. A participant role MUST be unique within a given instance of the relationship. The set of valid roles is defined by the relationship type. This attribute is REQUIRED.

Relationship/muws-p2-xs:Participant/muws-p1-xs:ManageabilityEndpointReference is a reference to a WSDM manageability endpoint. This GED is defined in part 1. It MAY be included if the participant is WSDM manageable and the provider of this information knows and wishes to indicate that. If more than one manageability endpoint is known, more than one instances of this element may be present.

muws-p2-xs:Relationship/muws-p2-xs:Participant/muws-p1-xs:ResourceID is a WSDM manageable resource identifier which MAY be reported by the provider of the relationship information. This GED is defined in part 1. This information may be used to locate manageability endpoints for this participant or may be used for other purposes. For example, the resource identifier SHOULD be used to express that the provider of the relationship information is also a


115011511152115311541155

1156

11571158

1159116011611162116311641165116611671168116911701171117211731174

117511761177

117811791180118111821183

11841185

1186118711881189

11901191119211931194

11951196119711981199

9495

96

participant of the relationship (by returning its own resource identifier for one of the participants). Obviously, in order for this assertion to work, the provider of the relationship information has to be a WSDM manageable resource.

muws-p2-xs:Relationship/muws-p2-xs:Participant/muws-p2-xs:Role is a URI which identifies the role that the participant plays in the relationship. A participant role MUST be unique within a given instance of the relationship. The set of valid roles is defined by the relationship type. This attribute is REQUIRED.

muws-p2-xs:Relationship/muws-p2-xs:Participant/{any}* is an XML extensibility content which MAY contain elements that further or otherwise describe the participant. For example, when a participant is a Web service endpoint, an EndpointReference element as defined by MOWS MAY be included in the extensibility content to indicate reference to the functional/operational Web service endpoint participant of the relationship.

muws-p2-xs:Relationship/muws-p2-xs:AccessEndpoint is a reference to the Web service endpoint which provides access to this relationship (if available). The endpoint MUST implement the relationship access capability (see section 4.2).

Following is an example of a relationship information instance. The relationship is that a WSDM manageable network host myhost.myorg.org contains an attached SCSI disk which is not manageable by itself, but is exposed as a functional/operational Web service endpoint (e.g. to read/write from the disk). The “containment” is represented by the relationship below:

<muws-p2-xs:Relationship> <muws-p2-xs:Name>SCSI disk attached to the host computer</muws-p2-xs:Name> <muws-p2-xs:Type> <scsi:Attached> <bus:Connected> <generally:Linked/> </bus:Connected> </scsi:Attached> </muws-p2-xs:Type><muws-p2-xs:Participant> <muws-p2-xs:Role>urn:role:bus:host</muws-p2-xs:Role>

<muws-p1-xs:ManageabilityEndpointRefrence> ...EPR1... </muws-p1-xs:ManageabilityEndpointReference> <muws-p1-xs:ResourceID>urn:uuid:123</muws-p1-xs:ResourceID> <muws-p2-xs:Role>urn:role:bus:host</muws-p2-xs:Role>

<netop-xs:HostName>myhost.myorg.org</netop-xs:NostName> </muws-p2-xs:Participant> <muws-p2-xs:Participant> <muws-p2-xs:Role>urn:role:bus:device</muws-p2-xs:Role> <scsi-xs:Port>2</scsi-xs:Port> <scsi-xs:CH>0</scsi-xs:CH> <scsi-xs:BusID>5</scsi-xs:BusID> <scsi-xs:LUN>0</scsi-xs:LUN> <mows-xs:EndpointRefence> ...EPR2... </mows-xs:EndpointReference> </muws-p2-xs:Participant></muws-p2-xs:Relationship>

4.1.3 PropertiesThis capability defines the following property:

<muws-p2-xs:Relationship/> *


120012011202

1203120412051206

12071208120912101211

121212131214

1215121612171218

121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248

1249

1250

1251

9798

99

muws-p2-xs:Relationship is a representation of a relationship of which provider of this capability is aware. See section 4.1.2 for the definition of the Relationship element. The provider of this capability is not necessarily a participant in the relationships represented by this property.

It is not recommended to request all values of the Relationship property with either wsrp:GetResourceProperty or wsrp:GetMultipleResourceProperties operations as there may be too many relationships. It is RECOMMENDED to use wsrp:QueryResourceProperties operation when retrieving the Relationships property. Provider of this manageability capability SHOULD, in general, support wsrp:QueryResourceProperties operation. However, if the provider of this capability knows of just a few relationships, it MAY choose not to support wsrp:QueryResourceProperties operation.

For example, the following request may be sent to retrieve all “Bus connected” relationships which point to devices exposed as Web services.

<soap:Envelope ...> <soap:Header>

... </soap:Header> <soap:Body> <wsrp:QueryResourceProperties> <wsrp:QueryExpression Dialect=”http://www.w3.org/TR/1999/REC-xpath-19991116” >boolean(/*/muws-p2-xs:Relationship/muws-p2-xs:Type/*/bus:Connected and /*/muws-p2-xs:Relationship/muws-p2-xs:Participant[Role=”urn:role:bus:device”]/mows-xs:EndpointReference) </wsrp:QueryExpression> </wsrp:QueryResourceProperties> </soap:Body></soap:Envelope>

4.1.4 OperationsThis capability defines the following message exchanges.

4.1.4.1 QueryRelationshipsByType

This operation is optional and is a shortcut to query the relationships of the same type. The request to perform this operation has the following payload:

<muws-p2-xs:QueryRelationshipsByType><muws-p2-xs:Type>muws-p2-xs:RelationshipTypeType</muws-p2-xs:Type>

+</muws-p2-xs:QueryRelationshipsByType>

muws-p2-xs:QueryRelationshipsByType is a Global Element Declaration (GED) which identifies the operation requested.

muws-p2-xs:QueryRelationshipsByType/muws-p2-xs:Type is a category which the relationship belongs to. Such as containment, dependency, etc. The actual markup of the value of this element is described in section 4.1.2.2.

The response to the above request is either a fault (any fault) or the following message.

<muws-p2-xs:QueryRelationshipsByTypeResponse><muws-p2-xs:Relationship/> *

</muws-p2-xs:QueryRelationshipsByTypeResponse>

muws-p2-xs:QueryRelationshipsByTypeResponse is a GED which identifies response to the requested operation. wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 34 of 68

125212531254

1255125612571258125912601261

12621263

126412651266126712681269127012711272127312741275127612771278

1279

1280

1281

12821283

1284128512861287

12881289

129012911292

1293

129412951296

12971298

100101

102

muws-p2-xs:QueryRelationshipByTypeResponse/muws-p2-xs:Relationship is a relationship representation matching one of the requested types (categories). See section 4.1.2.2 for the definition of the relationship element.

4.1.5 EventsTo obtain notifications of changes in relationships, the following notification topics are defined in the manageable relationships capability.

<wstop:TopicSpace name=”ManageableRelationships” targetNamespace=”http://docs.oasis-open.org/wsdm/2004/12/muws/events”> <wstop:Topic name=”RelationshipCreated” messageTypes=”muws-p2-xs:RelationshipCreatedNotification””/><wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116">//muws-p1-

xs:ManagementEvent[count(muws-p2-xs:RelationshipCreatedNotification)=1] </wstop:MessagePattern></wstop:Topic> <wstop:Topic name=”RelationshipDeleted” messageTypes=”muws-p2-xs:RelationshipDeletedNotification”/><wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116">//muws-p1-

xs:ManagementEvent[count(muws-p2-xs:RelationshipDeletedNotification)=1] </wstop:MessagePattern></wstop:Topic></wstop:TopicSpace>

muws-events:ManageableRelationships/muws-events:RelationshipCreated indicates addition of a new relationship. It is recommended to subscribe to this notification with appropriate selector against the contents of the notification message to reduce the notification message volume. The notification message contains at least the following information.

<RelationshipCreatedNotification> <Relationship/></RelationshipCreatedNotification>

muws-events:ManageableRelationships/muws-events:RelationshipDeleted indicates removal of an existing relationship. It is recommended to subscribe to this notification with appropriate selector against the contents of the notification message to reduce the notification message volume. The notification message contains at least the following information.

<RelationshipDeletedNotification> <Relationship/></RelationshipDeletedNotification>

4.2 Relationship Access CapabilityThe manageability capability URI for this capability ishttp://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/RelationshipAccess

4.2.1 DefinitionThe capability to access a relationship is defined here. The provider of the Web service endpoint that supports this capability also provides access to the relationship. If this capability is supported, the endpoint reference for the service implementing it MUST contain sufficient information to allow the provider of this capability to disambiguate which relationship is being accessed by the message exchanges. The endpoint reference could be obtained from the Relationship/acccessEndpointReference in relationship element defined in section 4.1.2.2.wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 35 of 68

129913001301

1302

13031304

13051306130713081309131013111312131313141315131613171318131913201321

1322132313241325

132613271328

1329133013311332

133313341335

1336

13371338

1339

134013411342134313441345

103104

105

In general, this capability is not more specific than what is described above. That is, an endpoint MAY support any message exchanges it needs to provide access to the relationship. The message exchanges may entirely be management model specific.

The only other normative requirement is that if the relationship lifecycle is to be exposed by the provider of this capability, then the Web service endpoint MUST implement WS-ResourceLifetime specification [WS-RL].

4.3 Relationship Resource CapabilityThe manageability capability URI for this capability ishttp://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/RelationshipResource

4.3.1 DefinitionA Web service endpoint, in addition to providing access to the relationship as described in section 4.2, may also represent the relationship. Representing the relationship means that an endpoint is able to provide relationship information as described in section 4.1.2.2. In this case, the Web service endpoint MUST be a WS-Resource, as defined by the WSRF, and one such WS-Resource provides information about one relationship instance. Representing relationships as WS-Resources is useful when a manageability model defines additional properties, operations and/or events for a given relationship.

In order to represent a relationship as a WS-Resource, a set of properties is normatively required. The rest is up to the relationship manageability model and the discretion of the provider of the WS-Resource and the relationship.

Figure 8 is a UML representation of the Relationship Resource capability.

Name[0..1]Type[1]Participant[2..*]

MUWS::RelationshipResource-Name-Type-Participant

MUWS::RelationshipResource-Role-ManageabilityEndpointReference-ResourceId

MUWS::Participant

Figure 8: Relationship Resource capability

4.3.2 PropertiesThis capability defines the following properties.

<muws-p2-xs:Name>xs:string</muws-p2-xs:Name> ?

muws-p2-xs:Name is an element as defined by the Relationship/Name in section 4.1.2.2. It is optional.

<muws-p2-xs:Type>muws-p2-xs:RelationshipTypeType</muws-p2-xs:Type>

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

<muws-p2-xs:Participant><muws-p2-xs:Role>xs:anyURI</muws-p2-xs:Role>


134613471348

134913501351

1352

13531354

1355

1356135713581359136013611362

136313641365

1366

13671368

1369

1370

1371

13721373

1374

1375

13761377

1378

13791380

106107

108

<muws-p1-xs:ManageabilityEndpointReference/> * <muws-p1-xs:ResourceId/> ?<muws-p2-xs:Role>xs:anyURI</muws-p2-xs:Role>

{any} *</muws-p2-xs:Participant>

muws-p2-xs:Participant is an element as defined by the Relationship/Participant in section 4.1.2.2. It appears at least twice (one per participant in the relationship).

4.4 AdvertisementThe manageability capability URI for this capability ishttp://docs.oasis-open.org/wsdm/2004/12/muws/capabilities/Advertisement

4.4.1 DefinitionThe “advertisement” capability is exposed by Web services that are able to provide notification on creation and/or destruction of manageable resources. Since one cannot register for notification on a resource before the resource is created, the creation events reported by the implementer of the “lifetime notification” capability necessarily apply to other resources than those represented by the Web service on which the registration was done.

Note that this capability is not only implementable by manageable resources (see the distinction between “manageability capability” and “management-related capability” in section 4). A service might offer the capability to notify on creation/destruction of resources even though the service itself is not manageable. For example, if a system included a registry to which resources are added as soon as they are created and from which they are removed when they are destroyed, this registry could expose the “advertisement” capability and use it to share the information about resource creation/destruction with managers.

This capability does not define any property or operation, but it defines four topics used for notification.

An example of use of this capability would be for a container (e.g. a J2EE server, a business process execution engine, etc) to expose it to advertise the fact that it can notify a manager when a resource (in this example a resource contained by the container) is created.

Figure 9 is a UML representation of the Advertisement capability.

<<event>> ManageabilityEndpointCreation[0..1]<<event>> ManageableResourceCreation[0..1]<<event>> ManageabilityEndpointDestruction[0..1]<<event>> ManageableResourceDestruction[0..1]

MUWS::Advertisement-<<event>> ManageabilityEndpointCreation-<<event>> ManageableResourceCreation-<<event>> ManageabilityEndpointDestruction-<<event>> ManageableResourceDestruction

MUWS::Advertisement

Figure 9: Advertisement capability

4.4.2 EventsThis capability defines a topic space containing four notification topics:

<wstop:TopicSpace name=”AdvertisementTopicSpace” targetNamespace=”http http://docs.oasis-open.org/wsdm/2004/12/muws/ wd-wsdm-muws-events-1.0.xml”>


13811382138313841385

13861387

1388

13891390

1391

13921393139413951396

1397139813991400140114021403

14041405

140614071408

1409

14101411

1412

1413

141414151416

109110

111


Delete this.


I would use a stronger word here like “exclusively” to make the point more clear.

<wstop:Topic name=”ManageabilityEndpointCreation” messageTypes=”muws-p2-xs:CreationNotification”><wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116">//muws-p1-

xs:ManagementEvent[count(muws-p2-xs:CreationNotification)=1] </wstop:MessagePattern> <wstop:Topic name=”ManageableResourceCreation” messageTypes=”muws-p2-xs:CreationNotification”/> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116">//muws-p1-xs:ManagementEvent[count(muws-p2-xs:CreationNotification)=1] </wstop:MessagePattern> </wstop:Topic> </wstop:Topic> <wstop:Topic name=”ManageabilityEndpointDestruction”

messageTypes=”muws-p2-xs:DestructionNotification”><wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116">//muws-p1-

xs:ManagementEvent[count(muws-p2-xs:DestructionNotification)=1]</wstop:MessagePattern>

<wstop:Topic name=”ManageableResourceDestruction” messageTypes=”muws-p2-xs:DestructionNotification”/> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116">//muws-p1-xs:ManagementEvent[count(muws-p2-xs:DestructionNotification)=1] </wstop:MessagePattern> </wstop:Topic> </wstop:Topic></wstop:TopicSpace>

The “muws-events:ManageabilityEndpointCreation” topic corresponds to notification on creation of a new manageability endpoint for a resource. This could be because the resource was just created along with a manageability endpoint or the resource itself could have been creating some time in the past. In this case, this notification means that a new manageability endpoint for the resource was created. This new manageability endpoint could be the first one for the resource or be in addition to existing ones. The associated muws-p2-xs:CreationNotification message contains the EPR of the newly created manageability endpoint.

The “muws-events:ManageableResourceCreation” topic is a specialization of the “Manageability EndpointCreation” topic. This topic corresponds to the case where the resource itself is newly created. Note that if a resource is created that is not manageable (i.e. which does not have a manageability endpoint) no notification on this topic will be returned. But if, along with the resource being created, a manageability endpoint for the resource is created then a notification will be sent to subscribers on this topic.

The “muws-events:ManageabilityEndpointDestruction” topic corresponds to notification on destruction of a manageability endpoint. It does not imply that the associated resource was destroyed. The associated muws-p2-xs:DestructionNotification message contains the muws-p2-xs:ResourceId that the newly destroyed manageability endpoint was providing for the resource before being destroyed.

The “muws-events:ManageableResourceDestruction” topic is a specialization of the “ManageabilityEndpointDestruction” topic. This topic corresponds to the case where the resource itself is being destroyed at the same time as the manageability endpoint. Note that if a resource is being destroyed that was not manageable (that didn’t have a manageability endpoint) no notification on this topic will be sent. The associated muws-p2-xs:DestructionNotification message contains the muws-p2-xs:ResourceId that the newly destroyed manageability endpoint was providing for the resource before being destroyed.

The content elements for these topics are so described:wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 38 of 68

14171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445

1446144714481449145014511452

145314541455145614571458

14591460146114621463

1464146514661467146814691470

1471112113

114

<muws-p2-xs:CreationNotification"> <muws-p1-xs:ManageabilityEndpointReference"/> *</muws-p2-xs:CreationNotification">

Muws-p2-xs:CreationNotification/muws-p1-xs:ManageabilityEndpointReference is a reference to the manageability endpoint of the newly created resource. There can be more than one such reference if there is more than one known manageability endpoint.

<muws-p2-xs:DestructionNotification"> <muws-p1-xs:ResourceId"/> ?</muws-p2-xs:DestructionNotification">

Muws-p2-xs:DestructionNotification/muws-p1-xs:ResourceId is the ResourceId of the newly destroyed resource.


147214731474

147514761477

1478

147914801481

14821483

1484

115116

117

5 Discovery Many forms of discovery are supported by Web services. This specification does not prescribe a normative method for discovering manageability services. It is expected that discovery methods commonly used for Web services will be used as discovery methods for manageability services. The goal of discovery is to obtain the EPR of a manageability endpoint. The Advertisement capability (section 4.4), when supported, provides ways to facilitate discovery. This section also describe two other ways to discover manageable resources. These are just some of the discovery methods that can be used.

There exists but one normative requirement relative to discovering manageability services, as follows: A manageability service MUST provide the Identity capability as defined by MUWS. As a result of this requirement, a consumer can inspect the WSDL description for a Web service or attempt to use the Identity capability of the Web service and determine if the discovered service acts as a manageability service. If the discovered service provides the Identity capability defined by MUWS, then it is a manageability service.

5.1 Discovery using RelationshipsThere are at least two scenarios in which relationships are used in discovering manageable resources.

One approach is when manageable resources point to other manageable resources throught relationships: manageable resources that support the Relationship capability enable discovery of the EPRs of manageable resources that are participants in the relationship. This is done by using the “Relationship” property defined in section 4.1.3 or invoking the operations defined in section 4.1.4 that may provide as part of the response message EPRs of other resources.

The second scenario is when the consumer has access to WS-Resources representing relationships and these relationships have manageable resources as members. The consumer can then use the properties of the Relationship Resource capability to retrieve the EPRs of the member manageable resources.

5.2 Discovery using RegistriesIn addition to emitting the notifications on creation and destruction defined as part of the Advertisement capability (section 4.4), resources can be advertised actively to specific registries by invoking a registration interface. They can then be discovered by consumers invoking the query interface of these registries.

The WSRF WS-Service Group specification [WS-SG] defines a type of registry, along with the message exchanges used to interact with registries of this type. It is RECOMMENDED that registries used to discover manageable resources conform to the WS-Service Group specification and to the following additional constraints:

The service group SHOULD include as properties the following two elements:

<wssg:MembershipContentRule MemberInterface=”muws-p1-xs:Identity” ContentElements=”muws-p1-xs:ResourceId”><wssg:MembershipContentRule MemberInterface=”muws-p1-xs:ManageabilityCharacteristics” ContentElements=”muws-p1-xs:ManageabilityCapability”>


1485

1486148714881489149014911492

149314941495149614971498

1499

15001501

15021503150415051506

1507150815091510

1511

1512151315141515

1516151715181519

1520

152115221523152415251526

118119

120


Typo - through


“only” or still a manageability service even if it provides other capababilities?


Not needed. Replace it with a “—“.


Typo - “describes”

The service group MAY also have any other “MembershipContentRule”, including the rule with an empty value for both MemberInterface and ContentElements, in effect lifting any constraint on the members of the service group. The two membership content rules defined above are useful even in a service group with no effective constraint because they allow querying the service group on the “ResourceId” and “ManageabilityCapability” properties.

When adding a manageability endpoint for a resource to the membership of a service group using the “Add” operation, the requestor SHOULD include the muws-p1-xs:ResourceId element of the manageable resource in the wssg:Add/wssg:Content element of the request, even if the service group supports additional membership content rules that would have permitted registration of the manageability endpoint in the service group without providing this content element. Similarly, if the manageable resource supports the Manageability Characteristics capability, the requestor SHOULD include all the muws-p1-xs:ManageabilityCapability elements of the manageable resource in the wssg:Add/wssg:Content element of the request, even if the service group supports additional membership content rules that would have permitted registration of the manageability endpoint in the service group without providing this content element

Like all manageability endpoints, the manageability endpoints registered in a resource registry MUST implement the Identity capability defined in [MUWS Part 1]. In addition, in order to facilitate discovery, they SHOULD implement the Manageability Characteristics capability also defined in [MUWS Part 1].


15271528152915301531

15321533153415351536153715381539154015411542

1543154415451546

1547

121122

123

6 References

6.1 Normative[MUWS Part 1] William Vambenepe, Web Services Distributed

Management:Management using Web Services (MUWS 1.0) Part 1, OASIS Committee Draft, December 2004, http://docs.oasis-open.org/wsdm/2004/12/cd-wsdm-muws-part1-1.0.pdf

[XML1.0 3rd Edition]Tim Bray, et al., Extensible Markup Language (XML) 1.0 (Third Edition), W3C Recommendation, February 2004, http://www.w3.org/TR/REC-xml

[XML Schema Part 1]Henry S. Thompson, et al. XML Schema Part 1: Structures, W3C Recommendation, May 2001, http://www.w3.org/TR/xmlschema-1/

[XML Schema Part 2]Paul V. Biron, et al. XML Schema Part 2: Datatypes, W3C Recommendation, May 2001, http://www.w3.org/TR/xmlschema-2/

[WSDL1.1] Erik Christensen, et al., Web services Description Language (WSDL)

1.1, W3C Note, March 2001, http://www.w3.org/TR/wsdl

[WS-Resource] Steve Graham, et al. Web Service Resource 1.2 (WS-Resource), OASIS Working Draft, October 2004, http://www.oasis-open.org/apps/org/workgroup/wsrf/download.php/9547/wsrf-WS-Resource-1.2-draft-01.doc

[WS-Addressing] Don Box, et al., Web services Addressing (WS-Addressing), W3C Member Submission, August 2004, http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/

[WS-RP] Steve Graham, et al., Web Services Resource Properties 1.2 (WS-ResourceProperties), OASIS Working Draft, June 2004, http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-04.pdf

[XPath 1.0] James Clark, et al., XML Path Language (XPath) Version 1.0, W3C Recommendation, November 1999, http://www.w3.org/TR/1999/REC-xpath-19991116


1548

1549

1550155115521553

1554155515561557155815591560156115621563156415651566156715681569157015711572157315741575157615771578157915801581158215831584158515861587

124125

126

http://www.w3.org/TR/1999/REC-xpath-19991116

http://www.w3.org/TR/1999/REC-xpath-19991116

http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-04.pdf

http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-04.pdf

http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/

http://www.oasis-open.org/apps/org/workgroup/wsrf/download.php/9547/wsrf-WS-Resource-1.2-draft-01.doc

http://www.oasis-open.org/apps/org/workgroup/wsrf/download.php/9547/wsrf-WS-Resource-1.2-draft-01.doc

http://www.w3.org/TR/wsdl

http://www.w3.org/TR/xmlschema-2/

http://www.w3.org/TR/REC-xml

http://docs.oasis-open.org/wsdm/2004/12/cd-wsdm-muws-part1-1.0.pdf

[WSN] Steve Graham, et al., Web Services Base Notification 1.2 (WS-BaseNotification), OASIS Working Draft, June 2004, http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-03.pdf

[WST] William Vambenepe, Web Services Topics 1.2 (WS-Topics), OASIS Working Draft, Jully 2004, http://docs.oasis-open.org/wsn/2004/06/wsn-WS-Topics-1.2-draft-01.pdf

[RFC3066] IETF (Internet Engineering Task Force). RFC 3066: Tags for the Identification of Languages, ed. H. Alvestrand. 2001, http://www.ietf.org/rfc/rfc3066.txt

[WS-RL] Latha Srinivasan, et al., Web Services Resource Lifetime 1.2 (WS-ResourceLifetime), OASIS Working Draft, June 2004, http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-03.pdf

[WS-SG] Tom Maguire, et al., Web Services Service Group 1.2 (WS-ServiceGroup), OASIS Working Draft, June 2004, http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ServiceGroup-1.2-draft-02.pdf

6.2 Non-normative[WS-RF] WSRF OASIS technical committee,

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrf

[WSRMD] Steve Graham, et al., Web Services Resource Metadata 1.0 (WS-ResourceMetadataDescriptor), OASIS Working Draft, October 2004, http://www.oasis-open.org/committees/download.php/9758/wsrf-WS-ResourceMetadataDescriptor-1.0-draft-01.PDF


1588158915901591159215931594159515961597159815991600160116021603160416051606

1607

1608

1609161016111612161316141615

1616

127128

129

http://www.oasis-open.org/committees/download.php/9758/wsrf-WS-ResourceMetadataDescriptor-1.0-draft-01.PDF

http://www.oasis-open.org/committees/download.php/9758/wsrf-WS-ResourceMetadataDescriptor-1.0-draft-01.PDF

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrf

http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ServiceGroup-1.2-draft-02.pdf

http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ServiceGroup-1.2-draft-02.pdf

http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-03.pdf

http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-03.pdf

http://www.ietf.org/rfc/rfc3066.txt

http://docs.oasis-open.org/wsn/2004/06/wsn-WS-Topics-1.2-draft-01.pdf

http://docs.oasis-open.org/wsn/2004/06/wsn-WS-Topics-1.2-draft-01.pdf

http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-03.pdf

http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-03.pdf

Appendix A. AcknowledgementsThe following individuals were members of the committee when the specification was approved by the technical committee

Guru Bhat, Jeff Bohren, Winston Bumpus, Nick Butler, Brian Carroll, Fred Carter, Michael Clements, David Cox, John DeCarlo, Andreas Dharmawan, Mark Ellison, John Fuller, Paul Lipton, Heather Kreger, Hal Lockhart, Frederico Maciel, Tom Maguire, Bryan Murray, Richard Nikula, Mark Peel, Richard Pelavin, Homayoun Pourheidari, Warren Roberts, Karl Schopmeyer, Igor Sedukhin, David Snelling, Thomas Studwell, William Vambenepe, Andrea Westerinen, Jim Willits, Zhili Zhang.


1617

16181619

162016211622162316241625

130131

132

Appendix B. NoticesOASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.

OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.

Copyright © OASIS Open 2003-2004. All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself does not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an “AS IS” basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


1626

162716281629163016311632163316341635

163616371638

1639

164016411642164316441645164616471648

16491650

16511652165316541655

1656

1657

1658

1659

1660

133134

135

Appendix C. Schemas<?xml version="1.0" encoding="utf-8"?><xs:schema targetNamespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd" xmlns:muws-p2-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd" xmlns:muws-p1-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs:import namespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd" schemaLocation="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd"/> <xs:import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing" schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing"/> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/>

<xs:complexType name="LangString"> <xs:simpleContent> <xs:extension base="xs:string"> <xs:attribute ref="xml:lang" use="required"/> <xs:anyAttribute namespace="##other"/> </xs:extension> </xs:simpleContent> </xs:complexType>

 <xs:element name="Caption" type="muws-p2-xs:LangString"/> <xs:element name="Description" type="muws-p2-xs:LangString"/> <xs:element name="Version" type="xs:string"/> 

<xs:complexType name="CategoryType"> <xs:sequence> <xs:any minOccurs="0" namespace="##any" processContents="lax"/> </xs:sequence> </xs:complexType>

<xs:complexType name="StateType"> <xs:complexContent> <xs:extension base="muws-p2-xs:CategoryType"/> </xs:complexContent> </xs:complexType>

<xs:element name="State" type="muws-p2-xs:StateType"/>

<xs:element name="EnteredState" type="muws-p2-xs:StateType"/>


1661

1662166316641665166616671668166916701671167216731674167516761677167816791680168116821683168416851686168716881689169016911692169316941695169616971698169917001701170217031704170517061707170817091710171117121713171417151716171717181719

136137

138

<xs:element name="PreviousState" type="muws-p2-xs:StateType"/>

<xs:complexType name="StateTransitionType"> <xs:sequence> <xs:element ref="muws-p2-xs:EnteredState"/> <xs:element ref="muws-p2-xs:PreviousState" minOccurs="0"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:attribute name="Time" type="xs:dateTime" use="required"/> <xs:attribute name="TransitionIdentifier" type="xs:anyURI"/> <xs:anyAttribute namespace="##other"/> </xs:complexType>

<xs:element name="StateTransition" type="muws-p2-xs:StateTransitionType"/>

 <xs:element name="OperationalStatus"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Available"/> <xs:enumeration value="PartiallyAvailable"/> <xs:enumeration value="Unavailable"/> <xs:enumeration value="Unknown"/> </xs:restriction> </xs:simpleType> </xs:element> 

<xs:attributeGroup name="MetricAttributes"> <xs:attribute name="ResetAt" type="xs:dateTime"/> <xs:attribute name="LastUpdated" type="xs:dateTime"/> <xs:attribute name="Duration" type="xs:duration"/> </xs:attributeGroup>

 <xs:element name="CurrentTime" type="xs:dateTime"/> 

<xs:complexType name="RelationshipTypeType"> <xs:complexContent> <xs:extension base="muws-p2-xs:CategoryType"/> </xs:complexContent> </xs:complexType>

<xs:complexType name="RelationshipParticipantType"> <xs:sequence> <xs:element ref="muws-p1-xs:ManageabilityEndpointReference" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="muws-p1-xs:ResourceId" minOccurs="0"/> <xs:element name="Role" type="xs:anyURI"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:anyAttribute namespace="##other"/> </xs:complexType>


17201721172217231724172517261727172817291730173117321733173417351736173717381739174017411742174317441745174617471748174917501751175217531754175517561757175817591760176117621763176417651766176717681769177017711772177317741775177617771778177917801781

139140

141

 <xs:element name="Name" type="xs:string"/> <xs:element name="Type" type="muws-p2-xs:RelationshipTypeType"/> <xs:element name="Participant" type="muws-p2-xs:RelationshipParticipantType"/> 

<xs:complexType name="RelationshipType"> <xs:sequence> <xs:element ref="muws-p2-xs:Name" minOccurs="0"/> <xs:element ref="muws-p2-xs:Type"/> <xs:element ref="muws-p2-xs:Participant" minOccurs="2" maxOccurs="unbounded"/> <xs:element name="AccessEndpointReference" type="wsa:EndpointReferenceType" minOccurs="0"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:anyAttribute namespace="##other"/> </xs:complexType>

 <xs:element name="Relationship" type="muws-p2-xs:RelationshipType"/> 

<xs:element name="RelationshipCreatedNotification"> <xs:complexType> <xs:sequence> <xs:element ref="muws-p2-xs:Relationship"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:element name="RelationshipDeletedNotification"> <xs:complexType> <xs:sequence> <xs:element ref="muws-p2-xs:Relationship"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:element name="QueryRelationshipsByType"> <xs:complexType> <xs:sequence> <xs:element name="Type" type="muws-p2-xs:RelationshipTypeType"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:element name="QueryRelationshipsByTypeResponse"> <xs:complexType> <xs:sequence>


17821783178417851786178717881789179017911792179317941795179617971798179918001801180218031804180518061807180818091810181118121813181418151816181718181819182018211822182318241825182618271828182918301831183218331834183518361837183818391840184118421843

142143

144

<xs:element ref="muws-p2-xs:Relationship" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:element name="CreationNotification"> <xs:complexType> <xs:sequence> <xs:element ref="muws-p1-xs:ManageabilityEndpointReference" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:element name="DestructionNotification"> <xs:complexType> <xs:sequence> <xs:element ref="muws-p1-xs:ResourceId" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:complexType name="SituationCategoryType"> <xs:complexContent> <xs:extension base="muws-p2-xs:CategoryType"/> </xs:complexContent> </xs:complexType>

<xs:complexType name="SubstitutableMsgType"> <xs:sequence> <xs:element name="Value" type="xs:anySimpleType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="MsgId" type="xs:string" use="required"/> <xs:attribute name="MsgIdType" type="xs:anyURI" use="required"/> </xs:complexType>

<xs:complexType name="SituationType"> <xs:sequence> <xs:element name="SituationCategory" type="muws-p2-xs:SituationCategoryType"/> <xs:element name="SuccessDisposition" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Successful"/> <xs:enumeration value="Unsuccessful"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="SituationTime" type="xs:dateTime"/> <xs:element name="Priority" type="xs:short" minOccurs="0"/> <xs:element name="Severity" type="xs:short" minOccurs="0"/> <xs:element name="Message" type="muws-p2-xs:LangString" minOccurs="0"/> <xs:element name="SubstitutableMsg" type="muws-p2-xs:SubstitutableMsgType"


18441845184618471848184918501851185218531854185518561857185818591860186118621863186418651866186718681869187018711872187318741875187618771878187918801881188218831884188518861887188818891890189118921893189418951896189718981899190019011902190319041905

145146

147

minOccurs="0"/> </xs:sequence> </xs:complexType>

<xs:element name="Situation" type="muws-p2-xs:SituationType"/>



<xs:element name="Capability" type="xs:anyURI"/>

<xs:complexType name="DialectableExpressionType"> <xs:sequence> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="Dialect" type="xs:anyURI" use="required"/> <xs:anyAttribute namespace="##other"/> </xs:complexType>

<xs:element name="ValidWhile" type="muws-p2-xs:DialectableExpressionType"/>

<xs:element name="Units" type="xs:string"/>

<xs:element name="ChangeType"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Counter"/> <xs:enumeration value="Gauge"/> <xs:enumeration value="Unknown"/> </xs:restriction> </xs:simpleType> </xs:element>

<xs:element name="TimeScope"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Interval"/> <xs:enumeration value="PointInTime"/> <xs:enumeration value="SinceReset"/> </xs:restriction> </xs:simpleType> </xs:element>

<xs:element name="GatheringTime"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="OnChange"/> <xs:enumeration value="Periodic"/> <xs:enumeration value="OnDemand"/> <xs:enumeration value="Unknown"/> </xs:restriction> </xs:simpleType> </xs:element>

<xs:element name="CalculationInterval" type="xs:duration"/>

<xs:element name="MetricGroup" type="xs:anyURI"/>

<xs:element name="PostCondition"wd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 50 of 68

19061907190819091910191119121913191419151916191719181919192019211922192319241925192619271928192919301931193219331934193519361937193819391940194119421943194419451946194719481949195019511952195319541955195619571958195919601961196219631964196519661967

148149

150

type="muws-p2-xs:DialectableExpressionType"/>

</xs:schema><?xml version="1.0" encoding="utf-8"?><xs:schema targetNamespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd" xmlns:muws-p2-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd" xmlns:muws-p1-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs:import namespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd" schemaLocation="file:///C:/Documents and Settings/bryanm1/My Documents/WSmgmt/WSDM/WSDL/wd-wsdm-muws-part1-1.0.xsd"/> <xs:import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing" schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/addressing"/> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/>

<xs:complexType name="LangString"> <xs:simpleContent> <xs:extension base="xs:string"> <xs:attribute ref="xml:lang" use="required"/> <xs:anyAttribute namespace="##other"/> </xs:extension> </xs:simpleContent> </xs:complexType>

<xs:element name="Caption" type="muws-p2-xs:LangString"/> <xs:element name="Description" type="muws-p2-xs:LangString"/> <xs:element name="Version" type="xs:string"/>

<xs:complexType name="DescriptionPropertiesType"> <xs:sequence> <xs:element ref="muws-p2-xs:Caption" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="muws-p2-xs:Description" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="muws-p2-xs:Version" minOccurs="0"/> </xs:sequence> </xs:complexType>

<xs:element name="DescriptionProperties" type="muws-p2-xs:DescriptionPropertiesType"/>


19681969

1970197119721973197419751976197719781979198019811982198319841985198619871988198919901991199219931994199519961997199819992000200120022003200420052006200720082009201020112012201320142015201620172018201920202021202220232024202520262027

151152

153

<xs:complexType name="CategoryType"> <xs:sequence> <xs:any minOccurs="0" namespace="##any" processContents="lax"/> </xs:sequence> </xs:complexType>

<xs:complexType name="StateType"> <xs:complexContent> <xs:extension base="muws-p2-xs:CategoryType"/> </xs:complexContent> </xs:complexType>

<xs:element name="State" type="muws-p2-xs:StateType"/>

<xs:element name="EnteredState" type="muws-p2-xs:StateType"/> <xs:element name="PreviousState" type="muws-p2-xs:StateType"/> <xs:element name="TransitionIdentifier" type="xs:anyURI"/>

<xs:complexType name="StateTransitionType"> <xs:sequence> <xs:element ref="muws-p2-xs:EnteredState"/> <xs:element ref="muws-p2-xs:PreviousState" minOccurs="0"/> <xs:element ref="muws-p2-xs:TransitionIdentifier" minOccurs="0"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:attribute name="Time" type="xs:dateTime" use="required"/> <xs:anyAttribute namespace="##other"/> </xs:complexType>

<xs:element name="OperationalStatus"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Available"/> <xs:enumeration value="PartiallyAvailable"/> <xs:enumeration value="Unavailable"/> <xs:enumeration value="Unknown"/> </xs:restriction> </xs:simpleType> </xs:element>

<xs:complexType name="OperationalStatusPropertiesType"> <xs:sequence> <xs:element ref="muws-p2-xs:OperationalStatus"/> </xs:sequence> </xs:complexType>

<xs:element name="OperationalStatusProperties" type="muws-p2-xs:OperationalStatusPropertiesType"/>

<xs:attributeGroup name="MetricAttributes"> <xs:attribute name="ResetAt" type="xs:dateTime"/> <xs:attribute name="LastUpdated" type="xs:dateTime"/> <xs:attribute name="Duration" type="xs:duration"/> </xs:attributeGroup>


20282029203020312032203320342035203620372038203920402041204220432044204520462047204820492050205120522053205420552056205720582059206020612062206320642065206620672068206920702071207220732074207520762077207820792080208120822083208420852086208720882089

154155

156

<xs:element name="CurrentTime" type="xs:dateTime"/>

<xs:complexType name="MetricsPropertiesType"> <xs:sequence> <xs:element ref="muws-p2-xs:CurrentTime"/> </xs:sequence> </xs:complexType>

<xs:element name="MetricsProperties" type="muws-p2-xs:MetricsPropertiesType"/>

<xs:complexType name="RelationshipTypeType"> <xs:complexContent> <xs:extension base="muws-p2-xs:CategoryType"/> </xs:complexContent> </xs:complexType>

<xs:complexType name="RelationshipParticipantType"> <xs:sequence> <xs:attribute name="Role" type="xs:anyURI”/> <xs:element ref="muws-p1-xs:ManageabilityEndpointReference" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="muws-p1-xs:ResourceId" minOccurs="0"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:anyAttribute namespace="##other"/> </xs:complexType>

<xs:element name="Name" type="xs:string"/> <xs:element name="Type" type="muws-p2-xs:RelationshipTypeType"/> <xs:element name="Participant" type="muws-p2-xs:RelationshipParticipantType"/>

<xs:complexType name="RelationshipType"> <xs:sequence> <xs:element ref="muws-p2-xs:Name" minOccurs="0"/> <xs:element ref="muws-p2-xs:Type"/> <xs:element ref="muws-p2-xs:Participant" minOccurs="2" maxOccurs="unbounded"/> <xs:element name="AccessEndpointReference" type="wsa:EndpointReferenceType" minOccurs="0"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:anyAttribute namespace="##other"/> </xs:complexType>

<xs:element name="Relationship" type="muws-p2-xs:RelationshipType"/>

<xs:complexType name="RelationshipPropertiesType"> <xs:sequence> <xs:element ref="muws-p2-xs:Relationship" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType>


20902091209220932094209520962097209820992100210121022103210421052106210721082109211021112112211321142115211621172118211921202121212221232124212521262127212821292130213121322133213421352136213721382139214021412142214321442145214621472148214921502151

157158

159

<xs:element name="RelationshipProperties" type="muws-p2-xs:RelationshipPropertiesType"/>

<xs:element name="RelationshipCreatedNotification"> <xs:complexType> <xs:sequence> <xs:element ref="muws-p2-xs:Relationship"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:element name="RelationshipDeletedNotification"> <xs:complexType> <xs:sequence> <xs:element ref="muws-p2-xs:Relationship"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:complexType name="RelationshipResourcePropertiesType"> <xs:sequence> <xs:element ref="muws-p2-xs:Name" minOccurs="0"/> <xs:element ref="muws-p2-xs:Type"/> <xs:element ref="muws-p2-xs:Participant" minOccurs="2" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType>

<xs:element name="RelationshipResourceProperties" type="muws-p2-xs:RelationshipResourcePropertiesType"/>

<xs:element name="CreationNotification"> <xs:complexType> <xs:sequence> <xs:element ref="muws-p1-xs:ManageabilityEndpointReference"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:element name="DestructionNotification"> <xs:complexType> <xs:sequence> <xs:element ref="muws-p1-xs:ManageabilityEndpointReference"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:complexType name="SituationCategoryType"> <xs:complexContent> <xs:extension base="muws-p2-xs:CategoryType"/> </xs:complexContent> </xs:complexType>


21522153215421552156215721582159216021612162216321642165216621672168216921702171217221732174217521762177217821792180218121822183218421852186218721882189219021912192219321942195219621972198219922002201220222032204220522062207220822092210221122122213

160161

162

<xs:complexType name="SubstitutableMsgType"> <xs:sequence> <xs:element name="Value" type="xs:anySimpleType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="msgId" type="xs:string"/> <xs:attribute name="msgIdType" type="xs:anyURI"/> </xs:complexType>

<xs:complexType name="SituationType"> <xs:sequence> <xs:element name="SituationCategory" type="muws-p2-xs:SituationCategoryType"/> <xs:element name="SuccessDisposition"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Successful"/> <xs:enumeration value="Unsuccessful"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="SituationTime" type="xs:dateTime"/> <xs:element name="Priority" type="xs:short" minOccurs="0"/> <xs:element name="Severity" type="xs:short" minOccurs="0"/> <xs:element name="Message" type="muws-p2-xs:LangString"/> <xs:element name="SubstitutableMsg" type="muws-p2-xs:SubstitutableMsgType"/> </xs:sequence> </xs:complexType>

<xs:element name="Situation" type="muws-p2-xs:SituationType"/>



<xs:element name="capability" type="xs:anyURI"/>

<xs:element name="units" type="xs:string"/>

<xs:element name="changeType"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Counter"/> <xs:enumeration value="Gauge"/> <xs:enumeration value="Unknown"/> </xs:restriction> </xs:simpleType> </xs:element>

<xs:element name="timeScope"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Interval"/> <xs:enumeration value="PointInTime"/> <xs:enumeration value="SinceReset"/> </xs:restriction> </xs:simpleType> </xs:element>


22142215221622172218221922202221222222232224222522262227222822292230223122322233223422352236223722382239224022412242224322442245224622472248224922502251225222532254225522562257225822592260226122622263226422652266226722682269227022712272227322742275

163164

165

<xs:element name="gatheringTime"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="OnChange"/> <xs:enumeration value="Periodic"/> <xs:enumeration value="OnDemand"/> <xs:enumeration value="Unknown"/> </xs:restriction> </xs:simpleType> </xs:element>

<xs:element name="calculationInterval" type="xs:duration"/>

<xs:element name="metricGroup" type="xs:anyURI"/>

<xs:element name="validWhile" type="muws-p1-xs:CorrelatablePropertiesType"/>

<xs:element name="invalidWhile" type="muws-p1-xs:CorrelatablePropertiesType"/>

<xs:element name="preCondition" type="muws-p1-xs:CorrelatablePropertiesType"/>

<xs:element name="postCondition" type="muws-p1-xs:CorrelatablePropertiesType"/>

<xs:element name="event"> <xs:complexType> <xs:sequence> <xs:element name="situationType" type="xs:string" minOccurs="0"/> <xs:element name="situationQualifier" type="xs:string" minOccurs="0"/> <xs:element name="successDisposition" type="xs:string" minOccurs="0"/> <xs:element name="sourceResourceType" type="xs:anyURI" minOccurs="0"/> <xs:element name="severity" type="xs:short" minOccurs="0"/> <xs:element name="messagePattern" type="xs:QName" minOccurs="0"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element>

</xs:schema>


22762277227822792280228122822283228422852286228722882289229022912292229322942295229622972298229923002301230223032304230523062307230823092310231123122313231423152316231723182319232023212322232323242325

166167

168

Appendix D. WSDL elements<?xml version="1.0" encoding="utf-8"?><definitions targetNamespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.wsdl" xmlns:muws-p2-wsdl="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.wsdl" xmlns:muws-p2-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd" xmlns:muws-p1-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd" xmlns:wsrf-rp="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/">

<types> <xs:schema elementFormDefault="qualified" targetNamespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.wsdl">

<xs:import namespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd" schemaLocation="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd"/>

<xs:import namespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd" schemaLocation="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd"/>

<xs:element name="QueryRelationshipsByType"> <xs:complexType> <xs:sequence> <xs:element name="Type" type="muws-p2-xs:RelationshipTypeType"/> </xs:sequence> </xs:complexType> </xs:element>

<xs:element name="QueryRelationshipsByTypeResponse"> <xs:complexType> <xs:sequence> <xs:element ref="muws-p2-xs:Relationship" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element>

</xs:schema> </types>


2326

2327232823292330233123322333233423352336233723382339234023412342234323442345234623472348234923502351235223532354235523562357235823592360236123622363236423652366236723682369237023712372237323742375237623772378237923802381238223832384

169170

171

<message name="QueryRelationshipsByTypeRequest"> <part name="body" element="muws-p2-wsdlxs:QueryRelationshipsByType"/> </message>

<message name="QueryRelationshipsByTypeResponse"> <part name="body" element="muws-p2-wsdlxs:QueryRelationshipsByTypeResponse"/> </message>

<portType name="Identity" wsrf-rp:ResourceProperties="muws-p1-xs:IdentityProperties"> </portType>

<portType name="ManageabilityCharacteristics" wsrf-rp:ResourceProperties="muws-p1-xs:ManageabilityCharacteristicsProperties"> </portType>

<portType name="CorrelatableProperties" wsrf-rp:ResourceProperties="muws-p1-xs:CorrelatablePropertiesProperties"> </portType>

<portType name="Description" wsrf-rp:ResourceProperties="muws-p2-xs:DescriptionProperties"> </portType>

<portType name="OperationalStatus" wsrf-rp:ResourceProperties="muws-p2-xs:OperationalStatusProperties"> </portType>

<portType name="Metrics" wsrf-rp:ResourceProperties="muws-p2-xs:MetricsProperties"> </portType>

<portType name="Relationships" wsrf-rp:ResourceProperties="muws-p2-xs:RelationshipsProperties">

<operation name="QueryRelationshipsByType"> <input name="QueryRelationshipsByTypeRequest" message="muws-p2-wsdl:QueryRelationshipsByTypeRequest"/> <output name="QueryRelationshipsByTypeResponse" message="muws-p2-wsdl:QueryRelationshipsByTypeResponse"/> </operation>

</portType>

<portType name="RelationshipResource" wsrf-rp:ResourceProperties="muws-p2-xs:RelationshipResourceProperties"> </portType>

</definitions>


238523862387238823892390239123922393239423952396239723982399240024012402240324042405240624072408240924102411241224132414241524162417241824192420242124222423242424252426242724282429243024312432243324342435243624372438243924402441

172173

174

Appendix E. Topics<wstop:TopicSpace name="MuwsNotificationTopics" targetNamespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-events-1.0.xml" xmlns:wstop="http://docs.oasis-open.org/wsn/2004/06/wsn-WS-Topics-1.2-draft-01.xsd" xmlns:muws-p1-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd" xmlns:muws-p2-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd" xmlns:wsrf-rp="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd">

<wstop:Topic name="IdentityCapability" messageTypes="muws-p1-xs:ManagementEvent"> </wstop:Topic>

<wstop:Topic name="ManageabilityCharacteristicsCapability" messageTypes="muws-p1-xs:ManagementEvent"> </wstop:Topic>

<wstop:Topic name="CorrelatablePropertiesCapability" messageTypes="muws-p1-xs:ManagementEvent"> </wstop:Topic>

<wstop:Topic name="DescriptionCapability" messageTypes="muws-p1-xs:ManagementEvent"> </wstop:Topic>

<wstop:Topic name="OperationalStatusCapability" messageTypes="muws-p1-xs:ManagementEvent"> </wstop:Topic>

<wstop:Topic name="MetricsCapability" messageTypes="muws-p1-xs:ManagementEvent"> </wstop:Topic>

<wstop:Topic name="RelationshipsCapability" messageTypes="muws-p1-xs:ManagementEvent">

<wstop:Topic name="RelationshipCreated" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> //muws-p1-xs:ManagementEvent[count(muws-p2-xs:RelationshipCreatedNotification)=1] </wstop:MessagePattern> </wstop:Topic>

<wstop:Topic name="RelationshipDeleted" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> //muws-p1-xs:ManagementEvent[count(muws-p2-xs:RelationshipDeletedNotification)=1] </wstop:MessagePattern> </wstop:Topic>

</wstop:Topic>


2442

2443244424452446244724482449245024512452245324542455245624572458245924602461246224632464246524662467246824692470247124722473247424752476247724782479248024812482248324842485248624872488248924902491249224932494249524962497249824992500

175176

177

<wstop:Topic name="RelationshipResourceCapability" messageTypes="muws-p1-xs:ManagementEvent"> </wstop:Topic>

<wstop:Topic name="ManageabilityEndpointCreation" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> //muws-p1-xs:ManagementEvent[count(muws-p2-xs:CreationNotification)=1] </wstop:MessagePattern>

<wstop:Topic name="ManageableResourceCreation" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> //muws-p1-xs:ManagementEvent[count(muws-p2-xs:CreationNotification)=1] </wstop:MessagePattern> </wstop:Topic>

</wstop:Topic>

<wstop:Topic name="ManageabilityEndpointDestruction" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> //muws-p1-xs:ManagementEvent[count(muws-p2-xs:DestructionNotification)=1] </wstop:MessagePattern>

<wstop:Topic name="ManageableResourceDestruction" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> //muws-p1-xs:ManagementEvent[count(muws-p2-xs:DestructionNotification)=1] </wstop:MessagePattern> </wstop:Topic>

</wstop:Topic>

</wstop:TopicSpace><wstop:TopicSpace name="MuwsNotificationTopics" targetNamespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-events-1.0.xml" xmlns:wstop="http://docs.oasis-open.org/wsn/2004/06/wsn-WS-Topics-1.2-draft-01.xsd" xmlns:muws-p1-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd">

<wstop:Topic name="IdentityCapability" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(ResourcePropertyValueChangeNotification[


250125022503250425052506250725082509251025112512251325142515251625172518251925202521252225232524252525262527252825292530253125322533253425352536253725382539254025412542254325442545254625472548254925502551255225532554255525562557255825592560

178179

180

namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"])=1]) </wstop:MessagePattern> </wstop:Topic>

<wstop:Topic name="ManageabilityCharacteristicsCapability" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(ResourcePropertyValueChangeNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"])=1]) </wstop:MessagePattern> </wstop:Topic>

<wstop:Topic name="CorrelatablePropertiesCapability" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(ResourcePropertyValueChangeNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"])=1]) </wstop:MessagePattern> </wstop:Topic>

<wstop:Topic name="DescriptionCapability" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(ResourcePropertyValueChangeNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"])=1]) </wstop:MessagePattern> </wstop:Topic>

<wstop:Topic name="OperationalStatusCapability" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(ResourcePropertyValueChangeNotification[


256125622563256425652566256725682569257025712572257325742575257625772578257925802581258225832584258525862587258825892590259125922593259425952596259725982599260026012602260326042605260626072608260926102611261226132614261526162617261826192620

181182

183

namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"])=1]) </wstop:MessagePattern> </wstop:Topic>

<wstop:Topic name="MetricsCapability" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(ResourcePropertyValueChangeNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"])=1]) </wstop:MessagePattern> </wstop:Topic>

<wstop:Topic name="RelationshipsCapability" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(ResourcePropertyValueChangeNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"])=1]) </wstop:MessagePattern>

<wstop:Topic name="RelationshipCreated" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(RelationshipCreatedNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd"])=1]) </wstop:MessagePattern> </wstop:Topic>

<wstop:Topic name="RelationshipDeleted" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(RelationshipDeletedNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd"])=1])


26212622262326242625262626272628262926302631263226332634263526362637263826392640264126422643264426452646264726482649265026512652265326542655265626572658265926602661266226632664266526662667266826692670267126722673267426752676267726782679268026812682

184185

186

</wstop:MessagePattern> </wstop:Topic>

</wstop:Topic>

<wstop:Topic name="RelationshipResourceCapability" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(ResourcePropertyValueChangeNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"])=1]) </wstop:MessagePattern> </wstop:Topic>

<wstop:Topic name="ManageabilityEndpointCreation" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(CreationNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd"])=1]) </wstop:MessagePattern>

<wstop:Topic name="ManageableResourceCreation" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(CreationNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd"])=1]) </wstop:MessagePattern> </wstop:Topic>

</wstop:Topic>

<wstop:Topic name="ManageabilityEndpointDestruction" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(DestructionNotification[


268326842685268626872688268926902691269226932694269526962697269826992700270127022703270427052706270727082709271027112712271327142715271627172718271927202721272227232724272527262727272827292730273127322733273427352736273727382739274027412742

187188

189

namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd"])=1]) </wstop:MessagePattern>

<wstop:Topic name="ManageableResourceDestruction" messageTypes="muws-p1-xs:ManagementEvent"> <wstop:MessagePattern Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"> boolean(//ManagementEvent[ namespace-uri(.)='http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part1-1.0.xsd' and count(DestructionNotification[ namespace-uri(.)="http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.xsd"])=1]) </wstop:MessagePattern> </wstop:Topic>

</wstop:Topic>

</wstop:TopicSpace>


27432744274527462747274827492750275127522753275427552756275727582759276027612762276327642765

190191

192

Appendix F. Description of situation typesThis appendix defines in more details the situation types introduced in section 2.4.1.

AvailabilitySituation

This category deals with the situations reported from the component, regarding its operational state and availability. This situation provides a context for operations that can be performed by the component to establish if a product is installed, operational and ready to process functional requests, or operational and ready or not ready to process management requests. Existing message include words like “now ready to take requests”, “online”, and “offline”, for example:Deals with the situations reported from the component, regarding its operational state and availability. This situation provides a context for operations that can be performed by the component to establish if a product is installed, operational and ready to process functional requests, or operational and ready or not ready to process management requests. Existing message include words like now ready to take requests, online, and offline, for example:

“SOAP connector available at port 8888”

CapabilitySituation

This category is specified when a change in capability of a resource occurs. For example, a printer has an envelope tray attached to it so that the printer is now has additional paper choices. The same category would be used if the envelope tray is removed from the printer.XXXX

ConfigurationSituation

This category deals with the components identifying configuration changes. Any changes that a component makes to its configuration should be logged using this category. Existing message include words like “port number is”, “address is”, and “process id”, for exampleDeals with the components identifying their configuration. Any changes that a component makes to its configuration should be logged using this category. Additionally, messages that describe the current configuration state fall into this category. Existing message include words like port number is, address is, and process id, for example:

“File transfer configured with host=’9.27.11.13’, port=’9090’, securityEnabled=’false’”

StopSituation

This category deals with the shutdown process for a component. Messages that indicate that a component has begun to stop, that it has stopped, or that the stopping process has failed all fall into this category. Existing messages include words like “stop”, “stopping”, “stopped”, “completed”, and “exiting”, for exampleDeals with the shutdown process for a component. Messages that indicate that a component has begun to stop, that it has stopped, or that the stopping process has failed all fall into this category. Existing messages include words like stop, stopping, stopped, completed, and exiting, for example:

“Application stopped: myApp.exe” “An error occurred while stopping myApp.exe” “Stopping the JMS provider”

StartSituationwd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 65 of 68

2766

2767

2768

27692770277127722773277427752776277727782779

2780

2781

2782278327842785

2786

2787

27882789279027912792279327942795

2796

2797

2798279928002801280228032804280528062807

2808

2809193194

195

This category deals with the startup process for a component. Messages that indicate that a component has begun the startup process, that it has finished the startup process, or that it has aborted the startup process all fall into this category. Existing messages include words like “starting”, “started”, “initializing”, and “initialized”, for exampleDeals with the startup process for a component. Messages that indicate that a component has begun the startup process, that it has finished the startup process, or that it has aborted the startup process all fall into this category. Existing messages include words like starting, started, initializing, and initialized, for example:

“XYZ protocol support was successfully started” “XYZ protocol support failed to start” “Starting EJB: myEjb.jar”

RequestSituation

This category is used in situations that a component uses to identify the completion status of a request. Typically, these requests are complex management tasks or transactions that a component undertakes on behalf of a requestor and not the mainline simple requests or transactions. Existing messages are of the form “request started” or “request completed” as in phrases like “configuration synchronization started”, and “backup procedure complete”, for exampleHandles the situations that a component uses to identify the completion status of a request. Typically, these requests are complex management tasks or transactions that a component undertakes on behalf of a requestor and not the mainline simple requests or transactions. Existing messages include words like configuration synchronization started, and backup procedure complete, for example:

“Configuration synchronization completed”Note that events generated from requests that start up or stop a resource would be categorized as StartSituation or StopSituation respectively because they are higher precedent than RequestSituation.

DestroySituation

This category deals with the situations occurring when an entity or component was removed or destroyed. Messages telling that a document was destroyed or a file was deleted all fall into this category. Existing messages include phrases like “was destroyed”, “about to remove”, and “no longer exists”, for exampleDeals with the situations documenting when an entity or component was removed or destroyed. Messages telling that a document was destroyed or a file was deleted all fall into this category. Existing messages include words like was deleted, about to delete, and now deleted, for example:

“The connection pool was destroyed for data source foo”

CreateSituation

This category deals with the situations occurring when a component creates an entity. Messages telling that a document was created, or a file was created, or an Enterprise JavaBean (EJB) was created all fall into this category. Existing message include words like was created, about to create, and now exists, for exampleDeals with the situations documenting when a component creates an entity. Messages telling that a document was created, or a file was created, or an Enterprise JavaBean (EJB) was created all fall into this category. Existing message include words like was created, about to create, and now exists, for example:

“New log file was created”

DependencySituationwd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 66 of 68

2810281128122813281428152816281728182819

2820

2821

28222823282428252826282728282829283028312832283328342835

2836

2837

28382839284028412842284328442845

2846

2847

28482849285028512852285328542855

2856

2857196197

198

This category deals with the situations where components cannot find some component or feature that they require. This category includes messages about not finding the ”version” of the component that was expected. Messages that say a resource was not found, or that an application or subsystem that was unavailable, also fall into this category. Existing messages include words like “could not find”, and “no such component”, for exampleDeals with the situations that components produce to indicate that they cannot find some component or feature that they require. This category includes messages about not finding the “version” of the component that was expected. Messages that say a resource was not found, or that an application or subsystem that was unavailable, also fall into this category. Existing messages include words like could not find, and no such component, for example:

“Error encountered while deploying database schema: no database found”

ConnectSituation

This category deals with the situations related to aspects about a connection attempt from one component to another component. Messages that say a connection failed, that a connection was created, or that a connection was ended all fall into this category. Existing messages include words like “connection reset”, “connection failed”, and “failed to get a connection”, for exampleDeals with the situations that identify aspects about a connection attempt from one component to another component. Messages that say a connection failed, that a connection was created, or that a connection was ended all fall into this category. Existing messages include words like connection reset, connection failed, and failed to get a connection, for example:

“Connection creation failed” “Connection with http://foo.com created” “Failed to close a connection”

ReportSituationThis category deals with situations that occur as a result of some setting or occurrence that causes the resource to asynchronously report various types of data. Types of information that falls into this category are:

Exception related – some exception has occurred within the resource and it not covered by any other category.

Performance related – some event occurs, that does not fall into any other category, that has affected performance in some way. For example, weather conditions may be affected line quality and network speeds are affected.

Security related – some security issue has been detected, like the cabinet door to a secure piece of equipment has been opened or an attack of some sort has been detected.

Heartbeat related – the resource has been configured to periodically report a ‘heartbeat’. Status related – some change of status that does not affect availability or capability of

the resource has been detected. For example, printer ink cartridge is low. Log related – the resource has been configured to generate a log entry based on some

event or at a fixed interval. This category identifies this event as a requested log entry. Debug related – the resource has been enabled to turn on diagnostic information flow

and will report the information within this category. Trace related – the resource has been enabled to run trace information and reports this

information using this categoryXXXXX

OtherSituationwd-wsdm-muws-part2-1.0Copyright © OASIS Open 2003-2004. All Rights Reserved. Page 67 of 68

28582859286028612862286328642865286628672868286928702871

28722873287428752876287728782879288028812882

2883

28842885288628872888288928902891289228932894289528962897289828992900290129022903290429052906

29072908

199200

201

WEF Edits, 11/26/04,

Note, we may want to change this to its own situationCategory given the importance of this.

This category is for those events that do not fall into any other category. Note that this category is defined for syntactic completeness but any events placed in this category will not be able to be effectively correlated and its use is therefore discouraged unless absolutely necessary.Deals with any situation not covered by the other situation types.


29092910291129122913

202203

204