I wish to be able to set up DTS namespaces, property types, and association
types via scripts. To create these things interactively in different
environments - dev, test, prod, - is tedious and subject to error.
I have the java API examples for these things, but a higher-level technique
would be appreciated - even SQL if there is no other way.
Jon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have been using TQL to export to Excel from the development environment.
Then in the next environment (Test) we interactively created the property
types and association types, and then used Import Wizard to load that content
into TEST.
I see (in the import wizard user guide) that the wizard can set up the types
automatically if the input file is DTS XML format; Therefore I will be looking
into how to generate that from the development environment.
Jon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Resolved! We have been using TQL to export the content to excel. We simply
need to specify the .xml extension onto the output file name (in the tql
editor’s “Output file: field) rather than .xls.
Thanks anyway!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wish to be able to set up DTS namespaces, property types, and association
types via scripts. To create these things interactively in different
environments - dev, test, prod, - is tedious and subject to error.
I have the java API examples for these things, but a higher-level technique
would be appreciated - even SQL if there is no other way.
Jon
More info on this issue:
We have been using TQL to export to Excel from the development environment.
Then in the next environment (Test) we interactively created the property
types and association types, and then used Import Wizard to load that content
into TEST.
I see (in the import wizard user guide) that the wizard can set up the types
automatically if the input file is DTS XML format; Therefore I will be looking
into how to generate that from the development environment.
Jon
Resolved! We have been using TQL to export the content to excel. We simply
need to specify the .xml extension onto the output file name (in the tql
editor’s “Output file: field) rather than .xls.
Thanks anyway!