1.3 - Installation and Configuration Installation and Configuration — 01 - Getting Started With AIQ. documentation. Installation and Configuration This section describes installation procedures, configuration, deployment options, and options to integrate Appvance IQ (AIQ in short) into your software development life-cycle, production monitoring, and build environment. For System Requirements, Install Guides, Evaluation Guides - Please refer to Getting Started with Appvance IQ. The following sections detail more information: Last updated: June 02, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Setting up MYSQL RDS Instance from AWS Log in to your Amazon account with valid credentials Once logged in successfully, click Services and select RDS from the list as seen in the below screenshot Now click the "Launch a DB Instance" button In the next screen, select MySQL as the engine and Click the 'Select' Button Under Production, Select MySQL as shown below and click Next Step NOTE: Please make sure the instances that you create and the database are in the same region. DB Instance Class: Select the DB instance class that allocates the computational, network, and memory capacity required by the planned workload of this DB instance Multi-AZ Deployment can be marked as 'No' Storage Type can be Provisioned IOPS (SSD) storage is suitable for I/O-intensive database workloads. Provides flexibility to provision I/O ranging from 1,000 to 30,000 IOPS Under Settings: DB Instance Identifier: Specify a name that is unique for all DB instances owned by your AWS account in the current region. DB instance identifier is case insensitive, but stored as all lower-case, as in "mydbinstance" Master Username: Specify an alphanumeric string that defines the login ID for the master user. You use the master user login to start defining all users, objects, and permissions in the databases of your DB instance. Master Username must start with a letter, as in "awsuser" Master Password: Specify a string that defines the password for the master user. Master Password must be at least eight characters long, as in "mypassword" NOTE: The Above "Master Username" and "Master Password" will be used to connect to SQL Workbench which is explained in the later section. Click Next In the next step, you can select the DB instance in any available VPC or create a new one DB Security Group: This is Important Select the security group or groups that have rules authorizing connections from all of the EC2 instances and devices that need to access the data stored in the DB instance. By default, security groups do not authorize any connections; you must specify rules for all instances and devices that will connect to the DB instance All other fields can be left to default Your DB Instance will be in 'creating' Status for about 4-5 minutes and will be in 'Available' status as seen in the below screenshot Open Workbench that is installed (if not this needs to be installed) in your local machine or on any of the EC2 machines Click Database > Connect to Database Host Name should be the End Point URL and provide valid credentials (which were created while creating the DB i.e. "Master Username" and "Master Password") Endpoint URL can be obtained from dB instance page by clicking that arrow button as seen in the below screen-shot which needs to be replaced in place of 'localhost' from the URL The user will be successfully connected to the database Creating Database and Tables: Open MySQL Workbench and connect to the local instance of MYSQL Drag and drop MySQLInitial.SQL file into the workbench and execute the query File located at "\AIQ\TestNode\webapps\AppvanceServer\WEBINF\classes\database" Now drag and drop MySQLAppvance.sql and execute File located at "\AIQ\TestNode\webapps\AppvanceServer\WEBINF\classes\database Launch Appvance IQ Navigate to the Global Options page (Should be logged in as Admin) > Go to Admin Options – Results, change the URL, and click Test Database Connection to see the "Connection Success" message To enable functions, procedures, and triggers for my Amazon RDS MySQL instance You can enable functions, procedures, and triggers when binary logging is enabled without the SUPER privilege by setting the log_bin_trust_function_creators parameter to true for the DB parameter group that you create for your MySQL instance. Note: A default DB parameter group is created if you create a DB instance without specifying a DB parameter group that you create. For more information, see Working with DB Parameter Groups. Create a DB Parameter Group (Check below on how to create a DB parameter) Modify the DB parameter group as follows:log_bin_trust_function_creators=1 Choose Save Changes Note: After you create or modify a DB parameter group, wait at least five minutes before creating your first DB instance that uses that DB parameter group In the navigation pane, choose Instances Choose the instance that you want to associate with the DB parameter group Choose Instance Actions and choose Modify Select the parameter group you want to associate with the DB instance The parameter group name is changed immediately, but the parameter group changes aren't applied until you reboot the instance without failover To create a DB parameter group Sign in to the AWS Management Console and open the Amazon RDS console at https://console.aws.amazon.com/rds/ In the navigation pane, choose Parameter groups Choose to Create a parameter group The Create parameter group window appears In the Parameter group family list, select a DB parameter group family In the Group name box, type the name of the new DB parameter group In the Description box, type a description for the new DB parameter group Choose Create Troubleshooting Error Code: 1419. You do not have the SUPER privilege and binary logging is enabled If you get the above error while running the MySQLAppvance.sql script on AWS RDS, make sure that the RDS parameter group has the value 1 (ON) for the log_bin_trust_function_creators parameter. The RDS database MUST be rebooted for parameter changes to take effect. Last updated: September 18, 2024 If you have any feedback on this topic, please contact us at documentation@appvance.ai TestNode Settings Change TestNode Port Number Appvance IQ communicates with a TestNode over port 8080 for HTTP and 8443 for HTTPS by default. Stop Appvance IQ. Navigate to \aiq_distribution\TestNode\etc Open jetty-http.xml in notepad editor or similar Search for 8080 and replace the port number with any preferred value Save the file Restart Appvance IQ Confirm the TestNode is on the new port number by browsing the new location. For example, after setting the TestNode to run on port 7070, browse http://:7070/TMServer/ws/TestNodeand see the message: TestNode. Hi there, this is an AXIS service! Perhaps there will be a form for invoking the service here. Changing TestNode Memory Settings To set the memory for an installed TestNode, change the contents of /AIQ/TestNode/startup.bat for Windows and /AIQ/TestNode/startup.sh for Unix and Mac OS X systems. These files contain the following command line: @"%Java_HOME%/bin/java" -Xmx128M -DSTOP.PORT=8079 -DSTOP.KEY=secret -jar start.jar @echo "TestNode? Started" Adjust the memory settings using the -Xmx parameter. Enabling Java Server Mode for Faster TestNode Performance The Java Virtual Machine (JVM) running the TestNode uses just-in-time compilation and other techniques to deliver the performance of your tests. You have two choices of JVM: Java Runtime Environment (JRE) and Java Development Kit (JDK.) To see which JVM you are running, open a command shell and run: java -version. The JDK offers a special -server switch. This tells the JVM to use pre-compilation and other techniques to improve your test performance. The tradeoff of -server is the test will take longer to start and use more memory. Proxy Server Configuration If you normally need a proxy service to access Web sites, instruct Appvance IQ to use the proxy with the following instructions for Appvance Designer 2.0 For Appvance Designer 2.0, configure the external proxy by editing /Appvance IQ/sahi/userdata/config/userdata.properties and setting these properties: ext.http.proxy.enable=true ext.http.proxy.host=external_proxy_server_hostname_or_ip ext.http.proxy.port=external_proxy_server_port If your proxy needs authorization, you should set these properties too: ext.http.proxy.auth.enable=true ext.http.proxy.auth.name=proxy_authorization_username ext.http.proxy.auth.password=proxy_authorization_password. Make the same changes with ext. HTTPS settings for HTTPS sites. In addition, if you need to bypass the external proxy for some local sites you need to configure that too in sahi.properties like this: ext.http.both.proxy.bypass_hosts=localhost|127.0.0.1|*.yourinternaldomain.com Note that there is only one bypass setting for both HTTP and HTTPS. For TestNode, configure the external proxy by changing the settings in the Options tab when using the Scenario Builder to configure the TestScenario. Appvance IQ/TestNode/startup.sh (or .bat)Appvance IQ/Appvance Monitor/startMonitor.sh (or .bat) Last updated: November 06, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Obsolete Flex Flash SWF Configuration Reference This page is retained only to flag that Flex, Flash, and SWF configuration is obsolete for current AIQ testing. What changed in this article Marked Flex/Flash/SWF configuration as obsolete because Flash-era browser technology is retired. Removed the impression that new AIQ environments should configure Flash or SWF support. Added migration guidance toward supported web technologies and modern browser execution paths. Validation workflow Do not configure new AIQ environments for Flash or SWF execution. Confirm whether any remaining customer workflow still depends on retired Flash technology. Document the dependency as legacy risk and plan migration to supported application technology. Review note: This page is a strong deletion/archive candidate unless a customer requires historical context. Last updated: October 2, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Installation and Configuration FAQ Use this FAQ for current AIQ installation and configuration questions that do not require a dedicated procedure page. What changed in this article Renamed the generic FAQ title so it is clear which book/context it belongs to. Reframed the FAQ as a routing and troubleshooting aid for installation/configuration topics. Added checks to avoid duplicating content that belongs in dedicated upgrade, Test Node, certificate, browser, or performance pages. Validation workflow Use this FAQ for short installation/configuration answers only when a dedicated article does not already cover the topic. Link to the canonical procedure page when the answer requires multiple steps or risk controls. Review FAQ entries periodically and promote repeated issues into standalone articles. Review note: This page now has a clear scope and should not become a dumping ground for unrelated topics. Last updated: October 2, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Best Practices to Improve AIQ Performance Best Practices to Improve AIQ Performance Use these practices to keep AIQ executions stable and results reliable. Performance tuning should consider the AIQ Controller, Test Nodes, database, browser capacity, network path, and the application under test. Execution practices Validate scenarios with a small run before scaling load. Use realistic ramp-up and ramp-down periods. Keep test data reusable, resettable, and separate from scenario logic. Avoid unnecessary fixed waits; use Scenario Editor conditional waits where possible. Environment practices Size Test Nodes for the execution type and expected browser or user count. Monitor CPU, memory, disk, network, and browser/driver health during large runs. Keep AIQ, browser, driver, and operating-system versions aligned with release guidance. Document environment changes before comparing performance results. Last updated: September 18, 2026 Installing and Configuring Desktop Designer Installing and Configuring Desktop Designer This is the installation and configuration process to setup Desktop Designer in order to test Windows applications. System Requirements Hardware Intel iCore 5 or above Memory 16 GB 1 TB Hardrive (SSD prefered) Amazon EC2 For Windows Server t3.xlarge OS and Software Windows 10 / Windows Server 2016 Windows Professional only. Window Home not supported. Windows 11 PRO is not certified at this time. Windows Server 2022 Datacenter not certified at this time. Windows Application Driver (WinAppDriver) (Version 1.2.1 or greater) Download Link Developer Mode must be set to On. Windows SDK (Optional) Download Link Install Chocolatey. Chocolatey is software management automation for Windows that wraps installers, executables, zips, and scripts into compiled packages. Installation Process Enable Developer Mode. Press WinKey+ I In Privacy and Security, Select For Developers Enable Developer Mode. Download Windows Application Driver. Follow the installation process. Download Link Open a Command Console in Administrator mode and navigate to the path where the Windows Application Driver was installed. cd C://Program Files/Windows Application Driver/ An Enviroment Variable can be set using the cmd prompt: setx APPIUM_WAD_PATH "C:/Program Files x86/Windows Application Driver" Download Video Recording Tool for Windows ( AppvanceAgent.exe) and copy to the path " C:/Program Files x86/Windows Application Driver Tool: The Windows Appvance Agent can be downloaded from the Desktop Designer Installation Downloads page. Access to this page is restricted and must be requested. Install Chocolatey. This is needed to install the ffmpeg plugin. Download Link Install Chocolatey. Full instructions can be found here: Installing Chocolatey. Run PowerShell as Administrator with the following command: Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1')) Restart PowerShell and run it as Administrator again. Run this command: choco install ffmpeg Navigate to C:/Program Files x86/Windows Application Driver in PowerShell and run the following command: AppvanceAgent.exe --port 4726 --executable WinAppDriver.exe --base_path /wd/hub --win_app_driver_port 4725 The first port is for video recording and the second is for WinAppDriver. Port 4726 would be the value videoPort in the config file. Port 4725 would be the port you use in the serverURL. The videoPort field is mandatory. See the Configuration File Example below. To access WinAppDriver Remotely there are two options: Use a bridge like NGrok: Start ngrok with: ngrok http http://localhost:4725 Copy the forwarding URL and use it in your script capabilities.Open a port on the test machine. Open up Windows Firewall with Advanced Security. Select Inbound Rules -> New Rule... Rule Type -> Port. Select TCP. Choose a specific local port (472x) Action -> Allow the connection Profile -> Select all Name -> optional, choose a name for the rule.You can also run the following command when run in an admin command prompt: netsh advfirewall firewall add rule name="WinAppDriver remote" dir=in action=allow protocol=TCP localport=4723 Run ipconfig.exe to determine your machine's local IP address. Setting * as the IP address command line option will cause it to bind to all bound IP addresses on the machine. Run AppvanceAgent.exe --port 4725 --executable WinAppDriver.exe --base_path /wd/hub --win_app_driver_port 4729 as an administrator with command line arguments as seen above specifying the local IP and port. Configuration File Example [  {    "app": "",    "appActivity": "TEST",    "appPackage": "Root",    "bundleId": "",    "validDomains": "",    "service": "On-Premises",    "configName": "Root_DesktopApp",    "deviceMode": "Desktop",    "proxyURL": "",    "videoPort": "4726",    "serverURL": "http://192.168.3.14:4725/wd/hub",    "source": "package",    "platformName": "Windows",    "capabilities": {      "deviceName": "WindowsPC",      "platformVersion": "",      "automationName": "Windows",      "app": "",      "noReset": "true"    }  }] Appium Capabilities Appium is an open source automation tool for running scripts and testing native applications, mobile-web applications and hybrid applications on Android or iOS using a webdriver. Appium has the ability to automate Windows PC Desktop apps. This driver relies on a project from Microsoft called WinAppDriver, which is an Appium-compatible WebDriver server for Windows Desktop apps (and more in the future). WinAppDriver is often abbreviated "WAD". WAD is bundled with Appium and does not need to be installed separately. https://appium.readthedocs.io/en/latest/en/drivers/windows/ Define the Application Under Test The application under test can be defined with the following: appCapabilities.SetCapability("app", "C:\Windows\System32\notepad.exe"); or appCapabilities.SetCapability("app", "Microsoft.WindowsCalculator_8wekyb3d8bbwe!App"); Both the path to the application and the application ID are valid. The application ID can be found running in PowerShell with admin permissions : Get-StartApps Platform and Device The Platform and device are required: appCapabilities.SetCapability("platformName", "platformName"); appCapabilities.SetCapability("deviceName", "WindowsPC"); Those capabilities are used to start the driver: driver = new WindowsDriver(new URL("http://127.0.0.1:4723"), appCapabilities); Enabling GUI even when RDP is Disconected GUI can be still running if an automated RDP’s disconnection file is created using a batch file. On the remote computer, do the following: Create a batch file : for /f "skip=1 tokens=3" %%s in ('query user %USERNAME%') do (   %windir%\System32\tscon.exe %%s /dest:console ) In the File properties, click Advanced and select Run as administrator. Connectivity Details If the Windows machine or Virtual Desktop Infrastructure (VDI) is in the same network than the machine running AIQ, then the local internal address can be use for connecting to the WinAppDriver. Otherwise the machine hosting Windows must have assigned a Public IP and ports for RDP 3389 and 4725, 4726, 4727 forwarding the machine where the driver is running. Last updated: October 12, 2026 If you have any feedback on this topic, please contact us at documentation@appvance.ai Roku Environment Setup This section will detail the required setup to allow recording and running Desktop Designer scripts for a Roku device on a local environment. This documentation does not include the steps related to the Roku device setup itself. It is assumed that the Roku device is already setup and working as expected. See the Roku website for information on Roku setup. System Requirements OS and Hardware Two machines running Windows 10 or newer. Windows 10 / Windows Server 2016 are supported. Windows Professional only. Window Home not supported. Windows 11 PRO is not certified at this time. Windows Server 2022 Datacenter not certified at this time. Intel iCore 5 or above Memory 16 GB 1 TB Hardrive (SSD prefered) One Roku device One HDMI Video Capture device Amazon EC2 For Windows Server t3.xlarge Architecture The way the Roku environment works is by using two different PCs / laptops connected to the same network. One of them (PC-A) is going to run AIQ and is going to be used for script recording/playback. The second one (PC-B) has a HDMI video capture device connected (with the Roku device connected to it). PC-B also runs the WindowsAppvanceServer along with the other required software applications used to display and control the Roku system. Prerequisite Setup Make sure both computers are connected to the same network before completing the setup. PC-A (AIQ) Properly setup AIQ on this machine. Refer to the AIQ Documentation for setup information for AIQ. PC-B (Roku Device) Make sure the Roku device is plugged to the HDMI capture device, and is plugged to the computer. Required Software Installations The following installations are required. Please see the individual websites for the installer downloads and installation instructions. AIQ specific configuration information for these components is provided later in this document. Windows Appvance Driver Windows Appvance Driver (WAD) works as a substitute for Windows App Driver in order to avoid well know issues reported in the WinAppDriver. Installation Instructions and Download Link: Windows Appvance Driver Setup Open Broadcaster Software OBS (Open Broadcaster Software) is free and open source software for video recording and live streaming. Download Link: https://obsproject.com/. Roku Remote Tool The Roku Remote Tool provides developers a quick and intuitive way to create reusable scripts for ad-hoc testing of their channel. Download Link: https://devtools.web.roku.com/RokuRemote/. Roku Deep Linking Tester The Roku Deep Linking Tester provides a UI for configuring, saving, import/exporting, and executing deep linking test cases. Download Link: https://devtools.web.roku.com/DeepLinkingTester/. Last updated: October 12, 2026 If you have any feedback on this topic, please contact us at documentation@appvance.ai Windows AIQ Driver Setup Windows AIQ Driver Setup Use this page when preparing a Windows machine to run AIQ browser, desktop, or device-related automation that depends on local drivers. Match driver versions to the target browser, operating system, and AIQ environment. Preparation Install drivers with an account that has the required Windows permissions. Confirm the driver version matches the browser or application version used by the test. Store drivers in a controlled path and document that path in the environment configuration. Allow the driver through endpoint protection only when approved by IT or the customer security policy. Restart related services or the machine when the driver installation requires it. Validation workflow Run a basic AIQ smoke test that starts the target browser or desktop application. Confirm the driver process starts and stops cleanly. Review output logs for path, permission, or version mismatch errors. Record the driver version and installation path for future upgrades. Last updated: October 8, 2026 Configure Open Broadcaster Software for AIQ Test Evidence Configure Open Broadcaster Software for AIQ Test Evidence Open Broadcaster Software (OBS) can be used to capture video evidence while AIQ tests run. Use it when a team needs visual proof of application behavior, playback issues, or environment-specific failures. Setup guidance Install a supported OBS version on the machine where the browser, desktop app, or device stream is visible. Create a dedicated scene for AIQ evidence capture and include only the required window, display, or device feed. Set the output path to a location with enough disk space for the planned run duration. Use a recording format that can be recovered if the session stops unexpectedly. Mask or avoid capturing credentials, customer data, and unrelated desktop content. Validation workflow Start a short recording before the AIQ run. Run a small scenario and confirm the video shows the relevant application state. Check audio, resolution, timestamps, and file size. Attach or reference the recording with the related execution evidence. Last updated: October 8, 2026 Set Up Roku Remote Control for AIQ Testing Set Up Roku Remote Control for AIQ Testing Use this guidance when AIQ tests need to control or validate a Roku-based application flow. Keep device setup consistent so remote-control actions are repeatable across test runs. Setup checklist Confirm the Roku device and test controller are on the required network and can reach each other. Verify the app build, channel, or sideloaded package before running the scenario. Use a dedicated test account and reset application state when needed. Document the remote-control commands used by the scenario and the expected screen after each action. Capture device logs or screenshots when troubleshooting navigation failures. Validation workflow Pair or configure the remote-control method for the target device. Run a short navigation smoke test. Confirm that AIQ can detect the expected screen or application response. Record any network, pairing, or device-state requirements in the test notes. Last updated: October 8, 2026 Set Up Deep Link Tester for AIQ Mobile Testing Set Up Deep Link Tester for AIQ Mobile Testing Use a deep link tester when an AIQ mobile test needs to launch an app into a specific route, screen, or state. Deep links should be validated before they are added to repeatable mobile scenarios. Prerequisites Confirm the app build installed on the device or emulator supports the target scheme, universal link, or app link. Document the exact deep link format, required parameters, and expected landing screen. Use test accounts and non-production data when validating app navigation. Reset the application state between runs when the deep link depends on login, cache, or stored preferences. Validation workflow Open the deep link manually on the target device and confirm the expected screen appears. Add the deep link launch step to the AIQ mobile flow. Run the test once with logging enabled and capture evidence. Add assertions for the landing screen so failures are detected immediately. Last updated: October 8, 2026 Arrange Applications for Reliable AIQ Desktop Testing Arrange Applications for Reliable AIQ Desktop Testing Arrange desktop applications consistently before an AIQ desktop test runs. Predictable window placement helps reduce failures caused by hidden controls, overlapping windows, or unexpected screen resolution changes. Recommended setup Use a dedicated test machine or session for desktop automation. Set the display resolution and scaling before recording or running tests. Open only the applications required by the scenario. Place the application under test in a known position and avoid overlapping windows. Disable pop-ups, notifications, and screen savers that can cover the application. Validation workflow Start from a clean desktop session. Open the required application and arrange it as expected. Run a short smoke test that validates the first interaction and a key screen state. Capture a screenshot if the arrangement is part of the support procedure. Last updated: October 8, 2026 Troubleshoot Possible AIQ Performance Issues Troubleshoot Possible AIQ Performance Issues Use this article when AIQ feels slow, executions queue unexpectedly, reports load slowly, or test nodes are not keeping up with scheduled demand. Start with environment evidence before changing configuration. Common areas to review Host resources: CPU, memory, disk I/O, and available storage on controller, database, and test-node hosts. Database health: Result-table growth, slow queries, retention settings, and backup activity. Test-node capacity: Number of concurrent executions, browser/device availability, and node connectivity. Scenario design: Excessive waits, unnecessary screenshots, large payloads, and missing cleanup steps. Network path: Latency or firewall issues between AIQ services, test nodes, databases, and target applications. Recommended workflow Capture the exact symptom, affected time range, and AIQ components involved. Review logs and resource metrics before restarting services. Run a small known-good scenario to separate platform issues from scenario-specific issues. Apply one change at a time and record the result. Last updated: October 8, 2026 Cloud Configuration Cloud Configuration Test Deployment in a Cloud onnEC2 Configuration Cloud Architecture Features and Benefits Grid Configuration Softlayer Configuration Cloud Testing Options Scriptless Test Deployment Configuration Cloud Config - FAQ Last updated: July 17, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Test Deployment in a Cloud AIQ is a distributed test environment. AIQ runs your tests on a Grid of your test equipment, in a Cloud Computing environment, or both. AIQ provides specific commands to support the automatic deployment and operation of your tests in a grid of servers and a Cloud Testing environment. For example, identify a cloud testing service like Amazon EC2 in a Test Scenario. AIQ creates the Test Nodes in EC2 instances, runs the test, retrieves the results, and takes down the EC2 instances. AIQ deploys and operates tests in a "lights out" manner for full Cloud Test automation. Appvance IQ works on-premises behind your firewall or in your favorite cloud environment, or both in hybrid mode. It supports integration with the following: Amazon Web Services IBM Softlayer OpenStack Cloud Software AIQ Grid technology works in your QA lab, in the Cloud, or both. Identify a set of TestNodes running in your QA lab to AIQ. AIQ automatically selects the available TestNodes to deploy and operate your tests. Appvance provides Test OnDemand Testing as a Service (TAAS) services to host your tests. Last updated: June 02, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai AIQ Cloud Architecture Overview AIQ Cloud Architecture Overview AIQ cloud deployments use controller, execution, storage, and integration components sized for the target workload. Exact architecture depends on the customer environment, deployment model, and AIQ release. Core areas Controller services coordinate users, projects, executions, and reporting. Execution capacity is provided by Test Nodes or equivalent worker resources. Storage and data services retain configuration, execution results, and operational test data. Networking, certificates, proxy rules, and integrations connect AIQ to the systems under test. Operational checklist Document ports, domains, certificates, and proxy requirements. Size execution capacity for the expected browser, service, mobile, or performance workload. Monitor controller, database, and Test Node health during high-volume runs. Review security, access, backup, and retention requirements with the environment owner. Last updated: September 18, 2026 Features and Benefits Cloud Computing and AIQ Grid technology provide huge new benefits to app performance solutions: Run At User Levels Never Before Possible - Building a test lab used to be prohibitively costly for medium and large-scale load tests. Cloud computing delivers bandwidth and computing power to achieve tests in the millions-of-users levels at commodity prices Run From Multiple Locations Around The World - Cloud Testing environments are a worldwide phenomenon. AIQ runs tests in multiple Cloud Testing environments. This makes it possible to manage performance from your user's geographic location Pay As You Go, Pay Only For What You Need - Cloud Testing eliminates the cost of building and maintaining a test lab for load and performance testing. No longer is there a need to provision expensive and difficult to manage quality test labs. Appvance Cloud Testing lets you pay as you operate tests. Ideal for automating test operation from a Continuous Integration environment. The CI platform starts a Test Scenario test and AIQ automatically provisions and deploys tests to the available TestNodes in your own Grid or in a Cloud Testing environment Test In Your Environment, In A Cloud Environment, Or Both - Appvance delivers ultimate flexibility Last updated: June 02, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Cloud Testing Options Appvance IQ provides several options for running tests in a Cloud Testing environment. These options are configured in a TestScenario and determine how AIQ provisions, uses, and manages TestNode instances during test execution. The Scenario Builder supports the following Cloud Testing settings. Name The Name identifies the Cloud Testing environment configuration used to manage the cloud resources. Type The Type specifies the cloud environment to use. Available options include: EC2 SoftLayer Grid OpenStack Beginning The Beginning setting determines how Appvance IQ provisions or starts TestNode instances when staging the test. Available options are: Create All — Creates new instances for all required TestNodes. None — Does not start or create any instances. Create Required — Uses available running instances and creates new instances only when additional machines are required. For example, if three machines are required and one is already running, AIQ uses the existing machine and creates the remaining two. Start All — Starts all stopped instances. This option requires all machines to be stopped. If some machines are already running while others are stopped, an error may occur. End The End setting determines what Appvance IQ does with the TestNode instances when the test finishes. Available options are: Terminate All — Terminates all instances. Started — Terminates only the instances that were started for the test. None — Does not terminate or stop any instances. Stop All — Stops all running instances. Reboot The Reboot setting determines whether AIQ reboots TestNode instances after test execution. Rebooting can help release resources when an application under test leaves network connections open or otherwise prevents resources such as memory and network connections from being released properly. Available options are: After — Reboots the node after the test. AIQ does not reboot machines that have already been terminated. Never — Does not reboot the node after the test. All Available Machines All Available Machines specifies the desired number of TestNode instances available for the test. Config Config specifies the path to the AIQ Cloud Testing configuration file. The configuration file contains the cloud access credentials, security keys, and account preferences required to access the selected Cloud Testing environment. Network Bandwidth Network Bandwidth specifies the network bandwidth, in Kbps, to use for tests running in the specified location. Username and Password Username and Password specify the credentials used to log in to the TestNode machine. These credentials should correspond to the original credentials of the machine used to create the AMI. If the default credentials were used when creating the AMI, leave these fields blank. Last updated: August 19, 2026 If you have any feedback on this topic, please contact us at documentation@appvance.ai. Configure Scriptless Test Deployment Use scriptless test deployment configuration to prepare Scenario Editor tests for execution in the intended AIQ environment. Keep deployment settings aligned with the target environment, Test Node capacity, browser support, and test data strategy. Before deployment Confirm the target environment, browser or device requirements, and Test Node availability. Validate test data and credentials using approved secure configuration methods. Review scenario waits, locators, and validations for maintainability. Run a focused validation execution before adding the test to a larger suite. Deployment notes Document environment-specific settings and avoid hard-coding them into steps. Keep reusable data in DPLs or approved data sources. Review output after the first scheduled or suite execution. Last updated: September 18, 2026 Cloud Configuration FAQ for AIQ Last reviewed: September 25, 2026 Use this FAQ to answer common AIQ cloud configuration questions without duplicating provider-specific setup steps. What changed in this article Moved the FAQ toward cloud/grid decision points instead of old one-off provider instructions. Clarified when to use cloud execution, grid execution, or local test nodes. Added checks for credentials, network reachability, browser availability, and capacity before troubleshooting a cloud run. Validation workflow Identify whether the question is about cloud provider setup, grid capacity, or node connectivity. Verify credentials, routing, firewall rules, and browser versions before changing AIQ settings. Use a small validation run before scaling to a full cloud execution. Review note: Connected this FAQ to the newer cloud/grid configuration articles and treated old provider-specific details as legacy. Last updated: September 25, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Load Runner Legacy LoadRunner Integration Overview Last reviewed: September 29, 2026 Use this overview only when an AIQ environment still needs to reference LoadRunner integration concepts or migration details. What changed in this article Marked the broad Load Runner page as legacy overview content. Connected the overview to the separate LoadRunner script creation, download, admin, and execution pages instead of duplicating steps. Added decision guidance for when to keep LoadRunner support versus migrate to AIQ-native or JMeter-based workflows. Validation workflow Confirm why LoadRunner is still required for the environment. Identify whether the work involves script creation, software download, admin configuration, or execution. Route the user to the specific LoadRunner page and document any migration plan. Review note: This page now acts as an overview/router instead of a generic placeholder. Last updated: September 29, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Legacy LoadRunner Download Reference Last reviewed: September 29, 2026 This page is retained as a legacy reference for locating and preparing LoadRunner software in environments that still depend on it. What changed in this article Marked the download instructions as legacy because LoadRunner availability, licensing, and vendor download paths can change. Added checks for license ownership, version compatibility, installer source, checksum/security review, and supported operating system. Added a warning not to download installers from unapproved third-party locations. Validation workflow Confirm the approved LoadRunner version and license with the customer or tool owner. Use the vendor-approved download path and validate the installer before use. Record version and install location before configuring AIQ integration. Review note: This page now avoids hard-coding stale vendor download guidance. Last updated: September 29, 2026 If you have feedback on this topic, contact documentation@appvance.ai. LoadRunner Installation This installation has to be done on all Test nodes (Load Generators) which will be used to run scenarios from Appvance IQ. See LoadRunner for information on downloading LoadRunner. Here is an example installation of LoadRunner. This is not meant to replace the instructions in the appropriate LoadRunner Installation Guide. See the LoadRunner Professional Help Center for more the appropriate installation guide. Launch the installer file that you downloaded. For example, Micro_Focus_LoadRunner_2023_Community_Edition.exe. Select the temp folder for the installer. Click Next. The installation files are extracted to the temp folder. The required prerequisite installations are identified. Click Ok to begin these installations. Once the prerequisite installations complete, the LoadRunner Setup Wizard displays. Select LoadRunner. Click Next. Accept the license agreement. Confirm or change the installation location. Click Install. Installation progress is displayed. If you have a certificate, browse to it. Otherwise, deselect the "Specify a certificate" option. Click Next. The installation completes. Click Finish. Post Installation Verifications Here are the ways you can confirm the location and status of LoadRunner. These checks should be the first step of any LoadRunner troubleshooting. LoadRunner Install Location The LoadRunner admin page displays the installation location of LoadRunner. LoadRunner is a testing tool used to test applications, measuring system behavior and performance under load. From AIQ navigate to Global Options > Admin Options > Load Runner. LoadRunner Status If needed, you can verify the status of LoadRunner. From AIQ navigate to Global Options > AIQ Status > Load Runner. Next Steps: Creating a LoadRunner Script Running LoadRunner Scripts Last updated: June 17, 2024 If you have any feedback on this topic, please contact us at documentation@appvance.ai Legacy LoadRunner Script Creation Reference Last reviewed: September 29, 2026 This page is retained as a legacy reference for teams that still need to create LoadRunner scripts for AIQ-related workflows. What changed in this article Marked LoadRunner script creation as legacy/environment-specific content rather than current default AIQ guidance. Added checks for protocol choice, correlation needs, parameterization, runtime settings, and data files before AIQ execution. Separated script creation from download/admin/runtime configuration, which are covered by the other LoadRunner pages. Validation workflow Confirm the customer still requires LoadRunner scripts before creating new assets. Create or update the script with required protocol, parameters, correlations, and test data. Run a small validation before connecting the script to AIQ execution. Review note: Use this page only for legacy LoadRunner support or migration work. Last updated: September 29, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Run Legacy LoadRunner Scripts in AIQ Last reviewed: September 29, 2026 Use this article when an existing LoadRunner script must be executed through AIQ for a supported legacy workflow. What changed in this article Marked LoadRunner execution as legacy/environment-specific and separated it from script creation/download/admin setup. Added checks for script path, runtime settings, data files, controller/node access, licenses, and result collection. Added a validation step to run a small script before scheduling larger runs. Validation workflow Confirm the LoadRunner script and dependencies are available to the AIQ execution environment. Validate runtime settings, data files, and any required licenses before execution. Run a small execution and verify output/results before scaling or reporting. Review note: This article now focuses on safe execution of existing LoadRunner assets. Last updated: September 29, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Evaluation Guides AIQ Evaluation Guides Recommended guidance Evaluation guides should help users prove AIQ value through a focused, realistic, and repeatable workflow. Keep evaluation content current, scoped, and aligned with modern AIQ terminology such as Scenario Editor, Service Suite, AISG, and Test Nodes. Evaluation planning Define business goals, success criteria, timeline, and stakeholders. Select representative web, mobile, API, performance, or data-driven scenarios. Prepare test data, accounts, applications, environments, and access ahead of time. Capture evidence through reports, logs, screenshots, and repeatable results. Quality checks Avoid broad demos that do not map to customer outcomes. Use current product names and remove obsolete Designer or Blueprint wording when not historical. Document assumptions, limitations, and follow-up actions. Keep customer-specific evaluation notes out of public documentation. Last updated: October 6, 2026 Working with Test Designer Appvance Designer is a powerful code-free scripting environment that is included in Appvance IQ. In this lesson, you will learn how to use Test Designer Scripts (DS3) to load test a web application. Pre-Requisite This guide assumes you successfully completed Recording a Appvance Designer Script from Designer 3.0 or have a working Designer script. About Appvance Designer Scripts Designer scripts are captured using Appvance Test Designer, and easy and straightforward to modify, modularize and data-drive. Designer Exercise 1 Go to your Appvance IQ URL and login Select Build and click Scenario Editor Select File and click New A new scenario appears with the Info tab selected, displaying the Scenario Test Type options. You will configure the scenario by selecting multiple tabs along the left, and supplying the requested information. Click Please select a Test Type and select Functional Test Select the Test Management tab For this example, we will only run the functional test case one time. Use this section in the future to indicate how many times to repeat each test case, as well as how many concurrent users you wish to allow. Select the Test Cases tab The Test Case tab allows you to define test cases to run for each iteration. If we had indicated to repeat the scenario more than once, an equivalent number of iterations would exist. Click Add a Test Case Execution Test Cases are a collection of one or more scripts, executed sequentially in the order you define. Any of the supported Script Types can be used together in a single Test Case. Scripts can also use, or share data (DPL) and browser sessions (Instances). Continue following our evaluation guides to learn more. Enter a name in the Test Case Name box Enter a name in the Script Name box Many times, test cases are a collection of scripts, where the test case name is different than a single script's name. We'll use only one script in this example, making the name potentially appear redundant. Click the Script Type box and select Appvance Test Designer Script 3.0 In the Resource box, click Browse The Open window displays access to the Appvance IQ Server file system as well as any source control repositories configured in your user's Global Settings. Select your Designer script containing the *.ds file extension and click Open Click the Browser box and select the browser the scenario should use to run the script Click Save Select File and click Save The Save window display the same access to the Appvance IQ Server file system as well as your connected source control repositories. Select a location to save the scenario, enter a name in the File Name box and click Save Your scenario is ready to run. Remember, your scenario runs on the indicated test node, which for evaluations is most commonly the same location as the Appvance UTP Controller. You will not visually witness the test execute, as it is executing on the test node, with a physical browser. You can however monitor results live and post execution. Click Play Scenario The scenario displays the live execution results Once the execution completes, click Output and select Click here You can return to past executions by going to Analyze and selecting any prior execution Similarly, you can click Play, and open a currently running execution, run or edit the scenario Designer Exercise2 Open Appvance IQ and login. Click Build. Select File > Open Navigate to the Designer_example/Spree directory in the training examples. Select spree_performance.scenario, and click Open.The Scenario Test Type is Performance Test Select Test Management. Repeat scenario's test case is set to 1 Here you'll notice the Test Case is set to run with 2 users and 1 execution. This means two browser windows will open as separate users. Click the pencil icon to edit the Test Case.The Script Type is set to Appvance Designer Script, and the test case Resource points to the spree_test.ds file located in the Designer_example/Spree directory. Additionally, here we have a Data Production Library (DPL) called 'Users' which is a CSV file containing a list of users the test will use to login to the Spree site. Click 'Cancel' Select 'Resources 'All resources related to the Scenario are summarized, including the test case and CSV called Testusers.csv for data driving at the bottom. This is the file containing the aforementioned users. Click Play Scenario to execute the scenario. The Scenario loads in new browser windows (two this time as two users) and executes the interactions recorded in the designer script. Execution completion is indicated with Execution Done at the top. Click Output, then Click Here at the bottom to see the reports generated. Last updated: June 02, 2023 If you have any feedback on this topic, please contact us at documentation@appvance.ai Work with TestNG Scripts in AIQ Last reviewed: September 29, 2026 Use this article when a TestNG script needs to be prepared, packaged, and executed from AIQ. What changed in this article Moved the page from generic installation wording into a TestNG execution workflow. Added concrete checks for dependencies, testng.xml, classpath, JAR packaging, parameters, and browser/node compatibility. Clarified that TestNG scripts should be validated locally before being scheduled in AIQ. Validation workflow Build the TestNG project and confirm testng.xml points to the intended classes and parameters. Package dependencies so the AIQ execution node can resolve them. Run a small AIQ execution and compare failures with the local TestNG output. Review note: Focused the article on execution readiness, not just “working with scripts.” Last updated: September 29, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Running SoapUI Scripts as a Functional Test SoapUI support was removed in release 5.2.0 of AIQ. Appvance IQ is a platform that supports to run SoapUI scripts. Here are the steps that we need to follow to run the SoapUI scripts from Appvance IQ. From the Appvance IQ Home screen and click Build a Scenario or open the Scenario Editor from the navigation tree. Click File > New to create a new scenario. Select Functional Test from the Scenario Test Type dropdown. Click the Test Management tab and check: "Repeat scenario's test cases 1 time". Click Test Cases tab and click the link for Add test case execution. Enter Test case name and Script name. Select SoapUI from Script Type dropdown. Click Browse and browse the Soap UI file and then the Test Suite and then the Test Case. Save the test case. Click Locations tab. Enter Name: localhost and URL: http://localhost:8080/TMServer/ws/TestNode Navigate to Resources and make sure SoapUI bundle with version 5.2.1 added by default. Also make sure the resources are added with Name, Type and the correct path of the xml file. Navigate to Options and make sure that Enable logging, Safe logs on Failure are selected. Click check box Custom Database Credentials (Database Logging) and make the following settings: Database Type: MySQL Driver: com.mysql.jdbc.Driver URL: jdbc:mysql://localhost:3306/utp?useSSL=false Default Schema: utp Username: utp Password: utp Click File->Save to save new scenario. Click Play Scenario from the top navigation bar. Controller window will open in a new tab which displays the tests running and will display the pass/fail status of the tests upon the test completion. Left part shows the steps and the duration in milliseconds and right side shows the test run status under Output tab. On the Transactions tab we can find the request/response and an error tab to drill down further. Click Click here link to get to the list of Reports that Appvance IQ supports. Last updated: July 25, 2024 If you have any feedback on this topic, please contact us at documentation@appvance.ai Running SoapUI scripts as a Performance test Appvance IQ is a platform that supports to run SoapUI scripts. Here are the steps that we need to follow to run the SoapUI scripts from Appvance IQ. SoapUI support was removed in release 5.2.0 of AIQ. SoapUI Performance test Navigate to Appvance IQ Home screen and click Build. Click File >New to create a new scenario. Select Performance Test from the Scenario Test Type dropdown. Click Test Management tab. Enter Iteration name, select Total Execution from Completion Type dropdown and enter Total Execution : 100. Click Test Cases tab and click the link for Add test case execution. Enter Test case name and Script name. Select "Service Suite-SoapUI" from Script Type dropdown. 9. Click Browse and browse the Soap UI file and then the Test Suite and then the Test Case. Save the test case. 10. Browse the SoapUI script the xml file and save the test case. 11. Enter 100 in User box. Click Set (Run Time): 12. Ramp up 10 users every 10 second Maximum ramp up time 100 second and save Run Time option. 13. Click Locations tab. 14. Enter Name: localhost and URL:http://localhost:8080/TMServer/ws/TestNode (Should be added by default). 15. Navigate to Resources and make sure SoapUI bundle with version 5.12 added by default. 16. Also make sure the resources are added with Name, Type and the correct path of the jmx file. 17. Navigate to Options and make sure that Enable logging, Save logs on Failure are selected. 18. Click check box Custom Database Credentials (Database Logging) and make the following settings: Database Type: MySQL Driver: com.mysql.jdbc.Driver URL: jdbc:mysql://localhost:3306/utp?useSSL=false Default Schema: utp Username: utp Password: utp 19. Click File >Save to save new scenario. 20. Click Play Scenario from the top navigation bar. 21. Controller window will open in a new tab which displays the tests running and will display the pass / fail status of the tests upon the test completion. 22. Left part shows the steps and the duration in milliseconds and right side shows the test run status under Output tab. 23. On The transactions tab we can find the request / response and an error tab to drill down further. 24. Click Click here link to get to the list of reports that Appvance IQ supports. Last updated: July 25, 2024 If you have any feedback on this topic, please contact us at documentation@appvance.ai Run JMeter Scripts as Functional Tests in AIQ Last reviewed: September 25, 2026 Use this article when a JMeter script is being executed in AIQ for functional validation rather than load generation. What changed in this article Clarified that functional JMeter runs should validate behavior, assertions, and transaction success, not virtual-user scalability. Added guidance to keep datasets small and expected results explicit. Separated functional execution from performance execution so teams do not interpret functional results as load-test evidence. Validation workflow Import or select the JMeter script and confirm assertions are present. Run with a controlled user count and data set appropriate for functional validation. Review output, assertions, and results before promoting the script to performance testing. Review note: Reduced ambiguity between functional JMeter execution and performance JMeter execution. Last updated: September 25, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Run JMeter Scripts as Performance Tests in AIQ Last reviewed: September 25, 2026 Use this article when a JMeter script is executed in AIQ to generate load and measure performance behavior. What changed in this article Clarified that performance runs require workload model, ramp-up, duration, and result interpretation. Added reminders to validate test data, target environment capacity, and monitoring before load generation. Separated performance-test guidance from the functional JMeter article so reports are interpreted correctly. Validation workflow Confirm the workload model, virtual-user target, ramp-up, duration, and data requirements. Run a small shakeout before the full performance test. Review throughput, response times, errors, and infrastructure monitoring after execution. Review note: Focused this page on load/performance concerns instead of generic JMeter playback. Last updated: September 25, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Work with HAR Scripts in AIQ Last reviewed: September 29, 2026 Use this article when HAR network captures are converted, replayed, or validated as part of AIQ testing. What changed in this article Clarified that HAR scripts are network-capture artifacts and not a substitute for functional assertions. Added checks for request ordering, dynamic tokens, cookies, headers, payload masking, and environment-specific URLs. Connected HAR usage to validation/storage workflows and security review before sharing. Validation workflow Review the HAR for sensitive headers, cookies, tokens, and customer data before reuse. Validate that dynamic values are parameterized or regenerated during playback. Run the HAR-based flow and compare network responses with the expected application behavior. Review note: The page now treats HAR as a network-evidence artifact with security and dynamic-data constraints. Last updated: September 29, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Record a Scenario Editor Test Record a Scenario Editor Test This article replaces legacy Designer 3.0 wording with current Scenario Editor terminology. Use recording as a starting point, then review and maintain the scenario before adding it to a suite. Recommended workflow Prepare approved test data and a clean application state. Record the shortest flow that proves the target behavior. Review generated steps and replace fragile locators or fixed waits. Add validations and stored values where they prove business behavior. Run a small validation execution and review output before scaling. Maintenance notes Do not keep obsolete Designer-only instructions in current AIQ documentation. Prefer clear scenario names and reusable data mappings. Use conditional waits instead of arbitrary pauses where possible. Last updated: September 18, 2026 Legacy Functional Scenario Creation Reference Last reviewed: October 2, 2026 This page is retained as a legacy reference for older Appvance Designer Script 3.0 functional scenario workflows. What changed in this article Marked Designer Script 3.0 functional-scenario creation as legacy content. Added migration framing toward Scenario Editor for current functional scenario creation. Added checks for locators, waits, test data, browser support, and validation evidence before reusing legacy assets. Validation workflow Confirm whether the functional test can be rebuilt or maintained in Scenario Editor. If the legacy workflow is still required, document the exact AIQ version and browser/runtime assumptions. Replay the scenario and update locators, waits, and validations before considering it maintained. Review note: This page should not be treated as the current functional-scenario creation path. Last updated: October 2, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Legacy Performance Scenario Creation Reference Last reviewed: October 2, 2026 This page is retained as a legacy reference for older Appvance Designer Script 3.0 performance scenario workflows. What changed in this article Marked Designer Script 3.0 performance-scenario creation as legacy content. Added guidance to verify load model, test data, pacing, browser/runtime assumptions, and current AIQ execution support. Connected legacy scenario review to current performance-test readiness rather than blindly following old steps. Validation workflow Confirm the performance scenario still represents the current business workflow and load model. Validate data, pacing, correlations, and execution-node capacity before running at scale. Prefer current AIQ scenario creation paths for new performance work. Review note: This page now signals legacy status and focuses on safe reuse only. Last updated: October 2, 2026 If you have feedback on this topic, contact documentation@appvance.ai. Legacy App Pen Scenario Creation Reference Last reviewed: October 2, 2026 This page is retained as a legacy reference for older Appvance Designer Script 3.0 App Pen scenario workflows. What changed in this article Corrected the title grammar and marked Appvance Designer Script 3.0 content as legacy. Replaced current-action wording with guidance to use Scenario Editor for new work where possible. Added checks for customer dependency, migration path, scenario ownership, and whether screenshots/data still match the old workflow. Validation workflow Confirm the workflow still depends on Appvance Designer Script 3.0 before following this page. Prefer Scenario Editor for new scenario creation and document any blocker that requires legacy App Pen steps. Validate the resulting scenario in the current AIQ environment before reusing it. Review note: This page is a legacy bridge, not recommended setup guidance for new scenarios. Last updated: October 2, 2026 If you have feedback on this topic, contact documentation@appvance.ai.