Unified Architecture

Pega/PRPC is a popular rules engine and BPM tool from Pega systems that is gaining good
market share among large corporations.
Architects and developers build the Pega/PRPC instance while administrators and even select
business analysts have the option of changing workflow rules during runtime. Infact, their motto
itself is "Build for change".
The goal is to "eliminate software coding" and "automate manual work" to the minimum and
build complex systems at the enterprise level with features right out-of-the-box. That's how it
works in the utopian world. But in the real world, you need good developer support.
So the lesser the code, the closer you are to the goal of a true BPM tool. Software coding might
be reduced drastically. But you still need people with a development background using inputs
from Business Analysts to make changes or add functionality.
Pega/PRPC is pretty expensive so they primarily target any corporation that can afford such a
luxury.
Pega 7 provides a unified, model-based application development platform for building business applications.
Traditional application development tools focus on creating individual business applications that must then be integrated
with each other.
These business applications may be developed and maintained by separate groups that use different application
development languages, tools, methods, and repositories. Examples include a visual design environment to model
processes, a business rules engine to provide business logic, an integrated development environment to build integrations,
an analytics platform to execute predictive models, or a document management system to manage case data.
These business applications are integrated, but they are not unified. As a result, sharing and reusing artifacts when
building business applications is difficult.
Unified architecture
The Pega 7 platform is unified. This means that all the functionality needed for business applications is configured using a
consistent set of artifacts that are defined and stored together in a single database repository.
Each business application built on top of the Pega 7 platform uses a common set of tools, a common vocabulary, and a
consistent model to communicate, implement, and validate requirements.
Business processes and policies, integrations with external systems, mobile interfaces, business performance monitoring
and reporting, or adaptive analytics are all defined using a consistent, model-based application development approach.
This makes sharing and reusing artifacts easier when building business applications.
What is PRPC?
ranadheer reddy d 10:34 AM BPM, BRE, Pega, prpc
PRPC (PegaRULES Process Commander) is a software product created, licensed,

and marketed by Pegasystems Inc (PEGA). PRPC is the core component of
Pegasystems's "SmartBPM" suit of BPM (Business Process Management) solutions.
Pega
PegaRULES Process Commander comes essentially as two discreet entities,
PegaRULES : Core Java-based/Object-Oriented Rules Engine.

Process Commander : Layers of pre-configured rules that provide a solid
foundation on which to perform development and customization.
Incorporating both of the following components, PRPC addresses simple to complex
business challenges:
BPM
o Procedural processing through a user-interactive BPM / BPMS(BPM
Suite) tool.
BRE
o Declarative "On-Change" processing through an event-driven tool.
The advantages that PRPC offers from a Business perspective are as follows:
Software platform enabling businesses the opportunity to migrate all their
disparate, diverse, and often complex business rules onto one platform.
Ability to streamline, automate, and document business processes.
Consolidate multi-stream processes into one system.
Through service connectors (such as SOAP, MQ, active file listening) connect
to existing enterprise applications.
Pass data between systems and have such information parsed, extracted,
and interpreted.
The advantages that PRPC offers from a Developer perspective are as follows:
Development can be achieved in small iterative-based parts
Development is contained within heavily graphic-driven 'Rule Forms' that are
version and ruleset controlled.
All run-time Java code is compiled and executed by the system at run-time.
Changes or new configurations can be tested in real-time, even on production
systems without affecting other users or processes.
Ultimately PRPC is a software platform that allows businesses the opportunity to
migrate all their disparate, diverse and often complex business rules, practices and
processes into one platform. The platform offers the possibility of streamlining,
automating and documenting business processes in a way that can truly allow
consolidation of multi-stream processing into one system. Through PRPC's myriad
service connection capabilities (such as SOAP, MQ, active file listening on directories
etc...), it is possible to connect already existing enterprise applications to PRPC and
pass to the platform messages, data or information and have such information
parsed, extracted and interpreted for use either within user driven processes, or
even system-driven events.
So, what does that really mean?
Think of PRPC as a box of sophisticated Lego. You are provided with a number of
building blocks that enable you to quickly and easily build an application to suite the
requirements of your business. The Lego blocks (or Rules as Pegasystems calls
them) represent different parts of your application. There are rules for screens,
decisions, correspondence, interfacing to external systems, etc. You can take these
rules and put them together to design and build your solution.
This also means that it is very simple and easy to change your solution to suit the
ever changing requirements of the business - you simply change the lego bricks
around!!
"Pega is a Business Process Management tool. It is developed on Java and uses OOP and
java concepts. And the big advantage is we don't have to build the system from the
scratch like any conventional programming. It is becoming popular because of that,
though most conventional programmers would disagree. And also because of it is agile
way, Flexibility,and being extensible.
Pega
PEGA is a platform which provided a systematic approach to build and deploy process-
oriented and rule based solution and applications. Business Process Management,
Customer relationship management, Decision management and case management
solutions are some of the examples where process and rules are integral part of
application development. What PEGA provides to a developer is a Designer studio
which acts as an Integrated Development Environment (IDE) to build applications. The
best part is this Designer studio is web based so a developer can work and create
solutions from anywhere in the world.
Technically PEGA is not a language or database or operating system. What PEGA

provides us is a framework which is process driven; everything that we do in traditional
programming such as designing user interfaces, writing business logic, applications
logic, creating physical and logical mode of databases etc. we do the same thing in
PEGA. The difference lies between PEGA and traditional programming is that in PEGA
to build or develop anything (UI, data access logics, validation rules etc) there are
processes and gadgets that we have to use.
In the heart of PEGA is PRPC server (PegaRULES Process Commander) which

provides the platform and interfaces to business analyst, system analyst and developers
to design and build applications in PEGA. The main focus in PEGA is on automation of
works and program code.
PEGA is a BPM tool. BPM stands for Business Process Management. The current
version of PRPC server is v6.2 sp2
Honestly the purpose of the technology isn't something I want to be digging into for
free... but you can watch lots of videos on the subject here: BPM Professor
Comparison of Pegasystems Pega 7 versus Java

ranadheer reddy d 8:58 AM comparision, Pega
The PEGA 7 Platform provides a single, unified platform with everything you need to build or modify enterprise
applications.
Business and IT stakeholders work together, using visual models to capture business requirements. With no coding
required, Pega 7 automatically generates the application and its documentation.
This detailed independent study by Capgemini finds Pega 7 is 6.4 times faster than Java Enterprise Edition (Java EE) to develop
robust business applications. The study looks at six key areas where the high productivity of Pega technology drives significant
competitive advantage:
Reduction in the time to market for new or enhanced products and services
Acceleration in the readiness of multi-channel customer engagement
Improvement in the ability and time to respond to customer-driven demands, new market opportunities, or competitor
actions in the market
Flexibility to innovate by way of more, faster, and less costly experimentation
Heightened process accuracy and reliability and lower defect occurrence gained from extensive re-usability
Greater resource optimization of key personnel derived from business process and application development and
deployment productivity improvements and cycle time reductions

Unified Architecture

Uploaded by

Copyright:

Available Formats

Unified Architecture

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unified Architecture

Uploaded by

Copyright:

Available Formats

Pega/PRPC is a popular rules engine and BPM tool from Pega systems that is gaining good

market share among large corporations.

PRPC (PegaRULES Process Commander) is a software product created, licensed,

PegaRULES Process Commander comes essentially as two discreet entities,

PegaRULES : Core Java-based/Object-Oriented Rules Engine.

So, what does that really mean?

Technically PEGA is not a language or database or operating system. What PEGA

In the heart of PEGA is PRPC server (PegaRULES Process Commander) which

Comparison of Pegasystems Pega 7 versus Java

Acceleration in the readiness of multi-channel customer engagement

Flexibility to innovate by way of more, faster, and less costly experimentation

You might also like