Table of Contents

Search

  1. Preface
  2. Part 1: Using Process Developer
  3. Part 2: Creating and Modifying Processes
  4. Part 3: Functions, Events, Errors, and Correlation
  5. Part 4: Testing and Deployment
  6. Part 5: Process Central and Process Server (On-Premises)

Process Developer

Process Developer

EJB/Java Invoke Handler Properties Dialog (on-premises only)

EJB/Java Invoke Handler Properties Dialog (on-premises only)

A custom invoke handler bypasses the standard Informatica Business Process Manager invocation framework. The standard framework invokes a partner service by packaging a message into a SOAP request and sending it over the HTTP protocol to the designated service endpoint address.
A custom invoke handler bypasses the standard Business Process Manager invocation framework. The standard framework invokes a partner service by packaging a message into a SOAP request and sending it over the HTTP protocol to the designated service endpoint address. You can create a different invocation mechanism by implementing an interface in the Web service input/output library.
Assuming you have written a custom invoke handler, you can complete the Invoke Handler Properties details in the PDD editor by filling in details for one of the following:
  • EJB
    An EJB invocation is appropriate only for Process Servers capable of handling EJBs. For an EJB invocation, specify the JNDI location of the EJB as well as the query string required to invoke the endpoint. For example:
    Name:
    ejb/jndiLocation/MyInvokeHandler
    Query String:
    invokeHandler= "ejb:AeApproverInvokeHandler?type-namespace= http://tempuri.org/services/loanapprover& type-localpart=approvalMessage&maxLoan=1000000"
  • Java
    For a Java class invocation, specify the fully qualified class name for the Java class as well as the query string required to invoke the endpoint. For example:
    Name:
    java.org.ActiveVOS.rt.axis.bpel.MyInvokeHandler
    Query String:
    parameter=someValue
    invokeHandler= "java:org.activebpel.rt.axis.bpel.AeTestInvokeHandler? type-namespace= http://localhost:8080/active-bpel/services/OrderIdService& type-localpart=getNextOrderIdResponse& getNextOrderIdReturn=wsio-109"
Be sure to package and deploy the invoke handler to the server.

0 COMMENTS

We’d like to hear from you!