Intermapper and Intermapper Flows do not need to run on the same server. In fact, this may be necessary when Intermapper Flows is handling a lot of flow data. You can leave the Intermapper server running on its current hardware and use a higher performance system for the NetFlow analysis.
The two servers communicate through a TCP connection. By default, they connect through localhost, but this can be changed by modifying two configuration files. You need to do the following:
# Automatically generated configuration file
# (C) COPYRIGHT HELP SYSTEMS, LLC 2013
# WARNING: this file might get overwritten by the application!
# Manual changes are accepted based on your license agreement.
# If you want to save a copy (including your comments), please
# make a backup copy of your modified configuration file
databasepath C:\ProgramData\Intermapper\Intermapper Settings\Flows\SESSIONDB
logfile C:\ProgramData\Intermapper\Intermapper Settings\Intermapper Logs\flows.log
user HelpSystems License Key
Now that the configurations have been made, make sure the Intermapper server has the flows service disabled, and the Intermapper service running. On the flows server, have the flows service running and the intermapper service disabled. Now on the Intermapper server you can open the flows window and use it as you normally would.
Still have questions? We can help. Submit a case to Technical Support.