Question
CYBG
GB
Last activity: 28 Jun 2019 10:18 EDT
Where can I find prbootstrap.properties?
I see many references to this mysterious file, "prbootstrap.properties", when attempting to upgrade PRPC. The only place I have seen a copy in the Pega-supplied media is in a BIX subfolder, but I am not using BIX. Can anyone tell me where this file can be found?
I am attempting to upgrade to 7.4.
***Edited by Moderator: Lochan to tag SR***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
PEG
GB
I'm not sure what messages you're seeing during the upgrade.
Did it generate this in the temp directory when you ran the upgrade?
CYBG
GB
Hi Laurence,
Yes, it generated during the upgrade. But now I need to change it to force the correct codeset version (for some reason when we did the schema lift-and-shift to the next environment it insists on trying to start using codeset 06-01-25 instead of 07-10-35). I was expecting this to exist on the server for PRPC to pick up during startup, but no one can find it anywhere. Do you know where it should live?
PEG
GB
Well to be honest this isn’t anything that I’d tried before just now.
But when I ran the upgrade.bat as-is, this was showing: -
Configuration:
[echo] Database Type: oracledate
[echo] JDBC Driver JAR: C:\JDBC\ojdbc7.jar
[echo] Bootstrap Config: D:\MyTemp/PegaInstallTemp-27-June-2019-17.05.17/prbootstrap.properties
[echo] PegaRULES Config: D:\MyTemp/PegaInstallTemp-27-June-2019-17.05.17/prconfig.xml
[echo] PegaRULES Logging Config: D:\MyTemp/PegaInstallTemp-27-June-2019-17.05.17/prlog4j2.xml
[echo] Deployment Logging Config: ./config/deploylogging.properties
I’ve then copied the prbootstrap.properties file to my ./scripts directory and amended the setupDatabase.properties file by adding the following line: -
prbootstrap.config=D:\download2\pega\PRPC\PEGA_7_4\115943_Pega7.4\scripts\prbootstrap.properties
And now this is outputting: -
Configuration:
[delete] Deleting: D:\download2\pega\PRPC\PEGA_7_4\115943_Pega7.4\scripts\taskRuntimes\ConfigurationRuntime.properties
[echo] Database Type: oracledate
[echo] JDBC Driver JAR: C:\JDBC\ojdbc7.jar
[echo] Bootstrap Config: D:\download2\pega\PRPC\PEGA_7_4\115943_Pega7.4\scripts\prbootstrap.properties
Well to be honest this isn’t anything that I’d tried before just now.
But when I ran the upgrade.bat as-is, this was showing: -
Configuration:
[echo] Database Type: oracledate
[echo] JDBC Driver JAR: C:\JDBC\ojdbc7.jar
[echo] Bootstrap Config: D:\MyTemp/PegaInstallTemp-27-June-2019-17.05.17/prbootstrap.properties
[echo] PegaRULES Config: D:\MyTemp/PegaInstallTemp-27-June-2019-17.05.17/prconfig.xml
[echo] PegaRULES Logging Config: D:\MyTemp/PegaInstallTemp-27-June-2019-17.05.17/prlog4j2.xml
[echo] Deployment Logging Config: ./config/deploylogging.properties
I’ve then copied the prbootstrap.properties file to my ./scripts directory and amended the setupDatabase.properties file by adding the following line: -
prbootstrap.config=D:\download2\pega\PRPC\PEGA_7_4\115943_Pega7.4\scripts\prbootstrap.properties
And now this is outputting: -
Configuration:
[delete] Deleting: D:\download2\pega\PRPC\PEGA_7_4\115943_Pega7.4\scripts\taskRuntimes\ConfigurationRuntime.properties
[echo] Database Type: oracledate
[echo] JDBC Driver JAR: C:\JDBC\ojdbc7.jar
[echo] Bootstrap Config: D:\download2\pega\PRPC\PEGA_7_4\115943_Pega7.4\scripts\prbootstrap.properties
[echo] PegaRULES Config: D:\MyTemp\PegaInstallTemp-27-June-2019-17.05.17/prconfig.xml
[echo] PegaRULES Logging Config: D:\MyTemp\PegaInstallTemp-27-June-2019-17.05.17/prlog4j2.xml
[echo] Deployment Logging Config: ./config/deploylogging.properties
Looks like it should be worth a try
Pegasystems Inc.
US
Are you seeing an error during the upgrade or post upgrade? You should not need to modify anything with this during the upgrade. Please post the upgrade log with the error that you are seeing.
CYBG
GB
Thanks Laurence. I'll give that a try.
Celeste - we're hitting an issue during startup whereby PRPC appears to be using the 06-01-25 codeset. We know the rules schema has the 07-10-35 codeset because we've copied it from another environment where it's working correctly. So we were thinking of trying to "kick-start" PRPC into using the correct codeset, hopefully just the once, then it would correct itself and pick up the right one later.
I'll let you know how I get on.
CYBG
GB
OK, so it didn't seem to do anything. Turns out my colleagues have an SR open with Pega about this, so it's probably best if I continue this with them rather than duplicating any effort. Many thanks for your help thus far.
Pegasystems Inc.
IN
Thank you for the update! Please let us know the SR number here so that we may continue to track this issue.
CYBG
GB
Sure. It's SR-D25138.
Pegasystems Inc.
IN
Thank you!