Originally posted by: SystemAdmin

Hi,
I am a newcomer to the DataStage TX and am trying out the Map Designer and am hoping if somebody could help me out...
I have built an Input Type Tree from an XML Schema(with Target namespace="ABC") and an Output Type Tree from an XML Schema(with Target Namespace ="CDE").
I need to map an Element XYZ in the output from an identical Element on the Input(however belonging to a different namespace). Is there anything I need to do specific with the attributes on the output to achieve the desired result.

Thx,

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

Originally posted by: SystemAdmin

Hey SJ

Target Namespaces shouldn't affect your mapping in any way, except in the xmlns you put the namespace declaration.

You should just be able to drag and drop from input to output, assuming that the field properties are not dissimilar.

Are you experiencing any particular issues?
Regards

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

Originally posted by: SystemAdmin

Hi Tarun,
What's happening is that on the Output side, the element ABC has two child nodes, the AttrList(which I have set to NONE) and Value. When I drag and drop from the Value of the Element from the Input side to the Value on the Output side, I see in the traces that it always evalutes to NONE. As for the properties, the only difference I see is that the value of the Description field in the properties point to the different/respective Namespaces.

Thx,

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

Originally posted by: SystemAdmin

If you want to use a namespace like xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
you would set the prefix to ":xsi" and the url to "http://www.w3.org/2001/XMLSchema-instance"
in the AttrList
Then drag the data value across.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Thx Guys for your leads, I was finally able to get the mapping going. Also, does any of you know how to turn off Validations totally in the Maps. I have the Document Verfication field set to NEVER.
The reason I ask is one of the fields in the Input was TelephoneNumber which is defined to be of a Numeric Type and had non-numeric content in it and so the Map kept failing.
Is there a way to turn validations off totally and copy the value as is. The reason I ask is there is some other process after that does data validations and hence desirable that the maps not be doing it.

Thx,
SJ
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Hi SJ,

Can you please tell that how you resolved that issue?

I am facing the same issue here. I created a type tree using WSDL importer. WTX is giving an error called INITIATOR is not matching- it seems the issue with namespace soapenvelope: and the schema url. I am not sure that what we should configure in type tree properties. Please help me.

Thanks and Regards,
Lakshman.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Setting Validation-->PresentationError in the Map Settings to Ignore should do what you want.

img:ba64afed9fhttp://home.att.net/~jim.divoky/MapSettings.bmp[/img:ba64afed9f]
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Might be better just to re-define that one field to be text.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Folks,
Thanks for your input. Both of your suggestions seem to work. Was wondering if there is anything similar on the Output side. The Output type tree was also built using a Schema and what(if any) would be the process to removal all Validations/Restrictions.
For e.x. all elements in the Output type tree have max length restriction. If I wanted to remove this restriction and map them as is from the input, what steps would I have to take.

Thx,

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

Originally posted by: SystemAdmin

If you change your max length, you are breaking the rules of your schema. Max length is there for a reason. If it is too large on input it should be flagged as an error. You should only be able to create output which is valid for the schema.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

The reason I ask is as I had stated earlier there is a downstream component that does Schema and Data Validation and hence was trying to use the Map Designer as a plain Data Mapping tool.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

DSTX doesn't perform output validation. I believe all you will get is a warning at build time which may be ignored. Try it in a map and you'll know for sure.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Jim is correct that output validation isn't done but the tool does enforce field lengths so your data will be automatically truncated. It's best to check the build warnings and figure out which fields will be affected by the field length issue and then remove the max length on those fields in your tree if the validation will be done downstream.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

I verified that the output validations do not happen, however the fields are being automatically truncated. Besides, removing the max length on these fields, are there any other alternatives. The reason I ask is because every field in this particular case has a max length restriction.

Thx,

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

Originally posted by: SystemAdmin

Based on your last question, it sounds like the schema doesn't do a very good job of describing the data. If the data is large than it should be, then it is not valid. If the data is OK, then the schema should be adjusted.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender