WCF and Xcelsius

Hi there,
I'm trying to make a data connection to a localhost WCF service and get "unable to load URL" when I add the WSDL URL http://localhost/PFSServices/PFS.Services.PurchaseOrders.svc?wsdl
Using old style web services works fine though.
Does anyone have WCF working with Xcelsius data connections ? Which binding did you use ?
Many thanks,
Andy

Andy,
You may wish to refer the link below:
"Unable to log URL" error when importing WSDL into Web Service connection
WSDLs that use DIME and other binary formats are not supported.
WSDLs that contain overloaded method are not supported.
-Anil

Similar Messages

  • Authentication to CR and Xcelsius

    Hi All,
    What authentication mechanisms are supported by Crystal reports and Xcelsius when connected to Web Serves, i.e. WSE3.0/WCF etc
    In what scenarions Win AD will work for Crystal reports and Xcelsius.
    Is it possible to setup WinAD SSO for custom .net Web services from Crystal Reports and for Xcelsius.
    Thanks in advance for your help.

    web services can be set up with vintela SSO (look up key words liveoffice SSO on SAP notes). This will work for live office and qaaws (3.1).
    Crystal and Xcelsius can consume WSDL's made in qaaws but this will not enable SSO for the client. Currently SSO to Crystal and Xcelsius clients is not supported.
    Regards,
    Tim

  • Can I access Webi queries and Xcelsius dashboards from SAP portal?

    Hello,
    Can I access Webi queries and Xcelsius dashboards from SAP portal?  And how?
    Thanks

    Portal Part 1
    /people/ingo.hilgefort/blog/2010/03/29/sap-businessobjects-enterprise-sap-enterprise-portal--part-1-of-4
    Portal Part 2
    /people/ingo.hilgefort/blog/2010/03/30/sap-businessobjects-enterprise-sap-enterprise-portal-part-2-of-4
    Portal Part 3
    /people/ingo.hilgefort/blog/2010/04/08/sap-businessobjects-enterprise-sap-enterprise-portal--part-3-of-4
    Portal Part 4
    /people/ingo.hilgefort/blog/2010/04/21/sap-businessobjects-enterprise-and-sap-enterprise-portal--part-4-of-4
    Ingo

  • Liveoffice is not visible in Excel and Xcelsius

    Hi,
    We have installed LiveOffice. This is visible in all MS Office applications like powerpoint, word and excel for the administrator .
    But when I logged into the same system, live office is visible only in powerpoint and word. It is not reflected in excel and Xcelsius. But live office is enabled for all the applications in "Live Office enable_addin".
    Please help me resolve this issue.
    Thanks in advance.

    I'm experiencing this same issue. 
    I'm running XI 3.1 with Live Office SP6 and Excel 2010
    I used the Live Office "Enable Add-in" tool to enable Excel support for Live office 3.1
    I launch Excel, and I see the Add-in for Business Objects Live Office 3.1 is present, however---
    it does not appear in the Excel menu bar
    and when I try to customize the excel toolbar or ribbon, it (Live Office) does not appear as an available option
    and when I re-launch the Live office add-in tool again, the excel box gets un-checked.
    Ideas?
    Thanks - Phil

  • Difference between Crystal Report and Xcelsius ?

    Hi,
    I am newbie to CR and Xcelsius. In most of the articles I read about CR and Xcelsius, I could not understand the difference between these two. Can anyone tell me in simple technical language whats the difference ?
    Also, does Xcelsius works only with Excel sheet ? Whats about pulling data frm Mysql to show data ?
    Thanks,
    Prashant

    Hi Prashant,
    Xcelsius is a dashboarding tool. In its simplest format it takes data from an Excel sheet and displays it graphically. It is possible to import live data into Xcelisus, primarily through Web service connections and Excel XML maps. It produces swf files (flash).
    Crsytal Reports is a toll for building reports. These are reports typically laid out in a header, detail footer format, though there is a high level of control over the display. Crystal Reports will connect to almost anything, Relational DBs, Excel, XML data. Business Objects Universes. You can imbedd Xcelsius swf files into Crystal Reports.
    In summary, CR is for reporting and Xcelsius is for dashboarding
    Try help.sap.com and business objects for the product overview documents.
    Regards
    Alan

  • Crystal Reports and Xcelsius 2008 Conference

    Hello all,
    I'm not sure which forum I should be putting this in so I'm putting it in the General Forum.  We just purchased Crystal Reports and Xcelsius in the middle of last year and I missed last years conference.  Is there a conference anywhere this year that that will really focus on Business Objects platforms?  I downloaded the SAP TechED 2008 schedule for next month but everything seems to really be geared only to SAP activities which we have none of.
    Thanks in advance,
    Ron

    Keep your eyes on the following link
    http://www.businessobjects.com/events/
    This lists current events for Business Objects and should list the next user conference as it gets closer.

  • Crystal Reports and Xcelsius Installation

    Hi I have a mac book pro and wanted to learn crystal reports and xcelsius in a hands on way. I have created a partition on the laptop and am wondering which OS to install - Windows(if so which one) or Linux. Immediate goal is have an environment where I can use CR and Xcelsius with a non sap data source. My end goal eventually is to have an environment where I can use Crystal report and xcelsius with SAP ECC6.
    I am trying to learn CR, Xcelsius with SAP ECC and SAP BW. Your ideas and isights are welcome.
    Thanks

    Hi Otto,
    Thanks for the link. Your link will be a good start for me in terms of finding out the major components required to accomplish this 'project'. I am definitely interesting in collaborating and discussing the findings and exploring the areas of opportunity, so lets stayi in touch.
    I dont have access to any windows os right now. So I am thinking about installing linux on my mac book pro since its free and probably going to beef up the ram to 3 gb (per my understanding max supported on my 2007 model). Hopefully this will get me going in the right direction.
    Any recommendations on Suse vs Red hat. looking for something that is free.
    Thanks

  • Using CR and Xcelsius with SAP BW - what is the minimal installation?

    Hi,
    If this question is allready asked and answered several times i appologize.. but I'm having a hard time finding the correct information.
    Our situation is that we run an SAP ERP and SAP BW solution with a federated SAP Enterprise Portal on top. The users require more graphical solutions for both static reporting and dynamic dashboards. So we want to use Crystal Reports and Xcelsius to provide frontend interface, but we want to do as little as possible backend, i.e avoid installing a full BO server with roles etc.
    I appriciate that we need SAP NW EhP 1 SPS 5 to load data directly into Xcelsius and the BO integration kit transports have to be loaded into the BW system for full CR connectivity.
    The problem that I'm having a hard time finding anwsers to is if this setup is capable of storing and and distributing the CR reports and dashboards to endusers? Can CR reports be stored on the BW server? Or can the CR reports and the dashboards be stored in the KW part of the portal?
    Another partly related question, what desktop tool does the enduser need to run CR reports that updates with data from the BW server?
    Alot of customers will have an SAP environment without any BO server/tools. Naturally we want to change as little as possible. A guide to what is needed for each BO BI tool to be implemented on SAP BW would be appriciated.

    Hi
    for the CR reports you need a BO Enterprise (or BO Edge) installation. The access to the BOBJ server is done transparently for your SAP BW users (they are able to start their reports in SAP GUI) but the reports are not stored on the SAP system rather in the BO repository.
    Regards,
    Stratos

  • How to deploy Qaaws queries and Xcelsius in multi server architecture

    Hi Experts ,
    I have developed a very good looking dashboard which uses qaaws queries (Dev ) to get the data in to it . I have deployed these qaaws queries to another server (UAT ) using deploy option in Query as a Web service . But still the webservice URL pointing to my DEV server .
    Also , I saved my xcelsisu file to the BO platform (in DEV) and then I imported this file in to my UAT server using import wizard . Now I opened this xcelsius file in the UAT server . In datamanager , Still I can see my webservice URL's pointing to DEV server .
    How can I deploy Qaaws and Xcelsius in a mult server Architecture . We have different servers for each environment ( Dev, INT,UAT , PRD )
    Need some one help to getout of this problem .
    Please note that my output of Xcelsius is in PDF file .
    Many thanks in advance.
    Regards,
    Dirasa

    There are several options, and an approach to make the QaaWS services environment independent
    1. When you use the QaaWS clinet builder and use the option to Copy to another server, you'll need to select the Advanced Parameters button on the 1st screen and change the server environment referernce.
    2. QaaWS services can be captured adn moved with the import wizard and Bair files.  You may want to  consider this option if you also want to capture adn contriol the QaaWS defintions for change,manangement, release management and source code control and rollback.  Moving to an new BusinessObjects environment  with Import wizard may require changnig the server environment reference with the AqqWS client connected to the target environement after it is moved.
    We have found an approach to make the QaaWS data connections in Xcelsius BO environment indendent and relatively referenced, so when you move Xcelsius dashboards sourced with QaaWS between BO environements you don't need to redefine the data connection in Xcelsius
    In Xcelsius data connections, after you paste the QaaWS WSDL on the definition tab, and import the Web Service URL field is populated with a full web service URL path http://BusinessObjectsServer/dswsbobje/qaawsservices/queryasaservice
    We have found the after the import you can edit  the web service URL and remove the BO server reference at the beginning and start it with /dswsbobje/qaawsservices/queryasaservice .
    Xcelsius dashboards in the BOE with QaaWS data connections still works to supply data to the dashboard.  When the dashboard run the BOE must assume that without an explict server reference, that it must be the current BO environment.  Another advantage of this approach is it avoids the need for a crossdomain.XML file on the BO web server.

  • BI Widgets and Xcelsius

    Hi all,
    I've got a vanilla deployment of Business Objects Enterprise XI 3.0 Premium, with some Webi and Xcelsius content added in.
    I'm trying to use BI Widgets, and I've found that while Webi works okay (ie can open a report up, drag a block onto my desktop as a widget), Xcelsius refuses to work.
    If I have a SWF file in my public folders, I cannot open it at all.  If I try to open a widget from disk, and pick the SWF that is saved to my desktop, it gives me an error.
    Anyone have any idea what is causing this?
    Thanks in advance,
    Joshua Fletcher

    Hi Fletcher,
    I am unable to solve ur problem but I will suggest u to reffer few documents from the link  http://help.sap.com/businessobject/product_guides/...
    I hope u will able to get few benifits from this.

  • Live/realtime connection between WebI and Xcelsius

    Hi,
    is it possible to have some kind of a live connection between WebI and Xcelsius for the following scenario...
    I need to have my WebI report made availabe as an Xcelsius Dashboard and when I filter a value in the dashboard it should also get filtered in the WebI report. Is this possible and if so then how?
    Pls help.
    Thanks,
    SD
    Edited by: Sebastian D'Souza on Feb 22, 2011 11:39 AM

    Hi Sebastian,
    Yes this is very possible. Of the three connection methods (QaaWS, Live Office, BI Services) I would recommend BI Services for flexibility, speed to set up, and speed for query refresh times.
    Check out this post for a step-by-step guide http://blog.davidg.com.au/2011/03/drill-down-in-xcelsius-using-bi.html
    And refer to the Webi Rich Client guide in the section "Sharing Web Intelligence content with other Web applications" for the full details of how this works.
    Hope this helps.

  • Beginner's questions about WCF and web services

    For the purpose of this forum let me just say that I got my certs back in Dot Net 2.0.  I know how to write simple web services.  Now someone has dumped a huge package of code on my desk that (I think) contains a WCF project (without documentation
    of course).  Contains references to System.ServiceModel.
    So my questions...
    1.  What (if anything) is the difference between WCF and Web API?
    2.  If there is a difference,  how do you decide which one to use?
     3.  Assuming that this project on my desk is a WCF project, where can I find some hints on how to run it in VS2013 Community? 

    WEB API is restricted to ASP.NET and HTTP. 
    http://captechconsulting.com/blog/john-nein/aspnet-web-api-vs-windows-communication-foundation-wcf
    WCF uses more communication protocols than just HTTP, there are more ways to host a WCF service other than IIS, like a selfhosting exe type WCF server,   and WCF is a SOA solution.
    WCF is a more robust solution in a whole lot of ways is the bottom line.
    http://en.wikipedia.org/wiki/Service-oriented_architecture
    http://www.codeproject.com/Articles/515253/Service-Oriented-Architecture-and-WCF

  • What's the difference between polestar and xcelsius?

    HIi all,
    I've new to BOBJ software and have played a little bit with xCelsius. It seems that both Xcelsius and polestar can be used to generating charts/reports and so on, can anyone tell me
    1. what's the difference of these 2 tools?
    2. I know after creating a chart with xCelsius, it can be exposed as a webservice and can be used to integrate into other webpages, can polestar also do so? if yes, is there any document about it?
    thanks very much!
    Regards,
    Bin

    Xcelsius is a data visualization tool whereas Polestar is a search engine with graphical capabilities.
    Xcelsius was established to enable users to load and quickly create dashboards from disparate sources. Polestar was established to search through all your enterprise meta data - and Xcelsius is now another component that can be included in this enterprise wide search.
    I.e. Xcelius exists on a level below Polestar.

  • Difference between Performance Manager and XCelsius

    Can anybody outline the differences/provide a document which would help me understand the differences between the working of Performance Manager and XCelsius?
    Can Performance Manager be substituted with XCelsius and can XCelsius be integrated with Performance Manager?
    Thanks,
    Karthik Mohan

    I think your problem may be able to be solved by Dashboard Builder. It can embed the Xcelsius

  • 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:RequireThumbprintReference/>-->
    <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:RequireThumbprintReference/>-->
    <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:RequireThumbprintReference/>-->
    <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:RequireThumbprintReference/>-->
    <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.

Maybe you are looking for