Page History

01 - 03

Convey the recipient of the response message. Note that this time we are talking about the service requestor; The address matches the <wsa:From> previously found in the corresponding request

04 - 06

Indicate this is a GetResourceProperty response. This is done as usual using a wsa:Action that is part of WS-Addressing specification

07 - 09

Convey a unique identifier associated with the current response message

10 - 12

This element provides the identifier of the correlated (request) message

13

The <wsa:From> element (part of WS-Addressing specs too) identifies the source endpoint, the originator of this response message

14 - 16

This is the address of the source service endpoint. As said for lines 01-03 this time this is referred to service provider (the message originator)

17

This element represent a single resource as part of QMan management domain.

18 - 22

The "group" membership information for a specific resource are detailed using a SericeGroupEntry which is separated from the WS-Resource itself.
In fact, the service group entry is a WS-Resource itself which has its own address (line 20) and identifier (line 21). That means we could have properties belonging to group membership of WS-Resource, not to WS-Resource itself.

24 - 28

The resource member that is part of QMan management group. This element contains all what is needed for identifying and addressing the WS-Resource.

25

This is the resource soap:address (as declared on its WSDL)

26 - 27

The WS-Resource identifier. This is the most important information about resource. Subsequent requests directed to resource will contain this identifier.

29

Additional (optional) management group information.

33 - 34

Those are two additional entry summaries. Note that for each resource there's a dedicated wsrf-sg:Entry.