Originally posted by: SystemAdmin

I am wondering if anyone has upgraded to Ascential 7.5.1 from 6.5.2? If you have, did you or are you encountering a lot of issues?

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

Originally posted by: SystemAdmin

Just completed. Audit logs and changed. They removed the word Mercator from the audit logs produced. The type tree had to be modified.

Behavior changes to the IF() when testing if the map failed, or you can say that I found way to use the IF() that shouldn't have worked.

DSTX 7.5.1
=IF(mapreturn Attribute Value:mapreturn Attribute:ExecutionSummary AttList:ExecutionSummary:MercatorMapAudit Element:Auditlog color=red:c7841692f6b:c7841692f6!= "0", [/b:c7841692f6][/color:c7841692f6]
Mercator 6.5.2
=IF(mapreturn Attribute Value:mapreturn Attribute:ExecutionSummary AttList:ExecutionSummary:MercatorMapAudit Element:Auditlog color=red:c7841692f6b:c7841692f6!= 0, [/b:c7841692f6][/color:c7841692f6]
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Started testing 7.5.1. Stopped for now. Some of the things I noted are:

Launcher.txt file is gone (real drag for us as we reference it and you could determine how much information it should log).

Appears that 'Debug' is always running as it's creating the debug files in '\\path\Ascential...\logs\' without 'debug' being selected. We don't typically let developers into application folders as its a potential problem. But they are also the ones that address problems and need access to the files. Can't reassign log file location either. Considering options.

Looks like there are some nice new features though. Want to find the time to test it again.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

The launcher.txt file has been replaced with logs gernerated in \logs file. The corresponding launcher.txt file is call CompoundSystem01-04-05-02-03-33-PM.txt The date/time will change.

The information in this file should be the same as in the launcher.txt file.

An option is to change the permission on just the \logs directory or map it to an area that the developers have access to. That way the don't have access to the parent directory \Ascential or other directories and files below it.

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

Originally posted by: SystemAdmin

Also if you are using the SWIFT adapter, you'll need a patch for client and server side when upgrading to 7.5.1
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Have been using 7.5 for several months now and am happy with it. There are a number of changes to be aware of, least of all the branding changes (yes you can remove the Ascential banner from the designers if you like!).

You would be advised to read the documentation that comes with 7.5 (& 7.5.1) to discover the differences.

If you're using XML, be sure to re-import all trees rather than just upgrade them in the Type Designer. This is because they are constructed differently with regards to initiators/terminators etc.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Tarun,
Is it essential to reimport xsd or just desirable?
Jan
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Jan,

in my client's current architecture we are using an XML structure as a Common Data Model between all TX interfaces.

This XML structure is imported and then we "cut out" the sections we require a form a separate tree that is actually used in the maps. Therefore we have 2 XML trees -- a "Master" and a "Section" so to say.

I re-imported the "Master" in 7.5. Then I opened the existing "Section" in 7.5 (I did not re-import or re-cut it). I tried to merge the two, which caused problems due to the different manner in which terminators are handled.

Therefore it became essential for us to re-import our XML structures.

Personally I would recommend re-importing your trees. Of course, you'll have to look at your cost/benefit ratio to see whether this is worthwhile. If you have maps already ini production then it is probably worth leaving them until a change becomes necessary.

I found Ascential Support (UK) to be very helpful on this topic.

We're now upgrading to 7.5.1 to resolve a memory leak issue on our Windows server.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender