SOAP sender endpoint problem

Hi all,
I'm now fighting for quite a time with a SOAP sender channel.
I generated a WSDL in the configuration. I used this wsdl in XMLSPY in order to send a request to XI.
And I must confess that I'm totally confused with the URLs. Which one do I need to take (we're using XI 3.0):
http://server:3400/sap/xi/engine?type=entry&version=3.0&Sender.Service=service&Sender.Interface=urnInterface
or
http://server:50000/XISOAPAdapter/MessageServlet?channel=party:service:channel
What is the difference between those URLs?
And for the Java URL (port 50000): Which channel do I have to announce? The Name of the SOAP sender communication channel?
Since XI proposes the url with 3400 port I think this one is appropriate. But whenever I use it I receive a RCVR_DETERMINATION.MESSAGE_INCOMPLETE error and the message is indicated in the monitoring as coming from "AnonymousClient". What do I do wrong? I also tried to force the SOAP adapter to use the parameters by checking the option "Use Query String" in the channel config.
Please help!
Thanks in advance.

Hi Frank,
thank you for your answer.
I added the default XI parameters.
Concerning the userID and Password: I am asked to enter login/pwd if I call the service. Is this what you mean?
Unfortunately this does not affect anything...
The response I get is the following:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
  <faultcode>SOAP:Server</faultcode>
   <faultstring>System Error</faultstring>
    <detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
     <context/>
     <code><b>RCVR_DETERMINATION.MESSAGE_INCOMPLETE</b></code>
                         <text/>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
What amases me is that the ns is http://sap.com/xi/WebService/<b>xi2.0</b>. I used the url including the part &version=3.0
Does this url work for you (I mean including the version)
Could the error also be related with other configuration errors (wrong receiver agreement) - I do'nt thnik so but sth goes definetively wrong.
Greets,
Joachim

Similar Messages

  • Problem: Original Attachment Name from SOAP Sender changes to attachment-1

    Hi everybody,
    we have a scenario where a SOAP sender receives a xml message describing several documents. Each document has a mime type and a file name, size, md5 checksums etc as attributes.
    The documents are send as attachments with the same Web service in SWA(SOAP with attachment style).
    The web service calls an ABAP proxy provider class in a R/3 backend.
    The ABAP proxy class will save the attached documents for further processing and must use the original document names.
    At the soap communication channel monitoring(Java Stack) we still see the original attachment names in the message content tab.
    At the Integration Server(sxmb_moni) the attachment name changes to attachment-1, attachment-2 and so on.
    Using the method
    IF_AI_ATTACHMENT ->GET_DOCUMENT_NAME
      in the provider ABAP proxy class returns the name attachment-1.
    We can see that there is a mapping of the new attachment-1 name to the old, original name in the manifest section of this message on the Integration server.
    Is there a way to access the manifest section at a provider ABAP proxy class?  Or otherwise a PI configuration setting to preserve the original attachment names.
    Thanks a lot,
    Heiko
    => PI 7.1 SP9

    Hi Stefan,
    (I was hoping you would find that thread ...)
    I see a good reason why the attachment names are changed as the PI message protocol sends the main document as an attachment as well. So no problem with that because the information of the mapping old to new names still exists in the manifest part and is visible at the sxmb_moni.
    We see a manifest part like this (Sorry cant post the whole xml doc as the formatting for longer messages isn't working in the forum)
    <SAP:Payload xlink:href="cid:4cc43edd-839f-423f-b7c6-7e44294d663a_sig.p7m">
      <SAP:Name>attachment-1</SAP:Name>
      <SAP:Description>attachment</SAP:Description>
      <SAP:Type>ApplicationAttachment</SAP:Type>
    </SAP:Payload>
    The (red) cid entry is the original file name. This manifest is from the sxmb_moni in the r/3 backend. So all the information is there..  The question is how to retrieve this information .. Any idea?
    Best Regards,
    Heiko Bergmann

  • Another problem with SOAP sender

    I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
    Scenario:
    Soap Sender -> PI -> Soap Receiver
    Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
    I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide.  It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call). 
    Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\].  The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
    Problem One:
    The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types.  XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
    Problem Two:
    I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send.  In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
    The other doGoogleSearch fields seem to be missing, i.e.
      <part name="q" type="xsd:string" />
      <part name="start" type="xsd:int" />
      <part name="maxResults" type="xsd:int" />
      <part name="filter" type="xsd:boolean" />
      <part name="restrict" type="xsd:string" />
      <part name="safeSearch" type="xsd:boolean" />
      <part name="lr" type="xsd:string" />
      <part name="ie" type="xsd:string" />
      <part name="oe" type="xsd:string" />
    Does anyone know why:
    (1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
    (2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
    Thanks for any help with this.

    I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
    Scenario:
    Soap Sender -> PI -> Soap Receiver
    Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
    I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide.  It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call). 
    Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\].  The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
    Problem One:
    The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types.  XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
    Problem Two:
    I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send.  In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
    The other doGoogleSearch fields seem to be missing, i.e.
      <part name="q" type="xsd:string" />
      <part name="start" type="xsd:int" />
      <part name="maxResults" type="xsd:int" />
      <part name="filter" type="xsd:boolean" />
      <part name="restrict" type="xsd:string" />
      <part name="safeSearch" type="xsd:boolean" />
      <part name="lr" type="xsd:string" />
      <part name="ie" type="xsd:string" />
      <part name="oe" type="xsd:string" />
    Does anyone know why:
    (1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
    (2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
    Thanks for any help with this.

  • Problem to invoke SOAP Sender Adapter

    Hi,
    i've got a problem to invoke the SOAP sender adapter. The returned exception says:
    "Some of the IS access information is not available. SLDAcess property may be set to true, but SLD is not available."
    I can access the SLD web client and I have also refreshed the SLD runtime cache. The J2EE engine had a shutdown due to an "out of memory error", could it be that some things have become upside down there?
    Regards,
    Heiko

    hi,
    restart your j2ee server and try again.
    naveen

  • Problem between SOAP Sender and JDBC Receiver

    Hi,
    I have a asynchronous scenary between SOAP Sender and JDBC Receiver.
    The idea is sending an ID for updating one register.
    Table structure is:
    TABLE AS_PERSONA
        (P_RUT                         VARCHAR2(10) NOT NULL,
        P_NOMBRE                       VARCHAR2(50),
        P_APELLIDO                     VARCHAR2(50))
    The ID is the P_RUT field.
    The structure of message that I send by SOAP, is the following:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <SOAP-ENV:Body>
              <m:MT_CONS_SOAP xmlns:m="urn:prueba:voliva">
                   <CONSULTA>
                        <P_RUT>15445</P_RUT>
                   </CONSULTA>
              </m:MT_CONS_SOAP>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    The JDBC receiver structure is:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_CONS_PERSONA xmlns:ns0="urn:prueba:voliva">
         <Statement>
              <AS_PERSONA action="UPDATE">
                   <table>AS_PERSONA</table>
                   <access>
                        <P_NOMBRE>DELETE_BY_XI</P_NOMBRE>
                        <P_APELLIDO>DELETE_BY_XI</P_APELLIDO>
                   </access>
                   <key>
                        <P_RUT>15445</P_RUT>
                   </key>
              </AS_PERSONA>
         </Statement>
    </ns0:MT_CONS_PERSONA>
    When I do a call to SOAP by XMLspy, it returns a message without data, that means succesfull reply.
    I see message monitor and see the succesfull flag. But in the database it doesn't update the register.
    This scenario was proved using the File Sender and same JDBC Receiver, then result was succesfull.
    I proved SOAP Sender with a File Receiver, storing information from SOAP sender in an archive, and works well.
    Then I imagine that exist some problem between SOAP and JDBC. what could be happening ?
    Thanks.

    Hi,
    Looks like the problem is with the JDBC receiver...try updating the value in the table by using a File-JDBC scenario..does it work..check the adapter monitor in RWB..
    Regards,
    Sushumna

  • Problem with Soap Sender CC

    Hi,
    SOAP - Proxy.
    I have 3 seperate Scenarios in PI 7.0 in different Name space, with different Message interface names, under same SWC.
    I imported them to PI 7.1 and used the same format that help says... with Service:cc and gave it to the calling service.
    During my import, I noticed that the Message Interface and Name space were knocked off from the SOAP Sender adapter in PI 7.1. The scenarios are configured and working currently.
    I have 3 CC in this format. In Soap sender CC, we will specify NS and Interface name. Thus I had to use 3 CC.
    As per SAP Note 856597, the sender CC format should be...
    http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&senderService=FS&interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace
    Now, in 7.10 we dont need to specify NS and Message Interface in soap sender CC. Hence, I created 3 sender URL for each scenario to call to PI 7.10 ( based on the interface / NS names ) and I have created 1 CC only instead of 3. This I thought would work because the sender CC is not tied with NS or MI any more, which are included in URL, and thus I have 3 different calling URLs.
    Now, when I do this and activate, it is always calling only one service all the time.
    Regards,
    Venkat.

    I have used the other channels in the same format. only NS and MI name changed. Sender and receiver are same.
    We do specify outbound Interface and its NS in sender Soap CC prior to 7.1.
    Morever, I am following the format as per the note I specified above.
    It is able to call PI 7.1 succesfully but failing to call proper IM and MM.
    No error mesage but only one scenario is called all the time.
    Its like this...
    prior to 7.1, we will have MI and NS info on the sender Soap sender CC. Hence we just mention the name of the CC in the target URL along with service. so it picks up the NS and MI from CC.
    in 7.1, since we dont specify NS and MI in sender Soap CC, we have to notify the sender side MI and NS and we do that in sender side URL( to be given to the calling system ).
    Now as per my understanding, since no NS or MI dependant info is speicfied in CC, I thought we can use one single CC instead of 3.
    See my thought looks reasonable ...
    but wondering why it isnt working.
    Regards,
    Venkat.

  • Connection problem in SOAP Sender Channel

    Dear All,
    I have created two SOAP Sender channel with the following specification:
    Transport Protocol - HTTP
    Message Protocol - SOAP 1.1
    HTTP Security Level - HTTP
    But while sending a message from a Java client, I am getting the following error :
    The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Basic realm="XISOAPApps"'.
    Please suggest if you find any way out.
    Thanks and Regards,
    Rana Brata De

    Hi Rana
    Looks like you have used authentication scheme as 'anonymous'. But you have chosen the option 'HTTP' in soap adapter.
    So you have to pass the user id and password during the call.
    Sample Code:
    ICalcCTCWebService calcCTCWebService = calcCTCWebServiceImplServiceLocator.getCalcCTCWebServiceImplPort();
    Stub stub = (Stub)calcCTCWebService;
    stub._setProperty(Stub.USERNAME_PROPERTY, "abc");
    stub._setProperty(Stub.PASSWORD_PROPERTY, "xyz");
    You can also test the WSDL from SOAP UI and provide user name and password in the header section in SOAP UI and see if the message goes to PI or not.
    You can also try the below option in the sender soap adapter and see if it works or not.

  • Soap sender adpater issue missing sender interface and namespace in the msg

    Hi Expert,
    I got a problem when try to using soap sender adapter.
    Here is the sceanrio:
    Http web service client call ---PI soap sender adapter -some routing data-business system inbound.
    Sytem information:
    SAP_ABA     700     0019     SAPKA70019     Cross-Application Component
    SAP_BASIS     700     0019     SAPKB70019     SAP Basis Component
    PI_BASIS     2005_1_700     0019     SAPKIPYJ7J     PI_BASIS 2005_1_700
    ST-PI     2008_1_700     0001     SAPKITLRD1     SAP Solution Tools Plug-In
    SAP_BW     700     0021     SAPKW70021     SAP NetWeaver BI 7.0
    ST-A/PI     01L_BCO700     0000          -     Servicetools for other App./Netweaver 04
    Here is my problem. I use soapui trigger a test msg to PI system. But in the sxmb_moni, only sender service is there.
    The sender interface and sender namespace is missing. And the msg has error called: :INTERFACE_REGISTRATION_ERROR.
    Which means I do not have a inbound interface to process the msg.
    But I suppose to redirect the msg to business system.
    Here is the configuration:
    reciever determination: soap sender service, soap outbound interface, soap interface namespace --> reciever business sytem.
    Interface ditermination: soap sender service, soap interface --> receiver interface, receiver namespace.
    Sender agreement: soap service, soap itnerface --- soap communication channel
    receiver agreement, soap service---> receiver sevice, receiver interface, reciever namespace  and reciever cummunication channel
    define of soap sender adapter:
    soap sernder, with use encoded header and use query string checked and qos as exactly once.
    Anyone has any idea here? Many thanks! And most strange thing is yesterday it works and today it failed.
    Please kindly help here.
    Thanks a lot,
    Leon

    Hi guys,
    thanks for the input.
    Hi Sven,
    I have input default interface and namespace.
    Hi sivasakthi,
    Regarding mistype, it may happen, I will do it again right away.
    And the URL is generated by the wsdl toolkit in the directory.
    I marked use encoded header and query string in the communication channel.
    I will generate the wsdl again and test it again.
    Regarding URL(endpoint of web service):
    http://hostname:50000/XISOAPAdapter/MessageServlet?channel=:AGSSAL_SOAP:AGSSAL_SOAP_CC&version=3.0&Sender.Service=AGSSAL_SOAP&Interface=urn:a1s_saplivelinkcontent.service.sap.com^MI_O_AS_DELIVERNOTIFY_SOAP
    Again thanks for you guys help.
    Best regards,
    Leon

  • Variable Transport Binding - Soap Sender

    Hello all,
    I'm trying to retrieve a parameter from the HTTP header of a SOAP request.
    I have created a SOAP sender communication channel, checked "Set Adapter-Specific Message Attributes" and "Variable Transport Binding", and entered the name of the parameter in Variable Header (XHeaderName1).
    When I send the SOAP request, DynamicConfiguration exists with all standard parameters, but there is no XHeaderName1...
    If I try the same with sender HTTP adapter, it works fine.
    In the other way, if the dynamic configuration parameter XHeaderName1 already exists, and I try to add it in a HTTP header parameter in a receiver SOAP CC, that works.
    Does somebody know why this doesn't work in the sender one?
    Thanks,
    Greg
    PS: I'm using PI7.0 SP14

    Hello,
    I can see in dynamic configuration, with the namespace http://sap.com/xi/XI/System/SOAP, the standard HTTP parameters like SServerHost, SRemoteUser, etc...
    But if I add a HTTP header parameter in the SOAP request, and I try to retrieve it with the SOAP sender CC, the parameter is not added in the dynamic configuration. If the name of the added HTTP header parameter is "TestParam", I put "TestParam" in the XHeaderName1 field of the sender CC, but the value is not added in the dynamic configuration. This is my problem.
    Thanks,
    Greg

  • Variable Transport binding - SOAP Sender Adapter

    Hi All
    have a scenarion where Sender System is sending Custom SOAP Header as below into P through SOAP Sender ChannelI.
    And the requirement is to access the values coming in Header fields, example within Message Mapping need to Map Headername1 value to Outgoing structure.
    <soapenv:Header>
         <Header1>S1</Header1>
         <Header2>S2</Header2>
         <Header3>S3</Header3>
    </soapenv:Header>
       <soapenv:Body>
         u2026..
       </soapenv:Body>
    Have checked the Paramter KEEP Headers in SOAP Adapter and in Adapter Specific Message Attributes have defined the following
    Variable Header (XHeaderName1) = Header1
    Variable Header (XHeaderName2) = Header2
    Variable Header (XHeaderName1) = Header3
    Now need to know what should be mentioned in the UDF in the Message Mapping for accessing Dynamic Configuration. Will these headers mentioned will be a part of Dynamic Configuration or not ?
    Using the below UDF and its failing in Message Mapping - kindly suggest the corect way of achieving the same
    DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "XHeaderName1");
    String value = conf.get(key1);
    return  value  ;
    Appreciate response in this regard
    //Swetank

    Hi Abhishek
    Its failing at runtime at Message Mapping stage. The real problem is that I can't see the Header1 in my Dynamic Configuration header - it has all the other fields like SServerHost, SRemoteUser, but not my Header1 (S1) field. Thus either the UDF is wrong or any configuration in SOAP Sender Channel needs to be adjusted.
    Further I am not sure whether Custom SOAP Header fields can be a part of Dynamic Configuration or they only show fields which are part of HTTP header.
    //Swetank

  • SAP PI 7.1 SOAP sender 500 internal server error

    Hello!
    We would like to receive messages from our business partner. As the partner sends EDIFACT we have to use the conversion from EDIFACT-text to EDIFACT-xml. That's why we have to use SOAP instead of plain HTTP.
    As the partner already sent messages over X.400 we just added a SOAP communication channel and used this channel in the sender agreement instead of the X.400 communication channel.
    We sent the following link to the customer:
    http://<server>:<j2ee port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<SOAP sender communication channel>
    One question: is the <service> the communication component used for the partner?
    At the moment the partner receives a 500 error message. Due to our network partner the message reaches the PI system.
    Due to the information I found that also a message parsing error can cause a 500 error message I would like to add the processing sequence:
    Does anyone have an idea how to solve this problem?
    Thanks a lot!
    Regards
    Christian

    Hi Christian
    You can refer to the following SAP Library link on how to configure the SOAP sender.
    Configuring the Sender SOAP Adapter - Configuring the SOAP Adapter in the Integration Directory/PCK - SAP Library
    For the URL, the <service> is the Communication Component that the SOAP channel belongs to.
    Using the example below, the value would be P_B2B_:BC_:CC_S_SOAP_
    Actually SAP recommends a new alternative for the URL. If you scroll right to the end of the library link above.
    You have configured the sender SOAP adapter. 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://hostname:portname/XISOAPAdapter/MessageServlet?channel=partyname:service name:channelnameIf you have not created a party, enter channel=servicename:channelname.
    http://hostname: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
    You can get this by generating the WSDL from the Sender Agreement object (Sender Agreement -> Display WSDL). The generated URL will be at the last section of the WSDL.
    Also, please note that modules cannot be added to the SOAP sender adapter, also mentioned in the link.
    You cannot add your own modules to this adapter.
    An alternative would be to receive the EDIFACT Flat file as it is, and write it to at temporary File/FTP location. Then have a second channel pick it up, you can configure the second channel with module to convert it to EDIFACT XML.
    Lastly, regarding the issue about the partner getting HTTP 500 error. Please check if you are able to see any error logs in the communication channel. It might give you some pointers as to what might be wrong - invalid sender agreement, etc, etc.
    Rgds
    Eng Swee

  • SOAP receiver exception problem

    Hi XI expert,
    I am using scenario as following:
    ABAP proxy -> xi -> soap receiver -> webservice
    in sxmb_moni, the message runs ok. but in RWB, there are some error in CC monitor.
    2007-07-07 11:33:54 Success SOAP: continuing to response message e305dd90-2c3a-11dc-95af-0015c5f7cd3b
    2007-07-07 11:33:54 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
    2007-07-07 11:33:54 Success SOAP: sending a delivery error ack ...
    2007-07-07 11:33:54 Success SOAP: sent a delivery error ack
    2007-07-07 11:33:54 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
    2007-07-07 11:33:54 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
    2007-07-07 11:33:54 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors.
    2007-07-07 11:33:54 Success The asynchronous message was successfully scheduled to be delivered at Sat Jul 07 11:38:54 CST 2007.
    2007-07-07 11:33:54 Success The message status set to WAIT.
    What is the problem? and how can I deal with to identify the problem?

    hi
    Go through this links
    Check out these threads..
    RFC -> XI -> External web service
    How to resolve this RFC_adapter_sender to SOAP_adapter_receiver Exception?
    Why getting "DeliveryExcetion" in SOAP->XI->RFC scenario?
    You may refer these fallowing weblogs
    /people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
    Thanks & Regards
    Sridhar.Bommireddy

  • SOAP sender adapter and XI adapter reusablity

    Hi,
    We are having good amount of interfaces using SOAP sender and XI Adapters (WS to Proxy scenarios).
    My question is :
    we can make reuse of Sender SOAP and Rcvr XI adapters in all scenarios.
    If we reuse these adapters in all our interfaces what are the limitations and any problems we may face in future?
    Replies will be highly helpful.
    Thanks
    Kishore
    Edited by: kishore kumar on Jan 21, 2010 7:23 PM

    SOAP sender depends on the Sender Message Interface and Namespace (in versions lower than SAP PI7.1) so if your scenarios satisfy these parameters then you can (rather should) re-use the channels.
    Similarly for the PROXY receiver channel....if the proxy is being hosted on one particular receiver SAP ECC system then the details in all the channels that you create will be the same and wont be recommended....hence even this can be re-used.
    There is no issue in re-using the channels....just that you should closely monitor these channels to ensure that they do not stop/ fail causing all the involved interfaces to stuck.
    Regards,
    Abhishek.

  • Defalt VI Parameters in SOAP Sender Channel Config

    Hi all,
    I have configured soap sender channel with Default XI Parameters as * for both Interface name space and Interface name.
    SOAP adapter sends the message with * as the interface namespace and interface and fails with the error "No receiver could be determined".
    Why is SOAP adapter is using the default XI parameters from the channel instead of the parameters passed with the SOAP message.
    I could make this work specifying the Default XI parameters with correct name space and interface, but my problem is I have 2 different interfaces from the same service and cannel, I don't want to create a separate channel for each of the interfaces.
    Please help.

    Hi Pratat,
    you have to set the
    Use Query String to true and the adapter will take the service/interface data from the query string instead of the Default XI Parameters
    Regards,
    Nicolá

  • Using custom http headers in SOAP sender adapter

    Hi,
    my problem is exactly the same as reported [here|Re: SOAP Sender - Extract Header Values;] and [here|Variable Transport Binding - Soap Sender;
    Basically I'd like to send through the soap sender adapter some custom http headers. I check the necessary options in the advanced tab (set adapter-specific message attributes and variable transport binding), and in the variable header one I put x-StoreCode, which is the same http header I send to PI.
    But I won't see anything in the dynamic configuration section when the message is persisted in PI.
    Very surprised that I've seen this issue is a common problem others have faced before without success.
    Thanks!

    Hi Michal,
    the extra info I'm trying to send separated from the message is an http header, not part of the query string.
    If I incorporate the extra info as a parameter to the query string like this, for example:
    http://host:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=S1&receiverParty=&receiverService=&interface=Int&interfaceNamespace=urn:test&x-StoreCode=13&nosoap=true
    Then I can see the value in the dynamic configuration section:
    <SAP:Record namespace="http://sap.com/xi/XI/System/SOAP" name="SQueryString">senderParty=&senderService=S1&receiverParty=&receiverService=&interface=Int&interfaceNamespace=urn:test&x-StoreCode=13&nosoap=true</SAP:Record>
    But what I'm trying to do shoould be possible, according to sap help:
    http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm (section Define Adapter-Specific Message Attributes)

Maybe you are looking for