Export Jobs to ATL from BAT file

[Former Member]

Hi Experts,

I would like to know how to export jobs into .atl files with Data Services XI 3.2 using al_engine.exe from a BAT file.

I found some tips but I am unable to get the same ATL output file as from the GUI export.

%LINK_DIR%\bin\al_engine.exe" -NMicrosoft_SQL_Server -Ssqldb -QDSRepo -Uuserid -Ppswd -XpJ@jobname_JobBt.atl@jobname_JobBt@D

I want to exclude the DataStores and export a single job to a single ATL file.

This will allows us to keep versions of the jobs in an SVN library for source code versioning.

I have been able to import the ATL files with this method thanks to sample BAT file from:

http://wiki.sdn.sap.com/wiki/display/Snippets/DataServices-ATLImport+Automation

I have been able to export the entire repository with the -X parameter successfully.

%LINK_DIR%\bin\al_engine.exe" -NMicrosoft_SQL_Server -Ssqldb -QDSRepo -Uuserid -Ppswd -X

Kind regards,

VA_pdj

[Former Member]

Hi,

as far as I know, you cannot export ATL files the way you are planning to do (you probably could write a script that removes the unwanted information, but that might be cumbersome).

What you can do, though, is to do an XML export. Thus, in case it would be acceptable in your situation to use the XML import/export, you could use the functionality from al_engine (I only tried with the windows version, maybe it is different under Linux/UNIX).

You could use the following command

al_engine.exe -NMicrosoft_SQL_Server -UUserID -PPassword -Shostname -QRepo -XX@J@filename@jobname@D

If there is a function to do this via ATL, it is well concealed.

[Former Member]

In the documentation it shows a -Xp command to export ATL files (vs. the -XX for XML).

Just have not been able to get it to work - it does not seem to recognize the "@" separators - files generated contain the "@" in the exported file names.

[Former Member]

That was what I meant. The -Xp parameter does not allow tweaks like exporting without datastores. Only the -XX parameter does allow to do that. The -Xp parameter helps you to export all objects of a certain type at once but you cannot selectively export them. That does only work with -XX.

[Former Member]

Unfortunately, I am unable to get the -Xp parameter to export anything other than the same as the -X parameter (whole repository) - or it outputs just 2 lines with the repository version.

[Former Member]

I know. That is why I was suggesting the -XX parameter that allows to export to XML. We are currently looking into using that to be able to use version management through SVN. It is still a text format that allows to use diff to see which changes were done.

[Update:

After having looked into this I think I understand your problem better. There is no way to script the import of XML job files or is there?]

Edited by: Christian Wunderlich on Jan 9, 2012 9:11 PM

[Former Member]

The IMPORT uses ATL files with the -f parameter. Seems very strange that we cannot EXPORT our jobs into ATL files using the al_engine.exe process - except for a full repository dump. I would think it would be an obvious need - to both import and export the same format. Exporting into XML and importing using ATL files does not make sense.

Just a little frustrated.

[Former Member]

I found a solution - but it is based on XML. You can export an object the way I described above (-XX parameter etc.). This file you can store in SVN. It will contain the object (e.g. a job) and all depending objects (for example Work Flows and Data Flows), but not the datastores.

To import the objects as XML (I tested this a couple of time just minutes ago) you can use the following command to import:

AL_ENGINE.EXE -XI%filename.xml

(I omitted -S, -Q, -U, -P parameters for easier readability).

This still does not allow you to export to ATL but you can export any object as XML and import it again as XML into a repository. The import will overwrite existing jobs or create a new one if it does not yet exist.

I hope this will help you, too.

[Former Member]

Thank you for your XML solution - unfortunately we already have all of our jobs in SVN in ATL format, so changing to using XML files is not going to fly.

It is unfortunate that the al_engine.exe process does not appear to be working for Export of individual ATL jobs.

Wonder if it is on the SAP radar to get it working properly eventually.