Review the Platform Support Guide to select the hardware and software needed to support your Process Commander system.
Process Commander is a JavaEE (J2EE) application and requires two pieces of supporting software:
- A database system to store the rules and work objects used and generated by Process Commander.
- An application server that supports the J2EE specification. You deploy the Process Commander software components into the application server. 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 Process Commander system, you deploy the Process Commander software components into the application server, and configure the application server environment to allow Process Commander to connect to the database and to other systems as needed. When the software has been installed and configured, both developers working on Process Commander applications and end-users working with those applications access Process Commander through Web browser interfaces.
File topics present the functional areas of installation and deployment, to help guide you through the process of a successful installation. The deployment steps listed below allow you to view these topics, based upon the where you are in the installation process.
Process Commander is a J2EE-compliant enterprise application. It can be deployed on a wide range of platforms (operating system, Java runtime environment, application server, relational database, and client Web browsers) which support the J2EE and Java standards. However, whenever possible you should select platform components from those listed in the Platform Support Guide. This guide lists the platforms that are most completely tested and most frequently used with Process Commander. The Platform Support Guide also documents any special requirements or known issues with particular vendors or software versions.
If you use platform components not listed in the guide, be sure to consult with your Pegasystems representative or Global Customer Support about your selection.
At a minimum, you must provide appropriate hardware and network connectivity to support:
- a relational database installation (such as Oracle, IBM DB2 or Microsoft SQL Server,)
- an application server installation (such as Oracle Application Server, WebSphere, or WebLogic,), and
- Web browser clients to access the Process Commander deployment.
The database and application server platforms may be either UNIX or Windows systems. However, a Windows system is required for the Pegasystems developer and end-user clients and for some of the Pegasystems monitoring tools, specifically, PegaRULES® Process AnalyzerT, Process SimulatorT, and Autonomic Event ServicesT. Your planning for the initial Process Commander system should include at least one Windows platform.
Platform preparation for your installation and deployment can be summarized in the five quick steps below.
- Take advantage of Pegasystems' training courses for your Process Commander administration support and development team.
- Review the Process Commander installation and configuration documentation.
- Obtain delivery dates from each team that will provide platform preparation support.
- Contact your Pegasystems Practice Lead or Engagement Lead to review your deployment plan.
- Prepare your database and application servers as specified in the Pegasystems checklists and documentation to support Process Commander.
Download and run the Installation Preverification Utility WebEnvVerify.ZIP (contains WAR file, 17KB) to verify that your deployment environment is suitable for a successful Process Commander installation. This utility works with all versions (V4.2, V5.1, V5.2, and V5.3) and has been verified against WebSphere 6.0 and 6.1, WebLogic 8.1.5 and 9.2, and Tomcat 5.5.20 using Java SDK 1.5.0_06. To get started, follow the steps below:
- Download the ZIP archive and extract the WAR file.
- Deploy the War file to your application server environment. For Tomcat, you can simply drop this file into the
webappsdirectory, and it will automatically deploy and install.
- Access http://<servername>:<port>/prWebEnvVerify and review the output.
- Cross reference against the Platform Support Guide for the release you are installing to ensure that you have a valid combination.
If the War file fails to deploy or run, a problem exists with the application server environment that should be resolved prior to proceeding with the Process Commander installation.
Successful installation of Process Commander requires proper platform preparation based upon your choice of supported platform. Before beginning the Installation Process, review the recommendations in the early steps of this series. In particular, be sure to review Planning Your First Process Commander Deployment to get an overview of the installation from an operational perspective.
To complete the installation, follow the step-by-step instructions in the Installation Guide for your platform. Links to Installation Guides for each release of Process Commander are provided on the following pages:
- V6 Deployment guides — Installation Guides for each Process Commander 6.x Version.
- V5 Deployment guides — Installation Guides for each Process Commander 5.x Version.
A separate Installation Guide is provided for each of the supported application servers. Each installation guide covers all of the supported database types.
Installation can be summarized in the following steps:
- Prepare Your Environment
Make sure that your environment meets the requirements for your Process Commander release in terms of the hardware platform, operating system, JVM, JDBC driver, application server, and database server.
Review the current Platform Support Guide. This document lists the recommended software components needed to support Process Commander, and any special requirements or known issues with particular vendors or versions.
- Prepare Your Database
Create and configure a blank database for Process Commander to use. You use SQL scripts provided by Pegasystems to create the schema required by Process Commander in the database. For Version 6.x installations you can instead choose to have the Installation and Upgrade Assistant create the schema for you when you run that tool.
- Prepare Your Application Server
Configure your application server to support the Process Commander application, including:
- Configure the right database driver for your database
- Configure the Process Commander data source
- Configure other Application Server Java EE settings required by Process Commander
- Deploy the Process Commander application (WAR or EAR)
- Deploy the online help application (prhelp.war) and System Management Application (prsysmgmt.war)
- Load the Process Commander Rulebase into the database
Run the Process Commander utility to load the initial set of Process Commanders rules and code into the database you prepared
- In Version 5.x installations, you deploy and run the Database Utilities application (prdbutil.war).
- In Version 6.x installation, you run a separate utility the Installation and Upgrade Assistant (PRPC_Setup.jar). This utility does not need to be deployed to the application server and can be run from any computer that can connect to the Process Commander database.
- Configure Process Commander
Log in to Process Commander and complete a few final setup steps in the Process Commander interface.
When your installation is complete, contact Global Customer Support (GCS) to register your new system. Registering your platform details saves time later on routine support calls.
Step 4: PegaRULES Process Commander Setup Operations
This topic discusses how to configure a correctly installed Process Commander application. Successful implementation of Process Commander requires proper platform preparation based upon your choice of supported platform and a verified software installation and deployment. For more detail on all installation and deployment steps, refer to Planning Your First Process Commander Deployment, or select a specific installation step in the graphic above.
Administration and Security V5.3 — This document describes how to perform the initial startup, setup, and day-to-day administration of your Process Commander systems. The chapters in this document do not describe every field on the forms used in the procedures that are presented. For help or information about all the fields on every Process Commander form, see the Application Developer help system. If your role involves managing part or all of a Process Commander system, you need to read this document.