TDM Publish inconsistency with ReadyAPI


Article ID: 208953


Updated On:


CA Test Data Manager (Data Finder / Grid Tools)


We are able to run the publish jobs from TDM portal successfully. When we are trying to run the same TDM Publish with 'ReadyAPI' we are getting errors most of the time. We are seeing this issue after upgrading TDM to 4.9 version. 

Error Message:

Http Exception in TDM Publish, Error: 401 null





Looking into the error, it indicates that the Token has expired, and is no longer valid. This is unusual behavior, since tokens by default are vaildfor24 hours after they are generated.


Release : 4.9

Component : CA Test Data Manager - TDM Web Portal



Engineering had a deep dive look at this problem, and the only way this can happen is if there are two TDM Portals are sharing the same GTREP repository.

The customer confirmed their offshore team stood up a second instance of TDM Portal, which uses the same GTREP repository database as this instance, because of network restrictions keeping them from accessing the first Portal installation. This is what's causing the inconsistencies with the API.

Only one Portal can connect to the GTREP Repository. Each Portal instance should have its own repository database. To resolve this issue:

  • (Best Practice)  - Open the network up, so the offshore team has access to the TDM Portal instance, and remove the second Portal instance. 

  • (Optional) - Keep the second instance of Portal, and install a second GTREP Repository database, that only that Portal instance has access to. Note that if you choose to go this route, the user data, project data, etc, will not be shared between the two repositories. Nor will the Find & Reserve data be shared between two Portal installations (OrientDB). Any changes made in one Portal instance, will not be automatically reflected in the other instance. 

Additional Information

See the following information for copying data from one repository to another repository: