Hello everyone, I'm a php developer and I'm trying to integrate Pentaho with an existing application, because I can see the benefits of "moving out" some procedures and jobs from the unaccessible code to something that customers with some junior ITs can modify and manage by themselves.
I'm now preparing the ground for them, and I am having a hard time putting it all together in a clean way
Ideally I'd like to call the jobs from my scheduler, built in the application, that passes some vital parameters to them (database connections, paths, smtp server/passwords).
I have set up the database connections using variables such as ${DBA_HOST}, and my first attempt has been to build commands like
Kitchen.bat /rep:MIS_DB_REPO /user:admin /pass:admin /dir:"/" /job:"test" /param:DBA_HOST="localhost"
and it works, but the DBA_HOST variable is visible in "test" job only if I define it in the expected parameters of the target job.
I have then tried another route, creating a transformation that reads an xml file from a webservice and then sets some variables (scope "Valid in the root job"), let's call this transformation "fetch parameters"
I have then put this in a job:
Start->fetch parameters(using webservice URL passed as named parameter)->call another job B
The problem is that the job B sees a variable (again the various hosts and passwords) only if it is defined in its expected named parameters
Bottom line is there a way to cleanly share some variables (having them available everywhere) between all the execution tree of jobs and transformations without explicitly declaring them in each job/transformation (jn the expected parameters)?
Many thanks
I'm now preparing the ground for them, and I am having a hard time putting it all together in a clean way
Ideally I'd like to call the jobs from my scheduler, built in the application, that passes some vital parameters to them (database connections, paths, smtp server/passwords).
I have set up the database connections using variables such as ${DBA_HOST}, and my first attempt has been to build commands like
Kitchen.bat /rep:MIS_DB_REPO /user:admin /pass:admin /dir:"/" /job:"test" /param:DBA_HOST="localhost"
and it works, but the DBA_HOST variable is visible in "test" job only if I define it in the expected parameters of the target job.
I have then tried another route, creating a transformation that reads an xml file from a webservice and then sets some variables (scope "Valid in the root job"), let's call this transformation "fetch parameters"
I have then put this in a job:
Start->fetch parameters(using webservice URL passed as named parameter)->call another job B
The problem is that the job B sees a variable (again the various hosts and passwords) only if it is defined in its expected named parameters
Bottom line is there a way to cleanly share some variables (having them available everywhere) between all the execution tree of jobs and transformations without explicitly declaring them in each job/transformation (jn the expected parameters)?
Many thanks