ISD 11.3.1 SOAP based web service questions
Posted: Mon Feb 09, 2015 11:18 am
The DataStage job is using the ISD Input and ISD Output stages.
1. ISD is taking the DataStage job columns have a DATE data type and converting them to XML dateTime data type in the WSDL. Example output includes the date, a 'T', the time, and a dash with time zone appended. All we need and want is the date; the data does not contain any time or time zone values.
The only workaround idea I currently have would be to change the job to use Char or Varchar so that ISD would choose an XML string type that contains the date value.
I had expected ISD would have matched the DATE column up a little better by using an XML date data type instead. Is there a way to make ISD force an XML date type?
2. We have noticed that the column order not preserved between the DataStage job and ISD console where you add it as a provider. ISD mixes the column order up randomly. We did not encounter this behavior in ISD 8.7.
Technically, it may not matter once the consumers are automated, but here is an example from an interface documentation and testing standpoint. We have the interface documented with a particular column order, which the job was developed to (i.e. key columns at the top, many output columns following, and status columns and error code column at the bottom). Now a tester or consumer has tediously to hunt through all the output columns searching for the error code, and finds it buried somewhere in the middle.
Is there any way to have ISD preserve the column order?
3. This one is cosmetic in that ISD takes the upper case column names and converts them all to lower case, which we also encountered in 8.7. If you try to override the ISD operation editor, it says, "Variable names must start with a lower case character." It appears that the ISD software cannot be made to comply with corporate naming standards. Is there any way to get around this limitation within ISD?
1. ISD is taking the DataStage job columns have a DATE data type and converting them to XML dateTime data type in the WSDL. Example output includes the date, a 'T', the time, and a dash with time zone appended. All we need and want is the date; the data does not contain any time or time zone values.
The only workaround idea I currently have would be to change the job to use Char or Varchar so that ISD would choose an XML string type that contains the date value.
I had expected ISD would have matched the DATE column up a little better by using an XML date data type instead. Is there a way to make ISD force an XML date type?
2. We have noticed that the column order not preserved between the DataStage job and ISD console where you add it as a provider. ISD mixes the column order up randomly. We did not encounter this behavior in ISD 8.7.
Technically, it may not matter once the consumers are automated, but here is an example from an interface documentation and testing standpoint. We have the interface documented with a particular column order, which the job was developed to (i.e. key columns at the top, many output columns following, and status columns and error code column at the bottom). Now a tester or consumer has tediously to hunt through all the output columns searching for the error code, and finds it buried somewhere in the middle.
Is there any way to have ISD preserve the column order?
3. This one is cosmetic in that ISD takes the upper case column names and converts them all to lower case, which we also encountered in 8.7. If you try to override the ISD operation editor, it says, "Variable names must start with a lower case character." It appears that the ISD software cannot be made to comply with corporate naming standards. Is there any way to get around this limitation within ISD?