Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Implementing: Step 1

Implementing: Step 1

Your first task is to create a function context that is a new class that implements the
IAeFunctionContext
interface.
This class exposes one public method:
getFunction(String)
. It returns an object of a type that implements the IAeFunction interface. The method uses the String argument to indicate the local name of the function and then select that object.You can implement multiple custom functions via one function context class.
getFunction()
throws an AeUnresolvableException if it is unable to locate the desired function by name.
Annotations
You add the
@AeFunctionContext
annotation to annotate the class at class level.
Add the
@AeFunctionUnit
annotation at the method level, for each function unit that you want to display in the Expression Builder function list.
The following example shows the function context:
@AeFunctionContext(name="myContext", namespace="myns") public class CustomContext implements IAeFunctionContext { @AeFunctionUnit( prefix = "ld", display = "MyLDAP", hoverText = "My LDAP Functions", functions = { @AeFunction( syntax = "${prefix}:getOrgUnit(${caret})", display = "getOrgUnit(id)", hoverText = "Returns OU details"), @AeFunction( syntax = "${prefix}:getSiblings(${caret})", display = "getSiblings(id)", hoverText = "Returns siblings nodes"), } ) public IAeFunction getFunction(String aFunctionName) throws AeUnresolvableException { } }
where:
  • @AeFunctionContext name
    is the display name of the function context in the Process Console Catalog
  • @AeFunctionUnit
    represents a group of functions
    • prefix
      is used for all functions in the unit
    • display
      is the unit name in the Expression Builder function list
    • hoverText
      is the unit's hover help
    • functions
      is the list of functions
  • @AeFunction
    represents the function
    • syntax
      is the syntax of the function added to the Expression text box when the function is double-clicked. Note that the syntax includes the
      ${prefix}
      and the
      ${caret}
      . The cursor appears in the column set by the caret token.
    • display
      is the function name in the Expression Builder function list
    • hoverText
      is the function's hover help


Updated March 30, 2020