Question

AES 7.3 support for Pega 8.2

Hello,

According to this PDN article : https://community.pega.com/knowledgebase/pega-autonomic-event-services-hotfixes AES 7.3 isn't supported with Pega 8.2

Is it the PDN article that is missing an update or is it true ?

If it's true, Is there any reason to force client using PDC while they made the choice to go OnPremise for their infrastructure ?

As 8.1 is supported, what could explain that 8.2 isn't supported anymore ?

Thank you,

Loïc

Comments

Keep up to date on this post and subscribe to comments

Pega
August 16, 2019 - 1:10pm

Hi Loïc,

 

Thanks for the great question.

 

First, let me address some confusion. AES 7.3 does not support any of the Pega Infinity series including 8.1. There is work going on in late 2019 to provide a version of AES that will support Pega Infinity.

 

Even with that offering, I strongly recommend adding PDC to your on-premise support model rather than AES.

 

One reason to choose PDC over AES is simply cost. With AES you need a separate license, while PDC is included in your overall Pega license at no additional charge. AES is software that you install and maintain. PDC is a service where the infrastructure and maintenance are all managed by Pega on your behalf. PDC is a lower cost option across the board.

 

As a service, PDC is following the DevOps model. New capabilities are being released at least once per week in PDC. When you select the feedback option in PDC, we have the opportunity to enhance rather quickly for you. There is no work for you to do to take advantage of the new capabilities. AES is a traditional software product managed on release schedules.  The AES releases will be at a much slower pace and likely no more than once per year.

 

As I am sure you have experienced working with Pega, we are your partner in success rather than just a software vendor.  When you have a support issue or question, there is often a delay as logs are collected and shared with the support team. Timely resolution is critical to all involved, and the use of PDC allows us to look at the data collaboratively rather than have a back and forth capturing data.  Also, when we observe an issue at other clients, we can leverage PDC to identify if you have the same issue.

 

Hope this answers your question,

 

Mark

August 16, 2019 - 4:28pm
Response to REPLM

Hello Mark,

Thank you very much for the detailed information.

First, let me address some confusion. AES 7.3 does not support any of the Pega Infinity series including 8.1. There is work going on in late 2019 to provide a version of AES that will support Pega Infinity.

As per https://community.pega.com/knowledgebase/pega-autonomic-event-services-hotfixes and SR I opened, AES 7.3 is compatible with 8.1 and it's why this post was open, for now even if warnings on agents & requestor are outdated other parts are working.

Regarding the usage of PDC instead of AES, we have in place operational procedure for our ops teams that rely on Quiesce and AES, as such thing isn't intended to be available on PDC it means we will have to change our operational procedure if we use PDC.

We opened a PDC tenant to test it and for sure the design and information provided are much more relevant and easy to leverage than AES but we rely hope AES 8.3 will cover the breach.

 

As I am sure you have experienced working with Pega, we are your partner in success rather than just a software vendor.  When you have a support issue or question, there is often a delay as logs are collected and shared with the support team. Timely resolution is critical to all involved, and the use of PDC allows us to look at the data collaboratively rather than have a back and forth capturing data.  Also, when we observe an issue at other clients, we can leverage PDC to identify if you have the same issue.

It's really interesting, I don't remember an article advertising about such thing, I wasn't aware that Pega support can access PDC tenant to look into client logs.

Loïc