This can be achieved with "importExecutionPlan" command of MetaServletCaller.
Here is the syntax for creating a very basic Exec Plan with just one task "Task1" (which should already exist in TAC) :
MetaServletCaller --tac-url=http://localhost:8080/org.talend.administrator --json-params={"actionName":"importExecutionPlan","authUser":"test@company.com","authPass":"test","result":{"ExecutionPlan":[{"label":"PlanB","desc":"This is my Plan","execPlanTimeOut":60,"planParts":{"planId":"PlanB","planPartTaskId":"Task1"}}]}}
As you can see from above, most the Exec Plan config is in "result" attribute.
To get the full syntax of "result" attribute if you want to create a more complex plan, then what you can do is start from an existing plan, and call MetaServletCaller's "listExecutionPlans". This will return "result" which you can edit/adjust to use when calling "importExecutionPlan".
This can be achieved with "importExecutionPlan" command of MetaServletCaller.
Here is the syntax for creating a very basic Exec Plan with just one task "Task1" (which should already exist in TAC) :
MetaServletCaller --tac-url=http://localhost:8080/org.talend.administrator --json-params={"actionName":"importExecutionPlan","authUser":"test@company.com","authPass":"test","result":{"ExecutionPlan":[{"label":"PlanB","desc":"This is my Plan","execPlanTimeOut":60,"planParts":{"planId":"PlanB","planPartTaskId":"Task1"}}]}}
As you can see from above, most the Exec Plan config is in "result" attribute.
To get the full syntax of "result" attribute if you want to create a more complex plan, then what you can do is start from an existing plan, and call MetaServletCaller's "listExecutionPlans". This will return "result" which you can edit/adjust to use when calling "importExecutionPlan".
