We are trying to customize the tenant URL for our AES 8.3 installation so that users can directly login to the tenant configured with a simple URL. Here is what we did,
1) We installed AES 8.3
2) We have created Tenant for our application to monitor.
3) We have configured our candidate systems to push data to the AES tenant.
4) AES is working fine as the application monitoring.
AES tenant has a separate URL as
AES Pega URL:
We want the tenant URL as
So that the AES users can directly land on the tenant and access the application monitoring data.
In short, we don't want tenant specific hash to identify the tenant separately.
Please let me know if anyone can help.
***Edited by Moderator Marije to add Capability tags***
@SoumyadyutiP8692 is your concern just the logon URL or the runtime URL? If logon URL, consider using load balancer rules to redirect https://[XYZ.com]/ to https://[abcd.com]/prweb/PRServlet/beEBp4uRVTogorRwSwWqbAsjpvPPkMOjtugocijmN-s*/!STANDARD
Posted: 6 months ago
Posted: 14 Mar 2022 9:14 EDT
Andy Werden (WERDA)
Senior Director, Product Management, Observability Services
I think you could do that from both load balancer rules or customizing @baseclass*Web-Login with some redirect logic - logging in with just URL and no hash puts one in shared layer; inspect the URL and redirect to the appropriate tenant hash for the URL