Back to Index |

Packaging Jobs for transport to another BlueSky Integration Studio Server

Sometimes it will be necessary to package up a entire job and move it to another BlueSky Integration Studio Server. An example of this functionality might be:

- You are working locally in the Personal Server and want to move the job into production on the Enterprise Server.

- You are a consultant working remotely and need to take a job to a client's location.

- You want to move a job from one Enterprise Server to another Enterprise Server location.

The difference between the Job Package functionality and the File->Export function is that the Job Package copies all the files necessary to run a particular job, including the jobs executable, the job design file, the parameters file and any local components, whereas the File->Export function simply exports the job design to an xml file.

To Package a job:

1. Select the Build->Package Job menu item.

2. Select the job that you would like to package up into a single package file (.pkg)

3. Select a filename and location for the new package file.

The Package Job function will then send a message to the BlueSky Integration Studio Server, which will look for all the files related to that job and combine them into a single file and save them to your local computer.

To Load a Job Package

1. Select the Build->Load Job Package menu option

2. Select the job package file (.pkg)

3. Select a location where you want to save the job in your repository.

The Load Job Package function will prompt you to overwrite if the job currently exists in the repository. Then, all the job files will be copied into the repository and the BlueSky Integration Studio server will update any relevant job status information and your job will be ready to run in the Job Control window.

** NOTE: Global component references not copied

Job Packages do not copy global component references or global Import statements necessary to re-compile a job. It is simply a method for you to move a job from one server to another. If you have References to external .dll components and Import statements built into your source server, it may be necessary to also reference them in the Target server if you wish to re-compile you job on the Target Server.

Also, if your job references 3rd party components in the Global Assembly Cache, it will be necessary to install those 3rd party components on your target server so that the job can find them and run correctly.

© 2003 - 2007 Relational Solutions, Inc. - All rights reserved