| Author |
Message
|
| murdeep |
 Posted: Tue Jun 08, 2010 1:46 pm Post subject: Editting the message set id |
 |
|
Master
Joined: 03 Nov 2004
Posts: 211
|
Hi, working with WMB V7. Some background. In the past we have had developers not follow our naming standard for message sets. Not good but whatever. What we did to ensure that the deployed message set was named correctly was to edit the dictionary name in the bar so when deployed it would meet our naming standard.
With V7 I have noticed that even if you edit the message set name in the bar when it gets deployed it reverts to the pre-editted name.
Ok, no biggie I will create a new message set with the correct name and base it on the old message set. Problem with this strategy is the message set id is uniquely generated by the system which will require me to ensure any esql or RCD nodes that refer to the old message set id will need to be updated. So my question is there any tricks that allow me to behind the scenes edit the message set id so I can set it to the old message set id?
I've tried opening the message set with the text editor and changing the id there but it doesn't appear to take. I've also tried editting the files in the filesystem after closing the project but this doesn't seem to work either. Any pointers will be appreciated. |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Jun 08, 2010 1:57 pm Post subject: Re: Editting the message set id |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| murdeep wrote: |
Problem with this strategy is the message set id is uniquely generated by the system which will require me to ensure any esql or RCD nodes that refer to the old message set id will need to be updated. So my question is there any tricks that allow me to behind the scenes edit the message set id so I can set it to the old message set id?
I've tried opening the message set with the text editor and changing the id there but it doesn't appear to take. I've also tried editting the files in the filesystem after closing the project but this doesn't seem to work either. Any pointers will be appreciated. |
you are trying to hack, message set id is an unique identification number,
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| murdeep |
| Posted: Tue Jun 08, 2010 1:59 pm Post subject: Re: Editting the message set id |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
| Gaya3 wrote: |
you are trying to hack, message set id is an unique identification number, |
That was helpful. Thanks Captain Obvious. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 08, 2010 3:08 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Are you changing both the name of the mxsd file and the name of the message set file in the broker.xml?
Or just one of the two? |
|
| Back to top |
|
|
| murdeep |
| Posted: Tue Jun 08, 2010 3:36 pm Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
| mqjeff wrote: |
Are you changing both the name of the mxsd file and the name of the message set file in the broker.xml?
Or just one of the two? |
From within the tooling I am opening the messageSet.mxsd file with the text editor from context menu and then looking for and changing all occurences of the message set id as it appears when opening the messageset.mxsd with the message set editor, then saving it and reopening with the message set editor. This has no effect on the message set id.
Not sure about the broker.xml file. How does that come into play here? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 08, 2010 8:12 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Going to a lot of trouble here.
Have the developers discontinue the use of the message set id and instead use an alias (defined on the message set (see default message set editor).
As long as the alias is unique there should be no problem using it as a reference...
However be careful of MQInput and RCD nodes... I believe they like to hold on to the messagesetId. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 09, 2010 3:03 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Okay, so you have tried two approaches:
1) renaming the original message set in the bar
2) creating a new message set with the appropriate name and subsitituting that in the bar
I asked some questions about how you were doing #1, not how you were doing #2. |
|
| Back to top |
|
|
| murdeep |
| Posted: Wed Jun 09, 2010 6:29 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
| mqjeff wrote: |
Okay, so you have tried two approaches:
1) renaming the original message set in the bar
2) creating a new message set with the appropriate name and subsitituting that in the bar
I asked some questions about how you were doing #1, not how you were doing #2. |
On point 2, this works but requires me to ensure that any ESQL or nodes that reference the msgSet Id must be updated. This is what I want to avoid by changing the msgSet Id. I understand that msgSet Ids must be unique and would manage this.
On point 1 I assume you are asking how I renamed the messageSet in the bar?
Hilite the dictionary in the bar after it has been added then choose edit from the context menu, change the name and save the bar. However what I have noticed is that when the bar is depolyed the dictionary name that is displayed in the EG is the name prior to editting so it appears not to work.
In V6 the edtted name of the dictionary in the bar is what would be displayed in the EG at runtime. This change in behavior in V7 is what is biting us now. |
|
| Back to top |
|
|
|
|
