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 Service

Simulating the Data Access Service

When you create the Process Deployment Descriptor for the process containing the Data Access service, you must specify the location of your database. Complete the deployment information as follows:
  1. On the Partner Links page, notice that the Partner Service Provider's Invoke Handler for data access is automatically set to System Service.
  2. If you are using a cloud process, in the edit field, replace the text, FILL_IN_DATASOURCE_JNDI, with one of the following:
    • The JNDI Name defined in your application server that is bound to the data source. There is no need to include the JNDI prefix. For example:
      jdbc/myDatabase
    • Similarly, for WebLogic and Websphere, no prefix is required:
      jdbc:/myDatabase
    • A URN that can be mapped to a JNDI Name or URL in the Process Console URN Mappings page. This option gives you a way to change the database connection information without refactoring and redeploying your process.
Note
: If you are deploying on-premise, you must also include the JNDI prefix as shown in this example:
java:comp/env/jdbc/myDatabase
For preliminary testing, if you want to set up a database connection within the server embedded in Process Developer, follow these instructions:
  1. In Process Developer, stop the embedded server, if it is running. For details, see Setting Up the Embedded Process Server.
  2. In the file system, in your Process Developer installation directory, navigate to the embedded server plugin. For example,
    [
    designer install directory
    ]\designer\plugins\org.activebpel.enginep_[
    versionNNN
    ]
    where versionNNN is the plugin version.
  3. In the
    org.activebpel.enginep
    plug-in, navigate to
    server\conf\Catalina\localhost
    and make a backup copy of the
    active-bpel.xml
    file. Then open the file.
  4. In the
    active-bpel.xml
    file, add a new
    <Resource>
    element within the
    <Context>
    element, as shown in the example:]
    <Resource driverClassName="driver_class_name" maxActive="100" maxIdle="30" maxWait="10000" name="jdbc/anyName" password="password" type="javax.sql.DataSource" url="url_of_your_db" username="db_login_name"/>
    Be sure to replace all attribute values with values for connecting to your database.
  5. Save the file and restart the embedded server.
  6. Be sure to add the JNDI name to the PDD of your process before deploying your BPR to the embedded server.


Updated March 30, 2020