3.2.4.1 FindServiceLocations

The FindServiceLocations operation provides a mechanism for a requestor to retrieve a URL for a specified service that is either offered by or known to the responding server.

FindServiceLocations message sequence diagram

Figure 3: FindServiceLocations message sequence diagram

 <wsdl:operation name="FindServiceLocations">

The SOAP operation is defined as follows.

 <soap:operation
  soapAction=
   "http://microsoft.com/DRM/ServerService/FindServiceLocations"
  style="document" />

Request Validation:

The responding server MUST validate the input parameters upon receiving a FindServiceLocations request. The FindServiceLocations request MUST follow the schema specified in section 3.2.4.1.1.1.

 Parameter

 Description

ServiceType

MUST be a valid service type from the following list: LicensingService, CertificationService, DrmRemoteDirectoryServices, GroupExpansionService, LicensingInternalService, CertificationInternalService. Other service types are not supported.

A single request MAY request URLs for multiple service types by including multiple <ServiceTypes> in the ArrayOfServiceLocationRequest as defined in section 3.2.4.1.3.1.

Data Processing:

For a successful request, the responding server MUST return the appropriate service location URL. For an unsuccessful request, the server MUST return a fault code. The following table describes the URL expected for each service type.

 Service Type

 Description

LicensingService

The URL of the responding server's licensing service (license.asmx).

CertificationService

The URL of the responding server's certification service (certification.asmx).

DrmRemoteDirectoryServices

The URL of the responding server's Binary Group Expansion interface.<10>

GroupExpansionService

The URL of the responding server's GroupExpansionServerSoap port type.<11>

LicensingInternalService

The internal URL of the responding server's the licensing service (license.asmx).<12>

CertificationInternalService

The internal URL of the responding server's certification service (certification.asmx).<13>

Response:

A successful FindServiceLocations response MUST follow the schema specified in section 3.2.4.1.1.2. If multiple service types were requested, a successful response MUST include the same set of service types with corresponding URLs. If a specific URL is not available, the URL MUST be an empty string but the service type MUST still be included. For an unsuccessful request, the server MUST return a fault code. This operation throws only Common Fault Codes for the RMS: Server-Server Protocol as specified in section 2.2.9.1.