Siebel Database Upgrade Guide > Performing the Siebel Incremental Repository Merge > Process of Upgrading the Siebel Development Environment from Siebel CRM Version 8.1.1.x (SIA Repository) >

Reviewing the Hierarchical Merge Report

This task is a step in Process of Upgrading the Siebel Development Environment from Siebel CRM Version 8.1.1.x (SIA Repository). Use this task to review the hierarchical merge log files.

The hierarchical merge report is generated in HTML format for Application Hierarchy objects, which are Application, Screen, View, Business Component, Applet, Table, Business Service, Business Object and Workflow Process. This report allows you to review the tree of a particular object and see exactly what has been changed in the Application Hierarchy. If an object on which the currently selected object depends has changed, then you can drill down on that object and get a better idea of the testing effort involved.

The report is generated in the SIEBSRVR_ROOT\log\upgrep_dev_*\output directory and is named MergeReport.html.

When you run Incremental Repository Merge on Microsoft Windows, the HTML report is generated automatically once the incremental repository merge has completed. On UNIX, you must generate the hierarchical merge report manually, by running MergeReport.bat. Typically, you run this report after running incremental repository merge. For Upgrade, you also must generate the hierarchical merge report manually. MergeReport.bat is located in the SIEBEL_TOOLS_ROOT\reppatch directory.

You are prompted to specify values for the following parameters, which are required to generate the report. Where necessary, you must enclose parameter values in double-quotes.

• Tools Installation Folder
• ODBC Data Source Name
• Database Table Owner
• Database Table Owner Password
• Table Owner User Name
• Tablespace Name
• Index Space Name
• 16k Tablespace Name
• 32k Tablespace Name
• Is DB Unicode or Not
• Grantee Role (SSE_ROLE)
• Repository Name
• Full Path of Directory in Which to Generate HTML Report
• Full Path of Log File to Run Patch
• Database Platform (Oracle, MSSQL, DB2UDB, or DB2390)
• Merge ID for Report Generation. This value can be identified in Siebel Tools. Log in to Siebel Tools, navigate to Screens menu, then Application Upgrader, Application Upgrade Object List. Select a record and get the row ID from Help, About Record.
• Generate Report for Latest Merge Run. Enter Y to generate report. Enter N to display all available Merge Log ID.
• Retain Files for Debugging. Enter N to retain files for debugging. Otherwise, enter Y.

Usability

Different sections of the report present different types of information, as follows:

• The left section of the report, the navigation section, lists the objects that are affected by the merge process. Select an object in this section to view information about the object.
• The top-right section of the report lists the objects that are dependent on the object that is selected in the navigation section.
• The bottom-right section displays the attribute-level details of the object that is selected in the top-right section.

Navigation Section

This report limits the objects that are part of the application hierarchy. Nine tabs are displayed for each object type. When a tab is selected, it expands and displays the list of objects that are affected by the merge process. Two options provide searching capability for any particular object in the report:

• Global Search, provided on the top left, can be used to search any object in all objects of the application hierarchy.
• Local search limits the search functionality on a particular tab on which a search operation is triggered.

Dependent Object Section

The dependent object section, in the top right, displays the dependent objects for the object that is selected in the navigation section. The selected object name is displayed above the dependent object section. You can further navigate to each tab to see the list of objects.

Tabs are displayed only for objects that are dependent on the selected object. For example, if Applet has been modified and no Business Service is dependent on that Applet, then the Business Service tab will not be displayed in this section. Under each tab, if an object name has no background color, it means that no attribute level information is changed as part of the merge for this object.

For example, for the View tab, responsibility information is displayed for the selected view. When the View tab is selected and a View object is selected, then the responsibility information for this view is also displayed.

The bottom-right section of the report displays attribute-level information for the selected object. You can filter the resulting records based on Critical Conflicts, Non Critical Conflicts and All Changes.

Related Topics

Reviewing Siebel Repository Object Property Conflicts