| Oracle® Load Testing for Web Applications Load Testing User's Guide Version 9.00 for Microsoft Windows (32-Bit) Part Number E15484-01 |
|
|
View PDF |
| Oracle® Load Testing for Web Applications Load Testing User's Guide Version 9.00 for Microsoft Windows (32-Bit) Part Number E15484-01 |
|
|
View PDF |
This chapter explains how to get started using Oracle Load Testing for Web Applications. It explains how to install and start the program, and the features of the main window.
The installation for Oracle Load Testing for Web Applications depends upon how you plan the virtual user test configuration. At a minimum, you need to install Oracle Load Testing for Web Applications on a single system that can access the Web application. If you are performing distributed testing in a networked environment, you need to install at least one station with Oracle Load Testing for Web Applications to use as a "Master" station and install the Oracle Load Testing for Web Applications Agent (or another seat of Oracle Load Testing for Web Applications) on the client machines to use as virtual user Agent stations.
The following sections explain the procedures for installing Oracle Load Testing for Web Applications and the Oracle Load Testing for Web Applications Agent.
The Oracle Load Testing for Web Applications setup procedure installs both Oracle Load Testing for Web Applications Server and Oracle Load Testing for Web Applications Agent. You should not install Oracle Load Testing for Web Applications Agent separately on the same system. To install Oracle Load Testing for Web Applications:
Go to: http://www.oracle.com/technology/software/products/app-testing/index.html.
Download the Oracle Application Testing Suite product from the Oracle Web site and save it to a temporary directory on your hard disk.
Unzip the the download file and then run oats###.exe.
Follow the setup instructions to install the Oracle Application Testing Suite. The install program will install the WebLogic web server and the Oracle 10g Express Edition Database by default. If you chose to have the install program use an existing Oracle database, follow the instructions for using an existing database below.
Select Oracle Load Testing for Web Applications from the Oracle Application Testing Suite start menu to start the Oracle Load Testing for Web Applications user interface.
Oracle Load Testing for Web Applications starts in an existing browser if one is available. To set Oracle Load Testing for Web Applications to always start in a new browser window, change the Reuse windows for launching shortcuts setting in Internet Explorer to be deselected. In IE, select Internet Options from the Tools menu then click the Advanced tab to change the setting under Browsing from the Advanced tab to access this setting.
If you choose to use an Oracle Database 11g Enterprise Edition existing database during the installation procedure, use the following instructions to setup the database for use with the Oracle Application Testing Suite.
Install the Oracle Database 11g Enterprise Edition and create a user with a minimum of the following privileges:
Create/Alter/Drop Tables
Create/Drop Views
Create/Alter/Drop Sequences
Create/Alter/Drop Triggers
Create/Alter/Drop Indexes
If you are performing the database administration yourself, use the following steps:
Log Into Database Control
Install the Oracle Database 11g Enterprise Edition and launch Database Control.
Login to Database Control as a user with "system" privileges.
Create a Tablespace
Click the Server tab.
Click Tablespaces.
Click Create.
On the General tab, give the tablespace a name.
Under Datafiles, click Add. Specify a file for the new tablespace. Set the file size to 1000 MB.
Click Continue.
Click OK to create the new tablespace
Create a User
Return to the database instance, Server tab and click Users
Create a new user ("ATSuser"). During user creation, designate the user's default tablespace to the one created above. On the Roles tab, assign the user the RESOURCE role. On the System Privileges tab, add the required system privileges defined above to that user.
Click OK to create the new user.
The following instructions explain how to setup an exsiting Oracle database for use with the Oracle Application Testing Suite.
Oracle Test Manager for Web Applications
Install the Oracle Database 11g Enterprise Edition Client OR
The Oracle Database Instant Client:
Basic Package, AND
ODBC Supplement
Note:
Read the ODBC Release Notes for specific configuration instructions, including the need to add the Instant Client directory to the PATH environment variable and the creation of the TNS_ADMIN environment variable.Create a text file called tnsnames.ora inside the folder defined by the TNS_ADMIN environment variable. The text file should contain the following text (to connect to an Oracle DB on a system with the name oracledbsys):
oracledbsys =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracledbsys.example.com)(PORT = 1521))
)
(CONNECT_DATA =
(SID = ORCL)
Create a DSN pointing to the Oracle DB Server, as follows:
Open the Control Panel from the Start menu.
Open the Administrative Tools and select Data Sources (ODBC)
Double-click Data Sources (ODBC) and select System DSN
Click Add and select the Oracle DB driver
Click Finish to select this DB driver
In the "Oracle ODBC Driver Configuration" dialog box enter the following information:
Data Source Name: <ANY name of your choice>
Description: optional
TNS Server Name: oracledbsys (correlating to the contents of tnsnames.ora. Use the appropriate TNS name you have given.)
User Id: the username assigned to you on the DB server
Click Test, enter the password for your username and click OK
If the test is successful, you can proceed.
Oracle Load Testing for Web Applications
Log into OLT http://systemname:8088/olt
Select Databases from the Manage menu then select New
Select Oracle from the drop-down list.
If you wish to create new tables in a schema, select the radio button for Create tables in the Database . If you wish to connect to an existing schema that has OLT tables in it, select the User existing database (default).
Enter the relevant database connection information in the fields.
Click OK
Note:
An SQL file is available on the Oracle Application Testing Suite system that can be used, if necessary, to delete the database components created by the product. (This will result in loss of data!) The file is delete tables.sql and is located in the <installdir>\OTM\Files\Oracle directory. This SQL can be executed in SQL Developer or similar utility for Oracle DB management.Popup blockers must be turned off for Oracle Load Testing for Web Applications to operate. To turn off popup blockers:
Firefox - Select Options from the Tools menu. Uncheck Block Popup Windows.
Internet Explorer - Select Pop-up Blocker from the Tools menu. If the pop-up blocker is on, select Turn Off Pop-up Blocker.
If you are using a firewall between the Oracle Load Testing for Web Applications Server machine and the agent machines, port 9001 must be open in your firewall software itself and on the agent machines. To change this port on the agent machine, change the wrapper.app.parameter.2 setting in the <installdir>\agentmanager\bin\AgentManagerService.conf file. In addition, change the port in the system configuration in Oracle Load Testing for Web Applications by selecting Systems from the Manage menu then selecting VU Agent Systems. Select the agent machine that is running on a different port, click Edit, and change the default port 9001 to the port that you set in the AgentManagerService.conf file.
To run Oracle Load Testing for Web Applications, it is recommended that you have the following general communication ports open before starting the Oracle Load Testing for Web Applications Application Service.
http=8088 agent=9001 dataCollector=7073 webservice=8083 https=8089
To change the ports:
Go to http://localhost:8088/console to start the WebLogic Console.
Log in as administrator using the password you defined during the Oracle Application Testing suite installation procedure.
In the Domain Structure, select Environment under "oats" and then select Servers.
Select AdminServer(Admin).
Change the port and release the config.
For more information about these settings, refer to Appendix C. See the Oracle WebLogic Server documentation for additional information about using the Console application.
The following ports are used between the Oracle Load Testing for Web Applications Server and the Agent Machine itself:
9001
7073 - Data Collector
8088 for running OpenScript scripts only
The Oracle Load Testing for Web Applications Agent is a subset of the full Oracle Load Testing for Web Applications installation. You should not install the Oracle Load Testing for Web Applications Agent if you have Oracle Load Testing for Web Applications installed on the system. You install Oracle Load Testing for Web Applications Agent on the agent systems (which should be Windows 2000/2003 machines) when you want to run distributed load tests in a network environment and you want the agent systems to have more system resources available for running virtual users. To install the Oracle Load Testing for Web Applications Agent:
Run the downloaded oats###.exe installaation program from the download zip file..
Follow the setup procedure to the Select Components and Installation Directory screen.
Clear the Java Support for Oracle Application Testing Suite and the Oracle Application Testing Suite check boxes.
Select the Remote Agent check box.
Click Next as necessary to complete the installation.
Verify network access from Oracle Load Testing for Web Applications system to the Agent systems and configure the Agent Systems as explained in the next sections.
Configure the agent system.
Define the system in Oracle Load Testing for Web Applications by selecting Systems from the Manage menu.
Once the Oracle Load Testing for Web Applications Agent is installed and the Agent systems are configured, you do not need to start or run an application. When you define your Oracle Load Testing for Web Applications testing scenarios, you specify which Agent machine to use to run the virtual users in the System field of the Build Scenarios tab. Oracle Load Testing for Web Applications automatically accesses and starts the Agent when you start the Autopilot.
Once you have the Oracle Load Testing for Web Applications and Agent software installed on the individual systems, you should verify network access between the Oracle Load Testing for Web Applications system and each Agent system. This section provides basic tips and techniques to make sure that Oracle Load Testing for Web Applications can successfully communicate with each Agent system.
Make sure that you have the Oracle Load Testing for Web Applications Agent software loaded on the Agent system(s) and that it is the same version as the Oracle Application Testing Suite software that is loaded on the Oracle Load Testing for Web Applications system. The systems you plan to use as agents must have either the Oracle Load Testing for Web Applications Agent software or the full Oracle Application Testing Suite installed to work as agents. Do not install both the Oracle Load Testing for Web Applications Agent software and the Oracle Application Testing Suite software on the same system. Otherwise, resource conflicts between the two programs may occur.
Make sure you can successfully Ping all of the Agent systems from the Oracle Load Testing for Web Applications system. The names you use to Ping the systems are the same names that you will specify for the Agent systems in the Oracle Load Testing for Web Applications system. If you cannot successfully Ping the Agent systems, contact your network administrator to resolve the issue. If you cannot Ping the agent systems from the Oracle Load Testing for Web Applications system, you will not be able to run the agents from the Oracle Load Testing for Web Applications system.
In the Oracle Load Testing for Web Applications system, add a Visual Script to the Configure Parameters of the Scenario list. Enter the machine name or IP address of the Agent system where you want to run the Visual Script into the System field on the Build Scenarios tab of Oracle Load Testing for Web Applications.
If you need to change the account that the agent service, and thus the agent itself uses, you must specify the login information. You may need to do this:
When testing with client side certificates. They are typically installed on agent machines and may only be accessible when logged in as that user.
When the system account has a proxy server configuration setup for use by the machine's local Internet Explorer.
To configure Oracle Load Testing for Web Applications agents:
Open Administrative Tools in the Control Panel then open Services. The Services dialog box displays.
Select Oracle Load Testing for Web Applications Agent Service.
Select Properties from the Action menu.
Click the Log On tab.
Select This account to specify the login information:
This Account - specify the account or use the Browse button to navigate to the account.
Password - specify the login password.
Confirm Password - confirm the login password.
Click OK.
If the password for this account changes, you must change the password using this procedure.
The Linux agent is not part of the standard Oracle Application Testing Suite product download Zip file. To install the Linux agent:.
Go to: http://www.oracle.com/technology/software/products/app-testing/index.html
Download the oats-linux-agent-x.xx.xxxx.zip from the Web site.
Copy oats-linux-agent-x.xx.xxxx.zip to your Linux machine.
Enter the following commands. <installdir> should be the location where you want to install the agent.
unzip oats-linux-agent-x.xx.xxxx.zip -d <installdir> cd <installdir>/agentmanager/bin chmod +x startAgentManager.sh
Start the AgentManager with the following command:
./startAgentManager.sh
Once the Linux agent is installed, define the remote agent system in the Oracle Load Testing for Web Applications Systems Manager.
When you define your Oracle Load Testing for Web Applications testing scenarios, you specify which Agent machine to use to run the virtual users in the System field of the Build Scenarios tab and you specify Java Client as the User Mode on the same tab. Oracle Load Testing for Web Applications automatically accesses and starts the Agent when you start the Autopilot.
Before ServerStats can monitor server-side statistics, the server(s) that you plan to monitor must be configured so that the ServerStats client has remote access to the server(s).
This section explains the server-side requirements for ServerStats remote access.
The ServerStats Solaris SNMP client gathers performance statistics from a Solaris SNMP agent. ServerStats uses Sun Microsystems' proprietary SNMP extensions to report on the overall status of a machine and its individual processes.
The Solaris SNMP agent is installed and enabled by default on versions 2.6 and above of Solaris and is officially part of the Solstice Enterprise Agents suite:
http://www.sun.com/software/entagents/.
To start the SNMP agent on Solaris:
Verify the Solaris SNMP agent is installed and that you have the following files and directories.
| Files and Directories | Description |
|---|---|
/usr/lib/snmp/snmpdx |
Sun Solstice Enterprise Master Agent |
/usr/lib/snmp/mibiisa |
Sun SNMP Agent |
/etc/init.d/init.snmpdx |
Initialization script |
/etc/snmp/conf |
configuration files directory |
/var/snmp/mib/snmpdx.mib |
Master agent MIB file |
/var/snmp/mib/sun.mib |
Sun agent MIB file |
The above directory and file locations apply to the default installation of Solaris and SNMP. Refer to the Solaris installation documentation for additional information about installing Solstice Enterprise Agents suite.
Start the Solaris SNMP agent.
If the snmpdx process is not already running, execute the following command to start the Solaris SNMP agent:
/etc/init.d/init.snmpdx start
Verify that snmpdx and mibiisa are in the process list.
To stop the SNMP server at any time, execute the following command:
/etc/init.d/init.snmpdx stop
To enable SNMP at startup, make a new entry in the /etc/rc*.d directories, or run the startup command from your local initialization script.
Refer to the Solaris documentation for more information on installing, configuring and running the SNMP agent. Online information can be found at:
The ServerStats Oracle SNMP client gathers performance statistics from the Oracle Enterprise Manager Intelligent Agent. The Oracle Intelligent Agent uses the Simple Network Management Protocol (SNMP). The agent exposes an extensive set of statistics through SNMP. The ServerStats Oracle SNMP client reports on statistics relating to I/O, load, and query activity.
You must configure Oracle SNMP support before starting the Intelligent Agent. Note that all configuration files for the following steps are located in the $ORACLE_HOME/network/snmp/peer directory.
This section provides basic instructions for configuring Oracle SNMP access. Additional documentation for the Oracle Enterprise Manager Intelligent Agent is located on the Oracle Documentation CD in the Server section (see section 4-19 of the Oracle8 Installation Guide). The installation documentation for the specific platforms describe how to start the agent on Windows and Linux.
In the CONFIG.master file, make the following change:
Search for the line beginning with MANAGER.
Change the ipaddr field, coded as 130.35.10.210, to the hostname or IP address of the Oracle server to monitor using ServerStats.
You can also make other changes to the CONFIG.master file, as documented within the file.
Add the following line to the snmpd.conf file:
trap hostname_or_IP_address
where hostname_or_IP_address represents the hostname or IP address of the Oracle server to monitor using ServerStats.
In the CONFIG.encap file, you can optionally modify the port number, which is set to 161 in the default file. If you modify the port number, you must also modify the port number for NEW_SNMPD_PORT in the start_peer script.
NEW_SNMPD_PORT is the port on which the snmpd agent (the native Solaris 2.x SNMP agent) listens. Make sure this is the same port as specified in the CONFIG.encap file. NEW_TRAPD_PORT is the PEER encapsulator port to which the snmpd agent sends traps.
NEW_SNMPD_PORT and NEW_TRAPD_PORT in the start_peer script must have different port numbers. You may also modify the NEW_TRAPD_PORT port number.
The start_peer script contains a line like the following:
SNMPD = snmpd_executable_path
If the snmpd executable on your system is not in the location indicated by the start_peer script, edit snmpd_executable_path to indicate the correct location of the snmpd executable.
Perform the following steps to start the SNMP components:
Verify that the SNMP components, master_peer, encap_peer, and snmpd, are not running:
$ ps -aef | grep peer
$ ps -aef | grep snmp
If any of the components are running, log in as the root user and use the kill command to terminate the processes before proceeding.
As the root user, run the start_peer script to start the PEER master agent, PEER encapsulator, and native Solaris 2.x SNMP agent:
# cd $ORACLE_HOME/network/snmp/peer
# ./start_peer -a
Warning:
If you do not have the native Solaris 2.x SNMP agent on your system, you must not use the PEER encapsulator. To start the master agent only, runstart_peer -m.You can use remote data collectors for collecting ServerStats data. To install a remote data collector:
Run oats###.exe installaation program from the download zip file.
Follow the setup procedure to the Select Components and Installation Directory screen.
On the Select Components and Installation Directory dialog box, deselect all options except for Oracle Load Testing for Web Applications DataCollector.
Follow the setup instructions to install the remote data collector.
In Oracle Load Testing for Web Applications, select Systems from the Manage menu to display the System Manager.
Select ServerStats Data Collectors and click New. The Add ServerStats Data Collector Dialog Box is displayed.
Enter the name, host name or IP address, and port number to use for the remote data collector.
Click OK.
Click Close.
The remote data collector will be available to use when adding or editing monitors in a ServerStats configuration. Select the remote data collector in the Data Collector section of the Edit Monitor and Add Monitor: Step 2 of 3 dialog boxes.
The default Oracle Load Testing for Web Applications web server port is 8088. You can change this to another port.
To change the port:
Go to http://localhost:8088/console to start the WebLogic Console.
Log in as administrator using the password you defined during the Oracle Application Testing suite installation procedure.
In the Domain Structure, select Environment under "oats" and then select Servers.
Select AdminServer(Admin).
Change the port and release the configuration.
You can set up Oracle Load Testing for Web Applications to use SSL (Secure Sockets Layer). The procedure is comprised of the following steps:
Go to http://localhost:8088/console to start the WebLogic Console.
Log in as administrator using the password you defined during the Oracle Application Testing suite installation procedure.
In the Domain Structure, select Environment under "oats" and then select Servers.
Select AdminServer(Admin).
Select the SSL tab.
See the Oracle WebLogic Server documentation for additional information about using the Console application.
The Oracle Application Testing Suite tools menu has options for viewing version and license information, restarting and stopping the Oracle Application Testing Suite Application service, and creating support files for troubleshooting. Select Tools from the Oracle Application Testing Suite start menu. This menu has the following options:
About Oracle Application Testing Suite - displays the About Oracle Application Testing Suite dialog box that shows copyright, version, and license information. It also has links to information about obtaining license keys and information about your system.
Create Support File - for troubleshooting purposes, creates the OATSSupport.zip file and places it on your desktop. From there you can email it to your support representative. This file contains the log files used for troubleshooting.
Oracle Load Testing Agent Authentication Manager - opens the Agent Authentication Manager for defining authentication profiles for multiple load testing agent machines.
Restart Oracle Application Testing Suite Application Service - stops and restarts the Oracle Application Testing Suite Application service.
Stop Oracle Application Testing Suite Application Service - stops the Oracle Application Testing Suite Application Service.
Data Migration Utility - opens the Data Migration Utility for migrating data from Oracle Test Manager for Web Applications or Oracle Load Testing for Web Applications in MS Access or SQL Server databases to Oracle Database 11g.
Using the Administrator you create user accounts, assign them user names and passwords, and assign the type of access that they have in Oracle Load Testing for Web Applications, none, full control, or view only. When Oracle Load Testing for Web Applications login is enabled, users must login to access Oracle Load Testing for Web Applications.
A default administrator account is created at installation. The username and password are specified during the installation process. You can change the password after logging in to the Administrator.
Enter http://<machine>:8088/admin in your browser where machine is where the Oracle Application Testing Suite is installed or select the Administrator from the Oracle Application Testing Suite start menu.
Select the load testing database that you want to access.
If you want to change the administrator password, click the User tab, select the Administrator user, and click Edit.
Enter the new password, verify it, and click OK.
This section describes the menus and options available in the Administrator.
Unlock Locked Records - unlocks locked records in the database. This is an emergency feature to be used to clear out locks in the database when the product fails and leaves entries locked for editing.
Purge Deleted Records - physically removes all deleted data from the database. Deleted items are marked as such and are not shown in the user interface; however, they are kept in the database until the database is purged.
Setup E-mail Config - pdisplays the Setup E-mail Configuration dialog box for configuring the mail server to use for e-mail notifications.
Manage Default Reports - displays the Manage Default Reports dialog box for selecting which default reports will be visible to individual users.
The Users tab is where you add, edit, and delete users and specify what Oracle Load Testing for Web Applications features they can access.
Add - displays the Add User dialog box for adding new users.
Edit - displays the Edit User dialog box for the selected user.
Delete - deletes the selected user.
Username - displays the user name for logging in to Oracle Load Testing for Web Applications.
First Name - displays the user's first name.
Last Name - displays the user's last name.
E-Mail - displays the user's e-mail address.
Access - displays the type of access the user has in Oracle Load Testing for Web Applications.
Administrator Access - displays whether the user can access the Administrator.
To add a user:
Click Add.
First Name - enter the user's first name.
Last Name - enter the user's last name.
E-Mail - enter the user's e-mail address.
Username - enter the user's username.
Password - enter the user's password.
Confirm Password - re-enter the user's password.
Enable E-mail notification - select this option to enable email notification when new issues are created and when the owner or assigned to fields are changed for issues.
Enable Administrator Access - gives this user the ability to log on to the Oracle Test Manager for Web Applications Administrator for managing the database.
Enter the user's information.
Select or clear the E-Mail notification and Administrator access options..
Click OK.
To edit a user:
Select the user whose information you want to change.
Click Edit.
First Name - enter the user's first name.
Last Name - enter the user's last name.
E-Mail - enter the user's e-mail address.
Username - enter the user's username.
Password - enter the user's password.
Confirm Password - re-enter the user's password.
Enable E-mail notification - select this option to enable email notification when new issues are created and when the owner or assigned to fields are changed for issues.
Enable Administrator Access - gives this user the ability to log on to the Oracle Test Manager for Web Applications Administrator for managing the database.
Make any changes.
Click OK.
The Oracle Load Testing for Web Applications main window is where you perform the majority of your load/performance testing activities. The main window consists of the menu bar, toolbar, and five dialog tabs.
The Oracle Load Testing for Web Applications main menu has the following options:
Scenario
Session
ServerStats
Tools
Manage
Help
Logout
The following sections explain each of the menu options.
These menu options let you work with scenario files. The following options are available:
New- creates a new Oracle Load Testing for Web Applications scenario.
Open- opens an existing Oracle Load Testing for Web Applications scenario to run or modify.
Save- saves any changes to the currently open Oracle Load Testing for Web Applications scenario. If the scenario has not been saved before, Oracle Load Testing for Web Applications asks for a filename.
Save As - saves the currently open Oracle Load Testing for Web Applications scenario using a different filename.
The Sessions Menu options let you manage sessions. The following options are available:
Attach - opens a dialog box for selecting another running session that you want to view.
Detach - detaches from the current session.
Stop - stops the current session.
Terminate Idle Agents - stops all idle agent processes running on your agent systems.
The ServerStats Menu options let you configure ServerStats configurations, metric profiles, and metrics, as well as start the virtual user display.
Configurations - opens a dialog box for managing ServerStats configurations.
Metric Profiles - opens a dialog box for configuring ServerStats metric profiles.
Metrics - opens a dialog box for configuring ServerStats metrics.
ServerStats Display - opens the ServerStats Status dialog box that shows the results and status of ServerStats monitors.
The following options are available:
Options - opens a dialog box for setting the Oracle Load Testing for Web Applications preferences.
VU Display - starts the virtual user display, which lets you monitor the progress of virtual users and view any errors virtual users may run into during playback.
Sync Point Status - opens a dialog box that displays the status of all sync points and lets you release individual sync points or all sync points.
Upload File - opens a dialog box for uploading a file to the repository.
Download File - opens a dialog box for downloading a file to the local system.
The following options are available:
Systems- opens a dialog box for adding, editing, and deleting systems that can be configured as VU Agents, Data Collectors, or Monitored Systems.
Databases - opens a dialog box for adding, editing, and deleting databases.
Sessions- opens a dialog box for editing and deleting sessions from the database.
Scenarios - displays a dialog box for editing and deleting scenarios.
User Defined Profiles - displays a dialog box for creating, editing, and deleting user defined profiles.
Graphs - displays the Graph Query Manager for editing and deleting saved graph queries.
The toolbar has the following buttons:
New Scenario - Creates a new Oracle Load Testing for Web Applications scenario.
Open Scenario - Opens an existing Oracle Load Testing for Web Applications scenario to run or modify.
Save Scenario - Saves any changes to the currently open Oracle Load Testing for Web Applications scenario. If the scenario has not been saved before, Oracle Load Testing for Web Applications asks for a filename.
Start Load Test - Submits the current scenario to the Autopilot and automatically starts the scenario.
Stop All Virtual Users - Stops all virtual users that are running in the current scenario.
Abort All Virtual Users - Aborts all virtual users that are running in the current scenario.
The Build Scenarios tab is where you specify which scripts and user-defined profiles to include in the scenario.
The Select scripts & user-defined profiles for your scenario list shows the Oracle Functional Testing for Web Applications Visual Scripts and user-defined profiles in the current workspace.
The Configure parameters of the scenario list shows the scripts and user-defined profiles selected for the current Oracle Load Testing for Web Applications scenario. You can configure each using the options provided here.
You can change the fields that are displayed and the default values for each field by selecting Options from the Tools menu then selecting Scenario Defaults and checking or unchecking the Show field.
Repository - a list of repositories. The default repository is the OFT folder in your installation directory. New repositories can be created by selecting Options from the Tools menu then selecting Repositories.
Workspace - lists the workspaces available in the selected repository. Workspaces store project-related Visual Script files, scenario files, and log files. You can use workspaces to organize these files.
Note:
Use Oracle Functional Testing for Web Applications to create and administer Workspaces.<Script and user-defined profile list> - a list of Oracle Functional Testing for Web Applications Visual Scripts and user-defined profiles that are available to include in virtual user scenarios.
Configure parameters of the scenario - a list of scripts and user defined profiles selected to be in the load scenario. The fields displayed here can be customized by selecting Options from the Tools menu then selecting Scenario Defaults. Select the fields you want to display by checking the field's corresponding checkbox in the Show column.
# VUs - specifies the number of virtual users to run for the selected profile. For each virtual user, Oracle Load Testing for Web Applications runs a separate instance of the Visual Script(s) specified in the virtual user profile.
System - specifies the machine on which the virtual users will run. When running virtual users across systems on a LAN/WAN, select the system name of a system running either Oracle Load Testing for Web Applications Server or Oracle Load Testing for Web Applications Agent from the option dropdown. Systems are defined using the VU Agents option in the System Manager. Initially, you must define the machine names or IP addresses of the system(s). Once the name(s) or IP addresses have been specified, you can select the system name from the drop-down list for future load tests.
User Mode - the mode in which to run Oracle Load Testing for Web Applications virtual users. The following options are available:
Thick Client - the virtual users run using full browser capabilities. This mode requires more resources and is less scalable than Thin Client, and should only be used in special cases. Reasons for using Thick client may include Web pages that require large amounts of client side processing.
Thin Client - a less resource intensive method that provides a high level of Web compatibility and Visual Script verification. Thin Client mode consumes fewer system resources per process than Thick Client, and is able to run more virtual users on a given agent system.
Java Client - a highly scalable version of the Thin Client that executes a compiled Oracle Functional Testing for Web Applications script in native Java code. This agent provides a flexible code interface for performing customized scripting operations.
When determining the number of virtual users to run per process or system, you need to include the Client overhead in the resource allocation. Each VU in Thin or Java Client requires approximately 350 KB-500 KB of memory to run. When calculating the available memory to run VUs on an agent system, you must account for a 20-30% client system overhead. Therefore, you only have 70-80% of the physical memory (RAM) available to run VUs.
Delay - specifies the amount of time (in seconds) to wait between iterations of virtual user runs. You specify the number of iterations using the Autopilot.
VUs Pacing - specifies the Visual Script playback delay between pages for each virtual user. This is the amount of time the user looks at a page before making the next request and is commonly referred to as "think time." There are four options:
Recorded - uses the delay times that were recorded in the Oracle Functional Testing for Web Applications Visual Script. You can set minimum and maximum delay times (in seconds) that override the Visual Script delay times in the Minimum and Maximum edit boxes.
Recorded/Random - uses random delay times based upon the recorded user delay. Oracle Load Testing for Web Applications sets the low end of the random range as the actual recorded user delay minus the Lower percentage setting. Oracle Load Testing for Web Applications sets the high end of the random range as the actual recorded user delay plus the Upper percentage setting. For example, if the actual recorded delay time was 100 seconds and the Lower and Upper settings are 10% and 25% respectively, Oracle Load Testing for Web Applications uses random delay times between 90 and 125 seconds.
Random - uses random times for Virtual User pacing. You can set minimum and maximum delay times for random delay in the Minimum and Maximum fields.
No Delay - plays back the Visual Scripts at the fastest possible speed with no time between page requests.
Each line also includes the following buttons:
Edit Scenario Details - Displays the Edit Scenario Details dialog box for configuring the parameters of each profile in the scenario.
Data Bank Control - Displays the Data Bank Control dialog box for configuring the Data Bank options for individual scripts and profiles.
Delete - Deletes the selected profile from the scenario.
For information about User-Defined Profiles, see Defining Virtual User Profiles in Chapter 4. For information about the Selected VU Profile settings see Defining Virtual User Scenarios in Chapter 5.
The Set up Autopilot tab is where the information needed to control the running of the scenario is specified. The Autopilot controls the starting and stopping of the scenario, the frequency with which new virtual users are started and the number of virtual users that are started from among the profiles submitted to it.
You specify the start and stop times, and the virtual user rampup specifications for the Submitted Scenario Profile. The Set up Autopilot tab also shows the list of virtual user profiles submitted in the Oracle Load Testing for Web Applications scenario and the available ServerStats Configurations for monitoring back-end systems during a load test.
The Timing and event controls section is where you specify when the Scenario profiles should start and when they should end and the rate at which the virtual users within the Scenario profile list should start.
The ServerStats Configuration section is where you specify an Oracle Load Testing for Web Applications ServerStats configuration to run during the load test. Each ServerStats configuration contains a collection of monitors for monitoring performance of back-end systems during a load test to identify bottlenecks.
The Submitted Scenario Profiles list shows the virtual user profiles submitted to the Autopilot as part of the Oracle Load Testing for Web Applications scenario. The list also shows the number of virtual users specified for each profile, the number of virtual users remaining to be started, and other details of the Scenario run.
For information about using the Autopilot, see Using Autopilot in Chapter 6.
The virtual user grid lists the currently running virtual users and the profile and playback details associated with each.
For information about using the virtual users grid, see Using Autopilot in Chapter 6.
The View Run Graphs tab is where you can view runtime graphs and reports. These graphs are only available for the running load test session. Use the Create Reports tab to view reports and graphs after the load test has finished running.
The View Run Graphs tab is refreshed according to what is set in the Graph refresh interval setting in the reporting options (select Options from the Tools menu).
To stop the display from being refreshed click the Pause button.
To resume refreshing the display, click the Resume button. Note that exiting the tab and returning to the tab will also resume refreshing the display.
The Overview tab shows a thumbnail view of each graph. Click on a thumbnail to see a full view of that graphs or reports.
Click the New Graph tab to create a custom run time graph.
For information about reports and graphs, see Chapter 7.
The System Manager, accessed by selecting Systems from the Manage menu, lets you add and remove Systems and create System groups.
The Systems Manager lets you configure four types of systems and groups and has the following options for each:
VU Agent Systems - these are systems that you want to use as remote virtual user agents for running virtual users during a load test. These systems appear in the Systems option of the Build Scenario tab.
New - displays the Add System dialog box for adding a new VU Agent system.
Edit - displays the Edit System dialog box for configuring the system name, IP address Start parameters.
Delete - deletes the selected systems. To select more than one system, hold down the CTRL key.
Name - lists the available systems.
VU Agent System Groups - system groups let you distribute virtual users across multiple VU Agent systems that have been grouped.
New - displays the Add System Group dialog box for configuring a new system group.
Edit - displays the Edit System Group dialog box for adding or deleting systems from the group.
Delete - deletes the selected system groups. To select more than one system group, hold down the CTRL key.
Name - lists the system groups that are available.
ServerStats Data Collectors - these are systems that you want to use as remote data collectors for gathering ServerStats data.
New - displays the Add System dialog box for adding a new ServerStats data collector.
Edit - displays the Edit System dialog box for editing the selected data collector.
Delete - deletes the selected data collectors. To select more than one data collector, hold down the CTRL key.
Name - lists the available data collectors.
Monitored Systems - these are systems that you want to monitor with ServerStats.
New - displays the Add System dialog box for adding a new system that you want to monitor using ServerStats.
Edit - displays the Edit System dialog box for editing the selected system.
Delete - deletes the selected systems. To select more than one system, hold down the CTRL key.
Name - lists the available systems.
Note:
Systems and system groups appear in the System list on the Build Scenarios tab.For more information about using the System Manager, see Defining Systems later in this chapter.
Before you can select systems in Oracle Load Testing for Web Applications Scenarios, you must define the machines that are Oracle Load Testing for Web Applications agent systems. The Oracle Load Testing for Web Applications System Manager lets you define system names or IP addresses and create system groups that the Oracle Load Testing for Web Applications scenarios can use as agents.
Note:
See the installation section at the beginning of this chapter for more information about installing the Oracle Load Testing for Web Applications Agent software on each system and verifying network access between the Oracle Load Testing for Web Applications system and each agent system.In addition, if you are using Oracle Load Testing for Web Applications ServerStats you must define the data collector systems and systems being monitored.
To add a new VU Agent system:
Select Systems from the Manage menu to display the Systems Manager.
Select VU Agent System.
Click New to display the Add VU Agent System dialog box.
General - enter the system information.
Name - enter the system name.
Host Name or IP - enter the host name or IP address of the system.
Start - enter the system information.
Port - enter the port number to use.
Username - enter the username to use for authentication.
Password - enter the password to use for authentication.
Test - checks to see whether the Oracle Load Testing for Web Applications server can contact the system and displays an informational message indicating if the system is available.
Enter the name of the system in the Name field, and enter the name or IP address of the system in the Host Name or IP field.
Enter the port and authentication settings.
Click OK.
Click Close.
Note:
Systems and system groups appear in the Systems list on the Build Scenarios tab.To add a new system group:
Select Systems from the Manage menu.
Select VU Agent System Groups.
Click New to display the Add System dialog box.
Name - enter the name of the system group.
Systems - lists the systems that are available to add to the group. Select the systems that you want to add and deselect the systems you want to remove.
Enter the name of the group in the Name field.
Select the systems you want to add from the Systems list.
Click OK.
Note:
Systems and system groups appear in the Systems list on the Build Scenarios tab.To add systems to groups:
Select Systems from the Manage menu.
Select VU Agent System Groups.
Either select the group you want to change and click Edit or click New to create a new group.
Select the systems you want to add from the Systems list.
Click OK.
Click Close.
Note:
Systems and system groups appear in the Systems list on the Build Scenarios tab.To add a new ServerStats Data Collector:
Select Systems from the Manage menu to display the Systems Manager.
Select ServerStats Data Collector.
Click New to display the Add ServerStats Data Collector dialog box.
General - enter the system information.
Name - enter the name of the data collector.
Host Name or IP - enter the host name or IP address of the data collector.
Remote Data Collector - - enter the port information.
Port - enter the port number to use.
Test - checks to see whether the Oracle Load Testing for Web Applications server can contact the system and displays an informational message indicating if the system is available.
Enter the name of the system in the Name field, and enter the name or IP address of the system in the Host Name or IP field.
Click OK.
Click Close.
Note:
Systems and system groups appear in the Systems list on the Build Scenarios tab.Monitored systems are those systems that will be monitored using ServerStats. In addition to defining the system, you can have Oracle Load Testing for Web Applications discover the components that are available for monitoring, manually add new component types and components, and configure the data sources to use. Information that is configured here will be available when you configure ServerStats.
A data collector can only monitor one type of JMX monitor at a time. To monitor more than one type of JMX monitor at the same time, you must use a separate data collector for each. All JMX monitors require some set up. Following are the broad steps followed by the specific procedures:
WebLogic 9.0 and NEC WebOTX 7.1
Copy configuration jar files to the data collector machines
Copy configuration jar files to the data collector machines
Update the properties file
WebLogic 8.0, 8.1
Copy configuration jar files to the data collector machines
Create jar files
For WebLogic 8.1, update the properties file
Copying the JMX Server Installation Jar Files
Before these server types can be used, the JMX agent needs a specific configuration jar file to be copied from the JMX server installation to the OracleATS\DataCollector\classes directory on all machines that will be used as data collectors for sampling from that server. The file can be obtained from your application server installation and copied to the appropriate directory as listed in the following table.
| Application Name | Files to Copy | Default Directory |
|---|---|---|
| BEA WebLogic 6.1 | weblogic.jar | C:\OracleATS\DataCollector\classes\weblogic6.1 |
| BEA WebLogic 7.0 | weblogic.jar | C:\ OracleATS\DataCollector\classes\weblogic7.0 |
| BEA WebLogic 8.1 | weblogic.jar, webservices.jar | C:\OracleATS\DataCollector\classes\weblogic8.1 |
| BEA WebLogic 9.0 | weblogic.jar, webservices.jar | C:\OracleATS\DataCollector\classes\weblogic9.0 |
| IBM WebSphere 5.0 | admin.jar, j2ee.jar, jflt.jar, jmxc.jar, mjxx.jar, log.jar, mail.jar, ras.jar, sas.jar, soap.jar, utils.jar, wasjmx.jar, wsexception.jar, wssec.jar | C:\OracleATS\DataCollector\classes\websphere5.0 |
| IBM WebSphere 5.1n | admin.jar, bootstrap.jar, ffdc.jar, ibmjsse.jar, j2ee.jar, jflt.jar, jmxc.jar, jmxx.jar, log.jar, mail.jar, ras.jar, sas.jar, soap.jar, utils.jar, wasjmx.jar, wsexception.jar, wssec.jar | C:\OracleATS\DataCollector\classes\weblsphere5.1 |
| IBM WebSphere 6.0 | admin.jar, bootstrap.jar, bsf.jar, classloader.jar, client.jar, commons-el.jar, configmanager.jar, db2j.jar, deployutils.jar, emf.jar, ffdc.jar, filetransfer.jar, ibmcertpathprovider.jar, ibmjceprovider.jar, ibmjsse.jar, idl.jar, iwsorb.jar, j2ee.jar, jacl.jar, js.jar, jspcore.jar, jspruntime.jar, jsptranslation.jar, jspvisitor.jar, mail.jar, mail-impl.jar, management.jar, pluginconfig.jar, ras.jar, runtime.jar, runtimefw.jar, sas.jar, security.jar, soap.jar, tcljava.jar, uddi4j.jar, utils.jar, validationmgr.jar, wasjmx.jar, wasproduct.jar, wccm_base.jar, webcontainer.jar, webservices.jar, wjmxapp.jar, wlmserver.jar, workspace.jar, wsdl4j.jar, wsexception.jar, wsprofile.jar, wssec.jar | C:\OracleATS\DataCollector\classes\weblsphere6.0 |
| NEC WebOTX 7.1 | j2ee.jar, wosv-rt.jar | C:\OracleATS\DataCollector\classes\webotx and C:\OracleATS\DataCollector\lib |
| NEC WebOTX 7.1 | cacerts.jks (trust file) | C:\OracleATS\DataCollector\classes\webotx |
Generating Jar Files for Weblogic 7.0, 8.1
Generate the weblogic-javax-management.jar file and copy it to the C:\OracleATS\DataCollector\classes\weblogic8.1 or 7.0 directory. This file contains all of the class files of javax.management from weblogic.jar.
Updating the Properties Files for WebLogic 8.1, WebSphere 5.0, 5.1, and 6.0
JMX must be set up for testing WebLogic and WebSphere. Use the following procedure for each application server you are testing. Note that only one type of application server can be tested at a time using a particular data collector.
Stop the Oracle Load Testing for Web Applications data collector.
Open the OracleATS\DataCollector\properties\jagent_service.properties file located in your installation directory.
Uncomment the line beginning with "#JHP.commandline =" corresponding to the application server you are testing by deleting the pound sign. Make sure that this is the only line that is uncommented.
Select Save from the File menu.
Copy the required jar files to the OracleATS\DataCollector\classes directory in the installation directory. These jar files are located on your WebSphere or WebLogic server machine in the Server LIB directory.
Restart the Oracle Load Testing for Web Applications data collector.
To add a new monitored system:
Select Systems from the Manage menu to display the Systems Manager.
Select Monitored System.
Click New to display the Add Monitored System dialog box.
This dialog box lets you configure systems that are going to be monitored using ServerStats. You can manually add system components and component types, discover components, and configure data sources.
New - displays the Add Component dialog box for manually adding components and component types.
Delete - Deletes the selected component.
Discover Components - Displays the System Discovery dialog box for specifying the components to discover and the data source to use.
General
Name - enter the name of the monitored system.
Host Name or IP - enter the host name or IP address of the monitored system.
Components - lists the component types and components that are configured for this system.
Following are the options for each type of monitored system. You only need to specify the settings for the type of monitored system you are adding. For example, if the monitored system is a database, then you need to specify the database settings. You can also configure this information from ServerStats when you configure the monitor.
Database - refer to the JDBC-ODBC documentation for information on configuring your database data source, or refer to:
http://download.oracle.com/javase/1.4.2/docs/guide/jdbc/bridge.html.
Oracle Load Testing for Web Applications uses a JDBC driver to connect to your database. When you select any driver other than Custom, the appropriate settings for that driver are automatically provided. Use these guidelines to select and configure the appropriate driver for your database.
For monitoring enterprise level databases, the native drivers (Oracle Thin JDBC driver) is recommended over the JDBC:ODBC Bridge option. The following are the driver options:
Oracle Thin JDBC Driver - This driver option applies to Oracle databases. This driver is installed automatically as part of Oracle Load Testing for Web Applications Data collectors.
Sun JDBC:ODBC Bridge Driver - This driver option is available as an option for SQL and Oracle databases and any other database for which you have an ODBC driver. This bridge driver is installed automatically as part of Oracle Load Testing for Web Applications.
SQL Database - The SQL Server ODBC driver is installed with MSDE and Microsoft SQL Server. If you do not have either of these on the Oracle Load Testing for Web Applications server and you are using a remotely installed SQL database for Oracle Load Testing for Web Applications, you need to install the SQL Server ODBC driver on the Oracle Load Testing for Web Applications machine and set up an ODBC DSN. The ODBC driver is included with the SQL Server Client utilities.
Oracle Database - You must set up an Oracle ODBC on the Oracle Load Testing for Web Applications machine in order to use this driver.
Driver - Select a driver type from the list: Oracle Thin JDBC driver, Sun JDBC:ODBC Bridge, or Custom. You must have the appropriate driver installed on the Oracle Load Testing for Web Applications machine to set up a Database monitor.
Driver String - This information will vary depending on the type of database that you are monitoring. If you selected any option other than Custom, the appropriate string is automatically displayed. For example, this is the string for the Oracle Thin JDBC driver:
oracle.jdbc.driver.OracleDriver
If you selected a Custom driver type, you can type in the Driver String yourself.
Connect String - For most drivers, this string is constructed from the information you supplied in the previous fields. The structure of the Connect String is different for each driver type, but Oracle Load Testing for Web Applications builds this string for all driver types except a Custom driver type. For a Custom driver setting, type in the Connect String.
Host - Specify the host name of the machine running the database. This is not required for a JDBC:ODBC or Custom driver setting.
Instance - Specify the SQL server named instance that you want to use. If nothing is specified, Oracle Load Testing for Web Applications uses the default instance as set up on your server. Refer to your database administrator for details.
Port - Oracle Load Testing for Web Applications displays the default port for the driver you selected. For example, the default port for an Oracle Thin JDBC driver is 1521. Modify the port number if necessary. This is not required for a JDBC:ODBC or Custom driver setting.
Database Name or Database SID - For the Inet Sprinta driver for SQL Server, provide the database name. For the Oracle Thin JDBC driver, provide the database or server ID.
Username - enter the username for connecting to the database, if required.
Password - enter the password for connecting to the database, if required.
JMX
JServer Type - enter the JMX server type you are using. The following is a list of supported types. Other types may be supportable. Contact support for more information.
Port - enter the port number for the connection.
Username - enter the username for logging on to the server.
Password - enter the password for logging on to the server.
Trust Store File Name - enter the client-side trust store path and file name.
Key Store File Name - enter the client-side key store path and file name.
Note:
Refer to your system administrator for information on configuring your server.Perfmon (Windows Performance Monitor) - authentication can be left blank if the system being monitored has a data collector running on it. Authentication is required when the system being monitored is remote to the data collector.
Username - enter the username for logging on to the system.
Password - enter the password for logging on to the system.
Domain Name - enter the domain or machine name of the user name account.
SNMP
Port - enter the port number for the connection.
Community String - the access key required for remote access. The Community String is typically "public" unless otherwise configured by the System Administrator. Contact the Administrator to find out the Community String required for remote access to the system.
SNMP Version - enter the SNMP version.
Url
System Homepage - enter the URL of the page you want to monitor.
Note:
If you are using SSH for the connection method, you must download plink.exe and copy it to the OracleATS\DataCollector\bin directory on the system on which the data collector is installed. The file name must be: username_host.key. The extension must be .key not .ppk. Leave the password file blank. plink is part of the PUTTY package by Simon Tatham. It is downloadable from:Remote Port - Specifies the port number. The default port for Telnet is 23, and the default port for SSH is 22.
Remote Protocol - Specifies the protocol to use to execute the command, Local Machine, Telnet, or SSH. You can use the Local protocol to monitor a remote machine if you have a Data Collector installed on that machine. Plink must be installed in the datacollector\bin directory on the machine on which you are running the Data Collector. This is only required if you intend to use the SSH connection method.
Remote Username - Specify a user name to log into an account on the host system.
Remote Password - Specify the password required to log into the User Name account on the system.
Command Prompt - Specify the command line prompt for the host machine. If you do not specify a command line prompt, Oracle Load Testing for Web Applications will attempt to infer the prompt by parsing the screen output. The default command prompt for the root user is #. For other users that have not configured a custom prompt, the default is $.
Operating System - Specifies the operating system of the host machine.
Test - checks to see whether the Oracle Load Testing for Web Applications server can contact the system and displays an informational message indicating if the system is available.
Enter the name of the system in the Name field, and enter the name or IP address of the system in the Host Name or IP field.
Enter data source information for the type of system you are adding.
Click Discover Components to find the components available on this system. Components that are found will be available in ServerStats. If you do not discover components when setting up the monitored system, you can discover them later when you set up your ServerStats monitor. The System Discovery dialog box is displayed.
Select Data Sources - select the data sources you want to use for discovery. When you select a data source, the components that it can discover are selected in the Select Component Types to Discover list.
Select Component Types to Discover - deselect component types that you do not want to discover.
Select the data sources you want to use for discovery. The components types that this data source can discover are automatically selected in the Select Component Types to Discover list.
Deselect and component types that you do not want to discover and click OK. The Discovery Setup dialog box for the data sources you selected is displayed. For example, if you selected Perfmon, the following dialog box is displayed.
This dialog box has the following options based on the selected data sources.
Database - refer to the JDBC-ODBC documentation for information on configuring your database data source, or refer to:
http://java.sun.com/j2se/1.4.2/docs/guide/jdbc/bridge.html.
Oracle Load Testing for Web Applications uses a JDBC driver to connect to your database. When you select any driver other than Custom, the appropriate settings for that driver are automatically provided. Use these guidelines to select and configure the appropriate driver for your database.
For monitoring enterprise level databases, the native drivers (Oracle Thin JDBC driver, Inet Sprinta JDBC driver) are recommended over the JDBC:ODBC Bridge option. The following are the driver options:
Oracle Thin JDBC Driver - This driver option applies to Oracle databases. This driver is installed automatically as part of Oracle Load Testing for Web Applications Data collectors.
Inet Sprinta JDBC Driver for Microsoft SQL Server - This driver option applies to SQL databases. This driver is installed automatically as part of Oracle Load Testing for Web Applications. For monitoring enterprise level SQL databases, the Inet Sprinta JDBC driver is recommended over the JDBC:ODBC Bridge option.
Sun JDBC:ODBC Bridge Driver - This driver option is available as an option for SQL and Oracle databases and any other database for which you have an ODBC driver. This bridge driver is installed automatically as part of Oracle Load Testing for Web Applications.
SQL Database - The SQL Server ODBC driver is installed with MSDE and Microsoft SQL Server. If you do not have either of these on the Oracle Load Testing for Web Applications server and you are using a remotely installed SQL database for Oracle Load Testing for Web Applications, you need to install the SQL Server ODBC driver on the Oracle Load Testing for Web Applications machine and set up an ODBC DSN. The ODBC driver is included with the SQL Server Client utilities.
Oracle Database - You must set up an Oracle ODBC on the Oracle Load Testing for Web Applications machine in order to use this driver.
Driver - Select a driver type from the list: Oracle Thin JDBC driver, Inet Sprinta JDBC driver for Microsoft SQL Server, Sun JDBC:ODBC Bridge, or Custom. You must have the appropriate driver installed on the Oracle Load Testing for Web Applications machine to set up a Database monitor.
Driver String - This information will vary depending on the type of database that you are monitoring. If you selected any option other than Custom, the appropriate string is automatically displayed. For example, this is the string for the Oracle Thin JDBC driver:
oracle.jdbc.driver.OracleDriver
If you selected a Custom driver type, you can type in the Driver String yourself.
Connect String - For most drivers, this string is constructed from the information you supplied in the previous fields. The structure of the Connect String is different for each driver type, but Oracle Load Testing for Web Applications builds this string for all driver types except a Custom driver type. For a Custom driver setting, type in the Connect String.
Host - Specify the host name of the machine running the database. This is not required for a JDBC:ODBC or Custom driver setting.
Instance - Specify the SQL server named instance that you want to use. If nothing is specified, Oracle Load Testing for Web Applications uses the default instance as set up on your server. Refer to your database administrator for details.
Port - Oracle Load Testing for Web Applications displays the default port for the driver you selected. For example, the default port for an Oracle Thin JDBC driver is 1521. Modify the port number if necessary. This is not required for a JDBC:ODBC or Custom driver setting.
Database Name or Database SID - For the Inet Sprinta driver for SQL Server, provide the database name. For the Oracle Thin JDBC driver, provide the database or server ID.
Username - enter the username for connecting to the database, if required.
Password - enter the password for connecting to the database, if required.
Perfmon (Windows Performance Monitor) - authentication can be left blank if the system being monitored has a data collector running on it. Authentication is required when the system being monitored is remote to the data collector.
Username - enter the username for logging on to the system.
Password - enter the password for logging on to the system.
Domain Name - enter the domain or machine name of the user name account.
SNMP
Enter the discovery information and click OK. The Discovery Status dialog box is displayed showing the progress of the discovery process.
This dialog box displays the progress of the discovery process. It also displays any errors encountered. The message, "Discovery Done," is displayed when discovery is complete.
When Discovery Done is displayed, click OK. If previously configured components could not be found, the Confirm Remove Components dialog box is displayed. If the configuration of previously configured components has changed, the Confirm Replace Components dialog box is displayed.
Check All - checks all of the listed components. Checked components will be removed or replaced.
Uncheck All - unchecks all of the listed components.
<components> - lists the previously configured components that either were not found or whose configuration has changed.
Deselect any components that you do not want to remove or replace and click OK.
The discovered components are added to the Components tree. Click on a component to view it's data source configuration. Click Delete to remove the data source. Click Add to add an available data source.
Click New to manually add component types and components. The Add Component dialog box is displayed.
Add Type
Component Type - select this option to add a new component type. This is the only option available from the system node.
Component - select this option to add components for the selected component type.
Definition
Component Type - when adding a new component type, enter a meaningful name for the component type. When adding a new component, this field defaults to the component type that was selected when you clicked the Add button.
Component - enter a meaningful name that allows you to identify the specific component you are adding.
Data Sources to Add to Component - select the data sources to add to this component.
Select whether you are adding a component or component type.
Specify the component type, if necessary, and the component. Select the data sources to apply to this component and click OK.
The data sources available for this component are displayed on the right. Enter the appropriate information. Click Delete to remove a data source. Click Add to add an available data source.
Click OK.
Click Close.
Note:
Systems and system groups appear in the Systems list on the Build Scenarios tab.To rename a system:
Select Systems from the Manage menu.
Click the type of system that you are renaming.
Select the system you want to rename.
Click Edit.
Enter the new name in the Name field. All instances of the system (within groups) are also renamed automatically.
Click OK.
Click Close.
To edit a system:
Select Systems from the Manage menu.
Select the system you want to edit.
Click Edit to display the Edit System dialog box for that type of system.
Make any changes.
ClickOK.
Click Close.
To delete a system:
Select Systems from the Manage menu.
Click the type of system you want to delete.
Select the systems you want to delete. To select more than one system, hold down the CTRL key.
Click Delete. All instances of the system (within groups) are also deleted automatically.
Click OK.
You can set Oracle Load Testing for Web Applications options for custom browsers, download rules, repositories, scenario defaults, session start and stop, session profile, and reporting options using Options from the Tools menu. Selecting this option opens the Options dialog box.
The following custom browser options are available:
New - displays a new line in the table.
Delete - deletes the selected browser.
Name - any name for the customized browser emulator. This name will appear in the Browser Emulation list in the Edit Scenario Details dialog box.
User Agent String - specifies the string to send to the server as the User Agent header string for the customized browser emulator.
These options let you specify which types of objects to download in Oracle Load Testing for Web Applications Thin Client and Java Client user modes. You can specify background images, ActiveX, CAB, JAR, CSS, Flash, Applets, and JavaScript library files. To specify objects, you define the HTML tags and attributes to use to filter references from other HTML in the page source.
Filtering is enabled when the Use Download Manager option is selected for the Edit Scenario Details dialog box.
To use the Download Manager:
Determine which types of files you want Oracle Load Testing for Web Applications Thin Client or Java Client to download.
Select Options from the Tools menu.
Select Download Rules.
The grid on the right side of the dialog box lists existing filters. The following options are available:
New - adds the new filter to the existing filters list.
Delete - removes the currently selected filter from the existing filters list.
Existing Filters grid fields - lists the following information for the defined download filters.
Tag Name - specifies the selected HTML tag.
Enabled - shows if the filter is enabled or disabled. Filters marked as true are enabled and will be used to download objects.
Attribute Name - specifies the selected attribute used to identify which specific Tag among all tags of the same Tag Name.
Attribute Value - specifies the value for the specified attribute name used to identify which specific Tag.
Download Attr - specifies which attribute identifies the file to download.
Filter Configuration - defines specific filter options to use for each download filter. The filter options identify specific tags and attributes in the HTML source that reference the object(s) to download. Set the following options and click New to add the filter to the existing filters list.
Tag Name - specifies the HTML tag to use to locate an object within the HTML source.
Enabled - select true to enable the filter. You can add filters to the Existing Filters list even if they are not enabled. You can select filters in the existing filters list at any time to enable or disable them for specific tests.
Attr Name - specifies the name part of the name/value pair that identifies the specific Tag among all tags of the same Tag Name. Select the attribute name to use to identify the tag(s) in the HTML source.
Attr Value - specifies the value part of the name/value pair that identifies the specific Tag among all tags of the same Tag Name. Specify the attribute value to use to identify the tag(s) in the HTML source.
Download Attr - specifies the tag attribute that identifies the object to download. For example, IMG tags reference the image filename using the SRC attribute.
To modify a filter, select it, then make changes using these fields. The changes automatically appear in the existing filters list.
Click New.
Set the Enabled field to true if you want to define and enable the download filter for use in Thin Client or Java Client. Set it to false if you just want to define a filter for future use but not enable it right away.
Select the HTML tag name that has an attribute that references the object to download.
Select the tag attribute name to identify specific HTML tags.
Enter the tag attribute value that identifies specific HTML tags. The Download setting shows the tag attribute that references the object to download.
Click New to add another filter or select an existing filter to change it.
Click OK.
Click the Edit Scenario Details button.
In the Browser Settings section, make sure that the Use Download Manager field is True.
Repositories give you the ability to share files. Any shared network directory can be used as a repository. Since the Oracle Application Testing Suite Application Service runs as the local SYSTEM user, there may be a policy restricting access to your network share. You can fix this by doing one of the following:
Ensure that both sharing permissions and security permission on the remote network directory allows for other SYSTEM users to gain access. The least restrictive setting is to allow the windows user "Everyone" to be given permission.
Configure the Oracle Application Testing Suite Application Service to run under a specific user account rather than the local System user account. Refer to "Configuring Oracle Load Testing for Web Applications Agents" earlier in this chapter.
New - adds a new entry to the table.
Delete - deletes the selected repository.
Name - enter the name of the repository.
Path - enter the path of the repository. If the path you specify is a shared network drive, the Oracle Load Testing for Web Applications Server must have access to that drive. By default, the Oracle Load Testing for Web Applications Server runs under the "Local System" account. You may need to change this to a user account in the Services panel.
To add a repository:
Select Options from the Tools menu.
Click Repositories.
Click New. A new entry is made in the table.
Enter the name of the repository.
Enter the location of the repository.
Setting Scenario DefaultsYou can change the default settings for profiles using the Scenario Defaults dialog box. Changes made are applied to profiles as they are added to the scenario. Note that changes are not applied to profiles that are already in the scenario. To apply changes to profiles already in the scenario, remove them from the scenario on the Build Scenarios tab, then add them back.
Each setting in the right panel has two columns:
Show - when checked, this field is displayed on the Build Scenarios tab.
Default Value - shows the value to which the option is set when a new script or user-defined profile is added to a scenario.
Main - the main settings are as follows:
# VUs - specifies the number of virtual users to run for the selected profile. For each virtual user, Oracle Load Testing for Web Applications runs a separate instance of the Visual Script(s) specified in the virtual user profile.
System - specifies the machine on which the virtual users will run. When running virtual users across systems on a LAN/WAN, enter the machine name of a system running either Oracle Load Testing for Web Applications or Oracle Load Testing for Web Applications Agent. Systems are defined using the Systems Manager. Initially, you must define the machine names or IP addresses of the system(s) in the Systems Manager. Once the name(s) or IP addresses have been specified, you can select the system name from the drop-down list for future load tests.
User Mode - the mode in which to run Oracle Load Testing for Web Applications virtual users. The following options are available:
Thick Client - the virtual users run using full browser capabilities. This mode requires more resources and is less scalable than Thin Client, and should only be used in special cases. Reasons for using Thick client may include Web pages that require large amounts of client side processing.
Thin Client - a less resource intensive method that provides a high level of Web compatibility and Visual Script verification. Thin Client mode consumes fewer system resources per process than Thick Client, and is able to run more virtual users on a given agent system.
Java Client - a highly scalable version of the Thin Client that executes a compiled Oracle Functional Testing for Web Applications script. This agent provides a flexible code interface for performing customized scripting operations.
Note:
User-defined scriptlets will not be executed when using the Java Client regardless of how the Execute User Defined Scriptlets options is set.When determining the number of virtual users to run per process or system, you need to include the Client overhead in the resource allocation. Each VU in Thin or Java Client requires approximately 350 KB-500 KB of memory to run. When calculating the available memory to run VUs on an agent system, you must account for a 20-30% client system overhead. Therefore, you only have 70-80% of the physical memory (RAM) available to run VUs.
Iteration Delay - specifies the amount of time (in seconds) to wait between iterations of virtual user runs. You specify the number of iterations using the Autopilot.
VU Pacing (Think Time) - specifies the Visual Script playback delay for each virtual user. There are four options:
Recorded - uses the delay times that were recorded in the Oracle Functional Testing for Web Applications Visual Script. You can set minimum and maximum delay times (in seconds) that override the Visual Script delay times in the Minimum and Maximum edit boxes.
Recorded/Random - uses random delay times based upon the recorded user delay. Oracle Load Testing for Web Applications sets the low end of the random range as the actual user delay minus the Lower percentage setting. Oracle Load Testing for Web Applications sets the high end of the random range as the actual user delay plus the Upper percentage setting. For example, if the actual recorded delay time was 100 seconds and the Lower and Upper settings are 10% and 25% respectively, Oracle Load Testing for Web Applications uses random delay times between 90 and 125 seconds.
Random - uses random times for Virtual User pacing. You can set minimum and maximum delay times for random delay in the Minimum and Maximum edit boxes.
No Delay - plays back the Visual Scripts at the fastest possible speed.
Use Data Bank - when true, Visual Scripts that have Oracle Functional Testing for Web Applications Data Banks will use the Data Banks as part of the virtual user playback. When false, Visual Scripts playback using the recorded data rather than the Data Bank.
Browser Settings - the browser settings are as follows:
Browser Emulation - specifies the type of browser to emulate.
Connection Speed Emulation - specifies the line speed to simulate for the virtual user's Internet connection. Set the speed to a specific number if you want the virtual user to simulate a dial-up connection using a modem, DSL, or other speed. Set the speed to True Line Speed if you want the virtual user to run using the actual connection speed.
Cache Emulation - specifies the type of user to simulate. This is useful for simulating different profiles of virtual users. A first time user places more of a load on the Web server because pages and image are not yet cached. A repeat user places less of a load on the server as only newer pages are requested and brought down from the Web server. There are three options:
Do Not Cache - cache is not used.
Note:
When using WinInet, selecting Do Not Cache has the same effect as selecting 1st Time as the Cache Emulation method. In this case, document cache is not created and not cleared. When using Thin Client for JHTTP, selecting Do Not Cache does not create cache or clear it. When the Cache Emulation method is set to 1st Time for Thin Client for JHTTP, cache is created and cleared after each iteration which can consume considerable amounts of memory.1st Time - the virtual users are considered to be using the Web site or application for the first time for each iteration so no cache is used. The cache is used during the iteration.
Repeat - the virtual users are considered to have visited or used the Web site or application previously. Pages and images are retrieved from the cache.
Use IP Spoofing - when true, Oracle Load Testing for Web Applications uses different IP addresses for Virtual User agents. Each virtual user must get a defined IP address. You must define the IP addresses available for use by Oracle Load Testing for Web Applications Agents in the TCP/IP network protocols of the system. All IP addresses must be added to each Agent system. When using IP spoofing, it is recommended that VUs run with Thin Client without WinInet or with Java Client. See Using IP Spoofing with Oracle Load Testing for Web Applications in Chapter 5 for additional information.
Use Download Manager - when true with Thin Client or Java Client User Mode, filters specified and enabled in Download Rules (select Options from the Tools menu) will be used to download objects as part of virtual user playback. When true with Thick Client User Mode, image objects will be downloaded as part of virtual user playback. Downloaded objects will be included as timers if you have Auto generate timers for all resources selected in the Scenario Defaults ( select Options from the Tools menu) and save data for reporting.
Use Winninet - when true, Oracle Load Testing for Web Applications uses its Microsoft Win32 Internet (WinInet) application programming interface (API) version of the Thin Client agent. When false, Oracle Load Testing for Web Applications uses a custom (JHTTP) version of the Thin Client agent (referred to as "Thin Client for JHTTP").
Enable Cookies - when true, the virtual user profiles will use cookies. Use this setting if your Web application uses cookies to manage session and other context information.
Extensibility - the extensibility settings are as follows:
Execute User Defined Tests - when true, Oracle Load Testing for Web Applications runs Oracle Functional Testing for Web Applications Text Matching and Server Response tests.
Execute User Defined Scriptlets - when true for Thick or Thin client, Oracle Load Testing for Web Applications runs Test Scriptlets included in Oracle Functional Testing for Web Applications Visual Scripts. Scriptlets are not executed when using the Java Client regardless of how this option is set. See the Oracle Functional Testing for Web Applications User Guide for more information about using Test Scriptlets with Oracle Functional Testing for Web Applications.
VU Display - the VU Display settings are as follows:
View All Responses - select when you want to display all responses, on error, always, never.
Show Request Headers - select when you want to display request headers, on error, always, or never. When displayed, request header information for Web page resources requested by the selected Virtual User appear in the Virtual User Display history list.
Show Response Headers - select when you want to display response headers, on error, always, or never. When displayed, the Response header information for Web page resources requested by the selected Virtual User appear in the Virtual User Display history list.
Reporting - the Reporting settings are as follows:
Auto Generate Timers For All Pages - when true, Oracle Load Testing for Web Applications automatically adds timers for each Visual Script page for reporting. The timers are used in Oracle Load Testing for Web Applications to provide performance monitoring and timing information for each page of the Visual Script(s) played back by a virtual user profile.
Auto Generate Timers For All Resources - when true, Oracle Load Testing for Web Applications automatically adds timers for all resources for monitoring and reporting purposes. Resources include images and other objects downloaded from the server as specified by the Download Rules setting (select Options from the Tools menu).
Error Handling - the Error Handling settings are as follows:
Object Download Errors Are Fatal - when true, a Web page object download error is considered a fatal error that ends the current iteration.
Zero Length Download Errors Are Fatal - when true, a server response that indicates zero bytes length is considered a fatal error. Set this setting to false if your Visual Scripts are recorded as Siebel scripts.
On Error Stop Virtual User - when true, all virtual users are stopped if an error is encountered.
Request Timeout - specifies the maximum amount of time a virtual user waits to access a page before timing out.
Advanced - the Error Handling settings are as follows:
Maximum Users Per Process - sets the maximum number of virtual users per single agent process. When running virtual users as threads in a single process, Maximum Users Per Process sets the maximum number of virtual user threads in a single process. Oracle Load Testing for Web Applications spawns new processes if the number of virtual users exceeds the maximum number in any single process and runs the additional virtual uses as threads in the new process.
The default setting is unlimited virtual users per agent process.
Maximum HTTP Threads Per Process - specifies the number of threads per agent process for optimizing the pooling of virtual user requests into a finite number of I/O worker threads.
Maximum HTTP Connections Per User - specifies the maximum number of server connections per process per server. Each VU makes multiple connections to request additional resources for images and additional frames for example. Setting this option specifies a limit on the total number of connections that the VU s can make to the server. The default setting is "Default," which means use the default connection limits as configured on the agent machine. (See Microsoft KBase article Q183110 for more information.) This setting is used to override the agent machine configuration for Thin Client agents using WinInet.
Ignore HTTP Proxy Settings - specifies whether to ignore the agent machine's default proxy setting as defined in Internet Explorer.
Java Client Preferences - these options only appear when User Mode is set to Java Client. When a setting is set to the default value, this means that the value that will be used is what is set in the OracleATS\OFT\jagent\ JavaAgent.properties file, unless a value is not set in the JavaAgent.properties file. In this case, the Java Agent uses the internal default value.
Report Counters - when true, Oracle Load Testing for Web Applications counters are reported.
Maximum Bytes of VU Display - when you select other, enter the number of bytes to send to the VU display per item, that is, a request is one item, a response is an item, and content is an item. The default in the JavaAgent.properties file is-1, which returns everything. The value entered roughly equates to the number of characters.
Report Sender Interval - when you select other, enter the time in milliseconds for how frequently the agent reports its status and accrued counters. The default in the JavaAgent.properties file is 5000.
Maximum JVM Heap Size (MB) - specifies the maximum size of the JVM heap. This value cannot be more than 90% of the total memory size.
Proxy Host - select other to enter the proxy host and override the system-specified proxy host.
Proxy Port - select other to enter the proxy port and override the system-specified proxy port.
Non Proxy Hosts - select other to enter non-proxy hosts. Delimit multiple hosts with a bar (|).
Enable Deflate - when true, deflate compression support is enabled.
Language - when you select other, enter the language to override the Accept-Language header. The default is the locale assigned by the JVM.
Accept String - this setting controls what the Accept: HTTP header value looks like. When you select other, enter the string. The default in the JavaAgent.properties file is: text/html, image/gif, image/jpeg, */*. If you modify a navigation in a script by adding a custom Accept: header, the custom header value from the script is used instead.
Preserve Connections Between Iterations - used to preserve connections between OpenScript and the browser between successive iterations of the script.
Preserve Variables Between Iterations - used to preserve or automatically clear variables added in the Run section of OpenScript scripts between successive iterations of the Run section.
Preserve Cookies Between Iterations - used to preserve or automatically clear cookies added in the Run section of OpenScript scripts between successive iterations of the Run section.
Max Number of Keep Alive Requests - select other to specify the maximum number of requests to make on a keep alive connection before closing it.
Download Local Files - when true, the Java Agent retrieves the requested local file contents.
Max Content Download Size - specifies the maximum size for downloads. You can specify Unlimited or Other. If you select Other, specify the maximum size in kilobytes.
Agent Inactivity Timeout - specify the length of time, in milliseconds, that Oracle Load Testing for Web Applications will wait to hear from the agent before it assumes that the agent is not available.
Ignored Url - specify the Urls, separated by commas, that should not be requested. This setting only applies to certain OpenScript scripts.
The Autopilot Defaults options let you specify the default settings for the Set up Autopilot tab. Refer to "Chapter 6" for a description of these options.
Sessions specify the scope for Oracle Load Testing for Web Applications data collection and reporting. The data collected while the Autopilot is running virtual users is shown in the virtual user grid, runtime performance statistics and load graphs, and can be saved to a database for post-testing analysis in the Analyze Results tab.
You can specify default settings for how sessions start and end data collection bu selecting Options from the Tools menu then selecting Start and Stop. See Chapter 5 for a description of these options.
These options specify the default characteristics for graphing and reporting. Unique session profiles are created for multiple instances of a script if the selected settings have different values.
Session Profile OptionsFor example, if you are running two profiles emulating different browsers, check the Browser Emulation attribute to view separate plot lines in the graphs for each browser.
Use these options to specify the parameters for refresh intervals and for creating profile timer names when generating timers for all resources. See Chapter 8 for a description of these fields.
These options set the Data Bank control defaults that will be displayed when you click the Configure Data Bank button for a script or profile on the Build Scenarios tab.
Record buffer size - specifies the number of Data Bank records allocated to each Oracle Load Testing for Web Applications agent.
Data Usage - lets you select which records to use.
Loop Forever - specifies that the virtual users cycle through the Data Bank records until the load test finishes.
Use All Records - specifies that the virtual users use all of the records in the Data Bank and then stop. For example, if the virtual users start at record 50 of 100, they run from 50 to 100, then loop back and run from record 1 to 49 and then stop.
Stop After Last Record - specifies that the virtual users stop when the end of the Data Bank has been reached regardless of the starting point in the Data Bank. For example, if the virtual users start at record 50 of 100 records, they run from record 50 to record 100 and then stop.
First Record Only - specifies that each virtual user takes the next record in the Data Bank and keeps on using that same record for each iteration. Use this setting if you want each virtual user to keep the same data for each iteration.
These options determine whether Oracle Load Testing for Web Applications will validate the hostname/IP address when you add a system.
Validate hostname/ip when user adds a system - checks to see if the Oracle Load Testing for Web Applications server can connect to the specified system. If it cannot, Oracle Load Testing for Web Applications displays a dialog box asking you if you want to proceed anyway.
Validate monitors when user adds or modifies a monitor - checks to see if the monitor can be applied to the target system when you create a monitor.
When Oracle Load Testing for Web Applications Server IP address changes - restarts or stops the Oracle Load Testing for Web Applications Application Service when the state of the network changes.
Restart Application Service - restarts the application service when the IP address changes.
Stop Application Service - stops the application service when the IP address changes.
Polling interval for network status check - the interval, in seconds, for checking the network status.
|
 Copyright © 1997, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|