PRPC Deployment

PegaRULES Process Commander (PRPC) is a Java EE-compliant enterprise application that

requires only two supporting systems in your environment: A database system to store the rules and
work items used and generated by PRPC, and an application server that supports the Java EE
specification. The application server provides a run-time environment and other services, such as
database connections, Java Messaging Services (JMS) support, and connector and services
interfaces to other external systems.
Both application designers working on PRPC applications and users working with those
applications access PRPC through Web browser interfaces. Because of PRPC's standards-based
open architecture, you have maximum flexibility in the way you deploy and evolve your Pega
applications. They can run concurrently in a wide variety of operating system environments,
including Windows, Linux, Solaris, IBM Systems Z and AIX. In these environments, you can
choose among the most popular application servers and database systems: IBM WebSphere, Oracle
WebLogic, Apache Tomcat and JBoss application servers; Oracle, Microsoft SQL Server and IBM
DB2 UDB or z/OS databases. Process Commander supports the same features and development
environment in all these environments. In addition, Pega Cloud makes PRPC available as a Cloud
application for development, test and production. You may mix approaches with development and
test environments on Pega Cloud and then move production-ready applications to on-premise
hardware and software systems. Pega provides the tools and procedures to make your deployment
easy with Pega Cloud, or with on-premise solutions using any of these vendors. With this flexibility,
you have the deployment agility to respond to changes in your business needs or IT environment.
You are not locked-in to particular vendors or hardware, nor Pega Cloud versus on-premise
deployments. PRPC components can even be deployed across a heterogeneous (multi-vendor)
environment and combine a variety of deployment patterns, including distributed, clustered, batch,
mainframe, and embedded. You can move your developed applications to different database and
application server vendors, and even across operating systems without reworking your applications.
In these ways, you can start small, and expand your PRPC system as your applications evolve.

What is Deployment?
PegaRULES Process Commander requires only two pieces of supporting software in your
environment:
1. A database system to store the rules and work objects used and generated by PRPC.
2. An application server that supports the Java EE specification. The application server
provides a run-time environment and other services, such as database connections, Java
Messaging Services (JMS) support, and connector and services interfaces to other external
systems.

To set up a PRPC system, you first configure the application server and deploy the PRPC
applications to it. Then you create an empty database in your database system and load the initial
rules and classes PRPC needs to run into the database. To set up the database, you use either an
Installation and Upgrade Assistant wizard which leads you through the process interactively, or you
can script the process using a complete command-line interface provided by Pega. Pega Cloud
provides a Software-as-a-Service model (SaaS) to get up and started quickly as another deployment
option.
After deployment is complete, you use tools in PRPC to complete a few configuration steps to
ready PRPC for development. You can also use the Import wizard in PRPC to add Solution
Frameworks to your system.
When the software has been installed and configured, both developers working on PRPC
applications and end-users working with those applications access PRPC through Web browser
interfaces.
back to top

Key Features & Attributes of Deployment

Basic Installation
Installation of a basic PRPC development system is completed in three steps; Preparation, Rulebase
Setup, and Configuration.
1. Preparation
In this step you follow procedures in the PegaRULES Process Commander Installation Guide to
prepare your environment. You first make sure that your environment meets the requirements for
your PRPC release by reviewing the PRPC Platform Support Guide. You then create and configure
an empty database for PRPC to use. You can use SQL scripts provided by Pegasystems to create the
schema required by Process Commander in the database, or you can choose to have the Installation
and Upgrade Assistant create the schema when you run that tool. Finally, you configure your
application server to support the Process Commander applications and deploy the Process
Commander application (WAR or EAR), the online help application (prhelp.war), and System
Management Application (prsysmgmt.war).
2. Rulebase Setup
You use tools provided by Pega to install the initial set of rules and classes Process Commander
needs to run into the database. You can use either a command-line interface provided by Pega to
script this process, or you can use the Installation and Upgrade Assistant.
The Installation Assistant is a self-standing Java program that connects directly to the database you
created for Process Commander and automates database setup. The screens in the Assistant lead you
through the options and collect the information needed to set up your database.

The Assistant then optionally creates the Process Commander schema in the database instance you
provide and automatically sets up the database to support Process Commander.

3. PRPC Configuration
After finishing the Installation, you log into Process Commander to complete a few configuration
steps for the Developer Online Help and System Management applications, and create the initial
organization and application to begin development.

Installing Solution Frameworks

To accelerate your development you can extend your basic Process Commander installation with
Pega's Solution Frameworks, extensible starter kits for specific industries. Each framework is a set
of rules that includes a class structure, process flows, and database fields (properties) to support a
typical application for the targeted business and industry. You can then customize the application for

your specific use.

You can use an Import wizard in Process Commander to easily add the Frameworks package to
your basic Process Commander deployment.

Upgrading
Pega provides a straightforward process for upgrading your system to a newer version of Process
Commander. Procedures and tools are provided to allow you to upgrade in-place, preserving your
development and reducing disruption to your work. Pega provides SQL scripts to update your
Process Commander database schema, and, as with installation, you can use a command-line
interface or the Installation and Upgrade Assistant to automatically update the rules and classes in
the database.
After updating the Process Commander environment, you log into Process Commander to run an
Upgrade Wizard which modifies existing rules and applications to make them compatible with new
features in the upgraded Process Commander release.