Sender Agreement endpoints URL - is it configurable?

Hello All
I have two PI servers: DEV and QA. DEV works ok, but after transporting objects from DEV I've noticed, that SOAP Sender Agreement gives WSDL which contains service endpoint url from DEV system. Main WSDL Url is correct - from QA.
Are those endpoinds somehow configurable? How to make this WSDL correct, that QA serves those services?
TIA
Best Regards
Maciej

Hi Maciej,
answering your question indirectly
it's not PI that you're looking for right now but your sender application
it's the sender application that needs to be able to determine the URL (server) correctly (for dev,qa, prd)
as you only generate a proxy for it once (on the dev system), right ?
so it should be possible to change it in the sender app and not in the receiver I believe - at least that's how it works in simplest cases (no SR etc.)
Regards,
Michal Krawczyk

Similar Messages

  • Sender Agreement Endpoint Creation

    Hi,
    I have a SOAP - PI - Proxy scenario where I want to call the sender agreement to initiate the message.  In the Integration Builder, I see that I can display the WSDL for the Sender Agreement.  If I take that URL and put it into WS Navigator, I can successfully get the entire message flow (sync).
    My question is, how do I create my own/secondary binding for this agreement?  It seems like they generate one for you automatically and you have no control over the configuration for it.

    Hey
    When you are using SOAP on the sender side,you need to generate WSDL file in Integration directory and provide to the sender system,in this WSDL you have option to specify the URL,this URL is used by the sender system to the post file.
    if you want to post the message directly to Integration engine of XI,then you can just click on "Propose URL" button which you get while creating WSDL file(this wont use sender agreement).
    The below blog will help you in that.
    /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
    But if you want to post to the adapter engine,then you need to generate the URL in the format as described in the below blog.don't click on "Propose URL" in this case(this will use sender agreement).
    /people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
    Thanks
    Aamir

  • No sender agreement configured in the XI Integration Directory

    Hi,
    I am using MPA(MML) message format in XI scenario. My scenarios are R3->XI->Marketplace and Marketplace->XI->R3. The first scenario works fine with no problems where as when i try to post MML message from marketplace to XI system, i am seeing the "No sender agreement configured in the XI Integration Directory for the given message header:SenderParty=xxxx; ReceiverParty=; SenderService=xxxxx; ReceiverSerivce=xxx; Interface=xxxx; InterfaceNamespace=xxx;". I have created sender agreement for this secenario, and moreover i haven't this sender agreement in the xi cache. Please let me know if i am missing anything in the configuration.
    Thanks & Regards
    Sruj

    Thanks a lot for replies, but i have tried all these options but no luck. Does it need any additional configurtion to resolve this issue, i dont think this is cache issue, if that is the case after all steps which i have done should have fixed it. Please post your comments.
    Once again thanks a lot for everyone.
    Thanks & Regards,
    Sruj
    Message was edited by: Srujan Gogineni

  • No Sender Agreement Configured in Dual Stack( PI 7.31)

    Hi All,
    I am configuring a simple file to file scenario.
    Initially i Have created the scenario without ICO and It worked fine.Later I changed this ( ie, I have deleted sender agreement,Interface determination etc)
    and used ICO to configure.
    But I am getting the below error.
    If the configuration is based on ICO,I don't think sender agreement is required.Please help.
    Regards,
    Tibin Joseph

    Hi Tibin,
    Please, if your issue is solved close the thread according this How to close a discussion and why
    In this way further SCN members can figure out how to resolve their problems easier.
    Regards.

  • XI 3.0  Sender Agreement error during Configuration Wizard

    Hi
    During the Sender Agreement generation of the Configuration Wizard an error occurs because it takes the value of "" for Receiver Party and Service.  This was discuused during the XI252 Session at the San Diego SAP TechEd.  The proposed solution was to copy the existing Sender Agreement and remove the "" values.  However, no Sender Agreement exists that could be copied.  Therefore, I attempted to manually create a Sender Agreement.  But now I end up with the following error:
    Thrown:
    MESSAGE ID: com.sap.aii.ib.bom.landscape.rb_landscape.SLD_***_NOT_FOUND_EX
    com.sap.aii.utilxi.swing.framework.PersistenceException: Unable to find an associated SLD element (source element: SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, XID, string], target element type: SAP_BCSystem)
    Has anybody encoutered this also, and more importantly, found a solution?
    Frank Deijkers

    Hi,
    I think you have to add:
    Optional: xml.addHeaderLine 0
    Obligatory: try to put the ; between quotation marks like:
    Hope this helps.
    Cheers,
    Paul

  • Sender Agreement SWIFT Configuration

    Hi Guys, I need your expertise regarding the SAP SWIFT configuration, i am following a PDF file (ConfGuide_SWIFT_602_v0_4.pdf).
    Basically, this is what I have done so far.
    1. Create a business service and modifying the receiver tab page according to the pdf file
    2. Create the receiver and communication channels in the created business service.
    3. During the creation of sender agreement, it states that the interface to be used is SwiftMessage, however, from the list of choices, it is not visible, I think this is due to the fact that in the design, the message interface SwiftMessage is declared as abstract.
    The question is, is there a way to get pass this without changing the category of the message interface?
    Thanks!

    When you create business services, you have to manually add the interfaces in the sender/receiver tabs of the service page. Once you add them here, you will be able to see them in the available interfaces.
    However, sender agreements are not needed for the abstract interfaces. You might have to recheck if you have wrongly defined your interfaces.
    VJ

  • Test Configuration Tool: Sender Agreement Not Found

    Hi, All:
    We have new XI3.0 setup and I just want to test simple file to file scenario, but the file was picked up by sender file adapter, however, there is no message sent to Integration server.
    When I use Test Configuration Tool, the sender agreement is green, however, it also mention Sender Agreement Not Found, see below:
    ================================================
    Sender Agreement
    ================================================
    futhermore, Interface Mapping is not found either. Actually, Interface has been created on IR. Sender Agreement also created in ID.
    Anyone who has idea about these two errors ?
    Thanks in advance
    Liang

    Hi, Raj and Srinivas:
    Thanks for your reply.
    First of all, all the objects are activated,  secondly, when create sender agreement, I just need to input the Sender Service Name / Sender Interface / Sender Interface Namespace. Then finally select commnication channel.
    For any Receiver sides, they are grey out, I am not able to input anything.
    So, there is no "*" in any fields.
    I doubt if there is any setup wrong, especially for adapter engine, maybe some modules that are not functional for file adapter engine, since I also see other problems,  I might post them as separate thread.
    In Adapter monitor page, I did not see the adapter.
    In RWB, if I use IE, there is Error in the page, using Firefox, it is OK.
    Thanks And Regards !
    Liang

  • Problem with Axis Adapter endpoint url in WSDL file.

    Dear experts,
    We are using PI 7.1 ehp1 with a SOAP to RFC scenarios using the Axis adapter.
    We have the XIAxisAdapter as sender Communication Channel and the related Sender Agreement.
    When i am looking into the WSDL file of the Sender Agreement than the endpoint contains ...location="host:port/ XISOAPAdapter /MessageServlet"... in stead of ...location="host:port/ XIAxisAdapter /MessageServlet"...
    The url with "XISOAPAdapter " will not work. When i export the WSDL file and manually adjust the location to "XIAxisAdapter " everything works fine.
    Is it possible to directly generate a correct WSDL with calling the url http://host:50000/dir/wsdl?p=xxxx?
    Thanks in advance!
    Best regards,
    Joost Weghorst

    Hi Sonya,
    You can use configuration plan while deploying composite.
    The configuration plan enables you to define the URL and property values to use in different environments. During process deployment, the configuration plan is used to search the SOA project for values that must be replaced to adapt the project to the next target environment.
    Please refer this doc. for getting introduced to config plan.
    http://docs.oracle.com/cd/E29542_01/dev.1111/e10224/sca_lifecycle.htm#SOASE10908
    To deploy soa composite with config plan refer this doc:
    http://docs.oracle.com/cd/E29542_01/dev.1111/e10224/sca_lifecycle.htm#SOASE85469

  • ERROR in PI : No sender agreement found for , , , , ,

    Hello everybody,
    i'm working with SAP PI 7.1
    it's a new installation.
    I created the first easy interface JDBC-Pi-File.
    when i activate the CC i don't see any message in SXMB_MONI but in RWM i see the messages in Waiting status and when i look inside i see the follow error:
    SOAPFAULT received from Integration Server. ErrorCode/Category: XIServer/INBOUND_BINDING_ERROR; Params: BS_CSIS_DEV, http://xxxx.com/test, SI_DB2SP_DOCUMENTS_AA_02; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Error in sender agreement for party , service BS_CSIS_DEV, interface namespace http://xxx.com/test interface SI_DB2SP_DOCUMENTS_AA_02 No sender agreement found for , , , , ,
    1-Configuration is ok. I create all steps and sender Agreement exist
    2-end point http://yyyyy:50100/sap/xi/engine?type=entry is correct and the same in SLD and sxmb_adm -> Integration Engine Configuration
    3-i suppose 50100 port is correct because when i try to use 8010 port i have a different error.
    4- i alreadi used CPA cache refresh and SXI_CACHE.
    Any suggestion?
    thanks

    after 20 minuts i retry.
    Now the error message is changed:
    Transmitting the message to endpoint http://yyyyyy:8010/sap/xi/engine?type=entry using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.net.ConnectException: Connection refused.
    Edited by: apederiva on Aug 25, 2010 11:35 AM

  • HTTP response code 500 : Error during Sender Agreement Determination

    I am trying a simple file to file scenario and messages are not being received in Integration Server.
    Through communication channel monitoring, i have received the below error message.
    Error Transmitting the message to
    endpoint http://<hostname>:50000/sap/xi/engine?type=entry using
    connection File_http://sap.com/xi/XI/System failed, due
    to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException:
    Received HTTP response code 500 : Error during Sender
    Agreement Determination.
    Can you please help
    Regards
    Harish

    Hi Harish,
    http://<hostname>:50000/sap/xi/engine?type=entry
    it should be http://<hostname>:8000/sap/xi/engine?type=entry not 50000 as port It should be your HTTP port...please .make the changes !!
    In SXMB_ADM transaction under Integration engine configuration please change the settings to http://<hostname>:8000/sap/xi/engine?type=entry
    make sure with your basis team that ur http port is 8000 or 8001 ..as per that make the necessary changes..
    Regards,

  • Invalid endpoint URL

    Hello all,
    I am developing a portlet that uses EDK 5.1 (.NET). In the Page_Load event handler, I have the following two lines of code:
    Plumtree.Remote.Portlet.IPortletContext myPortletContext = Plumtree.Remote.Portlet.PortletContextFactory.CreatePortletContext(this.Request, this.Response);
    Plumtree.Remote.PRC.IRemoteSession myRemoteSession = myPortletContext.GetRemotePortalSession();
    Unfortunately, the second line of code throws an exception that I am not able to know its reason. Here is the exception message:
    [HttpException(0x80004005): Invalid URI: The hostname could not be parsed.] Plumtree.Remote.Portlet.PortletContextWrapper.GetRemotePortalSession()in e:\buildroot\Release\devkit\5.0.x\portlet\src\dotnet\Plumtree\Remote\Portlet\PortletContextWrapper.cs:55 CommunityFolders.FoldersDisplay.Page_Load(Object sender, EventArgs e) +2008 System.Web.UI.Control.OnLoad(EventArgs e) +67 System.Web.UI.Control.LoadRecursive() +35 System.Web.UI.Control.LoadRecursive() +98 System.Web.UI.Control.LoadRecursive() +98 System.Web.UI.Page.ProcessRequestMain() +744
    From the EDK documentation, I recognized that this exception is thrown when "the endpoint URL is not valid", however, I couldn't know how to fix it. Is the endpoint URL stored in the database, or is it in a configuration file?
    Would anyone please help me with this?
    Thanks.
    Ramy Omar,
    ITWorx, on behalf of UTC

    Have you tried using TCPTrace or some other intermediate HTTP/SOAP interception tool that will let you watch the body of the request? I'd give that a go first just so you can peek inside and see what the EDK is trying to hit.

  • Sender Agreement - Display WSDL

    Hi,
    We have a sender agreement with a communication channel of type WS.
    When we try to do Sender Agreement --> Display WSDL, we get the following error:
    Cannot determine HTTP information (protocol, host, port) of current application server (RC=1-)
    Our system is configured for SSL and we have disabled the ICM HTTP service, leaving only HTTPS service on.
    If we activate the ICM HTTP service, then we can display the WSDL. But in the WSDL URL field, it says "http://ourdomain.com:50000/..........", which explains why it failed when we deactivate the HTTP service.
    How can we make this functionality working with HTTPS? We would like to have a WSDL URL like "https://ourdomain.com:50001/......."
    Thanks in advance

    By the way, when I start transaction SOAMANAGER, it open the browser with the URL http://server.domain.com:0/....... (we have configured ICM HTTP service with port 0).
    How I can make SOAMANAGER open the URL https://server.doamin.com:50001/..... (50001 is our ICM HTTPS port) ?

  • Sender Agreement Publishing

    Hi,
    I have a question about accessing a sender agreement's published web service.  I have a scenario where I have published the sender agreement to my service registry and can successfully test that webservice (endpoint) through WSNavigator. 
    The problem that I am having is that I can not see the webservice in Visual Composer or Web DynPro.  This is most likely due to the fact that I do not have the right destination templates configuration set in NWA on my CE server.  
    Can any of you provide the proper configuration settings for this so that I can use the webservice?
    Thanks in advance.

    Thanks for the response.
    We have used that guide to successfully access web service providers from ECC based systems, but when we followed the same strategy for our PI system we have no luck.
    Whats strange is that we can publish the service from the builder in PI, using their tool, and access it in the service registry.  Testing works fine and we can see the message flow the way we are expecting. 
    However when try to access the web service outside of the SR, like in Visual Composer or Web DynPro, we are not able to see the service.
    This makes me think it has something to do with the ability to query the SR or that the binding is somehow protected so that it is not visible.

  • Customizing ENDPOINT URL generated in PI

    Hi Experts,
    I have generated the WSDL in PI.
    The Endppoint URL is as follows.
    http://hostname:port number/XISOAPAdapter/MessageServlet/sender_party;senderService = xxx;receiverparty=;receiverService=yyy;interface name;namespace
    But the client needs the cutomized endpoint URL as mentioned below without PI object details like service interface name, namespaces
    http://hostname:port number/XISOAPAdapter/MessageServlet/DataInsert
    Any solution for this?
    Can we do the customization anywhere?
    Thanks in advance
    Best regards,
    Deepthi

    You can choose between 2 URL patterns, as stated in Configuring the Sender SOAP Adapter - Advanced Adapter Engine - SAP Library | paragraph Result:
    You can trigger a call to the sender SOAP adapter using either of the following URLs. However, SAP recommends you to use the second option. 
      http:// <host name> : <port name> /XISOAPAdapter/MessageServlet?channel= <party name> : <service name> : <channel name> . If you have not created a party, enter channel=: <service name> : <channel name>   
      http:// <host name> : <port name> /XISOAPAdapter/MessageServlet?senderParty= <name of the sender party> &senderService= <name of the sender service> &interface= <name of the interface> &receiverParty= <name of the receiver party> &receiverService= <name of the receiver service> &interfaceNamespace= <name of the interface namespace>

  • Change standard port in Endpoint URL Services registry

    Hello all,
    I am trying to publish a Service Interface into the Services Registry from a Sender Agreement. This works fine. Default this is done with port 50000. I would like to have a standard value of port 80 there so I do not have to change this by hand each time i publish a service.
    I already have tried HTTP Mapping in the NWA but I do not see the endpoint published with port 80 in the Services Registry.
    Has anyone an idea of how to change this value?
    Best regards,
    Fons van Nuland

    here is the error from .net
    The document at the url
    http://XXXX:8002/sap/bc/srt/wsdl/bndg_DEEFA40807E3B8F1948E00215E56BC34/wsdl11/allinone/standard/document?sap-client=100 was not recognized as a known document type.
    The error message from each known type may help you fix the problem:
    - Report from 'WSDL Document' is 'There is an error in XML document (1, 500).'.
       - 'Element' is an invalid node type. Line 1, position 500.
    - Report from 'DISCO Document' is 'Discovery document at the URL http://XXXX::8002/sap/bc/srt/wsdl/bndg_DEEFA40807E3B8F1948E00215E56BC34/wsdl11/allinone/standard/document?sap-client=100 could not be found.'.
       - The document format is not recognized.
    - Report from 'XML Schema' is 'Expected Schema root. Make sure that the root element is <schema> and the namespace is 'http://www.w3.org/2001/XMLSchema' for an XSD schema or 'urn:schemas-microsoft-com:xml-data' for an XDR schema. An error occurred at , (1, 40).'.

Maybe you are looking for