Installing and Testing AES: Configuring the Monitored System

Now that you have installed and tested the AES, you should configure a system for monitoring. The first thing that you need to do is to give the monitored node a name.

Give a New System Name to the Node to be Monitored

Login to the node to be monitored as an administrator, e.g. administrator@pega.com with the default password of install.

Once you have login, click Designer Studio > System > Settings > System Name:

 

Figure 42: Menu Navigation for Changing System Name

In the form that appears as shown below, enter your new system name in the field: “New Name”. In my case, I am renaming it as “MyVM2”.

 

Figure 43: Renaming the System Name

Click the “Submit” button above to save your changes. You will receive the following confirmation:

 

Figure 44: Successfully Configured System Name

Once you have successfully configured the system name, restart the system.

💡	If this is a multi-node system, you need to restart all the nodes.

💡	Remember to apply monitored systems hotfixes right after you have configured the system for monitoring with Pega Autonomic Event Services. For applicable hotfixes for your system, always check with Pega Support.

 

 

Enabling Pega Autonomic Event Services Integration On Monitored Systems

Once your system is back online, login to the system to be monitored, as an administrator (e.g. using the administrator@pega.com with the default password of install).

In the Designer Studio, clicked:

Designer Studio > System > Settings > Predictive Diagnostic Cloud:

 

Figure 45: Accessing the Predictive Diagnostic Cloud Settings

In the screen that opens, in the “ENDPOINT SOAP URL” field, enter the endpoint SOAP URL that corresponds to the Pega Autonomic Event Services server's SOAP URL.

In other words, this URL should point to the server that you have installed the AES.

The format is as follows:

http://[server name]:[port number]/prweb/PRSOAPServlet

The following is an example of the setting:

 

Figure 46: Setting for Predictive Diagnostic Cloud

💡	Ensure that your AES server is up and running before proceeding to the next step.

After that, click on the “Test Connectivity” button, and you should have a success message like the following:

 

Figure 47: Connection to AES Server Successful

Once your connection is successful, click on the “Update Configuration” button, and you should see the “Successfully updated Predictive Diagnostic Cloud configuration” as shown below:

Figure 48: Successfully Updated the Predictive Diagnostic Cloud Configuration

💡	In the installation guide, you were told to use the following format: <kbd>http://[server name]:[port number]/prweb/PRSOAPServlet</kbd> However, that does not work.

[Check the book availability here]