This chapter explains how to define the systems that will be used to run Virtual Users for creating load on the application-under -test.
The System Manager, accessed by selecting Options from the User 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 Agent Systems option in the Profiles section of the Composer tab.
New System - displays the Add System dialog box for adding a new VU Agent system.
Edit System - displays the Edit System dialog box for configuring the system name, IP address Start parameters.
Delete System - deletes the selected systems. To select more than one system, hold down the CTRL key.
Name - lists the specified name(s) of the available systems.
Host / IP - lists the specified Host name or IP address of the agent system.
VU Agent System Groups - system groups let you distribute virtual users across multiple VU Agent systems that have been grouped.
New Group - displays the New Group dialog box for configuring a new system group.
Edit Group - displays the Edit Group dialog box for adding or deleting systems from the group.
Delete Group - 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 System - displays the Add System dialog box for adding a new ServerStats data collector.
Edit System - displays the Edit System dialog box for editing the selected data collector.
Delete System - 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 System - displays the Add System dialog box for adding a new system that you want to monitor using ServerStats.
Edit System - displays the Edit System dialog box for editing the selected system.
Delete System - deletes the selected systems. To select more than one system, hold down the CTRL key.
Name - lists the available systems.
Host / IP - lists the specified Host name or IP address of the system.
For more information about using the System Manager, see Section 4.2, "Defining Systems".
Before you can select systems in Oracle Load Testing Scenarios, you must define the machines that are Oracle Load Testing agent systems. Select Options from the User menu then expand the Systems group to define systems that the Oracle Load Testing scenarios can use as agents. Once systems are defined you can add them to System Groups.
You can also add target Monitored Systems in the Monitoring subsection of the Composer tab.
Note:
See the installation section in the Basics chapter for more information about installing the Oracle Load Testing Agent software on each system and verifying network access between the Oracle Load Testing system and each agent system.In addition, if you are using Oracle Load Testing ServerStats you must define the data collector systems and systems being monitored.
To add a new VU Agent system:
Select Options from the User menu to display the Options Manager.
Expand Systems and 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 / 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 user name for agent authentication. The Username is the user name specified for the agent Authentication Profile in the Oracle Load Testing Agent Authentication Manager. The username for the default agent Authentication Profile is JMSAdmin. To view other defined agent Authentication Profile Usernames, select Oracle Application Testing Suite from the Start menu, then select Oracle Load Testing Agent Authentication Manager from the Tools submenu. Select an agent Authentication Profile to view the details. On Linux machines, use:
<instdir>/jdk/jre/bin/java -jar <instdir>/agentmanager/AMAuthManager.jar
to start the Oracle Load Testing Agent Authentication Manager.
Password - enter the password for agent authentication. The Password is the password specified for the agent Authentication Profile in the Oracle Load Testing Agent Authentication Manager. The password for the default agent Authentication Profile is blank. To change the password for a defined agent Authentication Profile Usernames, start the Oracle Load Testing Agent Authentication Manager and select an agent Authentication Profile to view the details and enter a new password.
Test - checks to see whether the Oracle Load Testing server can contact the system and displays an informational message indicating if the system is available.
Note:
If a firewall is running on the agent system, you must make sure Port 7 is open. The controller uses Port 7 to ping the agent system to determine if the system can be accessed or not while adding the agent system using the user interface.Enter the name of the system in the Name field, enter the name or IP address of the system in the Host / IP field, and specify the operating system type.
Enter the port and authentication settings.
Click OK.
Note:
Systems and system groups appear in the Systems list on the Build Scenarios tab.To add a new system group:
Select Options from the User menu.
Exapnd Systems and select VU Agent System Groups.
Either select the group you want to change and click Edit or click New to create a new group.
Name - enter the name of the system group.
VU Agent 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.
For new groups, enter a name for the group.
Select the systems you want to add from the VU Agent 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 Options from the User menu.
Expand Systems and select VU Agent System Groups.
Either select the group you want to change and click Edit Group or click New Group to create a new group.
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 a new ServerStats Data Collector:
Select Options from the User menu to display the Options Manager.
Expand Systems and select ServerStats Data Collector.
Click New System to display the Add ServerStats Data Collector dialog box.
General - enter the system information.
Name - enter the name of the data collector.
Host / 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.
Username - enter the user name for the data collector. The Username is the user name specified for the agent Authentication Profile in the Oracle Load Testing Agent Authentication Manager. The username for the default agent Authentication Profile is JMSAdmin. To view other defined agent Authentication Profile Usernames, select Oracle Application Testing Suite from the Programs Start menu, then select Oracle Load Testing Agent Authentication Manager from the Tools submenu. Select an agent Authentication Profile to view the details. On Linux machines, use:
<instdir>/jdk/jre/bin/java -jar <instdir>/agentmanager/AMAuthManager.jar
to start the Oracle Load Testing Agent Authentication Manager.
Password - enter the password for the data collector. The Password is the password specified for the agent Authentication Profile in the Oracle Load Testing Agent Authentication Manager. The password for the default agent Authentication Profile is blank. To change the password for a defined agent Authentication Profile Usernames, start the Oracle Load Testing Agent Authentication Manager and select an agent Authentication Profile to view the details and enter a new password.
Enter the name of the system in the Name field, and enter the name or IP address of the system in the Host / IP field.
Click OK.
Note:
Systems and system groups appear in the Agent Systems list on the Composer tab.Monitored systems are those systems that will be monitored using ServerStats. In addition to defining the system, you can have Oracle Load Testing 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 monitoring in the Monitoring section of the Composer tab.
You can use the Add Target option in the Monitoring section of the Composer tab to quickly define a Monitored System with a set of metrics in a configuration. You can also use the Systems Manager in the User Options to define Monitored Systems.
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:
Copy configuration jar files to the data collector machines
Copy configuration jar files to the data collector machines
Update the properties file
WebSphere 6.1, 7.0
Copy configuration jar files to the data collector machines
Copy keystore/trust store files
The following are the default values for the monitored system:
Port: 8880 (default)
Username: admin (check with the JMX system administrator for changes to the username)
Password: password (check with the JMX system administrator for changes to the password)
Trust Store File: C:\keys\DummyClientTrustFile.jks
Trust Store Password: WebAS
Key Store File: C:\keys\DummyClientKeyFile.jks
Key Store Password: WebAS
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 one or more specific configuration jar files to be copied from the JMX server installation to the <installdir>\DataCollector\classes directory on all machines that will be used as data collectors for sampling from that server. The default <installdir> is C:\OracleATS. The file(s) can be obtained from your application server installation and copied to the appropriate directory as listed in the following table.
Note:
Versions prior to 9.20 included the version number in the directory names for the Jar files. If you are upgrading from a previous version of Oracle Application Testing Suite and have JMX monitors configured, you will need to move the Jar files to the directories specified below. If the Jar files are in the previous version locations, you may receive an error message similar to the following message:Error loading websphereXX JMX classes--check classpath setting in data collectors OSDC.properties.| Application Name | Files to Copy | Default Directory |
|---|---|---|
| Redhat JBoss 4.x | jbossall-client.jar | <installdir>\DataCollector\classes\jboss |
| Redhat JBoss 5.x | all *.jar files under <JBoss5 install dir>/jboss-as/client/ | <installdir>\DataCollector\classes\jboss |
| Redhat JBoss 6.x | all *.jar files under <JBoss6 install dir>/client/ | <installdir>\DataCollector\classes\jboss
Execute C:\<JBoss6 install dir>\bin\run.bat -b hostname.com, to start the JBoss server (hostname.com is the FQDN of your machine). Note the -b argument above. JBoss server does not know which hostname to bind (i.e localhost or hostname or hostname.domain) so it must be specified as described above. |
| Oracle WebLogic 9.0 | weblogic.jar, webservices.jar | <installdir>\DataCollector\classes\weblogic |
| Oracle WebLogic 9.1 | weblogic.jar, webservices.jar | <installdir>\DataCollector\classes\weblogic |
| Oracle WebLogic 10.x | wlfullclient.jar (This file must be created using the WebLogic JarBuilder tool. On the WebLogic sever, switch to server/lib and use the command java -jar wljarbuilder.jar to create wlfullclient.jar in the server/lib directory, then copy the file.) |
<installdir>\DataCollector\classes\weblogic |
| 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-impl.jar, mail.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 | <installdir>\DataCollector\classes\weblsphere |
| IBM WebSphere 6.1, 7.0 | Both versions java\jre\lib\*.jar java\jre\lib\ext\*.jar
WebSphere 6.1 runtimes\com.ibm.ws.admin.client_6.1.0.jar plugins\com.ibm.ws.security.crypto_6.1.0.jar WebSphere 7.0 runtimes\com.ibm.ws.admin.client_7.0.0.jar plugins\com.ibm.ws.security.crypto.jar Trust Files DummyClientKeyFile.jks DummyClientTrustFile.jks |
<installdir>\DataCollector\classes\weblsphere |
To add a new monitored system with a ServerStats configuration in the Monitoring section of the Composer tab:
Open the Composer tab.
Click the Monitoring step.
Select Add Target.
Select the system type or Generic Target.
Specify the system information.
If you want to use the default ServerStats metric profile for the system type, select the Apply [type] metric profile automatically option.
Click OK.
Use the Add Counters menu to add additional counters to the configuration.
Click Test to verify the metrics can access the target monitored system and retrieve metric data.
Optionally, save the configuration.
To add a new monitored system using the Systems Manager:
Select Options from the User menu to display the Options Manager.
Expand Systems and select Monitored System.
Click New System to display the New Monitored Target 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.
General
Name - enter the name of the monitored system.
Host / IP - enter the host name or IP address of the monitored 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.
Oracle Load Testing 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 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.
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 server and you are using a remotely installed SQL database for Oracle Load Testing, you need to install the SQL Server ODBC driver on the Oracle Load Testing 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 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 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 builds this string for all driver types except a Custom driver type. For a Custom driver setting, type in the Connect String.
Database Name - For the Oracle Thin JDBC driver, provide the database or server ID.
Port - Oracle Load Testing 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.
Instance - Specify the SQL server named instance that you want to use. If nothing is specified, Oracle Load Testing uses the default instance as set up on your server. Refer to your database administrator for details.
Database Name or Database SID - 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
Server Type - select 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.
Oracle WebLogic
IBM WebSphere
Redhat JBoss
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.
Url
System Homepage - enter the URL of the page you want to monitor.
Connection 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 Port - Specifies the port number. The default port for Telnet is 23, and the default port for SSH is 22.
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 prompt for the host machine. If you do not specify a prompt, Oracle Load Testing 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.
Enter the name of the system in the Name field, and enter the name or IP address of the system in the Host / IP field.
Enter data source information for the type of system you are adding.
Click OK.
Note:
Systems, system groups, and cloud service configurations appear in the Agent Systems list in the Profiles pane of the Composer tab.To rename a system:
Select Options from the User menu.
Expand Systems and 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.
To edit a system:
Select Options from the User menu.
Expand Systems and select the system you want to edit.
Click Edit to display the Edit System dialog box for that type of system.
Make any changes.
Click OK.
To delete a system:
Select Options from the User menu.
Expand Systems and 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.
The Hardware Estimation tools provide ways for you to get an estimate of the amount of hardware that will be required to run an Oracle Load Test session for a given scenario.
The quick estimate is a simple, quick and quite accurate solution for estimating the hardware requirements of an OpenScript script that will be used as a Virtual User in an Oracle Load Test scenario.
The estimate process consists of the following:
Running a script in no delay mode and collecting hardware consumption data (CPU/Memory/Network) for only one VU for a short period of time.
Measuring the CPU and Memory consumption data of a VU.
Deducing hundreds or thousands of VUs running concurrently with simulated think time.
Estimating the hardware requirements of the specified number of VUs based on the deduction result.
To run a hardware estimate:
Add scripts to the Composer tab and save the scenario.
Note:
The Hardware Estimation feature does not support Block Scenario scripts.Click the Hardware Estimation toolbar button in the Profiles pane..
Click Generate Now to start a hardware estimation session for the selected scenario. A background session and local agent start and run one Virtual User for the selected scenario.
When the estimation finishes, click View Report to view the results.