Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Fabian Diaz (Fabian_Diaz)
WellCare

WellCare
US
Fabian_Diaz Member since 2015 17 posts
WellCare
Posted: Mar 22, 2017
Last activity: Mar 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

To see attachments, please log in.
System Administration

Accepted Solution

Posted: 7 years ago
Posted: 22 Mar 2017 10:38 EDT
Mahesh Midthuru (Mahesh Midthuru)
PEGA
Senior Principal Application Engineer, Customer Service Digital
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

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice