M-I (Model to Installation) Comparisons

An M-I comparison (sometimes called an M-I difference) is a comparison of a component model to a specific installation of a component. When relevant, this chapter's description of a resource type will include information about how the format or content of a resource type affects an M-I comparison.

During a snapshot the current state of the metabase is exported into an XML file. During an M-I comparison, the metabase is re-exported and compared against the original XML file.

M-I Comparison for IIS Types Introduction

During a snapshot the current state of the metabase is exported into an XML file. During an M-I difference the metabase is re-exported and compared against the original XML file. The standard XML differentiator is used to generate differences between these files.

M-I Comparison for COM+ Application

The COM+ Application is re-exported on the target system as an MSI file and compared against the MSI file used to install the application. M-I difference will only indicate that there were differences (i.e. the two binary files are different) but will not indicate the details of the differences.

M-I Comparison for COM Component

The COM component is compared as a binary file against the file used during installation. M-I difference will only indicate that there were differences (i.e. the two binary files are different) but will not indicate the details of the differences.

M-I Comparison for H Keys

During a snapshot the current state of registry key (and its children) is exported into an XML file. During an M-I difference the registry key is re-exported and compared against the original XML file. The standard XML differentiator is used to generate differences between these files.

M-I Comparison for Registry Settings

M-I Differencing is not supported for *.reg files. Snapshots will not be taking during installation resulting in nothing to difference during the M-I difference. If the user would like to difference registry changes they are encouraged to use the built-in Registry keys type.

M-I Comparison for MSI Files or Windows Installer Files

M-I Differencing is not supported for Windows Installer files. Snapshots will not be taking during installation resulting in nothing to difference during the M-I difference. Since ROX does not have first-hand knowledge of the actions taken during the installer run it is not feasible to determine what needs to be captured.

M-I Comparison for Windows Batch Files

M-I Differencing is not supported for Windows Batch files. Snapshots are not taken during installation resulting in nothing to difference during the M-I difference.

M-I Comparison for Comparison for Windows Scripting Host Files

M-I Differencing is not supported for WSH files. Snapshots will not be taking during installation resulting in nothing to difference during the M-I diff.

M-I Comparison for WebLogic WAR Files

Will use the standard file/directory MI difference approach.

M-I Comparison for WebLogic Web Application Settings

The relevant settings for the application will be exported into a file, which will be compared to the file that contained the settings during deployment.

M-I Comparison for WebLogic JAR Files

Will use the standard file/directory MI difference approach.

M-I Comparison for WebLogic EJB Settings

The relevant settings for the EJB will be exported into a file, which will be compared to the file that contained the settings during deployment.

M-I Comparison for WebLogic EAR Files

Will use the standard file/directory MI difference approach.

M-I Comparison for WebLogic Enterprise Application Settings

The relevant settings for the Application will be exported into a file, which will be compared to the file that contained the settings during deployment.