How to export jobs along with datastores ?

Hi ,

In a migration porject, can we export the old ETL jobs to a new project and edit them and run them ? How to export these and are there any issues in doing so ?
Can we change the datastore properties and import them back again into the repository ?
8)


jbodi (BOB member since 2011-09-07)

2 Things about Export:

  1. Exporting the entire repository into an .atl file like
    Right-Click in a blank space in Local Repo–>Repository–>Export to file and you could save it as an .atl file or .xml file also

  2. Exporting individual Jobs/WorkFlows/DataFlows/Custom Functions/File Formats/DataStores individually the objects or with their dependents using
    Right-Click on the specific object–>Export and a Window would open on the Right Pane and you could include/exclude specific objects

One thing you cannot do for sure is Exporting a Datastore and changing its parameters. Especially passwords you cannot, because they are encrypted when you export.

Again, the Technical Manual should help you lot more.


ganeshxp :us: (BOB member since 2008-07-17)

I got them to export. It worked fine and if i want to import them I tried by import from file …but nothing happened but data services struck.

How shall import other way ? and see if they work if i try to run?


jbodi (BOB member since 2011-09-07)

How much jobs you exported? I think you are exported very huge. Why don’t you use the concept of Central Repository for this?


ganeshxp :us: (BOB member since 2008-07-17)

I just tried with a small test DF 1 table mapped to a query and to a template table.

I wanted to see how would this work if i want to change to diff, repository along with with new data stores


jbodi (BOB member since 2011-09-07)

If you don’t mind can you explain the requirement of changing the Datastore? This part I am really not able to catch up?

Inspite of that, the Designer shouldn’t hang for importing such a small DF… What shows up in the Task Manager when you import? See how the AL_Designer.exe grows to? And see the CPU Graph…


ganeshxp :us: (BOB member since 2008-07-17)

I need to show dat a job can be exported as an ATL instead of creating a same new job again.
But while doing so i need to put a different table as a source in the imported ATL.


jbodi (BOB member since 2011-09-07)

Practically, directly you cannot change the sources the way you request. Still I am not clear of the reason.
Only way is to manually change the Table.

But there are plenty of concepts like Aliases, Datastore Config with which we can play around.


ganeshxp :us: (BOB member since 2008-07-17)

What if I replicate a previous job and use it for a different job as the logic is same, but concern tables are reloaded with different datastore ?
Can I do that or do I need to do all over again developing ? If Yes are there any issues I need to make before I start to replicate one by one ?

Thanks in advance.


jbodi (BOB member since 2011-09-07)

Hi

So are you going to load the table with exact same names from a different Datastore? Why should you do that? Why don’t you use the various Datastore Configurations for that?
In the same Datastore, you can configure a 2nd Database connection and use it.

Only thing is if your tables changes then the only solution is manual development/modifications.


ganeshxp :us: (BOB member since 2008-07-17)