Reliable messaging for webservices

Hi all
i want to send a message from on webservice(source) to another webservice(destination) reliably. in case if the destination webservice is down in that case the source webservice should store the message in the persistent store and should try again to send the message to the destination after a certain interval(should be cofigurable) of time.
i tried this using the WS Reliable messaging but failed
plz help me to solve the problem
Thanks in advance

1. No - WS Reliable Messaging came out after Java CAPS 5.1 came out support for it has not been retrofitted
2. No. SOAP over JMS is not a standard. Java CAPS supports JMS and XML Schemas, including these describing SOAP messages. There is nothing to stop you from sending SOAP messages over JMS. Remember, however, that JMS implementations form different vendors are not interoperable at the wire level.
Java CAPS 6,. due out soon, provides support for WS 1.1 standards including reliable messaging.
Perhaps you should reconsider your choice of web services for messaging in unreliable environment. HTTP has never been intended to do what people are trying to make it do, most notably stateful and reliable messaging

Similar Messages

Setup 'addressable client' for reliable messaging

Hello,
I have a use case where I have to make a reliable call to JAX-RPC Webservice from BPEL. Reliable messaging policy is attached to JAX-RPC webservice that BPEL is invoking. For BPEL to successfully invoke JAX-RPC webservice with reliable messaging setup, I am told that I need to setup an 'addressable client'.
Is there any documentation on how to set up an 'addressable client' for reliable messaging? Any help is much appreciated.
Thank you

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

HT201412 My ipjone keeps coming up with a message say that the cable or accessory urged in is not a reliable source for this iPhone but I do not have Nything plugged in to my iPhone. I Put it in a bowl of rice for 2 hours to see if that would help it but

My ipjone keeps coming up with a message say that the cable or accessory urged in is not a reliable source for this iPhone but I do not have Nything plugged in to my iPhone. I Put it in a bowl of rice for 2 hours to see if that would help it but it hasn't. Is there anything thank can do???

Clean the connector on the bottom of the phone. Use a magnifying glass, bright light, and a wood or plastic toothpick. If you got the phone wet put it in a bag of uncooked rice for several days, not hours.

For Working offline - Which one to use - local database caching or reliable messaging?

Hi,
I am working on a mobile application with lcds where there is a feature to be implemented. The user can use the application in airplane mode and be able to automatically send requests to server when he comes online. After some research, I found that I have to use a feature in the documentation called ocasionally conencted clients, which uses local database with dataservice.savecache() and offline adapter. I also found another feature called reliable messaging which takes care of sending the pending requests when the user comes online, but not sure if this feature supports offline mode for longer periods. The documentation mentioned that reliable messaging is only good for transient network disconnects, meaning disconenction for shorter time.
Can anybody please confirm which is the right feature that best suits this requirement?
Thanks,
Swathi.

Hi Ashish,
Thank you so much for the resource. One more question, The code in the resource link, has calls to Dataservice.disconnect() and Dataservice.connect() on the buttons. If my user need not bother to click on those buttons for connections and just set his phone to airplane mode and start working, I am using SocketMonitor class to monitor for network connection and then perform the Dataservice.connect(). In that case, I have problems when network is connected, the data service seems connected automatically some times and not connected other times resulting in errors. I am using autoConenct = true. How can I handle this? Do I have to call disconnect when socket is not available and then call conenct when it is available, things like that? Or Is there any other way to implement this without using SocketMonitor class?
Thanks,
Swathi.

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 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

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.

Regarding Kerberos authentication for webservices.

Hi,
I need to use kerberos authentication for my receiver webservice. I am working in PI7.1 . Which adapter I can use for this ( WS-RM adapter or SOAP adapter) and How to configure it for kerberos. I mean, which value of authentication parameter refers to kerberos authentication.
Regards,
Reyaz hussain

Hi Reyaz,
To tell you frankly i never come across this kerberos protocol but since you would like to use there is certainly a chance after the launch of PI 7.1. The launch has Opened the Door to the World of Web Services Reliable Messaging. "The Integration Directory enables you to easily configure scenarios where the Integration Server acts as a message hub between WS-RM-enabled applications and any other application or technical system. Thus, you can configure scenarios where either a Web Service client calls the Integration Server and the message is then routed to any other application, or the other way around where any application calls a Web Service provider via the Integration Server. In the Integration Directory you can do the complete configuration of the Integration Server inbound or outbound processing."
https://www.sdn.sap.com/irj/scn/wiki?path=/display/profile/2007/07/25/new+news&focusedcommentid=44360
Regards
joel

Standalone Web Service clients in NetBeans with Reliable Messaging

Following the WSIT tutorial (http://java.sun.com/webservices/reference/tutorials/wsit/doc/index.html) it's possible to create a Web Service with Reliable Messaging and a servlet client which run perfectly, great, but try and create a standalone client in NetBeans and it immediatly fails.
Basically I created a standard Java application, did New->Web Service Client exactly like I had done in the servlet example and then used the Web Service Client Resources -> Call Web Service Operation context menu to add a Web Service call to my java application.
The relevant code:
try { // Call Web Service Operation
            uk.ac.ox.sddag.glassfish.server.NonSecureWSService service = new uk.ac.ox.sddag.glassfish.server.NonSecureWSService();
            uk.ac.ox.sddag.glassfish.server.NonSecureWS port = service.getNonSecureWSPort();
            int x = 0;
            int y = 10;
            int result = port.add(x, y);
            System.out.println("Result = "+result);
            ((Closeable)port).close();
        } catch (Exception ex) {
            System.out.println("Exception:");
            ex.printStackTrace();
        }Result:
Exception:
javax.xml.ws.soap.SOAPFaultException: com.sun.xml.ws.rm.RMException: WSRM3018: Non RM Request or Missing wsa:Action header
        at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
        at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
        at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
        at $Proxy29.add(Unknown Source)
        at nonsecurestandaloneclient.Main.main(Main.java:29)
Caused by: javax.xml.ws.WebServiceException: com.sun.xml.ws.rm.RMException: WSRM3018: Non RM Request or Missing wsa:Action header
        at com.sun.xml.ws.rm.jaxws.runtime.server.RMServerTube.processRequest(RMServerTube.java:343)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
        at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
        at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
        at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:218)
        at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
        at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
        at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
        at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
        at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
        at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
        at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
        at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:176)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
        at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
        at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
        at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
        at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
        at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
        at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
        at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
Caused by: com.sun.xml.ws.rm.RMException: WSRM3018: Non RM Request or Missing wsa:Action header
        at com.sun.xml.ws.rm.jaxws.runtime.server.RMServerTube.handleProtocolMessage(RMServerTube.java:469)
        at com.sun.xml.ws.rm.jaxws.runtime.server.RMServerTube.processRequest(RMServerTube.java:145)
        ... 45 more
BUILD SUCCESSFUL (total time: 1 second)By removing the Reliable Messaging from the Web Service this error goes away. Initially I thought this error might be being caused by not specifying the WebMethod annotations 'action' parameter, but it's definitely set.
package uk.ac.ox.sddag.glassfish.server;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebService;
@WebService()
public class NonSecureWS {
    @WebMethod(action = "add")
    public int add(@WebParam(name = "x") int x, @WebParam(name = "y") int y) {
        return x+y;
}Interestingly, I found that this error also goes away if I add the library webservices-rt.jar from my glassfish libs to the project. Perhaps this is an oversight of NetBeans and should have been added automatically if reliable messaging is enabled, although by default it does have JAX-WS 2.1 jaxws-tools which I'm guessing is for some reason not adequate. JAX-WS version mismatch?

This bug still isn't fixed.
Thank you, adding Glassfish's webservices-rt.jar does fix it.

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

The problem about Secure Reliable Messaging between WCF and Weblogic

I'm doing a project for testing the interoperability between WCF and Weblogic with secure reliable messaging.
When WCF client talk to Weblogic service with Secure Reliable feature enabled.We got error when CreateSequence, the error message is below:
The incoming message was signed with a token which was different from what used to encrypt the body. This was not expected.
The remote endpoint requested an address for acknowledgements that is not the same as the address for application messages. The channel could not be opened because this is not supported. Ensure the endpoint address used to create the channel is identical to the one the remote endpoint was set up with.
My understanding is that the client accepted the RSTR from weblogic (so both sides now share the secure conversation token) and moved on to CreateSequence (and failed due to config mismatches). But I don't how the error happen and how to get it fixed.
-- below is the wsdl you are using --
Any ideas about it?
Thanks in advance!!!!!!
<?xml version='1.0' encoding='utf-8'?>
<WL5G3N4:definitions name="EchoStringSignOnly" targetNamespace="http://tempuri.org/" xmlns="" xmlns:WL5G3N0="http://www.w3.org/ns/ws-policy" xmlns:WL5G3N1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:WL5G3N2="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" xmlns:WL5G3N3="http://docs.oasis-open.org/ws-rx/wsrmp/200702" xmlns:WL5G3N4="http://schemas.xmlsoap.org/wsdl/" xmlns:WL5G3N5="http://tempuri.org/" xmlns:WL5G3N6="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:WL5G3N7="http://schemas.xmlsoap.org/wsdl/soap12/">
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly1_EchoString_Input_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="AckRequested" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly1_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<WL5G3N2:RMAssertion>
<WL5G3N2:InactivityTimeout Milliseconds="600000"/>
<WL5G3N2:AcknowledgementInterval Milliseconds="200"/>
</WL5G3N2:RMAssertion>
<sp:SymmetricBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:ProtectionToken>
<wsp15:Policy>
<sp:SecureConversationToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>
<sp:RequireDerivedKeys/>
<sp:BootstrapPolicy>
<wsp15:Policy>
<sp:SignedParts>
<sp:Body/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
<sp:EncryptedParts>
<sp:Body/>
</sp:EncryptedParts>
<sp:AsymmetricBinding>
<wsp15:Policy>
<sp:InitiatorToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/Never">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:AsymmetricBinding>
<sp:Wss11>
<wsp15:Policy>
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13>
<wsp15:Policy>
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
</wsp15:Policy>
</sp:BootstrapPolicy>
</wsp15:Policy>
</sp:SecureConversationToken>
</wsp15:Policy>
</sp:ProtectionToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:SymmetricBinding>
<sp:Wss11 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
<wsam:Addressing xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
<wsp:Policy xmlns:wsp="http://www.w3.org/ns/ws-policy">
<wsam:NonAnonymousResponses/>
</wsp:Policy>
</wsam:Addressing>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly_EchoString_output_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="AckRequested" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="UsesSequenceSTR" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="ChannelInstance" Namespace="http://schemas.microsoft.com/ws/2005/02/duplex"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly1_EchoString_output_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="AckRequested" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly_EchoString_Input_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="AckRequested" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="UsesSequenceSTR" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="ChannelInstance" Namespace="http://schemas.microsoft.com/ws/2005/02/duplex"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<WL5G3N3:RMAssertion/>
<sp:SymmetricBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:ProtectionToken>
<wsp15:Policy>
<sp:SecureConversationToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>
<sp:RequireDerivedKeys/>
<sp:BootstrapPolicy>
<wsp15:Policy>
<sp:SignedParts>
<sp:Body/>
<sp:Header Name="ChannelInstance" Namespace="http://schemas.microsoft.com/ws/2005/02/duplex"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
<sp:EncryptedParts>
<sp:Body/>
</sp:EncryptedParts>
<sp:AsymmetricBinding>
<wsp15:Policy>
<sp:InitiatorToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/Never">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:AsymmetricBinding>
<sp:Wss11>
<wsp15:Policy>
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13>
<wsp15:Policy>
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
</wsp15:Policy>
</sp:BootstrapPolicy>
</wsp15:Policy>
</sp:SecureConversationToken>
</wsp15:Policy>
</sp:ProtectionToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:SymmetricBinding>
<sp:Wss11 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
<cdp:CompositeDuplex xmlns:cdp="http://schemas.microsoft.com/net/2006/06/duplex"/>
<ow:OneWay xmlns:ow="http://schemas.microsoft.com/ws/2005/05/routing/policy"/>
<wsam:Addressing xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
<wsp:Policy xmlns:wsp="http://www.w3.org/ns/ws-policy">
<wsam:NonAnonymousResponses/>
</wsp:Policy>
</wsam:Addressing>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N4:types>
<xsd:schema targetNamespace="http://tempuri.org/Imports" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://tempuri.org/" schemaLocation="RequestReplySignOnly.svc.xsd0.xml"/>
<xsd:import namespace="http://schemas.microsoft.com/2003/10/Serialization/" schemaLocation="RequestReplySignOnly.svc.xsd1.xml"/>
</xsd:schema>
</WL5G3N4:types>
<WL5G3N4:message name="PingRequest">
<WL5G3N4:part element="WL5G3N5:PingRequest" name="parameters"/>
</WL5G3N4:message>
<WL5G3N4:message name="PingResponse">
<WL5G3N4:part element="WL5G3N5:PingResponse" name="parameters"/>
</WL5G3N4:message>
<WL5G3N4:portType name="IEchoStringSignOnly">
<WL5G3N4:operation name="EchoString">
<WL5G3N4:input message="WL5G3N5:PingRequest" name="PingRequest"/>
<WL5G3N4:output message="WL5G3N5:PingResponse" name="PingResponse"/>
</WL5G3N4:operation>
</WL5G3N4:portType>
<WL5G3N4:binding name="CustomBinding_IEchoStringSignOnly" type="WL5G3N5:IEchoStringSignOnly">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly_policy"/>
</WL5G3N0:Policy>
<WL5G3N6:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<WL5G3N4:operation name="EchoString">
<WL5G3N6:operation soapAction="urn:wsrm:EchoString" style="document"/>
<WL5G3N4:input name="PingRequest">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly_EchoString_Input_policy"/>
</WL5G3N0:Policy>
<WL5G3N6:body use="literal"/>
</WL5G3N4:input>
<WL5G3N4:output name="PingResponse">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly_EchoString_output_policy"/>
</WL5G3N0:Policy>
<WL5G3N6:body use="literal"/>
</WL5G3N4:output>
</WL5G3N4:operation>
</WL5G3N4:binding>
<WL5G3N4:binding name="CustomBinding_IEchoStringSignOnly1" type="WL5G3N5:IEchoStringSignOnly">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly1_policy"/>
</WL5G3N0:Policy>
<WL5G3N7:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<WL5G3N4:operation name="EchoString">
<WL5G3N7:operation soapAction="urn:wsrm:EchoString" style="document"/>
<WL5G3N4:input name="PingRequest">
<WL5G3N7:body use="literal"/>
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly1_EchoString_Input_policy"/>
</WL5G3N0:Policy>
</WL5G3N4:input>
<WL5G3N4:output name="PingResponse">
<WL5G3N7:body use="literal"/>
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly1_EchoString_output_policy"/>
</WL5G3N0:Policy>
</WL5G3N4:output>
</WL5G3N4:operation>
</WL5G3N4:binding>
<WL5G3N4:service name="EchoStringSignOnly">
<WL5G3N4:port binding="WL5G3N5:CustomBinding_IEchoStringSignOnly" name="CustomBinding_IEchoStringSignOnly">
<WL5G3N6:address location="http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Addressable_Soap11_WSAddressing10_RM11"/>
<wsa10:EndpointReference xmlns:wsa10="http://www.w3.org/2005/08/addressing">
<wsa10:Address>http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Addressable_Soap11_WSAddressing10_RM11</wsa10:Address>
<Identity xmlns="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity">
<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
<X509Data>
<X509Certificate>MIIDCjCCAfKgAwIBAgIQYDju2/6sm77InYfTq65x+DANBgkqhkiG9w0BAQUFADAwMQ4wDAYDVQQKDAVPQVNJUzEeMBwGA1UEAwwVT0FTSVMgSW50ZXJvcCBUZXN0IENBMB4XDTA1MDMxOTAwMDAwMFoXDTE4MDMxOTIzNTk1OVowQDEOMAwGA1UECgwFT0FTSVMxIDAeBgNVBAsMF09BU0lTIEludGVyb3AgVGVzdCBDZXJ0MQwwCgYDVQQDDANCb2IwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMCquMva4lFDrv3fXQnKK8CkSU7HvVZ0USyJtlL/yhmHH/FQXHyYY+fTcSyWYItWJYiTZ99PAbD+6EKBGbdfuJNUJCGaTWc5ZDUISqM/SGtacYe/PD/4+g3swNPzTUQAIBLRY1pkr2cm3s5Ch/f+mYVNBR41HnBeIxybw25kkoM7AgMBAAGjgZMwgZAwCQYDVR0TBAIwADAzBgNVHR8ELDAqMCiiJoYkaHR0cDovL2ludGVyb3AuYmJ0ZXN0Lm5ldC9jcmwvY2EuY3JsMA4GA1UdDwEB/wQEAwIEsDAdBgNVHQ4EFgQUXeg55vRyK3ZhAEhEf+YT0z986L0wHwYDVR0jBBgwFoAUwJ0o/MHrNaEd1qqqoBwaTcJJDw8wDQYJKoZIhvcNAQEFBQADggEBAIiVGv2lGLhRvmMAHSlY7rKLVkv+zEUtSyg08FBT8z/RepUbtUQShcIqwWsemDU8JVtsucQLc+g6GCQXgkCkMiC8qhcLAt3BXzFmLxuCEAQeeFe8IATr4wACmEQE37TEqAuWEIanPYIplbxYgwP0OBWBSjcRpKRAxjEzuwObYjbll6vKdFHYIweWhhWPrefquFp7TefTkF4D3rcctTfWJ76I5NrEVld+7PBnnJNpdDEuGsoaiJrwTW3Ixm40RXvG3fYS4hIAPeTCUk3RkYfUkqlaaLQnUrF2hZSgiBNLPe8gGkYORccRIlZCGQDEpcWl1Uf9OHw6fC+3hkqolFd5CVI=</X509Certificate>
</X509Data>
</KeyInfo>
</Identity>
</wsa10:EndpointReference>
</WL5G3N4:port>
<WL5G3N4:port binding="WL5G3N5:CustomBinding_IEchoStringSignOnly1" name="CustomBinding_IEchoStringSignOnly1">
<WL5G3N7:address location="http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Anonymous_Soap12_WSAddressing10_RM10"/>
<wsa10:EndpointReference xmlns:wsa10="http://www.w3.org/2005/08/addressing">
<wsa10:Address>http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Anonymous_Soap12_WSAddressing10_RM10</wsa10:Address>
<Identity xmlns="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity">
<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
<X509Data>
<X509Certificate>MIIDCjCCAfKgAwIBAgIQYDju2/6sm77InYfTq65x+DANBgkqhkiG9w0BAQUFADAwMQ4wDAYDVQQKDAVPQVNJUzEeMBwGA1UEAwwVT0FTSVMgSW50ZXJvcCBUZXN0IENBMB4XDTA1MDMxOTAwMDAwMFoXDTE4MDMxOTIzNTk1OVowQDEOMAwGA1UECgwFT0FTSVMxIDAeBgNVBAsMF09BU0lTIEludGVyb3AgVGVzdCBDZXJ0MQwwCgYDVQQDDANCb2IwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMCquMva4lFDrv3fXQnKK8CkSU7HvVZ0USyJtlL/yhmHH/FQXHyYY+fTcSyWYItWJYiTZ99PAbD+6EKBGbdfuJNUJCGaTWc5ZDUISqM/SGtacYe/PD/4+g3swNPzTUQAIBLRY1pkr2cm3s5Ch/f+mYVNBR41HnBeIxybw25kkoM7AgMBAAGjgZMwgZAwCQYDVR0TBAIwADAzBgNVHR8ELDAqMCiiJoYkaHR0cDovL2ludGVyb3AuYmJ0ZXN0Lm5ldC9jcmwvY2EuY3JsMA4GA1UdDwEB/wQEAwIEsDAdBgNVHQ4EFgQUXeg55vRyK3ZhAEhEf+YT0z986L0wHwYDVR0jBBgwFoAUwJ0o/MHrNaEd1qqqoBwaTcJJDw8wDQYJKoZIhvcNAQEFBQADggEBAIiVGv2lGLhRvmMAHSlY7rKLVkv+zEUtSyg08FBT8z/RepUbtUQShcIqwWsemDU8JVtsucQLc+g6GCQXgkCkMiC8qhcLAt3BXzFmLxuCEAQeeFe8IATr4wACmEQE37TEqAuWEIanPYIplbxYgwP0OBWBSjcRpKRAxjEzuwObYjbll6vKdFHYIweWhhWPrefquFp7TefTkF4D3rcctTfWJ76I5NrEVld+7PBnnJNpdDEuGsoaiJrwTW3Ixm40RXvG3fYS4hIAPeTCUk3RkYfUkqlaaLQnUrF2hZSgiBNLPe8gGkYORccRIlZCGQDEpcWl1Uf9OHw6fC+3hkqolFd5CVI=</X509Certificate>
</X509Data>
</KeyInfo>
</Identity>
</wsa10:EndpointReference>
</WL5G3N4:port>
</WL5G3N4:service>
</WL5G3N4:definitions>

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.

Oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25058. Error message parameters

Dear Guru's,
I am not able to solve the above issue for last couple of days.
I am newbie to the webservice
My Issue...
I am using Jdeveloper 11.1.2.4.0 Release 2
1. Using Jdev I built one small Web Service with two methods.
        While testing the Webservice...
               I passed User Id as Parameter and it successfully return the values (user id, user name and description) from fnd_user table
2. I created another application to consume the web service i created.
               1. I added the webservice SOAP and added the method.
               2. Created a jsf page and drag and drop the parameter and return values to the jsf page.
3. While executing the created jsf page I received the error message as below
"oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25058. Error message parameters are {0=Attribute, 1=UserName, 2=UserName}"
Even I know that this issue is repeated one in our forum, I was not able to solve this issue.
Can anybody help to solve this issue.
Thanks and Regards,
Durai S E

Dear Guru's,
I am not able to solve the above issue for last couple of days.
I am newbie to the webservice
My Issue...
I am using Jdeveloper 11.1.2.4.0 Release 2
1. Using Jdev I built one small Web Service with two methods.
        While testing the Webservice...
               I passed User Id as Parameter and it successfully return the values (user id, user name and description) from fnd_user table
2. I created another application to consume the web service i created.
               1. I added the webservice SOAP and added the method.
               2. Created a jsf page and drag and drop the parameter and return values to the jsf page.
3. While executing the created jsf page I received the error message as below
"oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25058. Error message parameters are {0=Attribute, 1=UserName, 2=UserName}"
Even I know that this issue is repeated one in our forum, I was not able to solve this issue.
Can anybody help to solve this issue.
Thanks and Regards,
Durai S E

Multipart message in Webservice.

Hello,
I am calling a webservice which is having multipart message as follows:
- <wsdl:message name="PricingAndAvailabilityRequest">
<wsdl:part name="PricingAndAvailabilityRequestBody" element="pa:PricingAndAvailability" />
<wsdl:part name="header" element="ebxml:MessageHeader" />
</wsdl:message>
- <wsdl:message name="PricingAndAvailabilityResponse">
<wsdl:part name="PricingAndAvailabilityResponseBody" element="par:PricingAndAvailabilityResponse" />
<wsdl:part name="header" element="ebxml:MessageHeader" />
</wsdl:message>
- <wsdl:portType name="PricingAndAvailabilityServicePort">
- <wsdl:operation name="PricingAndAvailability">
<wsdl:input message="avl:PricingAndAvailabilityRequest" />
<wsdl:output message="avl:PricingAndAvailabilityResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="PricingAndAvailabilityServiceBinding" type="avl:PricingAndAvailabilityServicePort">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="PricingAndAvailability">
<soap:operation soapAction="" />
- <wsdl:input>
<soap:body parts="PricingAndAvailabilityRequestBody" use="literal" />
- <soap:header message="avl:PricingAndAvailabilityRequest" part="header" use="literal">
<soap:headerfault use="literal" part="header" message="avl:PricingAndAvailabilityRequest" />
</soap:header>
</wsdl:input>
- <wsdl:output>
<soap:body parts="PricingAndAvailabilityResponseBody" use="literal" />
- <soap:header message="avl:PricingAndAvailabilityResponse" part="header" use="literal">
<soap:headerfault use="literal" part="header" message="avl:PricingAndAvailabilityResponse" />
</soap:header>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
When i am sending the message to Webservice, After mapping,Request message is having Header and body together.
I would like to know whether xi soap receiver adapter able to include Header in SOAP-HEADER and Body in SOAP-BODY as shown in wsdl definiton and will it support multipart messages.
Thanks in Advace.
Regards,
Sreenivas.

I would like to know whether xi soap receiver adapter able to include Header in SOAP-HEADER
and Body in SOAP-BODY as shown in wsdl definiton and will it support multipart messages
there is a piece of information given in SAP note for this....check if you can get some lead from it:
https://service.sap.com/sap/support/notes/856597
From the SAP note:
My web service expects a SOAP with multiple elements in the SOAP body. How can I create such SOAP message?
Regards,
Abhishek.

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

Reliable messaging for webservices

Similar Messages

Maybe you are looking for