Server User Guide > Custom Invoke Handlers > Adding the Custom Invoke Handler Attribute to the PDD
  

Adding the Custom Invoke Handler Attribute to the PDD

To bypass the Process Server's standard invocation framework, you must add the custom invoke handler attribute to the partner role in the Process Deployment Descriptor (PDD) file.
The custom invoke handler attribute tells the engine to use a custom invocation for the partner service. Add the attribute, along with optional message parameters to pass into the service, and then deploy the business process archive (BPR) file.
Depending on your invocation implementation, you must specify the URI information for a Java class or EJB container.
Java Class Implementation
Use the Process Developer's PDD wizard to specify a Java invoke handler. The following syntax show how to include the custom invoke attribute in the PDD file for a Java class file.
<partnerLink name="qname">
  <partnerRole endpointReference="type"
   invokeHandler="java:org.ActiveVOS.rt.axis.bpel
    .MyInvokeHandler?parameters+
...
  </partnerRole>
</partnerLink>
Example:
invokeHandler="java:org.ActiveVOS.rt.axis.bpel.
AeApproverInvokeHandler?type-namespace=
http://tempuri.org/services/loanapprover&
        type-localpart=approvalMessage&amp;maxLoan=1000000">
EJB Implementation
The following syntax show how to include the custom invoke attribute in the PDD file for an EJB.
<partnerLink name="qname">
  <partnerRole endpointReference="type"
   invokeHandler="ejb:jndiLocation/
    MyInvokeHandler?parameters+
...
  </partnerRole>
</partnerLink>
The jndiLocation defines the context that specifies where to look for the custom invoke handler.
Example:
invokeHandler="ejb:ejb/AeApproverInvokeHandler?type-namespace=
http://tempuri.org/services/loanapprover&
        type-localpart=approvalMessage&maxLoan=1000000">