The next step is to validate your AES installation.
To do that, login with the user name aesdeveloper. The default password is password.
Unable to Login as “aesdeveloper”?
If you are using Pega 7.4 onwards, you will
realise that you are not able to login using the aesdeveloper because Pega had added a
new security layer, where all newly imported users are disabled by default.
To resolve this, you need to login as
another administrator, e.g. administrator@pega.com with the default password of install. Followed by searching for the aesdeveloper.
The easiest way to search for an operator
is to enter it into the search box (located at the top right of the Designer
Studio), followed by clicking on the search icon (🔍) as shown below.
The following shows the list of rules
matching your search.
Since we are looking for Operator ID, click
on the “aesdeveloper”
of the “Operator ID” row, which will open the aesdeveloper operator rule.
You will notice that the "Force password change on next login" and "disable Operator" are both ticked.
To make things simple (for development and
learning purposes), you should untick these. However, if you were to untick
both at the same time and save, you would get the following error message:
To resolve this, tick only the Force password change on next login, and
click the “Save” button to save it. Once saved, untick the Force password
change on next login, and click the “Save”
button again.
Close this rule, and logout of Designer
Studio, then login as aesdeveloper again, with the default password of password (if you have not changed it) to continue the next section.
Verifying the Installation of Rulesets
After you have login as aesdeveloper, (depending on your
versions and settings, you might be asked to change the password, if so, follow
the instruction accordingly).
💡
|
If you
had unticked the “Force password change on next login”, you will not be
prompted to change the password. For development and training systems, you
might just want to use the default password for this user (i.e. password) or
change to the generic “rules” password. No matter what you decide, always
remember the password.
|
💡
|
If you
had forgotten any operator password, just follow the instruction in the
earlier section: “Unable to Login as aesdeveloper” and click on the “Update
password” button shown there. This only works for Pega managed
authentication, other forms of authentication are managed externally and is
beyond the scope of this guide.
Note
once again, this is meant for training purposes.
|
After you have successfully login, you
should notice that the application is “AES”:
In Designer Studio, click: Designer
Studio > Application > Structure > RuleSet Stack, as shown
below.
In the opened form, verify that the
following ruleset versions are listed:
· PegaAESCriteria:01-01-01 · PegaAES:07-30-01
💡
|
The
instruction in the Pega documentation stated PegaAES:07-30-01”, but mine is “PegaAES:07-30-20”.
That does not matter since mine is of a newer version.
|
If your system does not contain the latest
rulesets, the installation was not completed successfully. You need to contact
Pega support for assistance.
Testing the AES Install
While still in Designer Studio, launch
either the AES User Portal or the AES Manager Portal as shown below:
You should be able to see the respective
portal, like the following:
Note that the “Current System” drop-down
list does not contain anything. This is because you have not added any
monitored system yet!
