The glossary contains a list of terms and their definitions as they relate to Oracle Communications MetaSolv Solution (MSS) documentation:
The activation framework consists of the MetaSolv Solution XML APIs and the WebLogic Workshop. The environment lets you create workflows for the APIs that accomplish the tasks you want to integrate between MetaSolv Solution and ASAP.
The activation task is a task on a provisioning plan (in MetaSolv Solution) assigned to an order that triggers a gateway event to set the activation process in motion. Although a gateway event can be associated with any task in the provisioning plan, Oracle recommends creating a task called Activate for the purpose of triggering the gateway event. The Activate task should be placed as close to the Due Date task on the provisioning plan as possible.
Atomic Service Description Layer (ASDL)
An ASDL is a lower-level ASAP command that describes atomic operations to be applied to a network element by ASAP. When the Service Activation Request Manager (SARM) translates (CSDL) commands into ASDL commands, the parameters required for each ASDL command are obtained from the originating CSDL command.
Common Service Description Layer (CSDL)
A CSDL is an ASAP command associated with a particular work order. The CSDL command is associated with one or more operations on one or more network elements. Each CSDL command has a configuration record that you can set up. This record contains the following attributes:
name: the CSDL name should begin with the constant ”C” to represent CSDL, followed by a series of tokens separated by the underscore (”_”) character. Specifically, C_<technology>_<software load>_<action>_<service>. All of the characters contained in a CSDL command must appear in uppercase, for example:
C_HLRPS_MSP8_ADD_CFB
rollbackOnFailure: a true or false flag that indicates whether rollback is required for a CSDL.
priority: the priority of a CSDL within the work order.
failEvent: the event that is triggered if a CSDL fails. The event can either be system or custom.
completeEvent: the event that is triggered if a CSDL completes successfully. The event can be system or custom.
Any parameter required by an ASAP cartridge but not defined in MetaSolv Solution must be defined as a custom attribute. Custom attributes can be defined for network elements, connections, and the relationship between the physical and virtual connection.
For example, the ASAP integration for the Nortel DSLAM does not require equipment information, but it does require a parameter called Profile Name. MetaSolv Solution does not carry this parameter on the equipment specification, but the parameter can be defined as a custom attribute for the DSLAM network element.
DSL offers broadband service over ordinary copper telephone lines. Most DSL technologies allow the simultaneous transmission of both analog and data signals on the same telephone line.
A gateway event is triggered when a special task associated with an order is worked in the MetaSolv Solution Work Management module. For example, when the activation task is worked in the Work Management queue, an activation gateway event for the type of service to be activated is triggered and sent to the integration layer's event processor, which uses the Activation API to request the appropriate data from MetaSolv Solution to send to ASAP.
POTS (Plain Old Telephone Service)
A POTS order consists of an electrical path (line) between a service provider switch and a subscriber. The line is associated with an individual telephone number that can be used for incoming and outgoing telephone calls. The line can also have associated features such as call forwarding or call waiting.
WebLogic Integration Message Broker Channel
A Message Broker channel has similar properties to a Java Message Service (JMS) topic, but is optimized for use with WebLogic Integration processes, controls, and event generators. Within a WebLogic Integration application:
Message Broker Publish controls are used by process or Web service instances to publish messages to a Message Broker channel.
Event generators that receive outside events route them as messages to a Message Broker channel.
Subscription start nodes start processes upon receipt of a message from a Message Broker channel. This constitutes a static subscription to the channel.
Message Broker Subscription controls are used by process or Web service instances to receive messages from a Message Broker channel. This constitutes a dynamic subscription to the channel.
Publishers to a Message Broker channel can pass message metadata with the message. This metadata can be received by the subscriber as a parameter.
Channel files define the channels available in a deployed application. To restrict the messages routed to static or dynamic subscribers, XQuery filters can be applied against message metadata (if the metadata is typed XML) or message body (if the body is string or typed XML). All subscribers registered to receive a message on a channel receive the message, subject to any filters they have set up.