Web Service Reliable Messaging: Namespace confusion / bug

Hello,
according to the 9.2 doc and IMHO the spec the correct namespace for RM1.0 assertions is:
xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm/policy
however, the packaged example uses
xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm
even worse, this is the only way to get it to work!
does that mean I have to use a wrong namespace to get a working WS-RM example for the latest WLS9.2MP3?
thanks for your input.
Barossa

ok, it does work with the rm namespace. I have no idea why, as this should be a completely different schema.
also it works with the correct namespace rm/policy (which is more restrictive, first I had an ExponentialBackoff element
in the wrong order, for the rm namespace it was ok, but not for the rm/policy.)
so the example is plain wrong. the namespace and even the sequence of the elements. still it is working. how does that come?
Edited by: Barossa on Jan 22, 2009 6:35 PM

Similar Messages

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

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

SOAP Reliable Messaging (8.1) vs. Web Service Reliable Messaging (9.0)

I am looking for the differences in implementation and user experience for two Reliable Messaging solutions ( besides that WL 9.0 implemented WS-RM Spec. ). In particular, when a Reliable Messaging transaction is committed and successfully complete, which consumer element/component on the receiver side gets the message and how ( I mean a run-time component which is not implemented by WL on the receiver side) ? Does the message stay in receiver side persistent storage until it is taken by the consumer element/component or it sits in memory only ?
Docs in 8.1 version detailed how the SOAP RM worked while in 9.0 version such description is absent.
Please, send your response to [email protected]
Thank you in advance,
- Michael

Hi,
i think its not possible to get the response of the return type as void. you just think in normal core java also, its not possible that. i think you must change in the web service. and one more thing are you developing the web service in java or .NET? if it in java its easy to change the return type. i am also new to java web service. i am giving what i know.
Thanks

Web Services reliable messaging is not supported in SAP AS 7.0?

In 7.1 documentation, I find that one enables a webservice for reliable messaging by writing @RelMessagingNW05DTOperation annotation.
However I'm shocked to find that in 7.0 documentation, it only talks about some PL/SQL like code (LUW) that one has to implement to have reliable messaging (http://help.sap.com/saphelp_nw70ehp2/helpdata/en/46/9743916d1115ece10000000a114a6b/frameset.htm). As I'm not familiar with LUW, can you confirm that the developer himself has to handle creating sequences, reordering them and guaranteeing exactly once delivery? And the LUW code shown in the link, does it do all this?
Please advice.

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

Web Services Reliable Messaging

Does Oracle BPEL PM has WSRM implemented
1.As Server to expose WSRM based service ?
2.To consume other WSRM services ?
If so, what other app servers the interoperability is tested ?
regards,
Arun

BPEL PM does not support WS-RM .. But you can use Oracle's Webservice Manager, that should contain this feature as part of its SLA management ..
hth clemens

Enable WSRM (Web Service Reliable Messaging) in sap system

Hi All,
Can any one provide document to enable wsrm in sap pi system.
your help is much appreciated
Thanks,
Narendar.

Hi,
Please check below link it will help you.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/107256c4-d4c4-2d10-fca1-d1676081892b?QuickLink=index&…
Best Regards,
Atul

Can anybody tell how to access web service from Message Driven bean

Can anybody tell how to access web service from Message Driven bean

Can anybody tell how to access web service from Message Driven bean

Problem in Jdeveloper 10.1.3, web services and document style.possible bug?

Hello!
I would like to generate a document-style web service from a wsdl file. The problem is that when I use it I get the following error:
"operation echoStruct must have exactly one parameter as part of the SOAP body when used with a document-bare binding. All other parameters must be mapped to headers."
A similar message is shown with other wsdl file that I'm using.
I'm attaching the file that use to test it.
Could you help me and tell me how I can fix it, please? or is it a bug?
Regards,
Antonio.
<definitions xmlns:s1="http://soapinterop.org" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://soapinterop.org/xsd" xmlns:s2="http://soapinterop.org/AbstractTypes" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://soapinterop.org">
     <types>
          <s:schema elementFormDefault="qualified" targetNamespace="http://soapinterop.org/xsd">
               <s:import namespace="http://soapinterop.org"/>
               <s:element name="echoStructParam" type="s0:SOAPStruct"/>
               <s:complexType name="SOAPStruct">
                    <s:sequence>
                         <s:element minOccurs="1" maxOccurs="1" name="varFloat" type="s:float"/>
                         <s:element minOccurs="1" maxOccurs="1" name="varInt" type="s:int"/>
                         <s:element minOccurs="0" maxOccurs="1" name="varString" type="s:string"/>
                    </s:sequence>
               </s:complexType>
               <s:element name="echoStructReturn" type="s0:SOAPStruct"/>
               <s:element name="echoStringArrayParam" type="s1:ArrayOfString"/>
               <s:element name="string" type="s:string"/>
               <s:element name="echoStringArrayReturn" type="s1:ArrayOfString"/>
               <s:element name="echoStringParam" type="s:string"/>
               <s:element name="echoStringReturn" type="s:string"/>
          </s:schema>
          <s:schema elementFormDefault="qualified" targetNamespace="http://soapinterop.org">
               <s:import namespace="http://soapinterop.org/xsd"/>
               <s:complexType name="ArrayOfString">
                    <s:sequence>
                         <s:element minOccurs="0" maxOccurs="unbounded" ref="s0:string"/>
                    </s:sequence>
               </s:complexType>
               <s:element name="ArrayOfString1" nillable="true" type="s1:ArrayOfString1"/>
               <s:complexType name="ArrayOfString1">
                    <s:sequence>
                         <s:element minOccurs="0" maxOccurs="unbounded" name="string" nillable="true" type="s:string"/>
                    </s:sequence>
               </s:complexType>
               <s:element name="string" nillable="true" type="s:string"/>
          </s:schema>
          <s:schema targetNamespace="http://soapinterop.org/AbstractTypes">
               <s:complexType name="StringArray">
                    <s:complexContent mixed="false">
                         <s:restriction base="soapenc:Array">
                              <s:sequence>
                                   <s:element minOccurs="0" maxOccurs="unbounded" name="String" type="s:string"/>
                              </s:sequence>
                         </s:restriction>
                    </s:complexContent>
               </s:complexType>
          </s:schema>
     </types>
     <message name="echoStructSoapIn">
          <part name="echoStructParam" element="s0:echoStructParam"/>
     </message>
     <message name="echoStructSoapOut">
          <part name="echoStructResult" element="s0:echoStructReturn"/>
     </message>
     <message name="echoStringArraySoapIn">
          <part name="echoStringArrayParam" element="s0:echoStringArrayParam"/>
     </message>
     <message name="echoStringArraySoapOut">
          <part name="echoStringArrayResult" element="s0:echoStringArrayReturn"/>
     </message>
     <message name="echoStringSoapIn">
          <part name="echoStringParam" element="s0:echoStringParam"/>
     </message>
     <message name="echoStringSoapOut">
          <part name="echoStringResult" element="s0:echoStringReturn"/>
     </message>
     <portType name="WSDLInteropTestDocLitSoap">
          <operation name="echoStruct">
               <input message="s1:echoStructSoapIn"/>
               <output message="s1:echoStructSoapOut"/>
          </operation>
          <operation name="echoStringArray">
               <input message="s1:echoStringArraySoapIn"/>
               <output message="s1:echoStringArraySoapOut"/>
          </operation>
          <operation name="echoString">
               <input message="s1:echoStringSoapIn"/>
               <output message="s1:echoStringSoapOut"/>
          </operation>
     </portType>
     <binding name="WSDLInteropTestDocLitSoap" type="s1:WSDLInteropTestDocLitSoap">
          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="echoStruct">
               <soap:operation soapAction="http://soapinterop.org/" style="document"/>
               <input>
                    <soap:body use="literal"/>
               </input>
               <output>
                    <soap:body use="literal"/>
               </output>
          </operation>
          <operation name="echoStringArray">
               <soap:operation soapAction="http://soapinterop.org/" style="document"/>
               <input>
                    <soap:body use="literal"/>
               </input>
               <output>
                    <soap:body use="literal"/>
               </output>
          </operation>
          <operation name="echoString">
               <soap:operation soapAction="http://soapinterop.org/" style="document"/>
               <input>
                    <soap:body use="literal"/>
               </input>
               <output>
                    <soap:body use="literal"/>
               </output>
          </operation>
     </binding>
     <service name="WSDLInteropTestDocLit">
          <port name="WSDLInteropTestDocLitSoap" binding="s1:WSDLInteropTestDocLitSoap">
               <soap:address location="http://mssoapinterop.org/asmx/wsdl/InteropTestDocLit.asmx"/>
          </port>
     </service>
</definitions>

Dev update: WSDL file seems fine. The problem is that it's for a document-bare service and, by default, the Unwrap Wrapped Parameters option on step 2 of the top-down wizard is enabled and checked. This means that we try to pick apart the input message into a series of parameters, yielding the error shown because a document-bare operation must have only one input parameter.
If the Unwrap Wrapped Parameters option is unchecked, creation of the top-down service will succeed. In future, we ought to disable the option completely for everything but document-wrapped services, as that's the only time it applies.
This is covered by bug 4630382.

Web service scenario -- message stuck in receiver PI engine

Hello expert
I have scenario HTTP --> PI --> WS (ABAP backend).
I have PI 7.1 and the backend is based on NW 7.0
I have configured the scenario in ID with receiver agreement of ws adapter. In the backend, I've generated the server proxy based on the service interface and configured endpoint in soamanager.
After everything is done, I tested the scenario. In MONI in PI, everthing looks good, message send to ws of hte backend. In MONI in the backend, I see the message with green flag indicating Released for processing (WS). Looks like message arrived at the local PI engine of the backend, but it doesn't know how to process it (by calling the web service). Does anybody know what could be the problem?
Thanks
Eric

Eric
Looks like your SRT is not set up yet. Try running program SRT_ADMIN_CHECK (I am not sure about the exact program name but it is somelike this) and see if you get some errors. The WS adapter uses bgRFC and hence you are not going to find anything in SMQ2.
Run program SRT_ADMIN in client 000 (using DDIC user) and in all clients where you will be using WS adapter. Please note this is a part of post installation configuration and I am assuming your system hasn't been set up for the SRT yet.
You also will have to set up a user ID for bgRFC and RFC destination (in Tcode SBRFCCONF). Please refer to the documentation from service market place for post installation tasks or take from your basis admin guys for setting up the SRT.
Thanks
KK

Web service error message ' Invalid Response Code: (403) Forbidden'

Hi Experts,
I created a webservice, and it working fine in Development and Quality systems. But it is not working in Production system. When trying to click on 'Open Web Service navigator for selected binding' for testing it's giving the following error message.
Cannot download WSDL from http://na00stgerp01.systems.corbis.net:8003/sap/bc/srt/wsdl/bndg_DFCA9B84C8D5A7F1A013001C23C37FBD/wsdl11/allinone/standard/document?sap-client=120: Invalid Response Code: (403) Forbidden. The requested URL was:"http://na00stgerp01.systems.corbis.net:8003/sap/bc/srt/wsdl/bndg_DFCA9B84C8D5A7F1A013001C23C37FBD/wsdl11/allinone/standard/document?sap-client=120"
Please suggest me any solution.
Thanks
Lakshminarayana

Hi Lakshminarayana,
there may be lots of reasons.
[http://lmgtfy.com/?q=http%20%2B%20403]
Regards, Hubert

Web Service Reliability on ESB

Hi,
I am very new to ESB.
Requirement : is to call a reliable soap service from an ESB.
I need to enforce reliabilty on ESB to call a reliable web service.
Pls. let me know how can I acheive this.

Hi,
the new 2.1 version includes a test interface for business and proxy services.
-Kai

Best way to call web service from Message Driven Bean

I'm q'ing msgs up and would like to use a message driven bean to forward them to
an external web service. Weblogic workshop does not seem to support web service
controls in an EJB project. Any suggestions?
Thanks,
Paul

Paul,
A non-trivial alternative, since you have the WSDL, would be to forget about trying
to use generated client code and just use JAX-RPC dynamic invocation instead.
That's how I call external web services from within an EJB in situations in which
generated client code cannot be incorporated prior to deployment. Minimally all
that is required is the WSDL and the service name, port name, and operation name,
although if non-builtin parameter types are used then you will have to manipulate
the service's type mapping registry.
Mark
"Paul" <[email protected]> wrote:
>
I've taken our wsdl and generated a web service in Workshop 8.1 using
XMLBeans.
This produces a web page that contains a link"Java Proxy" for downloading
generated
client code. I assume this is the same as clientgen. It's interesting
that
it does not
use XMLBeans like the web service that generated it. It uses a different
serialization
method.
I've used this generated code to call the web service. Although the
client seems
to run
successfully to completion, I get the following error in the weblogic
server console:
<Sep 29, 2003 7:46:24 AM EDT> <Error> <WLW> <000000> <Failure=com.bea.wlw.runtim
e.core.request.ResponseValidationException: java.lang.RuntimeException:
Protocol
'http-soap' not available on this operation. [ServiceException]>
<Sep 29, 2003 7:46:24 AM EDT> <Warning> <WLW> <000000> <Returning HTTP
500 due
t
o SOAP fault occurring on DispFile=pjm.srcm.webservices.face.Receptor>
Frustrating...
Bruce Stephens <[email protected]> wrote:
Hi Paul,
Could you not first use clientgen on the external webservice, then take
the stubs it created, then add these to your code along with the
onMessage(Message msg) and roll it into the MBean?
We don't have exactly that example, but you might take a look at this
one to get some ideas:
http://webservice.bea.com/message.zip
Hope this helps,
Bruce
Paul wrote:
Bruce,
Don't think this will work for us. We are receiving data internallythrough
a JMS queue. We need to pull it off the queue (MDB), massage it alittle and
send it to an external web service. The link you sent me was howto implement
a web service with JMS.
I started out by trying to use the Web Service and JMS controls butit doesn't
seem like I can use a JMS control because that requires a conversationID,
which we don't have because nothing is comming in through a web services.
Paul
Bruce Stephens <[email protected]> wrote:
Hi Paul,
There is a chapter in the docs on this. See if this helps,
http://edocs.bea.com/wls/docs81/webserv/jms.html#1067060
Thanks,
Bruce
Paul wrote:
I'm q'ing msgs up and would like to use a message driven bean to
forward
them to
an external web service. Weblogic workshop does not seem to supportweb service
controls in an EJB project. Any suggestions?
Thanks,
Paul

Help: Flex can't parse web service fault message correctly

When I use class WebService to issue requests but the
server-side returns error, it is assumed the instance of FaultEvent
class in fault-event-handler contains error information. However
when inspecting member variables of the object I can only found
some very general error information which can't be mapped to the
original error on server side.
E.g.
The server side returns a SOAP document to Flex like:
<env:Envelope xmlns:env="
http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
<env:Body>
<env:Fault>
<faultcode>env:Client</faultcode>
<faultstring>com.sap.sbs.silo.bean.interfaces.ServiceException:
[SESSION] : No session can serve the request, pls check if the
session is expired!</faultstring>
<detail>
<ns1:ServiceException xmlns:ns1="
http://service.bean.silo.sbs.sap.com"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<reason>-1</reason>
<message>[SESSION] : No session can serve the request,
pls check if the session is expired!</message>
</ns1:ServiceException>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
But instance of FaultEvent class in Flex fault-event-handler
only contains general error informatin like: (the following values
are gotten during debug)
event = mx.rpc.events.FaultEvent
- fault = mx.rpc.Fault (@541e5e1)
- description = "HTTP request error" : String
- detail = "Error: [IOErrorEvent type="ioError"
bubbles=false cancelable=false eventPhase=2 text="Error #2032:
Stream Error。 URL:
http://PVGD50033332A:8080/silo/SessionService"
URL:
http://PVGD50033332A:8080/silo/SessionService"
: String
- errorID = 0 [0x0] : Number
- faultCode = "Server.Error.Request" : String
- faultcode = "Server.Error.Request" : String
- faultDetail = "Error: [IOErrorEvent type="ioError"
bubbles=false cancelable=false eventPhase=2 text="Error #2032:
Stream Error。 URL:
http://PVGD50033332A:8080/silo/SessionService"
URL:
http://PVGD50033332A:8080/silo/SessionService"
: String
- faultString = "HTTP request error" : String
- faultstring = "HTTP request error" : String
- message = "faultCode:Server.Error.Request
faultString:'HTTP request error' faultDetail:'Error: [IOErrorEvent
type="ioError" bubbles=false cancelable=false eventPhase=2
text="Error #2032: Stream Error。 URL:
http://PVGD50033332A:8080/silo/SessionService"
URL:
http://PVGD50033332A:8080/silo/SessionService'"
: String
- name = "Error" : String
- rootCause = flash.events.IOErrorEvent (@5572371)
- bubbles = false : Boolean
- cancelable = false : Boolean
- currentTarget = flash.net.URLLoader (@541e431)
- eventPhase = 2 [0x2] : Number
- target = flash.net.URLLoader (@541e431)
- text = "Error #2032: Stream Error。 URL:
http://PVGD50033332A:8080/silo/SessionService"
: String
- type = "ioError" : String
Could anybody tell me where I can find the original error
information like 'No session can serve the request, pls check if
the session is expired!' in Flex web service framework?

I am also encountering the exact same issue using Apache Axis
1.4 (
http://ws.apache.org/axis/)
as my web services stack. The fault information is seemingly
nowhere to be found. Can someone from the Flex support team please
sound off on this issue. Is fault data supposed to somehow be made
available? I would imagine it would be if meaningful error messages
are to be returned from Web Services in Flex.

Web Service Reliable Messaging: Namespace confusion / bug

Similar Messages

Maybe you are looking for