In this i expect that you have a better idea about this new adapter that comes up in PI 7.3.
OVERVIEW
HTTP AAE supports all the major functions of the ABAP HTTP Adapter, plus some industry standards.
Request Combinations
HTTP AAE supports different combinations of HTTP requests going through the HTTP POST/GET message protocols.
Form Submit Request
This is an HTTP POST request and the content type is “application/x-wwwform-urlencoded”. You use this scenario to select the PI main message
payload from one of the parameters of the form submit request.
• Form-Based File Upload
Form Based File Upload is a form based HTTP POST request and is multipart (RFC 1867). You use this scenario to select the PI message payload
and PI main message attachments from a form-based file-upload.
• Generic Multipart Request
This is a multipart HTTP POST request. You use this scenario to select the PI main message payload and the PI message attachments from a generic
multipart request.
• URL Parameter
This request is an HTTP GET request. You use this scenario to select the PI main message payload from a URL parameter.
HTTP AAE Sender Configuration in Details
To configure the HTTP AAE Sender, we need information about the message protocol (HTTP POST/HTTP GET) and the request details.
• Set Form
If the HTTP input is through form submission, select the Set Form checkbox. In the Main Payload Parameter Name field, specify the name of the request
parameter whose value should be copied to the PI main payload.
• Set Multipart
If the HTTP request is a multipart request where one or more sets of data are combined into a single body, choose the Set Multipart checkbox. In
the Main Payload Parameter Name field, specify the name of the request parameter whose value should be copied to the PI main payload. In addition,
if you want the attachments in the HTTP request to be copied as PI message attachments, select the Keep Attachments checkbox.
After configuring the sender Java HTTP adapter, use the following URL to trigger the call.
http://<host>:<port>//HttpAdapter/HttpMessageServlet?<query-string>
HTTP AAE Receiver Configuration in Detail
To configure the HTTP AAE receiver, details about the receiver scenario have to be provided.
• URL destination details
• Security and authentication information
• Proxy details
• Request details (Set Form Source/Set Multipart Source/Specify Content
Details)
Set Form Source
If the HTTP input from the receiver channel to the target system is through form submission, enter the Main Payload Field Name. In the Main Payload
Parameter Name field, specify the name of the parameter whose value should be copied to the PI main payload.
Set Multipart Source
If the HTTP request is a multipart request where one or more sets of data are combined into a single body, choose the Set Multipart Source checkbox. In
the Main Payload Parameter Name field, specify the name of the parameter to which you want to copy the value of the PI main payload. In addition, if
you want the attachments in the request to be delivered to the target system, select the Keep Attachments checkbox.
Specify Content Details
Content details are required if you want to specify the character encoding or the content type of the HTTP input. For a multipart request, specify the
character set and the content type details of the main payload.
Hope this overview let you have a better idea about this new adapter and the capcbilities that it provides.
Thanks