Originally posted by: SystemAdmin

Hi-
I'm upgrading from Mercator 6.5.2 to 6.7.1 on Windows 2000. Does anyone have any tips for upgrading? Any pitfalls to watch out for? From earlier postings, it doesn't sound like I need to recompile my maps and systems- is this true? Are there any functions that behave differently?

Any general information about upgrading is appreciated.

Thanks- Coleen
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

We did not experience any problems when upgrading from 6.5.2 to 6.7.1 (win 2000). As far as I remember the IFD will transform your MSD file when you open it in the 6.7 version and that was all we did.
We might also have changed a few things in the 6.7 Mercator.Ini file, based on the 6.5 ini file running in our production environment.
There is a pretty good pdf document that describes the changes in 6.7.
I think it comes with the installation.
You might want to take a look at that.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

We are also currently upgrading from 6.5.2 to 6.7.1 and we are not having any major issues with the upgrade. We did however have some problems with the installation and some database issues based on versions.

To address your question about not having to recompile maps and systems, in the release notes (Section 3: Upgrading from an earlier version) it says you don't have to, then in the next section about 'Preparing maps to Execute with V6.x' it recommends analyzing all type trees, build all maps, and generate the systems. This is the approach we chose to go, open everything and rebuild everything, however we do not have a large amount of systems either. We did not test using a 6.5.2 msl on the 6.7.1 Event Server, so I could not say for sure if that would work.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

I strongly suggest that you make a backup copy of all your 6.5.2 source files prior to opening any files - most of the design components will automagically update source files when opened. On occasion, this will inhibit being able to open the files in the previous product version.
6.7.1 should not have a problem executing maps and systems created in 6.5.2 - Hopefully, you are attempting the upgrade in a testing environment.
As already identified, it is generally best to recompile/deploy using the same version you are executing with.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Thank you for your replies. I agree that it seems safer/better to recompile the maps and systems in 6.7. Also, I did notice that the map designer opened my 6.5.2 map in 6.7.1 even though I chose to keep 6.5.2 as the default. I do have backups of all my 6.5.2 maps in case we accidentally save a file in 6.7.1.

It looked like there were a bunch of questions around the XML schema importer/xml type trees posted in the forum. Did anyone find they needed to make any changes to their schemas or type trees under the new version?

Thanks- Coleen
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange