Page 1 of 1

Trends for deployment of your production DataStage Jobs?

Posted: Tue Apr 21, 2009 10:49 am
by eostic
Hi all...

Wondering specifically if many/any of you deploy "only" executable Job details to your production servers, or if you also include the Design metadata?

(specifically, the export option of "Executables without Designs").

If so, why or why not? Do you use the read-only feature along with migrating design info? ...or other alternatives.

Thanks in advance!

Ernie

Posted: Tue Apr 21, 2009 12:56 pm
by kduke
Production is always read only to developers but we always do designs. It is easier to debug. It is also impossible to tell if production has the correct version unless you can see the design.

Posted: Tue Apr 21, 2009 1:17 pm
by ray.wurlod
... or use the Version number field.

Posted: Tue Apr 21, 2009 10:11 pm
by kduke
We are using the comment field in job properties but they don't always update it.

Posted: Wed Apr 22, 2009 4:21 am
by sima79
We use the option "Export job designs without executables". All code goes through our source code control procedure. Code is promoted through each environment dev->test->prod. The source code is imported into each environment then compiled. Good source code control should minimize the chance of deploying the wrong code.