Pega Community | Training & Resources for Pega Developers ......JVM,JDBCDriver,ApplicationServer,DatabaseServer,PRPC,andtheirrespectivesettings. 1.ReviewthecurrentPlatformSupportGuide,whichisavailableonthePegaDeveloper

Process Commander

Installation Guide

Version: 6.2 SP2

Database: DB2

Application Server: WebLogic

© Copyright 2012Pegasystems Inc., Cambridge, MA

All rights reserved.

This document describes products and services of Pegasystems Inc. It may contain trade secrets andproprietary information. The document and product are protected by copyright and distributed underlicenses restricting their use, copying distribution, or transmittal in any form without prior writtenauthorization of Pegasystems Inc.

This document is current as of the date of publication only. Changes in the document may be made fromtime to time at the discretion of Pegasystems. This document remains the property of Pegasystems andmust be returned to it upon request. This document does not imply any commitment to offer or deliverthe products or services described.

This document may include references to Pegasystems product features that have not been licensed byyour company. If you have questions about whether a particular capability is included in yourinstallation, please consult your Pegasystems service consultant.

For Pegasystems trademarks and registered trademarks, all rights reserved. Other brand or productnames are trademarks of their respective holders.

Although Pegasystems Inc. strives for accuracy in its publications, any publication may containinaccuracies or typographical errors. This document or Help System could contain technical inaccuraciesor typographical errors. Changes are periodically added to the information herein. Pegasystems Inc.may make improvements and/or changes in the information described herein at any time.

This document is the property of:Pegasystems Inc.101 Main StreetCambridge, MA 02142-1590

Phone: (617) 374-9600Fax: (617) 374-9620

www.pega.com

Document:Process Commander Installation GuideSoftware Version: 6.2 SP2

Updated: Wednesday, March 14, 2012

i

Contents

Introduction 1

Check the Pega Developer Network for the Latest Information 1

Pegasystems Documentation 1

Deployment information and updates 1

Pegasystems Training 1

Overview of the Installation Procedure 1

1. Preparation Phase 2

2. Rulebase Setup Phase 3

3. PRPC Configuration Phase 3

Notes for Users of Earlier Process Commander Versions 3

Optional: Move System Settings from Configuration Files to Database 4

Step1. Environment Considerations 5

Prerequisites 5

Process Commander Deployment Architecture 5

Process Commander Core Component Versions 6

Supported Process Commander Platforms 7

Step 2. Database Preparation - 8

Database Prerequisites 8

Create the Process Commander Database 8

Create Database Users 9

Creating Base and Admin Database Users 9

How Process Commander Uses the two Database Accounts 10

Create the Schema in Process Commander Database 10

Using a SQL Script to Create the Schema 11

ii

Next Steps 11

Step 3: Application Server Preparation 12

Verify the Java Environment 12

Configure Support for the Process Commander Database 12

Create a WebLogic Domain 13

Configure the WebLogic Environment 13

Set the JVM Memory Parameters 13

Set an Explicit Temporary Directory 14

Enable AWT to support PRPC Graphical Reports 15

Put the JDBC Driver in the WebLogic classpath 15

Save and close setDomainEnv 15

Next Steps 15

Deploy Process Commander Applications 16

Open the WebLogic Administration Console 16

Enable DNS Lookup 17

Create JDBC Resources 19

Configure JMS Resources for an EAR deployment 26

Create a Topic and Subdeployment 35

Deploy the Process Commander Core Application 38

Assigning the PegaDiagnosticUser Role to your System Management Application Users 52

Next Steps 53

Steps 4 to 9 - Rulebase Setup 54

Install the Process Commander Schema and Rules in the Database 54

Move the Process Commander Software Distribution to Your Computer 54

Update Java 6 JDK to JAX-WS API 2.2.5 55

iii

Process Commander Version 6.2 SP2

Rulebase Setup Using the Installation and Upgrade Assistant 55

Step 10 - Final Settings in Process Commander 71

Start and Login to Process Commander 71

Configure Process Commander 72

Enable Developer Help and the System Management Application 73

Optionally Set Search Index Host Node Settings 74

Create an Organization 76

Change the password for [email protected] 76

Install Solution Frameworks 77

iv

IntroductionThis document describes how to install a new instance of PegaRULES Process Commander 6.2 SP2.Upgrading an existing Process Commander installation is described in other documents:

To upgrade a Process Commander 4.2 system to 6.2 SP2, your current system must first be at4.2 SP6. If your current system is earlier than 4.2 SP6, see the Upgrade Guide for 4.2 SP6 forinstructions on moving to SP6.

To upgrade from 4.2 SP6 to 6.2 SP2, first upgrade to V5 (see the manual Upgrade Guide, V4.2SP6 to V5) and then upgrade to 6.2 SP2.

For information about upgrading any existing Process Commander 5 installation to 6.2 SP2 seethe Process Commander Upgrade Guide 6.2 SP2, released with Process Commander 6.2 SP2.

These documents and any updates to existing Process Commander documentation are available on thePega Developer Network (pdn.pega.com).

Check the Pega Developer Network for the Latest InformationBefore beginning your installation procedure, check the Pega Developer Network (PDN), located athttp://pdn.pega.com, for the latest information. The installation guides are updated whenever newinformation becomes available. Be sure to check for the latest version.

Pegasystems Documentation

The latest Process Commander documentation, including Installation, Upgrade, and Platform Supportguides is available on the Documentation page of the Pega Developer Network.

Visit http://pdn.pega.com and select Guides -> Process Commander V6 Deployment.

Deployment information and updates

Check the Deployment page on the Pega Developer Network for information, updates, and platformbulletins on deploying Process Commander including links to the latest Knowledge Base articles.

Visit http://pdn.pega.com and select Browse -> Deployment -> About This Topic.

Pegasystems Training

A range of Pegasystems course offerings are available to increase the effectiveness of your deploymentand development team members. For more information, visithttp://www.pega.com/Services/EducationalServices.

Overview of the Installation ProcedureThe following outline details the steps in the 6.2 SP2 installation process:

1

Introduction

Preparation Phase

Step 1 – Environment Considerations

Step 2 – Database Preparation

Step 3 – Application Server Preparation

Rulebase Setup Phase

Step 4 - License Agreement

Step 5 - Type of Setup

Step 6 - Database Configuration

Step 7 - Database Connection

Step 8 - System Name and Production Level

Step 9 - Rulebase Loading

PRPC Configuration Phase Step 10 – Final Settings in PRPC

1. Preparation Phase

You complete the Preparation Phase following the procedures in this guide.

Step 1: Environment Considerations

Make sure that your environment meets the requirements for PRPC 6.2 SP2 in terms of: Hardware, OS,JVM, JDBC Driver, Application Server, Database Server, PRPC, and their respective settings.

1. Review the current Platform Support Guide, which is available on the Pega DeveloperNetwork (PDN) or from your Pega account executive. This document lists the recommendedsoftware components needed to support Process Commander, and any special requirementsor known issues with particular vendors or versions.

2. Review your site’s deployment requirements with your IT representatives.

3. Consult with your Pegasystems representative about your installation plans. Pegasystems’prior experience with various platforms and deployment architectures can help yourinstallation go smoothly.

Step 2: Database Preparation

Create and configure an empty database for Process Commander to use. You can use SQL scriptsprovided by Pegasystems to create the schema required by Process Commander in the database, or youcan choose to have the Installation and Upgrade Assistant create the schema when you run that tool.

You provide connection information for this database to the Installation and Upgrade Assistant used inthe Rulebase Setup Phase and to specify the datasource in your application server. The connectioninformation you will need includes the location of the JDBC driver file, the driver class name, thedatabase connection URL, and the database user's username and password.

Note:When the Database Preparation is complete, Step 3, the Application Server Preparation, and Steps 4-9 inthe Rulebase Setup Phase can be performed in either order or simultaneously. You can, for example, launch theRulebase Setup process in Step 9 of the Assistant and then configure your Application Server while the Rulebaseload process is running.

2


However, you must configure the application server and deploy the Process Commander applications before youcan complete Step 10, PRPC Final Settings.

Important: You must be careful not to start the deployed Process Commander applications while the Rulebaseloading process is still running on the database. Note that your application server may start the applicationautomatically when it is deployed. If the Process Commander application attempts to connect to the databasewhile the Rulebase is loading, the database loading will not complete correctly.

Step 3: Application Server Preparation

Configure your application server to support the Process Commander application, including:

1. Configure the right Database Driver for your Database

2. Configure the PRPC Data Source

3. Configure other Java EE Application Server settings

4. Deploy the Process Commander application (WAR or EAR)

5. Deploy the online help application (prhelp.war) and System Management Application(prsysmgmt.war).

2. Rulebase Setup Phase

You complete the Rulebase Setup Phase by running steps 4 to 9 in the Installation and Upgrade Assistant(PRPC_Setup.jar). This tool is covered in this guide in the section Steps 4-9, Rulebase Setup Phase.

The Installation Assistant optionally creates the Process Commander schema in the database instanceyou provide, and loads the initial set of rules and classes Process Commander needs to run into thedatabase.

3. PRPC Configuration Phase

You complete the PRPC Configuration Phase after finishing the Installation by logging into ProcessCommander. The setup steps you should complete in Process Commander are described in section Step10: Final PRPC Configuration Steps.

Notes for Users of Earlier Process Commander VersionsThis installation procedure differs from earlier installation procedures in significant ways. Please reviewthe instructions carefully.

In particular, please be aware of the following changes:

3

Introduction

Pegasystems now recommends using JDBC data sources defined in your application server toestablish connections to your database instead of the Process Commander connection poolingas specified in the prconfig.xml configuration file.

Be sure to create and configure a temporary directory that Process Commander can use tostore static data. See the section “Setting the Explicit Temporary Directory” in the chapter thatdescribes deployment with your application server.

Optional: Move System Settings from Configuration Files to Database

In 6.2, System Settings you may have added to the prconfig.xml or prbootstrap.propertiesconfiguration files as "env" elements should be moved to Dynamic System Settings (Data-Admin-System-Settings). Settings in your current prconfig.xml or prbootstrap.properties files willcontinue to work, and you can move the settings to Data-Admin-System-Settings instances at anytime. Pegasystems provides a utility that can move the settings automatically from theconfiguration files to Data-Admin-System-Settings instances.

Moving the settings to the database has several advantages.

Since the settings are stored as Data- instances, they can be read from the database by allnodes running your Process Commander installation. All nodes will have the same settingvalues, unlike the values in the prconfig.xml file which apply only to the node where that file islocated.

The values of the settings can be viewed and modified from Process Commander. Values storedin the configuration files must be changed by editing the file, which sometimes requiresredeploying the Process Commander application.

For complete information on System Settings and the procedure to convert your settings, see the"Configuration Settings Reference Guide" for Version 6.2. You can find this document on the PegaDeveloper Network by going to Resource Library > Tech Papers.

4


Step1. Environment Considerations

PrerequisitesThe prerequisites for installing Process Commander are:

An application server host computer with adequate memory and disk space for the installation.Process Commander requires a minimum of 1GB of free memory. This is in addition to anymemory allocated for the operating system or other applications on the server. The memoryrequired for your system may need to be higher, depending on the number of users and yourspecific configuration.

A working installation of WebLogic.Process Commander Installation Guides for each supported application server are availablewith your Pegasystems software distribution and on the Deployment page of the PegaDeveloper Network (http://pdn.pega.com).

A DB2 database configured for Process Commander use, and support in your organization forthe installation and configuration of relational databases.

The database and application server platforms may be LINUX, UNIX or Windows systems.

A Windows system is required for the Pegasystems developer and end-user clients.

Process Commander Deployment ArchitectureProcess Commander is a Java EE enterprise application. As shown in the diagram below, it runs on top oftwo main platform sub-systems:

1. A database system to store the rules and work objects used and generated by ProcessCommander.

2. An application server that supports the Java EE specification. The application serverprovides a run-time environment and other services, such as database connections, JavaMessaging Services (JMS) support, and connector and services interfaces to other externalsystems.

5


Both developers working on Process Commander applications and users working with those applicationsaccess Process Commander through Web browser interfaces.

Process Commander Core Component VersionsThe Process Commander core application is packaged in four different versions to support deploymentinto different Java EE environments. The following table summarizes the packages provided and theiruse:

Type of deployment PRPC package to use

All Tomcat deployments prweb.war

New deployments on WebSphere 6.1.x, 7.0.x. prpc_j2ee14_ws.ear

New deployments on WebLogic 9.x, 10.3.1, 11g (10.3.2); JBoss CE 4.2.x, 4.3.x, 5.0.x prpc_j2ee14.ear

New deployments on JBoss EAP 4.3.x, 5.0.x (Red Hat) prpc_j2ee14_jbossJBM.ear

6


Pegasystems strongly recommends deploying the EAR file for all deployments other than Tomcat.

In the supported application servers, you can successfully deploy the WAR file for limited use. Inparticular, you must disable Java 2 security in the application server when using a PRPC WAR archive.Deploying and configuring the EAR file ensures that you can add advanced Java EE features as yourapplication evolves or when you migrate to a production environment.

Supported Process Commander PlatformsBecause Process Commander is developed to industry standards — Java and Java EE technologies, JavaEE compliant application servers, SQL databases, web browsers, XML, and HTML— a ProcessCommander system can be successfully deployed on a wide range of hardware and software platformcombinations. However, careful selection of your platform components can make your installation anddeployment of Process Commander easier.

To determine the right platform components for your Process Commander deployment:

1. Review the current Platform Support Guide, which is available on the Pega DeveloperNetwork (PDN) or from your Pega account executive. This document lists the recommendedsoftware components needed to support Process Commander, and any special requirementsor known issues with particular vendors or versions.

2. Review your site’s deployment requirements with your IT representatives.

3. Consult with your Pegasystems representative about your installation plans. Pegasystems’prior experience with various platforms and deployment architectures can help yourinstallation go smoothly.

For additional information see the Platform Support Guide, which is available as a PDF file on the PegaDeveloper Network (PDN), located at http://pdn.pega.com.

7


Step 2. Database Preparation -To prepare your database server to use with Process Commander, you must complete the followingtasks:

Create an empty database.

Create a database user that Process Commander can use to access the database.

Create a database schema that defines the data objects (tables, indexes, views, triggers andprocedures) required by Process Commander.

You can either have your DBA, or someone with similar permissions, use your database tools to run aSQL script provided by Pegasystems to create the schema objects, or, in Step 6 of the Assistant, you canselect the Create Schema option to have the Assistant create the schema automatically before loadingthe Rulebase.

Running the SQL script allows you to review and, if necessary, customize the schema for yourenvironment.

Database PrerequisitesBefore beginning the Process Commander installation, you must have access to a working installation ofa DB2 database server.

For specific information on supported versions and other prerequisites, see the Platform Support Guide,which is available as a PDF file on the Pega Developer Network (PDN). Go to http://pdn.pega.com andselect Guides -> Process Commander V6 Deployment..

Install and configure the relational database according to vendor directions. This database may resideon the same server as the Process Commander software, or it may be on a different server.

Important:

Be sure that Java is enabled for the Process Commander database.

Create the Process Commander DatabaseCreate a database with a minimum of 5GB for the user tablespace and, if possible, allow the database togrow. This minimum size allows you to load the initial Process Commander RuleBase and do simpledevelopment. Monitor the database use carefully. As development begins, the size of the database willneed to increase significantly, depending on your use of Process Commander and the number of users.

For each schema that contains Process Commander tables, Process Commander requires a 32Kbufferpool, a 32K user regular tablespace, and a 32K user temporary tablespace. By default, the UDBdatabase create process creates a bufferpool and temporary tablespace with only a 4K page size.

Be sure to record:

8

Step 2. Database Preparation -

Database server name

Database port number

The Process Commander system requires this information to access this database.

Create Database UsersCreate a user for this database with full read and write permissions.

Create a user account for the Process Commander database user with at least SYSADM privileges.

Important: The database user used to connect to the database during the installation and upgradeprocedures must be explicitly granted the CREATE_EXTERNAL_ROUTINE privilege. Grant this privilege tothe database user you create here. If you do not want to grant this privilege permanently, you canremove the CREATE_EXTERNAL_ROUTINE privilege after installation or upgrade is complete. It is notneeded for normal Process Commander functions.

When you configure data access in your application server, you must provide the user name andpassword for the user or users you have created to access the Process Commander database. Be sure torecord this information and have it available when configuring the application server.

If possible, it is best to create a single Process Commander user with these full permissions. If you wantto restrict users’ access to the Process Commander database, you can create two users:

A “base” user with only read and write permissions, and execute authority for running storedprocedures.

An Admin user with full access including permission for CREATE_TABLE and ALTER_TABLEoperations.

At a minimum this “base” Process Commander user must have appropriate read and write permissionsto be able to run SQL scripts on the database, and to execute stored procedures. In addition, a smallnumber of Process Commander functions require permission to run CREATE_TABLE and ALTER_TABLEoperations. You can assign permissions that include these operations to the Admin DB user whichProcess Commander uses only for these special functions.

For details, see “Creating Base and Admin Database Users,” below.

Creating Base and Admin Database Users

To implement two users, you configure access to the database in your application server by creating twodata sources:

One datasource referencing the JNDI location jdbc/PegaRULES that specifies the username andpassword for the base DB user. This user must have at least read and write permissions for thedatabase.

9


A second datasource referencing the JNDI location jdbc/AdminPegaRULES specifying theusername and password for the DB Admin user. This user must have full access includingpermission for CREATE_TABLE and ALTER_TABLE operations.

How Process Commander Uses the two Database Accounts

If you configure a second datasource for the Admin user, Process Commander uses that user whenperforming a small number of functions that require altering the database, specifically:

Using the Database Schema Management tool (Tools > Database > Modify Database Schema).

Creating any new Circumstance Definition rule or defining a single circumstance on a rule. Theextended permissions are needed to support reporting on circumstanced properties. (On thePega Developer Network, see PRKB-25173: How to create a rule with multiple circumstanceproperties.)

Exposing embedded properties for selection and reporting. (On the Pega Developer Network,see PRKB-25278: How to create Declarative indexes for embedded properties.)

For all other functions, Process Commander uses the base DB user which only requires read and writepermissions.

If you do not provide ALTER TABLE and CREATE TABLE permissions to any user, Process Commandergenerates a warning when you use these features. The warning includes SQL script that you can provideto your DBA to manually make the necessary database changes.

Create the Schema in Process Commander DatabaseBefore you load the initial Process Commander rules into the database in Steps 4-9 below, you mustcreate the database schema that defines the data objects (tables, indexes, views, triggers andprocedures) required by Process Commander.

You can create the schema in two ways:

1. In the Install and Upgrade Assistant user interface, you can select the Create Schemaoption. The Assistant then creates a default schema in the database automatically beforeloading the Rulebase.

2. Your database administrator (DBA), or someone with appropriate permissions, can run aSQL script, provided by Pegasystems, to create the schema in your Process Commanderdatabase, for example, udb_install_6.2 SP2.sql.

Running the SQL script allows you to review and, if necessary, customize the schema for yourenvironment.

If you want the Assistant to create the schema, skip the following section “Using a SQL Script to Createthe Schema”, and continue with the Assistant as described in Steps 4-9 below.

10

Step 2. Database Preparation -

To create the schema in the database using the SQL script, follow the procedure described in the nextsection.

Using a SQL Script to Create the Schema

If you choose not to select the Create Schema option in the Installation and Upgrade Assistant yourdatabase administrator (DBA), or someone with appropriate permissions, must run a SQL script tocreate the schema in your Process Commander database.

1. In the software distribution directory for Process Commander find the install SQL script foryour database type.C:\PRPC_distro\schema\udb\install\udb_install_6.2 SP2.sql

2. You or your DBA should review this script to make sure it is appropriate for yourenvironment. You can customize the script if necessary. For example, the default scriptscreate an ASCII database. Modify the scripts if you require Unicode.In most cases, the SQL script can be used without modification. If you are unsure aboutwhether the script can be run in your environment, contact Pegasystems Customer Support.

3. Use your database tools to run the appropriate SQL script against your Process Commanderdatabase.

Next StepsYou can continue either with Step 3, Application Server Configuration, or Steps 4-9, Rulebase Setup.These two procedures are independent and can be completed in either order or simultaneously.

Note, however, that you cannot run Process Commander successfully until the database setup iscomplete. If you deploy and start the Process Commander application before the database is complete,the application generates errors.

Important: You must be careful not to start the deployed Process Commander applications while the Rulebaseloading process is still running on the database. Note that your application server may start the applicationautomatically when it is deployed. If the Process Commander application attempts to connect to the databasewhile the Rulebase is loading, the database loading will not complete correctly.

11


Step 3: Application Server PreparationThis chapter describes the tasks you must complete to configure your application server and deploy theProcess Commander Java EE applications.

Before deploying the PRPC applications, you:

Verify the Java Environment

Create a Process Commander Server

Configure Support for the Process Commander Database on Your Server

Create a WebLogic Domain

Configure the Application Server

To deploy the Process Commander system, you deploy three applications:

the Process Commander core application, prweb.war or prpc_j2ee14.ear

the System Management Application, prsysmgmt.war or prsysmgmt.ear

the Developer Help application, prhelp.war.

Verify the Java EnvironmentConfirm that the Java JDK environment used by your application server is a Java 5 JDK of 1.5.0_07 orhigher, or a Java 6 JDK. The Java 7 JDK is not yet supported for Process Commander 6.2 SP2

Be sure your application server is configured to use an appropriate JDK. The default Java environmentfor your application server may not be one of the recommended JDKs for Process Commander.

Important: During installation, Process Commander requires access to the directory specified by thejava.io.tmpdir setting in the JVM. Confirm that there is write access to this directory before installingProcess Commander.

Refer to the Platform Support Guide, available as a PDF file on the Pega Developer Network (PDN)located at http://pdn.pega.com, for specific recommendations for your platform.

Configure Support for the Process Commander DatabaseIn order to support JDBC connections between your application server and the Process Commander, youmust install the appropriate database client software and JDBC drivers on your application server asrecommended by your database vendor.

Follow the IBM instructions for installing the client software and the JDBC drivers to make thedb2jcc.jar available.

12


This JDBC driver is the Type 4 universal driver.

Configure the application server so that this driver is loaded in the classpath.

Create a WebLogic Domain

Run the WebLogic Configuration Wizard to create a WebLogic domain in which to run the PegaRULESapplication.

When making the JDK Selection, select the Sun SDK, not the JRocket SDK.

For information on starting and completing the Configuration Wizard, see the WebLogic onlinedocumentation, “Creating WebLogic Domains Using the Configuration Wizard,” in the Oracle WebLogicdocumentation.

Be sure to note the User name and password for the Administrative user you configure for this domain.This is the user you will use to access the WebLogic administrative console for this domain.

Configure the WebLogic EnvironmentComplete the following procedures to set configuration properties in the WebLogic environment that arerequired by Process Commander.

Note: The procedures describe a typical method for setting configuration properties in a basic WebLogic installationby modifying the setDomainEnv file. More complex WebLogic installations may use different startup scripts. Ifyou are unsure about your environment, review this section with your WebLogic administrator to determine theappropriate script in which to enter these options so they will be read during startup.

Set the JVM Memory Parameters

You must edit the setDomainEnv file and increase the JVM memory heap size parameters to preventout-of-memory errors.

Depending on your use of Process Commander, memory consumption requirements can vary. Therecommendedminimum values for initial setup are:

Minimum Heap Size (-Xms): 1024MB

Maximum Heap Size (-Xmx): 2048MB

If your application server is using the Sun JVM as recommended, also add the PermSize andMaxPermSize settings:

PermSize (-XX:PermSize): at least 64MB

MaxPermSize: at least 384MB .

13


Note: These values are initial minimum estimates for typical development systems. They may need to be higherbased on your server hardware and the number of other applications on the server. Consult with your SystemAdministrator about the requirements for your site.

Edit the setDomainEnv Script or Batch file

Edit the files as follows:

1. Open the setDomainEnv file, setDomainEnv.cmd for Windows or setDomainEnv.sh forUNIX platforms, in a text editor.

These scripts are located in the bin directory of your WebLogic installation:

<app-server-install-root>/user_projects/domains/domain-name/bin

Example:

C:\Oracle\Middleware\user_projects\domains\pega\bin

2. Find the setting for USER_MEM_ARGS:

@REM IF USER_MEM_ARGS the environment variable is set, use it to override

ALL MEM_ARGS values

if NOT "%USER_MEM_ARGS%"=="" (

set MEM_ARGS=%USER_MEM_ARGS%

)

3. Before the override setting, add the line set USER_MEM_ARGS= to specify the memorysettings as follows:

set USER_MEM_ARGS=-Xms1024m –Xmx2048m -XX:PermSize=64m -XX:MaxPermSize=384m

For example:

@REM IF USER_MEM_ARGS the environment variable is set, use it to override

ALL MEM_ARGS values

set USER_MEM_ARGS=-Xms1024m –Xmx2048m -XX:PermSize=64m -XX:MaxPermSize=384m

if NOT "%USER_MEM_ARGS%"=="" (

set MEM_ARGS=%USER_MEM_ARGS%

)

4. Save the file.

Set an Explicit Temporary Directory

Still in the SetDomainEnv file, create a JVM property to set an explicit Temporary directory for ProcessCommander.

14


In the setDomainEnv.cmd file for Windows or the setDomainEnv.sh file for UNIX platforms, add theline set EXTRA_JAVA_PROPERTIES=-Dpega.tmpdir= and specify the full path to a directory youhave allocated, for example:

set EXTRA_JAVA_PROPERTIES=-Dpega.tmpdir=C:\PegaTemp\pr_temp

This directory is used by Process Commander to store static data during a session. It is important thatthe directory be properly specified and accessible to the Process Commander user.

Enable AWT to support PRPC Graphical Reports

You must add a “headless” AWT setting to the JAVA options in the setenv.bat (Windows) or the setenv.sh(UNIX) file that are passed to Java at startup to allow the system to render graphics. PRPC requires thissetting in order to display graphical reports.

Add or modify your JAVA_OPTIONS setting to include:

–Djava.awt.headless=true

For example, add the following line to the setDomainEnv.cmd (Windows) or the setDomainEnv.sh(UNIX) file:

set JAVA_OPTIONS=%JAVA_OPTIONS% –Djava.awt.headless=true

Put the JDBC Driver in the WebLogic classpath

For Process Commander to connect to the relational database, the database driver(s) must be in theWebLogic classpath.

In the setDomainEnv.cmd (Windows) or the setDomainEnv.sh (UNIX) file, add the line set EXT_PRE_CLASSPATH= and specify the path to db2jcc.jar. Using EXT_PRE_CLASSPATH ensures that thesystem finds and uses this JDBC driver.

For example, your setting will look similar to the following:

set EXT_PRE_CLASSPATH=C:\Oracle\Middleware\user_projects\domains\pega\lib\db2jcc.jar

This JDBC driver is the Type 4 universal driver: db2jcc.jar

Save and close setDomainEnv

When you have completed your edits, be sure to save and close the setDomainEnv file.

Next StepsIn the next section you complete the application server configuration in the WebLogic administrativeconsole and deploy the Process Commander applications.

15


Deploy Process Commander ApplicationsThe procedures below describe the steps you need to take in the WebLogic Administration Console toconfigure and deploy the Process Commander applications.

For more information on installing and using the WebLogic Administration Console, see the OracleWebLogic documentation athttp://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html

Open the WebLogic Administration Console

1. Start the Administration server for the Process Commander domain.

You can start the Administration Server by running the appropriate startWebLogic script,startWebLogic.cmd (Windows) or startWebLogic.sh (UNIX,) in the bin directory of yourdomain directory, for example:

Oracle\Middleware\user_projects\domains\pega\bin

On Windows, you can also start the Administration server from a shortcut on the Startmenu: Oracle WebLogic -> User Projects ->DOMAIN_NAME -> Start AdminServer for WebLogic Domain.

2. Start the Administration Console and login with the administrative user name and passwordthat you specified in the Configuration Wizard.

You can start the Administration Console in a browser by opening the URLhttp://hostname:port/console where hostname is the name of the AdministrationServer and port is the listen port on which the Administration Server is listening forrequests (port 7001 by default).

On Windows, you can also start the Administration server from a shortcut on the Startmenu: Oracle WebLogic -> User Projects -> DOMAIN_NAME -> Admin ServerConsole.

The Administration Console is displayed:

16


http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html

Enable DNS Lookup

The Process Commander Tracer requires that DNS lookup be enabled in order to display the name of theclient host, rather than its IP address. To enable DNS lookup, perform the following steps:

1. In the Admin console navigate to Environment -> Servers -> AdminServer ->Configuration -> Tuning.

Under Domain Structure click Environment -> Servers.

On the Summary of Servers page, click AdminServer

On the Settings for AdminServer page, make sure the Configuration tab isselected and click the Tuning tab on the Configuration menu bar.

The Tuning settings page is displayed:

17


2. On the Tuning page, enable Reverse DNS Allowed:

If configuration editing is not enabled, click Lock & Edit in the Change Center atthe top-left of the page.

Select the checkbox Reverse DNS Allowed.

Click Save on the Settings page.

If configuration editing is not enabled, click Activate Changes in the ChangeCenter.

A confirmation message is displayed on the AdminServer page:

18


Still in the Administration Console, continue on to the next procedure.

Create JDBC Resources

Complete the following procedure to create a JDBC Connection Pool and Data Source in WebLogic toallow PRPC to connect to the PRPC database.

1. In the Administration Console, under Domain Structure, open the Services ->JDBC->Data Sources page:

The page Summary of JDBC Data Sources is displayed.

2. If configuration editing is not enabled, in the Change Center click Lock & Edit.

3. On the Data Source page click New.

19


The page Create a New JDBC Data Source is displayed:

4. Complete this page as follows:

In the Name field, enter: PegaRules

In JNDI Name, enter exactly: jdbc/PegaRULES

Select the Database Type DB2

Select a Database Driver suitable for the Type you selected.

After you select the Database Type, the Database Driver dropdown lists theJDBC drivers available for that Type. If you are unsure about which JDBC driverto choose, check with your database administrator.

Important: If you choose an XA driver to enable two-phase commit, you must install the prpcj2ee14.ear file asthe core Process Commander component. For more information see Process Commander Core ComponentVersions on page 5.

20


For Oracle 10g or 11g, specify Type 4 (thin client) JDBC drivers. For Oracle 9, specify Type 2 (thick client) JDBCdriver.

PRPC stores some data in BLOBS (binary large objects.) In Oracle 9, the JDBCOCI (Oracle Call Interface)connection supported by the Type 2 driver is required to support PRPC’s use of BLOBS5. Click Next..

5. 5. Click Next.

A Transactions Options page, similar to the following, displays. The particular optionsthat appear depend on the type of driver you selected.

6. Unless instructed otherwise by your site database administrator, accept the defaults for thetransaction options and click Next.

The Connection Properties page displays:

21



In the Database Name field enter the name of the Process Commanderdatabase.

In the Host Name field, enter the name or IP address of the database server.

In the Port field enter the port number to be used to connect to the databaseserver.

Complete the User Name and Password fields with the credentials for theProcess Commander user you created for the database.

8. Click Next.

The next page varies depending on the type of database you are specifying, for example:.

22


9. Enter the Driver Class Name and URL for DB2

Driver Class Name: com.ibm.db2.jcc.DB2Driver

URL: jdbc:db2://localhost:50000/db_name

Modify localhost, the port number, and the database name to specify your database serveras needed.

23


10. Update the Properties text box to add the connection properties:

Specify the current Schema by listing the currentSchema, property specifying the DB userschema name, and the currentFunctionPath property specifying SYSIBM,SYSFUN,andthe DB user schema name:

currentSchema=<SCHEMANAME>,

currentFunctionPath=SYSIBM,SYSFUN,<SCHEMANAME>

For example, if the schema name is PRPC, the connectionProperties would be:

currentSchema=PRPC;

currentFunctionPath=SYSIBM,SYSFUN,PRPC

Be sure to enter the schema name in all capital letters, as in the example.

Note: SYSIBM and SYSFUN are system schemas provided by DB2. They are required becauseProcess Commander makes use of some functions made available in these schemas.

DB2 UDB versions 9.5 and 9.7 require four additional settings:

fullyMaterializeLobData=true

fullyMaterializeInputStreams=true

progressiveStreaming=2

progressiveLocators=2

You can add these settings as additional connection properties or as parameters in the URL.

To specify these settings as connectionProperties, add these to the connection propertiesfield.

To add these settings as parameters to the connection URL, append them to the URL assemi-colon separated properties:

url=jdbc:db2://sysvol2:50000/PRPC:fullyMaterializeLobData=true;

fullyMaterializeInputStreams=true;

progressiveStreaming=2;progressiveLocators=2;

Note: The currentSchema and currentFunctionPath properties must be specified as aconnectionProperties setting, and cannot be entered into the URL.

11. Click Test Configuration. If the test is successful, click Finish.

If the test is not successful, review your settings and retest.

24


When you click Finish, you will be returned to Summary of JDBC Data Sources.

12. If Configuration editing is not enabled, click the Activate Changes button in the ChangeCenter.

13. Click the name of the data source you just created in the Data Sources table.

14. On the Settings page for the data source, click the Connection Pool tab.

15. If Configuration editing is not enabled, click the Lock & Edit button in the Change Center toedit the data source Configuration.

16. Verify that the Connection Pool properties are correct for the data source you created, andmodify as needed.

17. Select the Targets tab and select the AdminServer as the target for the data source.

25


18. Click Save, then, if Configuration editing is not enabled, click Activate Changes.

Configure JMS Resources for an EAR deployment

If you are deploying Process Commander’s EAR archive, for example prpc_j2ee14.ear, complete thefollowing procedures to define JMS resources used by PRPC.

If you are deploying Process Commander’s WAR archive, prweb.war, you do not need to configure JMSresources. Continue with the configuration procedure, Deploying the Process Commander WAR file,prweb.war” on page 46.

Important: Process Commander's EJB components make use of JMS Services internally. If you are deploying theEAR archive, you must complete this procedure even if your PRPC application does not use messaging to integratewith external systems.

To configure the JMS resources required by PRPC, you will complete the following tasks:

1. Create a JMS Server targeted at your WebLogic server.

2. Create a JMS Module.

3. In the JMS Module create:

– a Connection Factory and subdeployment, targeted to the JMS Server

– a Topic and subdeployment, targeted to the JMS Server.

The procedure for each of these tasks is described below.

26


Create a JMS Server

1. On the Administration Console, under Domain Structure, click Services > Messaging> JMS Servers.

2. If Configuration editing is not enabled, click Lock & Edit in the Change Center. Click Newto create a new server.

3. In the Name field, enter a name to identify the PRPC JMS server, such as PRJMS_Server,and click Next.

27


4. In the Target dropdown, select your Admin Server or the managed server you created forPRPC, and click Finish.

You will be returned to the Summary of JMS Servers page:

5. Confirm that you see the message, JMS Server created successfully. If Configurationediting is not enabled, click Activate Changes in the Change Center.

6. 6. Click Home to return to the Domain home page.

Create a JMS Module

1. On the Administration Console, under Domain Configurations, click Services ->Messaging -> JMS Modules.

28


This will become the container for the connection factory and topic.

2. If Configuration editing is not enabled, click Lock & Edit in the Change Center. Click Newin the JMS Modules table.

3. On the Create JMS System Module page, enter a name, such as PRJMS-Module, and click

29


Next.

4. In the Targets table, select the checkbox for Admin Server, or the server to which you willdeploy PRPC, and click Next.

5. CheckWould you like to add resources to this JMS system module? and clickFinish.

The Settings page for your JMS Module is displayed:

30


6. Confirm that you see the message The JMS module was created successfully. IfConfiguration editing is not enabled, click Activate Changes in the Change Center.

Create a Connection Factory and Subdeployment

1. Still on the Settings page for your JMS Module, click Lock & Edit in the Change Center ifConfiguration editing is not enabled. Click New in the Summary of Resources table todisplay the page.

31


2. Select Connection Factory, and click Next.

3. Enter a Name for the Connection Factory, such as PRAsyncConnectionFactory, and enterexactly the JNDI Name jms/PRAsyncTCF. Click Next.

32


4. Click Advanced Targeting.

5. Click Create a New Subdeployment.

33


6. Under Subdeployment Properties, enter a Subdeployment Name, such as PRJMS_Subdeployment, and click OK.

You are returned to the Properties page for the Connection Factory:

7. Under Targets, select the checkbox for the JMS Server you created for PRPC and clickFinish.

You are returned to the Settings page for your JMS Module:

34


8. Confirm that you see the message Connection Factory created successfully. IfConfiguration editing is not enabled, click Activate Changes in the Change Center.

Create a Topic and Subdeployment

Repeat the procedure you just completed for the Connection Factory to create a JMS Topic andSubdeployment in this JMS Module.

1. On the Settings page for your JMS Module, click Lock & Edit in the Change Center ifneeded, and New in the Summary of Resources table to display the page Create a NewJMS System Module Resource again.

2. From the list of resource types, click Topic and then Next button to display the pageCreate a New JMS System Module Resource for the topic.

35


3. Enter a name for the Topic, such as PRAsyncTopic, and enter exactly the JNDI namejms/PRAsyncTopic. Click Next.

4. Select Create a New Subdeployment.

5. On the page Create a New Subdeployment, enter a new name for the subdeployment,

36


such as PRJMS_Subdeployment_Topic, and click OK.

Note: Be sure to use a different name than the one you used for the Connection FactorySubdeployment. The Connection Factory and the Topic should each have their own subdeployment.

6. Under Targets, select the checkbox for the JMS Server you created for PRPC and clickFinish.

You are returned to the Settings page for your JMS Module

37


7. Confirm that you see the message The JMS Topic was created successfully. IfConfiguration editing is not enabled, click Activate Changes in the Change Center.

This completes the configuration tasks for your WebLogic server. Continue with the following section:Deploy the Process Commander Application.

Deploy the Process Commander Core Application

Follow the procedure below to deploy the Process Commander Core Application, prweb.war or prpc_j2ee14.ear.

For more information on which application to use, see Process Commander Deployment Architecture onpage 5.

Note: Deploy either prweb.war or prpc_j2ee14.jar. Do not deploy both archives.

38


Deploying the Process Commander WAR file, prweb.war

1. In the Domain Structure section, click Deployments:

2. If Configuration editing is not enabled, click Lock & Edit to unlock the page. In theDeployments table, click Install.

3. In the Install Application Assistant, click the link upload your file(s).

39


4. Click the Browse button next to the Deployment Archive field, use the file dialog tonavigate to the archives directory of your Process Commander distribution.

5. Select the prweb.war file and click Open. When the file name is displayed in theDeployment Archive field, click Next.

40


6. Make sure the radio button next to prweb.war is selected and click Next.

7. Select Install this deployment as an application and click Next to display the optionalsettings page:

41


8. Make sure the Name is prweb and click Next to accept the defaults.

42


9. Leave Yes, take me to the deployment's configuration screen selected and reviewthat the other settings are as expected. Then, click Finish to begin deploying theapplication.

When the WAR file has deployed, you are returned to the application’s Settings page:

43


10. Review the Overview page to confirm that the settings are as expected.

11. Click on the Targets tab and verify that the target server is correct.

12. Click Save in the Assistant or Activate Changes in the Change Center to save theconfiguration.

44


13. In the Domain Structure panel, click Deployments again to continue with thedeployments of the prsysmgmt.war and prhelp.war applications.

Deploying the Process Commander EAR file, prpc_j2ee14.ear

Note: Deploy either prweb.war or prpc_j2ee14.jar. Do not deploy prpc_j2ee14.jar if you have already deployedprweb.war.

1. In the Domain Structure panel, click Deployments:

2. If Configuration editing is not enabled, click Lock & Edit to unlock the page. Click Install.

45


3. Click the link upload your file(s).

4. Next to the Deployment Archive field, click the Browse button and use the file dialog tonavigate to the archives directory of your Process Commander distribution. Select theProcess Commander archive, prpc_j2ee14.ear. When the file name is displayed in theDeployment Archive field, click Next.

46


5. On the Install Application Assistant, confirm the upload path and that the radio buttonnext to the archive name is selected and click Next.

6. Select Install this deployment as an application and click Next to display the optionalsettings page:

47


7. Click Next to accept the defaults.

48


8. Leave Yes, take me to the deployment's configuration screen selected adn reviewthe settings to confirm that they are as expected. Then, click Finish to begin deploying theapplication.

When the archive deploys, you are returned to the application’s Settings page:

49


9. Review the Overview page to confirm that the settings are as expected.

50


10. Click on the Targets tab to verify that the target server for the application is correct.

11. Click on the Overview tab again, and click Save.

12. In Domain Structure, click on Deployments to return to the Summary of Deploymentspage.

51


13. Continue with the deployments of the prsysmgmt.war and prhelp.war applications.

Deploy the prsystmgmt.war and prhelp.war applications

Repeat the procedure described for prweb above to deploy the two other Process Commanderapplications, prsysmgmt.war and prhelp.war:

Note: Do not start these applications after deployment.

For more details on the System Management Application, refer to the System Management ApplicationReference Guide available on the Pega Developer Network (pdn.pega.com).

Assigning the PegaDiagnosticUser Role to your System ManagementApplication Users

Users accessing the System Management Application in Process Commander must be assigned the rolePegaDiagnosticUser. If the user does not have this role they will be challenged for authentication whenthey attempt to access the System Management Application from Process Commander.

By default, the deployment configuration for Process Commander assigns the PegaDiagnosticUser roleto administrative users. If you want to restrict access to the System Management Application, use yourapplication server tools to assign the PegaDiagnosticUser role to any other users that must be able toaccess the System Management Application.

The role PegaDiagnosticUser is associated with the System Management Application through a security-constraint element on the Diagnostic Data servlet defined in the prweb.war application’s web.xml file:

<security-constraint>

<web-resource-collection>

<web-resource-name>Diagnostic Data</web-resource-name>

<description>Serves diagnostic files generated by the JMXclient</description>

52


<url-pattern>/DiagnosticData</url-pattern>

<http-method>GET</http-method>

<http-method>POST</http-method>

</web-resource-collection>

<auth-constraint>

<role-name>PegaDiagnosticUser</role-name>

</auth-constraint>

</security-constraint>

If you do not want to restrict access to the System Management Application, edit the web.xml file in theWEB-INF directory of the prweb.war deployment in your application server and delete this securityconstraint element.

In EAR file deployments, the web.xml file is located in the prweb.war file packaged inside the prpc_j2ee14.ear file.

Note: Changing this setting in the web.xml file may require redeploying of the PegaRULES Application.

Next Steps

If you have not completed the Rulebase Loading phase, continue with the next section: Steps 4-9Rulebase Setup Phase. Be sure that the Process Commander applications are not started.

If you have completed the Rulebase Loading phase, start the Process Commander applications andcontinue with Step 10, Final Settings in PRPC.

53


Steps 4 to 9 - Rulebase Setup

Install the Process Commander Schema and Rules in the DatabaseRun the Process Commander Installation and Upgrade Assistant to create the Process Commanderschema in the database, and load the Process Commander application rules.

Note: The following procedure describes the use of the user-interface to the installer to create the schema in thedatabase and load the base Process Commander rules. The 6.2 SP2 distribution also includes scripts to supportthese tasks through a command-line interface. Support is provided through install.bat and install.ksh filesconfigured through a properties file, setupDatabase.properties. To use the scripted option, see the README.txt filein the "scripts" directory of your Process Commander software distribution.

The computer on which you run the Installation and Upgrade Assistant must have access to allow adatabase connection to the Process Commander database. This computer should also have at least

1GB of RAM

6GB of disk space available for the temporary directory, pegaGuiInstallerTemp, created inthe directory in which PRPC_Setup.jar is run. This directory is deleted when the assistant'sprocesses are complete.

a local installation of at least Java JDK 1.5.

Note: Before running the Installation and Upgrade Assistant for a DB2 database, increase the log file size of thedatabase to at least 655360KB. The default log file size is 425984KB.

Move the Process Commander Software Distribution to Your Computer

If you are installing the software distribution downloaded from Pegasystems, copy the distributionfile, for example 113990_prpc62s2.zip, to the computer on which you will run the Installation andUpgrade Assistant. Extract the contents of the ZIP file to an empty directory.

If you are installing the software from the Process Commander DVD, copy the contents of the DVDto an empty directory.

Important: Be sure this computer has a high-speed network connection to your database. For best performance,run this Installation and Upgrade Assistant directly on the database server. The Rulebase Loading step in this toolloads several gigabytes of data to the database. Loading this data over a VPN or slow network connection candramatically increase the total time required to complete the process. If you cannot run the Assistant directly onthe database server, please run this tool on amachine with fast, direct network access to the database server.

The Process Commander home directory contains the following directories and files:

54


Update Java 6 JDK to JAX-WS API 2.2.5

If you are using the Java 6 JDK, you must update the JDK environment to use version 2.2.5 of the JAX-WS API.

The JAX-WS API (jaxws-api.jar) bundled with the Java 6 JDK is version 2.0. Process Commanderrequires JAX-WS version 2.2.5. Use the Java Endorsed Standards Override Mechanism(http://docs.oracle.com/javase/6/docs/technotes/guides/standards/) to ensure that the 2.2.5 classesare loaded:

1. In the expanded Process Commander software distribution, go toResourceKit/Utilities/Java6Updates.

2. From that directory, copy jaxws-api-2.2.5.jar to the <JAVA_HOME>/lib/endorseddirectory on your application server. Create the endorsed directory in the lib directory ifone does not exist.

When you restart your application server, the Java bootstrap loader loads the classes in the endorseddirectory in place of any it might find otherwise.

Rulebase Setup Using the Installation and Upgrade AssistantFollow these steps to load the Process Commander rules to the database.

1. Double-click on the PRPC_Setup.jar file or right-click the file and click Open With >Java, to launch the Installer.

55


If JAR files are not associated with Java commands on your system, launch the installer atthe command-line. In a command-line console, change to the directory containing PRPC_Setup.jar, and type in the following command:

Java –jar PRPC_Setup.jar

Note: Use the command-line jar command on Windows systems if you see the following error when you try tolaunch PRPC_Setup by double-clicking the JAR file.

Could not extract JAR file to directory: C:\Windows\System32\pegaGUIInstallerTemp

56


2. Click Next to display the Environment Considerations.

See Step 1, Environment Considerations in this guide for more information oncompleting this step.

3. Click Next to display the Database Preparation page.

57


Review this page to confirm that you have prepared the database as required.

See Step 2, Database Preparation in this guide for more information on completing thisstep.

These tasks are completed outside of the Assistant. You must complete this preparationbefore running the Rulebase Load phase. You can exit from this tool to complete them, andthen restart to continue beyond this point.

Important: Be sure you have configured the database user you will use during installationas described in Create Database Users Database Prerequisites on page 8In particular, thedatabase operator used to connect to the database during the installation procedure mustbe explicitly granted the CREATE_EXTERNAL_ROUTINE privilege, for example:

GRANT CREATE_EXTERNAL_ROUTINE ON DATABASE TO USER <username>

4. When your Database Preparation is complete, click Next to display Application ServerPreparation.

58


5. Review this page to learn about the tasks you complete to prepare your application serverbefore deploying the Process Commander applications.

These tasks are completed outside this Assistant. You can exit from this tool to completethem, and then restart to continue beyond this point, or you can continue with the RulebaseSetup phase immediately and complete the Application Server Preparation later.

Note:When the Database Preparation is complete, Step 3, the Application Server Preparation, andSteps 4-9 in the Rulebase Setup Phase can be performed in either order or simultaneously. You can,for example, launch the Rulebase Setup process in the Assistant and then configure your ApplicationServer while the Rulebase load process is running.

However, you must configure the application server and deploy the Process Commander applicationsbefore you can complete Step 10, PRPC Final Settings.

Important: You must be careful not to start the deployed Process Commander applications whilethe Rulebase loading process is still running on the database. Note that your application server maystart the application automatically when it is deployed. If the Process Commander applicationattempts to connect to the database while the Rulebase is loading, the database loading will notcomplete correctly.

6. If you have completed your Application Server Preparation or you want to continue with the

59


Rulebase Setup in the database before completing the Application Server Preparation, clickNext to display the License Agreement.

7. Review the License agreement and click Accept to continue to Type of Setup.

60


8. Select Installation and click Next to display the Database Configuration page.

61



Database Type

– Select the type of your Process Commander database.

Create Database Schema

– Leave Create Database Schema checked to allow the Assistant to create theappropriate schema in the database as part of the Rulebase Load process. Youdatabase should be empty.

– Uncheck Create Database Schema if you used your database tools to create theschema using the SQL scripts provided in the schema directory of your softwaredistribution.

See “Using a SQL Script to Create the Schema” in this guide for more information.

Note: If you run the Assistant with Create Database Schema selected on a database thatalready has the schema installed, the Rulebase Load process fails with an error message.

62


Click Next to display the Database Connection page.

Specify the location of the driver JAR file, the database connection URL, the database user nameand password, and the user schema name.

3. Complete the fields to specify the database connection to your Process Commanderdatabase:

JDBC Driver Class Name

Confirm the name of the appropriate database driver class: com.ibm.db2.jcc.DB2Driver

Driver JAR file

Enter the full path to the driver file.

This JDBC driver is the Type 4 universal driver: db2jcc.jar

Use additional fields if your database requires more than one JAR file.

See Configure Support for the Process Commander Database for information on yourdatabase.

63


Database JDBC URL

Enter the JDBC connection URL for your Process Commander database in the following format:

jdbc:db2://serverName:port/dbName

Be sure to include the following parameters:

- fullyMaterializeLobData=true;

- fullyMaterializeInputStreams=true;

- progressiveStreaming=2;

- progresssiveLocators=2;

Username and Password

Enter the user name and password you created for the Process Commander user on yourdatabase.

Important: Be sure you have configured the database user you will use during installation asdescribed in Create Database Users Database Prerequisites on page 8In particular, thedatabase operator used to connect to the database during the installation procedure must beexplicitly granted the CREATE_EXTERNAL_ROUTINE privilege, for example:

GRANT CREATE_EXTERNAL_ROUTINE ON DATABASE TO USER <username>

Schema Name

Enter the schema name assigned to the Process Commander database when it was created.

3. When you have completed entering the database connection information, click TestConnection.

The Installation Assistant tests whether it is able to make a connection to the database youhave specified and displays the result:

64


Click OK to close the window.

If the connection is not successful, review your connection information, correct any errors,and retest.

When the connection is successful, click Next to continue to the System Name andProduction Level page.

4. If required, specify the System Name and Production Level to assign to the installedProcess Commander System. In most cases, the defaults are used.

Enter the full path to a directory or Browse to specify a temporary directory for theInstallation Assistant to use while loading the Process Commander rules. By default, theAssistant uses a directory, pegaGuiInstallerTemp, created in the directory from whichthe tool is run. If you leave the field blank, the Installation Assistant uses the user systemtemporary directory.

Important: The Assistant requires at least 3 GB of space during the installation process. Be surethere is enough disk space to allow the directory to grow to this size. The Assistant deletes alltemporary files at the end of the process.

Click Next to display the Rulebase Loading page.

65


5. Press START to begin loading the database with the rules.

Note: A typical installation can take 30 to 60 minutes depending on the speed of your system. Ifyou choose to pre-load the assembled rules cache, the process takes an additional 90 minutes.

When processing the larger files, the log can appear inactive for someminutes. Please allow theAssistant to finish.

The Assistant shows the progress through the stages of the installation:

66


Click Show Logs to see the log detail as the process is running.

67


The Assistant displays the following window when complete:

68


If the process does not complete:

Review information on the logs in the Output and Error tabs, and correct the problems.

Exit from the Assistant.

Clear the Process Commander database:

Using your database tools, run the drop SQL script in the schema\udb\util directory in theProcess Commander software distribution, for example:

C:\PRPC_distribution\schema\udb\util\udb_drop_6.2.sql

Restart this Installation and Upgrade Assistant and complete the steps again as directed above.

5. When the process completes, the instructions for Step 10—Final Settings in PRPC opensin a browser window:

69


6. Click Exit in the Assistant and continue with the procedures in the next section Step 10—Final Settings in PRPC.

70


Step 10 - Final Settings in Process CommanderTo complete the installation, you login and configure settings in Process Commander.

Start and Login to Process CommanderAccess the Process Commander servlet, PRServlet, through a browser. Type in the URL for ProcessCommander application: http://<server>:<portnumber>/<context_root>/PRServlet. Forexample:

http://prpc-server:9080/prweb/PRServlet

The PegaRULES login screen (PRServlet) will be displayed:

Login to Process Commander:

– User Name: [email protected]– Password: install

The Process Commander Developer portal displays with a welcome message in the What’s Happeningsection of thepage:

71

Step 10 - Final Settings in Process Commander

Process Commander automatically launches a process to index the Process Commander rules in thesystem to support full-text search in the Developer environment. While this process is running, you maynotice some delay in the responsiveness of the Process Commander user interface. Depending on yoursystem, the indexing will complete in 10 to 15 minutes.

Note: This indexing process starts as soon as you start the Process Commander in the application server. Beforeyou login, you may notice this activity in your application server administrative console.

If you want to monitor the progress of the process, click here in the What’s Happening message.

Configure Process CommanderUse the Process Commander Landing pages, accessed from the Pega button, to configure your initialenvironment:

72


Enable Developer Help and the System Management Application

To enable Help and the System Management Application, you must set the URLs that are used to accessthem.

1. From the Pega button, select System -> Settings -> URLs

2. Complete this page to specify the URLs to access the Help (prhelp.war) and SystemManagement (prsysmgmt.war) applications.

In the field Online Help URL, enter the URL for the prhelp.war file in the form:http://nodename:portnumber/prhelp.

Typically, you provide the name and port number of your Process Commander server, forexample, http://prpc_server:9080/prhelp

In the field for SMA URL, enter the URL for the System Management Application,prsysmgmt.war in the form http: //nodename:portnumber/prsysmgmt, for example,http://prpc_server:9080/prsysmgmt.

These applications are accessed from the Process Commander interface. Either applicationcan be deployed to a different application server than the core Process Commanderapplication.

Note: If you specify localhost as the server name, only users logged into the same server on whichthe applications are deployed are able to access the applications. Replace localhost with the actualserver name if you want to allow access to the applications from other Process Commander nodes.

3. In the field Public Link URL, you can also optionally provide a URL for your Process

73


Commander system to allow Directed Web Access, typically in the form:http://nodename:portnumber/PRServlet.

Directed Web Access (DWA) allows external users that do not have a ProcessCommander Operator ID to process an assignment in your application on a one-time basis.The URL you specify here is provided in an email to the external users to access ProcessCommander and may identify a proxy server. On the Pega Developer Network,(pdn.pega.com) see PRKB-24206: How to send an assignment by email to an external partyusing basic Directed Web Access.

4. Click Submit

You must log out of Process Commander and log back in for these changes to take effect.

Optionally Set Search Index Host Node Settings

Search indexing supports the full-text search facility in Process Commander for rules, data instances,and work objects. By default, Search indexing is enabled and indexing starts automatically when youstart the application server after deploying Process Commander. Host Node Settings are set by defaultto your Process Commander node, and the Index directory is set to PegaRULESIndex in your ProcessCommander temporary directory.

You can change the default settings on the System – Settings landing page Search tab. From the Pegabutton, select System -> Settings -> Search.

74


For information about using this page, go to System category—Settings page in the Developer PortalOnline Help.

75


Create an Organization

1. From the Pega button, select the Org & Security > Organization Setup landing page:

2. In the Organization Name field, enter the name of your organization, leave the Actioncontrol set to Preview and click Run to review the objects and users that will be created.

Right-click in the window and select Print to print a record of this page.

Important: Be sure to preview and record the information on this page. The organization name youprovide will be used to create the initial users and access groups for your Process Commandersystem. You will need to know the user names to log on and begin using your Process Commanderinstallation.

3. Set the Action to Create and click Run to create the organizational structure.

4. Stop and restart the application server.

Change the password for [email protected]: To protect your system, be sure to change the password for the Operator [email protected]. The default password is widely published.

76


Install Solution FrameworksIf you are installing one of Pegasystems Solution Frameworks as part of your Process Commanderdevelopment environment, install the framework now. Follow the instructions in the Installation Guidefor the framework.

77


Documents

Pega Community | Training & Resources for Pega Developers ......JVM,JDBCDriver,ApplicationServer,DatabaseServer,PRPC,andtheirrespectivesettings. 1.ReviewthecurrentPlatformSupportGuide,whichisavailableonthePegaDeveloper