I'm not able to add WebLogic monitor. What could be the reason?
Please verify if you have followed all the below prerequisites before adding WebLogic monitor :
1. HTTP port of WebLogic server should be accessible from Applications Manager installed machine.
a. Check if the WebLogic host and port is accessible via TELNET.
b. Check if there is any firewall between WebLogic Host and the Applications Manager machine. If this is the case, then open WebLogic host and port in the Applications Manager side.
2. For monitoring your WebLogic server, the user need to have 'Administrator' privileges.
To assign 'Administrator' privilege to a user in WebLogic, refer here.
3. Applications Manager does a JNDI lookup to get the Mbeanserver. So please check whether the configured user has the permission to do a JNDI lookup
a. Access the JNDI Tree security policy from WebLogic Admin console by navigating to Admin console -> Environment -> Servers -> <Required server> -> View JNDI Tree-->Security-->Policies-->Methods.
b. Under Methods, it should be 'ALL'.
4. Make sure the same Host/IP which is configured in Listen Address in WebLogic server is used while adding the monitor in Applications Manager.
You can find the host/IP address of the same under Environment -> Servers -> <Required server> -> Configuration -> General -> Listen Address field.
5. T3 connection is should be possible from Applications Manager machine to WebLogic server.
a. Enable T3 Tunneling by following the steps mentioned here.
b. Check if the webLogic server is responding to T3 ping. Try to execute the below command from some other installation of WebLogic machine ( <WebLogic_HOME>/wlserver/server/lib directory ) to this WebLogic machine.
java -classpath weblogic.jar weblogic.Admin -url "t3://hostname:portnumber" -username <Username> -password <Password> ping
6. Check whether the /etc/resolv.conf file (in windows it is Windows\System 32\drivers\etc\hosts file) in the Applications Manager Machine has correct domain.
a. Make sure there is no incorrect resolution present for WebLogic server host.
7. Check whether Filters are enabled in Weblogic domain, and Applications Manager Host/IP is restricted.
- <mydomain> -> Security -> Filter
8. The jars might be either corrupted or outdated.
For version 12 and above, some WebLogic servers requires fullclient jars. Please use the jars below :
New to ADSelfService Plus?
Related Articles
Self monitor Applications Manager using Real User Monitoring
We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...How to add WebLogic monitor over SSL ?
For monitoring WebLogic servers using SSL port, you will have to load the SSL certificate to Applications Manager. Follow the below steps to load SSL certificate in Applications Manager: Load the certificate to Applications Manager using ..."Failed Exception : Connection failure" while trying to add WebLogic monitor
Check whether the WebLogic host and port is accessible via TELNET. Check if you have used the configured listener address while trying to add the monitor. Listener can be obtained under Environment -> Servers -> <myserver> -> Configuration -> General ...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 ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...