DSXchange

...let's hope that your namespaces and other details of the service don't change.

...I haven't tried this in awhile, but the "endpoint" property in the advanced tab of the WS Stage is paramaterizable --- meaning that you could just change the endpoint and the service will be invoked wherever it might be, even if the WSDL originally came from elsewhere.

Ernie

I would concur, or at least I can't think of anything else.... might be worth a support call. I don't know the history of this one back to 8.1....

Unfortunately I don't have access to an 8.1 right now, but it works in 8.7...I just did one where the xml document is on a web server and accessed via HTTP...... is your web server accessible directly from the DS engine machine?

I haven't tried URL access in awhile --- exactly what release? Also, make certain that it is getting the correct string via the folder stage.... I would test initially instead with a Transformer going into xmlInput, and just hard code the URL into a Derivation as a simple string (in a single big col...

What release? Make sure your table names are fully qualified (schema.table). Make sure your server string in the Stage is mapped for the correct Stage type and to the correct host.database where schema.table above exists. Check for spaces, mixed case, etc. Be sure that your default values exist in e...

mine allows multi-select. ...well, you have to select "all" of them (there is no "partial" workflow at this time. It's an option in the pull down. Wish it was an "up top" check box, but the pull down works.

Ernie

no......a REST API call would be nice, but no....

The Stage names do not have to be the same. There are various things that Metadata Workbench looks for when performing lineage on DataStage Jobs, Alias (really, the "string" that is used in the Stage for your database) as Vincent notes, being one of them. spend some time reading thru this ...

Hi Ray... I've done it on a variety of occasions, each time by being creative with Extended Data Sources and Extension Mapping documents. First, let's consider the "process" itself. The Teradata procedure, BTEQ, Autosys "thing" or whatever it might be, will typically be represent...

Exactly. The job never is "finished" when running in that fashion..instead, target an rdbms table that supports commit=1, and then get your data from there as you wish.

Ernie

Wondering if anyone has integrated non-bridge supported BI tools into Metadata Workbench? There are various ways to do this, using manual .csv files as opposed to the formal Import/Export Manager. Typically this is needed for reporting tools that are not supported by either the Import/Export Manager...

What exact release of DataStage and what method are you using to do the import? (Import...TableDefinitions....XML Definitions.... -or- The Library Manager of 8.5 and 8.7) ? If it's 8.5 or lower, create or find a fully populated instance document instead, and do your import on that. You should still ...

...maybe it's my browser, but I don't see the error that you indicated.... please re-post your error, describe exactly what you are trying to do when you get the error, and your exact release of Info Server.

It shouldn't be any different. The WSDL Metdata Importer will simply read the wsdl from disk or from the web.... you get it to disk simply by going to the wsdl yourself in your browser, and then saving it. Best bet right now is for you to try and find another service that also has no input arguments...