Move application to different database
Hi All,
We want to move the application to use a different database, where we doesn't want data such as decisioning and others to be lost. From the JBoss or Pega side (Cassandra, Kafka), what type of data needs to be retained so that decisioning not lost and what kind of data needs to be deleted so pega can refer to the new configuration.
is there any check list to move application to different database or best practice?
Thank you
Accepted Solution
Updated: 4 Jan 2024 9:10 EST
Pegasystems Inc.
GB
@OdiS9903 There will likely not be any official documentation for this type of thing.
there are best practices for moving a Pega application to a different database. Here are some key steps:
@OdiS9903 There will likely not be any official documentation for this type of thing.
there are best practices for moving a Pega application to a different database. Here are some key steps:
- Compare the source and target systems. Confirm that the Pega Platform version number of the target system is not earlier than the version number of the source system.
- Prepare the target system for migration. On the target system, access the Records Explorer and confirm that the target system includes all the prerequisite rulesets and versions.
- On the source system, create a product rule or product patch rule. Confirm that none of the rules to be migrated are checked out.
- Create a restore point on the target system so that you can roll back the import if there is an error.
- Review the updated target system. Log off and then log in again with the updated access group, and then review the uploaded results. If they are satisfactory, lock the imported rulesets and versions.
- In a multinode system, recompile the libraries and delete the lookup list cache on each of the other nodes.
Remember to back up your existing database in your deployment. For out-of-place updates, include the data schema in your backup. For in-place updates, include the data and rules schemas in your backup. Also, consider cloning the Pega database. This process involves taking a full snapshot/backup of an existing instance and porting it over to a new database instance. This can save time and ensure everything has been copied/moved over. Please note that this is a general guide and the specific steps may vary depending on your specific application and database setup.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Preparing to package and move applications
Backing up your deployment database
A quick keyword search on PSC brings up the following:
https://support.pega.com/question/moving-one-database-server-another
https://support.pega.com/question/can-i-move-database-table-one-database-another-database