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 Data Source

Using the Process Developer Data Source

Included in the Process Developer Template is a connection to the Data Source that is pre-defined to point to the Derby database included with the Process Server. Derby includes an embedded JDBC driver.
Note that Derby accepts only one connection at a time, so you cannot run the Process Developer embedded server while you are designing reports.
To view the connection configuration, open the Outline view, and expand Datasources. Double-click on the Process Developer data source, as shown in the illustration.
To change the configuration for a different Process Server, you must add the same Driver Class and Database URL that were configured for that server.
For example, if you have purchased Process Server with Apache Tomcat and want to configure the MySQL database on Apache Tomcat server, you would use the following settings:
Driver Class:
com.mysql.jdbc.Driver
Database URL:
jdbc:mysql://localhost:3306/ActiveVOS?useUnicode=true &characterEncoding=UTF-8&characterSetResults=utf8
If your server database connection was configured with any changes to the DDL script, or any configuration details, such as the User Name and Password, you must also update these settings. The User Name and Password shown are the default for all servers.
The JNDI URL for the data source is detected at runtime.
Use the three buttons as follows:
  • Manage Drivers
    : Pressing this button displays a dialog with two tabs. The first lets you manage JAR files used by your data source.
    The second lets you manage its drivers:
  • Test Connection
    : Pressing this button tests the connection to the data source.
  • Bidi Settings
    : (bidi stands for "bi-directinal") Pressing this buttons displays the Advanced Bidi Data Source Settings dialog box. Use the controls within it to set metadata and content Bidi formats.


Updated March 30, 2020