When I try to monitor WebLogic server, I get the "Check the user has 'Administrators' permission to deploy the agent in WebLogic server" message
The user needs to have Administrator privileges to monitor a WebLogic server. This is because Applications Manager will deploy an agent in the WebLogic server for data collection. A user should have Administrator privileges to deploy this agent.
Follow the steps below to associate 'Administrators' role to the user in WebLogic console:
- Go to Security->Realms->myrealms->Users
- Click on specified user->Groups tab
- Assign to Current/Chosen groups from the available groups.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...Mail Server Monitor - Troubleshooting
Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...When I monitor the WebLogic server, I get the "Data Collection in progress. Please wait till the next poll interval" message.
Solution 1 Check if the WebLogic server host is able to connect to Applications Manager as we connect in the browser. i.e. http://<ApplicationsManager hostname>:<portNumber> should be reachable. Also check whether any errors or exceptions are ...REST API Monitor - FAQS
1. What should I do when Basic Authentication fails in REST API monitor? Verify if the credentials provided in the Applications Manager are correct. Try if sending username and password in Authorization request header works Get an BASE-64 encoded ...