The Studio offers a number of different ways to export and import the jobs you create and each approach has a different purpose behind it. In this section we will look at the different methods of importing and exporting jobs and also look at why you might choose one method over another.
As we have seen in the section about job versions, the Studio creates file artifacts when you create a job design and stores these on your local computer's filesystem. When you run a job within the Studio, the artifacts, which represent the job configuration, are compiled into Java code before being executed. This development setup and process may be sufficient for some readers, particularly where there is only one developer creating jobs and/or the jobs can be run manually from the studio tool.
When this is not the case, it is useful to be able to export jobs from the Studio tool for two primary reasons:
You want to collaborate with other developers and need some...
