This chapter explains how to get started using Oracle Load Testing. It explains how to install and start the program, and the features of the main window.
The installation for Oracle Load Testing depends upon how you plan the virtual user test configuration. At a minimum, you need to install Oracle Load Testing 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 to use as a "Master" station and install the Oracle Load Testing Agent (or another seat of Oracle Load Testing) on the client machines to use as virtual user Agent stations.
The following sections explain the procedures for installing Oracle Load Testing and the Oracle Load Testing Agent.
The Oracle Load Testing setup procedure installs both Oracle Load Testing Server and Oracle Load Testing Agent. You should not install Oracle Load Testing Agent separately on the same system. To install Oracle Load Testing:
Go to: http://www.oracle.com/technetwork/oem/downloads/index-084446.html.
Download the Oracle Application Testing Suite product from the Oracle Web site and save it to a temporary directory on your hard disk. See the Oracle Application Testing Suite Installation Guide for additional information about the product zip files.
Unzip the download file and then run setup.bat.
Follow the setup instructions to install the Oracle Application Testing Suite.
Note:
A product establishes its Default Repository in $installDir/OFT, where $installDir is the directory where Oracle Application Testing Suite is installed or, if Oracle Application Testing Suite is not installed, where OpenScript is installed.During the Oracle Application Testing Suite installation, you will be required to enter a master password to be used with Oracle Application Testing Suite products. Remember this password. It will be required to log in to the Administrator, Oracle Load Testing, and Oracle Test Manager.
For Windows installations, select Oracle Load Testing from the Oracle Application Testing Suite Start menu or enter http://<machine>:8088/olt or http://localhost:8088/olt in your browser where <machine> is the name of the machine where the Oracle Application Testing Suite is installed.
For Linux installations, enter http://<machine>:8088/olt or http://localhost:8088/olt in your browser where <machine> is the name of the machine where the Oracle Application Testing Suite is installed.
Two default administrator accounts are created at installation. The usernames for the default accounts are administrator and default. The default password for both the administrator and default accounts is the master password specified during the Oracle Application Testing Suite installation process. Use the Oracle Application Testing Suite Administrator to customize the Oracle Load Testing database by creating user accounts, assigning user names and passwords, and assigning the type of access that they have in Oracle Load Testing. See Section 3.9, "Administrator" for additional information about using the Oracle Application Testing Suite Administrator.
Use the Oracle Application Testing Suite Database Configuration utility to configure database connections to Oracle Load Testing databases. On Windows machines, you can access the Database Configuration utility from the Tools sub menu of the Oracle Application Testing Suite Start menu. On Linux machines, you can access the Database Configuration utility from <oats_install>/bin/DbConfig.sh.
Oracle Load Testing starts in an existing browser if one is available. To set Oracle Load Testing 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.
The follow are the preconditions for running OpenScript functional test scripts with Oracle Load Testing:
Installation Requirements:
Linux: Must have installed 'vnc server'(4.2) and 'firefox'(ESR 31, 38, 45).
Windows: Must enable and start remote desktop service. Windows 2008 R2 is the minimum supported system. Windows 7 is not supported as Windows 7 only allows the single primary user of the licensed computer to access a session of the computer.
Privilege & License Requirements:
Linux: IPtables shall have rules accepting vnc server listen ports (5901-59**).
Windows: The agent system must have enough licenses to support the required number of the concurrent RDP sessions.
Windows: Configure 'Oracle ATS Agent' service to "Allow service to interact with desktop".
Go to Windows Services (Select Start, then Run, and enter services.msc or Go to Control Panel, Administrative Tools, then Services).
Select 'Oracle ATS Agent' service then right-click and select Properties.
Select the Log On tab, then select Local System account and select the Allow service to interact with desktop checkbox.
Click OK.
Click 'Restart the service' to restart the service.
Enabling the Allow service to interact with desktop checkbox is a one time requirement. After enabling this option and playing back Functional Test scripts one time on the agent, this setting can be disabled if you do not want to see the RDP session (which contains the browser playback within the session).
Windows: The agent system must have the required privileges to create windows accounts with 'remote desktop user group' privileges.
Windows: The User Account Control (UAC) level that controls Windows notifications on the agent system must be set to "Never Notify" - the least secure setting. This is not the default setting for Windows.
Windows: Internet Explorer Enhanced Security Configuration on the agent system must be disabled for the Administrators group (which includes all of the user accounts for the OLT functional test support). This is not the default setting for Windows.
The Oracle Application Testing Suite setup, installation, configuration and other scripts do not make these changes and security settings are not modified as part of the account creation for playback. These requirements must be manually configured by functional test users.
Encrypted Script Requirements:
You will need the password(s) for Oracle OpenScript scripts that use password protected encryption. When you add a password protected script to configure parameters in the Build Scenarios tab, the Import Script Password dialog box opens for specifying the script password.
Popup blockers must be turned off for Oracle Load Testing 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 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 a Windows agent machine, change the oracle.oats.agentmanager.port setting in the <installdir>\agentmanager\agentmanager.properties file.
To change this port on a Linux agent machine, do one of the following:
<installdir>/agentmanager/bin/agentmanager.sh --verbose --port=<new port>
start
AM_PORT=<#portnum> in /etc/init.d/OracleATSAgent and then restart the ATS agent.
In addition, change the port in the system configuration in Oracle Load Testing by selecting Options from the User menu then selecting VU Agent Systems in the Systems group. 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 agentmanager.properties file.
To run Oracle Load Testing, it is recommended that you have the following general communication ports open before starting the Oracle Load Testing Application Service.
http=8088 agent=9001 dataCollector=9001 webservice=8083 https=8089
To change the ports:
Go to http://localhost:8088/console to start the WebLogic Console.
Log in as username "oats" and 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.
In <oats-home>/config/oats-config.xml update http, admin, and cluster URLs with appropriate port specifications.
Restart the ATS service and login to Oracle Load Testing or Oracle Test Manager.
See the Oracle WebLogic Server documentation for additional information about using the Console application.
The following ports are used between the Oracle Load Testing Server and the Agent Machine itself:
9001
8088
The Oracle Load Testing Agent is a subset of the full Oracle Load Testing installation. You should not install the Oracle Load Testing Agent if you have Oracle Load Testing installed on the system. You install Oracle Load Testing Agent on the agent systems 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 Agent:
Run the downloaded setup.bat installation program from the download zip file.
Follow the setup procedure to the Select Components and Installation Directory screen.
Click Next as necessary to complete the installation.
Verify network access from Oracle Load Testing 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 by selecting Options from the User menu menu and selecting Systems.
Once the Oracle Load Testing 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 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 automatically accesses and starts the Agent when you start a Session.
Once you have the Oracle Load Testing and Agent software installed on the individual systems, you should verify network access between the Oracle Load Testing system and each Agent system. This section provides basic tips and techniques to make sure that Oracle Load Testing can successfully communicate with each Agent system.
Make sure that you have the Oracle Load Testing 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 system. The systems you plan to use as agents must have either the Oracle Load Testing Agent software or the full Oracle Application Testing Suite installed to work as agents. It is not recommended to use the local Oracle Load Testing Agent and the Oracle Application Testing Suite server 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 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 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 system, you will not be able to run the agents from the Oracle Load Testing system.
In the Oracle Load Testing system, add a 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 script into the System field on the Build Scenarios tab of Oracle Load Testing.
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 agents:
Open Administrative Tools in the Control Panel then open Services. The Services dialog box displays.
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.
Oracle Application Testing Suite server components (Oracle Load Test/Oracle Test Manager) and Agent components (Oracle Load Test agent/Data Collector) can be installed on Linux via a separate installer; however Oracle OpenScript is Windows only.
See the instructions in the Oracle Application Testing Suite Installation Guide for details about installing the applications and agent on Linux machines.
Once the Linux agent is installed, define the remote agent system in the Oracle Load Testing Options.
When you define your Oracle Load 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 automatically accesses and starts the Agent when you start a Session.
In some cases, it may be necessary to move an existing Oracle Application Testing Suite installation from one machine to another. This could be either for an Oracle Application Testing Suite software upgrade or a hardware upgrade.
There are several steps involved in moving an existing installation to another machine.
Transfer database schemas
Install Oracle Application Testing Suite and configure database connections
Copy repositories, workspaces, scripts, and files not stored in a repository:
Oracle Load Testing scenarios,
Oracle Load Testing ServerStats metrics,
customized files,
data files.
Restart the Oracle Application Testing Suite service and verify the setup on the new machine.
The following sections describe the steps.
Transfer the OATS, OTM, and OLT database schemas using the expdp and impdp database utilities, as follows:
Log into SQLPlus as system user and do the following:
CREATE DIRECTORY bkp_dir AS 'C:\backup';
Execute the following from the server\BIN directory of Oracle database (e.g. C:\OracleATS\oxe\app\oracle\product\1x.x.0\server\BIN) where x.x is the version number of Oracle Application Testing Suite installation:
expdp system/<passwd>@xe schemas=OATS directory=bkp_dir dumpfile=oatsbkp_x.x.dmp logfile=oatsbkpexp_x.x.log expdp system/<passwd>@xe schemas=OLT directory=bkp_dir dumpfile=oltbkp_x.x.dmp logfile=oltbkpexp_x.x.log expdp system/<passwd>@xe schemas=OTM directory=bkp_dir dumpfile=otmbkp_x.x.dmp logfile=otmbkpexp_x.x.log
In the new machine, install your database.
Log into SQLPlus as system user and do the following:
CREATE DIRECTORY bkp_dir AS 'C:\backup';
Copy the backup dump files to the new machine.
Execute the following from the server\BIN directory of Oracle database (e.g. C:\OracleATS\oxe\app\oracle\product\10.2.0\server\BIN) where x.x is the same version number used for step 2:
impdp system/<passwd>@xe schemas=OATS directory=bkp_dir dumpfile=oatsbkp_x.x.dmp logfile=oatsbkpimp_x.x.log impdp system/<passwd>@xe schemas=OLT directory=bkp_dir dumpfile=oltbkp_x.x.dmp logfile=oltbkpimp_x.x.log impdp system/<passwd>@xe schemas=OTM directory=bkp_dir dumpfile=otmbkp_x.x.dmp logfile=otmbkpimp_x.x.log
This section explains the installation and database configuration steps for using an existing database.
Install the Oracle Application Testing Suite on the new machine. When the Oracle Database installation screen appears, select "Configure an existing Oracle XE or EE Database" and manually enter system password which was used for DB installation.
During database configuration, the installation will prompt the following message:
"Warning: The database you have configured already contains the OLT and OTM schemas. You will need to run the Database Configuration Utility to re-configure these schemas after installation completes"
After the installation completes, select Oracle Application Testing Database Configuration from the Tools submenu of the Oracle Application Testing Suite Start menu.
Select Oracle Load Testing.
Click the New icon on the Database Connections toolbar.
Select Use existing schema and specify the Connection details for the existing database.
Name - OLT (can be anything).
Description - enter any description for the existing database.
Hostname, port, service of database instance.
Username - olt (must be "olt").
Password - the olt user password (the password specified during the Oracle Application Testing Suite installation).
Optionally, select Insert sample data.
Click Save.
In the new dialog box that opens, enter the password for the "Administrator" and "Default" accounts.
Set the new OLT database as current by clicking the Set Current (check mark) icon on the toolbar. Click OK in the confirmation message.
Select Oracle Test Manager.
Click the New icon on the Database Connections toolbar.
Select Use existing schema and specify the Connection details for the existing database.
Name - OTM (can be anything).
Description - enter any description for the existing database.
Hostname, port, service of database instance.
Username - otm (must be "otm").
Password - the otm user password.
Optionally, select Insert sample data.
Click Save.
Select Configuration schema.
Click the New icon on the Database Connections toolbar.
Select Use existing schema and specify the Connection details for the existing database.
Name - OATS (can be anything).
Description - enter any description for the existing database.
Hostname, port, service of database instance.
Username - oats (must be "oats").
Password - the otm user password.
Click Save.
Any files not stored in a repository folder will need to be copied manually from the old machine to the new machine. Close all Oracle Application Testing Suite applications before copying files.
Copy the following file types from the old machine to the new machine.
If your repositories were stored on the local machine, copy Repository folders and scripts from the old machine to the new machine. Make sure the folder names and directory structure are all the exact same. The default repository is <installdir>/OFT.
databank files (*.csv, *.txt saved to your custom directories).
OLT Scenario files (*.scn and *.scnzip files not stored in a repository).
OLT Session data files (*.osd saved to your custom directories).
"custom" ServerStats Configurations (*.config files stored in <installdir>/config/serverstats).
"custom" ServerStats Metrics (*.metric files stored in <installdir>/config/serverstats).
"custom" ServerStats Metric Profiles (*.hwm or *.zip files stored in <installdir>/config/serverstats).
"custom" MIBS added to ServerStats (*.mib files stored in <installdir>/config/serverstats/mibs).
"custom" Report Template files (*.rtf files saved to your custom directory).
"customized" template.properties file in the <installdir>/data/olt/reports folder.
"custom" data files (*.dat files saved to your custom directory).
any saved or exported report files.
any other custom files used with Oracle Application Testing Suite stored on the old machine.
To restart the Oracle Application Testing Suite service:
Open Control Panel.
Open Administrative Tools.
Open Services.
Select Oracle ATS Server and click Restart the service.
After the service restarts, open each Oracle Application Testing Suite application and verify the setup matches the old installation.
Repositories specify the location to use to store scripts and related asset files. Repositories also provide a way to share files between OpenScript and Oracle Load Testing. Oracle Load Testing requires that all assets live inside of a named Repository. Oracle Load Testing will not be able to find an asset located in the local file system outside of a repository. Any shared directory can be used as a repository. However, all repositories shared between Oracle Load Testing, Oracle Test Manager, OpenScript, and team members must share the same repository name. For example, if one member of a team calls a shared repository SharedRepo1, but another member of a team calls the same shared repository Shared_Repository_1, it is possible that some script assets may not be found when the team members share scripts.
To reduce the chance of local repository name conflicts, it is recommended that you create a new local repository named something unique to the user, such as <machineName>.<windowsUserName>.MyRepository. Store in this folder all scripts that are not intended to be shared among team members.
Best Practices:
Always store scripts and assets (i.e. databanks, .jar files, etc.) inside named repositories.
Avoid selecting the Save path relative to current script option in OpenScript when saving scripts.
Establish a consistent repository naming scheme across all Oracle Load Testing, Oracle Test Manger, and OpenScript installations.
Avoid using the repository named "Default" for storing local scripts. Use "machineName.Default" instead.
To add a repository:
Select Options from the User menu.
Select Repositories in the Manage group of the left pane.
Click New. A new entry is made in the table.
Enter the name of the repository.
Note:
When using OpenScript scripts with Oracle Load Testing, the repository names you specify should match the repository name specified in OpenScript (including case).Enter the location of the repository.
The default Oracle Load Testing web server port is 8088. You can change this to another port. The port number must be changed in the WebLogic Console and the Oracle Application Testing Suite configuration.
To change the port in the WebLogic Console:
Go to http://localhost:8088/console to start the Oracle WebLogic Server Administration Console.
Log in as an administrator (the default username is "oats") 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.
See the Oracle WebLogic Server Administration Console documentation for additional information about using the Console application.
In <oats-home>/config/oats-config.xml update http, admin, and cluster URLs with appropriate port specifications.
Restart the ATS service and login to Oracle Load Testing or Oracle Test Manager.
To change the port in the Oracle Application Testing Suite configuration:
Open the file <oats-home>/config/oats-config.xml in a text editor.
Change the port number from 8088 to the new value in all property keys where the port number is used.
Save the file.
Open the Registry Editor (regedit) and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\OracleATSServer\Parameters
Change the Port value to the new Port number and close the Registry Editor.
Open the Control Panel and then open Services in the Administrative Tools.
Restart the "Oracle Application Testing Suite Application Service" service.
Login to Oracle Load Testing and select Options from the User menu, and then select ServerStats Data Collectors in the Systems group.
Select your Oracle Load Testing server system, click Edit, enter the changed port number, and click Save.
If you are using remote data-collectors (non-localhost), Steps 6 and 7 should not be performed.
You can set up Oracle Load Testing 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 "oats" 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 default JVM Heap size is sufficient for most common load testing scenarios. However, it may not be suitable to operate efficiently when executing large, long-running load tests or load tests that generate verbose logging, such as when logging of all VU Log request/response details is enabled. Tuning the JVM Heap settings that are specific to your system becomes critical in such cases. This section describes how to modify the maximum Heap size for the Oracle Load Testing controller and specifies the values to enter that are specific to your system.
The following are the basic guidelines for the settings to use for the maximum JVM heap size:
On Linux machines:
32bit - Set the maximum JVM Heap size to -Xmx2g
64bit - Set the maximum JVM Heap size to -Xmx3g
On Windows machines:
32bit - User can not set more than 1 GB heap size
64bit - Set the maximum JVM Heap size to -Xmx3g
Where:
-Xms = Starting heap size (default is 256m)
-Xmx = Maximum Heap size (default is 512m)
To modify the heap setting on Windows machines:
Stop the Oracle ATS Server service. Use Services in the Control Panel or net stop OracleATSServer in a command window.
Open the Windows Registry Editor (Regedit.exe).
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\OracleATSServer\Parameters.
Select the key named CmdLine.
Select Modify from the Edit menu of the Registry Editor.
In the Value Data field, modify the startup value for the Heap from -Xms256m to desired value. For example, to update the value to use a 1GB Heap, modify the value to -Xms1g.
In the Value Data field, modify the maximum value for the Heap from -Xmx512m to desired value. For example, to update the value to use a 2GB Heap, modify the value to -Xmx2g.
Click OK.
Close the Registry Editor
Start the Oracle ATS Server service. Use Services in the Control Panel or net start OracleATSServer in a command window.
To modify the heap setting on Linux machines:
Stop the Oracle ATS Server daemon (service). For example, /etc/init.d/OracleATSServer stop.
Open the daemon script for editing using a text editor of your choice. For example, nano -w /etc/init.d/OracleATSServer.
Locate the line: "export USER_MEM_ARGS="-Xms256m -Xmx512m".
Modify the startup value for the Heap from -Xms256m to desired value. For example, to update the value to use a 1GB Heap, modify the value to -Xms1g.
Modify the maximum value for the Heap from -Xmx512m to desired value. For example, to update the value to use a 2GB Heap, modify the value to -Xmx2g.
Close the editor.
Start Oracle ATS Server daemon (service). For example, /etc/init.d/OracleATSServer start.
Users of 32-bit Windows Systems should leave the current default settings unchanged. However, you can enable the 4GT feature in your 32-bit edition of Windows to request a larger heap from the Operating system. Once you have enabled this feature you can then change the maximum Heap size setting to 2GB(-Xmx2g).
The Oracle Load Testing Controller also requires the Windows Weblogic patch in order to use the 4GT tuning feature. If you are running large load tests using Oracle Application Testing Suite version 9.31 on Windows 32-bit systems, you should upgrade to version 9.31.044 or later and set Windows 4GT tuning. Only version 9.31.044 and higher will allow the heap to be set to the recommended -Xmx2g, and only when the Windows 32-bit system has 4GT tuning applied.
On 32-bit Linux Systems, change the maximum Heap size setting to 2GB (-Xmx2g).
On 64-bit Systems, the recommend maximum Heap size setting is 3GB(-Xmx3g).
The Oracle Application Testing Suite tools menu has options for viewing version 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 and version information. It also has information about your system.
Create Support Package - 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. On Linux machines, use <oats_install>/bin/oats_support.sh to create support packages.
Oracle Application Testing Database Configuration - opens the database configuration utility for adding or removing database connections for Oracle Load Testing and Oracle Test Manger. On Linux machines, use <oats_install>/bin/DbConfig.sh to start the database configuration utility.
Oracle Load Testing Agent Authentication Manager - opens the Agent Authentication Manager for defining authentication profiles for multiple load testing agent machines. On Linux machines, use <oats_install>/jdk/jre/bin/java -jar <oats_install>/agentmanager/AMAuthManager.jar to start the Agent Authentication Manager.
Restart Oracle Application Testing Suite Application Service - stops and restarts the Oracle Application Testing Suite Application service. On Linux machines, use <oats_install>/bin/restartSvc.sh [OracleATSServer|OracleATSAgent]to restart the service.
Stop Oracle Application Testing Suite Application Service - stops the Oracle Application Testing Suite Application Service. On Linux machines, use <oats_install>/bin/stopSvc.sh [OracleATSServer|OracleATSAgent]to stop the service.
The Administrator allows you to create user accounts, assign them user names and passwords, and assign the type of access that they have in Oracle Load Testing, none, full control, or view only. The Administrator also lets you optionally enable authentication for Oracle Load Testing. When Oracle Load Testing login is enabled, users must login to access Oracle Load Testing.
Two default administrator accounts are created at installation. The usernames for the default accounts are administrator and default. The default password for both the administrator and default accounts is the master password specified during the Oracle Application Testing Suite installation process. You can change the password after logging in to the Administrator. It is recommended that you change the default password as soon as you log in.
For Windows installations, select Administrator from the Oracle Application Testing Suite Start menu or enter http://<machine>:8088/admin or http://localhost:8088/admin in your browser where <machine> is the name of the machine where the Oracle Application Testing Suite is installed.
For Linux installations, enter http://<machine>:8088/admin or http://localhost:8088/admin in your browser where <machine> is the name of the machine where the Oracle Application Testing Suite is installed.
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.
The Users tab is where you add, edit, and delete users and specify what Oracle Load Testing 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.
Restore - displays the Restore Previously Deleted User dialog box for restoring a previously deleted user to the users list.
Username - displays the user name for logging in to Oracle Load Testing.
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.
Administrator Access - displays whether the user can access the Administrator.
The Usage Audit tab is where you review and audit the load testing sessions stored in the Oracle Load Testing database.
OLT Databases - lists the installed Oracle Load Testing Databases available for auditing.
User Name - shows the name of the user who ran the load test. "Anonymous" indicates the login feature was disabled for the instance of Oracle Load Testing that ran the test and there is no username associated with the test. "Command Line" indicates the load test ran from the command line interface.
Session Name - shows the name of the load testing session.
Start Time - shows the start date and time for the load testing session.
End Time - shows the end date and time for the load testing session.
Duration (HH:MM:SS) - shows the duration of the load testing session in hours, minutes, and seconds.
Machine Name - shows the name of the machine on which the load testing session was run.
Max VU Count - shows the maximum count of Virtual Users that were run for the load testing session.
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.
Access - sets the type of access the user has in Oracle Load Testing.
Full Control - the user has full control in Oracle Load Testing.
View Only - the user cannot run tests but can view reports.
Enable Administrator Access - gives this user the ability to log on to the Oracle Load Testing 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.
Access - sets the type of access the user has in Oracle Load Testing.
Full Control - the user has full control in Oracle Load Testing.
View Only - the user cannot run tests but can view reports.
Enable Administrator Access - gives this user the ability to log on to the Oracle Load Testing Administrator for managing the database.
Make any changes.
Click OK.
To delete a user:
Select the user you want to delete.
Click Delete.
Click Yes when asked to confirm the deletion.
You can restore a previously deleted user to the user list. To restore users:
Click Restore.
Enter the Username of the user to restore.
Click OK.
To audit usage:
Click the Usage Audit tab.
Select the database. The session information appears in the right pane of the Usage Audit tab. See Section 3.9.3, "Usage Audit Tab" for additional information.
The Oracle Load Testing main window is where you perform the majority of your load/performance testing activities. The main window consists of the menu bar, toolbar, and three main tabs. Each tab contains sub-tabs for configuring scenarios, viewing active session data and generating post-session reports.
The Oracle Load Testing User menu has the following options:
Account Info - opens account information.
Options - opens the options dialog for specifying Oracle Load Testing options.
Help - opens the help contents.
Log Off - logs out of Oracle Load Testing.
The toolbar has the following buttons:
New Scenario - Creates a new Oracle Load Testing scenario.
Open Scenario - Opens an existing Oracle Load Testing scenario to run or modify.
Save Scenario - Saves any changes to the currently open Oracle Load Testing scenario. If the scenario has not been saved before, Oracle Load Testing asks for a filename.
Run Now - starts the current scenario immdiately.
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 Composer tab is where you specify which scripts to include in the scenario, the VU ramp options, testing goals, and ServerStats monitoring options.
Scenario name menu - shows the current scenario name. The menu has the following options:
New - creates a new scenario.
Open - opens an existing saved scenario.
Save - saves the current scenario.
Save As - saves the current scenario to a new name.
Import - imports an existing saved scenario.
Export - exports the current scenario.
The Composer tab has the following main toolbar buttons:
New Scenario - creates a new scenario.
Load Scenario - opens an existing saved scenario.
Save Scenario - saves the current scenario.
The Composer tab has the following sub-sections:
Profiles
Ramp
Goals
Monitoring
The Profiles section is where you specify the scripts to include in the scenario and the profile options for each script. The Profiles section has the following panels:
Scripts
Profiles
Properties
The Scripts panel includes the script tree and toolbar.
The Available Scripts list shows the Oracle OpenScript scripts in the current repository/workspace.
The scripts toolbar has the following options:
Add to Scenario - adds the currently selected script to the Profiles list.
Path - shows the directory path of the selected repository. The default repository is the OFT folder in your installation directory. New repositories can be created by selecting Options from the User menu then selecting Repositories in the Manage group.
<Script list> - a list of Oracle OpenScript scripts that are available to include in virtual user scenarios. Scripts can be both load testing-type scripts and functional testing-type scripts. See the preconditions for functional testing-type scripts in Section 3.1.2, "Preconditions for Using Functional Testing Scripts".
You can click and drag scripts to the Profiles panel or select scripts and click the Add to Scenario button.
The Profile panel shows the scripts selected for the current Oracle Load Testing scenario. You can configure each using the options provided here or in the Properties panel for the selected script.
You can change the fields that are displayed and the default values for each field by selecting Options from the User menu then selecting Default Properties in the Profiles group and checking or unchecking the Table View option.
Show/Hide Scripts tree - opens the Available Scripts panel if it is hidden or closes the Available Scripts panel if it is visible.
Virtual User Scale - specifies the maximum number of virtual users to which to scale the load test. Editing this value will distribute virtual users among all scripts in the scenario.
VU Distribution - opens a graph showing the Virtual User distribution.
Table View - Shows the profile list in table view. Properties for selected profiles can be set in the Profile table and the Properties panel.
Icon View - Shows the profile list in Icon view. Properties for selected profiles can only be set in the Properties panel.
Profile - a list of scripts selected to be in the load scenario. In Table view, the fields displayed here can be customized by selecting Options from the User menu then selecting Default Properties in the Profiles group. Select the fields you want to display by checking the field's corresponding checkbox in the Table View column.
Max # VUs - specifies the number of virtual users to run for the selected profile. For each virtual user, Oracle Load Testing runs a separate instance of the script(s) specified in the virtual user profile. For functional testing-type scripts, a warning indicator appears if you specify more VUs than the maximum allowed for the Oracle Load Testing Agent machine.
Agent 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 Server or Oracle Load Testing Agent from the option dropdown. Systems are defined using the VU Agent Systems 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.
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 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. For functional testing-type scripts, the number of VUs may be limited by the number of accounts available on the Oracle Load Testing Agent machine (Remote Desktop for Windows, VNC for Linux).
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 Ramp options.
VU Pacing - specifies the 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 OpenScript script. You can set minimum and maximum delay times (in seconds) that override the 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 sets the low end of the random range as the actual recorded user delay minus the Lower percentage setting. Oracle Load Testing 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 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 scripts at the fastest possible speed with no time between page requests.
Delete - deletes the selected profile from the scenario.
For information about the Selected VU Profile settings see Chapter 5, "Creating Scenario Profiles".
Displays the Properties for configuring the parameters of the script selected in the Profile panel. Select the script name in the Profiles pane and set the settings.
The Profile Settings are listed in the Profile Settings. Note that the settings differ between load test-type (protocol based) scripts and functional test-type (DOM based) scripts.
The Ramp section lets you configure the settings for the Virtual User Ramp rate and stop conditions.
Ramp Preview - shows a simulated ramp graph based on the specified ramp rate. Click the Expand/Collapse Ramp Preview button to show or hide the preview panel.
Ramp Rate - specifies the rate at which Virtual Users start.
Stop Condition - specifies when the Virtual Users should stop running.
Advanced - specifies advanced ramp conditions for each Virtual User individually.
Handle ramping of profiles individually - when selected, the advanced ramp conditions will used.
Profile - lists the names of the Virtual User profiles in the scenario. Select individual profiles and click the Ramp Rate, Start condition, and Stop Condition to change the default settings.
Ramp Rate - specifies the rate at which Virtual Users start.
Start Condition - specifies when the Virtual Users should stop running.
Stop Condition - specifies when the Virtual Users should stop running.
The Goals section lets you define specific test goals that specify when to stop ramping up Virtual Users.
Goals - specifies the goals and conditions to use as test goals.
Add Goal - Adds a new goal to the set of goals.
Stop ramping VUs when - specifies which goal condition stops the ramping of virtual users.
any of these goals are met - the ramping of virtual users stops if any of the specified goal conditions are met.
all of these goals are met - the ramping of virtual users stops only when all of the specified goal conditions are met.
Goal 1 (through X) - specifies the goal criteria for the load test. Click the (+) button to add additional goals and conditions. Click the (X) button to remove goals and conditions.
Add Condition - add additional conditions to the current goal.
Goal is met when - specifies the goal condition to achieve:
any of these conditions apply - when selected, the test goal is achieved when any of the specified goal conditions are met. Specify one or more goal conditions.
all of these conditions apply - when selected, the test goal is achieved only when all of the specified goal conditions are met. Specify one or more goal conditions.
Click the (X) button to remove conditions.
Select Counter - opens a list of available script counters to use as the goal condition criteria. For each script counter, the following conditions can be specified for the counter value of the test:
is greater than [value]
is less than [value]
equals [value]
does not equal [value]
Results - specifies the test results to set if the goals are met or not met.
When goals are met, mark load session - specifies the test result to set if the goals are met: No result, Passed, Failed, or custom result.
When goals are not met, mark load session - specifies the test result to set if the goals are not met: No result, Passed, Failed, or custom result.
Edit results values - opens options for editing the results values and creating custom values.
The Monitoring section lets you define specific target systems and metrics to monitor during the load test.
Monitoring Targets - specifies the metrics for monitoring.
New Configuration - clears the current configuration for creating anew configuration.
Open Configuration - opens a dialog box for selecting a saved configuration to open.
Save Configuration - opens a dialog box for saving the current configuration to a new configuration file.
Add Target - opens a menu for selecting target systems for monitoring.
Database - opens a dialog box for specifying a database system to monitor.
Weblogic - opens a dialog box for specifying a Weblogic system to monitor.
Linux - opens a dialog box for specifying a Linux system to monitor.
Windows - opens a dialog box for specifying a Windows system to monitor.
Generic Target - opens a dialog box for specifying any system to monitor.
Existing - opens a list of existing target configurations that have already been created.
Test Configuration - checks to see whether the Oracle Load Testing server can contact the system and displays an informational message indicating if the system is available.
The Active Session tab is where you can view runtime graphs and reports. These graphs are only available for the running load test session. Use the Reports tab to view reports and graphs after the load test has finished running.
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 Session menu provides options selecting active sessions to attach or detach.
The Session Overview tab shows a thumbnail view of each graph and statistics for the active session. Click on a thumbnail to see a full view of that graphs or reports.
The Virtual User Status tab shows the virtual users grid.
The Runtime Graphs tab is used to create a custom runtime graphs. The Runtime Graphs sub-tab is refreshed according to what is set in the Graph refresh interval setting in the reporting options (select Options from the User menu).
The Virtual User Logs tab shows the virtual user information saved to the log file.
The ServerStats tab shows server statistics for metrics being monitored.
The Sync Point Status tab shows sync point status.
For information about reports and graphs, see Chapter 11, "Using Graphs and Reports".
The Reports tab is where you can view reports and graphs for sessions for which you have saved data for reporting.
For information about reports and graphs, see Chapter 11, "Using Graphs and Reports".