PRPC63 Install WAS7Oracle

Process Commander

Installation GuideVersion: 6.3

Database: Oracle

Application Server:WebSphere 7

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.3

Updated: Tuesday, August 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. DatabasePreparation - 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 WebSphere Profile 13

Start and Configure the Application Server 14

Set JVM Requirements 15

Create URL Providers 22

Create JDBC Resources 27

Create a JDBC provider 27

Create Data Source 31

Configure WebSphere WorkManager 44

Set HTTP transport channel custom property CookiesConfigureNoCache to false 47

Deploy the PegaRULES core application 52

Deploying prpc_j2ee14_ws.ear in WebSphere 53

Installing the System Management and Online Help Applications 62

Assigning the PegaDiagnosticUser Role to your System Management Application Users 69

Next Steps 72

Steps 4 to 9 - Rulebase Setup 73

Install the Process Commander Schema and Rules in the Database 73

Move the Process Commander Software Distribution to Your Computer 73

Update Java 6 JDK to JAX-WS API 2.2.5 74

Rulebase Setup Using the Installation and Upgrade Assistant 74

Step 10 - Final Settings in Process Commander 91

Start and Login to Process Commander 91

iii

Process Commander Version 6.3

Configure Process Commander 92

Enable Developer Help and the System Management Application 93

Optionally Set Search Index Host Node Settings 94

Create an Organization 96

Change the password for [email protected] 96

Install Solution Frameworks 97

iv

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

To upgrade a Process Commander 4.2 system to 6.3, your current system must first be at 4.2SP6. 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.3, first upgrade to V5 (see the manual Upgrade Guide, V4.2 SP6to V5) and then upgrade to 6.3.

For information about upgrading any existing Process Commander 5 installation to 6.3 see theProcess Commander Upgrade Guide 6.3, released with Process Commander 6.3.

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 DocumentationThe 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 updatesCheck 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 TrainingA 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.3 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 PhaseYou 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.3 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 sites deployment requirements with your IT representatives.

3. Consult with your Pegasystems representative about your installation plans. Pegasystemsprior 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 PhaseYou 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 PhaseYou 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 DatabaseIn 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 WebSphere 7.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).

An Oracle database configured for Process Commander use, and support in your organizationfor the 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.

You must deploy the EAR file:

in WebSphere 6 or 7 (with or without J2SE and Java EE security options), or

if you plan to use any of the following Java EE container-managed features in your applications:

Two-phase commit

JMS message services

Service EJB rules (Rule-Service-EJB rule type)

Important: You must deploy the EAR file in the WebSphere application servers. WebSphere's strictimplementation of the Java EE specification does not support use of the Process Commander WAR file.The Process Commander EAR file is designed for use in WebSphere systems.

In the supported application servers other than WebSphere, you can successfully deploy the WAR file forlimited use. In particular, you must disable Java 2 security in the application server when using aPRPCWAR archive. Deploying and configuring the EAR file ensures that you can add advanced Java EEfeatures as your application 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 sites deployment requirements with your IT representatives.

3. Consult with your Pegasystems representative about your installation plans. Pegasystemsprior 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. DatabasePreparation -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.

Database PrerequisitesBefore beginning the Process Commander installation, you must have access to a working installation ofan Oracle 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.

If you are using Oracle 11g, do not use the UCP (Universal Connection Pool) feature in yourProcess Commander database. An Oracle bug (BUG 8462305) causes a failure when anapplication tries to call a stored procedure. This causes Process Commander to workincorrectly with a database using UCP.

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.

Be sure to record:

Database server name

Database port number

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

8

Step 2. DatabasePreparation -

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

Set the user account for the Process Commander database user with the default RESOURCE andCONNECT roles with all corresponding system privileges granted. In particular, be sure that the user hasbeen explicitly granted the Create View and Create Procedure system privileges.

Note: On the Oracle 10g HTML-based Enterprise Manager console there are separate tabs for setting the usersroles and system privileges. When editing the properties for the Pega user, be sure to go to the Roles tab to set theRESOURCE and CONNECT roles, and then to the System Privileges tab to set the Create View system privilege.

Important: Do not grant DBA access to the user, as this may cause problems with the installation.

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 UsersTo 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 AccountsIf 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 create the schema in one of two ways:

In the Install and Upgrade Assistant user interface, you can select the Create Schema option.The Assistant then creates a default schema in the database automatically before loading theRulebase.

Or, 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, oracledate_install_6.3.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 Next Steps on page 11.

10

Step 2. DatabasePreparation -

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 SchemaIf 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\oracledate\install\oracledate_install_6.3.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

Configure Support for the Process Commander Database on Your Server

Create a WebSphere Profile

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.3

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 all Oracle instructions for installing the JDBC drivers.

Confirm that the appropriate JDBC driver is in the /jdbc/lib directory of your Oracle installationdirectory or download it from the Oracle site.

12


The appropriate file depends on the Java version of your JVM:

For Java 5: ojdbc5.jar


If you are using the OCI (thick) driver, confirm or create the following environment variables for yoursystem.

Note: Pegasystems recommends use of the Thin Client driver.

Solaris

Set ORACLE_HOME and LD_LIBRARY_PATH environment variables.

Add $ORACLE_HOME/lib32 to the LD_LIBRARY_PATH before the reference to the standard$ORACLE_HOME/lib directory (as Process Commander uses 32-bit libraries).

AIX

Set ORACLE_HOME and LIBPATH environment variables.

Add $ORACLE_HOME/lib32 to the LIBPATH before the reference to the standard $ORACLE_HOME/lib directory (as Process Commander uses 32 bit libraries).

Windows

On Windows, the necessary environment variables are usually set by the Oracle installationprogram. Confirm that the ORACLE_HOME is set to your database installation directory and thatthe Path environment variable includes the path to the Oracle bin directory.

Create a WebSphere ProfileRun the WebSphere Profile Management Tool to create a WebSphere Application Server profile in whichto run the PRPC application. You must create a new profile dedicated to PRPC, so that PRPC can run in itsown JVM environment.

You may use either the Typical profile creation or the Advanced profile creation option. The Typicalprofile assigns default values for such things as the Profile name, Node name, Host name, and accessports. Advanced Profile creation lets you change the defaults. Both methods allow you to choosewhether to apply Administrative Security requiring a login with user name and password when startingthe Administrative Console.

If you choose the Advanced option, be sure to choose to deploy the Administrative Console.

Note: On Windows platforms, the Typical option creates the application server as a Windows service bydefault. This means that you must manage the profile as a Windows service, for example when startingand stopping the server.

13


If you do not want to run the application as a Windows service, choose the Advanced profile creationoption and, on the Windows Service Definition page, do not check Run the application server process asa Windows Service.

Make sure you record the following information about the profile you create:

Profile name

User name and password for the Administrative Console (if you choose to apply AdministrativeSecurity.)

Port numbers for the profile, including at least:

Administrative Console Port (9060 by default)

HTTP transport port (9080 by default)

Depending on your environment, you may also need to record the port numbers for the Administrativeconsole secure port, the HTTPS transport port, and the SOAP connector port. If you are unsure aboutthese requirements, check with your application server administrator

Start and Configure the Application Server1. Start the server for the new profile, launch the Administrative Console, and login.

On Windows platforms, you can start the profile server and launch the AdministrativeConsole from the Start menu, for example, in a default installation:

To start the server, click Start > All Programs > IBM WebSphere > Application Serverv7.0 > Profiles > AppSvr01 > Start the server.

To launch the Administrative Console, click Start > All Programs > IBM WebSphere >Application Server v7.0 > Profiles > AppSvr01 > Administrative Console.

If you enabled Administrative Security when you created the profile for this server, you willneed to login using the user name and password you specified at that time.

When the Administrative Console is launched, it displays the Welcome screen forWebSpheres Integrated Solution Console:

14


2. Click the link WebSphere Application Server to display the Welcome page for theApplication Server:

Set JVM Requirements

Setting Memory Parameters

Set these memory parameters as described below:

Initial Heap Size: 1024

Maximum Heap Size: 2048

If your application server is using the Sun JVM, add the PermSize and MaxPermSize settings aswell:

PermSize: 64

MaxPermSize: 384

15


Follow these steps to set these parameters.

1. 1. In the Administrative window, on the left side of the screen, click Servers > ServerTypes > Websphere application servers.

2. Find the name of the server on which Process Commander will run, and click that servername. (In the example above, the server is server1.) The Configuration tab for that serverappears.

16


17


3. In the Server Infrastructure section, click the + next to Java and ProcessManagement to expand the section, then click Process Definition.

You may need to scroll down in the window to see the Server Infrastructure section.

This displays the Configuration tab for Process Definition.

4. In the Additional Properties section, click Java Virtual Machine. This displays the

18


Configuration tab for the Java Virtual Machine.

19


5. On this window set:

- Initial Heap Size to 1024

20


- Maximum Heap Size to at least 2048

Note: These values are initial minimum estimates for typical development systems. They may needto be higher based on your server hardware and the number of other applications on the server.Consult with your System Administrator about the requirements for your site.

6. If your WebSphere instance is using the Sun JVM, in the Generic JVM Arguments fieldset a PermSize of 64MB and a MaxPermSize of 384MB by entering:

-XX:PermSize=64m -XX:MaxPermSize=256m

Separate the JVM Arguments with a space . Do not use commas.

Note: These settings are minimum settings only. They may need to be higher based on your serverhardware and the number of other applications on the server.

7. Click Apply. A message appears at the top of the screen explaining that the changes weremade.

8. Click Save to save these changes to the master configuration.

Enable AWT to support PRPC Graphs

This setting enables the server to render graphics used by the PRPCgraphical reports.

1. From the Application Servers > server1 > Process Definition page, underAdditional Properties, select Java Virtual Machine to return to the Configuration page.

2. In the Generic JVM Arguments field, enter the following system property JVM argument:

-Djava.awt.headless=true

For example,

21


Note: Separate this argument from any others in the field with a space. Do not use commas.

3. Click Apply.

4. In the Messages section at the top of the page, click Save.

Create URL ProvidersFollow the procedure below to set the required URL Pega reference and an explicit Temporary directoryfor Process Commander. The temporary directory is used by Process Commander to store static data. Itis important that the directory be properly specified and accessible to the Process Commander user. InWebSphere you specify this directory as a JNDI reference to a URL object.

1. In the WebSphere Administration console select Resources > URL > URL Providers inthe left frame.

2. Set the Scope level appropriate to your deployment, and click on the Default URLProvider link. In the following example, the scope is set to the server level.

22


3. Under the Additional Properties section, click on the URLs link to display the URLs listingpage:

23


4. Click New to display the Configuration page:

24


5. Define a URL for the NULL file that Process Commander can use to discard erroneouserrormessages Complete this form as follows:

In the Name field, enter PRPCnone

In the JNDI name field, enter url/pega/none

In the Specification field, enter file:///nul for Windows or file:///dev/null forUNIX/Linux.

6. Click OK and then Save in the confirmation message.

7. From the URLs page, click New again to return to the Configuration page.

8. Complete this form to create a URL specification for a temporary directory that ProcessCommander can use to store static data:

In the Name field, enter PegaTempDir

In the JNDI field, enter url/initialization/explicittempdir

In the specification field, enter file:/// followed by the full path to the temporarydirectory. Enter the path using forward slashes for both Windows and UNIX platforms. Forexample, on Windows the value might be: file:///D:/Temp/PegaTempDir.

25


Important: The directory names you enter here are case sensitive. Be sure to enter the names ofthe directories exactly as they have been created on your system.

Notes: If the directory you specify does not exist, Process Commander will attempt to allocate it. Itis good practice to allocate the directory on the system before specifying it here.

The user that owns the Java process must have the appropriate permissions to use this directory,including write access. In particular, if you have J2 security enabled, ensure that this directory isaccessible under your security policy.

In a clustered deployment, each Process Commander instance must have its own temporarydirectory. You cannot share a temporary directory with more than one Process Commanderinstance.

9. Click OK and then Save in the confirmation message.

26


Create JDBC ResourcesCreate a JDBC provider

1. In the Administrative console, click Resources > JDBC > JDBC Providers to display theJDBC Providers page:

2. In the Scopes dropdown, choose the scope level appropriate to your deployment, and clickNew to display the JDBC provider wizard:

27


Note: The screen shots in this section show the settings for an Oracle database. If you are not usingOracle, follow the instructions for each step to configure the JDBC provider for your database,replacing the Oracle settings shown in the screen shots with the appropriate information for yourdatabase.

3. Complete the fields in Step 1 as follows:

In the Database type dropdown,select Oracle .

In the Provider type dropdown, choose Oracle JDBC Driver.

In the Implementation type dropdown, select Connection pool data source.

In the Name and Description fields, accept the defaults or enter a descriptive nameand explanatory description for the driver you selected.

Click Next to display Step 2:

28


4. In the Directory location field, confirm the entry, if one is displayed, or enter the path tothe driver class file or files listed in the Class path field.




Note: Be sure only the appropriate JAR file is loaded. Do not put both sqljdbc.jar and sqljdbc4.jar inthe classpath.

Click Next to display Step 3.

29


5. Confirm that the settings are correct, and click Finish.

You are returned to the JDBC Providers page.

30


6. Click Save in the confirmation message.

Create Data Source

1. Still on the JDBC providers page, click on the name of the provider you just created todisplay the General Properties page.

31


2. Under the Additional Properties heading, click Data Sources.

32


10. Click New to display the data source wizard:

33


34


3. Click New to display the data source wizard:

In the Data Source name field, enter PegaRULES

In the JNDI name field, enter jdbc/PegaRULES.


35


4. Supply information about your Process Commander database.

Specify a URL for the Type 4 (thin client) JDBC driver, for example,jdbc:oracle:thin:@myServer:1521:myDatabase, where myServer is the DB servername, 1521 is the port number it is using for communication, andmyDatabase is thedatabase name.

In Data store helper class name, specify the Oracle 10g data store helper.

36


If you are unsure about the information to supply for your database server, consult withyour site DBA.


5. Click Next to display the Summary page. (You will supply DB credentials in a later step):

37


6. On the Summary page, confirm that the settings are correct and click Finish.

You are returned to the JDBC Providers page.

38


7. Click Save in the confirmation message.

8. Still on the Data Sources page, click the PegaRULES link in the Name column to open theConfiguration page for this data source. Then, under Additional Properties, click on theCustom Properties link to display the Custom Properties page:

39


9. Click New to define any additional properties you may need for your database connectionhere.

40


To create a new property, click New on the Custom Properties form. After creating eachproperty, click OK to save the property, and New again to create the next property. Besure to set the Type field appropriately for the Value of the connection property.

If you are using the Oracle ojdbc5 driver, PRPC requires the following property:

Name: connectionProperties Value: oracle.jdbc.V8Compatible=true

This property is not needed with Java 6 and the ojdbc6.jar driver.

10. After you have set the necessary properties, click the Save link in the message at the topof the page.

Define Database Authentication Credentials

1. In the link path at the top of the page, click PegaRULES to return to the PegaRulesproperties page. Then, under the Related Items section, click the link JAAS J2Cauthentication data. You will define your database authentication credentials here.

41


2. Click New to specify the General Properties.

3. Complete this form as follows:

In the Alias field enter any name that uniquely identifies this J2C entry.

In the User ID and Password fields, enter the user name and password for the PRPCdatabase user on your Process Commander database.

4. Click OK to return to the authentication data entries page, and click Save in the Messages

42


section at the top of the page.

5. In the link path at the top of the page, again click PegaRULES to return to the PegaRulesproperties page.

6. In the Security Settings section near the bottom of the page, use the Component-managed authentication alias dropdown to select the J2C alias you just created:

43


7. Click Ok, and then Save in the confirmation message on the Data sources page.

8. On the Data sources page,select the checkbox for PegaRULES and click Test Connectionto confirm your data source configuration.

Configure WebSphere WorkManagerIf you are deploying Process Commanders EAR archive, prpc_j2ee14_ws.ear, complete the followingprocedures to define a WorkManager. Process Commander uses the WorkManager to run asynchronoustasks to support internal components such as agents, services, daemons, and child-requestors.

If you are deploying Process Commanders WAR archive, prweb.war, you do not need to configure theWorkManger. Continue with the configuration procedure, Other WebSphere Configuration on page 46.

Complete the following procedures to define the WorkManager:

44


1. In the navigation menus on the left of the Administration Console, expand Resources,expand Asynchronous Beans, and selectWork Managers

2. On the Work Managers listing page, set the Scope to the level appropriate for yourdeployment, and click New.

45


3. Complete the Configuration page for the Work Manager as follows:

In the Name field, enter a name to identify this Work Manager, for example,PRPCWorkManager.

46


In the JNDI name field, enter exactly the JNDI locationwm/PegaWorkManager

In the Service names section, select the Security checkbox.

In Thread pool properties, setMaximum number of threads to 5.

Uncheck the Growable checkbox.

4. Click OK.

You are returned to the Work Managers listing page.

5. In the Messages box at the top of the page, click Save.

Set HTTP transport channel custom property CookiesConfigureNoCache tofalse

In order to support the ability to open files attached to work objects in Process Commander, you mustset a custom property, CookiesConfigureNoCache, on the transport chain in the Web Container settingsfor the Process Commander server.

Note: In earlier versions of WebSphere, this property was set to false so that cookies could be cached by default.Process Commander requires this caching to allow users to open attached files directly from a work object. InWebSphere 7.0, this property is set to True by default so that caching is not allowed. You must create and set thisproperty on the HTTP transport channel for the Process Commander server.

Complete the following steps to set this property.

1. In the administrative console, select Servers > Server Types > WebSphereapplication servers to display the Application servers page.

2. Click on the name of your Process Commander server to display the Configuration page:

47


3. Under Container Settings, expandWeb Container Settings, and then clickWebContainer transport chains.

This console displays the listing page for transport chains

48


4. Click the name of the appropriate transport chain:

If your site is using the default transport configuration for this server, selectWCInboundDefault or, if you have enabled SSL for the Process Commander port,WCInboundDefaultSecure.

If your site has defined a custom transport chain for this server, select that chain name

The console displays the Configuration page for the selected transport chain.

49


5. Under Transport Channels on this page, click HTTP inbound channel.

The console displays the Configuration page for the selected transport channel.

50


6. Under Additional Properties on this page, click Custom Properties.

The console displays the listing page for this channels custom properties

51


7. Click New

The console displays the form for a new custom property

8. Complete this form as follows

In the Name field, enter CookiesConfigureNoCache

In the Value field, enter False.

9. Click OK, and then Save in the Messages box on the Custom Properties listing page

Deploy the PegaRULES core applicationComplete the instructions below to deploy the PRPC core application component prpc_j2ee14_ws.ear.

Important: The PRPC core application component is available both as aWAR file, prweb.war, or an EAR file, prpc_j2ee14_ws.ear. Pegasystems recommends deploying the EAR file component, prpc_j2ee14_ws.ear for all newdeployments on WebSphere 7.0 systems. The WAR file core component, prweb.war, can be successfully deployedon the WebSphere application servers, but deploying and configuring the EAR file ensures that you can addadvanced J2EE features as your application grows or when you migrate to a production environment.

Do not install both prweb.war and prpc_j2ee14_ws.ear.

52


Note:WebSphere automatically starts the application, prweb.war or prpc_j2ee14_ws.ear, when it is deployed.When the application starts up, you may see error messages for missing resources and references. You may ignorethese messages. You will supply these resources as you complete the installation process. Be sure to stop theapplication after deploying.

Deploying prpc_j2ee14_ws.ear in WebSphere

1. Ensure that the WebSphere Application Server is running, and log into the administrationconsole

2. Under the left frame, select Applications > New Application

3. Click New Enterprise Application.

53


4. Click the Browse button and navigate to select prpc_j2ee14_ws.ear from your installationmedia. Click Next.

WebSphere displays Preparing for the application installation

5. Click the radio button: Detailed - Show me all installation options and parameters

This option will allow you to review all the installation options for the application, includingthe default bindings and resource mappings

6. Click the + sign to expand Choose to generate default bindings and mappings

54


7. Complete this page as follows

Check Generate Default Bindings

Check Use default virtual host name for Web and SIP modules.

Accept the other defaults and click Next:

WebSphere displays the following Security Warning

55


8. Scroll to the bottom on this page and click Continue

This security file allows Process Commander to run when J2EE Security Checking isenabled.

WebSphere displays a wizard in which you can specify installation options

56


57


This section of the installation process is a series of steps under the general heading ofInstall New Application. For Process Commander, you only need to make changes inStep 10, Map resource references to resources. For each of the other screens, youmay accept the defaults, or customize them according to the requirements of yourorganization.

9. For Step One, accept the defaults and click Next

10. Continue through the next steps, either accepting the defaults, or customizing for yourorganization, as needed.

In Step 10, you map resource references to resources

58


59


11. For the three Resource references to url/initialization/explicittempdir, enter the JNDIname url/initialization/explicittempdir in the field Target Resource JNDI Name.

There are url/initialization/explicittempdir references for the EJB EngineCMT, EngineBMTand prweb.war.

This maps the location you specified in the URL provider you created above to thecorresponding Resource Reference in the application, so that the application will use thelocation for the PegaTempDir.

12. Click Next

Depending on your configuration, you may see a set of warnings related to missingresource references, for example:

These are resource references that are defined in web.xml, the deployment configurationfiles for the application, but not mapped to resource definitions in your application. In thepage, Map resources to references, they are mapped to the Target Resource JNDI Nameurl/pega/none, indicating that they are not used. Pegasystems provides these referencesfor J2EE compliance, but their use is optional. You can continue with the deployment.

13. At the bottom of the Warnings page, click Continue.

14. Continue through the remaining steps, accepting the defaults, or setting them to therequirements of your organization.

60


15. The system begins installing the EAR file, which may take a few minutes. The followingmessage is displayed.

61


When the installation completes successfully, WebSphere displays a message similar to thefollowing:

16. Click Save directly to the master configuration.

Installing the System Management and Online Help ApplicationsIn addition to the Process Commander application, you must also deploy the online help application(prhelp.war) and System Management application (prsysmgmt.war).

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

Complete the following steps to deploy prsysmgmt.war or prsysgmgt.ear.

62


1. Under the left frame, select Applications > New Application.

2. Click New Enterprise Application.

3. Click the Browse button and navigate to select the application war file, prsysmgmt.war orprsysgmgmt.ear, from your installation media.

4. Click Next to begin the installation:

63


5. Click the radio button: Detailed - Show all installation options and parameters.

6. Click the + sign to expand Choose to generate default bindings and mappings:

7. Select the Generate Default Bindings check box, and leave the other settings at theirdefaults.

8. Click Next.

64


You may see some security warnings similar to the following:

9. Click Continue to pass by the warnings.

WebSphere displays the Install New Application wizard:

65


10. Accept the defaults and click Next for Steps 1 through 7.

11. In Step 8, enter the name of the file, prsysmgmt or prhelp, as the context root, and clickNext.

66


12. On the Summary page, click Finish.

67


WebSphere displays a message, Installing . . ., and updates it with information during theinstall. When complete the following message is displayed in the page:

13. Click the Save link to save the changes to the master configuration.

68


You are returned to the first page of the installation series:

14. Deploy prhelp.war using the same procedure as prsysmgmt.war

Use the name of the file, prhelp, as the context root and deploy to the same server.

Assigning the PegaDiagnosticUser Role to your SystemManagement Application UsersUsers accessing the System Management Application (SMA) in Process Commander must be assignedthe role PegaDiagnosticUser. Users can access the SMA in the Process Commander Developer portal byclicking Tools > System Management Application. If the user does not have this role they will bechallenged for authentication when they attempt to access the System Management Application fromProcess Commander.

You can use the SMA to monitor and control caches, agents, requestors, listeners, and other processingin the Process Commander system. For more information, consult the System Management ApplicationReference Guide available on the Pega Developer Network (pdn.pega.com).

Complete the following steps to set access to the System Management Application.

If you want to allow limited access to the SMA, use the Map Special Subjects dropdown toselect All Authenticated in Applications Realm, or click Map Users . . . to assign the role tospecific users.

69


1. Select Applications > Application Types > WebSphere enterprise applications.

2. Click the name of your Process Commander core application, for example prpc_j2ee14_ws,to open the Configuration page.

70


3. In the Detail Properties section, click Security role to user/group mapping.

If you installed the EAR archive, prpc_j2ee14_ws.ear, the PegaDiagnostic role is set toEveryone:

If you installed the WAR archive, prweb.war, the PegaDiagnosticUser role is set toNone:

4. Select PegaDiagnosticUser and set the proper access level for your site:

If you do not want to allow access to the SMA, use the Map Special Subjectsdropdown to select None.

If you want to allow limited access to the SMA, use the Map Special Subjectsdropdown to select All Authenticated in Applications Realm, or click MapUsers . . . to assign the role to specific users.

71


If you want to allow open access to the SMA, use the Map Special Subjectsdropdown to select Everyone.

Next StepsIf 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 you just deployed are notstarted.

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

72


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.3 distribution also includes scripts to support thesetasks through a command-line interface. Support is provided through install.bat and install.ksh files configuredthrough a properties file, setupDatabase.properties. To use the scripted option, see the README.txt file in 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 a Java 5 JDK of 1.5.0_07 or higher, or a Java 6 JDK. The Java 7 JDK is notyet supported with Process Commander 6.3.

Move the Process Commander Software Distribution to Your ComputerIf you are installing the software distribution downloaded from Pegasystems, copy the distributionfile, for example 113990_prpc63.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:

73


Update Java 6 JDK to JAX-WS API 2.2.5If you are using the Java 6 JDK, you must update the JDK environment to use version 2.2.5 or later ofthe JAX-WS API. The JAX-WS API (jaxws-api.jar) bundled with the Java 6 JDK is version 2.0. ProcessCommander requires at least JAX-WS version 2.2.5 to support its implementation of CMIS integrationand WS-Security.

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 and resolver.jarto the /lib/endorsed directory on your application server. Create the endorseddirectory in the lib directory if one 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.

74


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

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

75


2. Click Next to display the Performance Considerations

Review these items to be sure that your system is prepared to allow the installation toperform efficiently. In particular, network connectivity and database maintenance issuescan significantly increase the time required to load the 6.3 Rulebase into your PRPCdatabase.

3. Click Next to display the Environment Considerations.

76


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

4. Click Next to display the Database Preparation page.

77


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, besure the database operator used during installation has the create procedure permissionexplicitly granted.

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

78


6. 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.

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

79


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

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

80


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

81


10. Complete this page as follows:

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 that

82


Click Next to display the Database Connection page.

Specify the location of the driver JAR file, the database connection URL, and the database username and password.

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: oracle.jdbc.OracleDriver

Driver JAR file

Enter the full path to the driver file.


83




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

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

Database JDBC URL

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

Oracle 10g/11g (Native OCI Client): jdbc:oracle:oci:@your_tns_name

Oracle 10g/11g (Thin Client): jdbc:oracle:thin:@yourServer:1521:yourDatabase

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, be sure thedatabase operator used during installation has the create procedure permission explicitlygranted.

2. 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:

Click OK to close the window.

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

84


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

3. 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.

85


4. 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:

86


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

87


The Assistant displays the following window when complete:

88


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\oracledate\util directory inthe Process Commander software distribution, for example:

C:\PRPC_distribution\schema\oracledate\util\oracledate_drop_Version Number infilenames.sql

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

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

89


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

90


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://://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 Whats Happeningsection of thepage:

91

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 Whats Happening message.

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

92


Enable Developer Help and the System Management ApplicationTo 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

93


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 SettingsSearch 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.

94


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

95


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.

96


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.

97


IntroductionCheck the Pega Developer Network for the Latest InformationPegasystems DocumentationDeployment information and updatesPegasystems Training

Overview of the Installation Procedure1. Preparation Phase2. Rulebase Setup Phase3. PRPC Configuration Phase

Notes for Users of Earlier Process Commander VersionsOptional: Move System Settings from Configuration Files to Database

Step1. Environment ConsiderationsPrerequisitesProcess Commander Deployment ArchitectureProcess Commander Core Component VersionsSupported Process Commander Platforms

Step 2. Database Preparation -Database PrerequisitesCreate the Process Commander DatabaseCreate Database UsersCreating Base and Admin Database UsersHow Process Commander Uses the two Database Accounts

Create the Schema in Process Commander DatabaseUsing a SQL Script to Create the Schema

Next Steps

Step 3: Application Server PreparationVerify the Java EnvironmentConfigure Support for the Process Commander DatabaseCreate a WebSphere Profile

Start and Configure the Application ServerSet JVM RequirementsCreate URL Providers

Create JDBC ResourcesCreate a JDBC providerCreate Data SourceConfigure WebSphere WorkManagerSet HTTP transport channel custom property CookiesConfigureNoCache to false

Deploy the PegaRULES core applicationDeploying prpc_j2ee14_ws.ear in WebSphere

Installing the System Management and Online Help ApplicationsAssigning the PegaDiagnosticUser Role to your System Management Application U...Next Steps

Steps 4 to 9 - Rulebase SetupInstall the Process Commander Schema and Rules in the DatabaseMove the Process Commander Software Distribution to Your ComputerUpdate Java 6 JDK to JAX-WS API 2.2.5

Rulebase Setup Using the Installation and Upgrade Assistant

Step 10 - Final Settings in Process CommanderStart and Login to Process CommanderConfigure Process CommanderEnable Developer Help and the System Management ApplicationOptionally Set Search Index Host Node SettingsCreate an Organization

Change the password for [email protected] Solution Frameworks

Documents

PRPC63 Install WAS7Oracle