I’m currently researching multi user environment for SAP BODS. We currently only have one repository which is where everything is done from, but now that we have 2 devs, we need more structure.
We will soon implement: A Central repository, 3 Local repositories ( 2 for developers to work in and 1 as the Job Server).
My question is once a job is checked out, changed, and checked back in, is there another step required for the Job Server to ensure that it is using the most current version of that job or workflow?
If not, how does the central repository communicate that change to the job server?
I can’t find documentation on SAP’s tutorials and guides, maybe I am overthinking this process. I am just concerned as we have many scheduled jobs and I don’t want anything to break with no understanding of how to fix the issue.
Typically, the third local repository would not be required in development, since each developer can run their jobs in their local repository. If you are looking for a single place to merge code and test unified structures, then you will need to log in to the 3rd repository and do a Get Latest for the code from the Central Repository.
As Ernie stated, we typically adhere to the standard that each developer has their own repo and that each project has its own assembly or “compile” repository. The latter one is typically maintained by the development lead. Atomic unit testing can occur in the developer repositories but the solution integration testing occurs in the project repository.
In complex environments, with many DS projects, we may also have a Development Master repository in which all solutions live and are jointly tested to ensure that all jobs still work - in particular when changes are made to shared objects (e.g. from our ETL framework.)
While we do use central repository for version control, we do not use it for promotions any longer. Instead we use the object promotion feature to do this - and in our environments, only the project repository acts as the valid export source for the object promotion feature.
In our QA and Prod environments, we typically only have a single repository unless integration complexities dictate that we must keep certain jobs separated, which is rather undesirable of course.
(BOB member since 2005-09-16)
(BOB member since 2007-01-10)