Endpoint References

The WS-Management specification uses WS-Addressing endpoint references (EPRs) as the addressing model for individual resource instances. Table: Prefixes and XML Namespaces Used in this Document lists the prefixes used in this section to show the namespace of each element type.

An EPR is an XML element of the type wsa:EndpointReferenceType. An EPR element contains subelements that, in combination, provide the full reference to a resource instance. In terms of the HPOM Incident Web Service, this means that an EPR provides the full reference to an individual incident on a particular management server.

The following XML element shows an example of an EPR for the HPOM Incident Web Service:

<wsa:EndpointReference>

<wsa:Address>

https://manager1.example.com:443/opr-webservice/Incident.svc/

</wsa:Address>

<wsa:ReferenceParameters>

<wsman:ResourceURI>

http://schemas.hp.com/ism/ServiceOperation/IncidentManagement/1/Incident

</wsman:ResourceURI>

<wsman:SelectorSet>

<wsman:Selector Name="IncidentID"> 2b9cdf48-d6ca-71db-0d4b-1039228b0000

</wsman:Selector>

</wsman:SelectorSet>

</wsa:ReferenceParameters>

</wsa:EndpointReference>

The above EPR contains of the following conceptual elements:

Address at which the service is available on a management server. This is in the format:
https://<server_name>:<port>/opr-webservice/Incident.svc/
Unique identifier for the type of resource. This is the following URI:
http://schemas.hp.com/ism/ServiceOperation/IncidentManagement/1/Incident
Selector set that identifies an incident. This contains one selector, which contains an incident ID.

When you create a new incident using the service, the service returns an EPR for the new incident. You can store this EPR, and use it to uniquely identify the incident if you need to update it later. (See Create.)

WS-Addressing specifies that, to use an EPR in a request to a service, clients should add the contents of the EPR's wsa:Address subelement as the contents of the wsa:To subelement in the SOAP header. Where possible, clients should not rely on the wsa:ReferenceParameters subelement containing any particular subelements. Clients should instead treat the wsa:ReferenceParameters subelement as opaque, by unwrapping its contents and adding them all to the SOAP header of the request.

The following XML fragment shows an example of a SOAP header that contains the EPR of an incident:

<s:Header>

...

<wsa:To>