Originally posted by: SystemAdmin

Hello,

I have mapped the XML input to XML output...
The build was successful , but the Run produced o/p file like below.. there was no data.. but only empty tags..

What could be the possible reasons? Did I forget something?Please Help.

- <ims:DataArea>
<oa:Show />
+ <ims:Invoice>

• <ims:Header>
• <oa:DocumentIds>

<oa:CarrierDocumentId />
<oa:CustomerDocumentId />

• <oa:DocumentId>

<oa:Id IdOrigin="IDOC" />
</oa:DocumentId>..........................

Thanks in advance
PriJag

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

Originally posted by: janhess

Was the input valid? Have you mapped the correct items?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Yes the inputs were valid..I believe I mapped to the correct items...
I could get the attributes in the O/P , but data does nt appear.

I passed datas thro Fumctional map inside functional map till last level... Will that be a problem..?

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

Originally posted by: janhess

It will be if you have passed the wrong value to a functional map. Everything should go as an element or value. If any of the values to a functional map are empty then the functional map won't run.
Attach your map, typetrees and sample data and I'll have a look.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

I have included the type tree, input file and the map.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

Type tree ShowInvoice_2004-11-15a_IMS_1.3.mtt is missing. Can you add it.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: janhess

Your starting rule is wrong.
You shhould probably be passing INVOICE Element to a functional map in Global on the output card and map from there.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

Ignore the last post. You should be mapping INVOICE Element on Input to INVOICE Element on Output.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: janhess

These are simplified type trees with the 'rubish' removed from Global.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

I tried mapping INVOICE Element on Input to ShowInvoice Element on Output.But that does nt seem to work ;-(
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: janhess

Hardly surprising. I said INVOICE Element on Input to INVOICE on output which is further down ShowInvoice Element .
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

I can't test this without test4.xsd
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

INVOICE Element on Input to INVOICE on output which is further down ShowInvoice Element - This is how I mapped.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

I put together some mapping in the Header. I don't know what your mapping rules are. My output seems to work ok. Perhaps you can expand on this example.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

I've added more mapping using your functional maps.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Thanks a lotttt!.. It works... :)
I have a few more questions..Please answer these also..

Why WTX creates such complex type trees?
how did u cut down the unwanted elements from type tree-on wat basis?
why did u require the xsd file.. u could have created it from the xml...?


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

Originally posted by: janhess

This is quite a simple xml type tree. Try importing the xsd in classic mode then you'll get something complex.
When WTX imports a schema it created the Global choice Group containing all the Groups that appear in the type tree - I'm not sure why but there's probably a reason. If you look for the Group that is just used by Global in the Where Used property then you can delete all the other Groups from Global. Alternatively you just need to ensure that in your output card this is the starting point for mapping.
The xsd is required at run time as WTX uses it for XML validation. If I'd generated an xsd from the xml it would probably have ben diferent from your original.
Hope you manage to sort out the rest of the mapping.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

here is the o/p type tree.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: janhess

You forgot to attach it. Can I have some sample data as well?
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Sample data means input data? It is the Xml file..Test4.xml.
Output data is supposed to look like this..

<ims:ApplicationArea>
<oa:Sender>
<oa:LogicalId>XXXXXXXXXX</oa:LogicalId>
<oa:Component>XXXXXXXXXX</oa:Component>
<oa:Task>XXXXXXXXXX</oa:Task>
<oa:ReferenceId>XXXXXXXXXX</oa:ReferenceId>
<oa:Confirmation>0</oa:Confirmation>
<oa:AuthorizationId>XXXXXXXXXX</oa:AuthorizationId>
</oa:Sender>
<oa:CreationDateTime>2002-07-01T05:10:10-05:00</oa:CreationDateTime>
<oa:BODId>XXXXXXXXXX</oa:BODId>
<ims:Application>
<ims:InteractingApplication role="receiver">
<ims:ApplicationLogicalId>XXXXXXXXXX</ims:ApplicationLogicalId>
<ims:ApplicationName>XXXXXXXXXX</ims:ApplicationName>
<ims:ApplicationType>XXXXXXXXXX</ims:ApplicationType>
<ims:ApplicationCategory>XXXXXXXXXX</ims:ApplicationCategory>
<ims:ApplicationId>XXXXXXXXXX</ims:ApplicationId>
<ims:UserId>XXXXXXXXXX</ims:UserId>
<ims:SharedSecret>XXXXXXXXXX</ims:SharedSecret>
</ims:InteractingApplication>
<ims:ApplicationTransaction>
<ims:TransactionId>XXXXXXXXXX</ims:TransactionId>
</ims:ApplicationTransaction>
<ims:ApplicationStatus>
<ims:StatusId>XXXXXXXXXX</ims:StatusId>
<ims:LineNumber>XXXXXXXXXX</ims:LineNumber>
<ims:ErringApplication>XXXXXXXXXX</ims:ErringApplication>
<ims:ErrorCode>XXXXXXXXXX</ims:ErrorCode>
<ims:ErrorDescription>XXXXXXXXXX</ims:ErrorDescription>
<ims:ErrorData name="XXXXXXXXXX" type="XXXXXXXXXX">XXXXXXXXXX</ims:ErrorData>
</ims:ApplicationStatus>
</ims:Application>
</ims:ApplicationArea>
<ims:DataArea>
<oa:Show/>
<ims:Invoice>
<ims:Header>
<oa:DocumentIds>
<oa:CarrierDocumentId>
<oa:Id IdOrigin="XXXXXXXXXX">XXXXXXXXXX</oa:Id>
</oa:CarrierDocumentId>
<oa:DocumentId>
<oa:Id IdOrigin="XXXXXXXXXX" type="XXXXXXXXXX">XXXXXXXXXX</oa:Id>
</oa:DocumentId>
</oa:DocumentIds>
<ims:LastModificationDateTime>2002-07-01T05:10:10-05:00</ims:LastModificationDateTime>
<ims:DocumentDateTime>2002-07-01T05:10:10-05:00</ims:DocumentDateTime>
<ims:Description lang="en" owner="XXXXXXXXXX">XXXXXXXXXX</ims:Description>
<ims:Note author="XXXXXXXXXX" id="XXXXXXXXXX" type="XXXXXXXXXX">XXXXXXXXXX</ims:Note>
<oa:DocumentReferences>
<oa:ContractDocumentReference>
<oa:DocumentIds>
<oa:CarrierDocumentId>
<oa:Id IdOrigin="XXXXXXXXXX" type="XXXXXXXXXX">XXXXXXXXXX</oa:Id>
</oa:CarrierDocumentId>
<oa:CustomerDocumentId>
<oa:Id IdOrigin="XXXXXXXXXX...........
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender