Component Types and Model to Install Comparisons

A Model to Install comparison compares a component model to a specific installation of a component. This section describes how a component type effects a Model to Install comparison.

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

IIS Types Introduction

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

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. A Model to Install comparison will only indicate that there were differences (that is, the two binary files are different). It will not indicate the details of the differences.

COM Component

The COM component is compared as a binary file against the file used during installation. A Model to Install comparison will only indicate that there were differences (that is, the two binary files are different). It will not indicate the details of the differences.

H Keys

During a snapshot, the current state of registry key (and its children) is exported into an XML file. During a Model to Install comparison, 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.

Registry Settings

Model to Install comparisons are not supported for *.reg files. Snapshots are not taken during installation. Without a snapshot, there is nothing to compare in a Model to Install comparison. If you need to compare registry changes, use the built-in Registry keys type.

MSI Files or Windows Installer Files

Model to Install comparisons are not supported for Windows Installer files. Snapshots are not taken during installation. Without a snapshot, there is nothing to compare in a Model to Install comparison. Since the provisioning system does not have first-hand knowledge of the actions taken during the installation, it cannot determine what needs to be captured.

Windows Batch Files

Model to Install comparisons are not supported for Windows Batch files. Snapshots are not taken during installation. Without a snapshot, there is nothing to compare in a Model to Install comparison.

Windows Scripting Host Files

Model to Install comparisons are not supported for WSH files. Snapshots are not taken during installation. Without a snapshot, there is nothing to compare in a Model to Install comparison.

WebLogic WAR Files

Model to Install comparisons with WebLogic WAR Files use the standard file and directory approach.

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.

WebLogic JAR Files

Model to Install comparisons with WebLogic JAR Files use the standard file and directory approach.

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.

WebLogic EAR Files

Model to Install comparisons with WebLogic EAR Files use the standard file and directory approach.

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.