For LoadRunner Professional, load generator, MI Listener, and monitor over firewall:

<LoadRunner Professional root>\bin\lr_agent_settings.exe

Note: You must have write permissions to the LoadRunner Professional installation folder.

For a load generator:

<LG path>\bin\lr_agent_settings

Guidelines for Linux machines:

• You must have administrator privileges to run this on a Linux machine.

• In Amazon cloud environments (AWS), you need to set the M_LROOT environment variable, as shown in the following example:

  ~$ sudo M_LROOT=/opt/OT/OT_LoadGenerator /opt/OT/OT_LoadGenerator/bin/lr_agent_settings -check_client_cert 0

The names of the hosts to update with the new settings.

To access the local machine, specify localhost or 127.0.0.1.

For multiple machines, repeat the command: For example,

-remote_host host1 - remote_host host2.

The name of a file containing the host names or IP addresses. Separate multiple host names with a line break. For hosts over a firewall, specify a port. For example,

myserver1

myserver2:my_ofw_unix

myserver2:my_ofw_1

The load generator m_agent listening port.

Default: 54345

The load generator al_agent listening port.

Default: 54245

MIL listening port from Controller. This option is not available on Linux.

Default: 50500

MIL listening port from load generator over firewall.

If you change this port value, you should also change the port for the load generator over firewall machine using -mil_port. This option is not available on Linux.

Default: 443

Indicates whether to communicate over a firewall.

Changes the MI listener name or IP address from the side of the load generator over a firewall.

Changes the port for the MI Listener from the side of the load generator over a firewall.

Default: 443

Changes the host symbol (or local machine key) for load generator over a firewall, to establish a unique connection from behind the firewall.

Changes the MI Listener name and the local machine key in one string separated by a colon, ":".

Changes the user name and password with which to connect to the MI Listener machine, and the domain for the MI Listener machine (required only if NTLM is used).

Changes the sampling interval in seconds—the time the agent waits before retrying to connect to the MI Listener machine.

The over-firewall load generator machine polls the MI Listener regularly to see if any Controller needs to use it for a test run. If no request is found, it closes the connection and waits this specified timeout period, before polling it again.

Changes the connection type: HTTP or TCP.

Changes the name and port of proxy server when using HTTP connection.

Changes the proxy name and port in one string separated by a colon, ":",

Changes the user name and password with which to connect to the proxy server.

Changes the flag to connect using the TLS (formally SSL) protocol.

Use 0 to allow both TLS (SSL) and non-TLS connections.

Use 1 to enforce TLS (SSL) connections only and check if the client certificate is trusted by the CA installed on the agent machine.

Note: When monitoring over firewall, set this flag to 1 on the server machine. For guidelines on determining which machine is considered the server, see Two-way TLS (SSL) authentication.

Indicates how to authenticate TLS (SSL) certificates that are sent by the server.

None. Does not authenticate the certificate.

Medium. Verifies that the server certificate is signed by a trusted Certification Authority.

High. Verifies that the sender IP matches the certificate information.

Installs a CA certificate locally. It overwrites the dat\cert\verify\cacert.cer file, but does not affect any configuration file.

Note: You need to generate a CA certificate before installing it. To generate the CA certificate, run gen_ca_cert -common_name <your_selected_common_name, e.g. LoadRunner > from the bin folder.

Two files, cacert.cer and capvk.cer. are generated in the current directory, for the CA certificate and private key.

Store capvk.cer securely in a designated folder.

Install cacert.cer as a CA certificate on all of your LR/LoadRunner Enterprise installations.

Indicates the private key file for the CA certificate.

If you do not specify a private key, you cannot generate new TLS (SSL) certificates using this CA certificate.

Installs authentication certificate locally. It overwrites the dat\cert\verify\cacert.cer file, but does not affect any configuration file.

Note: This step assumes you already generated a TLS certificate ahead of time. To generate a TLS certificate, run the following from the bin folder:

gen_cert -common_name <your_selected_common_name, e.g. LoadRunner> -CA_cert_file_name <CA_cert_file_full_path> -CA_pk_file_name <CA_private_key_file_full_path>.

-generate_new_cert_file

-CA_private_key_file
_name

Generates a new authentication certificate and installs it in dat\cert\cert.cer.

Note: A CA private key is mandatory to generate a self-signed certificate. The CA certificate will be read from dat\cert\verify\cacert.cer from the current machine.

Sets the matching private key of the TLS (SSL) certificate you installed with gen_ca_cert -common_name (see above). If you generate a TLS certificate using gen_cert or using the -generate_new_cert_file option in this tool, you can skip this step. You only need to do this step if you use a certificate which does not include a private key in the certificate file, such as the openssl tool.

Restarts the magent or alagent. It automatically detects whether it is running as a service or process.

Note: If the agent is running as a process and you want to use the command line to restart it as a service, first use the Agent Configuration Settings dialog box to change between the Process and Service mode for the agent.

Retrieves the value of input parameters listed in a file. The prm file should have the following format:

-mil_name MyHost1 -local_machine_key my_ofw_win -channel_type HTTP -proxy_name www.acme.com -proxy_port 8080.

Note:

• When using the -prm argument in the command line, all other arguments are ignored.
• The parameter file should only contain arguments for changing settings. It should not contain the Remote Update arguments, -remote_host and -remote_file, which are ignored.

The name of the load generator. This name is used to connect to Controller through the Data Hub channel.

Default value: Machine name of the load generator machine.

New shared key value.

Enter the value default to restore the original shared key.

Changes the shared key included with the LoadRunner Professional installation. This key is used for encryption and decryption of passwords and other data required for authentication in certain protocols.

The key must be between 12–64 alphanumeric characters.