Joined: 20 May 2001 Posts: 107 Location: Zurich Financial Services
Yes I admit that there is a line in the manual which says that 2.0.2 control centres should not be used with 2.0.1 config mgrs.
BUT - you really must pay heed to this advice as it appears that the 2.0.2 control centres work quite happily with 2.0.1 config mgrs. In fact it works so well that I built several message flows with my 2.0.2 control centre.
HOWEVER - if you then export a msg flow built with a 2.0.2 c/c you'll notice a number of new XML attributes such as "useDefaults" and "orientation". Just you try and import this XML in to a 2.0.1 config mgr using a 2.0.1 c/c and you will fail.
I am now in the situation where I cannot migrate my message flows up to the next level (qa and production) as they will not import when I use the 2.0.1 c/cs used for QA and prod.
I tried hacking the xml export file to remove these new attributes but got in to a right mess. The only other real alternative is to edit the CMSGFLOW table on the MQSICFMG database to remove the attributes from the CXMLDATA column. I think this is going to be a very dangerous thing to attempt.
My only real alternative is to rewrite the message flows using a 2.0.1 c/c.
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