Page 1 of 1

regarding jobparameters

Posted: Thu Dec 07, 2006 4:19 pm
by avi21st
Hi gurus,

i created user name and password to connect to the database as jobparameters, so that i can make use of them at run time.
this entirely comes in the development environment.
what happens when we deploy the data in the production environment.
how to deal with these parameters, i wasn't involved in the production environment earlier, now i have to involve in production env.
how to deal with these parameters in which i have given user name and password to connect to database as job parameters in production env.
plz help me.

cheers;
vijay

Posted: Thu Dec 07, 2006 4:29 pm
by I_Server_Whale
You can still use them when you migrate the job to production. If you had already assigned default values to these job parameters, then those will used by default at run-time in production.

Ofcourse, you can change them at run time. But this is not usually the case. Nobody wants to pass parameters at run-time manually.

Best bet would be to be create environment variables for the same. This way you just change the parameters at one place (DS Administrator). This is at project level.

Also, by assigning the default values to these job parameters as '$PROJDEF' you can migrate DS jobs to different environments without worrying about changing them at job-level.

Whale.

Posted: Thu Dec 07, 2006 4:35 pm
by I_Server_Whale

Posted: Thu Dec 07, 2006 7:26 pm
by ray.wurlod
In production open Director and choose the Job menu. Select "Set Defaults". This allows an administrator to change the defaults to be appropriate for the new environment, and to determine whether or not they get prompted for.

Posted: Fri Dec 08, 2006 8:15 am
by thurmy34
Hi,
We use an .ini file that we read at the beginning of our jobs control,
Then value of the parameters are set by DSSetParam

Posted: Fri Dec 08, 2006 3:51 pm
by ray.wurlod
That's a good approach, provided that no-one else can read it to see values for passwords.

Posted: Sat Dec 09, 2006 9:23 am
by johnthomas
Also try this option . Define the Job parameters in a sequencer job and set those to the parameters in the job activity. This way it will be easier to maintain.