DSXchange

First, the table definition in DataStage needs to become a "Data File" as known to Metadata Workbench. The easiest way to do this is by opening the tabledef and first checking its "Locator" tab....be sure that it says "Sequential" in the pull down at the top (you can ty...

...suggest that you start a whole new topic for this, but basically, the lineage for "Data Files" is established by seeing if the fully qualified name in the Job at run-time matches the entire "Data File name" (complete with path details, etc.), or more appropriately, the "P...

If it only happens with random calls, then you have to look elsewhere...that means that the configuration is correct... Someone on the MDM side will need to understand what causes that error....you will need to work with your support provider.... if it is random, it could be many things: a particula...

That is not an ISD error directly....the MDM application must have issued it.....You may need to call your support provider, but before you do, here are some key things to check: a) does it happen with every single call that is ever made from MDM? ...or randomly? b) are other service operations at t...

(which is why I suggested an rdbms...then they go right in, are committed, and you can remove them....all while the job is running).

at least "one seat" was needed in order to do the install.....but it certainly isn't "per" each BG user. ...and indeed as Ray notes, you'd have to be "using" that seat in order to drill down to the WB from biz lineage.

answered already in another thread.

answered already in another thread.

No...you can't see the data unless you decide to write it somewhere such as an rdbms (with commit=1)....that's not necessarily advisable, as it could introduce performance issues, but when you are debugging, it works great. Just branch from a transformer to a target and make sure that the link to th...

Right...you only need "at least one" MWB user in order to have lineage and also to customize (if desired) the Business Lineage.

Ultimately though, check with your sales contacts. I'm just the "technical guy" ; )

Ernie

Lineage is defined for an "asset" that might be assigned to Term (a table, a column, an application, etc.)....

...and yes, in order to view Business lineage from inside of BG, you need to have Workbench installed and available (at least one seat).

Ernie

Yes...but a separate topic. The xsd can help generate the tabledef(s), but is critical if you want to perform formal xml "validation". With xmlInput Stage, you can generate the metadata for the output link any way you want, even hand type it, and still do validation by the "run time&q...

another thought came to mind also....

check the encoding value at the top.... see if it says something like encoding="UTF8" or similar, try a run in with a sample version of your xml document where you remove that attribute from the header entirely.

Ernie

as noted up above, it at least "looks" like External Source is now working great! Now look at your xml document. Does it have a schemaLocation attribute? This points to a schema. Unless you say you want validation, which you should NOT have checked at this time, it shouldn't be looking for...

for xmlInput stage, it has to be part of the current incoming document, fully qualified within the NoNamespaceSchemaLocation or SchemaLocation attribute in the header.

In the xml Stage, it is "the" formal xsd "library" that you import during design time.

Ernie