I am not able to perform any activity in Applications Manager's Web Client. Why?
You may have logged into Applications Manager with user access as 'Operator'. With the Operator role, you can only view Monitor details. You will not have the privilege to configure or edit the different components of the product.
Solution: To work with or configure the product, log in as 'Admin' user. For more information on user access, refer to the User Administration section in the User Guide.
New to ADSelfService Plus?
Related Articles
When I try to access Applications Manager;s web client, I am getting the error "The Page cannot be displayed". I am not able to access any page in Applications Manager.
Apache uses the sendfile syscall on platforms where it is available in order to increase the speed of sending responses. Unfortunately, on some systems, Apache will detect the presence sendfile at compile time, even when it does not work properly. ...Disable HTTP access in Applications Manager
Overview This article describes configuring a secure connection between Applications Manager server and the browser/client. Applications Manager can be accessed through any of the following URLs: For HTTP -> http://[hostname/ip-address]:[http-port] ...Integrating PagerDuty with Applications Manager using Webhook
Using Webhook, you can now integrate PagerDuty with Applications Manager and receive real-time alerts on incidents right into your PagerDuty instance. Step 1: Configuring PagerDuty Open the required PagerDuty instance to which Applications Manager ...I am unable to access Applications Manager web client through Internet Explorer browser. The error message says "your host name has non-standard characters".
Solution: Check if your host name contains any non-standard characters such as ”_”, “,”, “.”, ”@”. If any of these characters are present in your host name, Internet Explorer will block any attempts to set cookies on such domains. Refer this link to ...How do I change the timeout for Applications Manager web client session?
Solution: By default, the login timeout (session-timeout) is set to 20 minutes. To modify this setting, locate the web.xml file in the <AppManager_Home>/working/apache/tomcat/conf directory. Find the following tag within the file: ...