Originally posted by: muralee

Hi,

We are planning to upgrade to 8.2 version . can we deploy maps which got created in 8.1 to 8.2 version.

I heard that there is a specific option in 8.2 , where it can convert all the 8.1 maps to 8.2 version automatically , is this right ?

and is this is a good pratise to deply 8.1 maps into 8.2 version ?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: NancyR

You might want to read the Utility Commands pdf in the online library.

And, while you can run 8.1 maps with the 8.2 engine it's not recommended.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

You mean we have to rebuild and redeploy all the maps from 8.1 to 8.2?

Thanks.

Huong
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

I've run maps compiled at 6.7.1 and 8.1 under 8.2 without the need for change.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: thorstenhirsch

Actually you should also export the typetree in the old version an import it in the new version before compiling the map with the new version. Well, that's the cleanest way to upgrade. But most maps also work with a dirty upgrade. :-)
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: Kepa_Screen

My personal experience with migrations from one version to another, is that the better way to do it is with a "clean" method.

You should batch export from original version, analyze, and then re-import to another version, all sources ( mms, mtt, msd, mdq ... ) With msd is better to save old versions in their original format, we use Subversion with several paths in order to have all our diferent versioned files ( mercator6.7.1, datastageTx 7.5 .., now WSTX 8.1.0.3 ) well sorted and mantained.

You can also do it in a "dirty" way as said by thorstenhirsch but we had problems in the past with some trees and functions after the migration ( seriestotext function, xml restrictions on types, and now we have another bad experience with some complex Oracle AQ typetrees ).

So I recomend you to do it in a "clean" way. It's very simple, you can make a script that does it easy.

Create a .bat file containing something like

del type_export.log 

for %%K in (*.mtt) 

do 
"C:\Program Files\IBM\Websphere transformation extender 8.0"\texport %%K >> type_export.log

del type_analyze.log 

for %%K in (*.mtt) 

do 
"C:\Program Files\IBM\Websphere transformation extender 8.0"\tanalyze %%K >> type_analyze.log

del type_import.log 

for %%K in (*.mts) 

do 
"C:\Program Files\IBM\Websphere transformation extender 8.1"\timport %%K >> type_import.log

Also with maps, using mms and mexport, mimport, ( or dstxmapconv ) then mcompile....
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

I've always found that this just highlights problems with the new release and either patches have to be obtained or the map reworked.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

I gave up trying to export and import type trees and maps some years ago as errors were created upon importing them. It could be better now.

I load, compile, and save all maps and load, analyze, and save all type trees when performing an upgrade. I also load and save MDQ & MSD. I suppose this might be a chore if you had 1000's of files.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender