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

Using the Process Developer Debug Console

Using the Process Developer Debug Console

The Console view is part of the Process Developer Debug perspective.
This view shows execution events and provides a view into the evaluation of expressions and results.
The following illustration shows a sample of the Console.
1
Terminate. Stops the current simulation
2
Removes all terminated launches
3
Scroll Lock. Automatically wraps long lines to avoid horizontal scrolling.
4
Clears console
5
Pin Console. Not applicable.
As your process executes, the following types of events are displayed:
Activity type, name, and path
Executing, completed normally, or completed with a fault
Example:
Receive:Executing </process/flow/receive>
Link name, link transition condition, and path
Status and evaluation of expression
Example:
Link receive-to-assess Condition true : bpws:getVariableData('request','amount') < 10000 </process/flow/links/link[@name='receive-to-assess']>
On Alarm
Duration or deadline
Wait
Wait value and simulated Wait value
Join Condition
Evaluation of expression
While, If, Repeat Until Condition
Evaluation of expression
Unhandled events
Ancillary event information
Tips for using the Console:
  • Use the right-mouse menu to go to an activity that has already executed.
  • Use the right-mouse menu to find a simulation event in the Console.


Updated March 30, 2020