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
regarding jobparameters
Moderators: chulett, rschirm, roy
regarding jobparameters
Avishek Mukherjee
Data Integration Architect
Chicago, IL, USA.
Data Integration Architect
Chicago, IL, USA.
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
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.
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.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
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.
viewtopic.php?t=99957&highlight=environment+variables
viewtopic.php?t=100543&highlight=environment+variables
Happy learning !
Whale.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 56
- Joined: Mon Oct 16, 2006 7:32 am