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

 Meulenberg Meulenberg (ManuelM8288)
WW Informatik

WW Informatik
DE
ManuelM8288 Member since 2016 7 posts
WW Informatik
Posted: Jul 28, 2019
Last activity: Aug 12, 2019
Posted: 28 Jul 2019 6:53 EDT
Last activity: 12 Aug 2019 3:44 EDT
Closed
Solved

Logging of .jar Import Process

Hi,

we had some problems Importing our full Deployment package (around 50.000 instances, 280mb file) to our Production Environment (Designer Studio -> Application -> Distribution -> Import).

When we clicked "next" after the import of the package itself it took several tries and several hours to get to the next step.

So I was wondering:

1.) Is there any documentation on what exactly is happening during that step?

2.) Is there any logging we can activate to see error messages during the import process? (we didn't find anything in pega.rules).

3.) Is there a recommended limit for package size in the import wizard?

Thanks for your help.

Cheers

To see attachments, please log in.
Installation and Deployment

Accepted Solution

Posted: 5 years ago
Posted: 28 Jul 2019 11:01 EDT
Vikash Ranjan Karn (Vikash Karn)
Pegasystems Inc.
Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi,

 

You can enable logger for below classes to troubleshoot import related issues:

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

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

Show More

Hi,

 

You can enable logger for below classes to troubleshoot import related issues:

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

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

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

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

 

 

Regards,

Vikash


Show Less
To see attachments, please log in.
Posted: 5 years ago
Posted: 28 Jul 2019 7:39 EDT
Nandita Das (dasn1)
PEGA
Principal Engineer, Technical Support
Pegasystems Inc.
IN

Hi,

Below debug classes can be enabled for import process.

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

Thank You,

To see attachments, please log in.

Accepted Solution

Posted: 5 years ago
Posted: 28 Jul 2019 11:01 EDT
Vikash Ranjan Karn (Vikash Karn)
Pegasystems Inc.
Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi,

 

You can enable logger for below classes to troubleshoot import related issues:

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

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

Show More

Hi,

 

You can enable logger for below classes to troubleshoot import related issues:

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

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

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

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

 

 

Regards,

Vikash


Show Less
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