Integration

Hi guys,

I don't know if there is a thread that has already addressed this issue, but I couldn't find anything.

Here is the scenario. I have created Proxy Service X (http transport protocol) that routes a message to Business Service Y. Business Service Y calls myWebService that is deployed in a remote domain. I intentionally undeploy the EAR that contains myWebService in the remote domain. When Business Service Y tries to invoke myWebService it will error out, with the following message:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380002</con:errorCode>
<con:reason>Not Found</con:reason>
<con:location>
<con:node>RouteNode1</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>

Business Service Z is a standalone service that is used for sending messages to a queue. I have a Route Node Error Handler in Proxy Service X that uses a Service Callout to route messages to Business Service Z.

Now inside the Route Node Error Handler of Proxy Service X, I would like to retrieve the original xml request that was received by Proxy Service X and send it to a queue by making use of the previously mentioned Service Callout that routes messages to Business Service Z everytime the BEA-380002 type of error occurs.

When looking at Response of the Service Callout (by making use of reports), the inbound element of the http transport layer does not contain the xml request, but merely metadata of the message. How do I get the original xml request from the above-mentioned scenario?

Regards,
Ophola..