BAIC — XML-REST schema

User Interfaces Release 9.1 Subscriber Provisioning Reference Manual 200 — OK: Indicates the successful completion of request processing. 201 — Created: Used for newly created entities. The response header property “Location” will contain the URI of the newly created entity. 204 — No Content: The request completed successfully and no response content body is sent back to the client. 400 — Bad Request: This indicates that there is a problem with how the request is formatted or that the data in the request caused a validation error. 404 — Not Found: Indicates that the client tried to operate on a resource that did not exist.

4xx — Other status codes in the 4xx range that are also client request issues. For example, the client may be calling an operation that is not implemented/available or that is asking for a mime type that is not supported. 500 — Internal Server Error: This error and other errors in the 5xx range indicate server problems. If one of these errors occurs, please contact Tekelec customer support. Error handling Any operation in the XML-REST interface that results in an HTTP error response in the 4xx or 5xx range will include response content that includes an errorMessage entity. This entity defines both an error code and additional error text to explain the error. Subscriber field not found.

Key type name = MSISDN Key value = +33123654862 Field name = AccountId For example, when a subscriber exists and has no quota or state defined, and a delete or fetch request is sent to the XML-REST interface, two error responses are returned. They are HTTP 404 Not Found and MSR4053 Subscriber and field exist but the value provided is incorrect . For information about these SPR Event Log Messages, refer to section SPR Error Notifications in the SDM Management, Monitoring, Maintaining, Troubleshooting - Reference Manual . XML-REST schema The XML-REST interface uses the following XML Schema for both request and response content.

The schema defines the following entities and applies to subscriber or pool provisioning: Subscriber (or Pool) — This is a container element that is used to contain other elements with subscriber (or pool) data, such as the Field and Data elements. Field — This element contains a single field value. If a field has multiple values, the values are separated by a semicolon (;). Data — This element contains opaque data. ErrorMessage — This element contains information about errors that occur during the processing of a request. Note: If you are writing software to manipulate this data, you MUST use a non-validating parser when processing the XML data.

This parser allows new elements to be added in the future to support new features or functionalities. The XML schema definition (XSD) for these entities is presented as follows: xmlns:xs="http://www.w3.org/2001/XMLSchema"> 45 910-6701-001 Revision A, June 2013