DSXchange

Yes...you can automate it, but it's not particularly easy. I haven't done it in awhile, but last I recall, in (maybe) 8.1.2, it worked like this: (this is from memory, and in testing with Seq Stage, but it should give you a start to play with)... a) match the exact full path and filename in the prop...

Highlight the Operation's input in the wsdl importer and then use your right mouse.....this lets you open that message in the xml importer.....and then pick the elements you need....it could be more complicated than that, but that's the basic starting approach that you will need.

Ernie

I would suggest that you import your ERwin model (it will actually be the physical, since there is no logical model import at this time)...when you do, give it a host and/or database name that suggests that it is for the logical model.... Then import your other metadata (now in Excel) directly from ...

The easiest way to do this is via "Data Item Binding".... You have already created the Data File, so you know how that works (via Create Shared Table from Table def --- right mouse from your DataStage table Def while inside the designer --- and make certain first that your Locator says &qu...

A bigger question these days is "does anyone care"? CWM was a big deal 10+ years ago...but if you dig around, many of the resources, articles, etc. regarding CWM are all very old, and even the 1.1 standard at the OMG site is dated 2003. It used to come up all the time in discussions and so...

...and it is a best practice not to include CRLF's or extra spacing..it's just "noise" making your xml document larger. Nowadays every decent browser, editor and tool knows how to format the document for viewing. Specify NO formatting, regardless of what tooling you choose to write your xm...

On the first one, the only thing I can think of at the moment would be to create another file (on a separate link, perhaps from a transformer immediately upstream from your xmlOutput) that writes out as many rows as you are creating files from xmlOutput....have that sequential file contain the "...

As Vincent notes, you don't need to capture "all" your Talend details....but you most certainly can capture "key" parts of it..... First, take a look at your Talend transformations..which parts would be most interesting to a Business Glossary or Metadata Workbench user? Evaluate ...

Call your support provider...there is a patch beyond 8.5 fp1 to the Library Manager for handling really big xsd's.... (btw --- the new 8.5 stage does not use the xml metadata importer, but instead brings xsd's into a new "library" concept)...

Ernie

As you discovered, the "input" link column grid of the xmlOutput Stage is the real driver of the logic to construct the xml content. It's a bit counterintuitive, but the output link column list is really just the "receiver" of the final created xml.

Ernie

From what you've told us thus far, I don't think so (re: are you biting off more than you can chew)....but more detail is needed....the size of the xsd will impact your "design work", but has nothing to do with the run time....a HUGE xsd could still generate 100's of thousands of tiny &quo...

What do you need? Be creative...you can represent just about anything you want using Extended Data Sources...and then use Extension Mapping Documents to link those "things" into other "things" (tables, etc.). I have done it many times, especially for representing BI reports from ...

That was the perfect solution, and "by design". The XML data element is intended for those situations when YOU are taking sole responsibility for building xml -- which has to include escaping any characters that require it.......

Ernie

There are no short cuts. The notes above are a real good "cheat sheet"...my blog on lineage is a "cheat sheet"....the point is..there are a lot of things to go thru. Pick one and get started. Ping us if you get stuck.

There's a lot to read because there are a lot of things to consider... ; ) Work first on bringing in actual database tables...via ODBC or via Connectors (best way)...there are a myriad of other ways also. Get familiar with what you see, and how they relate to each other (columns/tables/schemas/hosts...