One projet with multiple environnements (parameters)
Moderators: chulett, rschirm, roy
One projet with multiple environnements (parameters)
Hi,
I've some difficulties to manage my data in my project (1 project).
I have to tests some data :
- from 2005 with user1/password1@Database
- from 2006 with user2/password2@Database
- from 2006 with user3/password3@Database
I create for each job 3 job sequences in which I change the parameters (repository, ...).
All string parameters (ex DSN, user, schema) can be changed but I can't change the password because it's in encrypted type. So, the password is always the default value filled in the job.
Is-it possible to create a parameter for a category or project in Datastage ? Difference between string and encrypted parameters.
Thanks.
I've some difficulties to manage my data in my project (1 project).
I have to tests some data :
- from 2005 with user1/password1@Database
- from 2006 with user2/password2@Database
- from 2006 with user3/password3@Database
I create for each job 3 job sequences in which I change the parameters (repository, ...).
All string parameters (ex DSN, user, schema) can be changed but I can't change the password because it's in encrypted type. So, the password is always the default value filled in the job.
Is-it possible to create a parameter for a category or project in Datastage ? Difference between string and encrypted parameters.
Thanks.
Re: One projet with multiple environnements (parameters)
This is not true, you certainly can change the value of encrypted parameters. Their 'default' can be changed in the Director and they can be changed in the Run dialog just like any other parameter. What lead you to believe that?shrek7577 wrote:All string parameters (ex DSN, user, schema) can be changed but I can't change the password because it's in encrypted type. So, the password is always the default value filled in the job.
Yes. Project is simple, leverage environment variables. Category? You may need something more custom depending on exactly what you need. However, don't pursue this for the reason stated above.shrek7577 also wrote:Is-it possible to create a parameter for a category or project in Datastage ?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
You wont be able to change it directly there. You need to define a parameter in the job sequence and pass that parameter as the value. Plus for encrypted passwords, you wont be able to "double click" and enter a value, you need to hit "Insert parameter" and then specify the job sequence's job parameter.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
Me neither. Nothing magical about Sequence jobs, our Production support peoples do this all the time. Matter of fact I just did it in one of our jobs to make sure I wasn't smoking something. At runtime, it should edit like any other parameter - right in the box. Inside a job, it should pop up a two entry dialog where you first enter and then 'verify' the value.shrek7577 wrote:In the job sequence, when i double click on a string parameter i can edit the value. When I double click on a encrypted parameter, nothing happens... don't undestand...
Is anyone else having this problem where you work? Have you reported it to your support provider?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
This may very well be the 'problem'. My assumption was that you were passing the passwords in at runtime by defining them in the Sequence job itself, this is a standard practice and why I kept mentioning the Run dialog and the Set Defaults option in the Director. If you are not doing that, then yes - you cannot double-click in an encrypted field in a Job Activity stage's parameters section. You are stuck with the value in the job. Of course, you could simply change the default value in the job itself...DSguru2B wrote:You wont be able to change it directly there. You need to define a parameter in the job sequence and pass that parameter as the value. Plus for encrypted passwords, you wont be able to "double click" and enter a value, you need to hit "Insert parameter" and then specify the job sequence's job parameter.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
So, I create all environment parameters in the properties/Parameters of the Job Sequence.
And for each job stage in the job sequence, I "Insert Parameter Value" for all environment parameters.
Then, for my 3 environments, I copy/paste 2 others jobs sequences and change only the Properties/Parameters without changing anything in all job stages inthe job sequence.
So, I spent 30minutes to do the first job sequence and 30secondes for the 2 others !!
Thanks chulett and DSguru2B for your help !!
And for each job stage in the job sequence, I "Insert Parameter Value" for all environment parameters.
Then, for my 3 environments, I copy/paste 2 others jobs sequences and change only the Properties/Parameters without changing anything in all job stages inthe job sequence.
So, I spent 30minutes to do the first job sequence and 30secondes for the 2 others !!
Thanks chulett and DSguru2B for your help !!