MASTER_40_Salesware_Installation_Guide

After PoolManager is installed, you should check the SiteDefaults.INI file that PoolManager
created in the SiriusFS\Install folder. See the following screen capture for an example of how
it is populated after installation by PoolManager. (If SiteDefaults.INI doesn’t exist, then you
did not have write permissions to the SiriusFS\Install folder when you installed PoolManager,
and you should create this file manually.) SiteDefaults.INI is not required, but makes
subsequent installs much easier. SiteDefaults.INI is used by installers that install Salesware
applications that use the middleware (EZs) to find the middleware servers where the EZs “live.” It is
also used by the Sales installer to find the credit card server. If you are using ProtoBase, the ProtoBase
server must have a static IP address and this address must be manually added to the
SiteDefaults.INI file using the .INI setting
CreditCardServer_IP=xxx.xxx.xxx.xxx.
Note: FileSync needs to be installed and configured before RentEZ functions properly. Installation
instructions for FileSync for the Food Service module are found in the Salesware Food Service
document. Installation instructions for FileSync for the Rentals module are found in the Salesware
Rentals document.
Pool.exe starts for each configured EZ automatically when you reboot the middleware server or log
in with the account name used to install PoolManager. No password is required. You can also launch
the EZs from the Start button or by using the desktop shortcuts.
Installing SysManager
The SysManager application can be installed on any computer on the network that has network access
to the SQL Server. If SysManager is being installed on a computer that has already had the
CommonFiles installer run on it (such as the SQL Server or PoolManager computer) you can skip the
step of installing CommonFiles. You need administrator privileges on the computer where
SysManager is installed. If you have write privileges to the SiriusFS\Install directory, the
35