Posted: Fri Mar 17, 2006 1:22 pm Post subject: Complex XML with alot of import/includes failing
Master
Joined: 19 Feb 2004 Posts: 259 Location: Flagstaff AZ
I am trying to bring in a message into the MRM by importing an XML Schema. The schema and all it's supported files is large (8MB).
When I just bring in the schema file I get several errors about unresolved base types. All of the base types are in the import/include files in the schema definition. However, there are dozens of these files.
I am trying to map a GJXDM message. The GJXDM is huge and this message is using a subset of the GJXDM and is still 8MB.
How do I get the environment to see these import and includes?
Do I have to import them all into the workbench also and then have the main schema reference the imported schemas?
My first attempt at this failed with an unspecified error (Please contact IBM....error message) and my environment became unusable anyway as a save took several minutes and then when I tried a simple mapping the save crashed....
Posted: Mon Mar 20, 2006 5:09 am Post subject: Large Xml Schema
Novice
Joined: 21 Feb 2006 Posts: 19
Klabran
I had a similar problem in attempting to bring in a very large schema with imported sub-schemas with the unspecified error showing up when I attempted to prepare each schema as individual files within the same message set. I am working on version 5. The subschema where the problem arose was the bottom largely defining the individual items.
I am now going to try a smaller subset, but still with the imports and shall keep you informed.
Joined: 19 Feb 2004 Posts: 259 Location: Flagstaff AZ
John: Thanks for the confirmation. I was able to eliminate all 600 warnings about unreferenced xml items by importing every single subshema into the toolkit. Unfortunately, this was incredibly time consuming. I had 50 schema's to import and the entire process of importing them into the toolkit took almost all day (about 6 hours).
Kimbert: I have messed with the java heap and I have turned off validation of xml and xml schema's when just saving a resource.
However, It appears that at least on my box (2GHZ and 1GB RAM) that mapping these large schema's is out of the question.
The save takes at best 6 minutes for any change made in my mapping node.
I think my only chance with working on these files is to code it entirely in ESQL and/or use the stylesheet node.
It is stated when reading up on IBM's website that large messages are "intensive" processes.
Joined: 19 Feb 2004 Posts: 259 Location: Flagstaff AZ
Does anybody know why the toolkit is brought to it's knees on this???
I have added RAM to my computer (now 2GB) which I wanted to do anyway but the additional RAM does nothing even if I tell the toolkit to use almost all of it on startup.
I have gone into preferences and have told the toolkit to not validate the XML or mapping on save or manual build and it doesn't do a thing.
Is there anyway I can get the toolkit to react in an acceptable time???
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum