I had promoted the Message Expiry time from MQheader to Message flow level.After the promotion now the expiry property is reflected at the message flow level but this property donot reflect in the barfile during the built time.
So after this i have found that in the infocenter that the Message expiry time is not configurable.
but at first i have tried to make this property configurable when i have read the following document which contradicts information provided in the infocenter
So as a conclusion in my case message expiry property is not working as a configurable property when i promote to message flow level (want to do to change the value in barfile at the deployment time).So as a alternative can we define this property as a UDP and code the MQMD header using ESQL so that i will be able to change the valu at the barfile level???
Wouldn't you want to set the expiration on the OutputRoot.Properties?
This should then get reflected in the MQHeader at serialization time.
A UDP seems to be the way to go, but I think some coding will also be necessary there.
There is nothing an end user can do to change a property that is non-configurable into a property that is configurable. This is done by the development team in the code that provides the node functionality.
You can raise a requirement to make this property configurable, but that only means that the development team will receive the requirement. It doesn't provide any SLA in terms of if or when they will actually implement that requirement.
As F.J. says, if you want to control the expiration time set on every message that passes through your flow through a property that is set on the BAR file when you deploy your flow, use a UDP and configure ESQL code to populate that into the logical message tree.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum