Joined: 15 May 2001 Posts: 3264 Location: London, ON Canada
jefflowrey wrote:
ApplicationID should not be used to hold Business Data, like a Password.
Absolutely true. This is the wrong field for this data and since you didn't mention encryption, I take it that you are send the password in plain text.
I hope your company is not doing business in the USA because this breaks both HIPAA and Sarbanes-Oxley rules. (and for Sarbanes-Oxley your CIO and possible CEO can go to jail!!)
IBM's original intention for the MQMD's applicationIdData field was for "meta-data" like information.
i.e.
If your message was XML then you could put XML.
If your message was formatted for EDI 508 then you could put EDI508.
etc...
This philosophy seems to have been dropped by most MQ developers or maybe they weren't taught it.
jefflowrey wrote:
You will almost certainly not be able to do this with JMS and will have to do this with the WebSphere MQ API for Java.
True. You cannot set the MQMD's applicationIdData field from JMS. (Been there, can't be done.)
Therefore, if you really need to set the MQMD's applicationIdData field then you have 2 choices:
1) Don't use JMS and use MQ Based Java API
2) Use JMS but write a Send Exit to set the MQMD applicationIdData. (I have done it and it is non-trivial.)
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