IBM FileNet P8, Version 5.2.1            

Generating audit reports from the audit files

After an import operation that includes the option to generate an audit file, use the audit file to generate an audit report. The audit report provides detailed information about the converted and imported objects.

Use FileNet® Deployment Manager to generate an audit report to present the contents of the audit file. The audit file captures a record of changes to the destination environment by the converted and imported objects. The operation to generate an audit report operation is an information-only operation; it reads the audit file and does not modify the destination environment.

The audit file captures a finer level of detail for the differences between assets in the destination FileNet P8 domain and the assets in the deployment data set. The audit file provides more detail than the change impact analysis report that is produced by the analysis operation. For each object in the deployment data set that is represented in the audit file, the following information is placed into the generated audit report:
  • An asterisk at the beginning of the header line for an object to indicate that an object changes in the destination environment as a result of the import.
  • Values for all scalar properties with both the before and after values when the values are different as a result of the import. The minus sign indicates the before value. The plus sign indicates the after value. A double plus sign '++' is used to indicate the after value for a property that is new. If the object itself is new, all of its properties are marked with the double plus sign.
  • IDs of all object valued properties:
    • If those objects also appear in the deployment data set, they are among the objects that are captured in the audit file and the ID can be used to locate them in the audit report.
    • If those objects do not appear in the deployment data set, they must exist in the destination environment in order for the import operation to succeed. The ID can be used to locate them in the destination environment.
Important: If an object is skipped during the import, it does not appear in the audit report.

You can generate an audit report from the FileNet Deployment Manager graphical user interface or from the command-line interface. The following procedure describes how to generate an audit report from the graphical user interface.

To generate an audit report:

  1. Ensure that an audit file was produced for the deployment data set and destination environment in which you are interested. See Auditing changes to imported objects.
  2. In FileNet Deployment Manager, right-click the source-destination pair for this deployment and click Generate Audit Report. The Audit Report dialog box is displayed.
  3. Select the deployment data set whose audit information you want to report.
  4. Select the audit file that contains the audit information that you want to report. The audit file list is populated with the names of all audit files that are associated with the deployment data set selected in step 3.
  5. Specify the fully qualified file name to use for the audit report file. By default, the generate audit report operation writes the report to the deployment data set directory that contains the converted objects.
  6. Specify the reporting options:
    1. Generate detailed report Select this check box to generate both the summary and detailed portions of the report, including detailed information for all objects audited. The default is to produce only the summary portion of the report.
    2. View report in browser after processing Select this check box to display the generated report. If you have an application other than a web browser associated with the XML file type, the associated XSL transform is not applied, and the source XML report file, instead of the generated HTML, opens.
  7. Click Finish. If a file of the same name is found in the specified path, you can choose to overwrite the existing the XML report file.
  8. If you choose to view the report after you generate it, the application that is associated with the XML file type opens to display the audit report.

    If the report generation stops because of an unrecoverable error, the error is reported in the installation_directory/deployment.log file and in the console window of the user interface. Examples of unrecoverable errors include an I/O error that occurs when the audit file is read, or an invalid XML syntax in the audit file.



Last updated: October 2015
p8pdb035.htm

© Copyright IBM Corporation 2015.