AppLoader 7.7 Load Testing On Windows Azure
CONTENTS INTRODUCTION... 3 PURPOSE... 3 CREATE A WINDOWS AZURE ACCOUNT... 3 CREATE A LOAD TESTING ENVIRONMENT ON THE CLOUD... 6 CONFIGURE A WINDOWS AZURE STORAGE ACCOUNT... 6 CREATE A VIRTUAL NETWORK... 8 CONFIGURE A WINDOWS AZURE VIRTUAL MACHINE FOR THE APPLOADER... 11 CONNNECT TO THE VIRTUAL MACHINE USING REMOTE DESKTOP... 15 CONFIGURE A SECOND VIRTUAL MACHINE FOR THE INJECTOR & SCENARIOBUILDER... 16 VALIDATING CONNECTIVITY WITH PING... 20 INSTALLING APPLOADER SUITE ON WINDOWS AZURE... 22 PREREQUISITES... 22 INSTALL APPLOADER CONTROLLER... 23 INSTALL INJECTOR... 24 INSTALL SCENARIOBUILDER... 27 INSTALL MICROSOFT.NET FRAMEWORK 3.5... 29 GETTING STARTED WITH APPLOADER... 33 CREATE AND EXECUTE A LOAD TEST... 33 MAKING IDENTICAL VMS USING A RE-USABLE IMAGE... 46 INDEX - TROUBLESHOOTING... 51 VIRTUAL MACHINES ARE GREYED OUT... 51 APPLOADER SERVICES... 51 VSTATION... 52 LOGS... 52 LICENSE... 53 2014 NRG Global, Inc. All rights reserved. Page 2
INTRODUCTION Azure is an open and flexible cloud platform that enables you to quickly build, deploy and manage applications across a global network of Microsoft-managed datacenters. You can build applications using any language, tool or framework. And you can integrate your public cloud applications with your existing IT environment. You can use the Virtual Machines as a testing environment on their cloud networks to configure AppLoader. PURPOSE We are convinced that AppLoader will work in your environment and we are here to convince you! This guide will explain how to create a new Windows Azure Storage Account and Virtual Machine using the Windows Azure portal. After the machine is provisioned, you will connect to the virtual machine using Remote Desktop Protocol (RDP). Once connected, you will be able to perform tasks on the virtual machine just as you would for an on premise machine. You will learn how to build a test scenario, send it to the controller, and set up a load test with 5, 10, 20,50 or as many rusers as you want. Also you will be able to run multiple Load Tests with multiple Injectors by cloning the Injector. CREATE A WINDOWS AZURE ACCOUNT Below is a step-by-step guide to create a Virtual Machine with Windows Azure. Please follow the steps below to configure a free trial account with Azure. Click on the link below to setup an account. https://azure.microsoft.com Next, click on Try for free. Then click on Try it Now. If you have an account, sign in to your Microsoft account, otherwise click on Don t have a Microsoft account? Sign up now link to create an account. (Be sure the account that is being created is 18 years or older). 2014 NRG Global, Inc. All rights reserved. Page 3
After creating an account or sign in to your Microsoft account, fill out the following form to sign up for Windows Azure account. You can choose the Free Trial subscription to have a full access to all services for 30 days. Next, login to your account s portal to start using the Window Azure s services. 2014 NRG Global, Inc. All rights reserved. Page 4
Once you log in to your portal, you will be able to use all the Azure's services easily. 2014 NRG Global, Inc. All rights reserved. Page 5
CREATE A LOAD TESTING ENVIRONMENT ON THE CLOUD CONFIGURE A WINDOWS AZURE STORAGE ACCOUNT In this part you will create a new Windows Azure Storage Account in the region closest to you. The underlying storage for virtual machines (VHD files) are saved in Windows Azure Storage. OS and Data Disks are stored in Windows Azure Storage Account, except for D:\ drive which is only temporary. 1. Click on the +NEW link at the bottom-left corner of the screen. 2. Select DATA SERVICE -> STORAGE ->QUICK CREATE. 3. Specify the storage account properties. a. A unique name for the storage account URL b. The Windows Azure Location to create the storage account in. c. Change REPLICATION to Locally Redundant. The Replication field refers to the location of a copy of the storage account. Selecting Geo-Redundant means that a copy of the Storage Account will be created in a different location (i.e. if storage account is created in West US, copy could be made in East US region). Selecting Locally Redudant means that a copy of the Storage Account will be created in the same region). 2014 NRG Global, Inc. All rights reserved. Page 6
4. Press the checkmark next to CREATE STORAGE ACCOUNT to provision the storage account. 5. Before proceeding wait for the storage account creation to complete. Once the storage account is finished being created, virtual machines can use this storage account to save data. 2014 NRG Global, Inc. All rights reserved. Page 7
CREATE A VIRTUAL NETWORK Load Testing On Windows Azure : AppLoader 7.7 A cloud only virtual network with a DNS server specified. Creating a virtual network will provide more control over the IP address assigned to each virtual machine. 1. Click on the +NEW link at the bottom-left corner of the screen 2. Click on NETWORK SERVICES -> VIRTUAL NETWORK -> CUSTOM CREATE. 3. Set the Virtual Network Properties. 2014 NRG Global, Inc. All rights reserved. Page 8
4. On the DNS Servers and VPN connectivity page, add a new DNS Server and specify the IP Address. 5. On the Virtual Network Address Spaces page, modify the default subnet and add additional subnets. 2014 NRG Global, Inc. All rights reserved. Page 9
Once the network account is finished being created, you can see it on the Networks section. 2014 NRG Global, Inc. All rights reserved. Page 10
CONFIGURE A WINDOWS AZURE VIRTUAL MACHINE FOR THE APPLOADER This first VM will host the AppLoader Controller. 1. Click +NEW link on the bottom left corner of the Portal 2. Select COMPUTE -> VIRTUAL MACHINE -> FROM GALLERY. 3. Select an image for the Virtual Machine, for the purpose of this guide, Windows Server 2008 R2 SP1 was selected. Then click the right arrow at the bottom of the dialog to move forward. Virtual Machines can be cloned by copying their images then accessing them under My Images. 2014 NRG Global, Inc. All rights reserved. Page 11
4. Provide basic properties for the virtual machine. a. Specify nrgvmapploader as the VIRTUAL MACHINE NAME b. Provide a USER NAME and PASSWORD. This will be the credentials you will use to login into the machine. c. Click the right arrow at the bottom of the dialog to move forward link. A machine can be set up with only one core. Later when the machine is ready to be used for testing more cores can be added to the machine. 5. Specify the final configuration properties of the virtual machine. a. Specify a unique CLOUD SERVICE DNS NAME to act as the container for the virtual machine. b. Select the REGION where you previously created the storage account. c. Select the nrgstorage as STORAGE ACCOUNT that was created at the beginning of this guide. This storage account will be the location where the VHDs (disks) for this virtual machine are stored. d. Configure the Endpoints for the Virtual Machine. By default Windows based virtual machines have ports enabled for Remote Desktop and Remote PowerShell. Virtual Machines can be created under an existing Cloud Service by selecting it from the drop down. Selecting an existing Cloud Service will auto populate the Cloud Service DNS Name. Creating VMs within the same cloud service will allow them to find and communicate with one another. 2014 NRG Global, Inc. All rights reserved. Page 12
6. Review the Virtual machine configuration and press the check mark button at the bottom of this dialog and Windows Azure will start provisioning the Virtual Machine. On the bottom right you will notice your machine is being created. 2014 NRG Global, Inc. All rights reserved. Page 13
After your Server is created, select your Virtual Machines from the items pane on Windows Azure. Click on the VM from the list, then open the Dashboard to view the status and set up of the VM. 2014 NRG Global, Inc. All rights reserved. Page 14
CONNNECT TO THE VIRTUAL MACHINE USING REMOTE DESKTOP Once the machine has been provisioned, you will see the CONNECT link light up for the virtual machine. Click on CONNECT. 1. When prompted to open or save the Remote Desktop File (RDP), click on Open. 2. Next you will be challenged to enter the credentials to login to the virtual machine. In the Windows Security dialog, click on the Use Other Account option and enter the credentials you specified when setting the properties for the virtual machine. 3. You will be asked to confirm the connection. This is because the certificate used to secure the connection is not signed by a trusted certificate authority on your computer. Click on Yes to connect. 2014 NRG Global, Inc. All rights reserved. Page 15
CONFIGURE A SECOND VIRTUAL MACHINE FOR THE INJECTOR & SCENARIOBUILDER After the first machine has been created successfully, a second VM will need to be created under the same cloud service. This second VM will host the Injector and ScenarioBuilder. 1. Click +NEW link on the bottom left corner of the screen. 2. Select COMPUTE -> VIRTUAL MACHINE -> FROM GALLERY. 3. Select an Image for the Virtual Machine, for the purpose of this document Windows Server 2008 R2 SP1 was selected. 2014 NRG Global, Inc. All rights reserved. Page 16
4. Provide basic properties for the virtual machine. a. Specify nrgvminjector as the VIRTUAL MACHINE NAME. b. Provide a USER NAME and PASSWORD. This will be the credentials you will use to login into the machine. c. Click the right arrow at the bottom of the dialog to move forward link. 5. Specify the provisioning configuration settings of the virtual machine. a. Using the drop down select the cloud service that was created for AppLoader Controller machine. b. Select the previously created storage account as well. c. Configure the Endpoints for the Virtual Machine. By default Windows based virtual machines have ports enabled for Remote Desktop and Remote PowerShell. 2014 NRG Global, Inc. All rights reserved. Page 17
6. Review the Virtual machine configuration and press the check mark button at the bottom of this dialog and Windows Azure will start provisioning the Virtual Machine. 7. Wait for nrgvminjector to move into the Running (Provisioning) state before proceeding. 2014 NRG Global, Inc. All rights reserved. Page 18
After the VM is finished provisioning, you will notice that DNS name for the two machines is the same. Connect to the second virtual machine using Remote Desktop Connection. For more information please refer here. 2014 NRG Global, Inc. All rights reserved. Page 19
VALIDATING CONNECTIVITY WITH PING Load Testing On Windows Azure : AppLoader 7.7 After both VMs have been created, communication must be established between them. To do this a Rule must be added to both of the machines. 1. Connect to nrgvmapploader using a Remote Desktop Session. 2. Once the machine has started, open a command prompt by pressing <Windows Key + R>, type CMD and press <Enter>. 3. Enter ping nrgvminjector and press <Enter>. 4. You should see that nrgvminjector has resolved to an IP address but you should receive timeouts in response to your ping request. This is because ICMP has not been enabled on either virtual machine's firewall. 5. Enter the following command on nrgvmapploader followed by <Enter> to enable this virtual machine to respond to ICMP (Ping) requests. netsh advfirewall firewall set rule name="file and Printer Sharing (Echo Request - ICMPv4-In)" new enable=yes A message should appear showing that the rule has been updated as seen above. 2014 NRG Global, Inc. All rights reserved. Page 20
6. Connect to nrgvminjector using Remote Desktop using the same steps as you used to connect to nrgvmapploader. Start a command prompt and enable ICMP using the same command as in the previous step. netsh advfirewall firewall set rule name="file and Printer Sharing (Echo Request - ICMPv4-In)" new enable=yes 7. Validate the firewall rules by pinging nrgvmapploader from nrgvminjector and nrgvminjector from nrgvmapploader. This will ensure that the firewall rule was updated. Pinging second VM (nrgvminjector )from first VM (nrgvmapploader): Pinging first VM (nrgvmapploader )from second VM (nrgvminjector): 2014 NRG Global, Inc. All rights reserved. Page 21
INSTALLING APPLOADER SUITE ON WINDOWS AZURE PREREQUISITES The AppLoader Suite consists of three components AppLoader Controller, Injector and ScenarioBuilder. Together, they comprise NRG Global s easy-to-use, script-free load testing solution. AppLoader works with Terminal Services from Microsoft to generate multiple users simultaneously interacting with an application from one Windows Server. Install the AppLoader components in the following manner: 1. AppLoader Controller Install on a Windows Server. Installation sets up the Controller which manages, drives, and monitors load tests in real-time, and provides test analyses through summarized and detailed reports and graphs. 2. Injector Install on a Windows server. Installation sets up the Injector which hosts multiple users performing real life Scenarios on the application under test. Make sure that AppLoader Controller is already installed before installing the Injector. 3. ScenarioBuilder Install on a Windows Server (same machine or clone of the Injector Server). This easy-to-use tool facilitates the creation of a wide range of test Scenarios for load testing. Start by downloading the AppLoader installation package from the Downloads page on the NRG Global website.. Save the apploader_suite_setup.zip file in the first VM (nrgvmapploader) and extract the contents of the file to a new folder. You will find a separate folder for each of the components; AppLoader, Injector and ScenarioBuilder. Within each folder is a setup file for its respective component. Click here for a video guide through the installation of the three AppLoader components. 2014 NRG Global, Inc. All rights reserved. Page 22
1. INSTALL APPLOADER CONTROLLER These are the steps to install AppLoader Controller: 1. Run the ALSetup.exe file in the AppLoader folder. 2. Click Next to advance to the End User License Agreement (EULA). 3. Review the terms of the EULA and click I accept the agreement and click Next to continue. 4. Select the destination folder for the AppLoader Controller program installation. Click Next to accept the default location or Browse to an alternate location, then click Next. 5. Enter the web server configuration and port settings and click Next. (Choose the defaults unless they are used by other applications. Web Server Port : 8888, Controller Port Range : 9001 9002 ) 6. Review settings and click Install to initiate the installation process. 7. Click Finish to complete the AppLoader Controller installation. To view more detailed installation steps and screenshots, please refer to the AppLoader Installation Guide document. You can find it in AppLoader folder installed on your system or download it here. 2014 NRG Global, Inc. All rights reserved. Page 23
2. INSTALL INJECTOR The Injector and the ScenarioBuilder should both be installed in the second VM (nrgvminjector). In order to install the Injector and ScenarioBuilder, there should be an RDP session open for each of the VMs. Start by copying the Injector and ScenarioBuilder folders found in the apploader_suite_setup file that were saved in the first VM (nrgvmapploader) in the previous section. 1. Run the IJSetup.exe file in the Injector folder. 2. Click Next to advance to the End User License Agreement (EULA). 3. Review the terms of the EULA and click I accept the agreement and click Next to continue. 4. Select the destination folder for the Injector program installation. Click Next to accept the default location or Browse to an alternate location, then click Next. 5. In this step you should enter the IP address of the Server hosting the Controller in the AppLoader Base IP Address field. Enter the AppLoader Web Server Port address use the same port that was assigned to the AppLoader Web Server Port in the AppLoader installation. (Choose the default one: Web Server Port: 8888 ), then click Next. Go to the Azure Portal and open the Dashboard of the machine that has the AppLoader Controller installed. Look for the Internal IP address: 100.75.254.35 2014 NRG Global, Inc. All rights reserved. Page 24
Copy and Paste the Internal IP Address to the Injector Installation Wizard. 6. The Injector setting will be configured automatically, Click Next. 2014 NRG Global, Inc. All rights reserved. Page 25
7. Provide authorized user credentials to log in automatically whenever the Injector Server is started. 8. Review settings and click Install to initiate the installation process. 9. Click Finish to complete the Injector installation. Once installed, the Injector will start automatically. But if it does not start, you can start it from the Injector s folder in program menu. To view more detailed installation steps and screenshots, please refer to the AppLoader Installation Guide document. You can find it in AppLoader folder installed on your system or download it here. 2014 NRG Global, Inc. All rights reserved. Page 26
3. INSTALL SCENARIOBUILDER Load Testing On Windows Azure : AppLoader 7.7 The Injector and the ScenarioBuilder should both be installed in the second VM. In order to install the Injector and ScenarioBuilder, there should be an RDP session open for each of the VMs. Make sure that ScenarioBuilder and Injecotr are installed in the same machine. 1. Run the SBSetup.exe file in the ScenarioBuilder folder. 2. Click Next to advance to the End User License Agreement (EULA). 3. Review the terms of the EULA and click I accept the agreement and click Next to continue. 4. Enter the IP address or name of the Server (nrgvmapploader)hosting the Controller in the Host Name field. Enter the Port Number address use the same port that was assigned for Web Server Port in the Controller/Base installation. (Choose the default one: Port Number: 8888 ), then click Next. 5. Select the destination folder for the ScenarioBuilder program installation. Click Next to accept the default location or Browse to an alternate location, then click Next. 2014 NRG Global, Inc. All rights reserved. Page 27
6. Select the destination folder for the ScenarioBuilder program shortcuts. Click Next to accept the default location or Browse to an alternate location, then click Next. 7. Review settings and click Install to initiate the installation process. 8. Click Finish to complete the ScenarioBuilder installation. To view more detailed installation steps and screenshots, please refer to the AppLoader Installation Guide document. You can find it in AppLoader folder installed on your system or download it here. Optimize The Server: After all the components have been installed, follow the steps in the Server Configuratio.pdf document located in the apploader_suite_setup folder. The pdf document that should be used depends on which server is being used (i.e. Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 or Windows Server 2012). 2014 NRG Global, Inc. All rights reserved. Page 28
INSTALL MICROSOFT.NET FRAMEWORK 3.5 After installing the AppLader Contoller, the Injector and ScenarioBuilder. Perform the following steps in both VMs. 1. Open the Server Manager. Click on Add Features. 2. Check.NET Framework 3.5.1 Features. Click Next 2014 NRG Global, Inc. All rights reserved. Page 29
3. Click on Add Requested Role Services 2014 NRG Global, Inc. All rights reserved. Page 30
4. Click Next. 5. Click Next. 2014 NRG Global, Inc. All rights reserved. Page 31
6. Click Install. 7. Wait for installation to finish. Restart machine. 2014 NRG Global, Inc. All rights reserved. Page 32
GETTING STARTED WITH APPLOADER CREATE AND EXECUTE A LOAD TEST The communication flow for AppLoader is: AppLoader Controller Injector rusermanager VStation VStation - The VStation is the component that is installed under each ruser. The VStation is what will perform the playback of the scenario during the load test, without it the ruser will not perform the Scenario playback. The VStation is programmed to start automatically once the ruser is logged in. rusers - The real user accounts which exist in the Windows environment and are administered through AppLoader. rusermanager - This is the component of ScenarioBuilder that is used to oversee the rusers during Scenario playback. Also, it is better to create your scripts inside the rusermanager. Before launching the controller and starting load testing, make sure to start the Injector and the VSation. You can start them from the Injector s folder in program menu. Launch AppLoader Controller: After installing AppLoader, a shortcut will be created on the desktop. Launch the AppLoader Controller web interface to manage, run, and analyze your tests. 1. Double-click the AppLoader shortcut to launch the AppLoader Controller in your default browser. You can also launch the AppLoader Controller by entering IP address of the Server (or localhost ) and Web Server Port number into the address bar of a web browser. 2014 NRG Global, Inc. All rights reserved. Page 33
2. Log in to AppLoader (User Name: admin / Password: admin) You ll notice the Injector has registered itself with the AppLoader Controller. If the Injector was not registered with the AppLoader Controller, turn off the Firewalls for both VMs (nrgvmapploader and nrgvminjector). Define rusers: Defining rusers is the first step in preparing a load test. Once rusers are defined, this step does not have to be repeated, unless rusers are deleted. Define rusers only applies to AppLoader suite if it is installed onto a server, if the AppLoader suite is installed on a PC, rusers cannot be defined. Check the Injector that you want to define rusers for. Then click the Define rusers the menu bar. Injector rusers form opens; button in 2014 NRG Global, Inc. All rights reserved. Page 34
Mode: Select the type of ruser accounts to create from the drop down menu (Incremental; From CSV File, One ruser). User Name: Provide a generic user name for ruser accounts. AppLoader will add a sequential numeric suffix to make each account unique (e.g. ruser001, ruser002, ruser003, etc ). User names must be compliant with the Windows server requirements. Recommended value: ruser) Password: Enter a password for the ruser accounts. Password must be compliant with the Windows server requirements. Recommended value: Password123). Click Submit to issue the Define rusers command. If rusers are not created prior to launching a test, ruser Manager will automatically create rusers for the test. Start rusers: The next step in the process is to Start rusers. This process launches the rusermanager on the Injector and initiates the ruser logins. Start rusers only applies to AppLoader suite if it is installed onto a Server. Click the Start rusers button. The Start rusers window pops up; # Of Users: Specify the number of users to start on the selected Injector. Launch Delay: Specify a launch delay in seconds. The system waits this amount of time after starting each ruser. Click Submit to start rusers. Started rusers can be viewed in the Real Time Results page of the Controller. 2014 NRG Global, Inc. All rights reserved. Page 35
Once you start the rusers, ruser Manager will automatically start on the second VM (nrgvminjector). The rusermanager can be viewed throughout the test process, from the starting of rusers through the complete execution of the test. It can be minimized or maximized on the Injector as the test is in progress. However closing the rusermanager during the test would end Scenario playback and disrupt the test. You can view, manage, delete, stop, and disconnect rusers from AppLoader Controller and delete them from Windows Server. 2014 NRG Global, Inc. All rights reserved. Page 36
Create A Scenario Using ScenarioBuilder Inside The rusermanager: In this part, you should create your scenario with ScenarioBuilder. Scenarios are the action sequences which emulate your real user activity within your application. Creating your first scenario is simple. If you know how to use your application, then you know how to script a scenario with ScenarioBuilder. For this guide, we creates three separate scenarios that are related to each other: Login, Search and Log off. The second scenario (Search)can include multiple scripts. You can create your own scenario. After you finish your scenario, do the following steps: 1. Playback scenario (as many times as necessary) to ensure that it performs as expected. 2. Set reference time (in execution report window after a successful scenario playback). 3. Save scenario. 4. Send it to Controller. You will see a dialog box indicating Send successful upon completion. To make sure that the scenario will be send to the correct controller, you can follow these steps: 1. Click on View in ScenarioBuilder toolbar 2. Go to Option 3. Click on Base 4. If you couldn t find the Controller address ( In this case, the IP address of the Controller is the Internal IP address of the first VM (nrgvmapploader: 100.75.254.35 ), click on Add button to enter your Apploader Controller information. 2014 NRG Global, Inc. All rights reserved. Page 37
5. Click on Test button to test the connection between ScenarioBuilder and Controller. 5. Close or minimize ScenarioBuilder. Please refer to the ScenarioBuilder User Guide for more information. You can download it from here. Click here for the complete ScenarioBuilder video tutorial series. 2014 NRG Global, Inc. All rights reserved. Page 38
Manage Tests: Click the Manage Tests button to design a Test Plan. The Manage Tests page defaults to the Test Plans List view; it is empty if you have not created any Test Plans yet. Click the Create New Test Plan button in the menu bar. The Test Plan form opens; The below image shows how the Test Plan form looks upon opening. Fill out the required information in each field. Here are the quick steps: 1. Enter a name for the new Test Plan. 2. Attach a Template for backend monitoring (optional). 2014 NRG Global, Inc. All rights reserved. Page 39
3. Provide a Steady State Time in minutes that the user will actively play scenario. As you login (Open) and log off (Close) a website or an application only once, it is better to set value 0 for the Steady State Time filed when you create the Login and Log off Test Plans. 4. Ramp-up Time and Users/Minute will be automatically calculated based on the Test Plan details provided (these fields cannot be edited manually). 5. Select the Injector. There is only one Injector that can be selected from Injector field in TestPlan Details section. 6. Select the scenario that should be tested. 7. Enter the number of rusers to play the selected Scenario on the selected Injector. 8. Enter the time, in seconds, that each ruser waits before playing the Scenario. A Delay value of "0" results in all rusers beginning simultaneously. A Delay value of "5" results in each ruser beginning 5 second after the previous. A Delay value of 30 will be an appropriate value for the Login and Log off Test Plans. 9. As soon as you select the scenario from the Scenario field in the TestPlan Details, AppLoader automatically calculates the test duration and iterations and populates those fields on the form. All the information about that scenario, such as the CSV Files, etc. will be set automatically. Although you can change them, it is not necessary. 2014 NRG Global, Inc. All rights reserved. Page 40
For more information on filling out these fields please refer to AppLoader UserGuide document. You can download it from here. After completing all of the applicable sections of the Test Plan, click the Save Details window to save your Test Plan. The following message will appear: button above the Click Yes to open the Execution Plan form for viewing and editing; The Execution Plan will show the ruser name, Host, assigned Scenario, assigned number of Iterations, Start Delay, CSV file, and Assigned CSV Rows. 2014 NRG Global, Inc. All rights reserved. Page 41
Close the Execution Plan window to continue. The following message will appear: If you have only one scenario that you want to run, click Yes to run your test otherwise click No to exit without running. If you clicked Yes the following window opens. Specify a name for your load test and click Submit. AppLoader shifts to the Real Time Results page automatically after submitting the test. 2014 NRG Global, Inc. All rights reserved. Page 42
For this guide, we create three scenarios. Therefore, we have to create three Test Plans for each of them. For Load Testing, we need to create an execution flow. Create An Execution Flow: With Execution Flows you are able to cue up a series of Test Plans to automatically play, one after the next. Click the Create New Execution Flow button in the menu bar. The Execution Flow Schedule form opens; The below image shows how the Execution Flow Schedule page looks upon opening. Fill out the required information in each field. Here are the quick steps: 1. Enter a name for the Execution Flow (avoid special characters). 2. Provide an optional description to help identify this Execution Flow. 3. Double-click on, the Available Test Plans pane the Test Plans you wish to include in your Execution Flow. 4. Use this feature to establish whether or not to execute tests on the rusers that failed in the previous test. 2014 NRG Global, Inc. All rights reserved. Page 43
5. Click Save button to save the Exectution Flow. 6. To initiate a test using an Execution Flow, click Run button. 7. Click on Submit AppLoader shifts to the Real Time Results page automatically after submitting the test. Congratulations! Your Execution Flow or TestPlan has been submitted! Go to the Second VM (nrgvminjector) and maximize the rusermanager to see each ruser session executing scenarios in real time. For more information please refer to AppLoader UserGuide document. You can download it here. 2014 NRG Global, Inc. All rights reserved. Page 44
Real Time Results: Click View Real Time Results for graphical view of the test in progress, from the Controller perspective. Click here for a video demonstration of Test Plan configuration and Real Time Results. Test Analysis: When test has completed, click Test Analysis for final results. The Test Analysis page contains four panes: Load Test; Pie Chart; Stats; Graph. Click here for a video demonstration of Test Analysis. Test Failures and Screenshots: View screenshots of application slowness or errors occurring during the playback in real-time. 2014 NRG Global, Inc. All rights reserved. Page 45
MAKING IDENTICAL VMS USING A RE-USABLE IMAGE VM profiles can be saved as images, these images can be used to provision identical virtual machines. An image of the Injector VM can be saved an used to create more Injectors. Run The System Preparation Tool (Sysprep) To Prepare The Virtual Machine as An Image: 1. Connect to the existing virtual machine nrgvminjector using a new or existing Remote Desktop session. 2. Press <Windows Key + R>and type in C:\Windows\System32\Sysprep\sysprep.exe then press <Enter> 3. Once the System Preparation Tool Launches a. Check Generalize b. Change Shutdown Options to Shutdown c. Press OK 2014 NRG Global, Inc. All rights reserved. Page 46
Capture The Virtual Machine As A Reusable Image: Load Testing On Windows Azure : AppLoader 7.7 Open Windows Azure Management Portal and select Virtual Machines in the left navigation so you may view the current state of all virtual machines. Do not proceed until nrgvminjector is in the shutdown state (this may take several minutes as sysprep generalizes the virtual machine). 1. Select the Virtual Machine by clicking nrgvminjector 2. On the bottom of the page click the CAPTURE button to capture the virtual machine as a reusable image. 3. Type in a name in the IMAGE NAME box and check I have run Sysprep on the virtual machine. Press the check mark to start the capture operation. The VM will be deleted after the image is captured. 4. The portal will automatically open the Images tab in the Virtual Machines section. 2014 NRG Global, Inc. All rights reserved. Page 47
5. Wait before the image status to be available before proceeding. Create A Virtual Machine Instance from the Image: 1. Click +NEW on the bottom left corner of the Portal 2. Select COMPUTE -> VIRTUAL MACHINE -> FROM GALLERY. 3. Select the custom image by clicking MY IMAGES on the left navigation and selecting opsvmimage and then click the right arrow at the bottom of the dialog to move forward. 2014 NRG Global, Inc. All rights reserved. Page 48
4. Provide basic properties for the virtual machine. a. Specify nrgvminjector as the VIRTUAL MACHINE NAME b. Provide a USER NAME and PASSWORD. This will be the credentials you will use to login into the machine. c. Click the right arrow at the bottom of the dialog to move forward link. 5. Specify the provisioning configuration settings of the virtual machine. a. Select the cloud service that was created in the AppLoader Controller machine section. b. Select the previously created storage account as well. c. Configure the Endpoints for the Virtual Machine. By default Windows based virtual machines have ports enabled for Remote Desktop and Remote PowerShell. 2014 NRG Global, Inc. All rights reserved. Page 49
6. Review the Virtual machine configuration and press the check mark button at the bottom of this dialog and Windows Azure will start provisioning the Virtual Machine. After the VM is finished provisioning, you will notice that DNS name for the two machines should be the same. 2014 NRG Global, Inc. All rights reserved. Page 50
After cloning the Injector, you can start to create and execute your Load Tests with the new Injector. To view more detailed steps and screenshots, please refer to the Create And Execute A Load Test section. INDEX - TROUBLESHOOTING VIRTUAL MACHINES ARE GREYED OUT Check on the status of your Virtual Machines and Virtual Networks: https://account.windowsazure.com/previewfeatures If your status is YOU ARE QUEUED like above, please contact support to have gain access to this feature. Normally, you would be able to set up a Virtual Machine from the moment you create your account. Cloud Service acts as a network and security boundary. To prevent IP addresses from changing, keep at least 1 VM open on the cloud service. APPLOADER SERVICES 2014 NRG Global, Inc. All rights reserved. Page 51
Some issues that occur while using AppLoader can be solved by restarting the AppLoader services. For example, communication issues between the different components of AppLoader, graphs not updating, and Injectors not connecting to the AppLoader Controller. The AppLoader Suite has three services: 1. AppLoader Controller Suite 2. AppLoader Scheduler 3. AppLoader WebServer To restart these services: 1. Launch the Task Manager 2. Open the Services tab. 3. Click on the button on the bottom right corner. 4. Look for the three AppLoader services, right click on them and click on Restart. VSTATION Some issues that can be traced back to the vstation include: the rusers not playing the scenario not playing, the AppLoader Controller not displaying any rusers connected or displaying the incorrect number of rusers that are connected. If these issues occur, check that the VStation is running. Follow below steps for troubleshooting VStation: 1. Open the Task Manager 2. Under the Processes tab look for VStation.exe 3. If the process isn t running open the Injector folder and click on the Start VStation file. 4. If the process needs to be restarted, right click on it from the Task Manager list and select Stop. Then open the Injector folder and click on the Start VStation file. The VStation Log file can be found here: VStation C:\Program Files (x86)\nrgglobal\injector\logs LOGS 2014 NRG Global, Inc. All rights reserved. Page 52
The logs will log everything the Injector, rusermanager, and ruser does and gives details about each event. There is a time stamp on each line that shows each event that took place. In this folder, you will find these logs: Injector.log - Show logs regarding the communication between AppLoader Controller and Injector. rusermanager.log - Show the connection status of rusers and when the commands were sent. ruser.log - Show how each ruser performed each action the ruser played back and communication events. This will be helpful with resolving issues and seeing when and where events occurred when performing tests and checking configurations. If you are requesting technical support, it is recommended to send copies of your log files attached to the email. You can find Logs files here: Injector, rusermanager, ruser C:\Program Files (x86)\nrgglobal\injector\logs LICENSE Some issues that can be traced back to the expired license include: AppLoader is not starting load testing, Scenario is not playing in the ScenarioBuilder, etc. Therefore, you need to renew your license. To request or purchase a new license, please contact NRG Global Sales team. To install the licenses, place the AppLoaderLicense.lic and sblicense.lic under the folders: AppLoader C:\Program Files (x86)\nrgglobal\ AppLoader\ license ScenarioBuilder C:\Program Files (x86)\nrgglobal\ ScenarioBuilder \ license Free POC! Need a Proof of Concept? Our experts will help establish AppLoader s viability so that your organization, from stakeholders down to data entry clerks, is 100% behind your decision to go forward with AppLoader! If at any point during your trial you need more help, our technicians are waiting to help you! Don t hesitate to call our experts at 888-624-4447 or email NRG Global Support. support@nrgglobal.com 2014 NRG Global, Inc. All rights reserved. Page 53