Configuring Service Bundles

There are two steps to configuring service bundles in ASAP, each corresponding to a separate layer of run time translation that is performed by ASAP.

To configure service bundles:

Write an XSL translation (XSLT) that accepts an XML document from an upstream system and outputs an XML document, consisting of name value pairs, that is used by the second layer of translation.

When complete, the XSLT is placed in a Oracle Communications Design Studio library in a location that ensures it is deployed by Design Studio to an ASAP environment (and possibly source controlled). The translation enables usage of the service bundles that are configured in step two. The SRT translates order data received from upstream systems into a format recognizable by downstream components of ASAP. The SRT also translates responses from ASAP back into a format recognizable by the upstream systems. Developers may need to create and configure lookups to obtain additional data required to activate the service, but unavailable from upstream systems. Developers may also use lookups to convert specific data elements into a format that is expected by the configuration further downstream.
Import one or more Activation Service cartridges into Design Studio, create a customer-specific service model, set up the Activation SRT cartridge, and model the required service bundles by mapping the upstream system order data to the service actions selected for use in the service bundles.

This step assumes that you have written the XSLT and can import upstream parameters into Design Studio, or that you manually configured upstream parameters and mapped them to service action parameters. See "Understanding Upstream Interface Parameters" and "Modeling Service Bundles" for more information.