Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 10116

Re: Projects in Central Object Library

$
0
0

Hi Ken,

 

A project can be added to the central repository for the first time with all its dependent objects thus making the jobs under the project to be associated in the central repository.  This works fine for the first time a project is added to the central repository.

 

However when adding additional jobs (batch or real-time) to the project after the first time a project is into central repository, it is necessary to have the object and dependents of the project in the local repository. This is necessary in order for central repository to reconcile the object and dependents. This is important to prevent any corruption of the object and dependents lineage in the central object library.

 

 

Hence to meet your requirement of multiple users working on separate jobs under a single project in the central object library,

 

 

If the jobs are already in the central repository they only have to check-out and check-in the job(s) with dependent objects to/from their local repository.

 

 

If the job is not under the project in the central repository,

 

 

Check out the project with object and dependents into a local repository where the new job that needs to be added is stored.  This can be a developer’s local repository where the new job to add into the project is stored or an entirely different local repository in which case, the new job with its dependent objects should be imported from an ATL file or exported into from the developer’s local repository.

 

 

Add the job to the project in the local repository and then check-in the project with object and dependents back into the central repository. This will add the new job and its dependent objects to the central along with establishing the link for the new jobs with the project as well as leaving the other objects’ lineage intact.

 

Alternatively, the developer can check-in just the jobs with their dependent objects into central repository without adding them to the project. Then an administrator/coordinator can import the jobs into a separate local repository, ensure they all validate without errors, add to the project in the local repository and then check-in the project to the central repository. This will be useful if there are a lot of jobs. This will help with the release management process from dev-->test--->UAT-->production.

 

 

Hope this helps.

 

kind regards

Raghu


Viewing all articles
Browse latest Browse all 10116

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>