BAIC — Provisioning in batch mode through the Command File Loader

User Interfaces Release 9.1 Subscriber Provisioning Reference Manual There is a timeout of one minute between the "Start Transaction" and the "Commit" commands. If the "Commit" command is not sent out within one minute of the "Start Transaction" command, the XML provisioning requests are rolled back (changes not applied to database). Sending out provisioning requests in a ( ) syntax (without the 'StartTransaction' request) is still supported and the same actions are taken (Start transaction, Rollback, Commit), except automatically. In this case, the provisioning changes are applied to the database immediately. ... ... Rollback and stop if error --> ... --> Note:

It is not possible to send "Start Transaction", "Commit" or "RollBack" requests within a context or within a template definition. However, it is possible to issue a "Start Transaction" request, then execute several templates, then issue a "Commit" or "RollBack" (this would group several templates into a transaction). Template requests which are not sent between a "StartTransaction" and a "Commit" request are by default automatically executed within a transaction context, which means that a template will either be fully executed, or not executed at all.

When running a template, any failure encountered will automatically provoke a roll back of all the changes already processed from this template. All the requests in the template succeed or they are all rolled back. In order to provide details of when a template is not successfully executed, the SDM system returns the following error notification, which includes information on which request within a template has failed: while processing RequestTemplate, on request %1 with error code %2"/> Provisioning in batch mode through the Command File Loader The Tekelec system provides a batch mechanism called Command File Loader (CFL) that supports bulk provisioning.

A file must be generated containing the XML requests. Then the CFL tool is executed to process the XML requests in the file. The Command File Loader tool reads the XML request transactions and processes them one after another. Each file must always contain an authentication request for user authentication. The Invoking file (containing the request template instructions) must be setup so that it is framed by the following XML File tags: Request template1 Request template2 Request template3 … The Command File Loader supports XML Templates and can also support files without templates using the following XML request types.

Update Insert Delete Select Operation (i.e., Authentication request) 31 910-6701-001 Revision A, June 2013