Error using XI HTTP adapter specific message attribute URL parameters

[Former Member]

Hi XI gurus, in our XI 7.0 SPS11,

we have problem using URL parameters of plain HTTP receiver adapter.

If I set Adapter specific message Properties in communication channel and activate switch for Apply URL parameters (using Parameter 1 to 5) filling them using message mapping, we have no effect; instead we have error "Dynamic Header - Missing Message Attributes: Fields/Parameters".

We carried out this test:

1. not using adapter specific message attribute and setting

a static URL target with fixed parameters it runs correctly.

2. using adapter specific message attribute for target

URL and URL parameters both doesn't runs correctly.

3. using adapter specific message attribute only for target

URL doesn't run correctly.

These attribute key used for URL parameters:

URLParamOne

URLParamTwo

URLParamThree

URLParamFour

URLParamFive

Namespace: http://sap.com/xi/XI/System/HTTP

Can you solve this issue? Are there oss notes, corrections, ...

Thanks in advance.

Marco Tricase

[Former Member · Accepted solution]

this is a known error due to difference is case

adapter metadata uses URLParamOne whereas XI header uses UrlParamOne(note the difference is case of URL/Url)

SAP has released note 1101338 for this

Thanx

Aamir

[Former Member]

Thank you very much

[Former Member]

Toto,

I also followed the SAP Adapter documentation. After much time wasting I finally found some conflicting documentation in a blog

Testing confirmed that the case must be changed from URL to Url

Regards,

Mike

[Former Member]

Some other test done with TCP gateway.

Activated adapter specific message properties for

*URL

*HTTP Header fields (one header field named "lisca")

*URL Parameters (one param named "objectType")

The HTTP message catched by TCP Gateway

POST /csl/cslinker HTTP/1.0

content-type: text/xml; charset=UTF-8

content-length: 318

connection: close

accept: /

user-agent: SAP Web Application Server (1.0;700)

host: 10.10.43.94:54000

accept-encoding: gzip

<?xml version="1.0" encoding="UTF-8"?>

...

seems nothing has been generated, and obviusly URL and params have been set in message mapping.

Hope some guru has been solved the issue ...

Pasquale Rossiello

[Former Member]

Hi all,

can you reply also to my direct email: marco.tricase@progetto29.it

Thanks