Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SMILA/Documentation/JobParameters"
(→Job Parameters) |
|||
Line 2: | Line 2: | ||
= Job Parameters = | = Job Parameters = | ||
− | |||
− | |||
The Job Manager entities can be parameterized to be configured for an actual use case. | The Job Manager entities can be parameterized to be configured for an actual use case. |
Revision as of 08:23, 5 September 2011
Job Parameters
The Job Manager entities can be parameterized to be configured for an actual use case.
Entities that declare parameter variables are:
Entities that initialize or set parameters are:
- Job definitions
- Workflow definitions
- Global workflow parameters
- Local worker parameters
- Bucket definitions
The parameter priority increases from top to bottom, meaning that the parameters in job definitions, for example, have a lower priority than those in workflow definitions.
Workflow definitions are special entities in as far as they allow you to define general parameters in the global workflow section and worker-specific parameters in local worker sections. It is important to know that the latter do not affect the buckets that the respective worker is using. As a consequence, parameters declared in a data object type can only be initialized using global workflow parameters or job parameters alternatively.