PII Heat Map is slow to open in TDM Portal 4.10.221.0
search cancel

PII Heat Map is slow to open in TDM Portal 4.10.221.0

book

Article ID: 373984

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

We started noticing that it takes anywhere from 30 minutes to 1 hour to open the PII Heat Map for some of our larger projects. 

Environment

TDM Portal 4.10.221.0

Cause

With TDM Portal in Debug mode; in the TDMModelService.log, we see that it takes a long time for TDM to build the Index maps in the gtrep repository, for the project in question.

For example:

[M:GET][P:/api/ca/v1/datamodel/profile/piidataheat]                   c.c.t.c.d.c.MssqlProfileBuilder:  Final connection string: [jdbc:sqlserver://<HOSTNAME>:<PORT>;database=<DATABASE>;integratedSecurity=true;trustServerCertificate=true]
[M:GET][P:/api/ca/v1/datamodel/profile/piidataheat]                       c.c.t.p.c.ResultsController:  RequestID: xxx, Module: Profiler_Service, getting Pii Data for job: nnnn
[M:GET][P:/api/ca/v1/datamodel/profile/piidataheat]                       c.c.t.p.c.ResultsController:  RequestID: xxx, Module: Profiler_Service, Get row counts for all tables ahead of time for job: nnnn 
[M:GET][P:/api/ca/v1/datamodel/entities]                  c.c.t.d.s.DataModelEntityService:  Returning relationships for '1000' entities
[SimpleAsyncTaskExecutor-1] --- [U:][M:][P:]                c.c.t.s.c.EventRegistrationService:  EventRegistrationService:successfully registered notification endpoints with project service
[M:GET][P:/api/ca/v1/datamodel/profile/piidataheat]                       c.c.t.p.c.ResultsController:  RequestID: xxx, Module: Profiler_Service, Get counts in gtrep_pii_raw_match for job: nnnn
[M:GET][P:/api/ca/v1/datamodel/profile/piidataheat]                       c.c.t.p.c.ResultsController:  RequestID: xxx, Module: Profiler_Service, Now add on tables missed out because there was no PII for job: nnnn
[M:GET][P:/api/ca/v1/datamodel/profile/piidataheat]                       c.c.t.p.c.ResultsController:  RequestID: xxx, Module: Profiler_Service, Done with getting PiiData For job: nnnn 
[M:GET][P:/api/ca/v1/datamodel/profile/piidataheat]                       c.c.t.p.c.ResultsController:  RequestID: xxx, Module: Profiler_Service, producing heat map for 973 tables 
[M:GET][P:/api/ca/v1/datamodel/profile/piidataheat]                       c.c.t.p.c.ResultsController:  RequestID: xxx, Module: Profiler_Service, Build index maps as we go for <TABLE_1> referencing 1 tags
[M:GET][P:/api/ca/v1/datamodel/profile/piidataheat]                       c.c.t.p.c.ResultsController:  RequestID: xxx, Module: Profiler_Service, Build index maps as we go for <TABLE_2> referencing 2 tags
[M:GET][P:/api/ca/v1/datamodel/profile/piidataheat]                       c.c.t.p.c.ResultsController:  RequestID: xxx, Module: Profiler_Service, Build index maps as we go for <TABLE_3> referencing 2 tags
....

Resolution

The delay in building out the index maps has been addressed in TDM Portal version 4.10.261.0 or greater.

The TDMWeb-4.10.261.0 patch is available for download from the Test Data Manager (TDM) Support Patches page.

It's recommended to back up the gtrep repository database, and the OrientDB database files, before apply ant TDM Portal patch

Additional Information

For more information on patching TDM components, see "How to apply patches for TDM".