Siebel Application Deployment Manager Guide > Guidelines for Deploying Siebel ADM >

Using the SRFDiff Utility for Validation and Diagnosis

The SRFDiff utility compares two given SRF files, which is useful for validating the SRF files when using Siebel Application Deployment Manager (ADM) to deploy repository data, and for diagnostic purposes. The validation and diagnostic scenarios for using SRFDiff include the following environments: development, test, staging, and production.

See also Synchronizing Repository Updates. For more information on using the SRFDiff utility, see Using Siebel Tools.

To use the SRFDiff utility in validation mode

1. Generate the package from the development environment.
2. Create test environment as a clone of the production environment.
3. Deploy the repository deployment units (SIF files) from the package to the test environment.
4. Compile the SRF to a temporary location on the test environment.
5. Add the SRF from the temporary location to the package as a file item.
6. Deploy the file units, which includes the SRF, and database units to the test environment.
7. Test and verify the changes.
8. Create the staging environment as a clone of the production environment.
9. Deploy the package to the staging environment.
10. Compile the SRF to a temporary location in the staging environment.
11. Run SRFDiff on the files created in Step 4 and Step 10.

NOTE:  No differences between these two SRF files indicates that the SRF and repository tables in the test environment were correctly cloned from the production environment. If there are any differences in the SRF files, do not deploy to the production environment.

To use the SRFDiff utility in diagnostic mode (SRF can be compiled in the production environment)

1. Compile the SRF to a temporary location in the production environment.
2. Run SRFDiff on the SRF created in Step 1 and the current SRF file in SIEBSRVR_ROOT\objects\lang directory.

NOTE:  No differences between the two SRF files indicates that the SRF and repository tables are synchronized. Any differences between the two SRF files indicates that the SRF and repository tables are out of synchronization.

To use the SRFDiff utility in diagnostic mode (SRF cannot be compiled in the production environment due to downtime concerns)

1. Export the repository as a .dat file from the production environment.
2. Import the .dat file to a temporary system.
3. Compile the SRF on the temporary system (thus avoiding downtime in the production environment).
4. Run SRFDiff on the SRF created in Step 3 and the current SRF file located in the SIEBSRVR_ROOT\objects\lang directory of the production environment.

NOTE:  No differences between the two SRF files indicates that the SRF and repository tables are synchronized. Any differences between the two SRF files indicates that the SRF and repository tables are out of synchronization.

To use the SRFDiff utility in diagnostic mode (SRF cannot be compiled in the production environment due to non-binary collation)

1. Export the repository as a .dat file from the production environment.
2. Import the repository to a temporary system that has binary collation (and thus can be SRF compiled).
3. Compile the SRF on the temporary system (thus avoiding downtime in the production environment).
4. Run SRFDiff on the SRF created in Step 3 and the current SRF file located in the SIEBSRVR_ROOT\objects\lang directory of the production environment.

NOTE:  No differences between the two SRF files indicates that the SRF and repository tables are synchronized. Any differences between the two SRF files indicates that the SRF and repository tables are out of synchronization.