WS Reliable Messaging

Hi,
I was able to configure WS-ReliableMessaging in WebLogic server 9.2 based upon the provided reliable example. However, when I try to import the WS-Policy file provided in the reliable example into the AquaLogic Service Bus, I get this error:
WS-policy "service/service-rmpolicy" contains a policy assertion with qname "{http://schemas.xmlsoap.org/ws/2005/02/rm}RMAssertion". This assertion is not recognized and will be ignored. Make sure the namespace declaration and local-name for this assertion are correct.
So I'm assuming that this is supported in the server and not in the bus. Is this correct?

WSRM is not fully supported in ALSB.

Similar Messages

Wert SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID and no WSRM assertion provided.

Hi All,
Im trying to call this Webservice in SOAP UI and Im getting this error.
The webservice , I Need to use is:
BusinessPartnerSUITEBulkReplicateRequest_In
http://es-workplace.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/render.asp?id=84B45EB7B18A11DE2B8D000F20FCB6A9&fragID=&pa…
Can you please help me to avoid it.
thank you for your help
Gireesh P.
Error Log:
Wert SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID and no WSRM assertion provided.

Hi Tim,
For this error following are the places that needs to be checked.
1. In C4C the protocol defined in the Communication System should be 5 - Web Services
2. In C4C Communication Arrangement should have the right protocol selected
3. In PI make sure the Communication Channel's are created using provided Communication Channel Templates as part of the standard PI content.
In other words just follow the integration guide available in SMP to avoid such errors.
Hope this helps.
Thanks,
Prakash

Web Service reliable messaging in PI 7.1

Hello Experts,
I am working on a POC on Web Service Reliable Messaging.
Anyone, Pls send me the detailed scenario on how to implement the same in PI 7.1.
I have searched in SDN but i cud not find much info specific to this.
Thanks in Advance.
Regards,
Swetha.

Hi Swetha ,
Please try:
Configuring Web Services Reliable Messaging
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/741a3dfcfa0eede10000000a155369/content.htm
Preview of Web Services Reliable Messaging in SAP NetWeaver Process Integration 7.1
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/304335f7-f33c-2a10-ae80-9c9ffdc86415
Web Services-Based Connectivity
Configuring Web Services Reliable Messaging
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/109aa318-5aa6-2a10-799d-a495383c1e01
Regards
joel
Edited by: joel trinidade on Apr 9, 2009 11:05 AM

Web services reliable messaging in weblogic 9

Hi Weblogic web services gurus,
I have some questions regarding the reliable messaging support in wls9 of web services.
1. Since the SAF used for persistent storage, does weblogic support the sequence recovery when system failures? Or sequence can't accorss system failures?
2. For the response sequence created by the web services service provider, what is the RM policy used? From the the wsdl file, we can see the policy only attach to the input message part of operation section.
Thank you very much!
Wayne Chen

Someone please reply. I'm clueless. Are they saying the webservices reliable messaging has already been implemented using ABAP LUW and is available in the workbench? If so how to use it ito create a reliable webservice? Why are they showing some PL/SQL like code then? It is all unintelligible to me as I haven't used any of these.
Edited by: convicted on May 11, 2011 10:59 AM

Inbound Web Service calls get error "Reliable Messaging(RM) configured, but no Message ID..."

We are setting up the Communication System and Communication Arrangement "Business Partner Replication from SAP ERP".
For protocol, we are using Type 5 - WebServices. See screenshot below.
Our error is that when we send webservice calls to our C4C, we get messages:
1. Web service response is "Web service processing error; more details in the web service error log on provider side"
2. Backend error messages is "SRT: Plain SOAP: Reliable messaging (RM) configured, but no Messaging ID and no WSRM assertion provided"
We have sent messages from PI and also independently thru soapUI.
So it seems the C4C in the backend is stuck on the RM messaging protocol setting.
Appreciate any and all assistance.

Hi Tim,
For this error following are the places that needs to be checked.
1. In C4C the protocol defined in the Communication System should be 5 - Web Services
2. In C4C Communication Arrangement should have the right protocol selected
3. In PI make sure the Communication Channel's are created using provided Communication Channel Templates as part of the standard PI content.
In other words just follow the integration guide available in SMP to avoid such errors.
Hope this helps.
Thanks,
Prakash

Reliable Messaging with a non @oneway method

Hi experts,
first of all, I'm new in the whole SAP-Application-Server business. I hope, i will give you enough and the correct information you need to follow and answer my problem.
I'm experimenting with Web Service Reliable Messaging. It works pretty fine with the IBM Rational Application Server. Now i would test it with the SAP Application Server, and i was wondering if there is no way to activate reliable messaging at a method with a return type different from null? This is what the documentation says and i got error messages when i tried it.
[Configuring Web Services Reliable Messaging|http://help.sap.com/saphelp_nwpi71/helpdata/en/46/741a3dfcfa0eede10000000a155369/content.htm]
Is there any opportunity to avoid this or a easy solution? I couldn't belief it. Is there no way to implement a simple web service, containing a method which return the current system time, and deliver it reliable to the requesting client?
I thank you for every little input, hint, advice, ...
Best regards
Matthias
Edited by: Matthias Brk on Oct 15, 2008 1:12 PM

is my topic in the wrong forum category? or is the topic the problem and nobody knows a solution?
I'm looking forward to any answer.
Best regards
matthias

Use of Reliable Messaging between WebLogic and a different vendor

Hello,
We have developed an application that is running on the WebLogic App Server v8.1
sp1.
Recently we have received a request/query on providing reliable SOAP messaging
from our application to 3rd party.
I have read the documentation on Reliable messaging support and have noted that
it is only supported between two WebLogic Application servers.
My questions are, since we do not have control of the 3rd party's application,
and it may not be based on a WebLogic App Server:
1. Will this work?
2. Does anyone have any idea of the type of issues that may be experienced?
3. How close is the implementation to the WS Reliable Messaging specification?
So, if the other party was based on an IBM or Microsoft implementation is this
likely to work?
It goes without saying that any work done would need to be very throughly tested
and qualified.
I have looked through the WebLogic Documentation on WebServices as well as searching
this newgroup for other posts on this topic, hopefully I have not missed anything
(If so, my apologies.)
Thanks,
Mike Shea.

Bruce Stephens <[email protected]> wrote:
Hi Michael,
The short answer, at this time, OOTB, WS-RM interop with an unknown
vendor would be doubtful. For a longer answer, David Orchard has a good
review of the emerging web services specs [0]. You might consider ebXML
messaging [1] as a more mature solution.
Thank you Bruce. I will look at these docs.
Mike S.
Hope this helps,
Bruce
[0]
http://dev2dev.bea.com/technologies/webservices/articles/ws_orchard.jsp
[1]
http://e-docs.bea.com/wli/docs70/ebxml/getstart.htm
Michael Shea wrote:
Hello,
We have developed an application that is running on the WebLogic AppServer v8.1
sp1.
Recently we have received a request/query on providing reliable SOAPmessaging
from our application to 3rd party.
I have read the documentation on Reliable messaging support and havenoted that
it is only supported between two WebLogic Application servers.
My questions are, since we do not have control of the 3rd party's application,
and it may not be based on a WebLogic App Server:
1. Will this work?
2. Does anyone have any idea of the type of issues that may be experienced?
3. How close is the implementation to the WS Reliable Messaging specification?
So, if the other party was based on an IBM or Microsoft implementationis this
likely to work?
It goes without saying that any work done would need to be very throughlytested
and qualified.
I have looked through the WebLogic Documentation on WebServices aswell as searching
this newgroup for other posts on this topic, hopefully I have not missedanything
(If so, my apologies.)
Thanks,
Mike Shea.

What is "reliable message" wait event in 10g??

Hi, all.
The database is 2 node RAC 10.2.0.2.0 on 32-bit windows 2003 EE SP1.
From time to time, I see "reliable message" wait event on the
"Top 5 Timed Events" section from AWR report.
The wait class is "Other".
There seems to be no manuals and html links explaining "reliable message"
wait event.
Thanks and Regards.
Message was edited by:
user507290
Message was edited by:
user507290

Metalink Doc 461052.1 is a fairly lightweight walk-through of a system resource profiling tool called LTOM, the "Lite Onboard Monitor". It has an appendix in which it simply points out "The following events were considered idle and ignored... reliable message..."
It also says that if you want to include something for wait analysis, just take it out of the list of idle and ignored events... so it's not exactly saying that the thing is an idle event, just that it was treated as such for the purposes of writing that document but that you might think differently.
On the other hand, this page:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm
...is 10g Release 2's description of "wait events of greatest interest"... and "reliable message" isn't on it! From which one concludes, I suppose, that it isn't of great interest!

Reliable message - Top first timed events

Hi All,
One fo my Db having reliable message as top first timed events. Does anyone have an idea about this cause and the solution for this . Please do the needful.
Event Waits Time(s) Avg wait (ms) % DB time Wait Class
reliable message 685,139 24,625 36 29.58 Other
Thanks

http://arulselvaraj.blogspot.com/2011/01/drop-tablespace-waiting-on-reliable.html

What is "reliable message" wait event?

Hi, all.
What is "reliable message" wait event?
The wait class is "Other", not "Idle".
From time to time, I can see "reliable message" wait event
in the Top 5 Timed Events section from AWR reports.
In addition, what is "CPU time" in the Top 5 Timed Events section?
Thanks and Regards.
Message was edited by:
user507290

Dear Yas.
Thanks for your reply.
The database is 2 node RAC database (10.2.0.2.0) on 32 bit windows 2003 EE SP1.
Does "AQ" mean Streams AQ???
Can I disable Streams AQ facility??
Thanks and Regards.
Message was edited by:
user507290
Message was edited by:
user507290

Web service reliable messaging on NW70 java

Hi all,
I need to ensure reliable messaging both in consuming and providing web services in a NW70-based java application.
I know that WSRM is enabled on NW71.
Can that be done on NW70 java too?
Thanks, regards
Vincenzo

not doable

[svn] 4226: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4226 Author: [email protected] Date: 2008-12-03 15:25:17 -0800 (Wed, 03 Dec 2008) Log Message: ----------- Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. QA: Yes Doc: No Checkintests Pass: Yes Details: * Make sure the <reliable/> option is treated as a nested element rather than an attribute of its parent <network> element. Ticket Links: ------------ http://bugs.adobe.com/jira/browse/LCDS-517 Modified Paths: -------------- blazeds/trunk/modules/core/src/flex/messaging/Destination.java

Revision: 4226 Author: [email protected] Date: 2008-12-03 15:25:17 -0800 (Wed, 03 Dec 2008) Log Message: ----------- Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. QA: Yes Doc: No Checkintests Pass: Yes Details: * Make sure the <reliable/> option is treated as a nested element rather than an attribute of its parent <network> element. Ticket Links: ------------ http://bugs.adobe.com/jira/browse/LCDS-517 Modified Paths: -------------- blazeds/trunk/modules/core/src/flex/messaging/Destination.java

[svn] 4195: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4195
Author: [email protected]
Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ServerConfig.as

Revision: 4195
Author: [email protected]
Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ServerConfig.as

[svn:fx-trunk] 14719: Bug: LCDS-1522 - RTE running reliable messaging test over NIO HTTP endpoint caused by checkin 272187 .

Revision: 14719
Revision: 14719
Author:   [email protected]
Date:     2010-03-12 02:20:41 -0800 (Fri, 12 Mar 2010)
Log Message:
Bug: LCDS-1522 - RTE running reliable messaging test over NIO HTTP endpoint caused by checkin 272187.
QA: Yes
Doc: No
Checkintests: Pass
Details: Checkin 272187 fixed small messages to work on NIO HTTP endpoints but this exposed a bug in HTTPChannel. HTTPChannel is not supposed to support small messaging feature but there was one place where small messages feature were still being enabled which caused the bug.
Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-1522
Modified Paths:
    flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/channels/HTTPChannel.as

[svn] 4193: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4193
Author: [email protected]
Date: 2008-11-26 11:40:05 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* Foundational update to include destination config in what we collect for runtime config exchange with new clients for destinations with network/reliable=true (LCDS only).
* Also typo in comment in AbstractConnectionAwareSession fixed.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/AbstractConnectionAwareSession.java
blazeds/trunk/modules/core/src/flex/messaging/Destination.java
blazeds/trunk/modules/core/src/flex/messaging/services/AbstractService.java

Revision: 4193
Author: [email protected]
Date: 2008-11-26 11:40:05 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* Foundational update to include destination config in what we collect for runtime config exchange with new clients for destinations with network/reliable=true (LCDS only).
* Also typo in comment in AbstractConnectionAwareSession fixed.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/AbstractConnectionAwareSession.java
blazeds/trunk/modules/core/src/flex/messaging/Destination.java
blazeds/trunk/modules/core/src/flex/messaging/services/AbstractService.java

Reliable messaging between XI and BizTalk using SOAP

I came across this document describing how reliable messaging between XI and BTS can be implemented using the SOAP extensions. This document has been authored by
- André Fischer, Project Manager CTSC, SAP AG
- Matthias Allgaier, Consultant XI, SAP Deutschland AG & Co.
- KG Jürgen Daiberl, SAP Program Manager CTSC, Microsoft Corporation
Does anyone know if the prototype code is available for download from SDN or elsewhere? A search on SDN did not produce any results...
Thanks.
- KishenM

Larry,
Let me see if I understood this - You need to use the SOAP adapter to integrate with BizLink. Bizlink Provides its own SOAP Header and hence you are not sure how to do this.
Got a few questions,
1. Has Bizlink given you a XSD / WSDL. Does this have the entire SOAP Payload including the SOAP Header and SOAP body? If yes, create the mapping as needed and instead of the SOAP adapter use the HTTP adapter or use the SOAP adapter and in the SOAP adapter select option Do Not Use SOAP Envelope.
2. If you do not have a XSD that contains the entire SOAP Enevelope - SOAP header and body then use XSL or Java Mapping that creates this output structure and use the SOAP adapter with the DoNotuseSOAP Envelope option or the HTTP adapter.
The SOAP adapter in the DONotUseSOAP Emvelope mode basically becomes a http adapter.
Regards
Bhavesh

WS Reliable Messaging

Similar Messages

Maybe you are looking for