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

 ChennaReddy Marreddy (ChennaReddyM)
Accenture

Accenture
IN
ChennaReddyM Member since 2013 20 posts
Accenture
Posted: Mar 15, 2016
Last activity: Apr 5, 2016
Posted: 15 Mar 2016 12:20 EDT
Last activity: 5 Apr 2016 12:44 EDT
Closed

How to handle Unlocked RuleSet Exception in Automation script.

Hi All,

I Added an Unlocked RuleSet,RuleSet Version into a Product(RAP) to move the code to Higher environment. And i didn't check the option "Allow Unlocked RuleSet Versions? " and  Saved it.

While creating the Jar file, it is giving error as shown below.

"The Product is referencing unlocked RuleSet Version instances, please follow the links below to lock them or update your Product rule to allow unlocked Versions to be exported. Be sure to save the Product rule if allowing unlocked RuleSet Versions to be exported, otherwise your change won't take effect."

The above is error is expected.

Now I tried to pull out the Jar file from the Product(RAP) using Automation script(Utils under script which will be shipped along with PRPC installable files).

The Jar file is created.

How to identify this exception in the logs of script. Do we get any warning in the logs?

Why the script is still proceeding with the Jar file creation even the Product is not proper(i mean either we need to lock the ruleset or we need to select the option "Allow Unlocked RuleSet Versions?" in Product while creating it)?

But i can see some errors in log file as shown below.These errors are representing the same unlocked RuleSet thing?, if yes, how to handle this?

Show More

Hi All,

I Added an Unlocked RuleSet,RuleSet Version into a Product(RAP) to move the code to Higher environment. And i didn't check the option "Allow Unlocked RuleSet Versions? " and  Saved it.

While creating the Jar file, it is giving error as shown below.

"The Product is referencing unlocked RuleSet Version instances, please follow the links below to lock them or update your Product rule to allow unlocked Versions to be exported. Be sure to save the Product rule if allowing unlocked RuleSet Versions to be exported, otherwise your change won't take effect."

The above is error is expected.

Now I tried to pull out the Jar file from the Product(RAP) using Automation script(Utils under script which will be shipped along with PRPC installable files).

The Jar file is created.

How to identify this exception in the logs of script. Do we get any warning in the logs?

Why the script is still proceeding with the Jar file creation even the Product is not proper(i mean either we need to lock the ruleset or we need to select the option "Allow Unlocked RuleSet Versions?" in Product while creating it)?

But i can see some errors in log file as shown below.These errors are representing the same unlocked RuleSet thing?, if yes, how to handle this?

[java] 2016-03-15 15:51:49,720 [localhost] [  STANDARD] [     PegaRULES:07.10] (  internal.access.DatabaseImpl) ERROR JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Cannot open the requested instance '': class or class group "" does not exist.

     [java] 2016-03-15 15:51:50,284 [localhost] [  STANDARD] [     PegaRULES:07.10] (   internal.util.CollectorImpl) ERROR JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Error adding . Class <blank> does not exist

     [java] 2016-03-15 15:51:50,285 [localhost] [  STANDARD] [     PegaRULES:07.10] (  internal.access.DatabaseImpl) ERROR JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Cannot open the requested instance '': class or class group "" does not exist.

     [java] 2016-03-15 15:51:50,297 [localhost] [  STANDARD] [     PegaRULES:07.10] (   internal.util.CollectorImpl) ERROR JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Error adding . Class <blank> does not exist

     [java] 2016-03-15 15:51:50,297 [localhost] [  STANDARD] [     PegaRULES:07.10] (  internal.access.DatabaseImpl) ERROR JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Cannot open the requested instance '': class or class group "" does not exist.

     [java] 2016-03-15 15:51:50,298 [localhost] [  STANDARD] [     PegaRULES:07.10] (   internal.util.CollectorImpl) ERROR JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Error adding . Class <blank> does not exist

     [java] 2016-03-15 15:52:52,323 [localhost] [  STANDARD] [     PegaRULES:07.10] (         internal.util.MoveLog) INFO  JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Operation Status: Exporting 629 instance(s).

     [java] 2016-03-15 15:52:52,324 [localhost] [  STANDARD] [     PegaRULES:07.10] (         internal.util.MoveLog) INFO  JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Operation Status: Exporting Inventory

     [java] 2016-03-15 15:52:56,273 [localhost] [  STANDARD] [     PegaRULES:07.10] (  internal.access.SQLGenerator) WARN  JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Unable to locate case-sensitive column name PXREQUIREDSKILL on table KPN_CM_INDEX_ORDERLINES. If this table will be accessed by Obj-* methods, create the corresponding Rule-Obj-Property definitions, otherwise if this is an external table to be accessed by RDB-* methods, disregard this message.

     [java] 2016-03-15 15:52:56,281 [localhost] [  STANDARD] [     PegaRULES:07.10] (  internal.access.SQLGenerator) WARN  JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Unable to locate case-sensitive column name PXSKILLNAME on table KPN_CM_INDEX_ORDERLINES. If this table will be accessed by Obj-* methods, create the corresponding Rule-Obj-Property definitions, otherwise if this is an external table to be accessed by RDB-* methods, disregard this message.

     [java] 2016-03-15 15:52:56,294 [localhost] [  STANDARD] [     PegaRULES:07.10] (  internal.access.SQLGenerator) WARN  JSR94|Deployment|Utility|pxExportApp|A02417A6FF46CF845619819D754114479  - Unable to locate case-sensitive column name PXSKILLRATING on table KPN_CM_INDEX_ORDERLINES. If this table will be accessed by Obj-* methods, create the corresponding Rule-Obj-Property definitions, otherwise if this is an external table to be accessed by RDB-* methods, disregard this message.


Show Less
To see attachments, please log in.
Pega Customer Service
System Administration
Low-Code App Development
Data Integration

Posted: 8 years ago
Posted: 5 Apr 2016 12:44 EDT
Kumar (VipinKumar38163630)

Hi Chenna, It seems like the command line tool failes to perform the same validation as the UI export tool. You should report that to Pega Support as a potential product defect. The errors you are seeing in log are related to the RAP export evident by 'pxExportApp' in the log messages.

Do not go aheap with this RAP and instead follow the best practice of locking the ruleset before the export.

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