New setup of Pega 7.1.9 and move entire code base from Cloud environment.
Hi,
We have our current application code base in the cloud base. We are planning to setup our own in-premise server and move the code base. What will be the best approach?
1st Approach:
Take back of the PegaRules and PegaData schema from the existing cloud env. Execute the DDLs in the new in-premise database. Configure the application server and connect to the schema. Deploy the archives.
2nd Approach:
Create the new database schema. Do the rulebase loading. Configure the application server and connect to the schema and deploy the archive. Take RAPs for the application instance from the cloud and deploy the same.
Please suggest. Also, Would be great if you highlight the positives and the negatives of both the aproach.
Thanks!
Message was edited by: Marissa Rogers - added category
Pegasystems Inc.
AU
Hi Rajib,
Approach 1
Taking the completely database dumps of Rules and Data schema and importing into your DB servers and configuring the DB connections in your newly created Application server instances where the PRPC EAR's deployed would be an appropriate approach, so that you wont be missing any of the data from both the schema's.
Updated: 13 May 2016 5:02 EDT
Pegasystems
IN
Note that pr_sys_statusnodes table which has the state of the nodes of the cluster should not be cloned to a different environment.
PEG
PL
I would suggest second approach. You have flexibility to pick and choose what you want to bring to new environment. For approach one, you need to take care of few db tables which keeps node specific information.
Merkle
GB
Thanks for your input. One more query, We have PRPC 7.1.7 with DSM, NBAM, NBAA and tomcat as the application server instance. However, in the new in-premise setup, we are planning to install JBOSS as the application server. As per the documentation from Pega on PRPC 7.1.7. DSM is not supported with JBOSS. Are you aware of any hotfix for the same?
Updated: 13 May 2016 7:48 EDT
Pegasystems Inc.
AU
Could see that the DSM v7.1.7 is supported on JBOSS, refer to the installation doc on PDN for DSM PRPC v7.1.7 https://docs-previous.pega.com/decision-strategy-manager-installation-guide-717
Merkle
GB
yes Kadakol.....But we already have an application in the previous instance running on tomcat.......Hence we need to take that into account while on-premise migration
Pegasystems Inc.
AU
Ok, I believe you have the DSM v6.3.1 which you would like to migrate to new PRPC version and deploy onto JBOSS, I am afraid to mention for prior PRPC v7.1.x there are no hotfixes to support the deployment of DSM, NBAM on JBOSS.
Merkle
GB
So, if we are take the 1st approach where we do the exact schema to schema copy in the new environment from an existing environment which are the issue that could be anticipated? Please let me know your view