Steps for successful content merge

Yujira — Wed, 23 Feb 2011 21:57:37 GMT

Current revision posted to Worksoft Certify Product Wiki by Yujira on 2/23/2011 3:57:37 PM

Steps for successful content merge

Filed under: Content merge, Certify 8.4.1, Certify 8.5.0, MergeCertify 8.5.1, Content, Content merge, Copying, MergingData, ProjectsMerge, DataMerging, Certify 8.5.1Projects

This article refers to both the Standalone Content merge tool (available in 8.5.0 and later versions of Certify. However, it is also applicable to the Content merge option under the Tools menu in Certify 8.4.1 as well.

Warning: Content merge is an administrator only tool. Only Certify users who are members of the Administrator group will be able to use this tool.

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.5.0, please use patch 8.5.0.409 and up.

*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. Back up the Certify database.

3. Run the Database validation tool (Please see details below).

4. Use Content merge on only one machine at one time. Please do not attempt to use content merge on more than one machine (pointing to the same Certify database) 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. This is done by going to the Project Editor to edit the project and select the appropriate application versions.

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 source and target projects and the process folder (or processes) being merged.

c. Name Names of projects being merged (both source and destination)

d. A screenshot of the Content merge dialog showing the selected process folders, variables, layouts, etc.

e . Attach a A screen capture of the error message (preferably in a JPG or PNG file) showing additional details (if available).

f.Attach the Certify The certify log from C:\Documents and Settings\<username>\Application Data\Worksoft\log-file.txt to the case
f

   g. Attach the Content The content merge log file from C:\Documents and Settings\<username>\Application Data\Worksoft\ContentMerge.log to the case
   g   .
   h 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.)
   h
   i. If possible, please provide the most recent copy of the database backup. If the merge is done between two different databases, then we'll need backup files from both databases. (We'll need database backup files that are an exact match of the one where you are currently having issues since the ICL data issue might have occurred recently).

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.5.0 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".

Steps for successful content merge

Yujira — Wed, 23 Feb 2011 21:56:02 GMT

Revision 17 posted to Worksoft Certify Product Wiki by Yujira on 2/23/2011 3:56:02 PM

Steps for successful content merge

Filed under: Content merge, Certify 8.4.1, Certify 8.5.0, Merge, Content, Copying, Merging, Projects, Data, Certify 8.5.1

1. For Worksoft Certify 8.5.0, please use patch 8.5.0.409 and up.

*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. Back up the Certify database.

3. Run the Database validation tool (Please see details below).

4. Use Content merge on only one machine at one time. Please do not attempt to use content merge on more than one machine (pointing to the same Certify database) simultaneously.

5. Please note that only the map windows and objects used by the selected processes will be merged.

7. Recommended for large projects:

8. If there is a problem during content merge, please file a case with the following information

a. Certify version Name of source and patch level target projects and the process folder (or processes) being merged.

b. Name of projects being merged (both source and destination)

c. A screenshot of the Content merge dialog showing the selected process folders, variables, layouts, etc.

d . Attach a screen capture of the error message (preferably in a JPG or PNG file) showing additional details (if available).
d

e. Attach the Certify log from C:\Documents and Settings\<username>\Application Data\Worksoft\log-file.txt to the case
   e
   f. Attach the Content merge log file from C:\Documents and Settings\<username>\Application Data\Worksoft\ContentMerge.log to the case
   f
   g   . 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
   h. If possible, please provide the most recent copy of the database backup. If the merge is done between two different databases, then we'll need backup files from both databases. (We'll need database backup files that are an exact match of the one where you are currently having issues since the ICL data issue might have occurred recently).

Existing limitations of content merge

Steps for successful content merge

Yujira — Wed, 23 Feb 2011 17:46:01 GMT

Revision 16 posted to Worksoft Certify Product Wiki by Yujira on 2/23/2011 11:46:01 AM

Steps for successful content merge

Filed under: Content merge, Certify 8.4.1, Certify 8.5.0, Merge, Content, Copying, Merging, Projects, Data, Certify 8.5.1

This article refers to both the Standalone Content merge is a complex feature tool (available in 8.5.0 and should be performed only by later versions of Certify. However, it is also applicable to the Content merge option under the Tools menu in Certify 8.4.1 as well.

Warning: Content merge is an administrator only tool. Only Certify users who are members of the Administrator group will see the Content merge option under the Tools menube able to use this tool.

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.5.0, please use patch 8.5.0.409 and up.

*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 Back up of the Certify database.

3. Run the Database validation tool (Please see details below).

4. Use content Content merge on only one machine at one time. Do Please do not attempt to use content merge on more than one machine (pointing to the same Certify database) 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 . This is done by going to the Project editor)Editor to edit the project and select the appropriate application versions.

7. Recommended for large projects:

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

Instructions for running the Database Validation for content merge (for Certify 8.4.1 8.5.0 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".

Steps for successful content merge

Yujira — Wed, 14 Apr 2010 00:20:36 GMT

Revision 15 posted to Worksoft Certify Product Wiki by Yujira on 4/13/2010 7:20:36 PM

Steps for successful content merge

Filed under: Content merge, Certify 8.4.1, Merge, Content, Copying, Merging, Projects, Data

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:

8. If there is a problem during content merge, please file a case with the following information

Existing limitations of content merge

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".

Steps for successful content merge

Yujira — Wed, 14 Apr 2010 00:20:36 GMT

Revision 14 posted to Worksoft Certify Product Wiki by Yujira on 4/13/2010 7:20:36 PM

Steps for successful content merge

Filed under: Content merge

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. Running 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:

8. If there is a problem during content merge, please file a case with the following information

Existing limitations of content merge

Instructions for running the Database Validation for content merge (for Certify 8.4 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".

Steps for successful content merge

Yujira — Fri, 26 Feb 2010 18:14:14 GMT

Revision 13 posted to Worksoft Certify Product Wiki by Yujira on 2/26/2010 12:14:14 PM

Steps for successful content merge

Filed under: Content merge

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. Running the Database validation tool

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:

8. If there is a problem during content merge, please file a case with the following information

Existing limitations of content merge

Instructions for running the Database Validation for content merge (for Certify 8.4 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".

Steps for successful content merge

Yujira — Fri, 26 Feb 2010 18:13:54 GMT

Revision 12 posted to Worksoft Certify Product Wiki by Yujira on 2/26/2010 12:13:54 PM

Steps for successful content merge

Filed under: Content merge

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.2.Start cleaning up any data issues by running

3. Running the Database validation toolwhich can be downloaded from the media section.
3

4. Use content merge on only one machine at one time. Do not attempt to use content merge on more than one machine simultaneously.
4

5. Please note that only the map windows and objects used by the selected processes will be merged.
5

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)
6

7. Recommended for large projects:

8. If there is a problem during content merge, please file a case with the following information

Existing limitations of content merge

Steps for successful content merge

Yujira — Fri, 26 Feb 2010 18:02:36 GMT

Revision 11 posted to Worksoft Certify Product Wiki by Yujira on 2/26/2010 12:02:36 PM

Steps for successful content merge

Filed under: Content merge

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.Start by taking a back up of the database. 2.Start cleaning up any data issues by running the Database validation tool which can be downloaded from the media section.
3. Use content merge on only one machine at one time. Do not attempt to use content merge on more than one machine simultaneously.
4. Please note that only the map windows and objects used by the selected processes will be merged.
5. 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)
6. 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).
7. 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. </username></username>

Existing limitations of content merge

Steps for successful content merge

Yujira — Tue, 08 Dec 2009 01:29:39 GMT

Revision 10 posted to Worksoft Certify Product Wiki by Yujira on 12/7/2009 7:29:39 PM

Steps for successful content merge

Filed under: Content merge

Content merge is a complex feature and should be performed only by an administrator.

If this is your first time running content merge, please read the online help on the topic of content merge carefully.
1.Start by taking a back up of the database. 2.Start cleaning up any data issues by running the Database validation tool which can be downloaded from the media section.
2
3. Use content merge on only one machine at one time. Do not attempt to use content merge on more than one machine simultaneously.
3
4. Please note that only the map windows and objects used by the selected processes will be merged.
4
5. 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)
5
6. 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).
6
7. 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. </username></username>

Existing limitations of content merge

Steps for successful content merge

Yujira — Tue, 08 Dec 2009 01:28:18 GMT

Revision 9 posted to Worksoft Certify Product Wiki by Yujira on 12/7/2009 7:28:18 PM

Steps for successful content merge

Filed under: Content merge

Content merge is a complex feature and should be performed only by an administrator.

1. Please

If this is your first time running content merge, please read the online help on the topic of content merge carefully.
1.Start by cleaning up any data issues by running the Database validation tool which can be downloaded from the media section.
2. Use content merge on only one machine at one time. Do not attempt to use content merge on more than one machine simultaneously.
3. Please note that only the map windows and objects used by the selected processes will be merged.
4. 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)
5. 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).
6. 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. </username></username>

Existing limitations of content merge

<p>

Steps for successful content merge

Yujira — Tue, 08 Dec 2009 01:10:58 GMT

Revision 8 posted to Worksoft Certify Product Wiki by Yujira on 12/7/2009 7:10:58 PM

Steps for successful content merge

Filed under: Content merge

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.
2
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.

<p>

Steps for successful content merge

Yujira — Tue, 08 Dec 2009 01:08:36 GMT

Revision 7 posted to Worksoft Certify Product Wiki by Yujira on 12/7/2009 7:08:36 PM

Steps for successful content merge

Filed under: Content merge

Existing limitations

<p>

Steps for successful content merge

Yujira — Tue, 08 Dec 2009 01:08:12 GMT

Revision 6 posted to Worksoft Certify Product Wiki by Yujira on 12/7/2009 7:08:12 PM

Steps for successful content merge

Filed under: Content merge

Existing limitations

Existing limitations besides requiring the database be clean (by running the latest Database validation tool) are
1. When there are two of the same name in both projects which are of different type.
2. 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 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".

Steps for successful content merge

Yujira — Mon, 24 Aug 2009 21:57:59 GMT

Revision 5 posted to Worksoft Certify Product Wiki by Yujira on 8/24/2009 4:57:59 PM

Steps for successful content merge

Filed under: Content merge

Content merge is a complex feature and should be performed only by an administrator.

1. Please read the online help on the topic of content merge carefully.
2. Use content merge on only one machine at one time. Do not attempt to use content merge on more than one machine simultaneously.
3. Please note that only the map windows and objects used by the selected processes will be merged.
4. 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)
5. 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).
6. 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. </username></username>

Instructions for running the Database Validation for content merge (for Certify 8.4 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".

Steps for successful content merge

Yujira — Wed, 05 Aug 2009 22:26:14 GMT

Revision 4 posted to Worksoft Certify Product Wiki by Yujira on 8/5/2009 5:26:14 PM

Steps for successful content merge

Filed under: Content merge

Content merge is a complex feature and should be performed only by an administrator.

1. Please read the online help on the topic of content merge carefully.
2. Use content merge on only one machine at one time. Do not attempt to use content merge on more than one machine simultaneously.
3. Please note that one only the map windows/objects windows and objects used by the selected process processes will be merged.
4. For older versions of Certify, the user may be required to add application version versions back to the project after content merge (via the Project editor)
5. Recommended for large projects: a. Select a process small Process subfolder (one containing very few processes) to merge. (Don’t '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).
6. 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. Capture the screenshot with 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 a the most recent copy of the database backup. </username></username>

Instructions for running the Database Validation for content merge:

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”. "DatabaseValidation.log".

Steps for successful content merge

Yujira — Wed, 05 Aug 2009 22:00:03 GMT

Revision 3 posted to Worksoft Certify Product Wiki by Yujira on 8/5/2009 5:00:03 PM

Steps for successful content merge

Filed under: Content merge

Content merge is a complex feature and should be performed only by an administrator. 1.

Please read the online help on the topic of content merge carefully. 2.
Use content merge on only one machine at one time. Do not attempt to use content merge on more than one machine simultaneously. 3.
Please note that one the map windows/objects used by the selected process will be merged. 4.
For older versions of Certify, the user may be required to add application version back to the project after content merge (via the Project editor) 5.
Recommended for large projects: a. Select a process small subfolder to merge (Don’t 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). 6.
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. Capture the screenshot with the error message
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 a copy of the database backup. </username></username>

Instructions for running the Database Validation for content merge: 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”. “DatabaseValidation.log”.