LoadRunner monitoring Weblogic and J2EE configuration practices in windows through jxm

 

Control side Configuration:

 

1. Copy the Lib folder (D: \ Bea \ weblogic81 \ Server \ Lib \ WebLogic) under the Weblogic installation directory. jar) weblogic. jar to the LR root directory classer folder (specifically: C: \ Program Files \ Mercury Interactive \ Mercury LoadRunner \ Classes );

 

2. Delete jmxri. jar in the LR root directory (specifically: C: \ Program Files \ Mercury Interactive \ Mercury LoadRunner \ Classes)

 

3. under DAT/monitors of LR (specifically: C: \ Program Files \ Mercury Interactive \ Mercury LoadRunner \ dat \ monitors \ weblogimon. INI) specifies the JVM path and version, pointing to the latest virtual machine of the current system. 1.4.2 is recommended:

 

JVM = c: \ Program Files \ Java \ j2re1.4.2 _ 04 \ bin \ javaw.exe
Javaversion = 1.4.2

 

You can also modify the monitoring port in the weblogimon. ini file, for example:

 

WebLogic = weblogic. Jar
Port = 7001

 

Configuration of Weblogic Machine

 

1. Create a new user in the Weblogic console Security user, Set Name To weblogic. admin. mbeam, and set the password as needed;

 

2. Add the group of the current user as needed (if you do not know it, you need to grant this user the permissions for the administrators and monitors groups );

 

3. Set WebLogic (jxm) under control in lr to add a monitor, and enter IP: Port in name. For example (10.19.129.15; or 192.168.1.127: 7001)

 

4. After confirmation, enter the user name and password created in the console. After confirmation, you can open the BEA monitor selection interface.

 

Install and configure j2ee_monitors when monitoring J2EE

 

1. Find the j2ee_monitors installation package.

 

2. Create a directory on the hard disk, such as merc_monitor_home.

 

3. decompress the \ add-ins \ monitors \ J2EE \ windows \ jmonitor_nt.jar (Windows) file on the installation disk to this directory. If there is no decompression tool, use the following method: \ bin \ jar.exe-XF if jmonitor_nt.jar is not in the merc_monitor_home directory, add the complete directory.

 

(In UNIX, use the jar utility to extract and install the jar: Go to the merc_monitor_home [directory created above] Directory and type the following command: jar-xvf jmonitor_nt.jar ), if jmonitor_nt.jar is not in the merc_monitor_home directory, you need to add the complete directory. unzipping them in Unix may lose their execution permissions. To fix this error, open the directory where jmonitor_nt.jar is located, then use the following command line to change the permission: chmod + x *. SH)

 

4. Double-click merc_monitor_home [directory created above] \ Classes \ sipatool. Jar (the Directory and file are only available after decompression) to open mercury. J2EE monitor initializer.

 

(If you cannot double-click a button on a UNIX platform, perform the following operations:

 

Merc_monitor_home [directory created above] \ Classes \ directory, type Java-jar sipatool. Jar) [This can also be done in Windows]

 

4. The main directory for running Java has been displayed in the pop-up interface. If it is not displayed, manually add it.

 

5. The remaining work is to add the installed monitoring directory and monitoring program to the Weblogic STARTUP configuration file as follows:

 

A. Back up the weblogicstart. CMD file and obtain a new name, which is usually weblogicstartmercury. cmd. Set the monitoring home directory, for example, set merc_monitor_home = c: \ j2ee_monitors.

 

B. Add the monitoring path to the startup path, for example, % merc_monitor_home % \ dat; % merc_monitor_home % \ Classes \ xerces. jar;

 

The following is a fully configured weblogicstartmercury. CMD file:

 

@ Echo off

 

@ REM warning: this file is created by the Configuration Wizard.
@ REM any changes to this script may be lost when adding extensions to this configuration.

 

Setlocal

 

@ REM ************************************** ***********************************
@ REM this script is used to start Weblogic server for the domain in
@ REM current working directory. This script simply sets the SERVER_NAME
@ REM variable and starts server.
@ Rem
@ REM to create your own start script for your domain, all you need to set is
@ REM SERVER_NAME, then starts the server.
@ Rem
@ REM other variables that startwls takes are:
@ Rem
@ REM wls_user-cleartext user for server startup
@ REM wls_pw-cleartext password for server startup
@ REM production_mode-true for production mode servers, false
@ REM Development Mode
@ REM java_options-Java command-line options for running the server. (These
@ REM will be tagged on to the end of the java_vm and mem_args)
@ REM java_vm-the Java Arg specifying the VM to run. (I. e.-server,
@ REM-hotspot, etc .)
@ REM mem_args-the variable to override the standard memory arguments
@ REM passed to Java
@ Rem
@ REM for additional information, refer to the Weblogic server administration
@ REM console online help (http: \ e-docs.bea.com \ WLS \ docs81 \ consolehelp \ startstop.html)
@ REM ************************************** ***********************************

 

@ REM initialize the common environment.

 

Set wl_home = c: \ Bea \ weblogic81
For % I in ("% wl_home %") do set wl_home = % ~ FSI

 

Set production_mode =

 

Set java_vendor = Bea
Set merc_monitor_home = c: \ j2ee_monitors

 

Set java_home = c: \ Bea \ jrockit8sp4_142_05
For % I in ("% java_home %") do set java_home = % ~ FSI

 

@ REM call commenv here after setting the java_vendor to get common environmental settings.

 

Call "% wl_home % \ common \ bin \ commenv. cmd"

 

@ REM set SERVER_NAME to the name of the server you wish to start up.

 

Set SERVER_NAME = myserver

 

Set classpath = % weblogic_classpath %; % merc_monitor_home % \ dat; % merc_monitor_home % \ Classes \ xerces. jar; % pointbase_classpath %; % java_home % \ JRE \ Lib \ RT. jar; % wl_home % \ Server \ Lib \ WebServices. jar; % classpath %

 

@ REM call WebLogic Server

 

Echo.
Echo classpath = % classpath %
Echo.
Echo Path = % PATH %
Echo.
Echo *************************************** ************
Echo * to start WebLogic Server, use a username and *
Echo * password assigned to an admin-level user. *
Echo * server administration, use the WebLogic Server *
Echo * console at http: \ [hostname]: [port] \ console *
Echo *************************************** ************

 

% Java_home % \ bin \ Java % java_vm % mem_args % java_options %-xbootclasspath/P: % merc_monitor_home % \ Classes \ Boot-dweblogic. name = % SERVER_NAME %-dweblogic. productionmodeenabled = % production_mode %-djava. security. policy = "% wl_home % \ Server \ Lib \ weblogic. policy "weblogic. server

 

Endlocal
/// Source Network