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
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.
Parts
» Oracle Fusion Middleware Online Documentation Library
» Click OK when you are finished setting preferences.
» Select Set Icon. Oracle Fusion Middleware Online Documentation Library
» Select the appropriate DSN and click OK.
» Click OK. Oracle Fusion Middleware Online Documentation Library
» Without opening a repository, select File Multiuser History.
» In the ODBC Data Source Administrator dialog, click the System DSN tab, and
» In the Select Data Source screen, in the Connection Type field, select the type of
» Click Finish. Oracle Fusion Middleware Online Documentation Library
» In the Administration Tool, select File, then select Import Metadata.
» Provide the Data source name for the primary database. Click OK.
» In the Select Data Source screen, select OracleADF_HTTP for Connection Type.
» Select the objects you want to import in the Available list and move them to the Click Finish.
» In the Database dialog, click the Features tab. In the Features tab, use the information in
» Specify or adjust the properties as needed, then click OK.
» In the Persist connection pool area, click Clear. Click OK.
» To add tables to the display folder, click Add. Then, in the Browse dialog, select Click OK.
» Click OK in the Hierarchy dialog.
» Select View Members. Click Query to display results. When finished, click Close.
» Click OK. Select Create Columns for Alias Table. Then, from the sub-list, select the alias
» Type the text of the hint in the Hint field and click OK.
» In the shortcut menu, select Update Row Count. Click Yes to check out the objects.
» If you want to provide a dynamic list of currency options, create a table in your
» Click OK. Click OK or Cancel to close the Dimensions dialog.
» From the right-click menu, select Create Logical Dimension, then select either
» In the Check Out Objects dialog, click Yes to check out the objects that appear in
» If the values for the source are unique, select the option Select distinct values.
» Click OK. To move a table, in the Name list, select the table you want to reorder. Then, use
» In the Finish Script screen, the complete path and file name appears. Click Finish.
» Click OK, then click OK again to return to the Identity Manager.
» On the General tab, in the Data source definition: Database field, ensure that the
» Click OK. Open the user.sh file. You can find this file at:
» Click Select next to Patch File. Browse to select the patch file you want to apply, Click Finish.
» Select Tools, then select Query Repository. Click Query.
» When you have finished mapping columns between the selected physical tables, Click Finish.
» In the Choose Directory dialog, click Browse to locate and select the location Click OK.
» To remove the selected objects, click Yes.
» Repository initialization blocks only In the Schedule area, select a start date and
» In the [Repository|Session] Variable Initialization Block dialog, click Edit Data
» Click Edit Data Target. Click OK.
» Check out the branch project using File Multiuser Checkout. You can check
Show more