Different Config Files for Sequence and Child Job

[nvalia]

Hi,

JobA uses a 1 Node Config file by setting the ENV Var $APT_CONFIG_FILE to point to different config file (instead of the default.apt) in the job and it works fine. But now when we call this job in a Sequence we need to add this Env Var to the Sequence as well and set it to use 1Node file and finally pass this to the JobA.

This works fine but this means all jobs in the Sequence (JobB, JobC) will also run on 1 Node impacting performance

How we can have only this job run on one node but all other jobs in the Sequence run on regular 2 node configuration?

Thanks

[lstsaur]

Use 2 nodes config file, but set jobA's Node pool and resource constrains to 1 particular node.

[ray.wurlod]

Why not pass hard-coded replacement values (pathnames of configuration files) to the jobs in the Job activities that invoke them?

[BI-RMA]

Another alternative is to create a parameter-set containing $APT_CONFIG_FILE.

Have value-files pointing to the different Configurations you want to choose from for different jobs. You can then configure each activity to use its individual configuration by choosing the appropriate value-file.

While being fairly similar to actually hardcoding a specific path as Ray suggested, this solution makes it possible to have a value-file TWO_NODE that points to two different configuration-files in two different projects. This way you do not need to change any values on the sequence and recompile after transporting a job from a development- to a test-environment, which may both be located on the same physical machine but use different resources specified in different configuration-files.

[nvalia]

Thank You all, this helps.