User Interfaces Release 9.1 Subscriber Provisioning Reference Manual "Y": The values of the attributes that are defined in the referenced Template requests and that are not listed in the 'Attribute Name' section of the template, can be modified by commands in the Invoking file. In this case, any of the attributes defined in the referenced template requests can be provided in the Invoking file commands along with new values and these new values will overwrite the ones defined in the template requests. "N":
The values of the attributes that are defined in the referenced Template requests and that are not listed in the 'Attribute Name' section of the template, cannot be modified by commands in the Invoking file. Only the attributes listed in this template can be modified by commands in the Invoking file. Request template instructions for invoking files This part of the Invoking file needs to be created as many times as there are modifiable attributes for which you need to override the default value.
Each Request Template instruction provides a specific attribute and value pair that are used to override the default attribute values found in Template Requests associated with the specified Template. The following attributes represent correspondingly the attribute and value pair: " tpi nm " and " val ". The " nm " attribute provides the name of a modifiable attribute found in the Template requests associated with the specified Command Template. The " val " attribute is used to define the new value of the specified modifiable attribute. This new value will override the default value defined for that attribute in the Template request associated with the Command Template used.
A Request Template instruction can also contain optionally a " tpi rid " attribute that allows to specify a Template request ID number (i.e., rid). In this case, attribute values would only be overwritten for the Template Request with the Template request ID number specified. By default, if no Template Request ID is specified, the values of all the attributes with this given name are overwritten in all the Template Request. The " tpi rid " attribute limits the overwriting of the modifiable attribute specified within one single Template request.
The modifiable attribute with the attribute name specified will only be overwritten by the value given in the Invoking file for the Template request specified. For examples on the use of XML Templates to provision subscribers, refer to the "Examples of XML Templates for Subscriber provisioning" section of the SDM Subscriber Provisioning - User Guide . Provisioning in direct mode through the SOAP interface The Tekelec SDM provides machine-to-machine (M2M) communication between a client џs SOAP application and the Tekelec SDM Web Server. SOAP (Simple Object Access Protocol) is a communication protocol that sends XML interface messages over the internet. Refer to figure below.
The SDM supports Web Services by using the SOAP protocol to exchange messages between network applications. The SOAP Messages and SOAP Replies are transported over the HTTP protocol. The SDM Web Server currently supports Request and Response message types. A benefit of using M2M is to simplify the Subscriber Provisioning process. The operator can change and update subscriber profiles in their system, save the changes, and then use the M2M interface to transfer updates to the SDM system. Subscriber changes can now be done once, thus saving an operator the steps of manually repeating the same subscriber updates on the SDM. 26 910-6701-001 Revision A, June 2013