Modeling Activation Tasks

You model activation tasks to integrate OSM with either and ASAP or IP Service Activator. You can model a process flow that includes one or more tasks that activate services in a network.

Note:

Before modeling activation tasks, ensure that you have defined the Design Studio preferences for the OSM SDK and WebLogic Server installations. See "Defining Order and Service Management General Preferences" for more information.

To model an activation task:

  1. Import an ASAP or IP Service Activator service cartridge.

    See "Importing Activation Cartridge Projects" for more information.

  2. Create an Activation Task entity.

    You create an Activation Task entity to hold all of the information necessary to send a request to the activation system, receive the response, update the order, and transition the task. See "Creating New Tasks" for information about creating tasks, and see "Designing Tasks and Activities" for information about creating tasks from the Process editor.

    Note:

    The first time that you create an Activation Task entity in a workspace, Design Studio automatically creates a new project to contain data elements necessary for integration between OSM and the activation system. This project is sealed and the data within should not be changed.

  3. Model the activation task data.

    You select the data that the activation task requires from the order data or from a data dictionary. See "Defining Task Data" for more information.

  4. Configure the mapping information needed to make the service action request to the activation system.

    See "Configuring Service Action Requests" for more information.

  5. Configure the mapping information needed to update OSM orders with the response data returned by the activation system.

    See "Configuring Service Action Responses" for more information.

  6. Configure state and status transitions for completion events and completion exceptions returned by the activation system.

    See "Configuring Service Action Response State and Status Transitions" for more information.

  7. Configure activation task details.

    You define the attributes that enable the activation task to execute properly in the Activation environment. See "Task Editor Details Tab" and "Task Editor Activation Task Details Tab" for more information.

  8. Define activation task compensation strategies.

    You specify how to compensate an activation task if the task is affected by amendment processing. See "Task Editor Redo Tab" and "Task Editor Undo Tab" for more information.

  9. Configure activation task states and statuses.

    A task state determines the milestone of a task in a process. A task status describes how a task was completed and determines the next task in the process. See "About Task States and Statuses" and "Assigning Task States and Statuses" for more information.

  10. Configure activation task permissions.

    You assign execution modes to roles for each task to specify which roles can perform the execution mode. See "Assigning Task Permissions" for more information.

  11. (Optional) Configure activation task jeopardies.

    You can configure conditional jeopardy notifications to alert users or systems that the activation task may be at risk. See "Task Editor Jeopardy Tab" for more information.

  12. (Optional) Configure task state automation events.

    You configure state-based event notifications to alert users or systems of changes to the activation task state. See "Task Editor Events Tab" for more information.