Content merge is a complex feature and should be performed only by an administrator. Only users who are members of the Administrator group will see the Content merge option under the Tools menu.
If this is your first time running content merge, please read the online help on the topic of content merge carefully.
1. For Worksoft Certify 8.4.1, please use patch 8.4.1.178 and up and for Worksoft Certify 8.3.2, please use patch 8.3.2.141 and up.
2. Start by taking a back up of the database.
3. Run the Database validation tool (Please see details below).
4. Use content merge on only one machine at one time. Do not
attempt to use content merge on more than one machine simultaneously.
5. Please note that only the map windows and objects used by the selected processes will be merged.
6. For older versions of Certify, the user may be required to add
application versions back to the project after content merge (via the
Project editor)
7. Recommended for large projects:
a. Select a small Process
subfolder (one containing very few processes) to merge. (Don't select
anything else, the needed dependencies will be automatically checked.
b. If the merge went well, select the rest of the processes to merge (one subfolder at a time).
8. If there is a problem during content merge, please file a case with the following information
a. Certify version and patch level
b. Name of projects being merged
c. Attach a screen capture of the error message (preferably in a
JPG or PNG file) showing additional details (if available).
d. Attach the Certify log from C:\Documents and Settings\<username>\Application Data\Worksoft\log-file.txt to the case
e. Attach the Content merge log file from C:\Documents and Settings\<username>\Application Data\Worksoft\ContentMerge.log to the case
f. Run the database validation in C:\program files\worksoft\Certify\Client\DatabaseValidation.exe and attach the log file in c:\temp\DatabaseValidation.log in the case. (Please see the instructions for running the Database Validation from the command line below.)
g. If possible, please provide the most recent copy of the database backup.
Existing limitations of content merge
Existing limitations besides requiring the database be clean (by running the latest Database validation tool) are
1. The source and destination database must have identical ICL data
2. When there are two of the same name in both projects which are of different type.
3. When the user selects a process or process folder, content merge will select any recordsets and variables required by the selected processes. If the user selects certain processes in the source project which uses variable in the recordset name field. If the user does not explicitly select the corresponding recordset, content merge will not be able to determine that the recordset is required by the selected process during run time.
Instructions for running the Database Validation for content merge (for Certify 8.4.1 and up):
1. Open a Command Prompt
2. CD to the C:\program files\worksoft\Certify\Client\ folder
3. Type in DatabaseValidation.exe {servername} {databasename}
{sausername} {sapassword} where {servername} is the name of your
database server,
{databasename} is the name of your Certify database,
{sausername} is the login id for a user with SA permissions on the database,
{sapassword} is the password for {sausername}
Example: C:\program files\worksoft\Certify\Client\DatabaseValidation.exe SRV_CERTIFY1, Certify, sa, sapa$$w0rd
4. Once the Database Validation completes, it will produce a log file in the temp folder called "DatabaseValidation.log".