Scheme lifecycles

As you may need to fine-tune and tweak execution, we anticipate (and recommend) setup and testing to be done within a Test/UAT instance, before applying a scheme to a production instance.

For this purpose, you can export and import schemes. This not only makes the process easier, but also provides a means for backup, versioning and/or even integration with a version control system.

Scheme export

Keep in mind, there are always different parts to a batch-orchestration:

• Steps and dependencies
  • Per step: One default batch class & default parameter setup
• Company specific setup i.e. batch job(s)-assignments
  • each batch job holds the actual parameters

The export can hold both, although it is during import that you select what to import.

Scheme import

During import the context of instance and company is evaluated, and if exported from an identical environment, the batch-job assignments can be restored.
Alternatively, if imported into a different environment, only the scheme definition is imported and batch job assignment (or creation) must follow the import.