Skip Headers
Oracle® Communications Design Studio Modeling OSM Processes
Release 7.2.4
Go to Design Studio Help Home
Go to Table of Contents
Go to Feedback page

Go to previous page
Go to next page
Mobi · ePub

Configuring Automation Plug-in Properties

After you add a plug-in to your automated task, you define the plug-in properties.

To configure automation plug-ins:

  1. From the Studio menu, select Show Design Perspective.

  2. In the Studio Projects view, double-click an Automated Task entity.

    Design Studio displays the entity in the Automated Task editor.

  3. Click the Automation tab.

  4. From the Automation list, select an automation plug-in.

  5. Click Properties.

    The Automation Plug-in Properties tabs are displayed.

  6. Click the Details tab.

    In the Details tab, you can name the plug-in and identify the user whose credentials will be used to run the automation plug-in. See "Properties View Details Tab" for more information.

  7. Click the Execution Mode tab.

    In the Execution Mode tab, specify the execution mode of notification automators of tasks. For example, when you define event notifications on tasks, you can choose for the notification to be triggered only in Do mode and not in Undo mode.

  8. (For internal event receivers only) Click the Compensation tab.

  9. In the Compensation tab, specify the execution modes in which the plug-in will run when invoked.

    See "Properties View Compensation Tab" for more information.

  10. (For external event receivers only) Click the External Event Receiver tab.

    Define the name of the external system from which the plug-in receives messages. Additionally, you can define whether the plug-in filters for specific properties on the incoming message header or body. Finally, you can provide specific connection information if the messages are retrieved from an external system. See "Properties View External Event Receiver Tab" for more information.

  11. (For external event receivers only) Click the Correlation tab.

    Map messages from external systems to specific OSM tasks. You can use the JMSCorrelationID or enter an XPath expression to filter for a specific element in the XML body of the message. See "Properties View Correlation Tab" for more information.

  12. (For XSLT types only) Click the XSLT tab.

    Define where the XSLT style sheet is located, caching properties for the style sheet, and the exit status that the plug-in should use if it throws an exception.

    See "Properties View XSLT Tab" for more information.

  13. (For XQuery types only) Click the XQuery tab.

    Define where the XQuery file is located, caching properties for the file, and the exit status that the plug-in should use if it throws an exception.

    See "Properties View XQuery Tab" for more information.

    Note:

    XQuery automation types cannot be implemented when using releases prior to OSM 7.0.
  14. (For Sender type automation plug-ins only) Click the Routing tab.

    Define where the automation plug-in should send messages, and where the external systems should send responses. See "Properties View Routing Tab" for more information.

  15. Click the Information tab.

    Document the intended use of the automation plug-in.

  16. Click Save.