Go to primary content
Oracle® Communications Diameter Signaling Router Subscriber Database Server Provisioning Interface
Release 8.3
E93213
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Examples

Below are some examples of how to use the <updateDomainRequest> request and likely response. Some of these examples are based upon previous requests; hence, the order of the requests could be important.

These examples show the SDS provisioning request and response contents that are stored within the appropriate SOAP envelope body tag (<soapenv:Body> or <SOAP-ENV:Body>). See Examples for an example of the whole SOAP request/response text.

Add New Domain Names

This example creates 3 new Domain Identifier values and sets their destination values to the specified values.

The result of this request is

  • New Domain Identifier value are created.
  • All of the destination values for each routing entity are set to specified values.

Request:

<updateDomainRequest timeout="10">
  <domainList>
    <domain>tekelec.com</domain>
    <domain>oracle.com</domain>
    <domain>cgbu-oracle.com</domain>
  </domainList>
  <destinationList>
    <imshss>IMS_HSS_1</imshss>
    <ltehss>LTE_HSS_1</ltehss>
    <aaa>AAA_Texas</aaa>
  </destinationList>
</updateDomainRequest>
Response:
<ns2:sdsResult affected="3" error="0">
</ns2:sdsResult>

Update Domain Identifier Destinations (Success)

This example updates existing Domain Identifier with new destination values.

Note:

This request does not update all Domain Identifier values that were specified in the previous request.

The result of this request is that the specified Domain Identifier values are updated with specified destination values.

Request:
<updateDomainRequest timeout="10">
  <domainList>
    <domain>tekelec.com</domain>
    <domain>oracle.com</domain>
  </domainList>
  <destinationList>
    <ltehss>LTE_HSS_4</ltehss>
    <pcrf>PCRF_Ohio</pcrf>
  </destinationList>
</updateDomainRequest>
Result:
<ns2:sdsResult affected="2" error="0">
</ns2:sdsResult>

Update Domain Identifier Destinations (Failure)

This example fails to update existing Domain Identifier with new destination values because the destination does not exist.

No changes are made to the database because the request fails.

Request:
<updateDomainRequest timeout="10">
  <domainList>
    <domain>tekelec.com</domain>
    <domain>oracle.com</domain>
  </domainList>
  <destinationList>
    <ltehss>junk</ltehss>
  </destinationList>
</updateDomainRequest>
Result:
<ns2:sdsResult description=“destination not found” affected="0" error="2006">
</ns2:sdsResult>