DAY 3

Application Structure
Agenda
Day 3

• Application Structure
• Enterprise Class Structure – ECS
• Classes – Concrete & Abstract Class
• Class Group & Work pool
• Organization Structure
• Framework & Implementation Classes
• Databases in PEGA

2
 UseCase

Consider Amazon is onboarding candidates to their company to hire developers with skills JAVA and PEGA.
Our application structure needs to reuse the rules such as logo, amazon account registration form.

We will create a framework application that holds reusable rules logo, registration form.
We can reuse this already created rules from framework into the implementation level application.

Similarly it wants to USEthe following layer rules.

1. Reuse organization level rules such as logo, registration form, login form.
2. Generate division level rules i.e From India.
3. Create unit level rules such as HR, candidate dashboard, etc.

Generate division layer and unit layer for the implementation layer application.
Organization structure to be set as AMAZON-INDIA-HR

3
 Application Structure

Application can be built on another application

ie.On Framework.
Framework application is primarily intended to be
developed for reusability within implementation level
applications.

Application creation wizard supports both these options.

1.Framework application class structure format as
ORG-FW-DIV-UNIT.
2. Select application structure as “Framework application”.

4
 Framework & Implementation
1.Login To new framework application and start creating reusable
rules under a casetype.
2.From new application creation wizard, select your framework.
3.Select application structure to “Implementation”
4.Generate division and unit layer to class structure.
5. Add rulesets to hierarchy if needed and select framework class.

5
Class Structure

6
Enterprise Class Structure

There are 5 layers of enterprise class structure.

1. Framework – to support reusability
2. Implementation – business rules for implementation.
3. Organization – organization wide rules such as logo, buttons, skin ettc
4. Division – division wide rules such as currency symbol, states, cities etc
5. Unit – unit wide rule such as HR, sales, services etc.

The class structure is usually of format ORG-DIV-UNIT-IMPLEMENTATION for

implementation applications.

The class structure is usually of format ORG-FW-DIV-UNIT-IMPLEMENTATION for

Framework applications.

7
Classes – Types of Classes

There are 3 types of classes in PEGA.

1. Concrete class
2. Abstract class
3. @base class

Concrete class – Class suffix doesnot end with -. Contains instances that can be
persisted to database.
Ex: AMAZON-IND-SALES-Work-CandidateHire
Abstract class – Class suffix ends with -. Instances cannot be saved to database.
@base class – contains topmost class rules such as PEGA functions, library etc.

8
Class Groups

Class Group is a group of similar/related concrete classes usually Work- class under
common relational database table.

A Concrete class should always belongs to or doesnot belongs to class group.

When belongs should inherit from Work- i.e Amazon-India-HR-Work-Onboarding etc
When doesnot belong to class group doesn’t need to inherit from work- class

Work pools are also similar to classgroup but they donot need to be similar/related
work object concrete classes.

Work types refer to broader definition of work to be resolved.

Work items refer to items before execution of case type.
Work objects refer to executed case types that generates work object such as C-12, C-
13 etc also called as Work object ID, case ID or pyID.

9
 Class Inheritance

PEGA as similar to parent/child classes also inherit the concept of inheritance from java.
There are 2 types of class inheritance concepts in PEGA.
1. Direct Inheritance
2. Pattern Inheritance

Direct Inheritance – Rule resolution determines the parent class of a child class from its class rule form.
Pattern Inheritance – Rule resolution determine the parent class of child class based on class structure
naming convention.

For. AMAZON-INDIA-HR . Here INDIA class (AMAZON-INDIA) is parent of HR Class (AMAZON-INDIA-

HR) Class and similar AMAZON class is parent of INDIA class based on class naming.

Pattern inheritance takes default priority.

Work-Cover- is default directed parent of a class.

10
Organization Structure

Organization structure of an operator can be updated from operator’s profile.

Work groups define the group of work users who can be part of eligible
Users to receive any routed assignments.

Format of work group is

[email protected]

11
Databases

12
 Databases in PEGA
PEGA Maintains 2 types of databases internally inorder to store rules.
1. PEGADATA
2. PEGARULES

PEGADATA database primarily stored all application rules created by the operator/generated by
application.

PEGARULES database primarily stores PEGA system rules such

as functions, library rules etc.

All classes are internally mapped to a database table in PEGA Data database.
As instances are created under the class, they are automatically saved to internal database.

Realtime projects use external databases from major providers such as Oracle, MySQL, etc.

We have database class mapping wizard to easily connect to an external database.

13
Hosting

PEGA application is deployed on Apache Tomcat app server (for personal edition) and IBM web
server (for cloud editions) and POSTGRESQL as DB Server to host and store rules.

The configurations related to PEGA Application can be found in PRCONFIG.XML File

Web.XML Contains the Servlett configuration
Tomcat > Webapps> PRWEB > webinf > class > prconfig.xml

In a WAR deployment, the prconfig.xml file is located under the contextroot directory in either the
\WEB-INF\classes subdirectory or the \APP-INF\classes subdirectory. For example for a WAR
deployment on Tomcat, this location is:

<app-server-install-root>\webapps\<contextroot>\WEB-INF\classes\

Example:

D:\apache-tomcat-5.5.16\webapps\prdbutil\WEB-INF\classes\prconfig.xml.

Tomcat generates .WAR Deployment while using IBM Websphere generates .EAR Deployment.

All the files such as images, documents, etc uploaded to PEGA application can be found under
WEBWB Folder.

The deployment archive holds the .JAR Application file to support deployment.

14
DSS – Dynamic system
settings

15
 Dynamic System Settings

PEGA application is usually hosted on multiple nodes (servers) inorder to improve load performance.
Also called as load balancing. Now PRCONFIG.XML is specific to node.

It needs to manually reconfigured for other nodes. Also its not possible to easily customize it.

Dynamic system settings overrides this restriction as its same for all the nodes. It can be easily
configured from the PEGA Application itself. They are not present in locked rulesets

PRCONFIG.XML changes can be overridden by DSS. Navigate to Sysadmin > DSS.

2 types of dynamic system settings.

1. Application server settings – settings related to system configuration.
2. Application data settings - settings related to application configuration

Use getsystemsetting function to get ASS DSS and getdatasetting function to get ADS
DSS values retrived.

16