Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Labanyendu Pattnaik (LabanyenduP) Morgan Stanley
Morgan Stanley
US
LabanyenduP Member since 2013 1 post
Morgan Stanley
Posted: Oct 24, 2018
Last activity: Nov 8, 2018
Posted: 24 Oct 2018 18:54 EDT
Last activity: 8 Nov 2018 15:53 EST
Closed

Schema Name Change for App Isolation

We are using Pega7.1.8 on Apache/tomcat server, DB2 9.x with spilt schema DB as PEGARULES and PEGADATA. Now we want to move to App specific schema Pair (ex: PEGARULES_APP1 and PEGADATA_APP1) for Application Isolation while still keeping them on the same DB.

With information gathered from other threads, I understand updating context.xml, DB triggers, StroredProcs with the new schema name should do the trick.

Does anyone have any experience with this? If so,

  • Is the scope of change limited context.xml, DB triggers, StroredProcs?
  • If this has to be done on Pega 8.1, is it any different?
  • Any other known issues?

To see attachments, please log in.
Pega Platform Installation and Deployment

Posted: 5 years ago
Posted: 8 Nov 2018 15:53 EST
Vipin Kumar (DHEER_GCS) PEGA Director, Technical Support, Cloud Service
Pegasystems Inc.
US

I'd suggest doing a fresh install with new schema names and them importing the application1 into schemas for App1. Then maintain application with schema convention going forward.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice