Data Processing Parsers

The purpose of a framer is to create service orders.

The main task of a parser in a protocol message flow is to break down the incoming protocol message frame(s) into service order data and eventually product orders. You may need to create a different parser for each type of driver that you deploy. The parser performs the following steps:

  1. Parse the current frame.

  2. Create and populate the service order data.

  3. Create and attach product orders (at least one is mandatory).

In fact, step 3 is commonly achieved by the Fulfillment Provisioning Catalog module.

Note:

The procedure for parsing the incoming frame depends on the protocol of the service management system from where the order originates.

The parser receives an incoming protocol message from a previous session module. It uses frame level information to create service orders.

For better configurability, you can use a Command Eval Script (CES) module (cesmodule::ScriptModule) to implement the framing function.

For better performance, you can use the following IDLos as a framework for your parser interface: 

package tcpca
{
        [ managedextent ]
        interface Parser : OSAStreams::Module
        {
                [ virtual ]
                void onPut(in OSAStreams::Message msg);
        };
};

As with other modules, a framer is instantiated when the corresponding Streams flow is loaded.

You can use the following IDLos as a framework for your parser factory interface.