Proxy 2 JMS Scenario: additional jms properties are not visible

[Former Member]

Hi @all,

I'm working with SAP PI 7.1 as middleware and ECC 6.0 as backend. The business affords to configure a Proxy to JMS scenario.

The configuration is done, with jms sender & receiver adapter and xi-adapter, aso.

Now the jms provider needs additional properties in jms header. The configuration is also done, i've added the modules and the properties in module configuration. The thing is, that the additional properties are not putted into the provider queue. Also the JMSType is null.

Within the communication channel the modules are in the following order:

RequestOnewayBean

DynamicConfigurationBean (for the jms_header)

ConvertyMessageToBinary

SendBinarytoXIJMSService

WaitResponseBean

Cache refresh is done and the server is restarted, but with no effects.

Is there someone with a similar scenario who could give me a feedback about solution? Step by Step?

By the way: is the length of the additional parameter value limited?

Thanks in Advance,

Stefan

[Shabarish_Nair]

how are you setting the additional attributes?

Are you using Dynamic configuration in the mapping?

[Former Member]

Hi,

I'm setting the additional attributes in receiver communication channel (where request is).

I'm not using dynamic configuration in relation to an UDF, but I'm using the DynamicConfigurationBean to set the properties for jms_header in this way:

PARAMETER VALUE = insert http://sap.com/xi/XI/System/JMS DCJMSMessageProperty0

The properties are fix values and not depending on the message comming in.

The connection parameter in sender and reciever is jms-conform. The provider is ibm websphere mq.

[Former Member]

Hi @all,

I found out what the mistake was:

The connection parameter "JMS-konform" was not set to "JMS-konform". After resetting the properties are visible in queue.

Greetings,

Stefan