Question Re: SENDER HTTP_AAE Sender adapter Parameters issue in Technology Q&A

SENDER HTTP_AAE Sender adapter Parameters issue

Former Member — Sun, 05 Mar 2017 16:32:03 GMT

Hi All,

We have a requirement where we are receiving HTTP request to our PO (PO 7.5) Server and the incoming request may have more than 6 URL Parameters. I can use Dynamic Configuration to yield the actual incoming values and that is not a problem, but I have gone through SAP Help and it says that we have a limit of only 6 parameters...Any help would be highly appreciated.

SAP Help:

https://help.sap.com/saphelp_nw74/helpdata/en/e4/a451e997364386a1f6f090c9ea17b6/frameset.htm

Referred to many threads but all seems to talk about RECEIVER HTTP_AAE Channel:

One is: https://archive.sap.com/discussions/thread/3241568

Regards,

Anuj

Re: SENDER HTTP_AAE Sender adapter Parameters issue

wilbertkarremans — Mon, 07 May 2018 21:36:05 GMT

Hi Anuj

I am facing the same issue, I have > 6 URL parameters in my HTTP_AAE Sender adapter.

Did you find a solution for this?

Best regards,

Wilbert

Re: SENDER HTTP_AAE Sender adapter Parameters issue

Former Member — Tue, 08 May 2018 13:20:45 GMT

Hi Wilbert,

I think we never found the solution to this problem, and we had gone to REST Adapter instead.

Cheers!
Anuj

Re: SENDER HTTP_AAE Sender adapter Parameters issue

karaulov_ed — Wed, 25 Jul 2018 08:39:23 GMT

For using more than 6 URL parameters in the HTTP sender adapter you need to make next settings (like in the HTTP receiver adapter settings):

1) activate the “Set Additional Parameters” option (see screenshot below)
2) add entries in the Additional Parameters table as described in a table below

Name

Value

SAP_URL_EXTENSION

urlext

urlext01

param7

urlext02

param8

3) activate adapter

Now we can test our settings. For this purpose I used Postman.

After we've sent a message we can check PIMON (received message Dynamic Configuration part)

Re: SENDER HTTP_AAE Sender adapter Parameters issue

Former Member — Sat, 04 Aug 2018 08:53:00 GMT

Hi Eduard,

Many Thanks for this.

We had actually gone with REST when we had faced this issue. will try this in coming requirements..

Regards,

Anuj