Configuring The Sitescope and Weblogic Servers
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.
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.
Enable RMI-IIOP protocol:
At Domain’s Security section, check if “Anonymous Admin Lookup” is enabled
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
Maybe a restart will be required
On the JMX Client
Make sure you will be running a JAVA VM at version 1.5 or above.
When activating the JMX client (jconsole, for example) add the following parameter:
-J-Dcom.sun.CORBA.transport.ORBTCPReadTimeouts=10:60000:500:10
This will change the timeouts for the CORBA protocol (remember we’re getting JMX from a WebLogic, so it goes thru RMI-IIOP)
Example:
H:\>jconsole -J-Dcom.sun.CORBA.transport.ORBTCPReadTimeouts=10:60000:500:10
Use the following URL pattern:
service:jmx:rmi:///jndi/iiop://YOURSERVERADDRESS:PORT/weblogic.management.mbeanservers.runtime
When asked for a Username and Password, give the RMI IIOPUsername/Password given in server configuration.
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.
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.
Enable RMI-IIOP protocol:
At Domain’s Security section, check if “Anonymous Admin Lookup” is enabled
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
Maybe a restart will be required
On the JMX Client
Make sure you will be running a JAVA VM at version 1.5 or above.
When activating the JMX client (jconsole, for example) add the following parameter:
-J-Dcom.sun.CORBA.transport.ORBTCPReadTimeouts=10:60000:500:10
This will change the timeouts for the CORBA protocol (remember we’re getting JMX from a WebLogic, so it goes thru RMI-IIOP)
Example:
H:\>jconsole -J-Dcom.sun.CORBA.transport.ORBTCPReadTimeouts=10:60000:500:10
Use the following URL pattern:
service:jmx:rmi:///jndi/iiop://YOURSERVERADDRESS:PORT/weblogic.management.mbeanservers.runtime
When asked for a Username and Password, give the RMI IIOPUsername/Password given in server configuration.
LoadRunner Training in Bangalore
LoadRunner Training in Hyderabad
LoadRunner Online Training
LoadRunner Training in BTM
LoadRunner Training in Marathahalli
Best LoadRunner Training Institutes in Bangalore
Best LoadRunner Training Institutes in India
Training Institutes in Bangalore
No comments:
Post a Comment