Question
1
Replies
291
Views
Capgemini
Posted: June 12, 2019
Last activity: July 9, 2019
Closed
Personal Edition - Do we Have some limitation with try install a specific framework ?
Hey Community,
So, I have the Pega personal edition version 8.1 in my work station and I need study and analyze the behavior that my application, generated in Pega Version 7.2.2 can have in Pega Version 8.1
I have installed the personal edition, that contain Tomcat application Server and Postgree database.
I have installed the Pega Underwriting Insurance 8.1. Follow the installation guide, after completed import package, we reserted the application server. However, when I started the application server i Received the follow warnings:
Some class/tables couldn´t be identified
2019-06-12 10:04:48,882 [ NTB143777] [ STANDARD] [ ] [ ] (nal.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL PEGAINS-DATA-APPLICATION-COMM-AUTO SETDRIVERPOSTPARAMS #20180826T132513.048 GMT due to Database-BadClassDefPegaIns-Data-Application-Comm-Auto; This may cause the wrong rule to run during rule execution.
After installation , was possible to saw that Pega Insurance NBB8 was available:
Records -> Application Definition -> Application
Attchament: Figure 1
However , when the server is starting this application not work fine:
2019-06-12 16:17:11,531 [http-nio-8080-exec-9] [ STANDARD] [ ] [ PegaRULES:8] (ngineinterface.service.HttpAPI) ERROR localhost|0:0:0:0:0:0:0:1 - Exception occured:
com.pega.pegarules.pub.context.PRSecurityException: Unable to construct authorization core due to authorization failure
com.pega.pegarules.pub.context.PRSecurityException: Unable to construct authorization core due to authorization failure
Caused by: com.pega.pegarules.pub.context.InvalidApplicationReferenceException: No such Rule-Application instance: PegaInsurance:8
Someone can help to understand that , if we have limitations to use this personal edition to work with anothers Framewrok.
Hi,
Thanks for posting the query.
Could you please set / replace the below SystemName property value to pega in prconfig.xml. Please restart the server after this change.
<env name="Identification/SystemName" value="pega" />