The following table shows an overview of the adapter characteristics:
Characteristic |
Values |
More Information |
---|---|---|
Transport Protocol |
HTTP(S) 1.1 |
|
Message Protocol |
POST, GET |
|
Quality of Service |
BE, EO, EOIO |
Quality of Service |
Attachments |
Yes |
|
Attributes in Message Header |
sender, receiver |
Using Adapter-Specific Message Attributes in the Message Header |
Acknowledgments |
System acknowledgments, system error acknowledgments |
|
Module Processor |
Module(s) configuration supported |
|
Security |
HTTP and SSL |
HTTP and SSL |
The Java HTTP adapter supports the following combinations of HTTP requests:
Set Form Selected? |
Set Multipart Selected? |
Message Protocol |
Scenario |
---|---|---|---|
Yes |
No |
Post |
It indicates that the HTTP POST request is a form submit request. Content type for this scenario is 'application/x-www-form-urlencoded'. You use this scenario to select the XI main message payload from one of the parameters of the form submit request. |
Yes |
Yes |
Post |
It indicates that the HTTP POST request is form based and is multipart (RFC 1867). You use this scenario to select the XI message payload and XI main message attachments from a form-based file-upload. |
No |
Yes |
Post |
It indicates that the HTTP POST request is a multipart request. You use this scenario to select the XI main message payload and XI message attachments from a generic multipart request. |
No |
No |
Get |
It indicates that the incoming request is a HTTP GET request. You use this scenario to select the XI main message payload from a URL parameter. |