Prpc715 Install Wasora

PegaRULES Process
Commmander Installation
Guide
Version: 7.1.5
Database: Oracle
Application Server:WebSphere
Copyright 2014
Pegasystems Inc., Cambridge, MA
All rights reserved.
This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary
information. The document and product are protected by copyright and distributed under licenses restricting their use,
copying distribution, or transmittal in any form without prior written authorization of Pegasystems Inc.
This document is current as of the date of publication only. Changes in the document may be made from time to time at the
discretion of Pegasystems. This document remains the property of Pegasystems and must be returned to it upon request.
This document does not imply any commitment to offer or deliver the products or services described.
This document may include references to Pegasystems product features that have not been licensed by your company. If
you have questions about whether a particular capability is included in your installation, please consult your Pegasystems
service consultant.
For Pegasystems trademarks and registered trademarks, all rights reserved. Other brand or product names are trademarks
of their respective holders.
Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or
typographical errors. This document or Help System could contain technical inaccuracies or 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.
One Rogers Street
Cambridge, MA 02142-1209
Phone: (617) 374-9600

Fax: (617) 374-9620
www.pega.com
Document: PegaRULES Process Commmander Installation Guide

Software Version: 7.1.5
Updated: Tuesday, April 29, 2014
Contents
About This Guide
Intended Audience
Documentation Resources
Platform Support Guide
Installation, Upgrade and Deployment Documentation
Installation Overview
Planning Your Install
Product mode
Automatic or manual DDL application
Split Schema
Optional database user for schema changes
Installation Prerequisites
PRPC Architecture
Database Server Setup
Database Prerequisites
Database Preparation
Database Configuration
10
Create the Database
10
Create the Tablespaces
14
Create Users
17
Optional: Manually Generate and Apply DDL
20
Installing the Rulebase
22
Rulebase Prerequisites
22
System Requirements
22
Running the Installation and Upgrade Assistant
23
Running the Command Line Script
30
Completing the Rulebase Installation
31
Application Server Setup
33
Application Server Prerequisites
33
Application Server Preparation
33
Include WebSphere Default Packages
33
Create a WebSphere Profile
PegaRULES Process Commmander Installation Guide
34
Configure the Application Server
34
Set JVM Properties
35
Create URL Providers
37
Create a JDBC provider
41
Configure Data Source Connection
44
Configure WebSphere Data Source Connections
52
Configure WebSphere WorkManager
53
Set HTTP transport channel custom property
56
Configure JNDI for Split-Schema
61
Deploying PRPC Application Archives
65
Deploy the PRPC Application (prpc_j2ee14_ws.ear)
65
Deploy the System Management and Online Help Applications
74
Assign the PegaDiagnosticUser Role
81
Login to PRPC
83
Post Deployment Configuration
85
Enable Help and System Management Applications
85
Configure Directed Web Access
85
Configure Search Index Host Node Settings
86
Change the Administrator Password
86
Install Solution Frameworks
86
About This Guide

This guide describes how to install a new instance of PegaRULES Process Commander (PRPC) 7.1.5 on an
Oracle 12c database and a WebSphere 8.5 application server.
It does not describe how to perform an upgrade to an existing PRPC instance. That information is in the
PRPC 7.1.5 Upgrade Guide.
Intended Audience
This guide is intended for anyone involved in the planning and installation of PRPC 7.1.5 including
resources that manage and administer your Oracle database and WebSphere application server.
Documentation Resources
A variety of documentation and online resources are available to help you with your installation and
deployment process.
The Pega Discovery Network (PDN) is Pegasystems' online documentation and information site. It is the
central depository for the review and download of updates to this guide and other installation and
deployment documentation.
To access the latest installation and deployment information, navigate to
https://pdn.pega.com/resources/deployment-guides.
Platform Support Guide
Included with your distribution media and published on the PDN, the 7.1 Platform Support Guide lists the
databases and application servers supported for the 7.1.5 release.
It is important that you review this document before installing PRPC to verify that you are installing on
supported versions of your database and application server. To access the latest Platform Support Guide,
click the Resources tab on the PDN and click the link under PRPC Deployment.
Installation, Upgrade and Deployment Documentation
7.1.5 release notes, deployment information and the latest versions of the installation and upgrade
guides are available for review and download from the PDN.
Installation Overview
Installing PPRC 7.1.5 is a multi-step process that involves configuring your database and application
server, loading rules into the database, and then deploying application archives to the application server.
Prior to installing PRPC:
n
n
See the Platform Support Guide for a list of supported versions.

Review the Planning Your Install topic in this section. This is particularly important when planning
for enterprise-scale systems with multiple nodes and/or environments.
This install guide is organized to expedite the installation process. It can be summarized in the following
install steps that are typically performed in sequence.
1. Configure the database
2. Load the rulebase
3. Configure the application server
4. Deploy PRPC archives
5. Configure PRPC
Some organizations follow specific governance procedures for the allocation and use of IT infrastructure,
including databases and application servers. If your organization has special teams for managing
databases and application servers, these resources should be engaged as early in the planning process as
possible. PRPC supports different deployment topologies and configuration options which impact how the
supporting infrastructure is configured and managed going forward.
Your PRPC distribution package contains a significant number of rules which are loaded into the database
using one of two methods:
n
Installation and Upgrade Assistant (IUA) The IUA is a graphical installer tool that guides
you through the installation process. It is a Java swing application that can be run on both Windows
and Unix systems. This tool requires Java 6 or 7.
Command Line Scripts are provided for both Windows and Unix that allow installation on
headless (non-UI) environments and/or environments that require a scripted, repeatable process
for installation. This tool requires Java 6 or 7.
Both installation methods use a batch process to load the rulebase. Due to the magnitude of rules and
other data objects which must be loaded, Pegasystems strongly encourages you to run the installer on
the same machine as the database server. If this is not possible, run the installer on a machine with fast
direct access to the database server. Do not attempt to run the installer on a virtual private network
(VPN) or a multi-hop wide area network (WAN).
Planning Your Install

PRPC 7.1.5 supports a new runtime mode and a variety of deployment topologies that can impact the
choices you make at different stages of the installation process. Before installing PRPC, consider the
following:
Product mode
PRPC 7.1.5 introduces support for a new runtime mode Multitenancy. The Multitenancy mode has
different installation requirements, different runtime behaviors and different administrative procedures.
This mode should not be selected without reviewing the Multitenancy Administration Guide which
discusses this mode in detail. It is included in your distribution package and available on the PDN.
Automatic or manual DDL application
The installer is designed to automatically render and apply schema Data Definition Language (DDL) to
your database. Optionally, DDL may be manually rendered via a command-line script and then applied
using native or 3rd party tools.
If you intend to manually apply the DDL, do this prior to running the installer.
Split Schema
In 7.1.5, PRPC supports a split schema database configuration. In a split configuration, Rules and Data
(including Work) are maintained in two schema. This configuration is required when using Pega 7's High
Availability features and is generally recommended for organizations requiring minimal downtime when
upgrading PRPC.
Optional database user for schema changes

PRPC supports the use of an optional database account that is preferentially used by specific PRPC
features that modify the schema structure. This configuration provides greater auditability and control of
schema changes, but requires:
n
the configuration of an additional database user account
the configuration of a dedicated connection pool in the application server
The use of a second database user is supported for both single and split-schema configurations.
Installation Prerequisites
The prerequisites for installing PRPC are:
Application Server
l
WebSphere Application Server. See the Platform Support Guide for a list of supported versions.
A minimum of 2 GB memory
l
PRPC web applications require a minimum of 2GB of memory to operate, although your
particular memory requirements may be higher depending on the number of users and your
specific configuration
A minimum of 200 MB of disk space

l
Make sure that you allocate enough storage to accommodate debugging and other logging
requirements. In general, ensure that your logging configuration is such that logs are not
written to the same directory as the application server runtime components.
Database Server
l
Oracle relational database. See the Platform Support Guide for a list of supported versions.
A minimum of 5 GB storage
l
The data schema that contains the PRPC work objects should be allowed to grow to
accommodate the page of work creation.
Database and application server time zone and character encoding

Configure your database server and app server to use the same time zone and character encoding to
avoid conflicts.
PRPC Architecture
PRPC is a Java EE-compliant enterprise application that requires two main subsystems for its operation
an application server and a database server.
l
The application server hosts PRPCs application archives and also provides interconnectivity to
other systems through various protocols.
The database server stores the rules, data and work objects used and generated by PRPC.
Application users and developers typically access PRPC through a web browser. Applications may also
expose HTTP-based services (e.g. SOAP, REST or HTTP) for purposes of administration or process
automation in a headless environment.
Database Server Setup

This section lists the database prerequisites and describes how to create user accounts, the database and
database schema for your PRPC install.
Database Prerequisites
Before you configure your database, see the Platform Support Guide for a list of supported versions for
your database.
n
Oracle server is installed and running.
Java is enabled in the database.
If you are using Oracle 11g, do not use the UCP (Universal Connection Pool) feature in your PRPC
database. An Oracle bug (BUG 8462305) causes a failure when an application tries to call a stored
procedure causing PRPC to work incorrectly with a database that uses UCP.
Private synonyms are not in use as they may conflict with the PRPC installer and cause installation
errors.
Database Preparation
Database preparation and configuration depends on three primary considerations.
1. Single vs. Split Schema
2. Base vs. Admin User
3. DDL application
Single vs. Split Schema

It is possible to configure PRPC 7.1 to access two schemas.
n
a Rules schema, which contains the PRPC rulebase
a Data schema, which contains both Data and Work instances
When possible, Pegasystems recommends the use of a split configuration particularly in critical software
development life-cycle (SDLC) environments such as QA, STAGE and PROD.
A split-schema configuration is required to support PRPCs High Availability features, namely rolling
upgrade.
In Oracle, schema are defined concurrently with the creation of a user. Therefore, a split-schema
configuration requires the establishment of two users, generally referred to as the Rules user and the
Data user. These users may be associated with individual tablespaces or a common tablespace.
Pegasystems recommends separate tablespaces per user for critical SDLC environments.
Database User Accounts

Oracle databases require a Deployment user with the DBA role just for PRPCinstallation or upgrade.
This user can be removed after installation or upgrade is complete. This is due to the unique nature of
Oracle to associate schemas with user accounts.For split schema environments, you will create a Rules
and Data schema, which will create associated user accounts. PRPCuses the Deployment user to
assign privileges to the Rules and Data users.
PRPC minimally requires one Base database user account which is used by the application server for
normal runtime operation. The default schema for base users should be the data schema. If possible, it is
best to use a single Base database account for all PRPC operations. However, PRPC is designed to
accommodate an additional Admin user account which is preferentially used by certain PRPC features
which modify the database schema.
To configure PRPC to use an Admin account, create the account in the database with the appropriate
permissions, then configure a second JDBC data source in the application server using the new database
account. With a Base + Admin user configuration, the Admin user is granted full privileges, while the
Base user is granted a smaller subset.
For most runtime operations, PRPC will use the Base data source and user. If one of the features
below is used, PRPC will choose the Admin data source and user.
Features requiring Admin account

The following features are preferentially accessed by the Admin account if two database accounts are
configured.
n
Schema Change Tracking tool System > Database > Schema Change Tracking
Optimize Schema tool System > Database > Optimize Schema
Modify Schema wizard System > Database > Modify Schema
Import wizard Application > Distribution > Import
Property optimization See the PDN article How to expose a property as a database column with
the Property Optimization tool
Creating any new Circumstance Definition rule or defining a single circumstance on a rule. The
extended permissions are needed to support reporting on circumstanced properties. See the PDN
article How to create a rule with multiple circumstance properties.
DDL Generation
The PRPC 7.1.5 installer is designed to automatically generate and apply the DDL. The DDL must be in
place before the installer can load the Rulebase you must create the schema objects (tables, indexes,
view, triggers and procedures) required by PRPC. This can be done in one of two ways:
n
Automatically You can use the Installation and Upgrade Assistant (IUA) to automatically tender
and apply the schema DDL for your platform. See the Running the Installation and Upgrade
Assistant section for details.
Manually If you prefer to inspect and/or manually apply the DDL, you can use the
generateddl.bat/.sh script packaged with your distribution. This tool automatically renders the
platform-specific DDL and writes the output to a file. You can then view and edit the file or directly
apply it using any number of native or 3rd party database management tools. For instructions for
using the file see the topic Optional: Manually Generate and Apply DDL.
Database Configuration
To prepare your Oracle database server for use with 7.1.5, complete the following steps.
n
Create the database
Create the tablespaces
Create users
Optional: Manually generate and apply DDL
Create the Database

Use the Database Configuration Assistant to create the database. The Assistant provides a guided
approach to common database management operations, including database creation and deletion.
10
1. Select Create Database and click Next>.
The Creation Mode screen displays.
11
Complete the following fields:

Global Database Name
Administrative Password
Confirm Password
"oracle" Password
Uncheck the Create as Container Database box
2. Click Next>.
The Assistant will run Pre Requisite Checks and, if passed, automatically progresses to the
Summary screen.
12
If desired, copy and paste the summary information to a safe location.

3. Click Finish to complete the Assistant and begin database creation.
It typically takes 5-10 minutes to create the database.

4. When database creation is complete, copy the value of the EM Database Express URL to a safe
13
location.
5. Click Exit to close the Assistant.
Create the Tablespaces
1. Log into the Enterprise Manager using the URL that was provided by the Database Configuration
Assistant. The URL is usually in the form of
https://<host>:5501/em
The Enterprise Manager login screen displays.
2. Enter the User Name and Password for the sys operator. Click Login.
User Name = sys
Password = <password>
The Enterprise Manager home screen displays.
14
3. Select Storage > Tablespaces.

The Tablespaces screen displays.
4. Select Actions > Create.
15
The Tablespace Creation Wizard displays. This provides a guided approach to configuring the
tablespace.
In the Name field, enter the name of the tablespace.

5. Click
The Add Datafiles screen displays.
Increase the values of the File Size to 5000M.

Accept the other defaults.
6. Click OK. The tool will automatically generate and execute the SQL.
16
If you are installing 7.1 in a split-schema configuration and wish to maintain Rule and Data
schema in separate tablespace, re-run the Create Tablespace wizard choosing the appropriate
values for the Data Tablespace.
In order to install PRPC, you must configure the Rules tablespace with a 5 GB datafile. The initial
7.1 rulebase consumes 4+ GB of space. If defined, the Data tablespace should be configured based
on a site-dependent analysis of how PRPC and any associated frameworks and/or applications will
be used in the environment.
Create Users
1. Log into the Enterprise Manager.
2. Select Security > Users.
The Users screen displays.
3. Select Actions > Create User.

The Create User wizard displays. This provides a guided approach to creating users and assigning
privileges.
17
On the User Account step, enter the Name and Password for the wizard.
4. Click
The Tablespaces step displays.
If you created a dedicated tablespace, choose that tablespace from the dropdown menu.
5. Click
The Privilege step displays.
18
Add the appropriate user privileges based on the table below. To use this table. find the row that
matches your configuration based on the values in the first two columns.
Split
Admin
Admin User
schema? User?
No
No
Yes
Base User
Data User
Rules User
No
N/A
CREATE
CREATE
CREATE
CREATE
CREATE
CREATE
Yes
CREATE SESSION
CREATE ANY TABLE
ALTER ANY TABLE
INSERT ANY TABLE
SELECT ANY TABLE
UPDATE ANY TABLE
DELETE ANY TABLE
CREATE ANY INDEX
CREATE ANY PROCEDURE
EXECUTE ANY PROCEDURE
CREATE ANY VIEW
CREATE ANY TYPE
CREATE ANY TRIGGER
ALTER ANY TRIGGER
GRANT ANY OBJECT PRIVILEGE
DROP ANY TRIGGER
DROP ANY TABLE
DROP ANY PROCEDURE
DROP ANY VIEW
DROP ANY INDEX
CREATE SESSION
UNLIMITED TABLESPACE UNLIMITED TABLESPACE
N/A
CREATE SESSION
UNLIMITED TABLESPACE
UNLIMITED TABLESPACE
Yes
CREATE SESSION
CREATE ANY TABLE
ALTER ANY TABLE
INSERT ANY TABLE WITH ADMIN
OPTION
SELECT ANY TABLE
UPDATE ANY TABLE
DELETE ANY TABLE
CREATE ANY INDEX
CREATE ANY PROCEDURE
19
SESSION
TABLE
PROCEDURE
UNLIMITED TABLESPACE UNLIMITED TABLESPACE
VIEW
TYPE
TRIGGER
Split
Admin
Admin User
schema? User?
Base User
Data User
Rules User
EXECUTE ANY PROCEDURE

CREATE ANY VIEW
CREATE ANY TYPE
CREATE ANY TRIGGER
ALTER ANY TRIGGER
GRANT ANY OBJECT PRIVILEGE
DROP ANY PROCEDURE
DROP ANY TRIGGER
DROP ANY TABLE
DROP ANY VIEW
DROP ANY INDEX
6. Click OK when you finish adding the permissions.

7. For a split schema configuration, repeat the steps to configure the Data user.
At this point, the database should be properly configured to load the Rulebase using the PRPC Installer
unless you plan to manually generate and apply DDL.
Optional: Manually Generate and Apply DDL
A generateddl script is provided for Windows (generateddl.bat) and Linux (generateddl.sh). This tool
automatically renders the platform-specific DDL and writes the output to a file. You can then view and
edit the file or directly apply it using any number of native or 3rd party database management tools. Both
scripts work identically and accept the arguments noted in the table below using the following
convention:
generateddl.bat --action[install] --arg1[value] --arg2[value] ..... --argn[value]
You must supply the --action parameter to the script. If no additional arguments are passed to the
script, the script defaults to the values of the properties set in the setupDatabase.properties file.
Script
Arguments
setupDatabase.properties
Required?
Description
--action
none
Yes
Required in the command line using a

value of install
--dbType
pega.database.type
Yes
Database vendor type. Enter udb for

DB2-LUW, mssql for MS SQLServer;
oracledate for Oracle, postgres for PostgreSQL
--dbSchema
data.schema.name
Yes *
(Optional) sets the data schema for a

split-schema environment
--outputDirectory
none
--mtSystem
multitenant.system
Yes **
Whether this is a Multitenant

System. 'true' if yes, 'false' if no
--username
pega.jdbc.username
Yes
Database username
--password
pega.jdbc.password
Yes
Database password
--url
pega.jdbc.url
Yes
Database jdbc url enclosed in double
(Optional) the output directory for the

scripts. Defaults to [distributionImage]
/schema/generate/[dbType]
20
quotes
--driverJar
pega.jdbc.driver.jar
Yes
Path to the jdbc driver
--driverClass
pega.jdbc.driver.class
Yes
Class of the jdbc drver
--connProperties
jdbc.custom.connection.properties
(Optional) Semicolon-delimited custom

JDBC properties (e.g. prop11=value;prop2=value;prop3=value)
* Required if using a split-schema database configuration

** Required if installing or upgrading a Multitenant system
1. Open the file setupDatabase.properties for editing. This file is located in the scripts folder of
your distribution.
2. Specify the properties noted in the table above.
3. Type generateddl.bat or generateddl.sh passing in the required --action install parameter.
For example: #generateddl.bat --action install
4. The script writes the output to the following directory.
<PRPC_HOME>\schema\generated
This directory is deleted and recreated each time the generateddl script is executed. If you want
to save a copy of the DDL, rename the directory prior to running the tool.
21
Installing the Rulebase

This section describes how to install and load the PRPC rulebase.
The PRPC Rulebase can be loaded using either of the following methods.
n
Installation and Upgrade Assistant (IUA) uses a Java-based UI guided tool that sets up the
PRPC Rulebase schema in the database and loads PRPC rules
Command-line script A command-line script is provided for both Unix and Windows platforms
and is suitable for automating the installation process of installing PRPC in headless environments
Rulebase Prerequisites
Prior to running the installer either the IUA or the command-line version confirm you meet the
following prerequisites:
n
Database users and roles are defined with the proper privileges
A new database is defined with sufficient capacity
Database schemas are defined

For a single schema configuration, you should have one schema for both rules and data objects
For a split schema configuration, you should have separate schema for rules and data objects
System Requirements
Because of the large volume of data loaded by the Installation and Upgrade Assistant (IUA), you should
run the installer or command-line install scripts on the same machine as the database server. If this is
not possible, run the tool on a system with fast, direct access to the database server.
The minimum systems requirements are:
n
Windows or Linux operating system
1.25GB of memory
6GB of disk space
Java Platform, Standard Edition Development Kit (JDK)
The installer creates a series of log files in <PRPC_HOME>\scripts\logs. If you encounter a problem
while running the installer, copy the logs to a safe location before re-running the installer. The IUA recreates this directory each time the installer is run.
The <PRPC_HOME>\.checksum directory provides an MD5 checksum for each the file in the
distribution. To verify that the distribution has been downloaded correctly, you can calculate a checksum
using the Jacksum tool www.jonelo.de/java/jacksum/.
For example: if your PRPC distribution was unzipped to <PRPC_HOME>:
java -jar jacksum.jar -m -a md5 -r -p -O outputFile.md5 <PRPC_HOME>
22
Compare outputFile.md5 to the md5 file located in <PRPC_HOME>\.checksum. The checksum

values should be identical.
Running the Installation and Upgrade Assistant

This section describes how to run the Installation and Upgrade Assistant (IUA) to install the rulebase.
Before running the IUA, make sure you have met the database and system prerequisites.
1. Copy the distribution file to the computer that you will use to run the IUA. Extract the contents of
the ZIP file into an empty directory.
If you are installing the software from the PRPC DVD included with your media distribution, copy
the contents of the DVD to an empty directory.
2. Double-click the PRPC_Setup.jar file.
Alternatively, right-click the PRPC_Setup.jar file and select Open With > Java.
3. The IUA loads and the install icon
appears in your task bar.
Throughout the install, you can click the buttons at the bottom of the screen to navigate from
screen to screen, get install help or cancel the process. The recommended selection is indicated by
the button with a blue background.
n
moves to the next screen

goes back to the previous screen
23
4. Click
starts a process
displays help for that screen
cancels the install and exits the IUA
to display the License Agreement.
Scroll to read the agreement.

5. Click
to accept it and move to the Installer Mode screen.
If you do not want to accept the agreement, click
to exit the IUA.
On the Installer Mode screen, choose Installation. If you are performing an upgrade, see the
PRPC 7.1.5 Upgrade Guide.
24
6. Click
to choose your Database Type.
25
Select your database type.

7. Click
to choose the Product Edition.
Select the PRPC edition you want to install.

PRPC Standard Edition this option installs a new instance of PRPC 7.1.5. It is the default
selection.
PRPC Multitenancy Edition this option installs PRPC 7.1.5 in a specialized mode designed to
support Software As A Service (SaaS) runtime environments. See the PRPC 7.1.5Multitenancy
Administration Guide on the PDN for more information.
Upgrading or migrating from one edition to another is not supported. If you install one edition
and later decided to use a different edition, you will need to drop and recreate the database or
create a new database. The schema DDL between the two editions are not compatible.
8. Click
to set up your database connection.
26
Complete the fields to specify the database connection to your PRPC database.
Some of the fields on this screen in particular the JDBC Driver Class Name and the
Database JDBC URL are pre-populated based on the type of database you selected on the
prior screen. If you edit these or any other fields on this screen and later decide to change the
database type, the IUA may not populate the fields correctly. If this occurs, you can enter the
correct field values as documented below or exit and re-launch the IUA, selecting the intended
database type.
JCBC Driver Class Name Enter the JDBC driver class name.
The IUA will attempt to pre-populate this field for you as oracle.jdbc.OracleDriver. If the field
does not populate correctly, manually enter the class name or exit and re-launch the IUA.
JDBC Driver JAR File Enter the full path to the appropriate driver file for your database type
and version. Click
supported drivers.
to browse and select the file. See the Release Notes for a list of
Database JDBC URL Enter the JDBC connection URL for your PRPC database.
The IUA will attempt to pre-populate this field asjdbc:oracle:thin:@//localhost:1521/orcl
. If the field does not populate correctly, manually edit the field or exit and re-launch the IUA.
Database Username and Password Enter the user name and password for the PRPC user on
your database.
27
Make sure you have configured the database user you use during the installation with full read,
write and administration permissions. The user must have access to the schema for the PRPC
database. In particular, the database operator used to connect to the database during the install
must be explicitly granted privileges that allow them to create user defined functions.
Rules Schema Name (Required) Enter the name of the Rules schema in the PRPC database.
Data Schema Name (Required) Enter the name of the Data schema in the PRPC database.
If you are installing into a single schema, the value for the data schema name should be
configured to match the value of the Rules Schema Name.
If you are installing into a split schema, those values should be different, corresponding to the
schema you defined in the database.
When you have completed entry of the database connection values, click
. If the
connection is not successful, review your connection information, correct any errors and retest.
9. If the connection is successful, click
schema.
to choose how you want to apply the database
By default, the IUA is designed to automatically generate and apply the schema DDL to your
database. If the DDL is already defined in the database, select the Bypass Automatic DDL
Application option. Otherwise, leave the box unchecked.
10. Click
to enter the System Name.
28
Complete the following fields.

System Name Enter a name for your PRPC system.
Production Level Enter a production level. Depending on the type of installation, choose:
5 for a system that will be used in production
4 for a pre-production system
3 for a test system
2 for a development system
1 for an experimental system
The Production Level affects many security features of your system. Both the System Name and
Production Level can be changed through PRPC once the system is running.
The System Name can be accessed from the System > Settings > System Name landing page. The
Production Level can be updated from the App Explorer by typing Data-Admin-System in the search
field and then selecting SysAdmin > Class > Data-Admin-System to open your system.
11. Click
to begin the Rulebase Load.
29
Click
to start the rulebase load. Installation logs automatically appear in this window.
The rulebase load time can last for several hours and will vary widely based on network proximity
to the database server. The log window may appear inactive when the IUA is processing larger
files. When the load is complete or if there is an issueduring installation, a message box appears. If
there is an issue, copy the installation log from the temporary directory to a safe location before
exiting the IUA.
12. Click
to close the IUA.
Running the Command Line Script

To use the install.bat/.sh script, you configure the setupDatabase.properties file and run the script.
1. First edit the setupDatabase.properties file.
You can find the setupDatabase.properties file in the scripts directory of your distribution, .e.g
<PRPC_HOME>\scripts\setupDatabase.properties
2. Open a command prompt and navigate to the scripts directory.
3. Type install.bat or ./install.sh to run the script.
The installation of the rulebase can take several hours, depending on the proximity of the database to the
system running the install script.
30
Completing the Rulebase Installation

When the install process completes successfully, the install will report performance metrics for each step
of the installation process. See the example below.
When you see these log messages you know that you installation has successfully completed.
31
32
Application Server Setup

This section describes how to configure your WebSphere Application Server for use with PRPC 7.1.5.
n
Prerequisites
Preparation
Configuration
Deploying PRPC Archives
Application Server Prerequisites

Before you start to set up your application server, confirm that the following prerequisites have been
met.
n
You have installed a supported JDK. See the Platform Support Guide for a list of supported
versions.
Confirm or set a JAVA_HOME environment variable that points to the directory where the Java
JDK is installed.
You have installed a supported version of the WebSphere application server. See the Platform
Support Guide for a list of supported versions.
Application Server Preparation

The application server configuration process depends on two primary considerations.
1. Single vs. Split-Schema
2. Base vs. Admin User
Single vs. Split Schema

In a split-schema configuration, PRPC uses the Java Naming and Directory Interface (JNDI) standard to
identify and access the appropriate schema. One of the benefits of using JNDI is that it allows PRPC to
access different schema while using only a single data source. The configuration of additional JNDI
parameters is straightforward and covered in this section.
Base vs. Admin User

A typical PRPC system requires the configuration of a single JDBC data source.
However, if you are using a dual-user configuration Base + Admin user you will need to configure
a second data source in the application server. The configuration of an additional JDBC data source is also
covered in this section.
Include WebSphere Default Packages
Confirm that your installation of the WebSphere application server includes all the default packages.
33
In particular, you must include the package EJBDeploy tool for pre-EJB 3.0 modules which is
required by PRPC.
Create a WebSphere Profile

Run the WebSphere Profile Management Tool to create a WebSphere Application Server profile in which
to run the PRPC application.
You can use either the Typical profile creation or the Advanced profile creation option. Both methods
allow you to choose whether to apply Administrative Security requiring a login with user name and
password when starting the Administrative Console.
n
The Typical profile assigns default values for such things as the Profile name, Node name, Host
name, and access ports.
On Windows platforms, the Typical option creates the application server as a Windows service by
default. This means that you must manage the profile as a Windows service, for example when
starting and stopping the server.
The Advanced Profile lets you change the defaults. If you choose this option, you must choose to
deploy the Administrative Console.
When you create the profile, record the following information for use later in the configuration.
n
n
Profile name
User name and password for the Administrative Console if you choose to apply Administrative
Security
Port numbers for the profile, including:
o
Administrative Console Port
HTTP transport port
Depending on your environment, you may also need to record the port numbers for the
Administrative console secure port, the HTTPS transport port and the SOAP connector port. If you
are unsure about these requirements, check with your application server administrator.
Configure the Application Server

Start the server for the new profile, launch the Administrative Console, and log in.
34
On Windows platforms, you can start the profile server and launch the Administrative Console from the
Start menu. For example:
Start > All Programs > IBM WebSphere > Application Server V8.5 > Profiles > AppSvr01 > Start the
server.
To launch the Administrative Console:
Start > All Programs > IBM WebSphere > Application Server V8.5 > Profiles > AppSvr01 >
Administrative Console.
Set JVM Properties
Follow these steps to set the JVM properties.
1. In the Administrative window, on the left side of the screen, click Servers > Server Types >
WebSphere application servers.
2. Find the name of the server on which PRPC will run and click that server name. The Configuration
tab for the server displays.
35
3. In the Server Infrastructure section, click + next to Java and Process Management to
expand the section, then click Process Definition to display its Configuration tab.
4. In the Additional Properties section, click Java Virtual Machine to display its Configuration
tab.
5. On this window, set:
Initial Heap Size to 2048MB
36
Maximum Heap Size to at least 4096MB

These values are initial minimum estimates for typical development systems. They may need to
be higher based on your server hardware and the number of other applications on the server.
6. In the Generic JVM Arguments field, enter the following to compress references to optimize
heap space:
-Xcompressedrefs
7. Set verbose garbage collection and provide a garbage collection log file:
-verbose:gc
-Xverbosegclog:<file>
8. Set the garbage collection policy to concurrent collector.
-Xgcpolicy:gencon
or
-Xgcpolicy:optavgpause
9. Click Apply. A message appears at the top of the screen explaining that the changes were made.
10. Click Save to save these changes to the master configuration.
Create URL Providers

This procedure sets the required URL Pega reference and an explicit Temporary directory for PRPC. The
temporary directory is used by PRPC to store static data. It is important that the directory be properly
specified and accessible to the PRPC user.
In WebSphere you specify this directory as a JNDI reference to a URL object.
1. In the WebSphere Administration console select Resources > URL > URL Providers in the left
frame.
37
2. Set the Scope level appropriate to your deployment, and click on the Default URL Provider link.
38
The default URL configuration page displays.
3. Under the Additional Properties section, click on the URLs link to display the URLs listing page.
4. Click New to display the Configuration page.
39
5. Define a URL for the NULL file that PRPC can use to discard erroneous error messages.
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 for UNIX/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 PRPC 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 temporary directory.
Enter the path using forward slashes for both Windows and UNIX platforms. For example, on
Windows the value might be: file:///D:/Temp/PegaTempDir.
40
The directory names you enter here are case sensitive. Be sure to enter the names of the
directories exactly as they have been created on your system.
If the directory you specify does not exist, PRPC attempts to allocate it. It is 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 is
accessible under your security policy.
In a clustered deployment, each PRPC instance must have its own temporary directory. You cannot
share a temporary directory with more than one PRPC instance.
9. Click OK and then Save in the confirmation message.
Create a JDBC provider
1. In the Administrative console, click Resources > JDBC > JDBC Providers to display the JDBC
Providers page.
41
2. In the Scopes dropdown, choose the scope level appropriate to your deployment. Click New to
display the JDBC provider wizard.
3. Complete the fields in Step 1 as follows:

In the Database type dropdown, select Oracle .
42
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 name and
explanatory description for the driver you selected.
Click Next to display Step 2.
4. In the Directory location field, confirm the entry, if one is displayed, or enter the path to the
driver class file or files listed in the Class path field.
The appropriate file depends on the Java version of your JVM:
For Java 6: ojdbc6.jar
For Java 7: ojdbc7.jar
43
5. Confirm that the settings are correct, and click Finish to return to the JDBC Providers page.
6. Click Save in the confirmation message.
Configure Data Source Connection
1. Still on the JDBC providers page, click on the name of the provider you just created to display the
General Properties page.
2. Under the Additional Properties heading, click Data Sources.
Click New to display the data source wizard.
44
3. In Step 1 of the wizard, enter the following information:
45
In the Data Source name field, enter PegaRULES

In the JNDI name field, enter jdbc/PegaRULES.
4. Supply information about your PRPC 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 server name, 1521 is
the port number it is using for communication, and myDatabase is the database name.
In Data store helper class name, specify the Oracle data store helper.
If you are unsure about the information to supply for your database server, consult with your site
database administrator.
46
5. Click Next to display the Summary page.

6. On the Summary page, confirm that the settings are correct and click Finish to return to the JDBC
Providers page.
7. Click Save in the confirmation message.

8. Still on the Data Sources page, click the PegaRULES link in the Name column to open the
Configuration page for this data source. Then, under Additional Properties, click the Custom
47
Properties link to display the Custom Properties page.
9. Click New to define any additional properties you may need for your database connection here.
48
To create a new property, click New on the Custom Properties form. After creating each property,
click OK to save the property, and New again to create the next property. Be sure 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 top of the
page.
Define Database Authentication Credentials

1. In the link path at the top of the page, click PegaRULES to return to the PegaRules properties
page. Then, under the Related Items section, click the link JAAS J2C authentication data.
You will define your database authentication credentials here.
2. Click New to specify the General Properties.
49
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 PRPC database
user on your PRPC database. This should be the data, or base, user.
4. Click OK to return to the authentication data entries page, and click Save in the Messages 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 PegaRules
properties page.
50
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.
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 Connection to
confirm your data source configuration.
51
Configure WebSphere Data Source Connections

At a minimum, set the Maximum data connections to 50.
You should determine the best value of this setting based on your application architecture,
usage profile and environment considerations. As a rule of thumb, the database connection pool
should be no smaller than the Work Manager pool.
To set the maximum connections:
1. On the Data sources page, click Connection pool properties:
2. Set the Maximum connections value to 50 or higher based on your environment need.
52
3. Click Apply and save the configuration changes.

Configure WebSphere WorkManager
If you are deploying PRPC's EAR archive, prpc_j2ee14_ws.ear, complete the following procedures
to define a WorkManager. PRPC uses the WorkManager to run asynchronous tasks to support
internal components such as agents, services, daemons, and child-requestors.
If you are deploying PRPC's WAR archive, prweb.war, you do not need to configure the
WorkManager. Skip this top and go to the topic: Set HTTP transport channel custom property.
Complete the following procedures to define the WorkManager:
1. In the navigation menus on the left of the Administration Console expand Resources,
expand Asynchronous Beans, and select Work Managers
53
2. On the Work managers listing page, set the Scope to the level appropriate for your
deployment, and click New.
54
3. Complete the Configuration page for the Work Manager.
55
In the Name field, enter a name to identify this Work Manager, for example,
PRPCWorkManager.
In the JNDI name field, enter exactly the JNDI location wm/PegaWorkManager
In the Service names section, select the Security checkbox.
In Thread pool properties, set Maximum number of threads to 20.
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
In order to support the ability to open files attached to work objects in PRPC, you must set a
custom property, CookiesConfigureNoCache, on the transport chain in the Web Container
settings for the PRPC server.
1. In the administrative console, select Servers > Server Types > WebSphere application
servers to display the Application servers page.
2. Click on the name of your PRPC server to display the Configuration page.
56
3. Under Container Settings, expand Web Container Settings, and then click Web
Container transport chains.
This console displays the listing page for transport chains.
57
4. Click the name of the appropriate transport chain.

If your site is using the default transport configuration for this server, select
WCInboundDefault 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.
58
5. Under Transport Channels on this page, click HTTP inbound channel.

The console displays the Configuration page for the selected transport channel.
59
6. Under Additional Properties on this page, click Custom Properties.

The console displays the listing page for this channels custom properties.
7. Click New
The console displays the form for a new custom property
60
8. Complete this form.

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.
Configure JNDI for Split-Schema
To configure WebSphere to communicate with both schemas, you create two Binding Identifiers.
n
One that points to PegaRULESDefaultSchema
One that points to PegaDATADefaultSchema
To create a new Binding Identifier:
61
1. Expand the Environment tab.
2. Click Naming and then Name Space Bindings.
3. Select the correct Scope for your environment and click New.
62
4. For the binding type, select String and click Next.
5. On Step 2: Specify basic properties screen, enter the following values:

Binding identifier Enter PegaRULESDefaultSchema
Name in the name space relative to lookup name prefix enter the string
prconfig/database/databases/PegaRULES/defaultSchema
String Value enter the schema name of your Pega Database RULES schema
63
6. Click Next.
7. On the Summary panel, click Finish.
8. On the Name Space Bindings screen, click Save.

9. Repeat the steps above for the data schema except: On the Step 2: Specify basic properties
screen, enter the following values for the DATA schema.
Binding identifier Enter PegaDATADefaultSchema
Name in the name space relative to lookup name prefix enter the string
prconfig/database/databases/PegaDATA/defaultSchema
String Value enter the schema name of your Pega Database DATA schema
10. Save the configuration.
64
Deploying PRPC Application Archives

This section describes how to deploy the PRPC application archives following the configuration of your
WebSphere application server. This includes:
n
the PRPC application
the System Management Application
the online help application
Deploy the PRPC Application (prpc_j2ee14_ws.ear)

Complete these instructions below to deploy the PRPC application using the prpc_j2ee14_ws.ear file
included in your distribution media.
The PRPC application archive is available both as a WAR file, prweb.war and as an EAR file, prpc_
j2ee14_ws.ear.
Pegasystems recommends deploying the EAR file component, prpc_j2ee14_ws.ear for all new
deployments on WebSphere.
The PRPC application WAR file , prweb.war, can be successfully deployed on the WebSphere application
server but deploying and configuring the EAR file ensures that you can add advanced 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.
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 ignore these messages. You will supply these resources as you complete the
installation process. Be sure to stop the application after deploying.
1. Make sure the WebSphere Application Server is running. Log into the administration console.
2. From the left frame, select Applications > New Application.
65
3. Click New Enterprise Application.
4. Click the Browse button and select prpc_j2ee14_ws.ear from your installation media. Click
Next.
WebSphere displays Preparing for the application installation.
66
5. Click the Detailed - Show me all installation options and parameters radio button.
This option allows you to review all the installation options for the application, including the default
bindings and resource mappings
6. Click + to expand Choose to generate default bindings and mappings.
7. Complete this page.
67
Check Generate Default Bindings.

Check Use default virtual host name for Web and SIP modules.
Accept the other defaults and click Next.
WebSphere displays Application Security Warnings.
8. Scroll to the bottom on this page and click Continue to display a wizard where you can specific
installation options.
This security file allows PRPC to run when J2EE Security Checking is enabled.
68
This section of the installation process is a series of steps under the general heading of Install
New Application. For PRPC, you only need to make changes in the Map resource references
to resources step. For each of the other screens, you may accept the defaults, or customize them
according to the requirements of your organization.
69
9. For Step One, accept the defaults and click Next.

10. Continue through the next steps, either accepting the defaults, or customizing for your
organization, as needed.
Locate the step where you Map resource references to resources.
11. For the three Resource references, to url/initialization/explicittempdir (in the EJB EngineCMT,
EngineBMT beans and the prweb.war module) enter the JNDI name
url/initialization/explicittempdir in the field Target Resource JNDI Name.
70
This maps the location you specified in the URL provider you created to the corresponding Resource
Reference in the application, so that the application will use the location for the PegaTempDir.
12. Click Next
Depending on your configuration, you may see a set of warnings related to missing resource
references, for example:
71
These are resource references that are defined in web.xml, the deployment configuration files
for the application, but not mapped to resource definitions in your application. In the page, Map
resources to references, they are mapped to the Target Resource JNDI Name url/pega/none,
indicating that they are not used. Pegasystems provides these references for 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 the requirements
of your organization.
72
73
15. On the Summary page, click Finish.

The system begins installing the EAR file, which can take a few minutes.
When the installation completes successfully, WebSphere displays a message similar to the
following.
16. Click Save directly to the master configuration.

Deploy the System Management and Online Help Applications
In addition to the PRPC application, you must also deploy the online help application prhelp.war and
the System Management application prsysmgmt.war.
For more details on the System Management Application, refer to the System Management Application
Reference Guide on the PDN.
Complete the following steps to deploy prsysmgmt.war or prsysgmgt.ear.
74
1. Under the left frame, select Applications > New Application.
2. Click New Enterprise Application.
3. Click Browse and navigate to select the application war file prsysmgmt.war or the ear file
prsysgmgmt.ear from your installation media.
4. Click Next to begin the installation.
75
5. Click the Detailed - Show all installation options and parameters radio button.
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 their defaults.
8. Click Next.
You may see some security warnings similar to the following.
76
9. Click Continue to bypass the warnings.

WebSphere displays the Install New Application wizard.
77
10. Accept the defaults and click Next for Steps 1 through 7.
11. In the Map context roots for Web Modules step, enter the name of the file, prsysmgmt or
prhelp, as the context root, and click Next.
78
12. Accept the defaults and click Next on Steps 9 and 10.
13. On the Summary page, click Finish.
79
WebSphere displays a message, Installing . . ., and updates it with information during the install.
When complete the following message is displayed in the page.
80
14. Click the Save link to save the changes to the master configuration and return to the first page of
the installation series.
15. 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.
Assign the PegaDiagnosticUser Role
Users accessing the System Management Application (SMA) in PRPC must be assigned the role
PegaDiagnosticUser. Users can access the SMA in the PRPC Developer portal by clicking Tools >
System Management Application. If the user does not have this role they will be challenged for
authentication when they attempt to access the System Management Application from PRPC.
You can use the SMA to monitor and control caches, agents, requestors, listeners, and other processing in
the Process Commander system. For more information, see the System Management Application
Reference Guide on the PDN.
If you want to allow limited access to the SMA, use the Map Special Subjects dropdown to select All
Authenticated in Applications Realm, or click Map Users . . . to assign the role to specific users.
81
1. Select Applications > Application Types > WebSphere enterprise applications.
2. Click the name of your PRPC core application, for example prpc_j2ee14_ws, to open the
Configuration page.
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 to
Everyone:
82
If you installed the WAR archive, prweb.war, the PegaDiagnosticUser role is set to None.
4. Select PegaDiagnosticUser and set the proper access level for your site.
l
If you do not want to allow access to the SMA, use the Map Special Subjects dropdown to
select None.
If you want to allow limited access to the SMA, use the Map Special Subjects dropdown to
select All Authenticated in Applications Realm, or click Map Users . . . to assign the
role to specific users.
If you want to allow open access to the SMA, use the Map Special Subjects dropdown to
select Everyone.
Login to PRPC
Log into the PRPC web application, replacing the <server> and <port> values with your specific values.
http://<server>:<port>/prweb/PRServlet
The PRPC log in screen displays.
83
Use the following credentials to log in.

User ID: administrator@pega.com
Password: install
After logging in, PRPC automatically launches a process to index the rules in the system to support fulltext search. While this process is running usually 10-15 minutes to complete depending on your
system configuration you may notice some delay in the responsiveness of the PRPC user interface.
84
Post Deployment Configuration

This section describes the post deployment activities that are performed in the system once you have
completed the setup and configuration of your WebSphere application server and deployed the PRPC
archives.
n
Enable Help and System Administration applications
Configure search index host node settings
Change the administrator password
Install solution frameworks
Enable Help and System Management Applications

The Help and System Management web applications are accessed from the PRPC interface through a URL.
Either application can be deployed to a different application server than the core PRPC application.
To enable these applications
1. From the
button, select System > Settings > URLs.
2. In the Online Help URL field, enter the URL for the Help application in the format:
http://<host>:<port>/prhelp
3. In the SMA URL field, enter the URL for the System Management Application in the format:
http://<host>:<port>/prsysmgmt
4. Click Submit.
You must log out of PRPC and log back in for these changes to take effect.

Directed Web Access (DWA) allows external users that do not have a PRPC 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 user to access PRPC and may identify a proxy server.
To configure DWA
1. From the
button, select System > Settings > URLs.
2. In the Public Link URL field, enter the URL that you want to provide in emails in this format:
http://<host>:<port>/PRServlet
3. Click
You must log out of PRPC and log back in for these changes to take effect.
85
Configure Search Index Host Node Settings

Search indexing supports the full-text search facility in PRPC for rules, data instances, and work objects.
By default, search indexing is enabled and indexing starts automatically when you start the application
server after deploying PRPC.
Host node settings are set by default to your PRPC node, and the Index directory is set to
PegaRULESIndex in your PRPC temporary directory.
You can change the default settings on the Search tab of the System Settings landing page. To access
this page, select
> System > Settings > Search.
Change the Administrator Password

Because the default password for the system administrator is widely published, it is important to protect
your system after an installation by changing the password for the Adminstrator@pega.com operator ID.
To change the password
1. From the Operator Menu located to the right of the Designer Studio header, select the Profile
option.
2. Click Change Password.
3. Verify the Current Password, then enter and confirm the New Password.
4. Click Save.
Install Solution Frameworks

If you are installing one of Pegasystems Solution Frameworks as part of your PRPC development
environment, install the framework now.
Follow the instructions in the Installation Guide provided on the distribution media for the Framework.
86

Prpc715 Install Wasora

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Prpc715 Install Wasora

Diunggah oleh

Hak Cipta:

Format Tersedia

PegaRULES Process

Phone: (617) 374-9600

Document: PegaRULES Process Commmander Installation Guide

Updated: Tuesday, April 29, 2014

Platform Support Guide

Installation, Upgrade and Deployment Documentation

Planning Your Install

Automatic or manual DDL application

Optional database user for schema changes

Database Server Setup

Create the Database

Create the Tablespaces

Optional: Manually Generate and Apply DDL

Installing the Rulebase

Running the Installation and Upgrade Assistant

Running the Command Line Script

Completing the Rulebase Installation

Application Server Setup

Application Server Prerequisites

Application Server Preparation

Include WebSphere Default Packages

Create a WebSphere Profile

PegaRULES Process Commmander Installation Guide

Configure the Application Server

Set JVM Properties

Create URL Providers

Create a JDBC provider

Configure Data Source Connection

Configure WebSphere Data Source Connections

Configure WebSphere WorkManager

Set HTTP transport channel custom property

Configure JNDI for Split-Schema

Deploying PRPC Application Archives

Deploy the PRPC Application (prpc_j2ee14_ws.ear)

Deploy the System Management and Online Help Applications

Assign the PegaDiagnosticUser Role

Post Deployment Configuration

Enable Help and System Management Applications

Configure Directed Web Access

Configure Search Index Host Node Settings

Change the Administrator Password

Install Solution Frameworks

PegaRULES Process Commmander Installation Guide

About This Guide

PegaRULES Process Commmander Installation Guide

See the Platform Support Guide for a list of supported versions.

Planning Your Install

PegaRULES Process Commmander Installation Guide

Optional database user for schema changes

the configuration of an additional database user account

the configuration of a dedicated connection pool in the application server

PegaRULES Process Commmander Installation Guide

A minimum of 200 MB of disk space

Database and application server time zone and character encoding

PegaRULES Process Commmander Installation Guide

PegaRULES Process Commmander Installation Guide

Database Server Setup

Oracle server is installed and running.

Java is enabled in the database.

Single vs. Split Schema

a Rules schema, which contains the PRPC rulebase

a Data schema, which contains both Data and Work instances

PegaRULES Process Commmander Installation Guide

Database User Accounts