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

Editing a B-unit File

Editing a B-unit File

You can design your own B-unit tests with the help of the B-unit editor. Double-click a B-unit file in Project Explorer to open the B-unit editor.
The B-unit editor displays the Design tab, containing an Outline pane and a Details pane. The Outline displays different sections of a B-unit file that you can select to edit in the Details pane.
The following is a description of each node in the B-unit Outline. For more details, select the node name.
  • BPEL Unit (Root)
    Specifies the BPEL, WSDL, Schema and other resources used in the test. The resources provide data that creates the set of deployed processes and resources for the Process Server engine. When the B-unit test is started, all of these resources are deployed to the engine much as they would be when the standard engine starts up. The standard static analysis rules for Informatica Business Process Developer are run against each BPEL process identified in the B-unit to ensure that there are no errors in the BPEL or environment.
    The Trace option controls console logging output. It is enabled by default and can be useful for tracking down assertion failures if the B-unit view does not provide adequate debugging information.
  • Extensions and Extension Activities
    Extensions specify Logical People Groups that are WS-HT (Human Task) Extensions. Extension Activities specify People activities that are BPEL for People Extension activities.
  • Invokes
    Specifies invoke activities.
  • Alarms
    Specifies Wait activities and onAlarm handlers for picks and event handlers. The alarms and invokes elements contain information about each alarm and invoke within the process that is expected to execute during the test. These elements should be thought of as re-active in the sense that they react to the execution of an alarm or invoke within the process. They do not cause an alarm or invoke to execute, but rather wait for the engine to signal that an alarm or invoke has executed and then match that activity within the process to a declaration within the B-unit. Once matched, the B-unit declaration will provide assertions, simulated response/fault/alarm.
  • Commands
    Sends messages to the B-unit test engine to execute the test logic. The commands element contains all of the commands that are sent into the engine when the B-unit test executes. These elements should be thought of as active in the sense that they are actions taken by B-unit when it starts the test. Each command is executed in sequence. If the command has an
    asynch="true"
    attribute then this command is executed on a separate thread. The B-unit test is considered completed when all commands complete. The most common command is the sendMessage command and is the only required command for each B-unit.


Updated March 30, 2020