Originally posted by: SystemAdmin

I have created a TypeTree by importing an XML Schema based on an OAGIS specification. The type tree generated numerous warnings when I analyzed it, however I am still able to map data TO the tree and create a valid XML document as output.

However, the problem I am encountering is when I try to use that same type tree to bring in that XML document as input to another map. I get an error message when I execute the map that states "One or more inputs was invalid". This doesn't make sense to me since I am using the same tree on the 2nd map's input as I used in the 1st map's output.

I have run a trace to try and figure out what is wrong with the XML document and why it supposedly contains invalid data, however determining exactly what is wrong with the input is proving to be somewhat futile since trying to read the DataStageTX trace file in this case is like trying to read Mandarin.

I'd be glad to supply the tree, map and XML file if anyone thinks they can help me on this.

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

Originally posted by: SystemAdmin

Actually, it does make sense. No validation is performed on outputs. Therefore, your output data does not have to match all the requirements of the output type tree. By default, your data is validated on input and may well fail if required fields are empty or values fails restrictions or formatting.

You didn't specify what version of DSTX or Mercator you are on. It does make a difference. The XML importers have improved with age. I recently attempted to import the incredibly complex IAA Model into the Type Tree Designer 6.7.1 and it just wouldn't work. There are limitations to the importer when dealing with very complex schemas. I converted the schema into a DTD using XMLspy and was able to successfully import it. You can download an evaluation copy at http:\\www.xmlspy.com. You might also want to verify that the OAGIS schema validates successfully in the first place.

I often find I have to make minor adjustments to schemas, DTDs, and/or type trees before beiing able to map successfully.

Send your files to me at jim.divoky@ec-solutions-inc.com and I'll take a look at them tonight.

Jim DIvoky, EC Solutions, Inc., 330-606-6826
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

The main reason for xml output to fail as input to another map is mandatory fields have not been given a value. This results is empty tags or sometimes invalid xml. Make sure all your mandatory output is completed.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Jim,

Thanks for the advice - what you are saying about validation also now makes sense - you are absolutely correct. I will take it to heart and try a couple of your suggestions.

Also, I do already have XMLSpy, and yes, the schema validates fine using that tool. However, I have not tried to convert the schema to a DTD. I will try that although I don't know how much success I'll have as it is a complex schema with many includes. Won't that affect the conversion to a DTD?

Additionally, I am using DSTX 7.5 to do all of this, so I believe I am using the latest and greatest version. One thing I am wondering is what kinds of slight changes are you making to type trees generated from an impported schema? What specifics should I be looking for? I guess I still need to learn/understand exactly what needs to be changed/modified. I will try a couple of your suggestions before I burden you with any my files. Thanks again for your input.

Matt Lincoln
Computer Analyst - Salt River Project
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

You may want to use XMLSpy to try to validate the XML data that you created with your map. If errors are found it may be easier to read than the trace file ;o)

One possible 'gotcha' in xml data mapping is making sure that your xml tags are all properly formatted. For example the trees created by the xml schema importer in DSTX6.7.x are subtly different than the trees created in DSTX7.5 - one difference another customer ran into was that the "/" in the end tags was moved from the one level to another (in this case it used to be the terminator on the group but migrated to be the terminator on the last component of the group). XMLSpy is good for finding and reporting such errors.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

The changes I was thinking of might be that you are receiving a batch of messages while the schema describes a single instance. That will require you to add a level to the type tree to account for multiple messages. Another was a few releases back empty data elements of the form <Tag/> weren't handled by Mercator and required a fix. I sometimes find things to change but not always. I wouldn't worry about them until they occur. The XML related importers work pretty well and sure are a lot easier than creating XML type trees from scratch as was required a few years back.

Jim Divoky, EC Solutions, Inc., 330-606-6826
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

There is only one record per message, so iterative structures are not really the issue here. Jim, I have sent you an e-mail with all my materials. Take a look please if/when you have the time. Many thanks.

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

Originally posted by: SystemAdmin

Why not validate your xml in xmlspy?
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Hi Jan,

Actually I did use XMLSpy to validate it. That was the problem. It validated using that tool, but when I try to use that XML file as input to the DSTX map, it comes up with errors. Jim was nice enough to make some suggestions that I am looking into. I'll let you all know how it goes. Thanks again for all the feedback and responses.

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

Originally posted by: SystemAdmin

We have had issues with using Oagis BODs with overlays. Check the date formats of your output. We had to change the date formats because the maps did not generate the date/time correctly.
Also, when you open the XML file in some tools, it modifies the BOD, and can cause it to fail when used as input to another map.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender