Clarification Regarding SOAP adapter

Hi,
   When we use webservice. do we need to go for BUSINESS SERVICE or Third Party BUSINESS SYSTEM. Please anybody can me help me regarding this.
Thanks,
dhanush.

Hi,
Go thru this blog.
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1 by Shabarish Vijayakumar
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2 by Shabarish Vijayakumar
trouble shooting rfc/soap -
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009 - search this to find all abt various parameters
Hope it helps..
Kumar.S

Similar Messages

  • Regarding SOAP Adapter

    Hi All,
    Can anybody explain me about the SOAP adapter as when exactly SOAP adapter is used ??
    Its flow taking any sampel example .
    pls reply me ASAP .
    I have got a reqt to work on .
    pls mail me asap .

    HI,
    Apart from the above explination.
    See the below links for more details..
    SOAP Adapter
    Consuming XI Web Services using Web Dynpro – Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
    Consuming XI Web Services using Web Dynpro – Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d7349b6-0901-0010-ddbe-ec43178a61ff
    /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
    /people/kevin.liu/blog/2006/04/12/wsdl-11-binding-extension-for-soap-12
    yes it will be possible, see below links
    /people/thomas.jung3/blog/2005/01/11/publishing-abap-webservices-to-an-external-uddi-server
    /people/sap.user72/blog/2005/11/17/xi-how-to-publish-wsdl-generated-from-xi-to-uddi
    /people/thomas.jung3/blog/2005/05/25/sap-teched-2005--shameless-plug
    Troubleshooting SOAP Message - XI - /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
    Troubleshooting - RFC and SOAP scenarios-/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
    Regards
    Chilla..

  • Plain HTTP Adapter vs SOAP Adapter with regards to SSL

    Hi,
    I need to setup communication channles within XI to send and receive secure xml. I am confused after reading the XI documentation and the some of the discussion forums on SDN.
    Can anyone clarify the following:
    1) Does the plain HTTP Adapter support SSL? According to the XI documentation is does NOT? Have I miss read it?
    2) This being the case, the only way to send and receive secure XML is to use the XI/SOAP Adapter?
    Thanx for your help.
    Cheers
    Yackeen

    Hi Yackeen,
    no, that's not true. The plain HTTP Adapter supports SSL. No problem.
    Regards,
    Udo

  • Regarding authentication in sender soap adapter

    how to do basic authentication in case of sender side soap adapter

    Hi
    To do the Basic Authentication in the sender soap adapter u have to provide the user name and the password of ur XI server.
    Thanks
    Rinku

  • Clarification regarding loadbalancing in RFC recever adapter

    Hi,
    what is the loadbalancing in RFC
    when do we go with or without Load Balancing option in RFC?
    SOAP action in SOAP adapter.
    Thanks
    dhanush

    Dhanush,
    If you have more than one instance of server for your Application system you should use Load balancing in that case.
    Sometime because of the heavy load on the sever they include more than one server to handle the load...where each request would be randomly assign to the available server. But they comes under one application system.
    So when you have multiple instace and if they have creates group to identify them use Load Balancing option.
    hope this will help you,
    Nilesh

  • Error while invoking the ABAP Proxy via SOAP Adapter

    Hi,
    My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
    SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
    Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
    SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
    With this approach, i am encountering the below error message
    2009-05-29 12:17:55 Error Adapter Framework caught exception: null
    2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
    Any ideas on the above errror message? Any pointers or inputs will be appreciated.
    Thanks,
    Vinayak Kamath

    > 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
    > 2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
    This is a generic error message which does not have any information about the error which has occurred.
    Do you see any error messages in the SOAP client?
    Regards
    Stefan

  • Error in while calling a Soap Adapter using the UDF

    hi,
    i am trying to make a call to Soap Adapter using a UDF.
    The code of the UDF is as follows :
    InputStream isPayloadStream = null;
    AbstractTrace trace= container.getTrace();
    String sService="Business Component";
    String sChannelName="Soap Channel(Sender)";
    SystemAccessor accessor=null;
    trace.addInfo("entered UDF");
    StringBuffer sb = new StringBuffer(" ");
    trace.addInfo("creating the reference file");
    sb.append("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n");
    sb.append("<ns0:MT_123082_UDF xmlns:ns0=\"http//infosys.com/pi/projects/png/n1\">\n");
    sb.append("<INTERCHANGECONTRLNOS>" + var1 + "</INTERCHANGECONTRLNOS>");
    sb.append("<PGPARTNERID>"var2"</PGPARTNERID>""\n""</ns0:MT_123082_UDF>");
    trace.addInfo("trigerring the SOAP channel ");
    try{
    Channel channel = LookupService.getChannel(sService,sChannelName);
    accessor = LookupService.getSystemAccessor(channel);
    isPayloadStream = new ByteArrayInputStream((sb.toString()).getBytes());
    trace.addInfo("creating the xml payload ");
    XmlPayload payload = LookupService.getXmlPayload(isPayloadStream);
    Payload result=accessor.call(payload);
    catch (Exception e){
    trace.addInfo(e.getMessage());
    finally{
    if ( accessor !=null) {
    accessor.close();
    return " ";
    The above code is throwing an error while end to end testing.
    the scenario is such,while graphical mapping a UDF will be used, which will create an Xml payload, and send this payload to another SOAP to file scenario.
    The error in the sxmb_moni is:  "Error when calling an adapter by using the communication channel CC_123085_UDF_SOAP_OUT (Party: , Service: BC_123082_REMADV_D96A, Object ID: fa9c6ee15efc30c68ec34b08034d87d1) XI AF API call failed. Module exception: 'failed to set up the channel fa9c6ee15efc30c68ec34b08034d87d1'. Cause Exception: 'Channel stopped by administrative task.'."
    Please can anyone suggest how this error can be rectified.
    regards,
    Meenakshi

    Hi,
    i have checked the communication channel and the XML. The following error occurs everytime i try to run the scenario.
    Error:
    Error when calling an adapter by using the communication channel CC_123082_UDFRECEIVER_SOAP_IN (Party: , Service: BC_123082_REMADV_D96A, Object ID: 2a895589066d30d4b2686e9d3a8d4c8d) XI AF API call failed. Module exception: 'SOAP Error'. Cause Exception: 'SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request'
    Please let me know how this error can be resolved.
    Regards,
    Meenakshi

  • Invoking a Webservice using a SOAP adapter

    Hi,
          I have the following scenario.
    SAP ABAP outbound proxy <-> SAP XI <--> External webservice.
    The above call is a synchronous call from SAP R/3 and a receiver soap adapter is configured for the Webservice.
    I am getting the following error messages when I try to run the scenario.
    1)ADAPTER.SOAP_EXCEPTION.
    2)<SAP:AdditionalText>
    soap fault: Server did not recognize the value of HTTPHeaderSOAPAction
    </SAP:AdditionalText>
    What could be the possible reasons for the error message?
    In the target URL of the soap adapter I am specifying the path till .asmx.
    Thanks,
    Leo

    Hi,
    There are 2 pieces of data that must be provided in the SOAP receiver adapter.  Both of them can be obtained from the WSDL of the soap service provider.
    1.  Target URL, which can be obtain from the attribute "location" of the "address" element in the WSDL.
    2.  SOAP Action, which can be obtain from the "soapAction" attibute of the "operation" element in the WSDL.
    Regards,
    Bill

  • Exception while posting a message using SOAP adapter

    Hi
    We are getting the following message while posting a SOAP request through SOAP adapter through Http Client. The error message is
    <SAP:Error>
    <SAP:Category>XIAdapterFramework</SAP:Category>
    <SAP:Code>MESSAGE.GENERAL</SAP:Code>
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>
    </SAP:Error>
    Please help in this regard.
    Regards
    Ramesh

    Dear Gopal,
             I am trying from HTTP->WEB SERvice (R/3 system)
    I have created a webservice from RFC.
    Receiver Adapter type : SOAP
    USer authentification provided
    URL provided. i picked from wsdl file
    i am getting this error
    com.sap.aii.af.ra.ms.api.DeliveryException : invalid content text/html.
    I hope u trouble shooted this kind of error.
    can u provide me some clues.
    regards
    chandra
    Message was edited by:
            chandra shekar dasari

  • WHAT IS THE BEST WAY TO CREATE AN XSD FILE (TO BE USED BY SOAP ADAPTER)

    Dear friends
    I have a simple scenario.
    OUTBOUND DATA  -->  SOAP ADAPTER  --> ( XI )  -->  RFC ADAPTER  --> INBOUND DATA
    The XML file that I got from mapping area of IR (Design) is as follows
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_NAME_SOURCE xmlns:ns0="http://test3.com">
       <FIRSTNAME>DAVE</FIRSTNAME>
       <LASTNAME>SMITH</LASTNAME>
    </ns0:MT_NAME_SOURCE>
    If you notice, there are only 2 fields.
    I need to create an XSD file and import it as an external object, which I can use for SOAP Adapter.
    Which is the best way to create it.
    Also, I need to know if there is any step by step of sending a message from XML SPY. I have downloaded this software, but am not able to undertand how to use this.
    Hope to hear from any experts on this forum.
    Thanks in advance
    Ram

    Hi Ram,
    See the below blog..
    It shows how to send SOAP message using XML Spy.
    It also shows how to generate wsdl.
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
    Regards,
    Sumit

  • The difference between SOAP adapter and WS adapter in PI 7.1

    Hello all,
    can anybody explain what is the main difference between SOAP adapter and WS adapter in PI 7.1?
    I have checked this [link|http://help.sap.com/saphelp_nwpi71/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm]
    but was not able to find the real difference.
    Or better, what can I do with WS adapter I can't do with SOAP adapter? What are their advantages/disadvantages?
    Thank you all, Igor.

    In addition to RM, ws adapter also support other ws standard like SAML which is not available in SOAP adatper. Beside:
    if your sender or receiver is SAP system, you can also monitor the message in the sender/receiver in addition to the PI box. This is a very good thing, because sometime the MONI in PI shows nothing wrong, but the MONI in your receiver will show you error message that's only related to the receiver system.
    However, if you define ws sender CC, and your ws client doesn't support RM, you will have issue sending ws request.
    And ws CC will generate ws runtime in PI box, if your configuration is wrong (like user name and password not correct), even if you correct it, the ws runtime sometime won't be regenated based on the correction. In this case you need to delete the ws CC/agreement, and re-create it with all correct information.
    Beside make sure your basis team configured the PI system properly regarding ws. If not, you will have lot of pain to figure the problem which was my case.
    Jayson

  • Sender SOAP Adapter

    Hi,
    Scenario is Sender SOAP and Receiver (Server Proxy) .
    Integrated the ESS applications on .net portal using soap adapter..example salary slip, ctcview....
    If we give input as empno to soap adapter it will give you salary details back to .net portal.
    All this functional;ity are working fine..
    Now i need to check the authorization to acess this soap request. As this webservice works for all the employess in the organazation. but i need to restrict for few employees. Is there any authorization check in XI as it is there in ESS.
    If so how to use that . Now in .net portal they are useing the same user name and pwd for all the soap requests.
    Regards
    Vijay
    Edited by: vijay Kumar on May 25, 2010 11:18 AM

    Michal
    Hopefully I can help you for once!
    You can set the SOAP action to debug in the Java Admin Console.
    Set com.sap.aii.af.mp.soap and com.sap.aii.messaging set to DEBUG
    Set location
    &#61680;     Services
    &#61680;     Log Configurator
    &#61680;     Locations
    &#61680;     Choose com.sap.aii.messaging
    &#61680;     Assign Severity Debug
    See https://service.sap.com/sap/support/notes/856597 for more info...
    This note has a an attachment: tcpgw.zip for tracing the whole message...

  • Error in Receiver Soap Adapter for Google API

    Hi,
    I am working on HTTP-XI-Soap scenario which on the receiver side calls google API for spell check.
    I get the following error : <b>No Deserializer found to deserialize a ':key' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.</b>
    However if I try calling the webservice individually using SOAP Client it works fine and do get desired response.The soap message that is sent by the client to the target URL is :
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:GoogleSearch" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <soapenv:Body>
          <urn:doSpellingSuggestion soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
             <key xsi:type="xsd:string">qXWD4x1QFHIo/dePqlYOLwT7kMmkv80E</key>
             <phrase <b>xsi:type="xsd:string"</b>>Bratney</phrase>
          </urn:doSpellingSuggestion>
       </soapenv:Body>
    </soapenv:Envelope>
    However if i remove the "xsi:type="xsd:string" part from the element 'phrase' and 'key' it returns the same error as it does while using with XI.
    Hence I am assuming that that the outgoing soap message elements need to have the above highlighed attribute.
    Now I want to have this attribute(xsi:type="xsd:string) in the soap message that is sent from XI.
    My question is , Is there any setting using which I can add the attributes in the above form to the outgoing message from XI.I do not want to use a adapter Module.
    Thanks & Regards,
    Sidharth

    Hi Sidharth,
    You post here the soap message that is sent by the client to the target URL, but did you look to the soap message that is sent by XI?
    Try the AF monitor http://<host>:<j2ee-port>//MessagingSystem/monitor/monitor.jsp?
    Because XI soap adapter doesn't support all tags of wsdl rpc-based, we need to adjust them...
    Look to the SOAP FAQ (SAP note number 856597) under question "Can I convert an RPC styled WSDL to a document styled WSDL?"... Look at last but one paragraph ;o)
    So, you need to change this attribute to one that it is compatible...
    Go to http://service.sap.com/xi > Media Library > Documentation and there you will find this xls document -> SAP XI 3.0 (SP11) - Supported XML Schema and WSDL (EN) in this document you have all the compatible elements of wsdl for XI.
    One more thing, you can adjust your soap request and change or add the required tags You can do it with xslt-mapping or create your won data types in XI without import the WSDL generated by google. 
    Hope it helps,
    Ricardo.
    Message was edited by: Ricardo  Quintino

  • HTTP Header fields in SOAP adapter

    Hi All,
      I have a scenario IDoc to SOAP adapter. In which my receiver given the details as
    URL : https://b2b.ecsc.us.gxs.com/invoke/GXSGateway:receiveCTE
    Header Name:             Header Value
    Ent-sender                xxxx
    Ent-receiver              yyyyy
    Ent-APRF                 zzzzz
    Ent-filename             (not sure what data need to give)
    1. I request you to let me know where I need to give these headername and hader values in soap adapter. 
    2. my client require file as an attachment.  Please let me know how I need to send the payload as an file and where the name need to be given in the header name (Ent-filename).
    Currently I used  MessageTransformBean to conver my XML to text structure(flatfile structure).
    Please let me know if any more details required
    Regards,
    Dhill

    Was out for lunch break..
    Juz Rechecking
    Transport Protocol : HTTP
    Message Protocol: Soap 1.1
    Adapter Engine -> Adapter Engine on the Integration Server
    Connection Parameters
    Target URL - > https://b2b.ecsc.us.gxs.com/invoke/GXSGateway:receiveCTE
    Sure about no sever authentication required  and they are not using any HTTP proxy for webservice >????
    Conversion Parameters
    Do Not Use SOAP Envelope -> Unchecked
    Keep Headers -> Checked.
    Keep Attachments -> Unchecked
    Use Encoded Headers -> Unchecked
    Use Query String -> not so sure might be Unchecked
    <b>Authentication Keys</b>
    If authentication is required for the receiver system, you can enter a password and a confirmation for each key value. This means that you do not need to write passwords in the enhanced message header.
    If you want to specify or display authentication keys, select View Authorization Keys.
    You can enter and confirm passwords for each authentication key value (TAuthKey or TproyxAuthKey).
    Try once sending the message with Adapter-Specific Message Attributes
    Unchecked. See if there is a hit.I knw itz not req but juz testing.
    Yeah adapter stat must be active.
    Last thing need to go through the whole scenario.
    <b>Cheers,
    *RAJ*
    *REWARD POINTS IF FOUND USEFULL*</b>

  • HTTP Header fields in SOAP adapter - Part 2

    Hi All,
    With regards to my previous thread HTTP Header fields in SOAP adapter
    my header issue is solved and hence I have closed the thread but still I am not able to make the connection successful. The new problem is below
    My vendor requirement is to specify the header as "Ent-sender" but when we give the same in XI in communication channel it automatically convets into uppercase "ENT-SENDER".  Due to case-sensitive in vendor server the connection is not gettingestablished.
    Please help me out how to solve the problem.
    <b>Note:</b> Sorry for the new thread as it was created due to new problem and also the previuos thread is already too long.
    Regards,
    Dhill

    Hi Neaves,
      Thank you, I jave seen the note and find the below solution will be some what realated to my prblem.
    <u><b>The nosoap mode lets the adapter send the XI payload directly without wrapping it in the SOAP envelope. Although the main use of this mode is to send some plain text content directly to some web server, one can use this mode to send their own SOAP message (e.g., with arbitrary headers) to an external web service (See related questions). In this case, the XI payload must be formatted in the SOAP envelope.
               To use the nosoap mode, the channel must be configured to use no SOAP envelope.</b></u>
    If yes, can you please let me know how to use nosoap mode otherise let me the other possibilities.  I am already using tcpg2.zip to trace the SOAP adapter in which it was confirmed that XI is changing the header automatically into CAPS whatever case we give,
    Regards,
    Dhill

Maybe you are looking for