Create a subset of branch repositories by extracting from Main and storing them as Developers must check out, develop, merge, and publish from their respective One specific group for example, release management should manage all project Extract a fresh Br

Setting Up and Using the Multiuser Development Environment 3-19 Using the Multi-Team, Multi-Release Model in Oracle Business Intelligence Using complex branching strategies in Oracle Business Intelligence requires attentive organization of repository files, as well as altering the Multiuser setting in the Administration Tool. The following procedure provides an overview of the required steps. To use the multi-team, multi-release model branching strategy: 1. Create a Main repository Master Repository and store it in the Master multiuser development directory. ■ Projects must be explicitly defined. ■ Branch developers should not have access to the Master directory.

2. Create a subset of branch repositories by extracting from Main and storing them as

the Team1 and Team2 multiuser development directories. The Main and Team RPDs must be stored and secured in separate directories on the network.

3. Developers must check out, develop, merge, and publish from their respective

Team RPDs. Developers A1 through A3 and B1 through B3 should manage their metadata work and merge to their Team repository. ■ Teams 1 and 2 must maintain their own repositories and periodically synchronize from Main to Team branches. ■ The Team repositories must be merged back into and published in the Main repository.

4. One specific group for example, release management should manage all project

definitions, perform merges, publish, and synchronize the Team RPDs back to Main. Synchronizing RPD Branches For large development teams, it is a good practice to perform periodic branch synchronization as Main changes, in order to ease the ultimate Team check-in. Use the Administration Tool to synchronize repositories in a three-way merge. To synchronize repository branches: 1. Check in all changes from your Team development branch and open the RPD in the Administration Tool. This the current repository.

2. Extract a fresh Branch subset from Main. This is the modified repository.

3. In the Administration Tool, select File, then select Merge and browse to the

backup of the previous Branch subset. This is the original repository. 4. Resolve all issues and perform the merge. The RPD named in the Save merged repository as field becomes the new branch development RPD and is called the Original in future synchronizations. Viewing and Deleting History for Multiuser Development You can view and delete the development history of a multiuser development repository. This section contains the following topics: ■ Viewing Multiuser Development History 3-20 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition ■ Deleting Multiuser Development History Viewing Multiuser Development History You can view the development history of a multiuser development repository. In the Administration Tool, multiuser development history is only available when no repository is open and after the administrator sets up the shared network directory. This prevents the confusion that could occur if a user opened a history log that did not match an open, unrelated repository. To view multiuser development history: 1. Open the Administration Tool.

2. Without opening a repository, select File Multiuser History.