Share this page

# Set up an over-firewall deployment

This task describes how to configure the over-firewall system.

1. Prerequisites.

   Make sure you have installed the necessary components as described in the first step of Set up your system over firewalls.

2. Set up your deployment (TCP or TCP over proxy)

   To run Vusers or monitor servers over the firewall, configure your system according to one of the following configurations. Note that these configurations contain a firewall on each LAN. There may also be configurations where there is a firewall for the Over-Firewall LAN only.

   - TCP configuration

     The TCP configuration requires every OpenText Professional Performance Engineering Agent machine behind the customer's firewall to be allowed to open a port in the firewall for outgoing communication.

   - TCP over proxy

     In the TCP over proxy configuration, only one machine (the proxy server) is allowed to open a port in the firewall. Therefore, it is necessary to tunnel all outgoing communications through the proxy server. A proxy server is required to support HTTP tunneling using the CONNECT method.

   Tip: The standalone load generator and standalone monitor over firewall (MOFW SA) cannot be installed on the same machine.

   However, the standalone load generator can be used for monitoring purposes, the same way as the MOFW SA.

   A single machine cannot be used simultaneously for both running Vusers and monitoring.

3. Configure the firewall to allow agent access.

   Modify your firewall settings to enable communication between the machines inside the firewall and machines outside the firewall.

   1. If your system has a TCP configuration:

      The Agent attempts to establish a connection with the MI Listener using port 443, at intervals specified in the Connection Timeout field in the Agent Configuration dialog box.

      To enable this connection, allow an outgoing connection on the firewall for port 443. The agent can then connect to the MI Listener, and the MI Listener can connect back to the agent.

      From this point on, the agent listens to commands from the MI Listener.

   2. If your system has a TCP over proxy configuration:

      The Agent attempts to establish a connection with the MI Listener, using the proxy port specified in the Proxy Port field, and at intervals specified in the Connection Timeout field in the Agent Configuration dialog box. When the connection is established, the proxy server connects to the MI Listener.

      To enable this connection, allow an outgoing connection on the firewall for port 443. The proxy server can then connect to the MI Listener, and the MI Listener can connect back to the agent through the proxy server.

      From this point on, the agent listens to commands from the MI Listener.

   3. If you intend to start the Agent service from the Local System account, you need to grant it permissions:

      1. Add a local user on the AUT machine with the same name and password as the local user on Agent machine.
      2. Add the AUT local user to the Performance Monitor Users group
      3. Restart the Agent process.

      Note: If you do not provide permissions, the monitor graph does not display any data.

4. Configure the MI Listener.

   To enable running Vusers or monitoring over a firewall, you need to install the MI Listener on one or more machines in the same LAN as the Controller outside the firewall. For installation instructions, see Components and applications.

   Note:

   - The Controller installation automatically includes the MI Listener, so you can designate Controller as the MI Listener machine.
   - The MI Listener can only be installed on Windows machines.

   For information on how to configure the MI Listener, see MI Listener Configuration dialog box.

Back to top

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 25.1-25.3 All View Local Help Center View Online Help Center Version: