
TestView Installation Instructions
Make sure you have at least 260 MB of available disk space for the complete installation of TestView.
When you install TestView on your computer, the installation program asks you for the components to install. Install just the Probing Client or the Load Machine software on the network host computers. Do not install the full product on the network host computers.
Note:
1. To successfully run TestView and all of its components, ensure that all previous WebLOAD and WebFT installations are removed before installing TestView.
2. The TestView license file is limited to the computer system (machine) on which TestView is initially installed. Before installing TestView, make sure you are installing on the machine you intend on working with.
3. WebRM and TestView should not be installed on the same machine. In instances where WebRM and TestView are installed on the same machine, TestTalk must be executed manually from the TestView installation before running WebLOAD or WebRM.
TestView Installation Instructions
- Browse to the location of the TestView executable (.exe) installation file.
- Double-click the file. The TestView Installation Wizard appears.
- Follow the instructions on your screen. When the Installation Wizard prompts for the component to install, select the desired component. For Load Machines and Probing Clients, select Load Generator / Probing Client.
- When the TestView Installation Wizard is finished the License dialog box opens with two tabs, Host ID and Select License. Select the Host ID tab. Note that you may be prompted to restart your computer before the License dialog box appears. In such cases, the License dialog box will appear after the computer has restarted.
- Copy the Host ID displayed in the text box into an email, along with your name, company, address and phone number and send the email to
license@radview.com.
- A TestView license file (*.lic) will be sent to you. After receiving the file, save it to your hard drive in the Program Files\RadView\TestView\License directory.
- Select Start | Programs | TestView | Tools | Update License to open the Update License dialog box and install the license key.
- On the Select License tab, browse for the location of the *.lic file sent to you by a RadView representative. Select the file, and click OK to load the new license and run TestView. Then you can begin working with TestView.
Note:
Load Machines can also be installed silently by running the installation file with the following parameter /s /lg.
For example:
WebLOAD-v7.0.100.00-Product-ssl128.exe /s /lg
During the installation process, no information is displayed on the screen. Please allow 5 minutes for the installation to complete.
Solaris and Linux Platform Installation Instructions
The Load Generator software is supplied as a compressed tar file with the name
webload-<platform>-<version>-<sslsupport>.tar.Z.
Examples: webload-solaris-v7.0.100.00-ssl128.tar.Z
webload-linux-v7.0.100.00-ssl128.tar.Z.
To install the Load Generator software complete the following steps:
- Choose or create a directory into which to install WebLOAD. This directory will be referred to hereafter as the "software root".
- Download the compressed file from a server or copy the file from the WebLOAD product CD to the "software root". Note that some browsers may change the name of the compressed tar file from <tarfile>.Z to <tarfile>.z. If your browser does this, then you must rename the file to <tarfile>.Z before performing the following commands.
- Change directory to your "software root" directory (referred to here as ~). (cd ~).
- Uncompress and extract the tar file using the following command:
zcat <name of file>.Z | tar xf -
If this command is not supported by your version of Unix or Linux perform step 5. If it is supported, go to step 6.
- Uncompress the WebLOAD tar file using the command:
uncompress <name of file>.Z.
Untar the resulting tar file using the command:
tar xf <name of file>.tar
- The installation procedure above creates the following directory structure:
radview/webload<version>
/<platform>/bin
/frm
/docs
/User/Log
/LiveConnect/classes/netscape/javascript
- Run setup from the /<platform>/bin directory.
a. During setup you are prompted to enter a value for the DISPLAY variable while suggesting the local station name as a reference. Insert a new value of DISPLAY if necessary and press Enter.
Note that if the selected DISPLAY is not valid, a message is displayed with the option to enter a new value or continue with the selected value. If the value is wrong it can later be corrected using the ./env_setup utility in the <platform>/bin directory before starting testtalk.
IMPORTANT: If the defined DISPLAY is correct but does not allow connections, setup may freeze during the DISPLAY validity check. In such a case, use Ctrl-C to stop it. There is no need to run setup again, just check the accuracy of the DISPLAY and use ./env_setup utility to complete the installation.
b. After the DISPLAY setting, you are prompted to set a path to the java runtime libraries while setup prompts the path of the java libraries that comes with installation. If another version of java is preferred enter it's path when prompted using the following pattern:
For Solaris:
[prompt] /usr/java/jre/lib/sparc:/usr/java/jre/lib/sparc/server:/usr/java/jre/lib/sparc/native_threads
For Linux:
[prompt] /usr/java/jre/lib/i386:/usr/java/jre/lib/i386/server:/usr/java/jre/lib/i386/native_threads
should be replaced with local JAVA installation path. The directories containing the java libraries are separated with a colon `:'.
Note: WebLOAD Load Generator will not function properly without correct java libraries paths.
- To start the TestTalk kernel run starttesttalk from the /<platform>/bin directory. DISPLAY and java library path variables that were set during setup are used to create the application environment. Any required changes should be made using the ./env_setup utility.
Note: To check the settings, run ./env_setup. The current settings appear as defaults and can be changed as required.
- To stop running TestTalk run stoptesttalk from the /<platform>/bin directory.
Tuning your Solaris Load Generator System for Optimal Performance
Solaris Load Generator systems should be modified as follows for optimized system performance:
Note: You must be logged in as root to use these commands.
 | Load Generators running on versions earlier than Solaris 7 enter the following command:
ndd -set /dev/tcp tcp_close_wait_interval 30000
|
 | Load Generators running on Solaris 7 and later, enter the following command:
ndd -set /dev/tcp tcp_time_wait_interval 30000 |
Note that the above setting will be lost when your Solaris system is restarted. In order to have this value set correctly at system startup, you will have to do the following while logged in as root:
- Create a startup script in /etc/rc2.d named S99<xxx>, where <xxx> is an arbitrary name.
- Add the ndd command shown above that is appropriate for your operating system to this script.
- Make the script executable.
For example, for a Solaris 7 system, the following sequence of commands could be used to create the script file and set its permissions correctly:
echo "ndd -set /dev/tcp tcp_time_wait_interval 30000" > /etc/rc2.d/S99ndd_tcp chmod +x /etc/rc2.d/S99ndd_tcp
For additional information on startup scripts, see /etc/init.d/README on your Solaris system.
Tuning your Linux Load Generator System for Optimal Performance
For correct execution of WebLOAD Agendas containing ftp and udp protocols, the station ip address must appear in /etc/hosts file.
- If your Linux Load Generator is failing with "Connection failed...... Reason -: Error number: 11" diagnostics, then the local port range will have to be increased on your Linux system. This is done while logged in as root with the following command:
/sbin/sysctl -w net.ipv4.ip_local_port_range="<lower limit> <upper limit>"
For example, a typical range for a standard installation of redhat 6.2 has a lower limit of 1024, and an upper limit of 4999. We suggest that the upper limit be set to 15000 as a minimum.
The command to set the upper limit to 15000 is:
/sbin/sysctl -w net.ipv4.ip_local_port_range="1024 15000"
To verify that you have set the port range correctly, use the command:
/sbin/sysctl net.ipv4.ip_local_port_range.
Note that the above setting will be lost when your Linux system is restarted. In order to have this value set correctly at system startup, we suggest that you add the following line to the file /etc/rc.d/rc.local. Note that you must be logged in as root in order to do this.
/sbin/sysctl -w net.ipv4.ip_local_port_range="1024 15000"
- If you receive the message "connection refused" do one of the following:
- Change the number of file descriptors dynamically - as root "echo 409600 > /proc/sys/fs/file-max". This will increase the number of available file descriptors on the machine. You need to change the number of file descriptors every time you reboot the machine.
or
- Recompile the kernel.
Modify the file /usr/src/linux/include/linux/fs.h and change the line (should be near line 52) "#define NR_FILE 4096" to "#define NR_FILE 409600".
- Upgrade the physical memory of the Linux Load Machine (at least 256 MB is recommended in order to run more than 500 virtual clients).
- To run more that a 1024 Virtual Clients do one of the following:
- Recompile the kernel. Modify the file /usr/src/linux/include/linux/tasks.h and change the line (should be near line 14) "#define NR_TASKS 1024" to "#define NR_TASKS 4090".
This increases the number of available processes to 4090 instead of 1024.
For details about how to compile the kernel, refer to redhat help or kernel-howto.
or
- Update your machine to Kernel 2.4 or later. Refer to redhat help or kernel-howto for details on upgrading your kernel.
Running Java with a Solaris or Linux Load Generator
The CLASSPATH environment variables must be set correctly in order for a Solaris or Linux Load Generator to work with Java.
- Setting CLASSPATH
The CLASSPATH environment variable is used to tell Java where to find your classes. Set CLASSPATH using the following command from csh:
setenv CLASSPATH path1[:path2]...
The paths specified in this command are paths to .jar, .zip, or .class files. For a .jar or .zip file, the path is the full pathname of the .jar or .zip file. For a .class file, the path is the path of the directory that contains the .class file. Note that paths are separated by the colon character on Unix or Linux.
Note: After any time you change the CLASSPATH environment variables, you must stop TestTalk and then restart TestTalk so that the new values take effect.
Installing SNMP Service on a Solaris Platform
SNMP service is automatically installed in Solaris version 8 and later. If you have a version of Solaris prior to version 8, you must install an SNMP agent. Sun's official SNMP agent is Sun Solstice Disksuite 4.1, although other SNMP agents are available as free or shareware.
To start SNMP service on Solaris:
The procedure for starting SNMP service may vary depending on your SNMP agent and your configuration. The instructions below are presented as an example.
- From the command line, go to the directory containing your SNMP executable file. Usually this directory is /etc/init.d.
- Type ./init.snmpdx start and press Enter. SNMP service is started. You can now access Solaris hosts in WebLOAD Console via SNMP.
Installing SNMP for WebLogic
The WebLogic SNMP agent will not work as a subagent for the OS master agent. The workaround is to make WebLogic act as master (on port 161) and delegate to the native OS agent.
- Modify winnt\system32\drivers\etc\services file from:
....
snmp 161/udp
.....
to:
snmp 1161/udp (any free port will do here)
- Modify the startsnmpagent.cmd file in the WebLogic root, e.g. %JAVA% weblogic.SNMPAgent -password mypassword -serverURLs t3://localhost:7001 -snmpPort 1161 -trapDestinations localhost:162 -otherAgents 1161:.1.3.6.1.2.1.
 | The -snmpPort 1161 makes WebLogic the master agent. The -otherAgents 1161:.1.3.6.1.2.1. tells this agent to delegate the 1.3.6.1.2.1 subtree to port 1161 (where the native agent is running).
|
 | Run this file and ensure the agent is restarted on the 1161 port. Use system command netstat -a -n -p udp to view the active udp ports. Both udp 161 and udp 1161 should appear in the resulting list. The WebLogic appserver should be running. |
 | winnt\system32\drivers\etc\services file from:
....
snmp 161/udp
.....
to:
snmp 1161/udp (any free port will do here) |
On the ORACLE machine perform following steps:
- Modify oracle\ora81\network\admin\encaps.cfg file, by adding the following line
 | AGENT AT PORT 1161 WITH COMMUNITY PUBLIC
|
- Modify oracle\ora81\network\admin\master.cfg file specifying that ORACLE runs on port 161
- Start following services
 | OracleSNMPPeerMasterAgent
|
 | OraclePeerEncapsulator |


