Basic source-control scenario for jobs and associated assets

This basic source-control scenario illustrates how you use the IBM® InfoSphere® Information Server Manager for source control of your IBM InfoSphere DataStage® and QualityStage® assets.

In this scenario, you submit an InfoSphere DataStage job to the IBM Rational ClearCase® source control system. Later, you want to change the job design, and so you change the design in the Designer client, and check the changed job back in.

Typically, you deal with more complex source control scenarios. This scenario illustrates the basic workflow of using the InfoSphere Information Server Manager for source control.

By default, executable files are included inside the archives that are sent to source control when you use the Send to Source Control Workspace command in this scenario. If you do not want to include executable files in your artifacts for source control, you must disable this option in the Source Control section of your client preferences.

The following steps describe the basic scenario:

The InfoSphere Information Server Manager gives you a view of your IBM InfoSphere DataStage project in the metadata repository. Browse the metadata repository to locate the job that you want to submit to the source control system.
In the InfoSphere Information Server Manager, select the job in the Repository tab, and select Send to Source Control Workspace. A file that contains the job is created in the source control project, ready to submit to Rational ClearCase. The file is a compressed archive file.
Rational ClearCase detects a new file in the source control project and opens the Add Resources to Source Control window. Click Apply in this window to add your job to Rational ClearCase. The icon representing this job in the InfoSphere Information Server Manager Repository tab changes to show that the job is now under source control.
You decide to change the job design.
In the Designer client, open your job, make the required changes, and save the job.
In the InfoSphere Information Server Manager, select the job in the Repository tab. Click Send to Source Control Workspace to update the archive file that contains your job in the source control project. Rational ClearCase detects the updated file which is checked-out automatically.
Select Team > Check In to check the archive file that contains your job back into Rational ClearCase.
The Eclipse Team menu gives you direct access to the Rational ClearCase menu items from within the InfoSphere Information Server Manager.

The scenario is similar for whatever source control system that you use, although there might be some minor operational differences.

If you have selected the Auto check-in local changes preference in IBM Rational Team Concert™, clicking Send to Source Control Workspace also updates your Rational Team Concert repository. Click Team > Deliver to make your changes available to other rational Team Concert users.

CVS does not have the concept of checking assets in and out, but rather you commit assets to CVS. Also, CVS does not automatically detect when an artifact is added to the source control project.

This scenario illustrates some important considerations about using the InfoSphere Information Server Manager for source control:

You submit a file containing the assets that you want to control to the source control system, not the assets themselves.
There is no lock that is put on the assets in the metadata repository. The assets can be edited outside of the control of the source control system. You must put your own process in place to prevent assets becoming out of step with their controlled version.
You can use the source control system directly from within the InfoSphere Information Server Manager. You access menus and windows that belong to the source control system by using Team menus.