<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: Proxy to HTTP_AAE / SOAP? in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410282#M47964</link>
    <description>&lt;P&gt;Thanks Vadim. Now I am not getting that error. &lt;/P&gt;
  &lt;P&gt;But I am getting different error in mapping, so I got another question - Do I need to use only the HTTP_AAE adapter or can I use any other adapter? If yes please advice me for the same.&lt;/P&gt;</description>
    <pubDate>Mon, 17 Jul 2017 21:52:38 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2017-07-17T21:52:38Z</dc:date>
    <item>
      <title>Proxy to HTTP_AAE / SOAP?</title>
      <link>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaq-p/410280</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;
  &lt;P&gt;My requirement is Sender is Proxy and for the receiver I have "HTTPS" url (eg. &lt;A href="https://xxx.xxxxx.com/xotp/stage/xxxx)" target="test_blank"&gt;https://xxx.xxxxx.com/xotp/stage/xxxx)&lt;/A&gt; so I tried using HTTP_AAE adapter as receiver. I have used normal structure for sender data type and for target I have a string (1 field) datatype. For target I am passing the entire XML and values into this string field using a custom UDT. I am using SAP PO 7.4 single stack.&lt;/P&gt;
  &lt;P&gt;I am getting this error when executing. "&lt;EM&gt;MP: exception caught with cause com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SENDING_HTTP_REQUEST-Message Processing Failed. Reason : java.net.UnknownHostException: &lt;A href="https://xxx.xxxxxxxx.com" target="test_blank"&gt;https://xxx.xxxxxxxx.com&lt;/A&gt;&lt;/EM&gt;"&lt;/P&gt;
  &lt;P&gt;But ping channel for the receiver communication channel is working fine. Also the certificates are also verified.&lt;/P&gt;
  &lt;P&gt;Attached is the HTTP_AAE receiver communication channel screen shot. &lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/53406-http-aae.png" /&gt;&lt;/P&gt;
  &lt;P&gt;Can I achieve it using HTTP_AAE adapter or SOAP adapter?&lt;/P&gt;
  &lt;P&gt;Thanks in Advance,&lt;/P&gt;
  &lt;P&gt;RVR&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jul 2017 16:13:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaq-p/410280</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-07-17T16:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: Proxy to HTTP_AAE / SOAP?</title>
      <link>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410281#M47963</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
  &lt;P&gt;Parameter 'Target Host' in HTTP_AAE receiver channel configuration shall not contain protocol scheme (http or https), it shall only contain IP address / DNS name / alias of the called remote server.&lt;/P&gt;
  &lt;P&gt;Regards,&lt;/P&gt;
  &lt;P&gt;Vadim&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jul 2017 16:20:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410281#M47963</guid>
      <dc:creator>vadimklimov</dc:creator>
      <dc:date>2017-07-17T16:20:04Z</dc:date>
    </item>
    <item>
      <title>Re: Proxy to HTTP_AAE / SOAP?</title>
      <link>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410282#M47964</link>
      <description>&lt;P&gt;Thanks Vadim. Now I am not getting that error. &lt;/P&gt;
  &lt;P&gt;But I am getting different error in mapping, so I got another question - Do I need to use only the HTTP_AAE adapter or can I use any other adapter? If yes please advice me for the same.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jul 2017 21:52:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410282#M47964</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-07-17T21:52:38Z</dc:date>
    </item>
    <item>
      <title>Re: Proxy to HTTP_AAE / SOAP?</title>
      <link>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410283#M47965</link>
      <description>&lt;P&gt;There is variety of HTTP based adapters in PI/PO systems - HTTP / HTTP_AAE, WS / WS_AAE, SOAP, REST, OData being some of them that are commonly used. The choice of the adapter is mainly driven by type of service on the receiver side that you need to consume - namely, which web service standards and data formats it is built on and supports. Hence, it is hardly possible to suggest any specific adapter without knowledge about details of the called web service.&lt;/P&gt;
  &lt;P&gt;Regards,&lt;/P&gt;
  &lt;P&gt;Vadim&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2017 10:21:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410283#M47965</guid>
      <dc:creator>vadimklimov</dc:creator>
      <dc:date>2017-07-18T10:21:25Z</dc:date>
    </item>
    <item>
      <title>Re: Proxy to HTTP_AAE / SOAP?</title>
      <link>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410284#M47966</link>
      <description>&lt;P&gt;Vadim,&lt;/P&gt;
  &lt;P&gt;Here is the complete picture of my requirement. I only have a "https" url and which is working fine in ECC system, they are using the REST classes and building the xml and sending it across to receive the token as output. Now they dont want to use the existing process instead they want to go through PO. They didn't mention about the adapter this is the problem. So I want to send the data in their xml format and should receive the output. The current process is very simple they use the URL and creating the below xml with data and sending it across.&lt;/P&gt;
  &lt;P&gt;Request Structure:-&lt;/P&gt;
  &lt;P&gt;&amp;lt;?xml version="1.0" encoding="utf-8" ?&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;payment&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;user&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;login-id&amp;gt;&amp;lt;/login-id&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;password&amp;gt;&amp;lt;/password&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;/user&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;header&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;account-number&amp;gt;&amp;lt;/account-number&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;auth-token1&amp;gt;&amp;lt;/auth-token1&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;payment-amount&amp;gt;18.31&amp;lt;/payment-amount&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;payment-type-code&amp;gt;&amp;lt;/payment-type-code&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;check-duplicates&amp;gt;&amp;lt;/check-duplicates&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;/header&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;payment-method-category&amp;gt;CC&amp;lt;/payment-method-category&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;customer&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;first-name&amp;gt;&amp;lt;/first-name&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;last-name&amp;gt;&amp;lt;/last-name&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;day-phone-nr&amp;gt;&amp;lt;/day-phone-nr&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;address&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;zip-code&amp;gt;&amp;lt;/zip-code&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;country&amp;gt;US&amp;lt;/country&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;/address&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;/customer&amp;gt;&lt;/P&gt;
  &lt;P&gt;&amp;lt;/payment&amp;gt;&lt;/P&gt;
  &lt;P&gt;So which adapter would be a right choice?&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2017 14:08:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410284#M47966</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-07-18T14:08:26Z</dc:date>
    </item>
    <item>
      <title>Re: Proxy to HTTP_AAE / SOAP?</title>
      <link>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410285#M47967</link>
      <description>&lt;P&gt;It is very unlikely somebody from ERP or receiver system will suggest which adapter you need to use - this is purely PI architect or developer's decision.&lt;/P&gt;
  &lt;P&gt;Given information you provided, you still have multiple adapters to choose from since quite a lot of built-in adapters support XML data format - for example, SOAP adapter does so since SOAP message is entirely based on XML (when you need to consume SOAP service), REST adapter supports XML (although in many use cases for REST adapter predominant data format is JSON), as well a XML can be passed in HTTP body of the message when using HTTP_AAE adapter.&lt;/P&gt;
  &lt;P&gt;I would suggest you getting in touch with somebody from receiver system side / service provider, and query them about what type of service they expose. Or alternatively, get in touch with your ERP team to gather more details about how they consume the remote service - this will also bring you extra useful details that can be used when making decision on adapter type selection in PI.&lt;/P&gt;
  &lt;P&gt;Regards,&lt;/P&gt;
  &lt;P&gt;Vadim&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2017 15:48:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410285#M47967</guid>
      <dc:creator>vadimklimov</dc:creator>
      <dc:date>2017-07-18T15:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: Proxy to HTTP_AAE / SOAP?</title>
      <link>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410286#M47968</link>
      <description>&lt;P&gt;I have used HTTP_AAE adapter, Message Transformation Bean and Java Mapping to resolve the issue. &lt;/P&gt;</description>
      <pubDate>Wed, 16 Aug 2017 15:47:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/proxy-to-http-aae-soap/qaa-p/410286#M47968</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-08-16T15:47:50Z</dc:date>
    </item>
  </channel>
</rss>

