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

 Pradyumna Harkar (PRADYUMNAH)
AGL

AGL
AU
PRADYUMNAH Member since 2012 5 posts
AGL
Posted: Jun 19, 2015
Last activity: Jul 18, 2017
Posted: 19 Jun 2015 3:18 EDT
Last activity: 18 Jul 2017 10:31 EDT
Closed
Solved

Does Pega 7.1.8 support both High Availability and MultiTenancy at the same time?


I have more questions associated with this

1. If we upgrade our system with Multitenancy
installation, do we need to enhance our schema ? What is difference b\w std.
and Multitenancy with respect to schema?

2. When we upgrade our system with standard
installation and after upgrade do we have any patch /plugin so that we can have
Multitenancy.?

Thanks in advance.

Pradyumna

***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
System Administration
Data Integration

Posted: 9 years ago
Posted: 19 Jun 2015 10:19 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Technical Support
Pegasystems Inc.
US

Hi Pradyumna,

The essential difference between standard and multitenant (MT) environments is the adding the database column pztenantid for many tables for MT. MT and High Availability (HA) are two separate concepts. I do not believe we currently support upgrade from standard to MT. To support HA, the critical requirement is the support of split schema (data and rules). I believe the support of MT+split schema is only available since 7.1.5 (not 100% sure). See https://collaborate.pega.com/question/deployment-guides for details regarding both MT and HA.

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