Martin Spier's Blog

Here is a very useful tip shared by my friend Odorico:

LoadRunner doesn’t provide native interface to WebLogic 9 and  10 (only to 8.1FP4) and SiteScope just do it using RMI-IIOP.

So before configuring such monitor, is good to get the Dev/Infra team aware of the monitoring request. They need to check and enable RMI IIOP features inside weblogic.

Here are the steps:

On the WebLogic Server:

Before edit any field on Weblogic you need click in “Lock & Edit”. When you finish all configuration settings, it is necessary click in “Active Changes” to put changes in place.

1. Enable RMI-IIOP protocol:
2. At Domain’s Security section, check if “Anonymous Admin Lookup” is enabled
3. For the service/server you’re monitoring, at service’s Settings, Protocols, IIOP, enable IIOP and in advanced configuration, set up IIOPUserName and IIOPPassword to weblogic’s admin credentials
4. Maybe a restart will be required

On the JMX Client

1. Make sure you will be running a JAVA VM at version 1.5 or above.
2. When activating the JMX client (jconsole, for example) add the following parameter:

-J-Dcom.sun.CORBA.transport.ORBTCPReadTimeouts=10:60000:500:10

3. This will change the timeouts for the CORBA protocol (remember we’re getting JMX from a WebLogic, so it goes thru RMI-IIOP)
4. Example:

H:\>jconsole -J-Dcom.sun.CORBA.transport.ORBTCPReadTimeouts=10:60000:500:10

5. Use the following URL pattern:

service:jmx:rmi:///jndi/iiop://YOURSERVERADDRESS:PORT/weblogic.management.mbeanservers.runtime

6. When asked for a Username and Password, give the RMI IIOPUsername/Password given in server configuration.

Related posts:

1. Configuring WebLogic JMX on LoadRunner Controller
2. How to Obtain an ICA File Through Citrix Web Interface 4.5 and 4.6