HP Application Lifecycle Management 12.00 Benchmark Kit ...community.softwaregrp.com/dcvta86296/attachments/dcvta86296/sws... · based on HTTP protocol and OTA API. Therefore, they

HP Application Lifecycle Management 12.00 Benchmark Kit Manual Process March 2014

PCoE ALM 12 - Benchmark Kit Manual

Legal Notices

Warranty

The only warranties for HP products and services are set forth in the express warranty statements

accompanying such products and services. Nothing herein should be construed as constituting an

additional warranty. HP shall not be liable for technical or editorial errors or omissions contained

herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying.

Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software

Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government

under vendor's standard commercial license.

Copyright Notices

© Copyright 2014 Hewlett-Packard Development Company, L.P.

Trademark Notices

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Microsoft SQL Server is a trademark of the Microsoft Corporation.

Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California.

UNIX® is a registered trademark of The Open Group.

Red Hat Linux is a trademark of Red Hat, Inc.


Table of Contents

Warranty ...................................................................................................................................... 2

Restricted Rights Legend .......................................................................................................... 2

1. Introduction ............................................................................................................................. 4

2. Kit Structure and Content ........................................................................................................ 5

2.1. Database ........................................................................................................................... 5

2.1.1. Project Size ............................................................................................................... 5

2.1.2. Data Structure ........................................................................................................... 7

2.2. Script Overview................................................................................................................ 9

2.3. Supporting Mechanisms ................................................................................................. 11

2.3.1. Run-Time Settings .................................................................................................. 11

2.3.2. Security ................................................................................................................... 12

2.4. Scenario .......................................................................................................................... 13

3. Kit Installation ....................................................................................................................... 14

3.1. Database ......................................................................................................................... 14

3.1.1. Oracle 11g ............................................................................................................... 14

3.1.2 MS SQL 2008 & 2008 R2 ...................................................................................... 14

3.2. Scripts ............................................................................................................................. 15

3.2.1. Scripts Package Installation .................................................................................... 15

3.2.2. Command line parameters ...................................................................................... 16

3.2.3. Connectivity Add-in................................................................................................ 18

3.3. ALM Server.................................................................................................................... 19

3.3.1. Site Admin Parameters ........................................................................................... 19

3.4. Supporting Mechanisms ................................................................................................. 19

3.4.1. Smart Repository over File System ........................................................................ 19

3.4.2. Upload Repository Files ......................................................................................... 19

3.4.3. Automatic Project Selection ................................................................................... 19

3.4.4. Ping Mechanism...................................................................................................... 21

3.4.5. FReq Parcer ............................................................................................................. 22


1. Introduction This document serves as a guideline for customers who would like to run a benchmark or

performance readiness on Application Lifecycle Management 12.00. LoadRunner scripts

and ALM Master DB have been created by the HP ALM Performance Center of Excellence.

With the right expertise, you can use this package for validating and tuning your ALM

environment.

All scripts in this package were built to run on HP standard projects (part of the Master DB

and repository supplied in the Benchmark kit).

The scripts are not “plug and play”. You should carefully read and follow the instructions

listed below.

Memory Requirements:

This scenario, using the current configuration, requires approximately 12GB of free

RAM on the Injector Machine. The load can be and preferred to distribute among

several injectors.

Please note:

- The scripts do not provide the ability to measure ALM's client response time, as they are

based on HTTP protocol and OTA API. Therefore, they can only measure the server and

network time.

- The scripts are specific for ALM version 12.00. They cannot be executed on other

versions of ALM.

The complete Benchmark Kit is found on the following FTP Server:

FTP: ftp.usa.hp.com (15.192.32.78)

Login: pcoe

Password: Pcoekit1

Folder: ALM 12 Benchmark Kit

ftp://pcoe:[email protected]/ALM 12 Benchmark Kit/

ftp://pcoe:[email protected]/ALM 12 Benchmark Kit/


2. Kit Structure and Content

2.1. Database

2.1.1. Project Size Oracle 11g Total 19,975.44 MB

MS SQL 2008 Total 14,553.600 MB

Table Name # Rows

ACTIONS 117

ALERT 46456

ALL_LISTS 41003

ANALYSIS_ITEMS 79

ANALYSIS_ITEM_FILES 0

ANALYSIS_ITEM_FOLDERS 22

ANALYSIS_ITEM_RESULTS 0

ANALYSIS_SEGMENTS 21

ASSET_RELATIONS 358306

ASSET_REPOSITORY_ITEMS 414936

AUDIT_LOG 2259733

AUDIT_PROPERTIES 2656054

BASELINES 0

BASELINE_ROOTS 0

BL_ALL_LISTS 0

BL_ASSET_RELATIONS 0

BL_ASSET_REPOSITORY_ITEMS 0

BL_BPM_ELEMENTS 0

BL_BPM_LINKS 0

BL_BPM_MODELS 0

BL_BPM_MODEL_FOLDERS 0

BL_BPM_PATHS 0

BL_BPTEST_TO_COMPONENTS 0

BL_BP_ITERATION 0

BL_BP_ITER_PARAM 0

BL_BP_PARAM 0

BL_COMPONENT 0

BL_COMPONENT_FOLDER 0

BL_COMPONENT_MULTIVALUE 0

BL_COMPONENT_STEP 0

BL_COMPONENT_STEP_PARAMS 0

BL_CONFIGURATION_COVERAGE 0

BL_CRITERION_COVERAGE 0

BL_CROS_REF 0

BL_DELETED_ASSETS_INFO 0

BL_DESSTEPS 0

BL_FACETS 0

BL_FRAMEWORK_PARAM 0

BL_REQ 0

BL_REQ_COVER 0

BL_REQ_CYCLES 0

BL_REQ_MULTIVALUE 0

BL_REQ_RELEASES 0

BL_REQ_TRACE 0

BL_RESOURCES 0

BL_RESOURCES_MULTIVALUE 0

BL_RESOURCE_FOLDERS 0

BL_RUNTIME_PARAM 0

BL_STEP_PARAMS 0

BL_TEST 0

BL_TEST_CONFIGS 0

BL_TEST_CRITERIA 0

Table Name # Rows

BL_TEST_MULTIVALUE 0

BL_TEST_PARAMS 0

BL_USER_ASSETS 0

BPM_ELEMENTS 0

BPM_ELEMENT_TYPES 355

BPM_GRAPH_RESULTS 0

BPM_LINKS 0

BPM_MODELS 0

BPM_MODEL_FOLDERS 2

BPM_PATHS 0

BPTA_CHANGE_STATUS 4

BPTEST_TO_COMPONENTS 20210

BP_ITERATION 100450

BP_ITER_PARAM 1004500

BP_ITER_PARAM_VIRT 0

BP_PARAM 202100

BP_PARAM_VIRT 0

BP_STEP_PARAM 40399

BR_ACTIONS 0

BR_ACTIONS_TO_FACTS 0

BR_BUSINESS_RULES 0

BR_CONDITIONS 0

BR_COND_TO_FACTS 0

BR_FACTS 0

BUG 60000

BUG_MULTIVALUE 180000

BUG_TOKENS 3353874

BUSINESS_VIEWS 36

CACHE 0

COMMENTS 0

COMMON_SETTINGS 60092

COMPARISONS 0

COMPARISON_NODES 0

COMPONENT 5210

COMPONENT_FOLDER 107

COMPONENT_MULTIVALUE 0

COMPONENT_STEP 506000

COMPONENT_STEP_PARAMS 0

CONFIGURATION_COVERAGE 184140

CONTENT_DEFINITIONS 0

CONTENT_PARTS 0

CONTENT_ROOTS 0

CRITERION_COVERAGE 184140

CROS_REF 133179

CYCLE 20002

CYCLE_MULTIVALUE 0

CYCL_FOLD 2803

DASHBOARD_FOLDERS 21

DASHBOARD_PAGES 0

DASHBOARD_PAGE_ITEMS 0

DATACONST 27

DELETED_ASSETS_INFO 0


Table Name # Rows

DESSTEPS 1331932

ENTITY_ATTRIBUTES 25

ENTITY_SUBTYPES 75

ENTITY_SUBTYPE_ATTRIBUTES 80

ENTITY_SUBTYPE_FIELDS 35

ENTITY_SUBTYPE_RELATIONS 60

EVENT_LOG 7

EXTENSIONS 3

FACETS 5210

FAVORITES 0

FAVORITE_FOLDERS 15

FORM_LAYOUTS 0

FORM_LAYOUT_FIELDS 0

FRAMEWORK_PARAM 52100

GROUPS 5

HIST_ASSET_RELATIONS 1688720

HIST_ASSET_REPOSITORY_ITEMS 2072520

HIST_BPM_ELEMENTS 0

HIST_BPM_MODELS 0

HIST_BPM_PATHS 0

HIST_BPTEST_TO_COMPONENTS 0

HIST_BP_ITERATION 0

HIST_BP_ITER_PARAM 0

HIST_BP_PARAM 0

HIST_COMPONENT 0

HIST_COMPONENT_STEP 0

HIST_COMPONENT_STEP_PARAMS 0

HIST_CROS_REF 345000

HIST_DESSTEPS 6659660

HIST_FACETS 0

HIST_FRAMEWORK_PARAM 0

HIST_REQ 153450

HIST_RESOURCES 220

HIST_RUNTIME_PARAM 0

HIST_STEP_PARAMS 1056300

HIST_TEST 921240

HIST_TEST_CONFIGS 921240

HIST_TEST_CRITERIA 921240

HIST_TEST_PARAMS 528200

HIST_USER_ASSETS 537320

HOSTS 0

HOST_GROUP 0

HOST_IN_GROUP 0

LIBRARIES 0

LIBRARY_CLOSURE 20

LIBRARY_FOLDERS 1

LIBRARY_MAPPINGS 0

LIBRARY_PARTS_DEFS 0

LIBRARY_USED_BY 0

LIB_MULTIVALUE 0

LINK 40999

LINKED_TEMPLATE_ITEMS 0

LISTS 10045

LOCKS 0

MAILCOND 2

MAPPING_UPGRADE_LOG 0

MODULES 9

POLICY_ENFORCEMENT_STATUS 1

PUBLIC_ENTITY_KEYS 0

QPM_KPIS 0

QPM_KPI_BREAKDOWN_RESULTS 0

QPM_KPI_BREAKDOWN_TYPES 13

Table Name # Rows

QPM_KPI_CALCULATIONS 0

QPM_KPI_CALCULATION_RESULTS 0

QPM_KPI_DEN_DRILLDOWN 0

QPM_KPI_DEN_DRILLDOWN_EXT1 0



QPM_KPI_DEN_DRILLDOWN_PERS 0

QPM_KPI_MILESTONE_SCOPEITEM 0

QPM_KPI_MULTIVALUE 0

QPM_KPI_NUM_DRILLDOWN 0

QPM_KPI_NUM_DRILLDOWN_EXT1 0



QPM_KPI_NUM_DRILLDOWN_PERS 0

QPM_KPI_TYPES 11

QPM_MILESTONES 0

QPM_MILESTONE_MULTIVALUE 0

QPM_MILESTONE_SCOPEITEM 0

QPM_SCOPE_ITEM 0

QPM_SCOPE_ITEM_MULTIVALUE 0

QPM_THRESHOLD_VALUES 0

RBT_CUSTOMIZATION 4

RBT_CUSTOMIZATION_ANSWERS 36

RBT_CUSTOMIZATION_QUESTIONS 12

RECENT_ITEMS 0

RELEASECYCLE_MULTIVALUE 0

RELEASEFOLDER_MULTIVALUE 0

RELEASES 200

RELEASE_CYCLES 2000

RELEASE_FOLDERS 36

RELEASE_MULTIVALUE 0

REPORT_PROJECT_TEMPLATES 79

REPORT_TO_RPT_LINKS 293

REPORT_USER_TEMPLATES 0

REQ 30692

REQ_COVER 245520

REQ_CYCLES 122760

REQ_MULTIVALUE 0

REQ_RELEASES 30690

REQ_TRACE 6000

REQ_TYPE 8

REQ_TYPE_FIELD 398

REQ_TYPE_HIER_RULES 8

RESOURCES 9220

RESOURCES_MULTIVALUE 0

RESOURCE_FOLDERS 1632

RESULTS 0

ROUTE_TABLE_1 0

ROUTE_TABLE_2 0

RULES 6

RUN 400100

RUNTIME_PARAM 0

RUN_CRITERIA 400100

RUN_ITERATIONS 0

RUN_MULTIVALUE 0

SEQUENCES 159

SITE_ACTIONS 0

SITE_ENTITIES 0

SITE_FIELD 0

SMART_REPOSITORY_LOGICAL_FILE 21922232

SMART_REPOSITORY_PHYSICAL_FILE 4158050

STEP 2980255


Table Name # Rows

STEP_PARAMS 264821

SYSTEM_FIELD 1664

SYSTRANSLATE 0

TABLES 121

TASKS 0

TASKS_LOG 0

TASK_LOG_TYPE 3

TASK_STATE 6

TEMPORARY_DATA_FOOTPRINT 0

TEST 185301

TESTCYCL 400020

TESTCYCL_MULTIVALUE 0

TEST_CONFIGS 185301

TEST_CRITERIA 205511

TEST_MULTIVALUE 0

TEST_PARAMS 105682

TEST_VC_INFO 0

TOKENS 1156

TO_ALERT 0

TRAN_RULES 9

USERS 3002

USER_ASSETS 107576

USER_SETTINGS 0

VC_ASSET_RELATIONS 220

VC_ASSET_REPOSITORY_ITEMS 270

VC_BPM_ELEMENTS 0

VC_BPM_MODELS 0

VC_BPM_PATHS 0

VC_BPTEST_TO_COMPONENTS 0

VC_BP_ITERATION 0

Table Name # Rows

VC_BP_ITER_PARAM 0

VC_BP_PARAM 0

VC_COMPONENT 0

VC_COMPONENT_MULTIVALUE 0

VC_COMPONENT_STEP 0

VC_COMPONENT_STEP_PARAMS 0

VC_CROS_REF 120

VC_DELETED_ASSETS_INFO 0

VC_DESSTEPS 867

VC_FACETS 0

VC_FRAMEWORK_PARAM 0

VC_REQ 56

VC_REQ_MULTIVALUE 0

VC_RESOURCES 0

VC_RESOURCES_MULTIVALUE 0

VC_RUNTIME_PARAM 0

VC_STEP_PARAMS 135

VC_TEST 120

VC_TEST_CONFIGS 120

VC_TEST_CRITERIA 120

VC_TEST_MULTIVALUE 0

VC_TEST_PARAMS 70

VC_USER_ASSETS 70

VER_CTRL 120

WORKSPACE_SHARES 0

* Data taken from Oracle DB

2.1.2. Data Structure Module Entity Amount Structure


Releases Release Folders 36 1 Root Folder -> 5 F -> 2 F -> 10 Rel -> 10 Release Cycle Releases 200

Release Cycles 2000

Requirements Requirements 30692 1 Root Req -> 30 Req -> [2 Req (9-10 Levels)]

Business Components

Component Folder

107 1 Root Folder -> 100 F -> 50 Components -> 100 Steps

Component 5210

Component Step 506000

Test Plan All Lists 41152 1 Root Folder -> 70 F

Tests 185261 1 Root Folder -> 19 F -> [2 F, 4 Tests (9 Levels)] -> 5 Tests 1 Root Folder -> 50 F -> 20 Tests

BP Test to Component

20210 1 Root Folder -> 50 F -> 20 Tests -> 20 Components

BP Parameter 202100 1 Root Folder -> 50 F -> 20 Tests -> 20 Components -> 10 Params

Test Lab Cycle Folder 2802 1 Root Folder -> 50 F -> 5 F -> 2 F -> 4 F -> 10 Tests Sets -> 20 Tests Cycle 20002

Run 400100

Defects Defects 60000 60000 Defects

ERI Assets Relation 337656 1 Root Folder -> 10 Res Folder -> 2 Res Folder -> 5RF -> 5 RF -> 2 RF -> 9 Files (5 Lib,3 Object Rep, 1 Recovery scenario)

Assets Repository items

414396


2.2. Script Overview Module Script Transaction

Global Login/Logout

Global_T00_SimpleAction

Global_T02_Login

Global_T03_Logout

Defects

Create / Delete

VB_DEF_CreateDeleteDefect_T01_AddDefect

VB_DEF_CreateDeleteDefect_T02_UpdateDefect

VB_DEF_CreateDeleteDefect_T03_DeleteDefect

Multi Value Filter

VB_DEF_Filters_MultiValues_T01_ORFilter

Filters

VB_DEF_Filters_T01_RegularFilter

VB_DEF_Filters_T02_OrderByFilter

VB_DEF_Filters_T03_ClearFilter

Link

VB_DEF_Link_GetDefectAudit

VB_DEF_Link_GetLinkedDefects

VB_DEF_Link_GetLinkedEntities

Group Grid VB_DEF_GroupGrid_T01_GroupingFilter

Text Search VB_DEF_MemoSearch_T01_MemoSearch

Modify Defect

VB_DEF_ModifyDefect_02_ModifyDefect

Releases Expand Release

VB_REL_Expand_Release_Folder

Requirements

Coverage Analysis

VB_REQ_CoverageAnalysis_T03_CoverageAnalysis

VB_REQ_CoverageAnalysis_T04_GetCoverEntitiesSummaryStatus

VB_REQ_CoverageAnalysis_T05_CoverageAnalysisViewByCycle

VB_REQ_CoverageAnalysis_T06_GetCoverEntitiesSummaryStatusByCycle

Create / Delete

VB_REQ_CreateDeleteReq_T01_CreateRequirement

VB_REQ_CreateDeleteReq_T04_DeleteRequirement

Expand Tree VB_REQ_ExpandTree_T01_ExpandRootReq

Filter Hierarchy

VB_REQ_FilterKeepingHierarchy_01_Filter_Requirements

Update Requirement

VB_REQUpdateRequirement_T02_UpdateRequirement

Storage

Download Multiple

Files

VB_STO_SMART_DownloadMultiple_T01_DownloadFiles

VB_STO_SMART_DownloadMultiple_T02_DeleteDownloadFiles

Logical Attachments

VB_STO_SMARTLogical_Attachment_T01_GetAttachmentValue

VB_STO_SMARTLogical_Attachment_T02_DownloadAttachment

VB_STO_SMARTLogical_Attachment_T03_AddAttachment

VB_STO_SMARTLogical_Attachment_T04_RenameAttachment

VB_STO_SMARTLogical_Attachment_T05_DeleteAttachment


Module Script Transaction

Storage

Logical Upload

Multiple Files

VB_STO_SMARTLogical_UploadMultipleFiles_T01_UploadFiles

VB_STO_SMARTLogical_UploadMultipleFiles_T02_DeleteUploadFiles

Physical Attachments

VB_STO_SMARTPhysical_Attachment_T01_GetAttachmentValue

VB_STO_SMARTPhysical_Attachment_T02_DownloadAttachment

VB_STO_SMARTPhysical_Attachment_T03_AddAttachment

VB_STO_SMARTPhysical_Attachment_T04_RenameAttachment

VB_STO_SMARTPhysical_Attachment_T05_DeleteAttachment

Upload Multiple

Files

VB_STO_SMARTPhysical_UploadMultipleFiles_T01_UploadFiles

VB_STO_SMARTPhysical_UploadMultipleFiles_T02_DeleteUploadFiles

Test Lab

Expand Create / Delete

VB_TEL_Expand_CD_AddTestTo_TestSet

VB_TEL_Expand_CD_Create_TestSet

VB_TEL_Expand_CD_Delete_TestSet

VB_TEL_Expand_CD_Expand_TestSet_Folder

VB_TEL_Expand_CD_Get_Runs

VB_TEL_Expand_CD_Get_TestInstance_List

VB_TEL_Expand_CD_Get_TestSets

Run Manual Test

VB_TEL_RunManualTest_T02_BeginRun

VB_TEL_RunManualTest_T03_Select_Next_Step

VB_TEL_RunManualTest_T04_EndRun

Test Plan

Create / Delete

VB_TEP_CreateDeleteTest_T01_CreateManualTest

VB_TEP_CreateDeleteTest_T02_CreateStep

VB_TEP_CreateDeleteTest_T03_DeleteTest

Expand Subject

VB_TEP_ExpandSubject_T01_ExpandSubject

Update Test

VB_TEP_UpdateTest_T01_FindTest

VB_TEP_UpdateTest_T03_GoToDesignStepsTab_MANUAL

VB_TEP_UpdateTest_T03_GoToDesignStepsTab_QUICKTEST_TEST

VB_TEP_UpdateTest_T04_LockUpdateDesStep_MANUAL

VB_TEP_UpdateTest_T04_LockUpdateDesStep_QUICKTEST_TEST

VB_TEP_UpdateTest_T05_PostUnlockDesStep_MANUAL

VB_TEP_UpdateTest_T05_PostUnlockDesStep_QUICKTEST_TEST


2.3. Supporting Mechanisms

2.3.1. Run-Time Settings • Run Logic - Run Logic settings should match your scenario goals.

• Pacing - Change pacing settings according to the workload that should be

performed during the load test.

• Log - To be able to investigate transaction failures during the load test, the log

setting should be enabled. Selecting Send messages only when an error occurs

with all Extended Log enabled, will provide enough information for the

investigation of transaction failures, and avoid unnecessary overload on the

Load Generator machines. It is recommended to increase the size of the log

cache.

Think Time – Change Think Time settings according to the workload that should

be performed during the load test.

Additional Attributes – Command line parameters for scripts can be added here as

shown in the figure below:


Miscellaneous – It is recommended to use the settings specified in the figure

below for all scripts:

2.3.2. Security • Client Authentication

Each request issued by WebGate (client side) is accompanied by an authentication

code (sent via an HTTP header). The code is sent in X-TD-ID header. The server

also computes an authentication code for the request, and checks to see if they

match. If they do not match, or if the client did not send the authentication code at

all, the server rejects the request (using HTTP 403 "Forbidden" code). There is an

option to disable this comparison (but not the calculation) on the server side, to

prevent breaking the LR HTTP scripts while still checking the performance impact

of this feature.

Solution

HP ALM 12.00 has a wrapper program that replaces the run.bat file from JBoss.

To disable http.authentication:

1) Navigate to C:\ProgramData\HP\ALM\wrapper\

2) Add the following line to wrapper.conf:

wrapper.java.additional.50=-Dcom.mercury.td.http.authentication=false

The argument number used should not be the same as a number already in use for

uncommented arguments. You can use a commented argument number.

3) Run HPALM.bat wrapper.exe to start ALM as a process.


2.4. Scenario The table below describes the setup of the basic scenario supplied with the kit:

Module Script Users

Pacing

Events in hour From Interval

To Interval

Average

Defects

vbs_def_create_delete 6 162 198 180 120

1695

vbs_def_filters 6 52 92 72 300

vbs_def_filtersmultival 6 52 92 72 300

vbs_def_groupgrid 6 124 164 144 150

vbs_def_memo_search 6 120 168 144 150

vbs_def_modify_defect 6 26 46 36 600

vbs_def_link 2 76 116 96 75

Release vbs_rel_expand_folder 2 60 90 75 96 96

Global WEB_loginout 22 140 180 160 495

3251 WEB_add_conc_user 850 1080 1140 1110 2756

Requirements

vbs_req_cover_analysis 2 52 92 72 100

1082

vbs_req_create_delete 2 62 82 72 100

vbs_req_filter_hierarchy 2 Fixed 18 400

vbs_req_expand_tree 2 78 96 87 82

vbs_req_update 2 Fixed 18 400

Test Lab vbs_tel_runmanual_test 19 265 295 280 244

584 vbs_tel_expand_create_delete 17 150 210 180 340

Test Plan

vbs_tep_create_delete 10 300 420 360 100

1000 vbs_tep_expand_subject 10 40 60 50 720

vbs_tep_update_test 10 180 220 200 180

Operations with Files

vbs_sto_down 3 256 384 320 33

144

vbs_sto_upload_physical 1 260 360 310 11

vbs_sto_upload_logical 3 260 360 310 34

vbs_sto_attachment_physical 1 170 260 215 16

vbs_sto_attachment_logical 3 170 260 215 50

Total 999 7852


3. Kit Installation

3.1. Database LoadRunner performance testing scripts for ALM are developed to run only on projects

based on the HP PCoE MASTER DB.

The role of the MASTER DB is to supply data:

- As volume for load purpose.

- Correlated with LoadRunner scripts described in the document.

- As users for the testing, that will be added to Site Admin. (Note that another 3000 users

will be added.)

Creating the MASTER DB requires a user in the DB with DBA permissions.

3.1.1. Oracle 11g Filename: MASTERDB_ORA11G_QC12.DMP

In order to restore this schema, perform the following steps:

1. Create QCDATA Tablespace

2. Create a directory object in Oracle:

CREATE OR REPLACE DIRECTORY <directory_name> as '<file_path>'

3. Import the dump file:

impdp <login>/<password>@<SID> parallel=4 DIRECTORY=<directory_name>

dumpfile=MASTERDB_ORA11G_QC12.DMP logfile=impdp_QC_MDB.log

remap_schema= MASTERDB_ORA11G_QC12:<new_schema_name>

4. Alter User with password:

Alter User <new_schema_name> identified by tdtdtd

3.1.2 MS SQL 2008 & 2008 R2 Filename: MASTERDB_MSSQL2008_QC12.bak

In order to restore MS SQL database backup, you should use MS Enterprise

Manager or run the command line:

RESTORE DATABASE <new_database_name> FROM DISK='<file_path>\

MASTERDB_MSSQL2008_QC12.bak' WITH RECOVERY, REPLACE, MOVE

'default_qc90_sql_new_db' TO '<sql_data_path>\<new_datafile_name>.mdf',

MOVE 'default_qc90_sql_new_db_log' TO '< sql_data_path

>\<new_logfile_name>.log', MOVE 'ftrow_QCFTCAT' TO

'<sql_data_path>\<new_indexfile_name>'

After the process is complete you will need to add the password to the User as

follows:

exec sp_change_users_login 'Update_one','td','td'

Update Statistics:

From MS Enterprise Manager, select the DB with which you want to work, and run

exec sp_updatestats on the selected database.


Important:

o After import, Update Statistics is required for all tables, in both Oracle and SQL

Server.

o If the TextSearch feature is in use, it must be enabled in ALM Site Admin and in

the Database setup. This Business Process is simulated by the script

VBS_DEF_Memo_Search.

If this feature is not used, remove this group (script) from the scenario.

o Warning: Performing Enable\Rebuilt TextSearch, under project details in ALM

Site Admin, may take a long time depending on the database configuration.

o Data may become corrupted after many loads. To avoid erroneous transactions,

perform drop and import to all Master DB schemas.

o The DB local settings are ANSI.

3.2. Scripts

3.2.1. Scripts Package Installation Unpack scripts to a network shared drive that is available from LoadRunner

Controller and Load Generators/Injectors machines. Do not change the folders

hierarchy.

The scripts package has a hierarchical structure. All scripts have references to

external libraries or headers. The paths must be updated, specifying the full network

path to these files.

3.2.1.1. WEB_Add_Conc_User & WEB_LOGINOUT

Script must be updated with the full library path.

Important Note: Use double backslash when defining the path (where needed.)

In Globals.h:

#include "<Replace Path>\Include\FrecParcer.h"

#include "<Replace Path>\Include\Initialize_QC_with_authentication.h"

#include "<Replace Path>\Include\Utils.h"

In Initialize_QC.h:

This file must also be updated with the full library path:

#define "<Replace path>\\lib\\FreqParser.dll"

#define "<Replace path>\\lib\\MultyThreadPingToQC.dll"

#include "<Replace Path>\Include\Utils.h"


3.2.2. Command line parameters All scripts within the ALM Benchmark Kit are built to support configurations via

the command line, meaning all parameters can and should be defined in the

scenario’s command line. This can be done in LoadRunner by setting additional

parameters as described in point 2.3.1, and in PC ALM or Controller in the format

“-<ParameterName1> <Value2> -<ParameterName2> <Value2>…”as shown in the

figure below.

There is no need to change the parameters within the scripts.

This list contains all parameters that are supported by all scripts in the package:


Group Parameter Description Values Default value

Server Details

ServerName The name of ALM web/app server. May Include port (e.g myserver:8080).

Text qcserver

Login Details

UserName UserName to be used to login to QC. If not specified, a user will be selected automatically.

Text admin

Password Password to be used to login to QC. Text <blank>

UserFirst Automatically generates the username to be used for login. The auto-generated username will be in the following format: {UserPrefix}{UserIndex}{UserSuffix} Example (default values used): admin512

Integer 1

UserTotal Integer 1000

UserPrefix Text admin

UserSuffix Text <blank>

Server Selection

Domain Domain name to be selected during login. Text DEFAULT

ProjectName Project name to be selected during login. Specifying this setting will ignore the rest “Project…” parameters

Text MASTERDB1

ProjectMethod

Accent: Emulate users working on 3 (ProjectMain) main projects and 100 (ProjectTotal) small ones. 75% of the Vusers log into the 3 main projects (25% to each one) Uniform: Selects randomly one of ProjectTotal projects.

Accent Uniform

Accent

ProjectPrefix <ProjectPrefix><ProjectIndex><ProjectSuffix>

Text MASTERDB

ProjectSuffix Text <blank>

ProjectFirst The minimal project index to be used for project name generation.

Integer 1

ProjectMain Number of main projects (Accent method). Integer 3

ProjectTotal Total number of projects that can be used in project name generation.

Integer 100

Specific Scripts Parameters

Parameter Scripts Description Default Value

EnableDelete VB_STO_Attachment VB_STO_Upload_local

Should delete uploaded files from ALM after upload Values: TRUE / FALSE

Y

SmartType Values: logical / physical logical

FileType Values: single / multi multi

Build Number WEB_Add_Conc_User WEB_LOGINOUT

You need to enter the build number you are using


3.2.3. Connectivity Add-in For OTA support, this Add-in must also be installed on the injector and should match the

Tested ALM version:

Click HP ALM Connectivity:

Download and install the Add-in:


3.3. ALM Server

3.3.1. Site Admin Parameters Open ALM Site Administration, select the Site Param tab and add the following

parameters:

Parameter Value

FORCE_UPLOAD_ALL_FILES Y

DISABLE_EXTENDED_STORAGE N

3.4. Supporting Mechanisms

3.4.1. Smart Repository over File System ALM 12 uses a Smart Repository, which keeps all the files indexed in the Database.

To create the physical file repository:

1. Extract the file “FullRepositorySmart_QC12.exe” to “<qc_repository_path>\qc\<project_name>” according to the number of

projects you have created.

2. Extract the RAR files inside each “<qc_repository_path>\qc\<project_name>\ProjRep\000\000\000”

3. Set each Master DB project repository path to appropriate folder.

3.4.2. Upload Repository Files Upload scripts uses a collection of custom files.

The “Upload_Repository.exe” file contains the folder “Upload_Repository”. Extract

the file in the injector machines to this location: “C:\” If a different location is used,

the script must be altered accordingly.

3.4.3. Automatic Project Selection Note: The section below relates to the Initialize_QC.h file.

LoadRunner performance testing scripts provide two algorithms for automatic

project selections – Accent and Uniform.

You can change the algorithm to provide a specific emulation of users’ behavior

relevant for your system, by modifying the Select_Project function that is placed in

<Package_Root_Directory>Include\Initialize_QC.h


Selection Algorithms:

o Accent Algorithm – By default, the accent algorithm emulates users working

on three (ProjectMain) main projects and 97 other ones (100 in total -

ProjectTotal). 75% of the Vusers log into the three main projects (25% to each

one), while Vusers from the remaining 25% randomly select one of the

remaining 97 projects. The amount of projects can be changed by sending the

relevant parameter via the command line.

o Uniform Algorithm – The uniform method randomly selects one of the

ProjectTotal projects. The Name of project generated using these algorithms

will be in the following format:

<ProjectPrefix><ProjectIndex><ProjectSuffix>

Command line parameters:

o ProjectName – Specify the name of the project to be selected. Specifying this

parameter will disable the automatic project selection algorithms.

o ProjectMethod – Project selection method definition (Accent / Uniform).

o ProjectPrefix – Prefix to be used in project name automatic aggregation

according to selected algorithm.

o ProjectSuffix – Suffix to be used in project name automatic aggregation

according to selected algorithm.

o ProjectFirst – Index of first project to be selected.

o ProjectsMain – Number of main projects (accent project selection method).

o ProjectTotal – Number of projects that can be selected during the project

name automatic aggregation.


3.4.4. Ping Mechanism When a user signs into ALM, the client application creates an additional thread.

This periodically sends a Ping request to the server in order to report that the client

is online, and the session should be kept open.

Since the Ping request should be sent independently of current client activity (by

default - every 290 seconds), it cannot be simulated by adding it to the script. In

order to provide the best client activity emulation, an external DLL has been

developed. At the initialization phase, all virtual users load up the

“MultyThreadPingToQC.dll” by calling the load_dll function. After completing the

login, Vusers call StartPingToServer method in order to create the additional thread

to Ping the server.

This mechanism does not require any additional configuration. All you need is to

verify that the path to this DLL is correct and accessible for all scripts.

If Vusers fail to load the DLL, validate that the path to the

MultyThreadPingToQC.dll file is correct. The path to PING.dll is placed at the

beginning of <Package_Root_Directory>Include\Initialize_QC.h file.


3.4.5. FReq Parcer Due to the changes in FREC format since QC 9.0, which require online

recalculation of the length of fields, the LoadRunner performance scripts for ALM

12.00 use an external library that automatically parses the FREC that should be sent

to the server, recalculating the length of fields.

This mechanism does not require any additional configuration. All you need is to

verify that the path to this DLL is correct and accessible for all scripts.

If Vusers fail to load the DLL, validate that the path to the

MultyThreadPingToQC.dll file is correct. The path to FrecParser.dll is placed at the

beginning of <Package_Root_Directory>Include\Initialize_QC.h file.

Documents

HP Application Lifecycle Management 12.00 Benchmark Kit ...community.softwaregrp.com/dcvta86296/attachments/dcvta86296/sws... · based on HTTP protocol and OTA API. Therefore, they