Question

1
Replies
93
Views
 Fabian Diaz (Fabian_Diaz)
WellCare

WellCare
US
Fabian_Diaz Member since 2015 17 posts
WellCare
Posted: March 22, 2017
Last activity: March 24, 2017
Posted: 22 Mar 2017 10:08 EDT
Last activity: 24 Mar 2017 8:46 EDT
Closed
Solved

DEBUG Classes for Import process

Hi Team,

Does anyone has the name of the classes so we can put the import on DEBUG mode?

Thank you,

Fabian

System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.

Accepted Solution

Posted: 4 years ago
Posted: 22 Mar 2017 10:38 EDT
Umamaheshwar Reddy Midthuru (Mahesh Midthuru)
PEGA
Sr. Software Solutions Engineer
Pegasystems Inc.
US

Hi Fabian,


You can find the list of common classes which you can debug in import process are as follows:


  • com.pega.pegarules.deploy.internal.inventory.SynchronizerImpl

  • com.pega.pegarules.deploy.internal.loaders.SaverLoader

  • com.pega.pegarules.deploy.internal.util.ImportImpl 

  • com.pega.pegarules.deploy.internal.archive.ApplicationBundle

  • com.pega.pegarules.deploy.internal.archive.PegaArchiveImpl

If you are debugging the schema related changes as well the you can enable the below loggers as well:


  • com.pega.pegarules.data.internal.access.DatabaseSchemaGeneratorImpl

  • com.pega.pegarules.deploy.internal.util.SchemaImporterTool

  • com.pega.pegarules.deploy.internal.archive.SchemaArchiveImpl

Hope this information might be sufficient for you to figure out the root cause of the issue.


Regards


Mahesh