1 Getting Started with Design Studio for ASAP SRT
As part of a customer solution, solution designers and systems integrators can create Activation Service Request Translation (SRT) cartridges to translate service request data sent to Oracle Communications ASAP from customer relationship management (CRM), provisioning control, or other upstream systems.
The Activation SRT cartridge contains translation information that enables the SRT to map the contents of orders sent from upstream systems to a format that is recognizable and usable by ASAP.
Activation SRT cartridges (which you can use only with the SRT component of ASAP) are most commonly used when operation support systems (OSS) require a much higher level of data abstraction at the interface point into ASAP, or have significant data customization requirements at the interface point, such as data messaging or lookup requirements.
For example, consider that a telephony company is marketing a new service that includes a VoIP phone and a mobile phone. When a request to activate this service is sent to ASAP, the XML order is received by the SRT component. The SRT component translates the XML order into a format that enables the SRT to analyze the order contents. Next, the data in the order is mapped to the service actions and parameters that are required to activate the service bundle. This may involve executing lookups to derive additional data required for activation. The order is then sent to downstream components of ASAP for activation. During the execution of the order, events are generated and passed upstream to the SRT component. The SRT component translates these events to a form recognized by upstream systems and forwards them to the upstream systems.
See the following topics: