Support Article
FirstUseAssemblerException in AES logs due to SQLParser
SA-2620
Summary
User has noticed FirstUseAssemblerException in PegaRULES log file which was caused due to SQLParser - "com.pega.aes cannot be resolved to a type".
Error Messages
Caused by: com.pega.pegarules.pub.generator.FirstUseAssemblerException: Failed to compile generated Java com.pegarules.generated.activity.ra_action_processpcfsql_47e4592fdb1d89b4da6bd07288c8a014: ----------
1. ERROR in com/pegarules/generated/activity/ra_action_processpcfsql_47e4592fdb1d89b4da6bd07288c8a014.java (at line 245)
com.pega.aes.utils.sql.SQLParser parser = new com.pega.aes.utils.sql.SQLParser();
^^^^^^^^^^^^
com.pega.aes cannot be resolved to a type
----------
2. ERROR in com/pegarules/generated/activity/ra_action_processpcfsql_47e4592fdb1d89b4da6bd07288c8a014.java (at line 245)
com.pega.aes.utils.sql.SQLParser parser = new com.pega.aes.utils.sql.SQLParser();
^^^^^^^^^^^^
com.pega.aes cannot be resolved to a type
Steps to Reproduce
NA
Root Cause
During AES installation, developer has to import 5 .jar files into the PegaRULES database with the codeset name “pegaaes”. You can find them by running the query - s
elect distinct pzjar from pr_engineclasses where pzcodeset='pegaaes'
. Pega-provided activity PegaAES-Data-UtilityObject fails to compile because it does not find the SQLParser class. Resolution
For the PRPC engine to load these JAR files, developer must add the Dynamic System Setting:
properties/com.pega.pegarules.bootstrap.codeset.version.pegaaes/default
and value: 07-20-01 with Owning ruleset: Pega-Engine
For more details, refer the PDN article.
Published January 31, 2016 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.