Question
Looking for best practices for Importing to production
I am looking for the best practice for Importing to production.
Starting point : First deployment to prod.
Approach 1:
1) In Dev Env. with prod level >= 2, create an app specific admin with level 5 for SchemaImport and ViewAndOptimizeSchema privelage.
2) Setup server with Pega rules in production.
3) Login with admin@pega.com.
4) Import the app RAP.
5) Submit the import with errors (Due to schema changes DDLs)
6) Login with app specific admin.
7) Re-import the RAP.
Use the app specific admin for further releases.
Approach 2:
1) Disable database/AutoDBSchemaChanges in all enviroments.
2) For each prod release, manually run all queries.
Approach 3:
1) Setup server with Pega rules in production.
2) Login with admin@pega.com.
3) Import the app RAP.
4) Take the failed queries and run them on DB seperately.
Approach 4:
1) Setup server with Pega rules in production with Prod level=2.
3) Login with admin@pega.com.
4) Import the app RAP.
5) Change DSS fieldtypechange/productionlevel= 5.
***Updated by moderator: Lochan to create new post from this comment; updated topic categories***
Let me know your thoughs!
Approach 1 Modified: I made some mistake in framing.
1) In Dev Env. with prod level <= 2, create an app specific admin with level 5 for SchemaImport and ViewAndOptimizeSchema privelage.
2) In Prod env, with prod level =5 ,Login with admin@pega.com.
3) Import the app RAP.
4) Submit the import with errors (Due to schema changes DDLs)
5) Login with app specific admin.
6) Re-import the RAP.
Use the app specific admin for further releases.
Hi Aqib,
It works fine. While you re-import the RAP using app specific admin, I feel you get an pop-up saying that RAP alreasy exists in the server.
Thanks,
Prudhvi
Hi Aqib,
I feel Approach 3 would be fine.
Approach 1: As you are doing in Dev env, are you going to change the pzproductionlevel for it.
Approach 2: Maintanence costs.
Approach 4: There is a chance of getting cache issues if you change the prod level. Also, you have to restart the server which is a maintanence cost again.
Thanks,
Prudhvi