Booster Monitor and Configuration Settings

When you first launch Booster Monitor, it will attempt to connect to the Booster at the default address of with the assumption that you are running the monitor on the system you installed it on. You can change that address to any valid IP address or FQDN of a Booster you have installed.

The default password will be "filewave".

Once you have connected with your Booster, you will see its Status Monitor window:

The status window lets you see the current settings and cache of the Booster.

You can set the Booster preferences to choose how the Booster can be reached, how it works with other Boosters, the main FileWave Server, and how it handles network traffic.

Booster Prefs

  • Booster Name – this is an identifier for you to distinguish a Booster in the FileWave Admin GUI. It does not have to be the hostname of the Booster, but would be a good practice to follow.
  • Location – this is a text field to help someone know the physical location of the Booster (it shows in the Booster view of FileWave
  • Booster Port – by default, this is 20013; but you can change it to any valid TCP port that won't interfere with active connections on your network. This port should also be open in the network firewall for external connections.
  • Booster Publish Port – this setting provides the port for the remote control VNC relay. See Chapter 4 (Clients) for more information on the VNC relay and its functionality. Port 20003 is the default and should not be changed. Booster Publish Port defines which port this Booster publishes messages on and should be consistent with subscription ports for all Boosters and clients that connect to this Booster.
  • Password / Confirmation – the default password is "filewave"
  • Number of Threads – this is the number of threads spawned by the fwBooster process. With FileWave 11, this value is no longer user-adjustable. The value will be automatically adjusted depending upon the hardware resources available to the fwBooster process.
  • Debug Level – you can change this value if you are troubleshooting an issue with FileWave Support. The higher the level, the more log files generated.
  • Delete Unused Filesets – this setting will cause the Booster to delete any Filesets that have been deleted at the main FileWave Server. If you leave this setting unchecked, then the Booster will keep every Fileset it has cached. This can come in handy as an ad-hoc backup of all your Filesets for recovery purposes.
  • Fileset Validation interval – this value determines how often the Booster checks to make sure it has every Fileset that the clients have requested and that the versions of the Filesets are correct and up-to-date.
  • Client Download Speed Limit – you can use this setting to throttle the bandwidth that the Booster will utilize with a given client. A word of caution though, if the Booster is feeding an IVS, you probably don't want to limit the download speed between the Booster and the IVS, as images can be quite large and take a lot of time to copy when unrestricted.
  • Use SSL For Loader Connections – this value will alter the port used by the Booster to 20014 and encrypt the traffic Note: You won't see the Booster Port value change, but the Booster will be on port 20014

Booster Server Prefs

These settings are where you build your distribution "tree" by assigning where this Booster connects. This specifies the order in which connection attempts will be made. The best way to set this up is to follow these guidelines:

  • Set Server 1 to be the next Booster upstream from your Booster. This may be the main FileWave Server or another Booster upstream from this one.
  • Set the other servers to be Boosters in the same general area or location as this Booster or ones that are upstream from each other (e.g., #2 would be upstream from #1). Do not set these to the other Boosters in a DNS "round-robin" configuration - that would leave these Boosters all asking each other for Filesets none of them may have.
  • If you have not entered the FileWave Server as server 1, set the last value in the table to the main server. This guarantees that if all the other Boosters never respond, the main FileWave Server will be contacted.
  • The Subscriptions Port is used for the Booster to contact the FileWave Server to pass along the VNC relay communications. Only the first Booster in the chain provides this service. If the first entry is the actual FileWave Server, the port is 20005. If the first entry is the primary Booster in the chain, then the port is 20003.

Configuring Clients to use Boosters for Server Messages

To activate the server message routing functionality introduced with FileWave 11, you must enable it using either the option on the Booster page of Superprefs or Client Preferences.

Boosters view

On the above screenshot you can see new options in the Boosters tab in Boosters view:

"Configure Discovery" button opens the Discovery Configuration dialog. Note: Network Discovery is covered in depth in Chapter 12
"Start Discovery Scan" button immediately starts a scan using the existing configuration, if a scanner configuration is currently disabled then the configured will be enabled at this point.
"Stop Discovery Scan" button immediately stops the current scan, if the configuration is enabled then it's also disabled.
"Device Name" column contains the name of the Booster. This is configured in Booster's preferences.
"Booster Status" column indicates green/orange/red icon based on last check-in time:

  • green = OK (check-in within the last 5 minutes and everything is fine)
  • orange = Warning / Requires Attention 
  • red = Danger (check-in more than 10 minutes ago and booster is offline)

"Next Scan Start Time" column indicates the start time of the next scan
"Last Discovery Scan Status" column shows the various statuses of a discovery scan and the discovery application (success, network scanner fail, network scanner crash, discovery application crash, discovery stop, generic failure).
"Requests per Second" column indicates the number of Booster requests per second within the last 15 minutes. Additionally, Booster statistics are sent by the Booster every 15 minutes at fixed times e.g. 0:00, 0:15, 0:30, 0:45.
"Booster Overload" column indicates if there are any clients' requests that couldn't be served by Booster. This doesn't necessarily mean the Booster is failing; it simply implies that the client has been told to retry later.
"Location" column contains location configured in Booster's preferences.

View modes

The Boosters view offers two primary view modes: the Cards view (which requires OpenGL on the administrator machine running FileWave Admin) and the Details view. These modes operate independently. Double-clicking on a Booster in either view opens the Booster Monitor for that particular Booster.

In the Cards view, each Booster is displayed as a card, with just an overview of its status. Besides using the contextual menu, on the top-right corner of each card there are two gears that when clicked open the same menu.
When the Booster Details tab is clicked on, the Boosters tab switches to the Details view. In this mode, a list with many columns is displayed instead: