Creating compare configuration report

Edit online

You can create a configuration comparison report that contains the differences between two related configurations, baselines, streams or change sets. The comparison report provides information that is related to elements that are found in source and target configurations, and the elements that are found in both configurations. The compare utility wizard is enhanced to create the comparison report.

Procedure

  1. From the Administration menu admin_publish_service, select Manage Components and Configurations.
  2. Click the current configuration name, and then click Compare Configuration.
  3. Select Configuration to Compare, which you want to compare with. (Source and target configurations).
    select_config_compare
  4. Click Print report to create the report of the selected configurations.
    print_report
  5. Select one of the various following options for creating the report:
    1. Include component properties.
    2. Include folder.
    3. Include artifacts.
    4. Include change sets.
      Note: The change sets included in the report are the ones that are used for the comparison. If an artifact is changed several times, then only the last change set is included in the list of change sets.
  6. Select the output format in the Create report dialog box.
    1. PDF
    2. Word
    ../images/end_result.jpg
  7. Click OK.
    end_result
    • The report is generated. The changes are visible in a special style. The gray elements are old changes and the yellow highlighted changes are new changes that are available in source stream.
    Warning: The Compare configuration report requires a large Java Virtual Machine (JVM) heap setting in DOORS Next server. You must take note of the following points:
    • A single report run can cause DOORS Next server to crash, if sufficient heap memory is not available to the JVM.
    • The API used to generate Word and PDF reports usually requires a large heap in the final stage of report generation. In addition, the amount of heap that is required to run your report varies greatly depending on the comparison. If you are comparing a baseline to the current stream and you choose an older baseline, it may multiply the amount of heap that is required to process the report.
    • Customers who perform many ReqIf or CSV or MS Word imports are likely to need more heap to process the compare configuration report.
    • Depending on the data shape, to successfully generate a compare configuration report of 500 MB may require 12-16 GB additional heap per concurrent report generation. To prevent the generation from having a large impact on other server operations, a larger heap is advised.
    • For more information, review the following technote: IBM Engineering Lifecycle Optimization - Publishing: Aspose.Words out of memory error when generating document-style report from DOORS Next