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

Simulating the Data Access Invoke Output

Simulating the Data Access Invoke Output

You can test the actual Data Access request and response during simulation by performing some additional steps prior to beginning simulation. The steps involve using the Eclipse Data Source Explorer that is bundled with Process Developer.
Using the Data Source Explorer, you can generate sample data from an actual statement execution and export the data to Process Developer in the correct schema format. This technique makes the actual data returned from the result set available to a process variable to which you are mapping data.
Step 1. Set up a database connection:
  1. Select
    Window > Show View > Other > Data Management > Data Source Explorer
    .
  2. Right-mouse click on Database Connections and select
    New
    .
  3. Select a Connection Profile Type from the list. For example, select MySQL.
  4. Name the new profile, and select
    Next
    .
  5. On the Driver page, select your database driver from the list. If the driver is not in the list, select
    New Driver
    and specify a driver definition.
  6. Enter the URL to connect to your database. For example, the default URL for MySQL is j
    dbc:mysql://localhost:3306/[database name]
    .
  7. Select Test the Connection, and if successful, finish the wizard.
  8. Notice there is a new database listed in the Data Source Explorer.
Step 2. Connect to the database and execute a statement:
  1. In the Data Source Explorer, right-mouse click on your database and select Connect if needed. Expand the tree, and you can see an outline of all the tables in your database.
  2. Right-mouse-click on your database and select Open SQL Scrapbook.
  3. Select your database from the Name list.
  4. Your Data Source Explorer and SQL Scrapbook window should look similar to the following example:
  5. If your Data Access invoke is based on the
    execSQL
    operation, copy and paste your single execution statement into the SQL Scrapbook.
  6. Right-mouse click and select
    Execute Selected Text
    . Notice that the results are returned in the SQL Results tab.
  7. For the
    execMultiSQL
    operation, copy and paste your statements into the SQL Scrapbook. Right-mouse click and select
    Execute All
    .
Step 3. Save the SQL Results as sample data:
  1. In the SQL Results view, right-mouse click and select
    Save > Current Result
    .
    You must select Current Result for a a single statement execution and All Results for multiple statement execution. The format of the data differs depending on your selection.
  2. In the
    Save Result
    dialog, browse to your Data Access project in your workspace and select the
    sample-data
    folder. Name and save your file into this location.
  3. In the File Type box, select Process Developer Data Access Sample. Then set the Output encoding to UTF-8. The following example shows all settings:
  4. Select
    OK
    .


Updated March 30, 2020