Action and Query-String in HTTP Adapter

[Former Member]

Hi,

I am doing an IDOC -> SAP PI -> HTTP scenario

HTTP application is external party (using Party).

I have to build the URL Dynamically; so I use Dynamic Configuration in Message Mapping.

The URL format (from help.sap.com) is http://<hostname:port>/<path>?<query-string>;

Hostname and port are know to me.

From where will I get information about path and query-string , are they mandatory?

help.sap.com has given details about sender HTTP: http://help.sap.com/saphelp_nwpi711/helpdata/en/44/8f54b8b01e3673e10000000a114a6b/content.htm but i want to know about receiver HTTP.

Is there any example available?

Thank you,

Pankaj.

[rajasekhar_reddy14 · Accepted solution]

>

> I have to build the URL Dynamically; so I use Dynamic Configuration in Message Mapping.

> The URL format (from help.sap.com) is http://<hostname:port>/<path>?<query-string>;

> Hostname and port are know to me.

>

Query string and Path will specify the complete address of destinaton, if you give one hostname and port data will be posted ,but not specific location.

Better to create HTTP destination and test the destination able to connect to your Target System or not,use HTTP destination in Receiver Adapter.

Regards,

Raj

[Former Member · Accepted solution]

Hi,

We have 6 external parties; which party should receive the message will be indicated by a field in IDOC. So I thought using a URL will be better.

Now got into another confusion, we even have an External Party(HTTP) -> SAP PI -> IDOC scenario, so in this flow do you mandatorily have a RFC destination of Type G?

Thank you,

Pankaj.

[stefan_grube · Accepted solution]

> so in this flow do you mandatorily have a RFC destination of Type G?

No, this is not necessary.

[Former Member · Accepted solution]

Hi,

No, this is not necessary.

So I have to ask the External Parties to send the message (to SAP PI) to the URL (http://hostname:port/<action>?<query-string>)?

Any idea about my original question (about action and query-string in receiver channel's URL) or should I use a RFC destination there (now it will be Type G I suppose)

There is SSL configuration also between External Parties and SAP PI (if this information is required).

Thank you,

Pankaj.

[stefan_grube · Accepted solution]

> So I have to ask the External Parties to send the message (to SAP PI) to the URL (http://hostname:port/<action>?<query-string>)?

When you replace the varaibles, yes.

> Any idea about my original question (about action and query-string in receiver channel's URL) or should I use a RFC destination there (now it will be Type G I suppose)

Just put the URL of the receiver.

> There is SSL configuration also between External Parties and SAP PI (if this information is required).

In that case, you put a URL with https://..

[Former Member · Accepted solution]

Hi,

When you replace the varaibles, yes.

Yes I will do that and form the URL as mentioned here: http://help.sap.com/saphelp_nwpi711/helpdata/en/44/8f54b8b01e3673e10000000a114a6b/content.htm

Just put the URL of the receiver.

Ok, I will try to get the exact URL from the external party. Is this similar to the one that we use as Target URL in receiver SOAP communication Channel?

Thank you,

Pankaj.

[stefan_grube · Accepted solution]

> Ok, I will try to get the exact URL from the external party. Is this similar to the one that we use as Target URL in receiver SOAP communication Channel?

How should I know, what you put in SOAP cc?

Simply use the URL the receiver tells you.

[Former Member · Accepted solution]

Hi,

How should I know, what you put in SOAP cc?

I was actually talking about the Target URL in general and not the one that I am using

I was actually asking if the Target URL that we put in SOAP CC and the one in HTTP CC serve the similar purpose/ functionality (again in general and not specific to any scenario)

Simply use the URL the receiver tells you.

Yes I will ask the receiver to give me the details.

Thank you,

Pankaj.

[stefan_grube · Accepted solution]

> I was actually asking if the Target URL that we put in SOAP CC and the one in HTTP CC serve the similar purpose/ functionality (again in general and not specific to any scenario)

Yes, this is the same.

In fact a SOAP call is based on HTTP also.