XML input stage behaving differently across installations

[dsguyok]

We have two environments with Datastage 8 and the XML plugin installed on both.

I have a job which uses the XML Input stage to read in filepaths from an External Source stage. It uses these filepaths to read in XML file content and then loads that XML content on to a queue.

The same job works fine in one environment but fails/warns in the other with the same test data.

In the failing environment the XML input stage appears to be looking for a XSD file referred to in the XML files' namespace. When it can't find it, it complains. No such problem in the other environment.


This is the error/warning message on the XML input stage:

Code: Select all

XMLinput_listToRecs,0: Warning: listFilesToQueue.XMLinput_listToRecs: XML input document parsing failed. Reason: Xalan warning (publicId: , systemId: , line: 0, column: 0): An exception occurred! Type:RuntimeException, Message:Warning: The primary document entity could not be opened. Id=/opt/infosphere/projects/DMData/log/outfiles/ResubmitJJJJRequest.xsd

This is the offending namespace:

xsi:schemaLocation="http://www.abcd.com.au/Namespace/Generic/Service/V1.0 ResubmitJJJJRequest.xsd"

Any ideas? Could it be a Xalan/java config problem? Thanks.

[eostic]

Hard to say. Patch levels maybe? Namespaces had a variety of issues in early 8.x.

Ernie

[dsguyok]

Patch levels maybe?

The environments are at the same patch level which is "no patches". We will look at installing the fixpacks. We're running Datastage v8.1

Does Xalan get installed with Datastage?

How can I check the version number of Xalan on AIX?

[eostic]

Can we assume that these two environments are also the exact same operating system?

Ernie

[dsguyok]

Can we assume that these two environments are also the exact same operating system?

Yes they are both AIX.

[eostic]

At the moment I can't think then, of why one environment would work and not the other.....I will assume that you have carefully checked both jobs, and that neither of them have "validate" checked, and that they are both truly reading the exact same documents. As noted earlier, namespaces created a host of issues in early 8.x...at one point I recall having to manually zap them out of the input documents in a transformer prior to the xml stage, but that's harder to do when you are using the External Source.

Ernie