WS-ReliableMessaging using OSB WS protocol

Question

Hi All,
We have a requirement to implement WSRM in OSB.
Our invocation pattern is
BPEL(Async)=> OSB(ASync)=>External APP(Sync)
We have chosen WS protocol and WSRM policies for both proxy and business services.
What I obseved is BS is sending WSRM payload to target application which is unwanted.
Obviously target application doesn't understand WSRM payload.BS has to discard this handshaking command and send ack to PS WSRM layer.
Anybody has worked on this WSRM in OSB?
BS is sending below payload to target application
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<wsa:To xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://soa.part.com:7201/soa-infra/services/default/Order/orderimport_client_ep</wsa:To>
<wsa:FaultTo xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
</wsa:FaultTo>
<wsa:MessageID xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">uuid:AdminServer:72c210997f83a732:-3e03b3bf:134156f2f57:-64e8</wsa:MessageID>
<wsa:Action xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
<wsa:ReplyTo xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<wsa:Address>http://osb.part.com:7101/alsb/ws/_async/AsyncResponseService</wsa:Address>
<wsa:ReferenceParameters xmlns:serviceidentity="http://www.bea.com/ServiceIdentity"><serviceidentity:ServiceIdentity xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" xmlns:serviceidentity="http://www.bea.com/ServiceIdentity">
<serviceidentity:ServerName>AdminServer</serviceidentity:ServerName>
<serviceidentity:ServiceName>weblogic.wsee.conversation.msg.cluster.service</serviceidentity:ServiceName>
</serviceidentity:ServiceIdentity>
</wsa:ReferenceParameters>
</wsa:ReplyTo>
</env:Header>
*<env:Body xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">*
*<wsrm:CreateSequence>*
*<wsrm:AcksTo xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm"><wsa:Address>http://osb.part.com:7101/alsb/ws/_async/AsyncResponseService</wsa:Address>*
*<wsa:ReferenceParameters xmlns:serviceidentity="http://www.bea.com/ServiceIdentity">*
*<serviceidentity:ServiceIdentity xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility">*
*<serviceidentity:ServerName>AdminServer</serviceidentity:ServerName>*
*<serviceidentity:ServiceName>weblogic.wsee.conversation.msg.cluster.service</serviceidentity:ServiceName>*
*</serviceidentity:ServiceIdentity></wsa:ReferenceParameters></wsrm:AcksTo>*
*</wsrm:CreateSequence>*
*</env:Body>*
</env:Envelope>
Regards,
Praveen
Edited by: Venkat K.V on Dec 20, 2011 4:10 AM

Answer 1

The 8.1 version of reliable messaging does not conform to the WS-ReliableMessaging specification, as that specification was not available at the time of 8.1 development. The next major release of WLS will contain a full WS-ReliableMessaging implementation.