When performing a new installation of PIPE-FLO (or any other Engineered Software application that uses enterprise network licensing), it can be convenient to copy the licensing configuration from another, existing installation. However, while the hostname or IP address or fully qualified DNS name of the license server must be entered on the "Server" screen of the installation wizard, this information is never displayed again except in the rare case that there is a licensing error upon (attempted) start-up of the application. This information is available; you just need to know where to look for it.

The "default.cfg" file

Configuration information that is shared between all users of the application - such as how to find the license server - is stored in a file called "default.cfg" in the application's installation folder. Depending on your personal settings in Windows Explorer, this file may appear simply as "default" (with no filename extension). This is a plain-text file containing just a few lines of data, in the standard "INI" file format; it can be viewed and edited with any plain-text editor, such as Notepad. The settings in this file are copied to the user's "flo.ini" file each time the application starts, so a change here will automatically propagate to every user the next time each user starts the application.

Copying data for a new installation

The following is an example of the contents of a "default.cfg" file:

[ID]
Company=ACME Engineering Co.
LicenseSvr=192.168.1.123
[SERIAL]
PF_=1234PF

(Note that the license server can be identified by either its fully qualified DNS name or its IP address.)

This represents all of the information that was entered during the installation of the product; it should be sufficient to copy down this information and enter it while running the installation wizard on a different computer.

Editing data in an existing installation

The "default.cfg" file is a plain-text file and is read each time the application starts. Therefore, editing this file with any plain-text editor and saving it affects all subsequent sessions of the application. If your license server has moved or been renamed, simply edit this file, update the information and save it again. The next time your application starts, the new configuration will take effect.