| Author |
Message
|
| dilse |
 Posted: Thu Nov 18, 2004 7:44 am Post subject: Adding Extra field in Input Message |
 |
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Guys,
I have a simple question for you. we want to add an extra field in incoming message which is basically an XML. we are converting XML to MRM on broker. what are the necessary steps to ensure safe modification and also in which places do i need to change the field. we have a message set for the MRM message. Our Environment: WMQI 2.1 with CSD 07.
Appreciate your opinions.
_________________
DilSe..
Take life as it comes.. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Nov 18, 2004 8:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You use SET to add fields to message trees.
If you have an dependancy on the order of output fields, then you should ensure that your SET statements occur in the correct order.
As to what steps are necessary to ensure "safe modification", you will have to be clearer on what is "unsafe" modification.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dilse |
| Posted: Thu Nov 18, 2004 8:12 am Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Thanks a million Jeff.. Yes. I do have order dependence in Output. What I meant by safe modification was that "is it safe to modify by adding just this new field to the essage set or do i need to create a new message set".
Thanks!
_________________
DilSe..
Take life as it comes.. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 18, 2004 8:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There's nothing in the product that prevents you from modifying a message set, except in 2.1 when you can "freeze" message sets.
So, as long as you use the product, it is safe to modify a message set.
On the other hand, if the application receiving your output is not prepared for the extra field, then it is not safe to modify the message set.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dilse |
| Posted: Thu Nov 18, 2004 11:20 am Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
THANKS A LOT JEFF..
_________________
DilSe..
Take life as it comes.. |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Nov 18, 2004 6:02 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
What is your output message format? Is it MRM-XML, MRM-CWF or MRM-TDS?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| dilse |
| Posted: Fri Nov 19, 2004 1:45 pm Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Hi Kiran,
It is MRM-XML. Any extra information appreciated.
Thanks..,
_________________
DilSe..
Take life as it comes.. |
|
| Back to top |
|
|
| KeeferG |
| Posted: Mon Nov 22, 2004 4:25 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
If you are using the MRM then you should create a new target message set with the extra field in it. Either that or change to the XML domain for the output message. I prefer the former option myself. Dont forget to use the SET commands in the right sequence for the new target message set otherwise you may end up with a physical/logical message mismatch.
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
|
|
