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.

Discussion

 Shankhabrata Chowdhury (Shankhabrata) Accenture Technology Architect
Accenture
IN
Shankhabrata Member since 2013 20 posts
Accenture
Posted: Dec 2, 2015
Last activity: Apr 6, 2018
Posted: 2 Dec 2015 1:44 EST
Last activity: 6 Apr 2018 19:26 EDT
Closed

Site Specific Cipher - Any Steps in Post Upgrade?

If I have Site Specific Cipher for encryption in my application, after upgrade that application to PRPC 7.1.X, do I need to do any extra/special steps for those Cipher? for example do I need to run the compileAndLoad script again with parameter "--codeset Pega-EngineCode –codesetversion 07-10-09 " ?

Regards

Shankha



**Moderation Team has archived post**


This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Updates

Posted: 8 years ago
Posted: 9 Dec 2015 6:59 EST
Chaitra Kamaraju (ChaitraKVL) PEGA Senior Manager, Product Management, Live Data
Pegasystems Inc.
IN

Hi Shankha,

If the Cipher is uploaded into the PegaRULES database with the Pega-Engine code-set version then after the upgrade it has to be updated. 

You might have to re-import the Cipher using the Pega utils giving the new engine-code, as a workaround in the engine classes you can update the engine codeset version for the specific cipher JAR which is already existing. 

To see attachments, please log in.

Related content:

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