CWM/XMI Export of ETL Jobs

[thomash123]

Hi all,

I would like to export a job I've built in the DI Studio 4.21M3 to a CWM/XMI file, that can be read in another metadata tool. How would I do that actually? All I can find is a functionality to trigger an SPK export.

Thanks and regards,

Thomas

[Patrick]

Hi

I've never done it but when searching DIS's help using keyword 'CWM' I find this entry: "Exporting Metadata with a SAS Metadata Bridge".

When choosing File/Export/Metadata I'm getting a long list of available export formats in my DIS instance (4.21).

HTH

Patrick

[thomash123]

I see, that did the trick. I was trying to export directly via right mouse click on the job.

But here it seems that I can only export tables and not jobs. Do I miss something?

Thanks,

Thomas

[nar_sas]

There is no CWM export facility for jobs, only for tables and columns.  One possible way to get CWM job output using some programming would be to first export the job into the  .spk package file which contains the  full job XML if you include associated objects such as physical tables in it.  Then write an XSL conversion on the job XML in the spk package  to convert it to CWM format.  Development does this sort of thing when it does differencing of job XML for versioning, which is coming in the 9.3 release of DI Studio.  The 9.3 differencing facility pulls out the job XML from the .spk package content, and runs an XSL conversion on it to make the view more user friendly.  You could do something similar to convert to another format.  The OMR metadata format is loosely based on CWM structures, so there would be a fairly close correlation to CWM object types. 

There has been a request to add this capability in the future, but no near term plans for it. 

Hope this helps,

nar@sas

[thomash123]

Hi,

as we are currently facing the same question: Has there been any update on this topic?

Thanks,

Thomas

[Patrick]

IT's still only tables according to doc: http://support.sas.com/documentation/cdl/en/etlug/65158/HTML/default/viewer.htm#n0zofifj793psgn1ss0a...

[Lars_Rishøj]

Hi all.

I'm currently engaged in a project using multiple technologies including SAS/DI Studio and a non-SAS Enterprise Metadata Catalog solution has been chosen.

Much of the basic data management are done using SAS/DI Studio (+500 jobs) with a typical job comprising 40-60 "objects" (tables, joins, mappings, business rules, etc.).

In order to establish E2E data lineage and impact analysis we need to registrer the flows, dependencies, etc. in the "Enterprise Data Catalog" to be used by Business, Data Scientists and Data Engineers based on common Glossary/Terms across the value chain.

Have tried to import a SPK exported out of SAS/DI Studio and imported into the Data Catalog, During the import it seems as if lots of objects are imported via the metadata bridge for SAS/DI Studio but of 55 objects in the SAS/DI job only 12 gets surfaced within the Data Catalog.

It sounds as if there is a way as the SPK actually contains all the right information but this is not supported by SAS's CWM/XMI export/import bridges.

Dispite all the major vendors wishes for a single vendor strategy, this is rarely (if never) the case in an enterprise organisation. Hence there is a need/request to be able to exchange metadata and integrate this in built for purpose Metadata Mgmt/Data Catalog solutions like Collibra, Alation, Waterline, Informatica, Talend, Oracle, SAP, etc.

So, since this is not currently supported by SAS (we need this) have anyone had success in exporting a SPK and manipulate the XML-structure to successfully import a SAS/DI Studio job/flow to any of the above technologies?

Thanks, Lars