Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Installing Pega Autonomic Event Services 7.3

Updated on November 2, 2017

Pega® Autonomic Event Services is an intelligent application monitoring tool that runs on Pega Platform. Before you install and configure Pega Autonomic Event Services, you must install Pega Platform 7.3.

Installing Pega Autonomic Event Services 7.3 includes these main steps:

  1. Importing the application bundle
  2. Restarting the Pega Autonomic Event Services servers
  3. Configuring the email server account and operators

After you complete and verify your Pega Autonomic Events Services installation, configure the systems that you want the application to monitor. For more information, see Configuring systems for monitoring with Pega Autonomic Event Services.

To plan and complete the installation, review the following information:


Before you install Pega Autonomic Event Services, make sure that you complete the following tasks:

  1. Ensure that you understand the deployment architecture and hardware requirements of Pega Autonomic Event Services. For more information, see Pega Autonomic Event Services architecture overview and deployment best practices.
  2. Install Pega Platform 7.3, and then verify your installation as described in the Platform Installation Guide for your environment, available on the Deployment Guides page.
  3. Apply any required hotfixes to the Pega Platform before proceeding with the Pega Autonomic Event Services application installation. For a list of required hotfixes, see Pega Autonomic Event Services Hotfixes.
  4. Update the Pega Platform online help to the latest version from the Online Help Files section on the Pega Platform Update page. After you download the latest prhelp.war file, deploy it in your Pega Platform installation before continuing. For deployment information, see the Pega Platform Installation Guide for your application server.

Importing the application bundle

The system data and rulesets for Pega Autonomic Event Services are loaded during this step.

  1. Log in to Pega Platform by entering the credentials that you established when you installed this server.

    The default user name is [email protected] and the password is install.

  2. Click Designer Studio > Application > Distribution > Import.

  3. Click Choose File, browse for the AES_07_30_01.jar file from your distribution media, and follow the instructions in the wizard.
    The wizard identifies differences between the database schema of your current system and the schema of Pega Autonomic Event Services 7.3.

  4. If you use a Microsoft SQL Server, ask the database administrator to run the following database statement:
    EXEC sp_rename '<name of the Pega schema>.pegaam_action_work.clusterName', 'ClusterName', 'COLUMN';

If you use a split-schema configuration, substitute <name of the Pega schema> with the name of the Data schema. For more information, see the Split-schema and single-schema configurations section in the Pega Platform Installation Guide for Microsoft SQL Server and Apache Tomcat.
  1. Restart the Pega Autonomic Event Services server.

  2. Apply any required hotfixes to the Pega Autonomic Event Services application. For a list of required hotfixes, see Pega Autonomic Event Services Hotfixes.

Verifying the installation of rulesets

Perform this procedure to ensure that the required application rulesets are in the correct location.

  1. Log in to your application with the user name aesdeveloper. The default password is password.
  2. Change the default password. Ensure that you store your new password in a safe location.
  3. In Designer Studio, click Application > Structure > RuleSet Stack.
  4. Verify that the following ruleset versions are listed:


If your system does not contain the latest rulesets, the installation was not completed successfully. Follow these steps.

  1. Use the Log Files tool to review any errors or warnings that occurred. For more information, see Log Files tool.
  2. Contact Global Customer Support.

Configuring the email server account

Scorecards and work item notifications are sent through your company’s email system. Configure the account to use for sending email.

  1. In Designer Studio, click Integration > Email > Outbound Email.
  2. Click the Default account.
  3. Complete the Sender section. For more information, see Email Account form – Completing the Email Account tab.
  4. Click Save.
  5. Click Test connectivity to test the connection.

Configuring operators

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.
  • aesmanager — 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.
  • aesuser — Uses the user portal, which includes a uniform approach for finding, entering, and completing work within one or more clusters.

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 PDC operator records.

The linked article describes Pega Predictive Diagnostic Cloud (PDC), but the procedure also applies to Pega Autonomic Event Services 7.3. In the procedure, replace Predictive Diagnostic Cloud or PDC with Pega Autonomic Event Services.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

100% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us