Here is a tip shared by my friend Daisy:
The WebLogic SNMP monitor is enable in the Controller as default. If you need to monitor Weblogic JMX, you have 2 options:
- Use the SiteScope as a monitoring tool instead of Controller;
- Enable the Weblogic JMX monitor into Controller.
- To do this you will have to configure online_resource_graphs.rmd file – located under <LoadRunner DIR>\dat\online_graphs: update the EnableInUi param of the relevant monitor (i.e. for WebLogic (JMX): search for the [WebLogicJMX] section and update its EnableInUi param).
- Also, you might need to install java jdk on Controller (I didn’t have chance to test it):
WebLogic Monitor Requirements and Setup
- JDK 1.4 on controller
- Permissions on WebLogic MBeans.
Setup on Controller
- After JDK installation Copy weblogic.jar from the lib folder of WebLogic Server to LoadRunner root\classes.
- Remove jmxri.jar from LoadRunner root \classes.
- Specify the path in the LoadRunner root folder\dat\monitors\WebLogicMon.ini file. Edit the JVM entry in the [WebLogicMon] section. For example: JVM=”E:\Program Files\JavaSoft\JRE\1.4\bin\javaw.exe
- Edit the JavaVersion entry in the [WebLogicMon] section.
Set permissions on WebLogic
- Open the WebLogic console (http://<host:port>/console).
- In the tree on the left, select Security > Realms > myrealm > Users, and click Configure a new User… in the screen on the right. The Create User: General tab opens.
- In the Name box, type weblogic.admin.mbean, enter a password, confirm the password, and then click Apply.
- In the Groups tab, enter the name of any user or group you want to use for monitoring, and then click Apply.