Synchronize Requests to Execute Sequentially

Concurrent requests to the same database target or from the same generator may cause a request to fail with a database integrity violation, because the same key could be generated by different jobs. To prevent concurrent requests to the same database target, or from the same generator, configure  to synchronize the requests. Synchronized requests run sequentially, but possibly more slowly. This configuration enables synchronization for Publish, Testmatch, Rally and HP ALM requests. 
tdm49
Concurrent requests to the same database target or from the same generator may cause a request to fail with a database integrity violation, because the same key could be generated by different jobs. To prevent concurrent requests to the same database target, or from the same generator, configure
Test Data Manager
 to synchronize the requests. Synchronized requests run sequentially, but possibly more slowly. This configuration enables synchronization for Publish, Testmatch, Rally and HP ALM requests. 
Follow these steps:
  1. Navigate to the
    TDM_HOME\conf
    folder.
  2. Open the
    application.properties
    file in a text editor.
  3. Specify the following parameters:
    • tdmweb.tdmJobEngineService.queueConcurrentJobs=true|false
      Specifies whether you want to synchronize the requests or not. To synchronize and execute the requests sequentially, leave this parameter set to TRUE. Set this parameter to FALSE to run jobs concurrently.
      Default:
      true
    • tdmweb.tdmJobEngineService.queueJobsOn=DP_SOURCE_AND_TARGET | CP_TARGET
      Specifies at which level to queue the requests. Set this to DP_SOURCE_AND_TARGET to synchronize the requests at the generator (data pool). Set this to CP_TARGET to synchronize the requests at database target. 
      Default:
       DP_SOURCE_AND_TARGET
       In case of synchronizing requests at target, currently the identity of the database target is determined only by the comparison of profile names. If you rename a copy of a profile, and don't change the database target, it is not identified as being the same.
    • tdmweb.tdmJobEngineService.queuePublishOnDPSource=true|false
      This parameter specifies whether you want to synchronize the
      publish
      requests at the generator or not. Set this parameter to
      true
      , to synchronize the publish requests. To run the publish requests concurrently, set this parameter to
      false
      .This parameter is applicable only, if the 
      tdmweb.tdmJobEngineService.queueJobsOn= 
      is set to 
      DP_SOURCE_AND_TARGET.
      Default:
      false
    • tdmweb.tdmJobEngineService.queuedJobTimeout=
      n
      Specifies the maximum number of seconds a request can wait for the previous request to complete. After this time period has passed, the job does not run. The job status is set to "failed" with the output message "The job was queued for too long and has timed out." To disable the timeout, set this value to
      0
      seconds. 
      Default:
      3600 seconds
  4. Save the file.
You can view the submitted requests, scheduling times, and statuses, in the TDM Portal under Requests. 
You can restart and stop the job engine without disrupting the synchronized requests. On startup, the TDM continues to process the requests that were previously in Queued state. All the jobs that were in Running state are marked as failed.