Question
Charles Schwab
US
Last activity: 13 Dec 2022 10:30 EST
Customer CodeSet External Jars Versioning
I am looking to upgrade some external jars that currently are in the customer codeset. I am curious how versioning works on these codesets. Will pega only load jars that are indicated in the same version?
Example:
A.jar, B.jar, and C.jar are listed as Codeset customer 06-01-01
B.jar, C.jar, D.jar are listed as Codeset customer 06-01-02
DSS properties/com.pega.pegarules.bootstrap.codeset.version.Customer is set to 06-01-02 means that only B.jar, C.jar, D.jar are compiled for the application?
And these can be changed quickly by updating the DSS to 06-01-01 and restarting the servers to have only A.jar, B.jar, and C.jar loaded?
Accenture
GB
@Dylan Murphy Hi, Greetings. I think if DSS is set to 06-01-02, all the jars get loaded during start-up (A, B, C, D) but if you set it to 06-01-01, only A, B, C will be loaded. Any change to DSS will need a restart of JVM as these codeset changes are applicable during start-up via prboostrap.properties.
Regards,
Bharat
Charles Schwab
US
@KOMARINA Thanks for your response.
Are you aware of any method to AB test different sets of compiled libraries without removing row from the database
Anamata
NL
@KOMARINA(and @Dylan.Murphy) Actually, this answer is incorrect. When setting DSS to 06-01-02 ONLY the jars from that specific codeset version get loaded during startup. Older versions are skipped. So in this case only B, C and D are included.