How to build the RejectedMessageHandler process?

Question

Hello All,
I am trying to build a RejectedMessageHandler process to send notification to administrator if any message has been rejected by Adapters.
I read this document.
http://www.oracle.com/technology/products/integration/adapters/pdf/Adapter_TN_004_Adapter_ErrorManagement.pdf
Then I downloaded the RejectionMessage.wsdl and JCAErrorHandling.xsd from SOA server. Then use the RejectedMessage in JCAErrorHandling.xsd as the input type for this Async RejectedMessageHandler process.
The add rejectedMessageHandlers information in bpel.xml of my Adapter test process to call the RejectedMessageHandler process.
<property name="rejectedMessageHandlers">
bpel://default|RejectedMessageHandler|initiate|RejectedMessage
</property>
The un-well formatted message will go to the defined directory, but no RejectedMessageHandler instnace has been created.
Any suggestion.
Regards,
Kerr

Answer 1

Hi Kerr,
<property name="rejectedMessageHandlers">
bpel://<bpel-domain[:<password>]>|<process-name>|<operation-name>|<input-message-part-name>
</property>
(<password> for domain if not "bpel" - can be encrypted - "[]" means optional)
for example
<property name="rejectedMessageHandlers">
bpel://default|JCA-RejectionHandler|handleRejection|message
</property>
This rejection handler will send the bad message to another (designated error handling) BPEL process. The user can thus define a process with a Receive operation of his own choosing (WSDL and BPEL src) - the only constraint is on the Message Type of the message that will be sent to this rejection handler. It must be declared to have the type "RejectedMessage". This can conveniently be achieved by importing the "xmllib" resident WSDL "RejectionMessage.wsdl" which defines such a message:
<message name="RejectionMessage">
<part name="message" element="err:RejectedMessage"/>
</message>
An xmllib WSDL import (from another WSDL) is achieved using the "well-known" URL
<import namespace="http://xmlns.oracle.com/pcbpel/rejectionHandler"
location="http://localhost:9700/orabpel/xmllib/jca/RejectionMessage.wsdl"/>
i.e. the Receive operation WSDL which the user defines for his Rejection Handler BPEL Process would simply contain this import and then the port type would reference this:
<definitions ...
xmlns:rej="http://xmlns.oracle.com/pcbpel/rejectionHandler"
<portType name="MyRejectionHandlerPortType">
<operation name="myHandleRejectionOperation">
<input message="rej:RejectionMessage"/>
</operation>
</portType>
WSIF Based Rejection Handler
<property name="rejectedMessageHandlers">
wsif://<wsif-wsdl-location>|<operation-name>|<input-message-part-name>
</property>
for example
<property name="rejectedMessageHandlers">
wsif://file:/C:/orabpel/samples/test/ErrorTest/FileAdapterWrite.wsdl|write|message
</property>
This last rejection handler lets the user configure any type of WSIF WSDL (JCA, EJB, JMS, HTTP, Java etc), i.e. any kind of Service which can be reached via WSIF - as the bad message handler. The exact same constraint vis-a-vis the Message Type as described above for the BPEL Process Rejection Handler also applies here.
You might want to use WSIF for the same as mentioned in : http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b31005/life_cycle.htm#CIAGHAAD
Hope that helps!
Cheers
A