Originally posted by: SystemAdmin

Hi,

I have a question regarding the usage of complex xml schema structures (OAGIS uses a lot of imports) and TX 8.2.0.0 on Windows. I'm evaluating if TX is an option for mappings from and to the OAGIS standard.

I have tried to create a type tree of the message which seems to work fine however but I run into problems when trying to build the map, the design studio just crashes. I have also tried using the native XSD support but this fails once I try to assign the type to the input card and I get an error message that it cannot find the schema file. The documentation does not say if import is supported when using native schemas or not.

So I guess my question is of anyone have encountered similar problems and have any recommendation when working with complex schemas in TX. If you know of any examples or documentation about this that would also be great.

Any guidance in this matter would be highly appreciated.

BR

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

Originally posted by: janhess

You need to use the latest version 8.2.0.3 which fixes a lot of xml bugs.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

It imports ok into 8.2.0.3 for both Classic and Xerces but uses lots of memory.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Hi,

Thanks for your help. I managed to create a valid type tree with the lastest version of design studio.

However the native schema support does still not seem to work for schemas using imports.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

What error are you getting? It worked fine for me once I had downloaded all of OAGIS - OAGi-BPI-Platform-OAGi-platform-1_0-GA.zip & OAGi-BPI-Platform-OAGIS-9_3-GA.zip - and imported OAGIS.xsd. There were warnings generated but these were as expected.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Hi Again,

My bad. I did the new test in an old tx project. When I created a new project it I was able to use it as an input card.

However there seems to be some problems for some complex types. Once the input card is created and set to the root element, I expand the structure and look at any element defined by the OAGIS IdentifierType, like BODID or DocumentId. There are two identical instances of the "value" definition in the input card and when testing this none of these values seems to hold any data from the test xml file (validated in xmlSpy).

When using the Type Tree definition I run into different problems where TX fails to identify the correct type definition for some elements. I use the same test file as in the test of the scenario described above. I have verified that a test file with only the DocumentIdentifier works fine. But when I add some other complex elements to the testfile I get the following error:

Error (-9), "XMLParser: Could not find type to assign XML data."

The added complex elements belong to the same namespace as the root element so that shouldn't be the problem.

Once again your support is very much appreciated.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

Can you post some example xml?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

I have attached the testfile I have used.

This is based on OAGIS v9.0 ShowPurchaseOrder BOD.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: janhess

I think you need to run this against a type tree imported from oagis.xsd. The xml doesn't quite match this and appears to have some mandatory elements missing from ShowPurchaseOrder. I'll keep playing with it but my PC isn't up to the size of this typetree.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

I cheched your xml against the schema and it is incorrect. It contains a tag <ScheduleTimePeriod> which is not in the schema.
If you look at the example in the download in C:\oagis\OAGi-BPI-Platform\org_openapplications_oagis\9_3\Instances\BODs\ShowPurchaseOrder.xml it has a different structure. This example works ok with the generaterated type tree though I had to add a tag <OAGIS9BODs></OAGIS9BODs> around the ShowPurchaseOrder to get it to work with the full type tree. If you need an example I can post a map and type tree.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: janhess

I checked your xml against the schema and it is incorrect. It contains a tag <ScheduleTimePeriod> which is not in the schema.
If you look at the example in the download in C:\oagis\OAGi-BPI-Platform\org_openapplications_oagis\9_3\Instances\BODs\ShowPurchaseOrder.xml it has a different structure. This example works ok with the generated type tree though I had to add a tag <OAGIS9BODs></OAGIS9BODs> around the ShowPurchaseOrder to get it to work with the full type tree. If you need an example I can post a map and type tree.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Hi,

Yes if you could upload an example I would be grateful. I think the problem with the time period might be due to that we have two different versions of OAGIS. In my test the validation fails on the SupplierParty element so it does not seem to be related to the TimePeriod bit of the sample file.

I have also just imported the ShowPurchaseOrder BOD and not the complete OAGIS standard.

I have made some additional tests on this and I think I have found a similarity for all elements that fail validation (where the type cannot be found). All these elements like SupplierParty or Item has the xsi:type attribute that somehow are related to the problem. I have tried to specify the target type definition in this attribute in the test file but it does not seem to work.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

In the attached example, I built the classic type tree using 9_3 version of oagis.xsd. I removed all the junk from Global and made the bods optional so it handles any bod. The input xml is from the examples provided in 9_3 but with the <OAGIS9BODs> added. I raised the question of all the bods being mandatory within the metadata schema and the reply was to use the individual bods - I didn't fully understand how oagis was used.
However this type tree from the metadata may prove useful.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Hi,

I have found the problem why the input message failed validation when executing the map it had to do with how I had configured the input card, I used the root element of the definition and not the DOC definition. The only trouble with this is that all elements are listed and that does not give a good overview of the input card.

There is still another problem with the mappning though. Some values of the elements don’t get mapped. I have also tried to create an output card that is just a copy of the input card and only about 5 of the elements in the input file appears in the output file. The elements are recognized when validated but the mapping of these elements does not seem to work. And I don’t get any errors or warnings in the trace/log files. Are there any known problems to any specific schema constructs?

BR
Albin
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender