Hi Sabrina.
Thanks for response.
With the option "transmit whole context" checked, the context variables declared into the parent job are transmitted to the child job.
It's not what I want to do.
The goal is the following :
In my parent child, I've got 2 contexts (DEV and PROD).
In my child jobs, I've got the same 2 contexts (DEV and PROD).
In my child job "job_generate_logs", wich responsability is to generate logs in a specified repository, I've got a group context "ctx_path_logs" (only added in this child job, because it is his own responsability, not in his parent).
FYI : "ctx_path_logs" describes the paths where to write the logs, for the DEV environment and for the PROD environment.
Before publish, I can set, into the tRunJob component, the rigth context. But it's vey tiresome to do this action for all my tRunJob, at each time I want to split DEV or PROD.
So I want to use, into the TAC, in the "ESB Conductor" tab, the runtime configation of the service : select the rigth context here (for example PROD context). But when I do that, only the parent job is running with the PROD context. The child jobs stay running with the context itinialized into the tRunJob component.
However, the "Job Conductor" tab, for the task, have the "Apply context to children" option ; that's work finely, even if the tRunJob components specified an different context. It's very usefull.
I would like to have the same feature in the "ESB Conductor" tab.
