Tag Archives: LoadRunner installation

License features used by the HP (Former Mercury) Functional Testing Concurrent License Server when working with QuickTest Professional (QTP) or Service Test (ST)

List of license features
The features below are used by the Concurrent License Server and are displayed in the tools that are shipped with it, such as WlmAdmin, Wcommute, or LSdecode: Common/Latest/Most-used features:

* UnifiedFunctionalTesting – Unified Functional Testing (UFT)
Usage: Unified Functional Testing (version 11.5 and above), QuickTest Professional (version 11.00 and above) and Service Test (version 11.00 and above) core products and QuickTest Professional add-ins. * HpFunctionalTesting – HP Functional Testing
Usage: Only for QuickTest Professional (version 9.5 and above) and WinRunner (only 9.2) core products and their add-ins, not working for UFT 11.50 and above!!! * FT-unified – Functional Testing core
Usage: QuickTest Professional (version 6.5 and above) and WinRunner (version 7.6 and above) core products and the core add-ins (Visual Basic, Active X and Web). * FTAddins – Functional Testing add-ins
Usage: WinRunner (version 7.6 and above) and QuickTest Professional (version 6.5 and above) external add-ins that are not shipped with the core product. * QuickTestPro – QuickTest Professional core
Usage: QuickTest Professional (version 6.5 and above) core program and the core add-ins (Visual Basic, Active X and Web). * QTAddins – QuickTest Professional add-in
Usage: QuickTest Professional (version 6.5 and above) external add-ins that are not shipped with the core product. * QTPEssentials – QuickTest Professional Essentials
Usage: Enables only QTP 11 basic features (version 11.00 and above), meaning ActiveX, Visual Basic, Web, Java and .NET add-ins. All other installed add-ins will be disabled as well as UFT check-box. * ServiceTest – Service Test
Usage: Service Test VuGen (10.x and older) and Service Test Visual Test Designer (11.x and newer). Other/Older features:

* WR-core – WinRunner core
Usage: WinRunner (version 7.6 and above) core program and the four add-ins that are shipped with it. * WRAddins – WinRunner add-ins
Usage: WinRunner (version 7.6 and above) external add-ins that are not shipped with the core product. * Java – QuickTest Professional Java add-in
Usage: QuickTest Professional Java add-in version 8.2 and above. * WinForms – QuickTest Professional .Net add-in
Usage: QuickTest Professional .Net add-in version 8.2 and above. * SapGui – QuickTest Professional mySAP.com add-in
Usage: QuickTest Professional mySAP.com add-in version 8.2 and above. * Siebel – QuickTest Professional Siebel add-in
Usage: QuickTest Professional Siebel add-in version 8.01 and above. * TerminalEmulators – QuickTest Professional Terminal Emulator add-in Usage: QuickTest Professional Terminal Emulator add-in version 8.0 and above. * Oracle – QuickTest Professional Oracle add-in
Usage: QuickTest Professional Oracle add-in version 8.2 and above. * PeopleSoft – QuickTest Professional PeopleSoft add-in
Usage: QuickTest Professional PeopleSoft add-in version 8.2 and above. * Stingray – QuickTest Professional Stingray add-in
Usage: QuickTest Professional Stingray add-in version 8.2 and above. * VisualAge – QuickTest Professional VisualAge SmallTalk add-in Usage: QuickTest Professional VisualAge SmallTalk add-in version 8.2 and above.

Advertisements

Install/set up a redundant license server pool

These are the required steps to install redundant licenses:
1. Make sure there is no concurrent license already installed on the license servers (look for the LSERVRC environment variable or for “lservrc” on Windows search, if the file exists, remove any concurrent license keys contained on it or remove the file).
2. Stop the Sentinel RMS service for all the license server machines that will be on the redundant license pool (go to Start > Control Panel > Administrative tools > Services).
3. Use the WRlfTool utility to add the servers (name and IP address) and the redundant license key to the “lservrlf” file (redundant license file). The WRlfTool is located under the “utils” folder on the License Server installation files.
4. Save the lservrlf file under the License Server’s installation path (i.e. C:\Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager Server\WinNT)
5. Copy and paste the lservrlf file into the other license servers on the pool in the same path as saved on the Leader license server (i.e. C:\Program Files\Common Files\SafeNet Sentinel\Sentinel RMS License Manager Server\WinNT).
6. Start the Sentinel RMS service for all the license server machines that will be on the redundant license pool.
7. On the UFT/QTP client machine, create the LSHOST environment variable under the user variables (go to Start > Control Panel > System > Advanced > Environment variables). The value should be the name or IP address of all the license servers on the pool, separated by colon (i.e. lserver01:lserver02:lserver03 ) or semi-colon (i.e. lserver01;lserver02;lserver03 ) depending on the environment.
8. The Redundant License pool should be set now. Launch UFT/QTP to verify it is working fine.
Note: The redundant license servers use the majority rule. This means that a majority (over half) of the redundant license servers must be up and running in order to get a license for UFT/QTP. For example, if there are 3 redundant license servers, at least 2 of them must be up and running. If there are 5 redundant license servers, 3 of them must be up and running to get a license.
For more information about setting up a redundant license server pool, refer to “Setting up the Redundant License Servers” on the license server installation files at\LicenseServer\server\SysAdminHelp\Default.htm

How to set the LSHOST or LSFORCEHOST system variable

Determine which variable to use then set the system variable

On Windows NT
1. Bring up the System Properties dialog:
a. Right-click on “My Computer.”
b. Choose Properties.

OR

a. Go to Start -> Settings -> Control Panel.
b. Double-click on System.

2. Select the Environment tab.
3. Select a variable in the System Variables group.
4. Replace the Variable name with “LSHOST” or “LSFORCEHOST.” 5. Replace the Value with the License Server name or names.

Note:
You can use the name or IP address of the server machine.

6. Click .
7. Click .

On Windows 2000, XP and Vista
1. Bring up the System Properties dialog:
a. Right-click on “My Computer.”
b. Choose Properties.

OR

a. Go to Start -> Settings -> Control Panel.
b. Double-click on System. (i.e. System can be found in the “Classic View” of both Windows XP and Vista). For Windows XP, if you have a list of categories, you can find System in the “Performance and Maintenance” category. For Windows Vista, you can find System in the “System and Maintenance” category and click on the “Advanced system settings” in the left panel.

2. Select the Advanced tab.
3. Click .
4. Click for System Variables.
5. Enter “LSHOST” or “LSFORCEHOST” for the Variable name.
6. Enter the License Server name or names for the Value.

Note:
You can use the name or IP address of the server machine.

7. Click
8. Click

On Windows 95/98/Me
1. Go to Start -> Run.
2. In the Open edit field, type sysedit.
3. Click .
4. Set the LSHOST or LSFORCEHOST variable.

Example:
Set LSHOST=

OR

Set LSFORCEHOST=.

Note:
You can use the name or IP address of the server machine.

5. Save and close the autoexec.bat file.
6. Reboot the machine. This will force the information added to the autoexec.bat file to be entered into the system environment.

When should LSHOST and LSFORCEHOST be defined

Defining the LSHOST and LSFORCEHOST variables
Note:
These variables only need to be defined if WinRunner has trouble locating your License manager server or if you want the specified effect. Define LSHOST:
1. When the client and server are in different domains.
2. If you want the client to use more than one available server, in a specific order.
Define LSHOST to be the server names in the order you would like to search them. Separate the server names with a semicolon (“;”). Note:
When LSHOST is used, WinRunner will first look for a license on the specified servers, in the specified order. If a license is not found there, WinRunner will search your network for one.
Define LSFORCEHOST when you want the client to search the license on only ONE specific server. Define LSFORCEHOST to be the name of that server.

Install / delete a license code with the lslic utility

The lslic utility installs or deletes a license. lslic can be run on supported version of Windows and UNIX. It can be run from the operating system command prompt by an administrative user on a stand-alone, client, or license server computer. It works for both stand-alone and network computers.

Use lslic in the following format:
lslic [option]
Where the option might be:
-a license-code

Adds a license code to the contacted license server without updating the license file. Note: Change is temporary until the license server is restarted.

-f filename

Adds all the license codes in the supplied file to the contacted license server without updating the license file (lservrc). Note: Change is temporary until the license server is restarted.

-A license-code

Adds a license code to the license server’s license file (lservrc) and communicates the change to the contacted license server. Note: Change is permanent

-F filename

Adds all the license codes in the supplied file to the license server’s license file (lservrc) and communicates the new information to the contacted license server. Note: Change is permanent

-df feature_name feature_version[capacity | NOLIMIT]

License(s) with specified feature name and version are deleted from the license server memory. Note: Change is temporary until the license server is restarted.

-removeall

Removes all license codes (redundant and non-redundant) from the license server but does not delete them form the license file. Note: Change is temporary until the license server is restarted.

-removeallcap [feature version]

Removes capacity for specific license from the license server but does not delete them from the license file. Note: Change is temporary until the license server is restarted.

-DL feature-name
feature version
license hash
[capacity | NOLIMIT]

License with specified feature_name, version and license hash is deleted from the license server memory and file. Note: Change is permanent Tip: The license hash can be obtained using the lsmon utility.

-p feature-name
feature version
license hash
precedence

Sets the precedence of a trial license. The license hash can be obtained from WlmAdmin or lsmon.

-p

Pauses the utility and then shows the output in another console. Only for Windows Vista, 7, and Server 2008.

Tips on Using lslic

* If you do not include necessary information on the command line, lslic will ask for the missing information.

* You can use the LSFORCEHOST environment variable to add/delete licenses to a particular license server.

* When you enter a license code, if you are entering an encrypted license code, type only the characters before the # symbol.

* lslic can add or delete licenses without stopping and restarting the license server, but the change is only temporary unless you use an option that makes the change to the license file.

* To use lslic to modify a license file or redundant license file for a license server on a remote computer, use the LSFORCEHOST environment variable to point your computer to the computer containing that license server.

* If you are using lslic to modify a license file on a remote computer, you must have write-access to that computer.

* License deletion is not supported for the following licenses:

* Checked out commuter license tokens residing on the local computers

* Grace licenses being used on the non-networked computers

* Licenses in the redundant license files (lservrlf)
For further information, please consult Sentinel RMS Kit System Administrator’s Help that can be found in \LicenseServer\server\SysAdminHelp\Default.htm.

Create group reservations for concurrent licenses

To reserve a limited amount of licenses for use by different groups of users.

Instructions:

1. Create a plan which machines/users are restricted to using (or from using) particular amount of licenses and/or its features

2. Create the Reservation file (lsreserv) based on step 1 using the Wlsgrmgr.exe (see more on below section)

(Recommended) Save created file on the same directory where the process used by the License Server service.

3. If file is not saved on above location, then create a Windows System Environment Variable called “LSRESERV”, pointing to where lsreserv file is located (step 3)

Note: If the variable is not set, the local directory is searched for the “lsreserv” file. If none of the above suggestions are set, reservation feature is not used.

4. Restart the License Server service

5. If above doesn’t reflect the use of file, then restart/reboot machine
Note: To disable/turn-off the reservation file, just rename LSRESERV file mentioned on steps 2,3, and restart License Server.

General Guidelines:

1. The name of the file containing the group reservations should be lsreserv, and it should be located in the installation directory for the license server.

2. Adding, modifying, or deleting the lsreserv file must be followed by restarting the SentinelLM service for the changes to take effect.

3. User names in the lsreserv file are case-sensitive.

4. User names can appear in more than one group. The license manager searches downwards through the lsreserv file, using the first group it finds with that user in it.

5. Adding, modifying, or deleting the LSRESERV system environmental variable requires a server reboot for the changes to take effect. The value of this system environmental variable should be the full path (including the file name) to the lsreserv file, and it allows the reservations file to be placed somewhere other than the installation directory.

Setting Group Reservations
Group reservations give you the ability to exercise local administrative controls by associating a series of groups with each feature and reserving for each group a pool containing a certain number of licenses. Any licenses not specifically reserved fall into the general pool.

Including/Excluding Users
Selected users can be allowed to run certain applications or can be prevented from accessing applications. This can be used as an additional security measure.

Including/Excluding Computers
Certain computers can also be allowed to run or prevented from running applications. This can help to balance application usage when you want to prevent users from running applications on heavily loaded computers or file servers.

Configuring the Reservation File
A group specification consists of:

1. The name of the feature for which the reservation applies.

Important: If you use FT-Unified and FTAddIns license features, please ensure, that you use first FT-Unified and then FTAddins. Otherwise the reservation for the FT-Unified feature will seemingly be ignored. This seems to be either a defect or an internal interpretation error.

2. The name of the group

3. The number of licenses reserved for that group

4. The login names of users or host IDs of computers that belong to that group

The groups must be mutually exclusive. Different groups for the same feature should not have common users or computers. The number of licenses reserved for a feature cannot exceed the number of concurrent copies specified in the license code for that feature.

Background functionality

1. When the License Server receives a request, it checks whether the user making the request belongs to a group. If so, and licenses are available for that group, the License Server will issue the license(s) and remove them from that group’s pool. Otherwise, requests will be serviced with licenses from the general pool until no licenses are available.

2. At start up, the License Server consults the environment variable, LSRESERV, for the path and file name of the reservation file. If the variable is not set, the local directory is searched for the file, lsreserv. If no file is found, the License Server assumes that no reservations exist. Reservation File (lsreserv) Format
Group reservations should be entered according to the following format, with one group per line:

feature_name,ver:group_name:num_of_licenses:{ user_name | computer }

One or more of user_name and/or computer may be specified, but at least one value must be specified in the last field. Version number is optional. If no version number is specified, only the feature name is used.

The characters $ and ! have special meaning: $ indicates the computer name, and ! indicates a logical NOT.

For example, two users, one computer in group 1:

stars:group1:2:tom bryant $athena

One user, one computer in group 2:

stars:group2:1:doug $0x4f3c5801

One computer to be excluded from dots, two licenses to be reserved for jill:

dots:group1:2:!$0x592ae8b0 jill

In these examples, the two groups denoted as group1 are distinct because they specify different feature names.

The following apply to groups:

* A maximum of 256 groups with 256 members (user names or computer IDs) each are supported. Versions of the license server greater than, or equal to, 8.0.5 support 1024 members in a group.

* Groups must be mutually exclusive.

* Different groups for the same feature should not have common users of computers.

* Group names and member names cannot exceed 64 characters each.

* The number of licenses reserved for a feature cannot exceed the number of concurrent copies specified in the license code for that feature.

* If you want to exclude all members of a group from using license tokens for a feature, you can specify 0 tokens.

* If the number of license tokens reserved is greater than the number of concurrent copies specified for the feature in the license code, the number of tokens specified in the license code will be used.

* The group reservation assumes the priority as per the information available in the group reservation file.

* The License Server user guide(index.html) can be found in \LicenseServer\server\SysAdminHelp. In this guide “Setting Group Reservations” directory has detailed information on how to setup reservation to users or groups.

An invalid link on the topic “How to Enable the UFT Agent for Google Chrome” in “HP Unified Functional Testi ng Add-ins Guide”

In “HP Unified Functional Testing Add-ins Guide”, there is a invalid link on the topic “How to Enable the UFT Agent for Google Chrome”.
In UFT12.01 release, the document on the topic “How to Enable the UFT Agent for Google Chrome” include one incorrect link.

The error can be found in “HP Unified Functional Testing Add-ins Guide” -> “Part 18 Web Add-in” -> “Chapter 33 Web Add-in” – Testing and Configuration” -> “Tasks” -> “How to Enable the HP Unified Functional Testing Agent Chrome Extension” (on Page 534 of “HP Unified Functional Testing Add-ins Guide.pdf”, English version.) The document can be found under \help

On this page, the link for manually install and enable the extension in web store is: https://chrome.google.com/webstore/detail/kohokhibioddenbhekdbbdbmcmbeeeih , which is incorrect

The correct link should be: https://chrome.google.com/webstore/detail/jjkpkaoeaicepkfjgeeopfcfpdgblbdc