Pega Platform Installation Guide

Transcription

1 Pega Platform Installation Guide Database: Microsoft SQL Server and EnterpriseDB Application Server: Apache Tomcat

2 Copyright and trademark notices Copyright Copyright 2015 Pegasystems All rights reserved. Trademarks For Pegasystems trademarks and registered trademarks, all rights reserved. Other brand or product names are trademarks of their respective holders. For information about the third-party software that is delivered with the product, refer to the third-party license file on your installation media that is specific to your release. Notices This publication describes and/or represents products and services of Pegasystems It may contain trade secrets and proprietary information that are protected by various federal, state, and international laws, and distributed under licenses restricting their use, copying, modification, distribution, or transmittal in any form without prior written authorization of Pegasystems. This publication is current as of the date of publication only. Changes to the publication may be made from time to time at the discretion of Pegasystems This publication remains the property of Pegasystems and must be returned to it upon request. This publication does not imply any commitment to offer or deliver the products or services described herein. This publication may include references to Pegasystems product features that have not been licensed by you or your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems services consultant. Although Pegasystems strives for accuracy in its publications, any publication may contain inaccuracies or typographical errors, as well as technical inaccuracies. Pegasystems may make improvements and/or changes to the publication at any time. Any references in this publication to non-pegasystems websites are provided for convenience only and do not serve as an endorsement of these websites. The materials at these websites are not part of the material for Pegasystems products, and use of those websites is at your own risk. Information concerning non-pegasystems products was obtained from the suppliers of those products, their publications, or other publicly available sources. Address questions about non-pegasystems products to the suppliers of those products. This publication may contain examples used in daily business operations that include the names of people, companies, products, and other third-party publications. Such examples are fictitious and any similarity to the names or other data used by an actual business enterprise or individual is coincidental. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 2

3 This information is the property of: Pegasystems One Rogers St. Cambridge, MA USA Phone: (617) Fax: (617) Updated: Monday, September 21, 2015 Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 3

4 Contents Copyright and trademark notices 2 Copyright 2 Trademarks 2 Notices 2 Using Pegasystems documentation 1 Online resources 1 Installation Overview 2 Pega 7 Platform architecture 2 Planning your installation 3 Single and split-schema systems 3 Installation methods 4 Product mode 5 Transport-layer encryption 5 Business Intelligence Exchange (BIX) and Pega 7 Platform product versions 5 Triggers in Pega System requirements 5 Installation and Upgrade Assistant (IUA) 6 Application server 6 Database server setup 8 Preparing your database 8 Configure time zone, character encoding and locales 8 Configuring your Microsoft SQL Server and EnterpriseDB database 8 Database users 9 Creating an empty database 11 Creating new schema 11 Installing the Pega 7 Platform 12 Manual or automatic application of schema changes 12 Editing the setupdatabase.properties file 12

5 Common properties 12 Editing the file 13 Manually generating and applying DDL 14 Applying schema changes 15 Editing setupdatabase.properties to bypass DDL generation 15 Rulebase Prerequisites 15 Configuring Kerberos authentication 15 Installation and Upgrade Assistant (IUA) 16 Running the Installation and Upgrade Assistant (IUA) 17 Installing from the command line 26 Application Server Setup 27 Application server prerequisites 27 Synchronizing hardware clocks 27 Configuring ports 27 Gathering database connection information 28 Configuring the Application Server 28 Single versus Split Schema 28 Base versus Admin User 29 Setting JVM memory parameters 29 Turn Off Session Persistence 30 Enabling AWT to support Pega 7 Platform Graphical Reports 30 Creating JDBC resources 31 Create an explicit temporary directory 32 Configure Roles and Users 32 Creating JNDI binding identifiers 32 Deploying the Pega 7 Platform Archives 34 Post Deployment Configuration 35 Starting the Pega 7 Platform applications 35 Logging in to the Pega 7 Platform 35 Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 2

6 Enabling help and System Management applications 36 Configuring Directed Web Access 36 Configuring search index host node settings 36 Changing the administrator password 37 Changing the default path to the Pega 7 Platform logs 38 Installing Pega-supplied applications 39 Appendix A: setupdatabase.properties 40 Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 3

7 Using Pegasystems documentation This guide describes how to install a new instance of the Pega 7 Platform on a system with Microsoft SQL Server and EnterpriseDB and Apache Tomcat. See the Platform Support Guide on the PDN for a list of supported platforms. To upgrade, see the Pega Upgrade Guide. To update from Pega 7.1.x, see the Pega Update Guide. Online resources The Pega Discovery Network (PDN) at is Pegasystems' online documentation and information site. To access the latest documentation, navigate to the Support & Resources tab. Platform Support Guide: The Platform Support Guide lists the databases, drivers and application servers supported for this release. Review the Platform Support Guide before you install the Pega 7 Platform to verify that your database and application servers are supported. Deployment guides: The PDN includes the latest installation, upgrade, and update guides. Release notes: Review the important information in the release notes before you continue. Updated help files: Download the current prhelp.war file from the Resources & Support tab of the PDN, or use the online version: v71/procomhelpmain.htm. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 1

8 Installation Overview Installing the Pega 7 Platform 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. This guide is organized to expedite the installation process. It can be summarized in the following steps that are typically performed in sequence. 1. Configure the database 2. Configure the application server 3. Install the Pega 7 Platform 4. Configure the Pega 7 Platform 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. The Pega 7 Platform supports different deployment topologies and configuration options which impact how the supporting infrastructure is configured and managed going forward. Pega 7 Platform architecture The Pega 7 Platform is a Java EE-compliant enterprise application that requires two main subsystems for its operation an application server and a database server. The application server hosts the Pega 7 Platform 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 the Pega 7 Platform. Application users and developers typically access the Pega 7 Platform through a web browser. Applications may also expose HTTP-based services (for example, SOAP, REST or HTTP) for purposes of administration or process automation in a headless environment. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 2

9 Planning your installation The Pega 7 Platform supports a run-time mode and a variety of deployment topologies that can impact the choices you make at different stages of the installation. Before beginning, read this section thoroughly. Note: If you are making changes in your environment as part of the upgrade, do them before upgrading. Single and split-schema systems There are two configuration types: Single schema: One schema contains all rules and data objects. Split schema: There are two schemas on the same database: Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 3

10 a Rules Schema contains Rules tables and associated data and objects a Data Schema contains transaction data, including Work objects Split-schemas allow you to conduct an in-place upgrade in one environment and then migrate the upgraded objects to other environments. Split-schema configurations are best practices, particularly in critical development environments such as QA, STAGE and PROD. The following diagram illustrates the difference between a single-schema system and a splitschema system. Installation methods You can install the Pega 7 Platform either automatically or manually. This guide includes instructions for both methods. Automatically Use the UI-based Installation and Upgrade Assistant (IUA) to automatically install either the rulebase or the rulebase and the schema. The IUA runs on any Windows, Unix, Linux, or zlinux system with Java 6 or higher. Manually Configure the setupdatabase.properties file with your site-specific properties. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 4

11 Then run scripts to install and optionally generate DDL. If you generate DDL, have your Database Administrator apply the DDL to your schema. Both 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 network 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). Product mode The Pega 7 Platform includes a Multitenancy mode. The Multitenancy mode has different requirements, different run-time behaviors and different administrative procedures from other modes. Before you select the Multitenancy mode, review the Multitenancy Administration Guide which discusses this mode in detail. It is included in your distribution package and available on the PDN. Transport-layer encryption Pegasystems recommends that you use a strong transport-layer encryption (for example, Transport Layer Security 1.2) to secure Pega 7 Platform web applications. This requires that you create and install TLS/SSL digital certificates on your web application server for the Pega 7 Platform. For more information, see the documentation for your application server. Business Intelligence Exchange (BIX) and Pega 7 Platform product versions Release versions of the Business Intelligence Exchange (BIX) product are synchronized with release versions of the Pega 7 Platform. To use the BIX product once you have obtained a license, the version of BIX must be the same as the version of the Pega 7 Platform. BIX is included in the full distribution. See the Pega BIX User Guide for information about installing BIX. Triggers in Pega Pega handles triggers differently than previous versions. Triggers that reference the updates cache and rule view tables will drop when the Pega 7 Platform opens for the first time. The Pega 7 Platform now maintains these tables. If you have custom triggers that only maintain these tables, do not recreate the trigger. If you have custom triggers that depend on these tables or are defined on these tables and these triggers also have other logic you want to keep, contact Pegasystems Global Customer Support for instructions on how to proceed. System requirements Before you install, check the supported versions of your application server and database. See the Platform Support Guide on the PDN for a list of supported versions. Ensure that your system meets the minimal requirements describes in this section. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 5

12 Installation and Upgrade Assistant (IUA) The minimum systems requirements to run the Installation and Upgrade Assistant (IUA) are: Windows or Linux operating system 1.25 GB minimum available memory 10 GB minimum disk space and at least 8 GB available space in the temporary directory of the root file system Java Platform, Standard Edition Development Kit (JDK). Set JAVA_HOME to the root directory of the JDK. For Java 8, you may need to remove from the PATH any references to a Java shortcut. Application server Pegasystems recommends that you install only the Pega 7 Platform on the application server. The application server requires: 1 GB minimum free disk space Note: Allocate enough storage to accommodate debugging and other logging requirements. Configure logging to avoid writing logs to the directory that contains the application server runtime components. Application server memory requirements The Pega 7 Platform runs in memory on Java Virtual Machines (JVMs). This memory is called a heap. In general, all activity is distributed over multiple JVMs (nodes) on the application server. Standard suggested system heap size is 4-8 GB based on monitoring of memory usage and GC frequency. Larger heaps may be advisable if a system is to run applications designed to allow a high number of concurrent open tasks per session or to cache a large collection of transaction or reference data. Do not deploy the Pega 7 Platform in an environment wher the heap size exceeds the vendorspecific effectiveness limit. In current 64 bit JVMs, compression is enabled by default. Do not deploy the Pega 7 Platform in an environment where compression is disabled or where the heap size exceeds the vendor-specific effectiveness limit. The host application server memory size must be at least 4 GB larger than the Pega 7 Platform heap size. The additional 4 GB is recommended to allow for operating system, monitoring tools, operating system network file buffering, and JVM memory size (-xmx option). The minimum host application server memory size is 8 GB: Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 6

13 4 GB heap + 4 GB for native memory, operating system, and buffering Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 7

14 Database server setup This section lists the database prerequisites and describes how to create user accounts, the database, and database schema for your installation. Preparing your database Before you begin preparing your database, verify that a supported version of the database server is installed and running. Modify your Pega 7 Platform database configuration to match the latest requirements. In particular, pay attention to the requirements described below. Download a supported version of the JDBC4 driver for your version of the database. Enable the common language run time (CLR) on the database to enable User-Defined Functions (UDFs). To check whether CLR is enabled, run the following script: select value from sys.configurations where name ='clr enabled' If the return value is 1, CLR is enabled. Configure time zone, character encoding and locales Configure your database server, application server, and the system on which you are running the installation to use the same: Time zone Character encoding (UNICODE or EBCDIC) Regional settings/locale Configuring your Microsoft SQL Server and EnterpriseDB database To prepare your Microsoft SQL Server and EnterpriseDB database server for use with the Pega 7 Platform, complete the following steps: 1. Create database user accounts. 2. Create an empty database. 3. Create the database schema. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 8

15 Database users This guide refers to the following database users: Deployment user: the user who runs the installation. After the installation, you can remove this user. Run-time users: These users perform actions on the Pega 7 Platform after the installation. In a dual user configuration, an Admin user is granted full privileges, and a Base user is granted a smaller subset. Pegasystems recommends the dual user configuration : Base user: the user who will run the Pega 7 Platform. For most run-time operations, the Pega 7 Platform uses the Base user and associated data source. The data schema should be the default schema for Base users. Admin user: an optional user provided to the Pega 7 Platform that is preferentially used by certain features that require creating, modifying, or dropping database schema objects; for example, System Management facilities and certain decisioning operations. Pegasystems recommends that you create the Admin user separate from the Base user, however, you can create a single Base user with both sets of privileges. If there is no separate Admin user, the Pega 7 Platform uses the Base user for all run-time operations. User permissions The following table describes the general permissions for each user and the purpose of each permission. Pegasystems recommends the dual-user configuration. For a single-user configuration, the Base user also requires the permissions listed for the Admin user. Permission Deployment User Base User Admin User Insert/select/update/delete on data and rules tables Select data and rule schema metadata Execute stored procedures in data and rules schemas Create/update/drop tables, indexes, and constraints in data and rules schema The deployment process saves instances to data and rules tables. The deployment process reads metadata about tables and other objects to determine the most efficient way to access and store data. The deployment process uses stored procedures for system operations. The deployment process installs the tables, indexes, and constraints used by PegaRULES. User has basic read and write access to data and rules tables. PegaRULES reads metadata about tables and other objects to determine the most efficient way to access and store data. PegaRULES uses stored procedures for system operations. Various system management tools allow you to create and modify tables and indexes. For data schemas, various facilities in decisioning create short-lived tables to assist with strategy analysis. Create/update/drop views The deployment process Various facilities in decisioning create Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 9

16 Permission Deployment User Base User Admin User in data and rules schemas Create/update/drop stored procedures, triggers, & functions Enable & disable triggers on rule tables Truncate rule and data tables Grant object-level privileges on rules schema to data user installs the views used by PegaRULES. The deployment process installs stored procedures, triggers, and functions used by PegaRULES. The installation and upgrade processes disable triggers in order to save large amounts of records more quickly. Various tables must be truncated during a PegaRULES upgrade. When the install & upgrade processes create tables and other objects in the rules schema, they must grant the base user access to these objects. short-lived views to assist with strategy analysis. Import also requires this when importing views. When system management utilities create tables and other objects in the rules schema, they must grant the base user access to these objects. Microsoft SQL Server user permissions The permissions needed for your database users depend on whether you have a split schema or a single schema, and whether you are using the recommended dual Admin/Base user configuration. Split-schema configuration PegaDATA Schemas owned by this user PegaRULES Privileges Deployment User Base User * AdminUser CREATE TABLE CREATE PROCEDURE CREATE VIEW CREATE ASSEMBLY CREATE FUNCTION none SELECT ON SCHEMA data-schema INSERT ON SCHEMA data-schema UPDATE ON SCHEMA data-schema DELETE ON SCHEMA data-schema EXECUTE ON SCHEMA data-schema SELECT ON SCHEMA rules-schema INSERT ON SCHEMA rules-schema UPDATE ON SCHEMA rules-schema DELETE ON SCHEMA rules-schema EXECUTE ON SCHEMA rules-schema PegaDATA PegaRULES CREATE TABLE CREATE PROCEDURE CREATE VIEW CREATE ASSEMBLY CREATE FUNCTION * Pegasystems recommends the dual-user configuration. For a single-user configuration, the Base user also requires the permissions listed for the Admin user. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 10

17 Single schema configuration Schema owned by this user Pega schema none Privileges Deployment User Base User * Admin User CREATE TABLE CREATE PROCEDURE CREATE VIEW CREATE ASSEMBLY CREATE FUNCTION SELECT ON SCHEMA schema INSERT ON SCHEMA schema UPDATE ON SCHEMA schema DELETE ON SCHEMA schema EXECUTE ON SCHEMA schema Pega schema S CREATE TABLE CREATE PROCEDURE CREATE VIEW CREATE ASSEMBLY CREATE FUNCTION * Pegasystems recommends the dual-user configuration. For a single-user configuration, the Base user also requires the permissions listed for the Admin user. Creating an empty database Create a database with a minimum of 5 GB for the user tablespace. This minimum size allows you to load the initial RuleBase and do simple development. Monitor the database use carefully. As development begins, the size of the database will need to increase significantly, depending on your use of the Pega 7 Platform and the number of users. When you configure your Microsoft SQL Server database, you can set the collation type to either Windows or binary. To shorten sort time in environments where you do not need language-specific sorting, you can consider setting a binary sort. See the Microsoft Windows documentation for more information about Windows collations and binary collations. Creating new schema Create the required schema depending on whether you are using a single or split schema configuration. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 11

18 Installing the Pega 7 Platform This section describes how to install and load the Pega 7 Platform. Use one of these methods to install the Pega 7 Platform: Installation and Upgrade Assistant (IUA) A Java-based UI guided tool that sets up the Pega 7 Platform Rulebase schema in the database and loads the Pega 7 Platform 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 the Pega 7 Platform in headless environments. Manual or automatic application of schema changes As part of installing the Pega 7 Platform, you must prepare the database schema. You can either use the generateddl script to generate a DDL file of schema changes you can give to your DBA to apply, or the installation process can automatically apply the schema changes. If you use the generateddl script, edit the setupdatabase.properties file. Editing the setupdatabase.properties file Skip this section if your deployment meets both these criteria: You will use the IUA to install. You will allow the installation process to automatically apply the schema changes. If your deployment does not meet both these criteria, follow the steps in this section to edit the setupdatabase.properties file. Follow these instructions if you plan to use the command line scripts to install or if you plan to use the generateddl script to generate a DDL file of schema changes. The Deployment user should perform these actions. The setupdatabase.properties file is used by the scripts that update the database schema and the rulebase. These scripts use the setupdatabase.properties file: The install.bat/sh script deploys the most recent version of the Pega 7 Platform. The generateddl.bat/sh script generates a SQL file to manually apply schema changes. See Appendix A: setupdatabase.properties for a sample edited file. Common properties These properties specify the settings needed to connect to the database: Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 12

19 The script arguments column lists the arguments for the generateddl.bat/sh script. The setupdatabase.properties column lists the corresponding file property. generateddl script argument --dbtype setupdatabase.properties pega.database.type Description Database vendor type. Enter: mssql --dbschema --dbdataschema rules.schema.name data.schema.name In a single schema environment sets rules schema and data schema. In a split-schema environment, sets the rules schema only. Optional: Specified for a split schema environment only. Sets the data schema for the environment. --mtsystem multitenant.system Is this a Multitenant System? true/false --dbuser pega.jdbc.username User name of the Deployment user. --dbpassword --dburl pega.jdbc.password pega.jdbc.url Password of the Deployment user. If you plan to use encrypted passwords, leave this blank. The Database jdbc url. See See "Gathering database connection information " on page 28 for more information. --driverjar pega.jdbc.driver.jar Path and file name of the jdbc driver --driverclass pega.jdbc.driver.class Class of the jdbc driver --tempdir --connproperties user.temp.dir jdbc.custom.connection.properties Optional: the location of the temp directory. If you leave this blank, the Pega 7 Platform uses the default. Pegasystems recommends that you set this to C:\TEMP. Optional: Semicolon-delimited custom JDBC properties (for example: prop1=value;prop2=value;prop3=value) Editing the file To edit the setupdatabase.properties file: 1. Open the file setupdatabase.properties for editing. This file is located in the scripts folder of your distribution. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 13

20 2. Specify the properties for your system. For each property, add the appropriate value after the equals sign. 3. Save and close the file. Manually generating and applying DDL Skip this section if you do not need to generate a DDL file. A generateddl script is provided for Windows (generateddl.bat) and Linux (generateddl.sh) in the <PRPC_HOME>\scripts directory. This script 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 database management tools. Both scripts work identically and accept the arguments noted in Editing the setupdatabase.properties file. Use the following convention: generateddl.bat --action install --arg1 [value] --arg2 [value]... --argn [value] Note: You must supply the --action parameter to the script. You can also supply an --outputdirectory parameter. If no additional arguments are passed to the script, the script defaults to the values of the properties set in the setupdatabase.properties file. See Appendix A: setupdatabase.properties for a sample edited file. To use the script: 1. Perform these steps as the Deployment user. 2. If you have not already done so, edit the setupdatabase.properties file. See Editing the setupdatabase.properties file. 3. Open a command prompt and navigate to the scripts directory. 4. Type generateddl.bat or generateddl.sh passing in the required --action install parameter. For example: Single-schema: #generateddl.bat --action install --dbschema <rules schema> Split-schema: #generateddl.bat --action install --dbschema <rules schema> -- dbdataschema <data schema> If you do not pass another value for --outputdirectory, the script writes the output to the following directory: PRPC_HOME\schema\generated\ Note: The output directory is deleted and recreated each time the generateddl script executes. To save a copy of the DDL, rename the directory before you run the script. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 14

21 Applying schema changes Before you continue, have your DBA follow these general steps to apply the schema changes: 1. Review the DDL files in the DDL output directory. The default directory is: PRPC_ HOME\schema\generated\database-type\install\udfstatements. 2. Determine the order in which the DDL files must be applied. 3. Make any needed manual changes to the files. 4. Apply the DDLs for the UDFs from the DDL output directory in the correct order. a. Enable UDF execution for the database. b. Register the C#.cs code files with the database. c. Apply the CREATE FUNCTION DDL. 5. Install the UDF archive file PRPC_HOME\archives\udf\prreadstream.jar to the schema. Editing setupdatabase.properties to bypass DDL generation After your DBA applies the changes to your database, set the property bypass.pega.schema=true in the setupdatabase.properties file. Then, when you run install.bat/sh, the system does not try to apply a schema that is already present. Doing so would cause the installation to fail. Rulebase Prerequisites Prior to running the installer either the IUA or the command-line version confirm you meet the following prerequisites: Database users and roles are defined with the proper privileges. A new database is defined with sufficient capacity. Database schemas are defined correctly. 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. Configuring Kerberos authentication The Pega 7 Platform supports Kerberos functionality. Kerberos is a computer network authentication protocol which allows nodes communicating over a non-secure network to prove their identity to one another in a secure manner. To use Kerberos for authentication, you must use the command line to install Pega 7 Platform. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 15

22 To use Kerberos authentication: 1. Edit the setupdatabase.properties file. a. In the Uncomment this property section of the file, uncomment the jdbc.custom.connection.properties property. b. Provide the correct parameters to the jdbc.custom.connection.properties property as semicolon-delimited name/value pairs. The specific parameters depend on your security infrastructure: jdbc.custom.connection.properties=<parameter1>=<value1>;<parameter2>=< value2>;<parameter3>=<value3>; For example, on a Microsoft SQL Server database server from a Windows client machine (where both machines belong to the same Windows domain), using the Microsoft JDBC driver, the property may be set as follows: jdbc.custom.connection.properties=integratedsecurity=true; c. Comment out all the username and password properties so that they appear as follows: # pega.jdbc.username db username # pega.jdbc.password db password [lines removed here] # pega.jdbc.username=admin # pega.jdbc.password=admin 2. Set up your database to enable Kerberos functionality. This may include additional vendor-specific JDBC driver configuration, or other setup procedures. Check the documentation from your database vendor to determine what Kerberos setup is needed for your database. 3. Continue at Installing from the command line to install the Pega 7 Platform. Installation and Upgrade Assistant (IUA) Because of the large volume of data loaded by the Installation and Upgrade Assistant (IUA), you should run the IUA or command-line scripts on the same network as the database server. If this is not possible, run the tool on a system with fast, direct access to the database server. 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. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 16

23 Note: 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, calculate a checksum using the Jacksum tool at For example: if your distribution was unzipped to <PRPC_HOME>: java -jar jacksum.jar -m -a md5 -r -p -O outputfile.md5 <PRPC_HOME> Compare outputfile.md5 to the md5 file located in <PRPC_HOME>\.checksum. The checksum values should be identical. Running the Installation and Upgrade Assistant (IUA) Before running the IUA, make sure that your system meets the requirements. 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 DVD included with your media distribution, copy the contents of the DVD to an empty directory. 2. Double-click the PRPC_Setup.jar file to start the IUA. Note: If JAR files are not associated with Java commands on your system, start the IUA from the command-line. In a command-line console, change to the directory containing PRPC_Setup.jar, and type java -jar PRPC_Setup.jar. The IUA loads and the install icon appears in your task bar. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 17

24 3. Click Next to display the License Agreement. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 18

25 4. Review the License Agreement and click Accept. 5. On the Installer Mode screen, choose Installation and click Next. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 19

26 6. Choose your Database Type and click Next. 7. Choose the product edition and click Next. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 20

27 Standard Edition this option installs a new instance of Pega It is the default selection. Multitenancy Edition this option installs Pega in a specialized mode designed to support Software As A Service (SaaS) run-time environments. See the Multitenancy Administration Guide on the PDN for more information. Note: 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 DDLs for the two editions are not compatible. 8. Configure the database connection. The JDBC drivers allow the Pega 7 Platform application to communicate with the database. Note: Some of the fields on the Database Connection screen in particular the JDBC Driver Class Name and the Database JDBC URL - are pre-populated based on the type of database you selected. If you edit these or any other fields on this screen, and then later decide to change the database type, the IUA may not populate the fields correctly. If this occurs, enter the correct field values as documented below, or exit and re-launch the IUA to select the intended database type. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 21

28 JDBC Driver Class Name Verify that the pre-populated value is accurate: com.microsoft.sqlserver.jdbc.sqlserverdriver JDBC Driver JAR Files Click Select Jar to browse to the appropriate driver files for your database type and version. See the Platform Support Guide on the PDN for a list of drivers. Database JDBC URL Verify that the pre-populated value is accurate. See See "Gathering database connection information " on page 28 for information. Enter your connection similar to the following. Replace the variables with the values for your system: jdbc:microsoft:sqlserver://server:1433; database= dbname;selectmethod=cursor;sendstringparametersasunicode=false Database Username and Password Enter the user name and password you created for the Deployment user on your database. Rules Schema Name Enter the name of the rules schema in the database. Data Schema Name Enter the name of the data schema in the database. For singleschema configurations the Data Schema Name is identical to the Rules Schema Name. 9. Click Test Connection. If the connection is not successful, review your connection information, correct any errors and retest. When the connection is successful, click Next to choose how to apply the data schema. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 22

29 10. Specify whether to bypass automatic DDL generation. By default, the IUA generates and applies the schema DDL to your database. To manually generate and apply the DDL, select the Bypass Automatic DDL Application option and continue the installation. After you complete the installation, run the generateddl script to apply the DDL. See See "Manually generating and applying DDL " on page 14for more information. Click Next. 11. Enter the System Name and Production Level and click Next: Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 23

30 System Name Enter a name for your Pega 7 Platform system. The System Name can be accessed from the System > Settings > System Name landing page. Production Level Enter a production level. The Production Level affects many security features of your system. Both the System Name and Production Level can be changed after the system is running. 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 can be updated from the App Explorer. Type Data-Admin-System in the search field and select SysAdmin > Class > Data-Admin-System to open your system. 12. Click Start to begin the Rulebase Load. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 24

31 Installation logs automatically appear in this window. The log is also stored in the <distribution image>/scripts/logs directory. 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, the following screen opens. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 25

32 If there is an issue, copy the log from the temporary directory to a safe location before exiting the IUA. 13. Click Back to return to the previous screen and then click Exit to close the IUA. Installing from the command line To use the install.bat/.sh script, first configure the setupdatabase.properties file. Note: If no additional arguments are passed to the script, the script defaults to the values of the properties set in the setupdatabase.properties file. See Editing the setupdatabase.properties file. 1. If you have not done so already, edit the setupdatabase.properties file. See Editing the setupdatabase.properties file. 2. Open a command prompt and navigate to the scripts directory. 3. Type install.bat or./install.sh to run the script. Installing the rulebase can take several hours, depending on the proximity of the database to the system running the install script. As the install proceeds, it reports performance metrics for each step of the installation process. When complete, you see a BUILD SUCCESSFUL message and the Total Time in minutes and seconds for the installation. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 26

33 Application Server Setup This section describes how to configure your Apache Tomcat Application Server for use with the Pega 7 Platform: Application server prerequisites Before you start to set up your application server, confirm that the following prerequisites have been met: Your system includes a supported JDK. See the Platform Support Guide on the PDN 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 Apache Tomcat application server. See the Platform Support Guide on the PDN for a list of supported versions. Synchronizing hardware clocks Pega 7 Platform uses Hazelcast distributed clustering technology to share data and send events between server nodes. Like most clustering technology, Hazelcast assumes that all cooperating servers have synchronized clocks. Pega 7 Platform validates time synchronization to ensure proper operations and triggers a PEGA0055 alert if clocks of sync between nodes. Pega 7 Platform also reports these errors to AES. The impact of these errors can include timeout errors and other system problems. Every operating system has a provision for referencing a common time standard like the one available at On UNIX, this is the network time protocol daemon, ntpd. On Windows, you can set a similar service through the clock settings in the control panel or task bar. See the documentation for your specific hardware operating system for information about setting this critical service. Configuring ports Before you start to set up your application server, ensure that the following ports are open and available: Search (Elasticsearch): one TCP port in the range (default 9300) Cluster communication - Hazelcast: multiple ports in the range (default 5701) Search To enable communication between the host nodes in the cluster, open a TCP port in the range on each node. (By default, Search uses port 9300.) These ports are used for internal node-to-node communication only, and should not be externally accessible. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 27

34 Cluster Communication - Hazelcast The Pega 7 Platform can include multiple servers, or nodes, and each node can contain multiple JVMs. The number of available ports in this range needs to be greater than or equal to the greatest number of JVMs on any one node in the cluster. For example, if there are 3 JVMs on one node, and 7 JVMs on another node, there must be at least 7 ports available. For cluster communication, the port range needs to be left open. By default, the system begins with port 5701 and then looks for the next port in the sequence (5702, followed by 5703 and so on). To override the default port range, set the value of cluster/hazelcast/ports in the prconfig.xml file. Gathering database connection information The connection URL depends on how you connect to the database. Obtain the following information from your DBA: Connection method: Service or SID Host name Port number Service or SID name You will need to enter the connection URL as pega.jdbc.url when you configure the application server. Your connection string will be similar to the following. Replace the variables with the values for your system: jdbc:microsoft:sqlserver://server:port;databasename=database Configuring the Application Server The section describes how to prepare and configure your application server. The application server configuration process depends on two primary considerations. 1. Single versus Split-Schema 2. Base versus Admin User Single versus Split Schema In a split-schema configuration, the Pega 7 Platform 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 the Pega 7 Platform to access different schema while using only a single data source. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 28

35 Base versus Admin User The Pega 7 Platform minimally requires one JDBC data source. However, if you are using the recommended dual-user configuration, Base + Admin user, you must configure a second data source in the application server. Setting JVM memory parameters Set the JVM memory options to increase the amount of system memory allocated to the application server running the Pega 7 Platform. Pegasystems recommends these settings: Initial Heap Size (Xms): between 4 GB - 8 GB, based on monitoring of memory usage and GC frequency Maximum Heap Size (Xmx): between 4 GB - 8 GB or larger, depending on your system configuration. See Application server memory requirements for more information. If your application server is using the recommended Oracle JVM, and you are using Java 7, also add the PermSize and MaxPermSize settings. (Java 8 does not require you to set PermSize.) PermSize (-XX:PermSize): 512 MB MaxPermSize (-XX:MaxPermSize): 1024 MB Note: If the server does not have enough memory allocated to run the Pega 7 Platform, the system may hang without an error message. Your values may need to be higher than these recommendations based on your server hardware, the number of other applications, and the number of users on the server. The method you use to set the memory parameters for the JVM depends on the way you installed Tomcat. If you installed Tomcat by expanding the.zip file, create a setenv.bat file on Windows or setenv.sh file in Unix in Tomcat s bin directory. Use the following examples as a guide, and substitute your values for those given: Note: This example is for Java 7. Java 8 does not require you to set PermSize or MaxPermSize. On Windows setenv.bat set JAVA_OPTS=-Xms4096m Xmx8192m XX:PermSize=512m XX:MaxPermSize=1024m On Unix setenv.sh JAVA_OPTS="-Xms4096m Xmx8192m XX:PermSize=512m XX:MaxPermSize=1024m" If you installed Tomcat as a Windows service, you can set the JVM options using a command line utility packaged with Tomcat. Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 29

36 tomcat7.exe //US//Tomcat7 ++JvmOptions=-Xms4096m Xmx8192m;-XX:PermSize=512m;- XX:MaxPermSize=1024m For systems that do not require Transport Layer Security (TLS), to deploy Pegasystems System Management Application on a different server than the Pega 7 Platform application, modify the JAVA_ OPTS environment variable to enable remote operation of the System Management Application. For more information on setting JVM parameters, see the Apache Tomcat documentation at Turn Off Session Persistence During application server shutdown, Tomcat persists session information into the session.ser file, created in the server file directory. When the application server restarts, it reloads the session information from the session.ser file and deletes the file. If serialized session objects refer to classes that are not visible to the container layer, you see a ClassNotFoundException error, such as the following: Jul 19, :37:46 PM org.apache.catalina.session.standardmanager doload SEVERE: ClassNotFoundException while loading persisted sessions: java.lang.classnotfoundexceptioncom.pega.pegarules.session.internal.authorization.contextmap DiagCallback java.lang.classnotfoundexception: com.pega.pegarules.session.internal.authorization.contextmapdiagcallback To suppress these errors, turn off Tomcat session persistence by uncommenting the Manager pathname parameter in the context.xml file, as follows: <!-- Uncomment this to disable session persistence across Tomcat restarts --> <!-- <Manager pathname="" /> --> Uncomment the parameter so it looks like this: <!-- Uncomment this to disable session persistence across Tomcat restarts --> <Manager pathname="" /> Enabling AWT to support Pega 7 Platform Graphical Reports The Abstract Window Toolkit (AWT) is Java's original platform-independent windowing, graphics and user interface widget toolkit. You must add a headless AWT setting to the JAVA options in the configuration file that is passed to Java at startup to allow the Pega 7 Platform to render and display graphics. To enable the required setting, add the following JVM option. -Djava.awt.headless=true Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 30

37 Creating JDBC resources Follow the steps in this section to create data sources. 1. Add JDBC connection information and temporary directory location to the context.xml file. Substitute your specific values for the host, port, dbname, username, password, and connection URL. For more information about connection URL strings, see See "Gathering database connection information " on page 28 <Resource name="jdbc/pegarules" auth="container" type="javax.sql.datasource" driverclassname="com.microsoft.sqlserver.jdbc.sqlserverdriver" url="jdbc:sqlserver://[host]:[port];databasename= [dbname];selectmethod=cursor;sendstringparametersasunicode=false" username="username" password="password" maxactive="100" maxidle="30" maxwait="10000" /> 2. If you are using the recommended dual-user configuration with a separate Admin user, configure a second data source. <Resource name="jdbc/adminpegarules" auth="container" type="javax.sql.datasource" driverclassname="com.microsoft.sqlserver.jdbc.sqlserverdriver" url="jdbc:sqlserver://[host]:[port];databasename= [dbname];selectmethod=cursor;sendstringparametersasunicode=false" username="username" password="password" maxactive="10" maxidle="5" Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 31

38 maxwait="5000" /> 3. Make the JDBC.jar file accessible to Tomcat: a. Download the JDBC.jar file appropriate to your database. b. Save the JDBC.jar file in the /lib directory on your application server. 4. Start the server to make these changes effective. Create an explicit temporary directory In context.xml, create a temporary directory using the following syntax: <Environment name="url/initialization/explicittempdir" value="path" type="java.lang.string" /> In a clustered deployment, each Pega 7 Platform instance must have its own temporary directory. You cannot share a temporary directory with more than one Pega 7 Platform instance. Configure Roles and Users Add the required roles, users and passwords to the tomcat-users.xml file. <role rolename="admin-gui"/> <role rolename="manager-gui"/> <role rolename="pegadiagnosticuser"/> <user username="admin" password="admin" roles="admin-gui,manager-gui,pegadiagnosticuser"/> Note: The PegaDiagnosticUser role is intended for use with the Pega 7 Platform System Management application (SMA). If you don t intend to use this application, this role can be omitted from the Tomcat configuration. Creating JNDI binding identifiers Modify the JDNI settings so the data source uses the correct schemas. Create these binding identifiers: One that points to the PegaRULES default schema One that points to the PegaDATA default schema Pega Installation Guide Apache Tomcat Microsoft SQL Server and EnterpriseDB 32