What is the Codeset
Codeset is:
"A CodeSet is a name for a set of Java code and JAR files that are stored in the pr_engineclasses table in the PegaRULES database. Analogous to a RuleSet, a CodeSet version has the structure Name:99-99-99, where 99-99-99 is a version. Version 6.X+ contains two CodeSets, Pega-EngineCode and Customer. The optional Customer CodeSet can identify customer-created and third-party JAR files that are uploaded into the database."
Can anyone explain pros and cons when you use Codeset:06-01-01 and your own ruleset (ex. MyApp:01-01-01) when you import external Jar file. What kind of differences will it make?
Thanks,
Pegasystems Inc.
US
The difference is that if you use the default codeset value/version as shown above, pega engine will load your jars automatically upon restart. But this can be a maintenance nightmare if you have so many different external jars. The better way is to enter your own codeset name/version so that you can control what code/version of jars being loaded by pega engine. However, you need to add an extra DSS to enable Pega engine loading the jars. See the screenshot here for an example - the codeset name is pegamkt3rdparty, version is 08-04-01. So the DSS is (owning ruleset if Pega-Engine) properties/com.pega.pegarules.bootstrap.codeset.version.<codeset name> with the value <codeset version>. So if you have some class conflict issue with OOTB pega jars, you can update the codeset version to something different from what you used when importing the jars, then your jars will not be loaded into pega engine. No database access needed, very convenient.
