Question

4
Replies
1032
Views
Aqib Mushtaq (Aqib_Shah)
Societe Generale

Societe Generale
IN
Aqib_Shah Member since 2016 3 posts
Societe Generale
Posted: November 11, 2016
Last activity: November 15, 2016
Posted: 11 Nov 2016 2:52 EST
Last activity: 15 Nov 2016 6:29 EST
Closed

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!

DevOps Testing Applications Data Integration System Administration Installation and Deployment
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.