regarding jobparameters

avi21st · Post by **avi21st** » Thu Dec 07, 2006 4:19 pm

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

I_Server_Whale · Post by **I_Server_Whale** » Thu Dec 07, 2006 4:29 pm

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.

I_Server_Whale · Post by **I_Server_Whale** » Thu Dec 07, 2006 4:35 pm

The below URL's might be of good help !

viewtopic.php?t=99957&highlight=environment+variables

viewtopic.php?t=100543&highlight=environment+variables

Happy learning !

Whale.

ray.wurlod · Post by **ray.wurlod** » Thu Dec 07, 2006 7:26 pm

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.

thurmy34 · Post by **thurmy34** » Fri Dec 08, 2006 8:15 am

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

ray.wurlod · Post by **ray.wurlod** » Fri Dec 08, 2006 3:51 pm

That's a good approach, provided that no-one else can read it to see values for passwords.

johnthomas · Post by **johnthomas** » Sat Dec 09, 2006 9:23 am

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.