HTTP Receiver channel

[Former Member]

Hi experts,

I'm working on an RFC => HTML scenario to access exchange rate data from the oanda application, which is something like this:

1º RFC.request ==> XML_request for the HTTP (a Message Interface Synchronous)

2º XML_response (the output for my MI) ==> RFC.response

I already created the 2 maps needed, and the interface mapping containing request = 1º, response 2º

In the scenario i have 1 sender Rfc channel, 1 receiver det, 1 interface det (MI to IM), receiver agreement (with the HTTP channel)

The problem is that, i'm not used to HTTP receiver channels

- What are the parameters needed?

- How do i pass the XML request to the HTTP?

Any help would be appretiated!

[Former Member · Accepted solution]

Hi Alexis

PI dont have HTML adaptor.

You need to send data as a web service and consume the web service using JSP page or Web Dynpro development.

RFC ->XI -> SOAP ( -> JSP ->) which generate response

SOAP response -> XI -> RFC response

This can satisfy your requirement.

Thanks

Gaurav

[Former Member · Accepted solution]

My mistake!!

When i talk about an HTML i meant that parameter in the comunication channel (Adapter Type), and i wanted to say HTTP!

There's a "HTTP" adapter type, and it has two types of Adressing (URL Adress and HTTP destination)

And there's a "SOAP" that has a lot of message protocols (HTTP, SMTP, HTTP (axis), File (axis), etc etc)

My only doubt is..

To make a request (POST, not GET) to the Oanda HTTP (that returns an XML:

- What type of channel i have to generate (SOAP, HTTP? and the subtypes?

- What are the required parameters for this to work correctly?

The example posted above is with a "SOAP" but i believe (not sure) that i need a HTTP type, but i would need to understand the difference between them, and if i really need one the questions are still the same above, since i'm new to http comunication channels

Edited by: Alexis Alanis on Oct 2, 2008 9:59 AM

[Former Member · Accepted solution]

You can use the URL addressing

And give the hostname port and all the details of the destination system.

Some targets require header enhancements then use prolog for that.

[Former Member · Accepted solution]

I just got a test more likely

-

---

These are the parameter for my HTTP receiver channel:

Adapter Type: HTTP

Transport protocol: HTTP 1.0

Message protocol: XI Payload

Adapter Engine: Integration Server

Adressing type: URL Adress

Target host: (the url for the site)

service number: **

path prefix: (the path to do the request)

Proxy host: ***

Proxy port: *****

Anonymous logon

content type: text/xml

-

---

And i need to pass this xml request to the site

<convert>

<client_id>

<exch>

<expr>

<amount>

<nprices>

<date>

</convert>

Am i missing something?

Because even when i pass the correct client_id i get an error as if that client_id was invalid

************************************************************************

I just noticed, i do get to connect with the HTTP, but the message seems to be just blank (i get to connect but it seems i'm only passing the url without the xml payload), i don't know why, because checking the monitoring i do see the xml!

Maybe i'm missing a parameter in the channel?

Any ideas?

Edited by: Alexis Alanis on Oct 2, 2008 6:05 PM

[Former Member]

For OANDA you need to include the "fxmlrequest=" for the prologue value and check the box for URL escaping. Hope this helps.

[Former Member]

Below blogs shd help you,

[Former Member]

Thanks for the answer, but i believe that the adapter type used for this type of development should be "HTTP" instead of SOAP (like in that example)

My main problem is that i don't really understand which type use and what are the required parameters