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

Partner Role Invoke Handlers

Partner Role Invoke Handlers

A Process Deployment Descriptor (.pdd) file describes the information required for a process to execute in the Process Server environment.
By default, the Process Server invokes an endpoint by looking up the service name in the WSDL to find the endpoint (for example, the <soap:address>) and using the standard engine invocation framework. You can select a different invocation method by making one of the following selections:
Invoke handler
Invokes an endpoint based on:
WSA Address
URL in the <wsa.Address>
field of the PDD file. For details, see
Selecting a Service for a Deployment Descriptor Partner Link
. Note that you can provide a URN and then map the URN to a URL in the Process Console. For details, see
Specifying a Replaceable URN/URL for an Endpoint Reference.
WSDL Service Port
URL in the Service's port section of the WSDL file. Select this to use the service address as is; that is, the engine only looks at the WSDL's service port at runtime. No changes are allowed to the service address. See
Selecting a Service for a Deployment Descriptor Partner Link.
WSRM:Address
Same as address above, except that the messages are sent using the WS-Reliable Messaging protocol. Select this handler if you will attach the reliable messaging policy assertion, described in
WS-Reliable Messaging. An addressable ReplyTo endpoint is required.
EJB Service
(
on-premises only
)
Deployed JARs, WSDL, and other resources created from an EJB Interface. Note that an EJB Service cannot be used on Apache Tomcat. It is supported on other application servers. For details, see
Creating a Java Interface.
Java Service
Deployed JARs, WSDL, and other resources created from a Java Interface. For details, see
Creating a Java Interface.
JMS Service
For details, see
Using a Java Messaging Service Invoke Handler. Note that an addressable ReplyTo endpoint is required.
REST Service
For details, see
Using a REST-based Service.
System Service
Partner role based on one of the System Services, such as
Server Log Service,
Email Service,
Identity Service
,
Reporting Service
,
Shell Command Invoke Service
,
Data Access Service
and
Using a REST-based Service
.
Process
BPEL process and PDD located in a workspace project and deployed to the same server as the calling process. For details, see
Creating a BPEL Process as a Service for Another BPEL Process
.
To select a process, see
Select Process Service
.
Select this option when deploying to Informatica Cloud.
Process:Subprocess
BPEL process and PDD located in a workspace project and deployed to the same server as the calling process. The process is a
subprocess
; that is, it is eligible for compensation within the enclosing scope of the calling process. For details, see
Creating a BPEL Process as a Service for Another BPEL Process
.
To select a process, see
Select Process Service
.
EJB Wrapper
Custom EJB you have written, packaged and deployed to A Process Server that supports EJBs. You can specify the JNDI location of the EJB as well as the query string required to invoke the endpoint. For details, see
EJB/Java Invoke Handler Properties Dialog
.
Java Wrapper
Custom Java class you have written, packaged and deployed to the server. You can specify the fully qualified class name for the Java class as well as the query string required to invoke the endpoint. For details, see
EJB/Java Invoke Handler Properties Dialog
.


Updated March 30, 2020