MQSeries.net :: View topic - ESQL User Defined Properties override limitation

garg

Dear Masters,

I would like to request you for your valuable inputs and guidance on this implementation.

I have a requirement to set Envrionment specific properties, which actually prepare security headers for HTTP REST services, along with other additional properties as well (e.g setting email ids etc.).

All of these properties are environment specific properties, hence the the intent is to define them as user defined properties within the esql code. Most of these are to be used multiple times within each flow (there are couple of http service calls in a single flow, hence the headers, need to be prepared repetitively) and to add further, there are several flows, utilizing the same functionality all over.

As an implementation, I have firstly written down common procedures that replicate the common functionalities, and used them within all the set of flows. Now each of these common functionalities need to use these envrionment specific properties, hence i have defined all these properties in the same common procedure file where all these procedures are implemented, instead of defining them reptitively in each of the respective flows.

More importantly the rationale behind putting them in this common file itself and not at the individual flows is, since they are to be used in common procedures, in case if they would have been defined on each flow, then they all would have to be passed to those procedures, thus
increasing the number of parameters to a great extent.

On the other hand, there is a limitation as well. Since these user defined properties are declared in esql only, they are NOT overridden by the deployment descriptor file, using the mqsiapplybaroverride command. Reason being, these have to be declared at flow level only, then only these could be overridden.

Please advice:

a) Does this approach looks ok, and is there any other way, by which these user defined properties can be overridden using the deployment descriptor itself, with the above implementation

b) If not, then please suggest if their could be any other alternative way to meet this peculiar requirement.

Since all these properties are envrionment specific the preference is to have these user defined properties which can be overridden by the deployment descriptor, as the whole code moves across envrionments.

c) Any other suggestive approach, if the above implementation doesn't fits in?

Thanks and Regards,
Garg