We have handful of context variables in our jobs (DEV environment) out of which DB connectivity is also parameterized/contextualized, my question is when these jobs get migrated to Production where I don't have a choice to put in the passwords, how are these context variables expected to be refreshed with correct values. Any thoughts please
I was able to work out an answer for my own question and thought of sharing with the community, so that it may be helpful for some one in need...
Solution:
The ideal way to handle Context variables (including variables used for DB connections) is to be handle them in a properties files away from the job code, such that these variables are initiated by reading from this properties file. Refer to the attachments where i have put in a sample properties file and image of the context tab
Thanks Manodwhb. While I know that Job level extra settings allow us to load these context variables from an external file, they would typically override the project settings, so i was not sure what happens to settings set at repository/project level.
I was able to work out an answer for my own question and thought of sharing with the community, so that it may be helpful for some one in need...
Solution:
The ideal way to handle Context variables (including variables used for DB connections) is to be handle them in a properties files away from the job code, such that these variables are initiated by reading from this properties file. Refer to the attachments where i have put in a sample properties file and image of the context tab
