Merging FPR Files

The FPRUtility -merge option combines the analysis results from two FPR files into a single FPR file. The values of the primary project are used to resolve conflicts. When you merge two FPR files, copies of both the primary analysis results and the secondary analysis results are stored in the merged FPR. When you open a merged FPR in Fortify Audit Workbench or Application Security, removed issues are determined as those that exist in the secondary analysis results but not in the primary analysis results. Similarly, new issues are those that exist in the primary analysis results, but not in the secondary analysis results.

To merge FPR files:

FPRUtility -merge -project <primary>.fpr -source <secondary>.fpr \
-f <merged>.fpr

To merge FPR files and set instance ID migrator options:

FPRUtility -merge -project <primary>.fpr -source <secondary>.fpr \ 
-f <merged>.fpr -iidmigratorOptions "<iidmigrator_options>"

FPRUtility Data Merge Options

The following table lists the FPRUtility options that apply to merging data.

FPRUtility Option	Description
`-merge`	Merges the specified project and source FPR files.
`-project <primary>.fpr`	Specifies the primary FPR file to merge. Conflicts are resolved using the values in this file.
`-source <secondary>.fpr`	Specifies the secondary FPR file to merge. The primary project overrides values if conflicts exist.
`-f <merged>.fpr`	Specifies the name of the merged FPR file to contain the result of the merged files. When you specify this option, neither of the original FPR files are modified. If you do not use this option, the primary FPR is overwritten with the merged results.
`-forceMigration`	Forces the migration, even if OpenText SAST and the Rulepack versions of the two projects are the same.
`-ignoreAnalysisDates`	Specifies to ignore the analysis dates in the primary and secondary FPR files for the merge. Otherwise, the secondary FPR is always updated with the primary FPR .
`-useSourceIssueTemplate`	Specifies to use the filter sets and folders from the issue template in the secondary FPR.
`-useMigrationFile` `<mapping_file>`	Specifies an instance ID mapping file. This enables you to modify mappings manually rather than using the migration results. Supply your own instance ID mapping file.
`-iidmigratorOptions <iidmigrator_options>`	Specifies instance ID migrator options. Separate included options with spaces and enclosed them in quotes. Some valid options are: `-i` provides a case-sensitive file name comparison of the merged files `-u <scheme_file>` tells iidmigrator to read the matching scheme from `<scheme_file>` for instance ID migration Wrap `<-iidmigrator_options>` in single quotes (`'-u <scheme_file>'`) when working from a Cygwin command prompt. Windows example: `FPRUtility -merge -project <primary>.fpr` -source <secondary>.fpr -f <merged>.fpr -iidmigratorOptions "-u scheme_file"
`-debug`	Displays debug information that can be helpful to troubleshoot issues with FPRUtility.

FPRUtility Data Merge Exit Codes

Upon completion of the -merge command, FPRUtility provides one of the exit codes described in the following table.

Exit Code	Description
0	The merge completed successfully.
5	The merge failed.