Select the destination repository by clicking Select next to the Modified Provide a password for the modified repository in the appropriate Password field. Click Next. If there are any conflicts, the Define Merge Strategy screen of the Click Finish.

16-16 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition

5. In the Select Input Files screen, for Merge Type, select Full Repository Merge.

6. Click Select next to Original Master Repository. Then, browse to select your

blank repository file as the original repository and click Open. Leave the password field blank.

7. Select the destination repository by clicking Select next to the Modified

Repository field. Browse to select the modified repository, then click Open. This is the repository into which you want to import objects.

8. Provide a password for the modified repository in the appropriate Password field.

9. Optionally, you can change the default name and location of the saved merged file by clicking Select next to the Save Merged Repository as field. Provide a new name and location, then click Save.

10. Click Next. If there are any conflicts, the Define Merge Strategy screen of the

Merge Repository Wizard appears. If there are no conflicts, the Merge Wizard continues with the merge process and then closes automatically when finished. 11. The Define Merge Strategy screen displays a decision table that shows conflicts for this merge. To make decisions about whether to include or exclude objects from the merged repository, choose Current or Modified from the Decision list. When you select an object in the decision table, the read-only text box below the decision table describes what changes were made to that object in the current repository. Refer to Figure 16–6 to see the Define Merge Strategy screen. Refer to Table 16–4 for information about additional options in the Define Merge Strategy screen, such as saving merge decisions to a comma-separated values .csv file. After you make a merge decision, the row for that decision in the table changes from red to black. When all rows have a value in the Decision field, the Finish button is enabled.

12. Click Finish.

Performing Patch Merges Oracle Business Intelligence provides the capability of generating an XML patch file that contains only the changes made to a repository. This patch can be then applied to the old original version of the repository to create the new version. This is very useful for development-to-production scenarios, and can also be used for Oracle BI Applications customers to upgrade their repository. This section explains how to generate a patch that contains the differences between two repositories, and then apply the patch to a repository file. This section contains the following topics: ■ About Patch Merges ■ Generating a Repository Patch ■ Applying a Repository Patch About Patch Merges In a patch merge, you create a patch that contains the differences between the current repository file and the original repository file. Then, you apply the patch file to the modified repository file. Managing Oracle BI Repository Files 16-17 In a development-to-production scenario, you have an original parent file, a current file that contains the latest development changes, and a modified file that is the deployed copy of the original file. To generate a patch, you open the current file and select the original file, then create the patch. Figure 16–7 shows how to create a patch in a development-to-production scenario. Figure 16–7 Development-to-Production: Creating the Patch To apply the patch, you open the modified file and select the original file, then apply the patch. Figure 16–8 shows how to apply a patch in a development-to-production scenario. Figure 16–8 Development-to-Production: Applying the Patch In an Oracle BI Applications repository upgrade scenario, the current file is the latest version of the repository shipped by Oracle, and the original file is the original repository shipped by Oracle. The modified file is the file that contains the customizations you made to the original file. To generate a patch, you open the current file and select the original file, then create the patch. Figure 16–7 shows how to create a patch in an Oracle BI Applications repository upgrade scenario. 16-18 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition Figure 16–9 Oracle BI Applications Repository Upgrade: Creating the Patch To apply the patch, you open the modified file and select the original file, then apply the patch. Figure 16–10 shows how to apply a patch in an Oracle BI Applications repository upgrade scenario. Figure 16–10 Oracle BI Applications Repository Upgrade: Applying the Patch Generating a Repository Patch Use the Administration Tool to generate a patch that contains the differences between two repositories. To generate a patch using the Administration Tool: 1. In the Administration Tool, open the current Oracle BI repository in offline mode. In other words, open the updated repository that contains the changes you want to put in the patch.

2. Select File, then select Compare.