User Interfaces Release 9.1 Subscriber Provisioning Reference Manual 2. Instead of using the SOAP header, all messages sent to/received from the system are in the following format: |---------------------| | Header | XML | |---------------------| Where Header is a 4 bytes integer in network byte order* indicating the size in bytes of the XML part. The maximum allowed value for requests is 14000 bytes (excluding the header). Bigger requests will be rejected by the system. There is no limit for the size of the reply. Note: "Network byte order" refers to the standard byte order defined in the IP protocol. It's what you receive when you invoke 'htonl' (Host To Network Long).
It corresponds to big-endian (most significant first). It is a zero-padded 4 bytes value. External commit protocol The SDM system supports provisioning transactions with new "external commit" commands. The following commands are supported and allow the Network Operator to be able to manually control the XML provisioning transactions sent to the system's OAM&P Manager: This allows the Network Operator to send a large amount of requests within one single transaction by sending a 'Start Transaction' and a 'Commit' request (Stop transaction and commit to database). Note:
These new requests are only available on a direct XML/TCP connection, not on a SOAP connection When sending XML provisioning transactions to the SDM system, the following requests must be sent in the following order: 1. The "Start Transaction" request must be sent first to indicate the beginning of a transaction 2. The template or text file with all the provisioning requests can then be sent out as usual. 3. The "Rollback" request or the "Commit" request can then be sent. If the system returned an error while processing the provisioning requests, you must send out a "Rollback" request in order to make sure the data changes processed prior to the error are not committed to the database.
In this case, no provisioning changes are applied to the database. In the other case where all the provisioning requests are processed successfully (no error is returned), you must send out a "Commit" request in order to make sure the provisioning changes are committed to the system's database. The "Commit" request indicates the end of the transaction. ... ... ... Note: If a "Start Transaction" command is sent, and then the connection is lost or the user logs off without sending a "commit" or "rollback" command, all pending requests are rolled back. One XML session can have one transaction at a time.
If a "Start Transaction" command is sent, another "Start Transaction" command will commit the pending requests and start a new transaction. 30 910-6701-001 Revision A, June 2013