Problem with External System Translations for OUTBOUND/INBOUND

[Stefano]

Hello all,

We had migrated a production systems from 5.0 windows version to 5.5 cu4 LINUX one, migrating also DB.
Migration go well and OTM work fine but we have a problem using external systems, in windows version we had used external systems with xls translation to export and re-import in the OTM data related to shipment and order base, adding special information in special place, for instance we use to add delivered events and pickup events in automatic way.
TO do this we had configured external systems to same otm installation using specific XSL file for the requested transformations.

After migration , this XSL transformations DON'T WORKS any more, we try also to re-create external system, we re-upload xls from dba user, we still we have a problem in OAS CONSOLE LOG saying that OTM don't found xsl file in integration path.

Consider that using external system configuration without xsl transformation, records correctly arrive in inbound OTM transmission.

Please could anybody help us

thanks in advance.

regards.

[Stefano]

Re: Problem with External System Translations for OUTBOUND/INBOUND

HEllo All

I write to close my issue to put informations on the forum that could be useful for others.

At the end we solve problem enables properties to remove Namespace from XML produced by OTM, this could be new feature on 5.5. and impact on our XSL translation working on 5.0, so we put
glog.integration.enableXmlNamespace = false on GLOG.PROPERTIES, re-start and extarnal system translation come back to work...

COnsider also that now are introduced XML profile and default are GLOG MIN , so if you xsl transformation are based on not mainly fields, perhaps you have to specify in external system GLOG

REgards.

[chrisplough]

Re: Problem with External System Translations for OUTBOUND/INBOUND

Stefano,

Just wanted to take a minute to thank you for coming back and updating the post with a resolution. It really help us build a knowledgebase of solutions, rather than just a bunch of half-answered problems. It's much appreciated.

--Chris

[Stefano]

Re: Problem with External System Translations for OUTBOUND/INBOUND

Chris,
I agree with you infact I post my solution hoping that this could helpful for others ..
I lost a lot of my "ZZZzzz" on it ...so

Ciao

[mkenney]

Re: Problem with External System Translations for OUTBOUND/INBOUND

We also had to remove the XML Namespace using the properties to get our processes that deal with the outbound XML working in the 5.5 environment. The errors we were getting were not descriptive so this took a while to find.

I wish I had read this post first!

Much appreciated Stefano, and good information that I think will help people a lot.