Originally posted by: SystemAdmin

I built a tree in 8.0 that a 6.7.1 map will now need to use. I could rebuild from scratch but would rather export to an mts file and import from there. Is this possible?

The export works fine, the import seems to work but 6.7.1 does not actually create a 6.7.1 tree. I move the mts file to an empty directory so the problem isn't that the mtt file already exists.

When importing I walk thru the prompts. Once it analizes the mts file it says 'Warning 43 reference 280: Analysis warnings occurred.'. (I expected this because I have some expected warnings in the 8.0 version of the tree.) When I select 'finish', though, it does not create the tree.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Hello! Have had it verified from support and found out from experience that 8.0 trees are not backwards compatible to previous versions.

Now upward compatibility exists but support still recommends analyzing any trees migrating from 6.7.1 to a higher version and compiling any maps migrating to a higher version as well.

The same thing happens with the Integration Flow designer, you cannot create a system on 8.0 and try to run it on a 6.7.1 installed environment, also Linux platform specified systems have issues running in a Unix based environment too.

Would assume trying to export to an mts file would have the same issues with backwards compatibility.

The best bet is to build the tree from scratch if you have to run in 6.7.1 or migrate completely to 8.0 if that is a possibility.

Hope this helps.

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

Originally posted by: SystemAdmin

I was hoping the mts import would be the work around as since I've been working with the tool mtt, msd and mmc files have not been backword compatable.

It's to late to build the tree in 6.7.1 and migrate it to 8.0 it's already in 8.0 and I want to integrate it into a 6.7.1 map. Just being lazy, I guess I'll have to build it manually....... unless it can build a dtd file from the mts and import that.....
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Might have a problem there too, since trees from a later version may cantain properties, etc. that did not exist in a previous version. Even if it did exist, it could have been updated.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Sorry to rehash an old thread, but has anybody had success with this?
We are trying to take trees from 8.1 down to 6.7.1 in order to keep up with a new type of EDI transaction that we have to handle in an older system. I understand that we can't take the .mtt files back direclty, but was hoping that the .mts files could be transferred.

From the looks of it (and a diff), the ttmaker60.dtd schema is all but the same, and the files produced by an export of a similar tree have a similar format. Thing is, I keep getting syntax errors, and can't isolate where the script files are different.

I'd prefer not to have to rewrite this .mtt, so if you guys have any ideas, I'd really appreciate the advice. I'm also open to hearing that this is a dead end, as I can then get started with plan B.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender