PEGA Database management

PEGA Platform is a platform for management of business processes (BPM), and management of customer relationships (CRM). PEGA helps companies and agencies build business apps quickly that deliver the results and end-to – end customer experiences they need.
This guide assumes you have a basic familiarity with the command line for Cloud Shell, Cloud SQL, Compute Engine and Linux.
The PEGA Platform is an enterprise application that complies with Java EE and consists of two layers.
Application servers host the application on the PEGA Platform and provide interconnectivity to other systems.
PEGA database servers
Database servers store the rules, data, and work objects which the PEGA Platform uses and generates. Users and developers of applications usually access the PEGA Platform through a web browser. Applications may also expose HTTP-based services, such as SOAP or REST, in a headless environment for administration or processing automation.
A reference architecture for the implementation on Google Cloud of a scalable PEGA framework which is suitable for a development environment. Your infrastructure and security needs differ so the configurations mentioned in this tutorial can be modified accordingly. A GitHub repository that contains the scripts you are using to install PEGA and other necessary components in the tutorial.
Configure PEGA platform to support Cloud Load Balancing
At the end of this tutorial, you’ll have a PEGA cluster with a single Cloud SQL for PostgreSQL instance and three clustered Compute Engine application virtual machines ( VMs) fronted by Cloud Load Balancing for web traffic. All SQL connections are made by using Cloud SQL Proxy. This tutorial uses the us-central1 region for the PEGA implementation.
The following products are used in this article. If you use different versions of these products, you might need to make adjustments to the scripts and commands that are referenced in this tutorial and in the repositories.
• PEGA Platform 7.4
• Postgre SQL 9.6
• Red Hat Enterprise Linux 7
• Apache Tomcat 8.5
Establishment of service account in PEGA PLatform
You need to build a Google Cloud service account to allow PEGA to access the tools for the tutorial. The service account will need to have the following roles:
• The.client cloudsql. Used for connecting via Cloud SQL Proxy to the Cloud SQL database.
• Viewer.objectStorage. Used when downloading Cloud Storage files.
• To log.logWriter. Used to log in to Cloud Logging.
• Follow.metricWriter. Used to write in Cloud Computing monitoring data.
• Errorwriting.writer. Used to write on Cloud Logging error info.
To build an account with the service in PEGA PLatform
Create a service account in Cloud Shell named PEGA-app.
Gcloud iam service accounts create PEGA-app —display-name “PEGA-application”
Add the service account functions to:
Gcloud projects add-iam binding policy ${DEVSHELL PROJECT ID} \
—member = account service: PEGA-app@${DEVSHELL PROJECT ID}.iam.gserviceaccount.com \
—role = roles / client cloudsql.
Gcloud projects add-iam binding policy ${DEVSHELL PROJECT ID} \
—member = account service: PEGA-app@${DEVSHELL PROJECT ID}.iam.gserviceaccount.com \
—role = roles / display.objectViewer
Gcloud projects add-iam binding policy ${DEVSHELL PROJECT ID} \
—member = account service: PEGA-app@${DEVSHELL PROJECT ID}.iam.gserviceaccount.com \
—role = functions / logging.logWriter
Gcloud projects add-iam binding policy ${DEVSHELL PROJECT ID} \
—member = account service: PEGA-app@${DEVSHELL PROJECT ID}.iam.gserviceaccount.com \
—role = roles /.metricWriter monitoring
Gcloud projects add-iam binding policy ${DEVSHELL PROJECT ID} \
—member = account service: PEGA-app@${DEVSHELL PROJECT ID}.iam.gserviceaccount.com \
—role = roles.writer / error reporting.
Establishing SQL in the Cloud in PEGA PLatform
The next step is establishing a database. You’ll use a PostgreSQL database on Cloud SQL for this tutorial.
Create Cloud SQL Instance in Cloud Shell:
Instances generating the ${CLOUD SQL INSTANCE NAME} \
— POSTGRES 9 6 —cpu=2 —region=${REGION} \
—memory=8 GB —auto-storage —backup-start-time=00:00 \
—TypeDisponibility = regional
You use an instance in this tutorial that includes two vCPUs and 8 GB of RAM. That may take a couple of minutes to complete.
Using a dual-user configuration create PEGA runtime users for your installation. In a dual-user configuration, full database privileges are granted to an Admin user, and a smaller subset is granted to a Base user.
Users of cloud sql build PEGAADMIN\
—instance=${CLOUD SQL NAME} \
—Name=${ADMIN USER PW}
Users of cloud sql create PEGABASE\
—instance=${CLOUD SQL NAME} \
—Name=${BASE USER PW}
Establishing a lock for Cloud Storage in PEGA PLatform
You need to build a bucket of Cloud Storage that houses the PEGA installation media and other scripts used in this tutorial.
Build the Bucket in Cloud Shell.
Regional -l${REGION} gs:/${GCS BUCKET} gsutil mb –c
The PEGA 7.4 installation zip file can be uploaded to the new storage bucket using the Cloud Console. Upload the file into your new bucket root.
The installation scripts are uploaded to a Cloud Storage seal.
You are now downloading your Cloud Shell instance to the GitHub source repository which is part of this solution. The server can then be transferred to a Cloud Storage container.
In Cloud Shell, download the zip file from the GitHub repository that contains the installation scripts:
Wget: https:/github.com/GoogleCloudPlatform/solutions-compute-cloudsql-PEGA7/archive/master.zip
Database PEGARULES – Definition
The database that contains the rules is known as the PEGARULES database — all instances of concrete classes derived from the Rule-base system. This database is also known as the rulebase occasionally, but it does contain more than rules.
Objects mapped to database PEGARULES are classified as internal groups. Concrete classes that correspond to outside database rows are known as external classes.
Contrary to the persistent instances of rules and other objects in the PEGARULES database, instances are temporary on a user clipboard. The system deletes the user’s clipboard when a user logs off.
If the program saves an instance from the clipboard into the PEGARULES database, the saved copy will stay after logging off from the user who created it, and will be available to other users. So the PEGARULES database contains Process Commander’s persistent objects.
Process Commander developers working with database administrators determine which classes of objects are stored into which database tables through the database table and data base instances.
While the PEGARULES database is sometimes referred to as a rulebase, don’t be confused with the word rulebase — it’s a concrete set of rules and other objects in a relational database — with the rule-base class, an abstract entity without instances.
To unzip the file’s contents
Unzip with master.zip
Scripts add to the bucket:
Gsutil cp -rP solutions-compute-cloudsql-PEGA7-master / scripts
Putting in the PEGA platform Rulebase
The PEGA Rulebase stores rules, pieces of service, and other data PEGA uses for its operations. You set up a temporary Compute Engine VM to run the PEGA Setup scripts to install the PEGA Rulebase. You can use a startup script that has preconfigured settings so that installation commands don’t have to be executed manually. You use a startup script in this step but you can also manually perform the installation.
Installation script PEGA Rulebase performs the following actions.
• Runs changes to framework.
• Installs agents for cloud logging, and cloud monitoring.
• Packages needed, such as PostgreSQL client and Java Development Kit (JDK), are installed.
• Cloud SQL Proxy installs and configures to connect to the Cloud SQL case.
• The PEGA installation file from the Cloud Storage bucket is downloaded and unzipped.
• Populates the file setupDatabase.properties that contains the required variables for the environment.
• Download the JDBC driver to PostgreSQL.
• Creates a database of PEGA schemas.
• Runs the script for installation on PEGA Rulebase.
• PEGA Rulebase Install:
• Build the VM in Cloud Shell which includes the startup script for PEGA Rulebase installation:
Instances of cloud computing build PEGA-db installer \
—Normal machine-type = n1-4\
—service-account = PEGA-app@$}.iam.gserviceaccount.com \
—scopes = https:/www.googleapis.com / auth / cloud \
— Rhel-7 family portrait \
—Project-image = rhel-cloud \
—Disk Size=35 GB \
—metadata = start-script-url = gs:/${GCS BUCKET}/scripts / PEGA / db-startup.sh, SQL INSTANCE ID=${CLOUD SQL INSTANCE NAME},GCS BUCKET=${GCS BUCKET},PEGA INSTALL FILENAME=${PEGA INSTALLL FILENAME},ADMIN USER PW=${ADMIN USER PW},BASE USER PW=$${BA
Conclusion
I hope you reach to a conclusion about PEGA platform database management. You can learn more through PEGA online training.
Please go through this links Pega CSSA, CPBA, CLSA
Contact Information:
USA: +1 7327039066
INDIA: +91 8885448788, 9550102466
Email: info@onlineitguru.com

Comments are closed