[The following are additional info from the Kickstarter page above]
The Project
Pega CLSA is the highest level of technical achievement in Pega. With
the recent changes to the 7.3/7.4 certification, the path of CLSA
certification had become much more complicated.
This guide is a compilation of the knowledge that the author had
gained along the way, highlighting specific tricks that you can legally
leverage on to improve your chance of passing this certification. The
focus is on demystifying this certification, and most importantly,
providing guidance and tips on how you could optimise your success rate.
To support pursuing this certification, the publisher is relaunching
the Google Play eBook version at a limited-time special price through
Kickstarter. Various other eBooks are bundled to support the overall
learning experiences.
Plan
So far, a number of books related to Pega and the certification are published. You can view sample chapters in this website.
Technically, there is no risk in this project as this would be a
republish of existing books as Google Play eBooks to support candidates
pursuing this certification.
Upon confirmation of the project go-ahead, supporters are required to
provide their Gmail account to receive the Google Play eBook(s). The
distribution of the eBook(s) should be completed within days.
The following is an example of how the book(s) will be listed in your Google Play account.
Listing of Books In Google Play
The following is an example of a 2-page-view in Google Play (on a computer):
Reading on Computer with 2-Page-View
The following is a sample page viewed on a mobile device:
Reading On a Mobile Device
Rewards
By supporting this project, not only would you receive the eBook(s)
at a reduced price, it also motivates the publisher to provide more
rewards to interested learners of the Pega technology. Most importantly,
encouraging the publisher to produce more publications related to this
wonderful Pega technology.
Risks and challenges
Technically, there is no risk in this project as this would be a
republish of existing book(s) as a Google Play eBook(s) to support
candidates pursuing this certification.
Click on the following link to support this initiative:
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.comwith 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”.
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.
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:
