Skip Headers
Oracle® Communications Design Studio Modeling Activation
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

Java Processor Class Example

The following is a coding example for an atomic action.

From the Java editor of the Package Explorer view:

  1. Create an atomic action and an action processor.

    See "Creating Model Elements" for more information.

  2. Select an ADD action and LINE entity for each.

  3. In the Atomic Action editor, map the action processor to the atomic action.

    See "Understanding Model Element Relationships" for more information.

  4. In the Parameters tab, right-click in the Parameters area and select Simple Data Element or Select Structured Data Element. See "Searching for Simple and Structured Elements" for more information.

  5. In the Parameter Details area, define values to the ASAP run-time type parameters.

  6. In the Mappings tab, click the mapped action processor to open the Action Processor editor.

  7. Select Java Action Processor (with Code Generation).

  8. Click New.

    The Studio Activation Java Implementation Wizard appears.

  9. Click Finish.

    A new atomic action class appears in the Java editor with basic code, such as the entry point, get functions to get the parameters defined in the atomic action, and, in the end portion, sendRequests and how the response is handled.

    Surrounding text describes implement_code.gif.
  10. Build the MML (the message itself) using the Eclipse message format.

    Use methods and classes. If no parameters are available in the atomic action, use a string to build the MML.

  11. Send the message to the switch using the send request.

  12. Set the user-defined exit type.

Related Topics

Understanding the Java Processor Class

Working with the Action Processor

Modeling Entities

Creating Model Elements

Understanding Model Element Relationships

Understanding Java Libraries in Design Studio

Understanding Unit Testing

Working with User-Defined Exit Types