Load Generator
Presentation
Components of Generator
 Virtual User Generator
 Controller
 Analysis
Virtual User Generator
 Virtual User Generator (VuGen), is a primary tool for creating testing scripts
that emulate behavior of real users on your system.
 When testing or monitoring an environment, you need to emulate the true
behavior of users on your system.
 Micro Focus testing tools emulate an environment in which users concurrently
work on, or access your system. To perform this emulation, the human is
replaced with a virtual user, ora Vuser. The actions that a Vuser performs are
typically recorded in aVuser script. The primary tool for creating Vuser scripts
is Micro Focus Virtual User Generator, also known as VuGen.
(1) Create New Script
 he first step in developing a new Vuser script is to create a blank script.
 The contents and structure of the blank Vuser script vary slightly based on the
protocol of the script. Therefore, before you create a blank Vuser script, you
must know the protocol to use for the script. After you create a blank
Vuser script, you are ready to perform the next step in the script creation
workflow - recording user actions into the script.
(2) Record
 After you create an empty Vuser script, you are ready to use VuGen to record typical user-actions into the
script. While you record the script, VuGen's floating Recording toolbar gives you access to the main
recording functionality, such as pausing and stopping the recording, and inserting transactions and
rendezvous points. For details on how to record a Vuser script, see Record a Vuser script.
 Each Vuser script contains at least three sections: vuser_init, one or more action sections, and vuser_end.
When you run multiple iterations of a Vuser script, only the Actions sections of the script are repeated—
the vuser_init and vuser_end sections are not repeated. Before you record, and during recording, you can
select the section of the script into which VuGen inserts the recorded functions. For details on the script
sections, see Vuser script sections.
 Before you start recording, make sure that the recording options are set correctly for the script. For more
information about the recording options, see Recording options.
 When you have finished recording the user actions, VuGen generates the Vuser script and performs various
other post-recording operations. You can replay the script to make sure that it functions correctly. For
details, see Replay.
 To resolve situations where you cannot install VuGen on the client machine, VuGen allows you to record
scripts using a LoadRunner proxy. Proxy recording may be required with certain Linux machines, Mac OS
machines, and mobile devices. For details, see Record via a proxy.
(A) ISA : Monitoring Parameters
(A) ISA : Mandatory Requirements for
Web Applications
 SSO_ID – All the web application should be behind SSO for enhanced protection.
 Website hosted on Production URL will not be audited. Staging server URL must be
provided for the application to be audited.
 In one department multiple modules exists for day to day working. The OIC of the
project may create one application for all the modules or create virtual directories
for modules. Separate domains are not recommended. For example - phed
department requested for separate URL of all the 11 modules.
(A) ISA : Process Flow
 OIC Project Requests for the Security Audit Testing (Internal or External) to OIC Security Audit
 OIC Security Audit validates the request and
 Return back to OIC if any shortcomings
 In case of Internal Security Audit Requirements: forward the Request to Internal Auditor for Security Audit.
 In case of External Security audit requirements: forward the Request to registered External Agencies for Security Team.
For External Audit, work order will be generated for the agency.
 For Internal Audit, Internal Team in SOC start the process of security audit (manual as well as automation
testing)
 Burp suite application – Manual testing - Freeware
 HCL App scan for automation testing – License copy in SDC
 ZAP Tool for manual testing - Freeware
 Kali Linux – manual testing - Freeware
 Internal Audit Team does manual and automation testing of the application within three (3) Days and share the
report to OIC Project.
 Now the development Team of the concerned Project does all the changes in the Website/application as per
report. The number of days for this is not defined.
 Once all the changes are done then OIC Project may request for Re-Audit Testing again.
 There may be many iterations of the (Step-3/4/5) till all the vulnerabilities are resolved.
 Security Audit completes after this and OIC Security Audit issue safe to host certificate for the application.
(A) ISA : Challenges
 Internal Time Line for changes to be done by the OIC is not defined.
(B) Application Performance Monitoring
 RFP :
 Scope of Work :
 FMS Firm : M/s Airtel <><><><>
 Representative of the firm Sh. Rahul Mourya is deputed in BSDC for the
installation of the app Dynamics App Agent
 Contract Period : From to <>
 Cost of One Year : <>
 The FMS activity is a part of the RFP of SOC (Security Operation Center –
SDC Project)
(C) APM : Summary Sheet
 Request for Proposal (RFP) for OEM Technical Support, Subscription and Maintenance
of Existing Micro Focus Load Runner for 3 years
 Firm Name :
 Work Order date :
 Work Order Value :
 Date of Installation :
 Verification of the Task :
 Payment Release (70%) :
 Payment to be released (30%) :
 First quarter :
 Scope of work in every Quarter :
 First Quarter Work order :
(B) APM: Process Flow
 OIC Project Request for the Application Performance Monitoring(APM).
 Performa of APM Fill
 Configuration Activity
 Setup app dynamics Agent on Production / Staging
 Application Restart required after AppDynamics App Agent Installation.
 Share the following to the concerned OIC
 Username and Password of Appdynamics portal
 User Manual of appdynamics Portal
 Training to developer team
 Daily Status Report (On Request) through email
(B) APM: Software application Used
 App dynamics App Agent
 License copy of software is purchased by DoIT&C
 No. of Concurrent License for installations is 54 max.
(B) APM : Testing Parameters
(B) APM: Challenges
(B) APM: Outcome
 Total No. of application where app dynamics app agent was installed <200>
 On the basis of testing parameters, OIC Project may modify the application
so that the performance of the application may be improved.
S. No. OIC Name Application Name Prior to App Dynamics Post App Dynamics
Param 1 Param 2 Param 3 Param 1 PAram 2 PAram 3
1
(B) APM: Request Format
S. No. Description
1 Application URL
2 Application Details Application Framework:-
Programing Language Used:-
Application Process Flow Document
3 Production Server Server IP:
Number of servers:-
Other Details
Staging Server details Server IP:
Number of servers:-
Other Details
4 Server Login details User Name
Password
5 OIC Details Name:
Mobile No.
Email:
6 Development Team Name:
Mobile No.
Email:
(B) APM: Way Forward
(C) Load Testing (External)
 Request for Proposal (RFP) for OEM Technical Support, Subscription and Maintenance
of Existing Micro Focus Load Runner for 3 years
(C) Summary of Load Testing (External)
 Request for Proposal (RFP) for OEM Technical Support, Subscription and Maintenance
of Existing Micro Focus Load Runner for 3 years
 Firm Name : M/s Integre Solution Pvt. Ltd., Gurgaon
 Work Order date : 29/08/2023
 Work Order Value : 4.0 Cr.
 Date of Installation : 08/09/2023
 Verification of the Task : 21/11/2023
 Payment Release (70%) : 70% Payment releases in last week of Nov 2023
 Payment to be released (30%) : 10% every year for next three years
 First quarter : 10/09/2023 to 10/12/2023
 Scope of work in every Quarter : Load Testing of 10 Web Applications
 First Quarter Work order : for Load Testing of 10 application on
22/12/2023
(C) Load Testing (Internal)
(C) Load Testing (Internal - Process Flow)
(C) Load Testing (Load Testing Parameters)
(C) Demo Application: Aadhaar Based Face Authentication
(Sh. Ranveer Singh S.A. (J.D.)
(C) Load Testing: Challenges & Outcome
(C) Load Testing: Way Forward
(C) Load Testing: Guidelines
(C) Proposed Application for Load Testing
(D) SSL (Secure Socket Layer) Certificate
(E) Business to Government (B2G) Portal
(E) B2G : NEED OF E-BUSINESS PORTAL
(E) B2G :
(E) B2G : Communication and its types
(E) B2G : Key Functionalities
(E) B2G : KEY BENEFITS
(E) B2G : The concept of e-Business has been
appreciated twice as detailed below:
(E) B2G : Following activities have been done for the
Business to Government Portal.
(E) B2G : Review Meeting by Chief Secretary
on 09.03.2023
(E) B2G : Project Status as on date
(E) B2G: Budget Estimation
(E) Way Forward

Load testing checks how a system performs under expected user traffic

  • 1.
  • 3.
    Components of Generator Virtual User Generator  Controller  Analysis
  • 4.
    Virtual User Generator Virtual User Generator (VuGen), is a primary tool for creating testing scripts that emulate behavior of real users on your system.  When testing or monitoring an environment, you need to emulate the true behavior of users on your system.  Micro Focus testing tools emulate an environment in which users concurrently work on, or access your system. To perform this emulation, the human is replaced with a virtual user, ora Vuser. The actions that a Vuser performs are typically recorded in aVuser script. The primary tool for creating Vuser scripts is Micro Focus Virtual User Generator, also known as VuGen.
  • 5.
    (1) Create NewScript  he first step in developing a new Vuser script is to create a blank script.  The contents and structure of the blank Vuser script vary slightly based on the protocol of the script. Therefore, before you create a blank Vuser script, you must know the protocol to use for the script. After you create a blank Vuser script, you are ready to perform the next step in the script creation workflow - recording user actions into the script.
  • 6.
    (2) Record  Afteryou create an empty Vuser script, you are ready to use VuGen to record typical user-actions into the script. While you record the script, VuGen's floating Recording toolbar gives you access to the main recording functionality, such as pausing and stopping the recording, and inserting transactions and rendezvous points. For details on how to record a Vuser script, see Record a Vuser script.  Each Vuser script contains at least three sections: vuser_init, one or more action sections, and vuser_end. When you run multiple iterations of a Vuser script, only the Actions sections of the script are repeated— the vuser_init and vuser_end sections are not repeated. Before you record, and during recording, you can select the section of the script into which VuGen inserts the recorded functions. For details on the script sections, see Vuser script sections.  Before you start recording, make sure that the recording options are set correctly for the script. For more information about the recording options, see Recording options.  When you have finished recording the user actions, VuGen generates the Vuser script and performs various other post-recording operations. You can replay the script to make sure that it functions correctly. For details, see Replay.  To resolve situations where you cannot install VuGen on the client machine, VuGen allows you to record scripts using a LoadRunner proxy. Proxy recording may be required with certain Linux machines, Mac OS machines, and mobile devices. For details, see Record via a proxy.
  • 7.
    (A) ISA :Monitoring Parameters
  • 12.
    (A) ISA :Mandatory Requirements for Web Applications  SSO_ID – All the web application should be behind SSO for enhanced protection.  Website hosted on Production URL will not be audited. Staging server URL must be provided for the application to be audited.  In one department multiple modules exists for day to day working. The OIC of the project may create one application for all the modules or create virtual directories for modules. Separate domains are not recommended. For example - phed department requested for separate URL of all the 11 modules.
  • 13.
    (A) ISA :Process Flow  OIC Project Requests for the Security Audit Testing (Internal or External) to OIC Security Audit  OIC Security Audit validates the request and  Return back to OIC if any shortcomings  In case of Internal Security Audit Requirements: forward the Request to Internal Auditor for Security Audit.  In case of External Security audit requirements: forward the Request to registered External Agencies for Security Team. For External Audit, work order will be generated for the agency.  For Internal Audit, Internal Team in SOC start the process of security audit (manual as well as automation testing)  Burp suite application – Manual testing - Freeware  HCL App scan for automation testing – License copy in SDC  ZAP Tool for manual testing - Freeware  Kali Linux – manual testing - Freeware  Internal Audit Team does manual and automation testing of the application within three (3) Days and share the report to OIC Project.  Now the development Team of the concerned Project does all the changes in the Website/application as per report. The number of days for this is not defined.  Once all the changes are done then OIC Project may request for Re-Audit Testing again.  There may be many iterations of the (Step-3/4/5) till all the vulnerabilities are resolved.  Security Audit completes after this and OIC Security Audit issue safe to host certificate for the application.
  • 14.
    (A) ISA :Challenges  Internal Time Line for changes to be done by the OIC is not defined.
  • 15.
    (B) Application PerformanceMonitoring  RFP :  Scope of Work :  FMS Firm : M/s Airtel <><><><>  Representative of the firm Sh. Rahul Mourya is deputed in BSDC for the installation of the app Dynamics App Agent  Contract Period : From to <>  Cost of One Year : <>  The FMS activity is a part of the RFP of SOC (Security Operation Center – SDC Project)
  • 16.
    (C) APM :Summary Sheet  Request for Proposal (RFP) for OEM Technical Support, Subscription and Maintenance of Existing Micro Focus Load Runner for 3 years  Firm Name :  Work Order date :  Work Order Value :  Date of Installation :  Verification of the Task :  Payment Release (70%) :  Payment to be released (30%) :  First quarter :  Scope of work in every Quarter :  First Quarter Work order :
  • 17.
    (B) APM: ProcessFlow  OIC Project Request for the Application Performance Monitoring(APM).  Performa of APM Fill  Configuration Activity  Setup app dynamics Agent on Production / Staging  Application Restart required after AppDynamics App Agent Installation.  Share the following to the concerned OIC  Username and Password of Appdynamics portal  User Manual of appdynamics Portal  Training to developer team  Daily Status Report (On Request) through email
  • 18.
    (B) APM: Softwareapplication Used  App dynamics App Agent  License copy of software is purchased by DoIT&C  No. of Concurrent License for installations is 54 max.
  • 19.
    (B) APM :Testing Parameters
  • 20.
  • 21.
    (B) APM: Outcome Total No. of application where app dynamics app agent was installed <200>  On the basis of testing parameters, OIC Project may modify the application so that the performance of the application may be improved. S. No. OIC Name Application Name Prior to App Dynamics Post App Dynamics Param 1 Param 2 Param 3 Param 1 PAram 2 PAram 3 1
  • 22.
    (B) APM: RequestFormat S. No. Description 1 Application URL 2 Application Details Application Framework:- Programing Language Used:- Application Process Flow Document 3 Production Server Server IP: Number of servers:- Other Details Staging Server details Server IP: Number of servers:- Other Details 4 Server Login details User Name Password 5 OIC Details Name: Mobile No. Email: 6 Development Team Name: Mobile No. Email:
  • 23.
    (B) APM: WayForward
  • 24.
    (C) Load Testing(External)  Request for Proposal (RFP) for OEM Technical Support, Subscription and Maintenance of Existing Micro Focus Load Runner for 3 years
  • 25.
    (C) Summary ofLoad Testing (External)  Request for Proposal (RFP) for OEM Technical Support, Subscription and Maintenance of Existing Micro Focus Load Runner for 3 years  Firm Name : M/s Integre Solution Pvt. Ltd., Gurgaon  Work Order date : 29/08/2023  Work Order Value : 4.0 Cr.  Date of Installation : 08/09/2023  Verification of the Task : 21/11/2023  Payment Release (70%) : 70% Payment releases in last week of Nov 2023  Payment to be released (30%) : 10% every year for next three years  First quarter : 10/09/2023 to 10/12/2023  Scope of work in every Quarter : Load Testing of 10 Web Applications  First Quarter Work order : for Load Testing of 10 application on 22/12/2023
  • 27.
    (C) Load Testing(Internal)
  • 28.
    (C) Load Testing(Internal - Process Flow)
  • 29.
    (C) Load Testing(Load Testing Parameters)
  • 30.
    (C) Demo Application:Aadhaar Based Face Authentication (Sh. Ranveer Singh S.A. (J.D.)
  • 31.
    (C) Load Testing:Challenges & Outcome
  • 32.
    (C) Load Testing:Way Forward
  • 33.
  • 36.
    (C) Proposed Applicationfor Load Testing
  • 37.
    (D) SSL (SecureSocket Layer) Certificate
  • 38.
    (E) Business toGovernment (B2G) Portal
  • 39.
    (E) B2G :NEED OF E-BUSINESS PORTAL
  • 40.
  • 41.
    (E) B2G :Communication and its types
  • 42.
    (E) B2G :Key Functionalities
  • 43.
    (E) B2G :KEY BENEFITS
  • 44.
    (E) B2G :The concept of e-Business has been appreciated twice as detailed below:
  • 45.
    (E) B2G :Following activities have been done for the Business to Government Portal.
  • 46.
    (E) B2G :Review Meeting by Chief Secretary on 09.03.2023
  • 47.
    (E) B2G :Project Status as on date
  • 48.
    (E) B2G: BudgetEstimation
  • 49.