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

Testing XQuery Functions in the XQuery Editor

Testing XQuery Functions in the XQuery Editor

You can write a test script for your functions and execute the script in the XQuery Editor. Process Developer provides a default interpreter for script execution.
For example, create a new
.xq
file, and write a simple test script where you hard-code a function argument as in the
Kitty
argument below:
xquery version "1.0" encoding "utf-8"; import module namespace xyz ="myFunctions" at "hello.xq"; xyz:sayHello('Kitty')
To run this script, right-mouse click in the editor and select
Run As > XQuery
.
Passing an External Value to a Test Script
If the test script has external variables defined, values for those variables can be passed as arguments from the Run As launch configuration. The following is a simple script that takes in an external variable, followed by a description of how to create the script argument:
xquery version "1.0" encoding "utf-8"; import module namespace xyz ="myFunctions" at "hello.xq"; declare variable $ip as xs:string external; xyz:sayHello($ip)
Create a Run As Configuration:
  1. Right-mouse click in the editor and select
    Run As > Run Configurations
    .
  2. Select New, and add your project name and test script name on the first page.
  3. On the Arguments page, add a Script Argument, such as
    ip="Kitty"
    .
  4. Run your named configuration.
Customizing the Interpreter Behavior
Process Developer includes a default Saxon interpreter. You can change the arguments to this interpreter by selecting
Preferences > XQuery > Interpreters
.
You can configure the default Process Developer interpreter by double-clicking it. Interpreter arguments can be changed based on the development needs. Documentation for the arguments can be found at the following URL: http://www.saxonica.com/documentation/using-xquery/commandline.xml
Do not change the first argument, which is the class name,
org.activebpel.rt.bpel.ext.expr.impl.xquery.AeQuery
.


Updated March 30, 2020