Pega Autonomic Event Services 8.3 is an intelligent application monitoring tool that runs on Pega Platform™. You install Pega Autonomic Event Services 8.3 on stand-alone multitenant servers.
To complete the installation, review the following information:
- Increasing the thread pool size
- Importing the application bundle
- Installing the required hotfixes
- Partitioning the database
- Configuring the email server account
- Configuring a Pega Platform tenant
- Optional: Configuring operators
Before you install Pega Autonomic Event Services, complete the following tasks:
- Verify that the Pega Autonomic Event Services deployment package contains the following files:
- AES.zip – The Pega Autonomic Event Services application bundle
- The following table partitioning scripts:
- alerts_partitions.sql – used for configuring thepegaam_alert database table
- alerts_aggregates_partitions.sql – used for configuring thepegaam_alert_aggregate database table
- exceptions_partitions.sql – used for configuring thepegaam_exception database table
- exceptions_aggregates_partitions.sql – used for configuring thepegaam_exception_aggregate database table
- index_events_partitions.sql – used for configuring thepegaam_index_events database table
- nodestats_partitions.sql – used for configuring thepegaam_node_stats database table
- palalerts_partitions.sql – used for configuring thepegaam_palalert database table
If you use a non-standard Pega Platform installation with schema names other than the default pegadata, replace the schema names in the partitioning scripts with your custom schema names:
Open a database tool, for example, the PostgreSQL tool pgAdmin.
Run the following query:In the query, replace <table_name> with the appropriate table name, as listed in the following table, for example, for the alerts_partitions.sql file, enter pegaam_alert.
SELECT DISTINCT schemaname FROM pg_indexes WHERE tablename = '<table_name>';
File name Database table name
pegaam_node_stats palalerts_partitions.sql pegaam_palalert
- Use a text editor to open the file that contains the table partitioning script.
- Find all occurrences of the phrase pegadata in the script file, and replace them with the result of the query in step a.
- Ensure that you understand the deployment architecture and hardware requirements of Pega Autonomic Event Services. For more information, see Pega Autonomic Event Services 8.3 architecture overview and deployment best practices.
Note: To run Pega Autonomic Event Services on PostgreSQL, you must install the PG Stat Statements module.
- Install a new instance of Pega Platform 8.3 with the Apache Tomcat 8 application server and the PostgreSQL 11 database, and then verify your installation, as described in the Pega Platform Installation Guide for your environment, available on the Deploy Pega Platform page.
Important: During the installation, in the Multitenancy Edition.stage, select
To avoid scenarios in which the default thread pool size in Pega Platform is not sufficient to run Pega Autonomic Event Services efficiently, increase the number of threads in the thread pool. As a result, you ensure the correct operation of Pega Autonomic Event Services and you prevent insufficient thread pool size exceptions.
- Log in to Dev Studio.
- Create a prconfig/agent/threadpoolsize/default dynamic system setting in the Pega-Engine ruleset with the value of 50. For more information, see Using dynamic system settings.
- In the header of Dev Studio, click Create > SysAdmin > Dynamic System Settings.
- In the Short description field, enter Thread pool size.
- In the Owning Ruleset field, enter Pega-Engine.
- In the Setting purpose field, enter prconfig/agent/threadpoolsize/default
- Click Create and open.
- In the Value field, enter 50.
- Click Save.
- Restart the application server.
Pega Platform loads the system data and rulesets for Pega Autonomic Event Services during this step.
- Log in to Pega Platform by entering the administrator credentials that you used when you installed the new instance of this server. The default user name is [email protected] and the password is install12345!
Note: If you are accessing the system for the first time, change the default password.
Click Configure > Application > Distribution > Import.
On the Application: Import wizard page, click Choose File or Browse, and then browse for the AES.zip file from your distribution media.
Select the Enable advanced mode to provide more granular control over the import process check box, and then click Next.
In the subsequent steps, click Next until you see the Operators tab.
Select the Enable new operators and overwrite existing operators on import check box.
In the subsequent steps, click Next until you see the following error messages: Import complete to database from the file AES.zip, and Errors encountered during library compilation. See log for details.
Restart the Pega Autonomic Event Services server.
Log in to Pega Autonomic Event Services as AESDeveloper with the password Install12345! For security reasons, change the default password when you log in for the first time.
After you import the application bundle for Pega Autonomic Event Services 8.3, install the required hotfixes for this version. For more information, see Pega Autonomic Event Services hotfixes.
To partition the database, for each of the table partitioning scripts that are listed in step 1 of the prerequisites, perform the following steps:
- Open a database tool, for example, the PostgreSQL tool pgAdmin.
- Run the script in the database tool. For more information, see the documentation for your database tool.
Pega Autonomic Event Services sends event-based notifications and daily digests through your company’s email system. Configure the account that you want Pega Autonomic Event Services to use for sending email.
- Log in to Dev Studio.
- Click Configure > Integration > Email > Email Accounts.
- Click the Default account.
- In the Viewing your email accounts. , complete the section. To learn more about email accounts in Pega Platform, see
- Click Submit.
Before you start using Pega Autonomic Event Services, configure at least one tenant and tenant administrator. When you create the tenant, the system automatically creates the tenant organization, division, and unit, as well as a Data-Admin-Tenant class instance for the tenant.
- Log in to Dev Studio.
- Click Configure > System > Tenant Management > Create.
- In the Tenant Name field, enter the name of the system tenant.
- In the Description field, enter a short (64-character) description to help distinguish systems with multiple shared-region applications.
- In the Contact Full Name field, enter the name of the person who is the contact for this tenant.
- In the Contact Email field, enter the email address of the tenant contact.
- In the Setup Activity field, select AESasService.
- Optional: The default manager password and user password are autogenerated and are both complex passwords that are automatically sent to your email after you create a tenant. To override the default passwords, in the Parameters section, enter a manager password and user password that comply with the password policies for your Pega Platform instance.
Important: If you decide to override the default passwords, ensure that your passwords comply with the password policies, which you can view by clicking Configure > System > Settings > Security Policies. Although Pega Platform sends a confirmation email for non-compliant passwords, you cannot access the accounts by using such passwords.
- In the Administrator field, enter the user identifier for the tenant administrator.
- In the Password field, enter the password for the tenant administrator.
Important: Although you are required to complete the Administrator and Password fields, completing them does not actually create an operator. To create a tenant administrator, run the TemporaryOperatorInTenant activity, as described in steps 12 to 18.
- Click Create Tenant to create the tenant and the organization. This operation creates an instance of Data-Admin-Tenant.
The previous steps imply that the operator who creates the Rule-File-Binary also creates the tenant. However, a different operator can also create the tenant. In this case, the operator who creates the tenant must have access to the Rule-File-Binary through the operator’s primary access group.
- In the navigation pane of Dev Studio, click Records > Technical > Activity, and then double-click the TemporaryOperatorInTenant activity.
You can filter the list of activities by clicking the Click to filter icon in the column header.
- Click Actions > Run.
- In the tenantName field, enter the name of the tenant that you entered in step 3.
- In the Operation field, enter create.
- In the EmailInput field, enter the email address to which you want to send the administrator password.
- In the OperatorName field, enter the user identifier of the tenant administrator.
- Click Run.
The TemporaryOperatorInTenant activity copies your shared-layer administrator user to the tenant that you are creating, and then sends the administrator password to your email.
- In the navigation pane of Dev Studio, click Records > SysAdmin > Dynamic System Settings, and then click the SharedURL dynamic system setting.
- In the field, enter the URL of the Pega Autonomic Event Services host system, for example, https://aes831prod.pegacloud.net/prweb.
- Click Save.
By default, Pega Autonomic Event Services contains the following standard operators with access to all clusters in the enterprise:
- AESDeveloper – Configures and manages Pega Autonomic Event Services data and rules from the developer portal. This operator has access only to the shared layer but cannot access the tenant layer.
- DiagnosticCloudManager – Uses the manager portal to monitor the operational status of nodes and clusters across the enterprise. The manager assigns work, monitors process operations, and performs administrative tasks in this portal. This operator has access only to the tenant layer.
- DiagnosticCloudUser – Uses the user portal, which includes a uniform approach to finding, entering, and completing work within one or more clusters. This operator has access only to the tenant layer.
Different stakeholders within your organization, such as business sponsors, operational managers, and developers, might require access to the Pega Autonomic Event Services server to review summaries, route work items, and resolve issues. For information about editing the existing operators and adding new ones, see Managing Pega Autonomic Event Services operator records.
What to do next
After you install and configure Pega Autonomic Event Services 8.3, configure the systems that you want to monitor. For more information, see Configuring your systems for monitoring with Pega Autonomic Event Services 8.3.
Check whether your monitored system needs an enhanced version of the PegaAESRemote ruleset to support the latest features. For more information, see Enhanced PegaAESRemote ruleset to support the latest Pega Autonomic Event Services features.