Install and configure a Load Generator

For information on how to install and configure a Load Generator to connect to NeoLoad Web, see Platform set-up for runtime.

Once you've connected a Load Generator to NeoLoad Web, only NeoLoad Web can use it. If you want to disable this security measure, edit the [Network]agent.accept.only=ALL key in the <Load Generator>/conf/agent.properties file.

Configure a Load Generator Agent

The access parameters to NeoLoad Web can be configured by launching the Load Generator Agent ".exe" file from the NeoLoad "bin" folder. A right-click on the Agent allows selecting the NeoLoad Web settings option.

NLW-LGAgentSettings

The Deployment section enables you to select how NeoLoad Web is deployed in your infrastructure. NeoLoad Web can be deployed either:

  • On SaaS, or,

  • On-premise

When NeoLoad Web is deployed on-premise, you need to enter the URL that will enable the Load Generator Agent to connect with NeoLoad Web. The port required is the NeoLoad connection port.

By default, the URL is "http://nlweb.<your company>.com:8080". To know the URL used in your deployment, contact your NeoLoad Web IT Administrator. For more information, see the Initial setup.

Please note:

  • In command line, the -nlwebAPIURL argument specifies the URL of the NeoLoad API in order to connect with NeoLoad Web when it is deployed on-premise. This argument overrides any corresponding environment variable previously defined. For more information, see List of arguments.

  • The NLWEB_API_URL environment variable allows specifying the URL of the NeoLoad API in order to connect with NeoLoad Web when it is deployed on-premise. It can be used as follows: NLWEB_API_URL={nlweb-onpremise-apiurl:port}

The Authentication section enables you to authenticate to NeoLoad Web using a token.

Token-based authentication secures an application based on access tokens that you can generate to enable other users to log in to the application. This way, you can give access to partners without exposing your password. You can change your password without updating your access tokens and delete the tokens you do not need any longer without having to change your password.

Access token: The access token generated in NeoLoad Web can be pasted in this field.

In command line, the -nlwebToken argument activates the connection with NeoLoad Web and declares an access token. This argument overrides any corresponding environment variable previously defined. For more information, see List of arguments.

Hostname: The field must be populated with the name of the machine where the Load Generator Agent is located.

The LG_HOST environment variable allows overriding the IP address of the host where the Load Generator can be reached. It can be used as follows: LG_HOST={lg.mycompany}.

Port: The field must be populated with the port number to access the Load Generator Agent.

The LG_PORT environment variable allows overriding the port on the host where the Load Generator G can be reached. It can be used as follows: LG_PORT={7100}.

Zone identifier: To associate a Load Generator Agent with a Zone you have created, the Zone ID must be copied and pasted in this field. For more information, see Manage Zones. Please note:

  • In command line, the -nlwebZoneId argument allows overriding the Zone. This argument overrides any corresponding environment variable previously defined. For more information, see List of arguments.

  • The ZONE environment variable allows specifying the Load Generator Zone to use. It can be used as follows: ZONE={zone-id}.

The Proxy section enables to select the proxy you want to use to connect to NeoLoad Web in HTTP or HTTPS mode. For more information, see Add a proxy. Please note:

  • In In command line, the -nlwebProxy argument allows connecting NeoLoad Web by using a proxy. This argument overrides any corresponding environment variable previously defined. For more information, see List of arguments.

  • The NLWEB_PROXY environment variable allows connecting NeoLoad Web by using a proxy. It can be used as follows: NLWEB_PROXY=http://{login:password}@{myproxy}.

In the Check connection section, use the Test button to check the connection (server configuration, authentication information, proxy settings if any, repository if any).

Tip: For more information about configuring a Load Generator Agent when using Docker, see the Dockerhub documentation.

Define a Load Generator Agent as a service

Both Controller and Load Generator Agents can either be installed as services or started in an ad hoc manner - running the executable when and as needed. The former approach (As an Administrator) is consistent with a long term and durable approach because Agents run as services are started once and for all and will automatically be restarted each time the machine reboots. The latter (For a specific user), although less intrusive and easier to accomplish, makes sense when targeting an occasional use only.

As an Administrator

The Load Generator Agent can be defined as a Windows service i.e. it can be launched and stopped each time Windows starts and stops. For more information, see the procedure below.

For a specific user

The Load Generator Agent can be defined as a service for a specific user.