ECase PDC Install On TI Environments
Pega/PDC Software Version: 7.4.13
Author(s): Pega
Version: Draft
ECase Run Book
Table of Contents
1
1.1
1.2
1.3
1.4
2
3
Brief Description of System ................................................................................................................. 1
Application Name.......................................................................................................................... 1
Version .......................................................................................................................................... 1
Environment.................................................................................................................................. 1
Brief Description ........................................................................................................................... 1
Environment preparation.................................................................................................................... 1
Environment Verification .................................................................................................................... 6
i
ECase Application Install On TI Environments Run Book
1
Brief Description of System
1.1 Application Name
ECaSE PDC
1.2 Version
Pega 7.4.13
1.3 Environment
TI
1.4 Brief Description
The Electronic Case Management (ECaSE) PDC system serves as systems that you want the application to
monitor. In addition to configuring the systems to push messages, you can set email scorecard
subscriptions and enable Pega PDC to receive information from the monitored systems.
For each Pega Platform system, complete the following tasks:

Ensuring that each system has a unique name

Enabling Pega Autonomic Event Services to send requests to monitored nodes
2
Environment preparation

Draft
Database preparation
o Launch the pgAdmin tool.
o Double-click the PostgreSQL instance that you want to configure.
 Note: You must enter the password for the administrator account that was
configured during the installation of PostgreSQL.
o Right-click Login Roles and select New Login Role.
o In the Role Name field, enter the name for your database user.
o On the Definition tab, enter the password for this user.
o On the Role Privileges tab, grant permissions to this user. When using a single
database user, you must grant at least the Can create database objects permission.
o Click OK.
Page 1
ECase Application Install On TI Environments Run Book




Draft
Creating PostgreSQL database schema
o Creating the primary schema for Rules and Data Objects (pega_rules and
pega_data)
o In pgAdmin, click + to expand your database.
o Under the database name, right-click Schemas and select New Schema.
o On the New Schema window, in the Name field, enter the schema name in lower
case.
o Use the Owner drop-down list to select your database user.
o On the Default Privileges tab, check ALL and click OK.
o Add the schema to the search path:
 Right-click on your database name under the Databases label and select
Properties.
 Select the Variables tab.
 In the Variable Name drop down box, select search_path.
 In the Variable Value text field, enter the name of the database schema.
Retrieve the Pega 7.4.13 media file from Artifactory - CB-PEGADev/Pega7.4.1/116395_P7413UPD.zip
Retrieve the Postgres JDBC driver from Artifactory CB-PEGA-Dev/postgresql9.4.1212.jar
Edit the setupDatabase.properties which can be located in /scripts folder under the media
folder
o Update the database properties – sample below
 #pega.jdbc.driver.jar=C:\Users\kapa0001\Downloads\PRPC-7.4.1GA\postgresql-9.4.1212.jar
 #pega.jdbc.driver.class=org.postgresql.Driver
 #pega.database.type=postgres
 #pega.jdbc.url=jdbc:postgresql://dev-xxx-xxx-1.dev.ti.census.gov:1525/
 #pega.jdbc.username=dbxxadmin
 #pega.jdbc.password=default
o Update the schema name for rules and data
 rules.schema.name=PEGA_RULES
 data.schema.name=PEGA_DATA
o Update the user temp directory
 user.temp.dir=<required atlest 2GB>
o Skip the UDF which RDS will not support
 bypass.udf.generation=true
o Enable Multitenant system allows organizations to act as distinct PRPC
installations
 multitenant.system=true
o save and exit
o Open a command prompt and navigate to the scripts directory
o ./install.sh to run the script
o Installing the rulebase can take several hours, depending on the proximity of the
database to the system running the installation script. When the installation is
complete, you see a BUILD SUCCESSFUL message.
Page 2
ECase Application Install On TI Environments Run Book



Configure the Tomcat server through the ansiable script
Retrieve PDC_07_30.jar RAP file from Artifactory and The system data and rulesets for
PDC application are loaded during this step.
o Log in to Pega Platform by entering the credentials (administrator user) that you
established when you installed this server.
o Select Designer Studio > Application > Distribution > Import.
 Select Choose File, browse for the PDC_07_30.jar file from your
computer and follow the instructions in the wizard.
Restart the PDC server.
The wizard identifies differences between the database schema of your current system and the
schema of PDC and applies automatically.
2.1
Ensuring PDC integration on monitored systems

Configuraing the PDC email account
Because scorecards and work item notifications are sent through your company’s email
system, must configure an instance of Data-EmailAccount that defines an account from
which the emails are sent.
Click Designer Studio > integration -> Email -> Email Accounts

Draft
Select the “Defult” Account ID and provide the nessccery information as
show below
Page 3
ECase Application Install On TI Environments Run Book

Make sure that it is secussfuly tested

Upon application import, we need an operator which an be used to create tenant in PDC
application for monitoring. Operator with access group “AESServiceDeveloper” has
privileges of administrator in shared layer.

Genratign the Tenant PDC URL
o Login as a AESServiceDeveloper and navigate to Tenant as show below
Draft
Page 4
ECase Application Install On TI Environments Run Book

Provide the all necessary information to create a tenant
1. Tenant Name and valide email which will be receive the tenant
information through email.
2. Make sure keep the informations safe.

Once we enable PDC integration in monitored systems so that PDC Services can receive
alerts and exceptions from a system, update the system's configuration with the correct
URL.
1. Click Designer Studio > System > Settings > Predictive Diagnostic Cloud.
2. In the ENDPOINT SOAP URL field, enter the endpoint SOAP URL that corresponds to
the Pega PDC Tenent SOAP URL.
3. Click Update Configuration and Wait for the data to arrive PDC. PDC might take 5 minutes
to display the new system.
2.2
Ensuring PDC integration on monitored systems
Once we enable PDC integration in monitored systems so that PDC Services can receive alerts and
exceptions from a system, update the system's configuration with the correct URL.
4. Click Designer Studio > System > Settings > Predictive Diagnostic Cloud.
5. In the ENDPOINT SOAP URL field, enter the endpoint SOAP URL that corresponds to
the Pega PDC Tenent SOAP URL.
Draft
Page 5
ECase Application Install On TI Environments Run Book
6. Click Update Configuration and Wait for the data to arrive PDC. PDC might take 5 minutes
to display the new system.

Provide access to environment specifically to the Tomcat server, file servers, Database
as per the Roles defined in the document
EnvironmentAccess.
docx
3
Environment Verification
After the environment is setup, verify the following:










Draft
Hazelcast ports are opened correctly as per the installation guide and “System Pulse”
works correctly.
Health Services on Load Balancers are working correctly and Nodes stay healthy for
extended period of time.
o Timeout is set on the Load Balancers to the Pega recommended value [tbd].
All Load Balancers are configured for Https connection.
Firewalls configurations allow the ECaSE Pega applications to connect to the PDC
SMTP Host is configured correctly on the PDC application and working.
Install certs to all ECaSE Pega Application monitored server(s) and PDC ndoes
PDC communications are established.
URLs are verified
Logs are verified
Environment access is verified.
Page 6