Use FileNet® Deployment Manager to
run a change impact analysis operation, a pre-import analysis of exported
objects that is intended for deployment to a destination environment.
The analyze operation is an information-only operation;
it reads but does not modify the destination environment. For more
information, see About
change impact analysis.
To run this operation, you can
use the FileNet Deployment Manager user
interface, as described in the following section, or you can use the
Analyze operation in the command-line interface. For more information,
see Deployment operation
formats and Deployment
command-line reference.
If the change impact analysis
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 these examples: an I/O error that reads an export file,
invalid XML syntax in a map file, or a connection problem to the destination
environment.
To analyze objects for import:
- In FileNet Deployment Manager,
right-click the source-destination pair for this deployment and click Analyze.
The Change Impact Analysis wizard displays.
From this wizard, you select a deploy data set to analyze.
- Select the default (most recently used) data set or you
can browse to another location to select a different data set. Click Next.
- Select one of the following import options to use during
analysis:
- Only update an object if the instance in the import data set
is newer than the one at the destination
- Always update an object if it exists at the destination
- Never update an object if it exists at the destination
- Specify the fully qualified file name to use for the change
impact analysis main report file. By default, the analysis operation
writes the main report to the deployment data set directory that contains
the converted objects.
The change impact analysis
operation also writes an XSL file (ChangeImpactReport.xsl)
to this path. The XSL file is referenced by the XML report file, and
is used to transform the main report XML file to generate an HTML
version when the main report file is opened in a web browser. For
the XSL transform to occur, the XSL file must remain in the same directory
as the main report XML file. A directory with the same name as the
analysis report file (minus the .xml file extension) is created to
store reports for objects that passed analysis. Detailed information
for objects that passed analysis is stored in multiple files that
are contained in a subdirectory with the same name that you assigned
to the main report file (minus the .xml extension). For more information,
see Analysis results.
- Specify the change impact analysis reporting options:
Option |
Description |
The maximum number of failures detected before terminating
analysis |
Specify the maximum number of failures to report. Controlling
the number of validation failures can assist you in diagnosing issues.
The default is 100. A value of zero indicates an unlimited number
of failures.
|
Include details for all objects in report |
Select this check box to generate a detailed report, including
information for all objects analyzed. The default is to produce a
summary report. For more information, see Analysis results for
more information. Regardless of whether you choose to create a detailed
or a summary report, the same data is saved to disk; only the generated
HTML in the main report changes.
|
View report after processing |
Select this check box to display the generated main 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) is opened.
|
Restriction: Detailed information for objects
that failed analysis is available in the Objects that Failed Analysis
section of the main report. By contrast, detailed information for
objects that passed analysis is stored in multiple files that are
contained in a subdirectory with the same name that you assigned to
the main report file (minus the .xml extension). If you open a passed
asset report XML file in a web browser, an associated XSL transform
(
PassedAssetsReport.xsl) is automatically applied
to generate an HTML version of the report. In addition, if you open
a passed asset report XML file with a text editor instead of a web
browser, you can view more information for assets that passed analysis,
including an estimated size breakdown for each property of an object.
For more information about viewing asset reports, see
Analysis results.
- Click Next. If a file of the same
name is found in the specified path, you can choose to overwrite the
XML report file.
- Your selected reporting options are displayed. Review the
summary of your settings and, if necessary, return to previous panes
to change your reporting options. Click Finish to
proceed with the analysis.