Plain HTTP

Hi Experts,
  I have the scenarion where an external web application needs to send so some data in the format of String (field=value) separated by a delimeter through HTTP. Now Here I want to develop an interface where i have to catch the string and convert and then send as RFC and then have to send back the response as a string again only. I request you kindly suggest me furhter.

"HTTP to RFC" is a classic scenario to use PI. You can use java mapping to map the strings to the rfc parameters.
BR,
Winters

Similar Messages

  • R3- RFC- XI-Plain HTTP

    Hi,
    I have a scenario where R/3 sends IDoc's to our external system using XI plain HTTP adapter. My configuration works fine but, the only issue is , I need to parse through the payload XML, in order to determine the IDOC type at my external system http listener. Is there a way I can get this information passed in the HTTP header(Message Interface/IDOC name or any info) which I can then use to uniquely identify the incoming IDOC?
    Thanks
    Don

    Hi Don
    Did you check the following blog.. You can write info to header parameters while sending to the target.. Use the same while receiving to PI
    /people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping

  • How to transmit a file via plain https?

    Hello all,
    i have a scenario as follows:
    The Vendor has provided a URL ( say https://www.somesite.com ) and UserID/PWD to login to their site. Once logged in i need to select a directory and then upload a file.
    Can i use here the https adapter??
    And how i have to config the communicaton channel with the ssl and the directory?
    Is it possible to do this using a other XI adapter like the soap or other software?
    Please feel free to ask for more information if needed
    Many thanks for your help
    ilka

    Ilka,
    Go through the urls:
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1334 [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
    /people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
    Also to configure the Plain HTTP adapter:
    http://help.sap.com/saphelp_nw04s/helpdata/en/84/e8763c997fda50e10000000a11405a/frameset.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/84/e8763c997fda50e10000000a11405a/frameset.htm
    ---Mohan

  • Error while XI and xMII integration (Plain HTTP as sender)

    Dear Friends,
       I am doing the scenario XI and xMII integration. While sending the input file from plain HTTP adapter the result comes as follows in *sxmb_moni* :
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!-- Call Adapter -->
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    <SAP:Category>XIAdapterFramework</SAP:Category>
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
    <SAP:P1/>
    <SAP:P2/>
    <SAP:P3/>
    <SAP:P4/>
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: <xMII server name></SAP:AdditionalText>
    <SAP:ApplicationFaultMessage namespace=""/>
    <SAP:Stack/>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    In HTTP Client Adapter for XI 3.0 it is shown as follows:
    <SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL
    </SAP:Code>
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: <xMII server name> </SAP:AdditionalText></SAP:Error>
    Please show the way to rectify this error.
    Regards,
    Jagan.

    Dear Sudharshan,
       I'm doing the scenario which is in the following blog.
    /people/dhanabal.thangavel/blog/2008/02/07/xi-and-xmii-integration--part-1 ==> XI and xMII Integration - Part 1
    This is a synchronous one. So I set QOS as BE in Client Http Adapter for XI 3.0.
    Scenario is HTTP <--> XI <--> xMII
    The following errors are I found:
    1) In RWB -> Message Monitoring
    Status : Canceled with Errors
    Message Details:
    SOAP : call failed
    SOAP :error occured: java.net.UnknownHostException: <HOST>
    Exception caught by adapter framework: <HOST>
    Delivery of the message to the application using connection AFW failed, due to: <HOST>. Setting message to status failed
    The message status set to FAIL.
    Returning synchronous error message to calling application: <HOST>.
    2) Error coming in the Client Http Adapter for XI 3.0 as follows:
    *URL:*
    http://xxxxxx07:xx10/sap/xi/adapter_plain?namespace=http%3A//www.xxxxxxx.com/XIBatch3/10099/xMII_Integration&interface=xMII_Integration_Sync_Outbound&service=BS_BATCH3&party=&agency=&scheme=&QOS=BE&sap-user=xxxxx&sap-password=xxxxx&sap-client=xx1&sap-language=EN
    *Result:*
    <SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL</SAP:Code><SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException:<HOST></SAP:AdditionalText></SAP:Error>
    *Input XML file:*
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:XacuteRequest xmlns:ns1="http://www.lighthammer.com/Xacute">
       <ns1:LoginName/>
       <ns1:LoginPassword/>
       <ns1:InputParams>
          <ns1:ProductName>ProductA1</ns1:ProductName>
       </ns1:InputParams>
    </ns1:XacuteRequest>
    *WSDL file (Which is generated using the xMII transaction):*
    <?xml version="1.0" encoding="UTF-8"?><definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.lighthammer.com/Xacute" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.lighthammer.com/Xacute">
        <!-- Types -->
        <types>
            <s:schema elementFormDefault="qualified" targetNamespace="http://www.lighthammer.com/Xacute">
                <s:complexType name="InputParams">
                    <s:sequence id="InputSequence">
                    <s:element maxOccurs="1" minOccurs="0" name="ProductName" type="s:string"/></s:sequence>
                </s:complexType>
                <s:element name="XacuteRequest">
                    <s:complexType>
                        <s:sequence>
                            <s:element maxOccurs="1" minOccurs="0" name="LoginName" type="s:string"/>
                            <s:element maxOccurs="1" minOccurs="0" name="LoginPassword" type="s:string"/>
                            <s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:InputParams"/>
                        </s:sequence>
                    </s:complexType>
                </s:element>
                <s:complexType name="Rowsets">
                    <s:sequence>
                        <s:element maxOccurs="1" minOccurs="0" name="FatalError" type="s:string"/>
                        <s:element maxOccurs="1" minOccurs="0" name="Messages" type="s0:Messages"/>
                        <s:element maxOccurs="1" minOccurs="0" name="Rowset" type="s0:Rowset"/>
                    </s:sequence>
                    <s:attribute name="StartDate" type="s:dateTime" use="required"/>
                    <s:attribute name="EndDate" type="s:dateTime" use="required"/>
                    <s:attribute name="DateCreated" type="s:dateTime" use="required"/>
                    <s:attribute name="Version" type="s:string"/>
                </s:complexType>
                <s:complexType name="Messages">
                    <s:sequence>
                        <s:element maxOccurs="unbounded" minOccurs="0" name="Message" type="s:string"/>
                    </s:sequence>
                </s:complexType>
                <s:complexType name="Columns">
                    <s:sequence>
                        <s:element maxOccurs="unbounded" minOccurs="0" name="Column" type="s0:Column"/>
                    </s:sequence>
                </s:complexType>
                <s:complexType name="Column">
                    <s:attribute name="Name" type="s:string" use="required"/>
                    <s:attribute name="Description" type="s:string" use="required"/>
                    <s:attribute name="SourceColumn" type="s:string" use="required"/>
                    <s:attribute name="MinRange" type="s:double" use="required"/>
                    <s:attribute name="MaxRange" type="s:double" use="required"/>
                    <s:attribute name="SQLDataType" type="s:int" use="required"/>
                </s:complexType>
                <s:complexType name="Rowset">
                    <s:sequence>
                        <s:element maxOccurs="1" minOccurs="1" name="Columns" type="s0:Columns"/>
                        <s:element maxOccurs="unbounded" minOccurs="0" name="Row" type="s0:Row"/>
                    </s:sequence>
                </s:complexType>
                <s:complexType name="Row">
                    <s:sequence id="RowSequence">
                    <s:element maxOccurs="1" minOccurs="1" name="Quantity" type="s:long"/><s:element maxOccurs="1" minOccurs="1" name="ProductName" type="s:string"/></s:sequence>
                </s:complexType>
                <s:element name="XacuteResponse">
                    <s:complexType>
                        <s:sequence>
                            <s:element maxOccurs="1" minOccurs="0" name="Rowsets" type="s0:Rowsets"/>
                        </s:sequence>
                    </s:complexType>
                </s:element>
            </s:schema>
        </types>
        <!-- Messages -->
        <message name="XacuteSoapIn">
            <part element="s0:XacuteRequest" name="parameters"/>
        </message>
        <message name="XacuteSoapOut">
            <part element="s0:XacuteResponse" name="parameters"/>
        </message>
        <!-- Ports -->
        <portType name="XacuteWSSoap">
            <operation name="Xacute">
                <input message="s0:XacuteSoapIn"/>
                <output message="s0:XacuteSoapOut"/>
            </operation>
        </portType>
        <!-- Bindings -->
        <binding name="XacuteWSSoap" type="s0:XacuteWSSoap">
            <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
            <operation name="Xacute">
                <soap:operation soapAction="http://www.lighthammer.com/Xacute" style="document"/>
                <input>
                    <soap:body use="literal"/>
                </input>
                <output>
                    <soap:body use="literal"/>
                </output>
            </operation>
        </binding>
        <!-- Service mapping -->
        <service name="XacuteWS">
            <port binding="s0:XacuteWSSoap" name="XacuteWSSoap">
                <soap:address location="http://<XMII_SERVER_NAME>/Lighthammer/SOAPRunner/Jagan/SDN_Fetch_Product_Qty"/>
            </port>
        </service>
    </definitions>
    Regards,
    Jagan.

  • Using extra attributes in plain Http Adapter

    Hi All,
    I am using a Plain HTTP Adapter to send messages to XI. This is working fine but i'm facing a problem with HTTP variables.
    I need to send a flag as an http variable that identifies the message as a new message or not. It's important for me that this variable is reachable in the Receiver Determination so i can create a routing rule based on that. I've read this help from sap (<a href="http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm">Configuring the Sender Plain HTTP Adapter</a>), but i couldn't find a place to set the "Adapter-Specific Message Attributes".
    Thanks a lot for any help.
    Regards,
    Leonardo Tayt-son

    In your Sender HTTP Adapter, check out for "Adapter-Specific Message Attributes" section (usually, it's the last section). Mark the "Use Adapter-Specific Message Attributes" checkbox. Then, mark "Apply URL Parameters" checkbox and enter a name for Parameter 1 (for example, New).
    Then, your incoming http URL shoud be something like http://<application_hostname>?New=true .
    And in your receiver determination, go to condition editor for each Business System, and enter expression editor for left expression. Check "Context Object" and select "URLParamOne" parameter from "http://sap.com/xi/XI/System/HTTP" namespace. For the right expression, use the value you want.
    Them you can use your condition like
    If (URLParamOne = true) send to BS 1
    If (URLParamOne = false) send to BS 2
    Regards,
    Henrique.

  • Problem with plain http adapter on XI 2.0

    Hi all,
    i have a problem setting up proper communication between XI 2.0 and PI 7.0 system using plain http adapter.
    Regardless of what i pass as url argument, i always receive the following error message:
    HTTP-Server Code 500 Reason Internal Server Error Explanation URL-Parameter namespace (Sender Interface-namespace) is missing (see first link)
    SXMB_MONI Trace:
    [http://image-upload.de/image/Rv3NeE/77c11c84fc.jpeg]
    Configuration:
    [http://image-upload.de/image/5Z2Gwr/90c19f2074.jpeg]
    [http://image-upload.de/image/hGrzQL/559bf5e566.jpeg]
    [http://image-upload.de/image/2WqCqz/7513a1a366.jpeg]

    Hi,
    the namespace of the inbound interface in the interface determination was missing. So now it kind of works. But we still have the problem, that we are not able to pass parameters via URL, the XI 2.0 just ignores them.
    Is there a way to enhance the url by using the Header Fields tab. Can you give me an example for the valid params?
    Best Regards
    Sven

  • Configure plain http adapter for receiving message from an external system

    Hi,
    we use Pi/700.
    Now I have an external system and I have to use HTTP (plain) to send messages to XI (via plain http adapter).
    I have no experiences with HTTP!
    In the external system I can only configure "URL, Username, Password" for sending messages - that's all!
    What do I have to configure in XI (communication channel, abap-stack, java-stack,...)?
    I don't know the URL of my XI-system. Is there an transaction code to get this information?
    Why do I need a Username/Pasword?
    For testing I can use a "http-post test tool" I found here in this forum.
    Thank you all for any help!
    Regards
    Wolfgang

    Hi Hummel,
    In Exteranl System u have to use these values
    name="myhost"      value="xiserver"
    name="myport"      value="8000"
    name="mysystem"    value="XY_BSservice"
    name="myinterface" value="Order_out"
    name="mynamespace" value="urn:xi:hcl:powebapp"
    name="myqos"       value="BE"
    name="myclient"    value="300"
    name="myuser"      value="XYZCLNT"
    name="mypass"      value="xiuser"
    Here My system is the Business service created in Integration directory of XI, Interface is the one created in Integration Repository (This is Outbaound from external sys to XI)
    In XI U have to create
    Data Types : 1) Source Structure data type(from extenal sys)
                 2) Target structure (where u want to send from XI)
    Message Types : 2 with above DT's
    Message Interface: 1) Outbound, Async (Order_out)
                       2) Inbound , Async (for the target sys)
    Then Message mapping and Interface mapping as usual..
    And in ID u have to create 2 services one is XY_BSservice for sending system and the other is for receiving system...
    For sending system no communication channel required...
    Hope u will get idea from the above..
    Need any further u r welcome..
    Regards
    Sridhar

  • Plain HTTP sender adapter - Extract XML from request

    Hi all,
    I face a blocking issue in one of my B2B process.
    A marketplace must send Purchase orders to my customer with synchronous HTTPs requests.
    When messages arrive, we can see the following payload in incoming message (SXMB_MONI)
    %24xmldata=+%3C%3Fxmlversion%3D%221.0%22encoding%3D%22UTF-8%22%3F%3E%0D%0A-%3CMessage%3E%0D%0A-%3CHeader%3E%0D%0A%3CFrom%3EPA%3C%2FFrom%3E%0D%0A+%3CTo%3E83092SAC01%3C%2FTo%3E%0D%0A+%3CDocType%3ETAEPa-xCBL30PO%3C%2FDocType%3E%0D%0A++%3CDocID%3EP-20050502T125611-TATG310-
    %0D%0A++%3C%2FMessage%3E&submit=Soumission
    WebServer of B2B partners don't put XML data in HTTP body but as HTML form in .
    Is there a way in Plain http adapter to interpret such a request ?
    How can we decode hexadecimal sequence ?
    Thanks to help us.
    Jean-Charles

    Hi Jean-Charles !
    Unfortunately, I don't know any other option (based on XI; maybe you can develop some kind of external translator between your system and  XI's http adapter). The first link (although it is based on a escenario in the oposite direction) speaks about using java proxy instead of the http adapter.
    Here are some links:
    /people/thorsten.nordholmsbirk/blog/2006/08/06/use-a-java-proxy-instead-of-a-jca-adapter
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30572c6a-d311-2a10-99ab-f646ec3b5b12
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d06315a6-e66e-2910-039c-ba8bbbd23702
    https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=java+proxy&adv=false&sortby=cm_rnd_rankvalue&start=21#
    Regards,
    Matias
    ps: please award points if helpful.

  • How to pass the SIN using a plain http adapter in sender side.

    Hi all,
       How to pass the SIN(System Identification Number) using a plain http adapter in sender side.
    Regards,
    Venu.

    You can set it in a specific HTTP header (as explained here : http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm) ...
    Rgds
    Chris

  • SOAP Adapter and plain HTTP

    Hello,
    what does the option
    "Do not use SOAP envelope" on a SOAP SENDER adapter mean?
    Does this mean, that only the payload from the soap message is sent to the integration server? (without the soap envelope)
    Or does this mean, that I can send a XML message without SOAP envelope to the adapter from a HTTP client?
    Which means, I can use the SOAP adapter like the standard PLAIN HTTP adapter, but I can implement a adapter module!
    How knows more details on that?
    Best regards
    Werner Magerl

    Hi Werner,
    > When I use the option nosoap=true and the setting "Do
    > not use SOAP envelope" then it works.
    > So both things must be used together.
    > Is this correct?
    Yes. In your scenario you need both parameters.
    > What does this mean, that the XI message is created
    > after the self-defined modules?
    When you write a module for sender file-adapter, you have to deal with an XI message, as the file adapter fisrt creates the XI message, then calls the customer module.
    When you write a module for sender SOAP adapter, you have to deal with the incoming message, as the SOAP adapter first calls the customer module, then creates the XI message.
    > We just want to check the incoming XML message
    > against a local XSD. If there is an error against the
    > XSD, we do not want to receive the message, we want
    > to send back a specific HTTP error code.
    > This is the reason, why we just want to send a
    > plainHTTP message and not a SOAP Message.
    > In my opinion this should work?!
    > We do not want to use other modules.
    Yes, that should work.
    > Do you have experience on adapter modules for SOAP
    > adapter?
    No, I have no experience with adapter modules for sender SOAP adapter.
    Regards
    Stefan

  • Plain HTTP Adapter (XML return without namespace)

    Hello Experts,
    I'm very new at XI.
    I'm using XI 7.0 SP9.
    I wanna make interface with public website using plain HTTP adapter.
    The receiver url is
    http://openapi.naver.com/search?key=cdb64b1f218b55acbb73105b3b6f68a9&query=news&target=rank
    It returns XML like
    <?xml version="1.0" encoding="UTF-8" ?>
    <result>
    <item>
        <R1>
            <K>CHOICE</K>
            <S>new</S>
            <V>0</V>
        </R1>
      </item>
    </result>
    How I can specify namespace and root document type ?
    I learned that I can specify namespace and root document type in JDBC communication channel.
    In plain HTTP, Is there any possibility to specify namespace like JDBC?

    Ji,
    look at this it will help u.
    /people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-i
    /people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-ii
    /people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-iii
    /people/stefan.grube/blog/2006/10/23/testing-and-debugging-java-mapping-in-developer-studio
    /people/alessandro.guarneri/blog/2007/03/25/xi-java-mapping-helper-dom
    Sreeram Reddy

  • Plain HTTP adapter error: Bad Gateway, Proxy Error, please help !

    hello all,
    i have the following scenario:
    filesystem->file adapter->XI->plain http adapter-> receiver system.
    the following error occurred while calling plain http adapter:
    <SAP:Category>XIAdapter</SAP:Category>
    <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_Server</SAP:Code>
    <SAP:P1>502</SAP:P1>
    <SAP:P2>Bad Gateway</SAP:P2>
    <SAP:P3> Proxy Error</SAP:P3>
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>HTTP-Server Code 502 Reason Bad Gateway Explanation Proxy Error</SAP:Stack>
    A RFC-Destination with SSL is used in this scenario. Connection test to the destination machine is also succeeded. some files have been transported to the receiver system, yet without payload. data is lost.
    anyone has encountered such problem or anybody can tell me please how to solve this problem.
    thanks for your help
    regards

    Hi,
    I´ve found a SAP-Note concerning this error-message 692057
    There is the note 450226 gives an overview over error codes
    Probably below solution may help you.........
    As an administrator on your portal go to:
    System Configuration > Service Configuration >applications
    Under: com.sap.portal.ivs.httpservice > Services > Proxy
    If any proxy settings are configured you may end up with the problem, so you need to set the "nonProxyHosts" to include the trex host.
    After a restart the search was working normally again.
    Thanks
    Swarup

  • Plain Http adapter Monitoring with CCMS / Alerting framework

    Hello all,
    Can you explain me the optimal way to monitor process using plain http adapter (Sender AND Receiver).
    My goal is to push issue information as soon as possible to monitoring team (via CCMS) when the process is in error.
    During my tests, I ve had a lot of messages with ICM HTTP error 110 but Integration engine did not trigger any alert.
    Thanks for your help.

    Hi,
    Check this link for ICF trace.
    http://help.sap.com/saphelp_webas620/helpdata/en/2d/64d041e74911d6b2e400508b6b8a93/content.htm
    /people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
    /people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
    regards
    Aashish Sinha
    PS : reward points if helpful

  • Plain HTTP adapter fort HTTPs

    Hi guys,
    I use receiver plain HTTP adapter for sending SOAP request. Followinf parameters have tu be entred:
    Addressing Type: URL Address
    Target Host: <host>
    Service Number: <port>
    Path Prefix: <path>
    Then final address is generated:
    http://<host>:<port>/<path>
    It's working fine if I use http protocol.
    Now I need to send SOAP request to address https://<host>/<path>. I don't know number of port where SSL communication's running.
    Is it possible to enforce using of https protocol instead of http? Is it possible to enter empty port number? Or do you have any other idea how to pass around this problem?
    Thank you in advance for every advice!
    Regards
    Zbynek

    >>Is it possible to enforce using of https protocol instead of http?
    Instead of using URL Addressing option, you need to start using HTTP Destination option. An RFC destination type G should then be created where the similar details of hostname and path should be provided.
    >Is it possible to enter empty port number?
    Yes it could be empty, but you need to confirm it from the receiver party that would they be able to receive https request or not if no port is provided. This would depend upon the type of implementation they have at their end.
    Regards,
    Prateek

  • ERD not determined while using plain http adapter as Sender

    Hi All,
    ERD is not determined while using Plain Http Adpter as Sender.Is there any way to determine ERD table by using Http adapteras Sender?
    Regards,
    Rajesh

    Are you doing synchronous scenario???
    if yes should have leaving the value for the Software Component Version empty for Receiver determination .
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
    /people/jin.shin/blog/2007/12/11/sap-netweaver-process-integration-enhanced-receiver-determination-for-synchronous-scenarios

  • Using plain http adapter using (SIN)---Most urgent please help me

    Hi Experts,
    all we need to do is call the pipeline directly using plain http adapter using (SIN) and get the output from the pipeline to the local file folders. This can help developers to verify the interfaces that have been migrated to XI , to compare the out put results generated in XI with the original output captured using existing middle ware solutions.
    Could anyone help me out this Urgent

    Hi Experts,
    all we need to do is call the pipeline directly using plain http adapter using (SIN) and get the output from the pipeline to the local file folders. This can help developers to verify the interfaces that have been migrated to XI , to compare the out put results generated in XI with the original output captured using existing middle ware solutions.
    Could anyone help me out this Urgent

Maybe you are looking for