MASTER_40_Salesware_Installation_Guide

Salesware Installation Guide 

SALESWARE INSTALLATION GUIDE ..................................................................................1 

INSTALLATION OVERVIEW ..................................................................................................2 

INSTALLATION OF CORE SALESWARE MODULES ..........................................................4 

Required installation files ..................................................................................................................................................... 4 

Optional installation files...................................................................................................................................................... 6 

Installing operating systems ................................................................................................................................................. 7 

Installing SQL Server............................................................................................................................................................ 8 

Installing SQL Server 2000 and SQL Server 2000 Service Pack 4 .................................................................................... 8 

Installing SQL Server 2005 ................................................................................................................................................ 9 

Installing ServerFiles........................................................................................................................................................... 11 

Verifying the SQL Server service pack level.................................................................................................................... 11 

Verifying mixed mode authentication is enabled ............................................................................................................. 15 

Running the ServerFiles installer...................................................................................................................................... 19 

Installing CommonFiles ...................................................................................................................................................... 26 

Installing PoolManager....................................................................................................................................................... 30 

Installing SysManager......................................................................................................................................................... 35 

Installing ReportManager .................................................................................................................................................. 40 

Installing Sales ..................................................................................................................................................................... 45 

Starting Sales for the first time ......................................................................................................................................... 51 

Other installation scenarios ................................................................................................................................................ 54 

Manually attaching the SiriusSQL database ..................................................................................................................... 54 

Installing a training database ............................................................................................................................................ 69 

Installing with an “execution protection” capable processor............................................................................................ 84 

Modifying a Salesware installation................................................................................................................................... 88 

Uninstalling Salesware ..................................................................................................................................................... 89 

INSTALLING CHARGE CARDS...........................................................................................89 

Installing and using ProtoBase Charge Cards.................................................................................................................. 90 

General notes .................................................................................................................................................................... 90 

Pre-install instructions ...................................................................................................................................................... 91 

1

ProtoBase Installation....................................................................................................................................................... 93 

Configuring ProtoBase for Salesware............................................................................................................................... 94 

ProtoBase settlement and Salesware reporting ................................................................................................................. 99 

ProtoBase offline transactions ........................................................................................................................................ 101 

ProtoBase questions........................................................................................................................................................ 103 

Installing DirectNet Charge Cards .................................................................................................................................. 107 

DirectNet .INI settings.................................................................................................................................................... 107 

Layouts ........................................................................................................................................................................... 109 

Security........................................................................................................................................................................... 109 

Licensing ........................................................................................................................................................................ 109 

Miscellaneous notes........................................................................................................................................................ 109 

Installing Ingenico Charge Cards .................................................................................................................................... 110 

General notes .................................................................................................................................................................. 110 

How Ingenico works with Salesware.............................................................................................................................. 110 

How Ingenico works with SysManager.......................................................................................................................... 111 

How Ingenico works with Sales ..................................................................................................................................... 111 

Sales Host settings for E-Commerce .............................................................................................................................. 112 

ww.dll registry settings................................................................................................................................................... 113 

Web.config settings ........................................................................................................................................................ 114 

Installing CreditCheq Cards ............................................................................................................................................ 114 

Pre-Install Checklist........................................................................................................................................................ 114 

Install - Setup.................................................................................................................................................................. 115 

Configuring EZCharge ..................................................................................................................................................... 120 

Installation overview 

Salesware, the Siriusware Point-Of-Sale (POS) application, requires four types of hardware: a 

database server, a middleware server, a SysManager management station and a salespoint. The 

database server is used to store the master database and software that is required by all the components 

of Salesware. The middleware server functions as a middleman, taking the load off the salespoints so 

sales can be made quickly without time- and resource-consuming database tasks. In addition, the 

middleware server serves to solve many problems of system vulnerability usually associated with 

network database systems. A SysManager station is where Salesware as a whole is managed. A 

salespoint is where sales are performed. 

With Salesware, there are many options for your hardware installation. The ideal setup is to have one 

server dedicated as the database and middleware server, at least two SysManager stations and as many 

salespoints as are necessary for your operation. However, a small operation may run Salesware on one 

computer, which acts simultaneously as the database server, middleware server, SysManager station 

and salespoint. Also, it is possible to use separate computers for the database server and the 

middleware server, or to combine a SysManager station and the middleware server. In this section of 

the installation guide you obtain an understanding of how the components of Salesware work together 

so that you understand why the “ideal setup” just mentioned is ideal, what other options exist, and 

what the strengths and weaknesses of each option are. 

2

Siriusware examined the worst problems that database-dependent networked operations experience 

and created the middleware server solution to address them. With a middleware server, the problems 

of faulty network cables, bad power, user error, slow or broken connections, unplugging, etc., are 

minimized to the greatest extent possible, which translates into less down time for your system and 

quicker processing where you need it – when making sales. 

When making sales, the salespoint takes the data from a transaction and stores it locally. The 

salespoint then directs the middleware to update the master database on the database server with the 

new data, and to download any new information from the master database on the database server to the 

salespoint’s local data files (e.g., pricing changes, new accounts, etc.). 

If all of the functional components are running on the same computer, then it is merely a question of 

various software programs talking to one other, with no phone calls or network connections. If your 

operation is small and only one salespoint is required, this could be optimal for you. 

However, once two computers are networked together, connections of some sort are introduced, which 

requires data to pass through those connections to open database files on the database server. This 

leaves your data and your network vulnerable because interruption of those connections while files are 

open can result in corrupted data. Similarly, database operations performed over network connections 

consume time and network resources. The greater the number of computers networked together and 

the farther the computers are from the database server, the more of this type of vulnerability and 

resource-consumption are introduced into your operation. 

This is where the middleware server comes into play. Instead of the salespoints talking over a network 

connection or phone line to an open database file on the database server, the salespoints direct the 

middleware to do the “dirty work” for them. The middleware server receives the data as a rapid 

stream of characters and commands, opens data files on the database server and does the timeconsuming 

database operations of opening, searching through, and updating files without delaying the 

salespoints in their POS activities. Therefore, the salespoints are never connected to the master 

database; the possibility for corruption and system crashes is greatly reduced, and the speed of sales 

operations is greatly enhanced. 

In addition, the middleware lets the salespoint know when it has completed its request. If the 

middleware server does not respond to the salespoint in 30 seconds (or whatever interval that you 

specify using the ServerTimeout .INI setting in the Sales32c.INI file) informing the 

salespoint of its successful operation, the salespoint automatically switches to standalone mode, 

operating independently of the network and saving its data locally. Once the middleware server and 

database server are available again, the locally saved data is automatically forwarded to the primary 

database on the database server for update. 

3

Middleware also performs another important function. It not only transfers updated information from a 

salespoint to the database server, it also downloads updated and required information from the 

database server to the salespoints. For example, if a new account has been created on a given 

salespoint, the middleware updates the database server with that information and then updates the 

other salespoints as well. If a new product is defined or a price is changed, that information is also 

transferred to all salespoints, on a continuous basis. 

With a network of two or more computers, middleware can be installed on a dedicated server of its 

own, on the database server or even on a salespoint. As already stated, the ideal setup for an operation 

of two computers or more is for middleware to be set up on the same server as is used to store the 

database files. This ensures that there are no open data files being shared by the salespoints over 

network connections, which translates into less data vulnerability and more speed. While a separate 

server can be used as the middleware server, installing middleware on the database server eliminates 

the network connection between the middleware and the files – a potential source of trouble. 

Another possible, but much less than optimal, setup is to have the middleware installed on a 

salespoint. The obvious advantage to this is that a single computer is used for two functions, reducing 

the number of computers to be purchased. However, this cancels out the purpose of the middleware, 

which is to prevent the salespoint computer from having open database files on the database server 

over a network connection. In this case, Sales would not be opening files from this computer, but 

middleware now would be, leaving your system vulnerable once again to data corruption and valuable 

use of network resources by performing time- and resource-consuming database operations over a 

network connection. 

For more information and recommendations on the numbers of middleware servers to use for a large 

number of salespoints, see the Salesware System Architecture and Specifications document, available 

from http://www.siriusware.com/docs. 

Note: Salesware doesn’t support any special capabilities to synchronize client date/time with the server 

date/time. Please use standard Windows networking capabilities like NET TIME to implement that 

capability across your Salesware network. 

Installation of core Salesware modules 

Required installation files 

The Salesware Product Table in the Modules section of the Salesware Modules, Configuration and 

Maintenance document (available from http://www.siriusware.com/docs) lists the names of the 

associated installer file used to install every Salesware product. This section covers installation of only 

the core Salesware modules– that is, those modules which must be installed at every Salesware 

installation to achieve the core product functionality. The installers required to do this are listed and 

described in the following table. In addition to the installation files, you also need the latest update 

4

files associated with each module, also listed in the table. For a detailed description of how update 

files are used in the Salesware application, see Updating Salesware Modules, available from 

http://www.siriusware.com/docs. The installers and update files are all available from the Siriusware 

web site. 

Installer Description Update file (Note: ** 

indicates the current 

release number) 

Install_Siriusware_ 

CommonFiles.msi 


ServerFiles.exe 


PoolManager.msi 


SysManager.msi 


ReportManager.msi 


Sales.msi 

Files required by all Salesware 

applications that run on a PC or server 

(not by handheld applications)—for 

example, fonts, TCPEZ and 

Runexe.exe. Not required with 


ServerFiles.exe. 

Creates Siriusware directory structure on 

database server computer. Copies in 

initial SiriusSQL database files; server 

must be updated with latest SiriusSQL 

scripts before deployment. 

Middleware manager. Spawns new 

instances of SalesEZ, BookEZ, RentEZ 

and TallyEZ. Must install Install_ 

Siriusware_CommonFiles.msi 

first. 

Core Salesware management module. 

Must install Install_Siriusware_ 

CommonFiles.msi first. 

Core Salesware reporting module. Must 

install Install_Siriusware_ 

CommonFiles.msi first. 

Module to enable Sales. This module 

provides the core Salesware functionality. 

Used in conjunction with almost all 

middleware components (though not 

TallyEZ). Must install Install_ 

Siriusware_CommonFiles.msi 

first. 

Only Runexe.exe, 

installed by the common 

files installer, has an 

update file: 

c_runexe_40**.exe. 

Not applicable. 

c_pool_40**.exe 

salesez_40**.exe 

bookez_40**.exe 

rentez_40**.exe 

tallyez_40**.exe 

c_sysmgr_40**.exe 

c_rptmgr_40**.exe 

c_sales_40**.exe 

In addition, you need a SiriusSQL database. When you run the ServerFiles installer, you are prompted 

to indicate which of the following you are installing: 

• An existing database – A SiriusSQL database that already has an associated license file and 

site-specific data. Normally installed at upgrade installations. 

• A new database – A “clean” SiriusSQL database that doesn’t yet have an associated license file 

or site-specific data. Normally installed at new installations. 

5

Depending on which you select, you need the following files, available from the Siriusware web site. 

Existing database 

SiriusSQL.ldf 

SiriusSQL.mdf 

SiriusSQL_Logs.ndf 

SiriusSQL_Transact.ndf 

Siriusware.LIC 

New database (Note: ** indicates the current release 

number) 

SiriusSQL_clean_4050h.zip (contains 

SiriusSQL.ldf, SiriusSQL.mdf, 

SiriusSQL_Logs.ndf and 

SiriusSQL_Transact.ndf) 

create_AppRole_SiriusSQL.sql 

Insert_SiriusSQL_SystemData_40**.zip 

In addition, you need to ensure that your database is up-to-date, regardless of which option you 

choose. You perform this step last and use a file with a filename of the format: 

SiriusSQL_40**_to_40**.sql. 

Optional installation files 

Other files that are also helpful when performing an installation are listed and described in the 

following table: 

File(s) 

Layouts for printing 

Siriusware 4.0 license file 

Global .INI file 

Description 

Layouts are used to format printed output on tickets, passes, 

vouchers, receipts, etc. See Salesware Layouts. These are placed in 

the Siriusware/SiriusFS/Layouts directory. 

If you are installing an existing SiriusSQL database, you cannot 

begin using Salesware until you place the associated license file in 

the Siriusware/SiriusFS/License directory. If you are 

installing a “clean” SiriusSQL database, you must make a request to 

Siriusware Client Services to generate a new license file for you 

using your unique Client # available from SysManager > Help > 

About SysManager after you install SysManager. It is also placed 

in the Siriusware/SiriusFS/License directory. 

Salesware 4.0 features self-configuration of salespoints using a 

global .INI capability, as described in the “configuration” section 

of the Salesware Modules, Configuration and Maintenance 

document. If you have already configured your global .INI file in 

SysManager, you can save it from the SysManager > Preferences > 

Miscellaneous > Global Salespoint INI tab > Write To File 

6

ports.INI file 

PDF documentation set 

Other installers 

Utilities 

button. You can then re-import the file after a fresh install of a new 

database to regain your original settings. 

The ports.INI file is used to configure cash drawers, customer 

(pole) displays and change dispensers at a salespoint. After you 

install Sales, this file can be copied into the Sales folder if you 

have multiple salespoints that are using the same ports.INI 

settings. 

The entire Salesware documentation set is available as a collection 

(zip file) of PDF files that can be “unzipped” into the 

Siriusware/SiriusFS/Docs directory. 

Siriusware provides a number of installers for further functionality. 

To obtain some of these installers an additional fee may be 

required. The advantage to having all of the installers that you need 

is that you can copy them all into one place on your network 

(typically \Siriusware\SiriusFS\Install). 

A variety of utilities are available from the Siriusware web site. 

These utilities are documented in the Salesware User Guide for 

Advanced Users. These utilities can be copied into the 

Siriusware/SiriusFS/Utilities directory. 

Installing operating systems 

Salesware currently supports the following operating systems: 

• Windows XP Home (not recommended) 

• Windows XP Professional 

• Windows 2000 Professional 

• Windows 2000 Server 

• Windows Server 2003 

Installation of operating systems should be performed in accordance with standard Microsoft 

procedures. For hardware specifications, see the Salesware System Architecture and Specifications 

document. 

Note: If you want to run the installers on unsupported operating systems (not recommended), you must 

first download the appropriate Windows Installer installation file from Microsoft and install it. 

Windows Installer v2.0 must be installed prior to running the installs (these are available in service 

packs for supported operating systems, but must be downloaded from the Microsoft web site to install 

on non-supported operating systems). If you don’t do this, the following message pops up: 

This operating system is no longer supported by Microsoft and is therefore not supported by 

Siriusware. PROCEED AT YOUR OWN RISK! If you have problems with the installation, or have 

7

problems running the software, you must upgrade your computer to a supported operating system and 

re-install Siriusware software before calling Siriusware Technical Support. 

Note: Can you run the new Salesware .msi (Microsoft Installer) installers on a system with the old 

(.exe-based) installs on them? Yes, but you must run the new CommonFiles installer first; it is a 

good practice to remove the old CommonFiles first. All new Salesware installers are .msi-based, 

except for ServerFiles, which remains .EXE-based. 

Installing SQL Server 

SQL Server is installed on Windows 2000 Server and Windows Server 2003. Siriusware supports both 

SQL Server 2000 and SQL Server 2005. To install SQL Server, you must have administrative rights to 

the server computer. 

Installing SQL Server 2000 and SQL Server 2000 Service Pack 4 

The following installation steps configure the system so that the database administrator logs in using 

the built-in system account. Please install using different parameters if they are more appropriate to 

your installation. 

To install SQL Server 2000: 

1. Insert the Microsoft SQL Server 2000 Standard Edition Installation CD. 

2. If “autorun” does not come up automatically, open the CD and double-click on 

autorun.exe. 

3. Select SQL Server 2000 Components. 

4. Select Install Database Server. 

5. At the Welcome dialog, click Next. 

6. At the Computer Name dialog, select Local Computer and click Next. 

7. At the Installation Selection dialog, select Create a new instance of SQL Server, or Install 

Client Tools, and click Next. 

8. At the User Information dialog, enter your name and company and click Next. 

9. At the Software License Agreement dialog, click Yes. 

10. At the Installation Definition dialog, select Server and Client Tools and click Next. 

11. At the Instance Name dialog, check Default and click Next. 

Note: If the check box for Default is grayed out and you are required to type an Instance Name, then 

a version of SQL Server has already been installed on this computer. In that case, open the Services 

Administrative Tool and find the existing version of MSSQLSERVER. It most likely has the 

software package with which it was installed in the name. 

12. At the Setup Type dialog, select Typical and click Next. 

8

Note: If you want to install SQL Server, the Data directory, or the Log directory to a drive other than 

C, select Custom and browse to the desired destination and click Next. 

13. At the Service Accounts dialog: 

1. Select Use the same account for each service. Auto start SQL Server Service. 

2. Under Service Settings, select Use the Local System account. Click Next. 

14. At the Authentication Mode dialog: 

1. Select Mixed Mode. 

2. Type a password into the Enter password: and Confirm password: boxes and click Next. 

Note: It is important to assign a password for the security of your database. Don’t leave it blank! 

15. At the Start Copying Files dialog, click Next. 

16. Let the installation run until you see the Setup Complete dialog and click Finish. 

To install SQL Server 2000 Service Pack 4: 

1. Insert the Microsoft SQL Server 2000 Standard Edition Service Pack 4 CD. 

2. From My Computer, open the CD drive and double-click on setup.bat. 


4. At the Software License Agreement dialog, click Yes. 

5. At the Instance Name dialog, click Next. 

6. At the Connect to Server dialog, select SQL Server Authentication and enter your password, 

and click Next. 

7. At the SQL Server 2000 Service Pack 4 Setup dialog, check Upgrade Microsoft Search and 

apply SQL Server 2000 SP4 [required] and click Continue. 

8. At the Error Reporting dialog, decide whether to check Automatically send fatal error 

reports to Microsoft and click OK. Information is gathered for the set-up. 

9. At the Start Copying Files dialog, click Next. Files are copied. 

10. Click OK to the backup prompt. 

11. At the Setup Complete dialog, click Finish. 

Installing SQL Server 2005 

The following installation steps install the minimum number of components required to deploy 

Salesware, and configure the system so that the database administrator logs in using the built-in 

system account. Please install using different parameters if they are more appropriate to your 

installation. 

Note: If you would like to optionally install Microsoft Reporting Services (recommended), you need to 

install the Microsoft IIS web server first and select Reporting Services from the Components to 

Install dialog in step 8 of the following installation instructions. You also need to select Install the 

9

default configuration from the Report Server Installation Options dialog when it appears. With 

Microsoft Reporting Services, you are provided with the ability to create extremely customized 

reports. 

To install SQL Server 2005: 

1. Insert the Microsoft SQL Server 2005 Standard Edition Installation CD. 

2. From the Install section of the Start dialog, select Server components, tools, Books Online, 

and samples. 

3. At the End User License Agreement dialog, click I accept the licensing terms and 

conditions and click Next. 

4. At the Installing Prerequisites dialog, click Install. After installation is complete, click Next. 

5. At the Welcome to Microsoft SQL Server Installation Wizard dialog, click Next. 

6. At the System Configuration Check dialog, click Next if the check is successful. 

7. At the Registration Information dialog, enter your name, company and product key. Click 

Next. 

8. At the Components to Install dialog, select SQL Server Database Services and 

Workstation components, Books Online and development tools. Click Next. 

Note: You must select Workstation components, Books Online and development tools to ensure 

that you install SQL Server Management Studio. However, several other components are installed as 

well, including Microsoft Visual Studio. If you would like to narrow down what gets installed by this 

selection, click the Advanced button and select individual components for installation. During 

installation of these components, you may be prompted to insert disk #2 of your installation disks. 

9. At the Instance Name dialog, click Default instance. Click Next. 

10. At the Service Account dialog, click Use the built-in system account and select Local 

system from the dropdown. In the Start services at the end of setup section, select SQL 

Server so that you can immediately test whether the installation was successful. Click Next. 

11. At the Authentication Mode dialog: 

1. Select Mixed Mode. 

2. Type a password into the Enter password: and Confirm password: boxes and click Next. 

Note: It is important to assign a password for the security of your database. Don’t leave it blank! In 

fact, if you do leave it blank, you may have trouble logging into SQL Server from SQL Server 

Management Studio. 

12. At the Collation Settings dialog, select Collation designator and sort order: and 

Latin_General from the dropdown box. Click Next. 

13. At the Error and Usage Report Settings dialog, decide whether to check the error reporting 

options and click Next. 

14. At the Ready to Install dialog, click Install. 

15. Let the installation run until you see Setup finished in the Status field next to each Product 

listed on the Setup Progress dialog and click Next. 

16. Review the Completing Microsoft SQL Server 2005 Setup dialog and click Finish. 

10

Note: If SQL Server Management Studio doesn’t appear in the Start > Programs > Microsoft SQL 

Server 2005 program group, you need to go to C:\Program Files\Microsoft SQL 

Server\90\Tools\Binn\VSShell\Common7\IDE and create an alias (shortcut) to SqlWb.exe. Add this 

alias to the Microsoft SQL Server 2005 program group for access from the Start button. 

To install SQL Server 2005 Service Pack 1: 

1. Download SQLServer2005SP1-KB913090-x86-ENU.exe from the Microsoft web site 

to the desktop of the server computer. 

2. Double-click on SQLServer2005SP1-KB913090-x86-ENU.exe. 


4. At the Software License Agreement dialog, check I accept the licensing terms and 

conditions and click Next. 

5. At the Feature Selection dialog, ensure that all options are checked and click Next. 

6. At the Authentication Mode dialog, select All instances and SQL Server Authentication. 

Enter your SA password, and click Next. You are validated. 

7. After installation is completed, click Next on the Installation Progress dialog. 

8. At the Installation Complete dialog, click Finish. Reboot if required (as indicated in the 

Status column on this dialog). 

Installing ServerFiles 

The Install_Siriusware_ServerFiles.exe installer sets up your Salesware server. You 

need administrator privileges on the server computer to run the ServerFiles installer. Before running 

this installer, you must have already installed SQL Server. See Installing SQL Server. The ServerFiles 

installer: 

• Creates the Salesware directory structure under the Siriusware directory. 

• Populates the Data, Install, and License directories in the Siriusware\SiriusFS 

directory. 

• Attaches the SiriusSQL database to SQL Server. 

Before beginning installation of ServerFiles, verify the following settings are correct on your server 

computer. 

• The latest SQL service pack is installed. 

• Mixed mode authentication is enabled. 

Note: To complete these procedures you need the SQL Server administrator password (often referred 

to as the SA password). 

Verifying the SQL Server service pack level 

11

For security reasons SQL Server should have the latest service pack installed as defined by the current 

Siriusware prerequisites to 4.0 installations. If you don’t know what the current service pack 

requirement is for SQL call, Siriusware Technical Support for further information. 

To verify the SQL Server service pack level for SQL Server 2000: 

1. Launch the Enterprise Manager application on the SQL server. This is usually done from Start 

> Programs > Microsoft SQL Server > Enterprise Manager. 

2. Expand the Console Root in the upper left corner of the screen until the server name to be used 

is displayed. (See screen capture below.) 

3. Right-click on the server group name to be used and select Properties. In this example, the 

(Local) (Windows NT) server is selected. 

12

The SQL service pack level is listed on the Product version line behind the build number. In this 

example you can see SP3 is listed indicating Service Pack 3. 

Note: If a service pack level is not shown and RTM is listed in its place, this indicates no service packs 

have been installed (the original Release To Manufacturing version is still installed). 

13

To verify the SQL Server service pack level for SQL Server 2005: 

1. Launch the SQL Server Management Studio application on the SQL server. This is usually 

done from Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management 

Studio. 

2. From the Connect to Server dialog, log in using either Windows Authentication or SQL 

Server Authentication. 

3. Click the New Query button in the upper left of the user interface, below the File menu. The 

query window displays. The service pack, if any, is listed below the query window. See the 

following screen shot. In this example, SP1 is installed. 

14

Verifying mixed mode authentication is enabled 

Mixed mode authentication must be enabled. If only Windows authentication mode is enabled, then 

the middleware is not able to access the SiriusFS\Data directory, where the database files reside. 

To verify mixed mode authentication for SQL Server 2000: 

1. Launch the Enterprise Manager application on the SQL server. This is usually done from Start 

> Programs > Microsoft SQL Server > Enterprise Manager. 

2. Expand the Console Root in the upper left corner of the screen until the server name to be used 

is displayed. (See screen capture below.) 

3. Right-click on the server group name to be used and select Properties. In this example, the 

(Local) (Windows NT) server is selected. 

15

4. Select the Security tab and verify the radio icon in front of SQL Server and Windows is 

selected and then exit the Enterprise Manager application. 

16

If Windows only was selected, you need to change it, save the settings and either restart SQL services 

or you can simply reboot the server computer for the changes to take effect. 

To verify mixed mode authentication for SQL Server 2005: 

1. Launch the SQL Server Management Studio application on the SQL server. This is usually 

done from Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management 

Studio. 

2. From the Connect to Server dialog, log in using either Windows Authentication or SQL 

Server Authentication. 

3. From Object Explorer, right-click on the top level (root) of the navigation tree and select 

Properties. (See screen capture below.) 

17

4. From the Server Properties dialog, select Security. (See screen capture below.) Verify the 

radio icon in front of SQL Server and Windows Authentication mode is selected and then 

exit the SQL Server Management Studio application. 

18

If Windows Authentication mode was selected, you need to change it, save the settings and either 

restart SQL services or you can simply reboot the server computer for the changes to take effect. 

Running the ServerFiles installer 

To install ServerFiles: 

1. On the desktop of the server computer, create a folder called SiriusTEMP. 

Note: The actual name that you assign to the folder is arbitrary. But you do need to create a separate 

folder. 

2. Copy the following files into the SiriusTEMP folder. 

• Software installation files – installation files are copied by the ServerFiles installer into 

\Siriusware\SiriusFS\Install. 

• The SiriusSQL database (if it is zipped, unzip the contents in this folder) – You install 

either an existing SiriusSQL database or a new, “clean” SiriusSQL database. The database 

consists of four files: SiriusSQL.ldf, SiriusSQL.mdf, SiriusSQL_Logs.ndf 

and SiriusSQL_Transact.ndf. See Installation of core Salesware modules. 

• The Siriusware 4.0 license file (only if you have a pre-made license file) – 

Siriusware.LIC. This option applies only if you are installing an existing SiriusSQL 

database. If you are installing an existing database, you should already have the license. 

• create_AppRole_SiriusSQL.sql and 

Insert_SiriusSQL_SystemData_40**.zip. This option applies only if you are 

installing a new, “clean” SiriusSQL database. The 

create_AppRole_SiriusSQL.sql script adds a user named sirius and password 

sirius that has public rights to the SiriusSQL database (this is necessary for sharing the 

database on the network – the middleware, SysManager and ReportManager expect this 

username and password to exist, with public rights). It is not a problem if this script is run 

multiple times. The Insert_SiriusSQL_SystemData_40**.zip file contains 

three files. Unzip these files into the directory. These three files are: 

Insert_SiriusSQL_SystemData_40**.sql, zipcodes.txt and 

Insert_SiriusSQL_SystemData_release.txt (release notes, for those 

interested). Insert_SiriusSQL_SystemData_40**.sql inserts required system 

data into the database – this data includes the administrator login name (admin), the 

default global .INI settings and zip codes (using zipcodes.txt). The 

Insert_SiriusSQL_SystemData_40**.sql script should only be run once. Both 

.sql scripts are executed automatically by the installer if they are in the SiriusTEMP 

folder (see following steps). 

3. Double-click on Install_Siriusware_ServerFiles.EXE from with the 

SiriusTEMP folder. 

4. You are presented with the following dialog. Click OK. 

19

5. You are presented with the following dialog. Click Next. 

6. You are presented with the following dialog. You should accept the default installation 

directory (C:\Program Files\Siriusware) unless you have good reasons to place it 

elsewhere. Click Next. 

20

7. You are presented with the following dialog. Un-check Install license file (requires 

siriusware.lic) if you are installing a new, “clean” SiriusSQL database or if you are installing 

an existing SiriusSQL database and, for some reason, you don’t have the license file. Leave the 

other options checked. 

21

8. If you selected Install license file (requires siriusware.lic) in the previous step, you are 

presented with the following dialog. Click Browse and navigate to the SiriusTEMP directory 

(though you are probably already in that directory by default). Select the Siriusware.LIC 

file and click Open. Then click Next to move on to the next dialog. 

9. You are presented with the following dialog. Click Next to start the installation. The installer 

creates the Siriusware directory structure and copies the installation files from the 

SiriusTEMP directory into the \Siriusware\SiriusFS\Install directory. It also 

copies the license file into the \Siriusware\SiriusFS\License directory (if you 

previously selected this option). 

22

10. You are presented with the following dialog. Select whether you are attaching a new, “clean” 

SiriusSQL database or an existing SiriusSQL database. Click Next. 

23

11. If you selected Attach a new, blank database in the previous step, you are presented with the 

following dialog. Click the Browse buttons and navigate to the SiriusTEMP directory 

(though you are probably already in that directory by default). Select the SiriusSQL.mdf 

file click Open. Then select the Insert_SiriusSQL_SystemData.4xxx.sql file and 

click Open. Then click Next. The installer attaches the database to your SQL Server. 

12. If you selected Attach an existing database in the previous step, you are presented with the 

following dialog. Click Browse and navigate to the SiriusTEMP directory (though you are 

probably already in that directory by default). Select the SirisSQL.mdf file and click Open. 

The installer attaches the database to your SQL Server. 

24

13. You are presented with the following dialog. Click Finish to finish the installation. 

14. Copy the application updates into the Siriusware updates folder 

(\Siriusware\SiriusFS\updates). You need an update for each installer you plan to 

25

un (each installer that you copied into the SiriusTEMP folder and that now “lives” in 

\Siriusware\SiriusFS\Install). At a minimum, to install the core Salesware 

modules, you need: 

• c_runexe_40**.exe 

• c_pool_40**.exe 

• salesez_40**.exe 

• bookez_40**.exe (if you purchased the Private Instruction or Activity/Facility 

Scheduling modules) 

• rentez_40**.exe (if you purchased the Rental module) 

• tallyez_40**.exe (if you purchased the Handheld Retail Inventory component of 

the Retail module) 

• c_sysmgr_40**.exe 

• c_rptmgr_40**.exe 

• c_sales_40**.exe 

15. Copy any layouts you wish to use into the \Siriusware\SiriusFS\Layouts folder. 

16. Adjust permissions. The ServerFiles installer ensures that the SiriusFS folder is shared. If 

your network has its own domain and users log into that domain, then their permissions 

automatically carry over to determine their permissions for access to the SiriusFS directory. 

Otherwise, each Salesware user needs to be added by the server administrator, and permissions 

determined at that time. In general, you should check that every user has read-only access to 

the SiriusFS directory. The one exception is users who are using SysManager to edit 

layouts. Those users also need write permission to the \SiriusFS\Layouts directory. It 

doesn’t matter what they log into SysManager as, but they must log into the SysManager 

computer as a user with write permissions to \SiriusFS\Layouts. 

17. Delete the SiriusTemp folder and all its contents from the desktop you created earlier. 

Installing CommonFiles 

You must run the Install_Siriusware_CommonFiles.msi installer previous to installing 

the remaining Salesware core installers: before Install_Siriusware_PoolManager.msi, 

Install_Siriusware_SysManager.msi, Install_Siriusware 

ReportManager.msi and Install_Siriusware_Sales.msi. If more than one of these 

installers is run on a single computer, you need only run the CommonFiles installer once. You need 

administrator privileges on the computer where CommonFiles is being installed. Before running this 

installer, you must have already installed SQL Server and the ServerFiles installer. 

The CommonFiles installer: 

• Creates the Siriusware directory structure. (If installing CommonFiles on the same 

computer where ServerFiles was installed, then you would normally specify that this directory 

structure is the same as that already created by ServerFiles, but this is not a requirement.) 

• Installs the runexe.exe application 

• Installs files used by a variety of Salesware applications, such as fonts and FoxPro libraries. 

26

• Writes shared information to the Windows registry, such as the location of the SiriusFS 

folder on the network 

To run the CommonFiles installer: 

1. On the computer where you are installing CommonFiles (and where you are about to install 

PoolManager, SysManager, ReportManager or Sales), access the \SiriusFS\Installs 

directory. 

2. If you are installing CommonFiles on the server computer where ServerFiles is already 

installed, you can run the Install_Siriusware_CommonFiles.msi installer directly 

from the \SiriusFS\Install directory. If you are accessing the \SiriusFS\Install 

directory over the network, you can either run the installer over the network or copy the 

installer to the desktop and run it from there. 


4. You are presented with the License Agreement. Read the agreement, and click I accept the 

license agreement to continue. 

5. You are presented with the following dialog. You should accept the default installation 

directory (C:\Program Files\Siriusware) unless you have good reasons to place it 

elsewhere. Click Next. Installation of CommonFiles begins. 

27

6. During installation of CommonFiles, you are presented with the following dialog. Click the 

Browse button and navigate to the shared SiriusFS directory on your network. This usually 

requires navigating via My Network Places > Entire Network (see screen capture). If you are 

installing CommonFiles on your SQL Server computer, you browse the local file system. 

When mapping across the network, Salesware accesses the SiriusFS directory using UNC 

conventions (i.e., \\servername\share); there is no need to map the SiriusFS share to 

a local drive prior to running CommonFiles. Click Next and the CommonFiles installation 

continues. 

28

7. When CommonFiles is finished installing, you are presented with the following dialog. Click 

Finish. 

29

Installing PoolManager 

It is recommended that you run PoolManager on a standalone computer. In some instances, 

PoolManager is installed on the computer running SQL Server. You need administrator privileges on 

the computer where PoolManager is installed and you need write privileges to the 

SiriusFS\Install directory (the PoolManager installer writes a file named 

SiteDefaults.INI to the SiriusFS\Install directory). Before running this installer, you 

must have already installed SQL Server and the ServerFiles installer, and you must have already 

installed CommonFiles on the computer where you are installing PoolManager. 

Note: The computer where PoolManager is installed must have a static IP address. You must have 

already assigned this address to the computer where PoolManager is being installed before running the 

installer. 

The PoolManager installer: 

• Creates the \Siriusware\Pool directory and associated files. 

• Installs desktop shortcuts to SalesEZ, BookEZ, RentEZ and TallyEZ; training shortcuts to each 

of these can be installed as well. 

• Installs the ODBC that enables Pool.exe to “talk” with the SiriusSQL database. 

• Creates and populates the SiteDefaults.INI file in the SiriusFS\Install directory. 

To run the PoolManager installer: 

1. Ensure that CommonFiles is already installed. 

2. If you are installing PoolManager on the server computer where ServerFiles is already 

installed, you can run the Install_Siriusware_PoolManager.msi installer directly 





30

4. You are presented with the following dialog. Depending on which EZ’s you plan to use, select 

which PoolManagers you want to install. These EZ’s should correspond to the update files that 

you copied into the \Siriusware\SiriusFS\updates folder earlier (see Running the 

ServerFiles installer). You can add the training mode EZ’s, but you are required to install a 

training database before you can use these (see Installing a training database). SalesEZ should 

always be installed, because it is used by salespoints. You can select either Will be installed 

on local hard drive or Entire Feature will be installed on local hard drive. The two options 

are equivalent. Click Next. 

31

5. You are presented with the following dialog. Type in the static IP address of the computer on 

which you are installing PoolManager. Click Next. 

6. You are presented with the following dialog. Click Next to install PoolManager. 

32

7. After PoolManager installation begins, you are presented with the following dialog. Enter the 

name or IP address of the SQL Server that contains the Siriusware database. If the computer on 

which you are installing PoolManager is that computer, choose or type (local) or the actual 

name of the SQL Server computer (the latter is recommended). This information is used to 

create the ODBC connection. Click OK. PoolManager installation continues. 

33

8. When PoolManager completes, you are presented with the following dialog. Click Finish. 

34

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

installer updates the value of the SiriuswareSQLServer setting in the SiteDefaults.INI 

file. 

The SysManager installer: 

• Creates the \Siriusware\SysManager directory and associated files. 

• Installs a desktop shortcut to SysManager; a training shortcut to SysManager can be installed 

as well. 

• Installs the ODBC that enables SysManager.exe to “talk” with the SiriusSQL database. 

• Creates and assigns a value to the LOCATION system environment variable. The value of the 

LOCATION environment variable must be unique for each computer where it is installed. 

To run the SysManager installer: 


2. If you are installing SysManager on the server computer where ServerFiles is already installed, 

you can run the Install_Siriusware_SysManagerManager.msi installer directly 





4. You are presented with the following dialog. You can add the training mode SysManager, but 

you are required to install a training database before you can use it (see Installing a training 

database). You can select either Will be installed on local hard drive or Entire Feature will 

be installed on local hard drive. The two options are equivalent. Click Next. 

36

5. You are presented with the following dialog. Enter the location name for this computer. This 

dialog causes the LOCATION system environment variable to be created and this value 

assigned to it. The value of the LOCATION environment variable must be unique for each 

computer where it is installed. If there is already a LOCATION environment variable on this 

computer, the value is changed to whatever you type here. Typical values used by clients 

reflect the physical location of the computer, such as office. The value must be 1 – 6 

characters in length. 

37

6. You are presented with the following dialog. Click Next to begin installation of SysManager. 

38

7. After SysManager installation begins, you are presented with the following dialog. Enter the 

name or IP address of the SQL Server that contains the Siriusware database. If the computer on 

which you are installing SysManager is that computer, choose or type (local) or the actual 

name of the SQL Server computer (the latter is recommended). This information is used to 

create the ODBC connection. In this example, the field is already pre-populated with (local) 

because the PoolManager installer was already run on this computer and that was the value 

specified. If you change this value and you have write privileges to the SiriusFS\Install 

directory, the installer updates the value of the SiriuswareSQLServer setting in the 

SiteDefaults.INI file. 

8. Click OK. SysManager installation continues. 

9. When PoolManager completes, you are presented with the following dialog . Click Finish. 

39

You can launch SysManager from the Start button or by using the desktop shortcut. The default login 

name is ADMIN with no password. 

Installing ReportManager 

The ReportManager application can be installed on any computer on the network that has network 

access to the SQL Server. If ReportManager 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 

ReportManager is installed. If you have write privileges to the SiriusFS\Install directory, the 

installer updates the value of the SiriuswareSQLServer setting in the SiteDefaults.INI 

file. 

The ReportManager installer: 

• Creates the \Siriusware\ReportManager directory and associated files. 

• Installs a desktop shortcut to ReportManager; a training shortcut to ReportManager can be 

installed as well. 

• Installs the ODBC that enables ReportManager.exe to “talk” with the SiriusSQL 

database. 

• Creates and assigns a value to the LOCATION system environment variable. The value of the 

LOCATION environment variable must be unique for each computer where it is installed. 

To run the ReportManager installer: 


2. If you are installing ReportManager on the server computer where ServerFiles is already 

installed, you can run the Install_Siriusware_SysManagerManager.msi installer 

40

directly from the \SiriusFS\Install directory. If you are accessing the 

\SiriusFS\Install directory over the network, you can either run the installer over the 

network or copy the installer to the desktop and run it from there. 


4. You are presented with the following dialog. You can add the training mode ReportManager, 

but you are required to install a training database before you can use it (see Installing a training 

database). You can select either Will be installed on local hard drive or Entire Feature will 

be installed on local hard drive. The two options are equivalent. Click Next. 

41

5. You are presented with the following dialog. Enter the location name for this computer. This 

dialog causes the LOCATION system environment variable to be created and this value 

assigned to it. The value of the LOCATION environment variable must be unique for each 

computer where it is installed. If there is already a LOCATION environment variable on this 

computer, the value is changed to whatever you type here. In the screen capture below, the 

value office is pre-populated in the field because this installation is occurring on the same 

computer where SysManager was installed, and that was the value that was specified during 

the SysManager installation. The value must be 1 – 6 characters in length. 

42

6. You are presented with the following dialog. Click Next to begin installation of SysManager. 

43

7. After ReportManager installation begins, you are presented with the following dialog. Enter 

the name or IP address of the SQL Server that contains the Siriusware database. If the 

computer on which you are installing ReportManager is that computer, choose or type (local) 

or the actual name of the SQL Server computer (the latter is recommended). This information 

is used to create the ODBC connection. In this example, the field is already pre-populated with 

(local) because the PoolManager installer was already run on this computer and that was the 

value specified. If you change this value and you have write privileges to the 

SiriusFS\Install directory, the installer updates the value of the 

SiriuswareSQLServer setting in the SiteDefaults.INI file. 

8. When the ReportManager installation completes, you are presented with the following dialog. 

Click Finish. 

44

You can launch ReportManager from the Start button or by using the desktop shortcut. The default 

login name is ADMIN with no password. 

Installing Sales 

The Sales application can be installed on any computer on the network that has network access to the 

SQL Server. The Sales application is the operator interface for all of the POS computers on the 

network. Each salespoint receives a separate installation of the Sales application, and a unique name is 

required for each. For criteria you should use when choosing salespoint names, see the Salesware User 

and Ticketing Guide for Beginning Users. If Sales is being installed on a computer that has already 

had the CommonFiles installer run on it (such as the SysManager or ReportManager computer) you 

can skip the step of installing CommonFiles. You need administrator privileges on the computer where 

Sales is installed. 

The Sales installer: 

• Creates the \Siriusware\Sales directory and associated files. 

• Installs a desktop shortcut to Sales; a training shortcut to Sales can be installed as well. 

Note: Before installing any salespoints, you need to have a license file in 

Siriusware\SiriusFS\License. If you installed an existing database when you installed 

ServerFiles, you probably already installed this license. If you installed a new, “clean” database, you 

need to get a license file from Siriusware Technical Support. When calling Siriusware Technical 

45

Support for a license file, you need to provide the client number that was assigned to your installation. 

Get this Client # from SysManager > Help > About SysManager. 

Before salespoint installation, verify that there are enough salespoints created in SysManager for the 

entire installation. Do this by going to SysManager > Activities > System Lists > Sales points menu 

and counting the number of names; this number should equal the number of salespoints to be installed. 

If there are not enough salespoints, simply add more by using the New button. You need a license for 

each salespoint added. Assuming you have an available license for a new salespoint, the name of the 

salespoint also appears on the Sales Point Licenses dialog (SysManager > Preferences > Sales Point 

Licenses) when you add a new salespoint. From the Sales Point Licenses dialog you should also 

verify that the salespoints are licensed correctly. Ensure that the Type is set correctly (C=Classic Sales 

and W= Web-based Sales). Verify that the appropriate check boxes are checked for each sales point 

based on the licensing that was purchased. If you are unclear as to what any of the check boxes stand 

for, hover the mouse pointer over the three-letter column name for a complete description, or consult 

the Salesware Modules, Configuration and Maintenance document, available from 

http://www.siriusware.com/docs. 

To run the Sales installer: 


2. If you are installing Sales on the server computer where ServerFiles is already installed, you 

can run the Install_Siriusware_Sales.msi installer directly from the 

SiriusFS\Install directory. If you are accessing the SiriusFS\Install directory 

over the network, you can either run the installer over the network or copy the installer to the 

desktop and run it from there. 


46

4. You are presented with the following dialog. You can add the training mode Sales, but you are 

required to install a training database before you can use it (see Installing a training database). 

You can select either Will be installed on local hard drive or Entire Feature will be 

installed on local hard drive. The two options are equivalent. Click Next. 

47

5. You are presented with the following dialog. This dialog is populated using the 

SiteDefaults.INI file that was installed by PoolManager. Note that in this example all 

modules were installed on the same computer, and that the CreditCardServer_IP .INI 

setting has not yet been added to the SiteDefaults.INI file. Setting the Credit card 

server field on this dialog sets the IP address for this particular installation of Sales only: the 

credit card server IP address must be manually added to the SiteDefaults.INI file if you 

want the IP address to appear in this dialog for future installs of Sales. Click Next. 

48

6. You are presented with the following dialog. The Global ini group lists the default groups in 

the global INI settings in the SysManager > Preferences > Miscellaneous > Global 

Salespoint INI tab. For a description of how this works, see the Salesware Modules, 

Configuration and Maintenance document, available from http://www.siriusware.com/docs. 

The three radio buttons should be set depending on whether you have a credit card server, the 

Private Instruction or Activity/Facility Scheduling modules, or Rentals, respectively. It is easy 

to change any of the settings you selected in this dialog later by accessing the 

Sales32c.INI file and modifying accordingly. For more information on the .INI settings 

created by this dialog, see the configuration section of the Salesware Modules, Configuration 

and Maintenance document. 

49

7. You are presented with the following dialog. Click Next to start the Sales installation. 

50

8. When the Sales installation completes, you are presented with the following dialog. Click 

Finish. 

Starting Sales for the first time 

Ensure that PoolManager is running on the middleware server. SalesEZ must be running, and possibly 

BookEZ or even RentEZ or TallyEZ, depending on your configuration. Click on the Sales icon on the 

desktop. 

You get a message indicating that files are not found (see the following screen capture). Sales must 

load them from the server (that is, Sales must create the local data files in the 

Siriusware\Sales\Data folder). Click Yes and the salespoint begins to build the file structure 

for the first time. This can take a few minutes depending on the size of the dataset. 

Previous to this, you may also get a small error window indicating Can’t find updates table! – simply 

ignore this error or click OK to close the window. There is no need to worry – at this point the deletes 

table has not yet been created. 

51

Salespoint setup 

The next screen prompts you for the name of this particular salespoint. The list of choices reflects the 

salespoint names that were entered into SysManager earlier, or a list of default salespoint names. 

Select the correct salespoint name from the list and click OK. 

52

The next screen can prompt you in one of two ways. If the salespoint name has never been used, it 

asks you to enter a new salespoint name and description. If you like the name as is, simply re-enter the 

name and supply a description. Click OK to continue. 

Note: You cannot have duplicate salespoint names, and no two salespoints can use the same name. 

You must choose a different name from the list for each computer on which Sales is installed. 

If the salespoint name has ever been assigned to any salespoint before, you see a warning that the 

salespoint name is already in use. This warning is designed to prevent someone from assigning the 

same salespoint name to more than one salespoint. It is only a warning to let you know that particular 

salespoint name has been used at some point in the past. If you know that the name in question is 

supposed to be used by this salespoint, simply click on OK to continue past the warning message and 

assign the name to the salespoint anyway. 

If your salespoint detects any changes in the Sales32c.INI file, it prompts you with a message 

stating that your salespoint settings have changed and that Sales must be restarted. Simply click OK 

and restart sales. 

Sales should now be installed and sitting at the login screen. 

53

Repeat the sales install procedure for each POS station. 

Other installation scenarios 

Manually attaching the SiriusSQL database 

There are several scenarios in which you may need to manually attach the SiriusSQL database, instead 

of using the ServerFiles installer: 

• When updating your installation from SQL Server 2000 to SQL Server 2005. 

• When upgrading your database from Salesware 3.4 to 4.0. 

• When you are moving an existing database from one instance of SQL Server to another. 

If the SiriusSQL database is detached from an instance of SQL Server and then re-attached at a later 

time, no steps in addition to what is normally done from SQL Server are necessary. But in the manual 

attachment scenarios just listed, additional steps are required. These steps are presented in this section. 

To attach the SiriusSQL database, you need the four files that comprise the database: 

• SiriusSQL.MDF 

• SiriusSQL.LDF 

• SiriusSQL_LOGS.NDF 

• SiriuSQLTRANSACT.NDF 

54

Note: The directions provided in this section apply primarily to attaching an existing SiriusSQL 

database. If you need to attach a new, “clean” SiriusSQL database, you should use the ServerFiles 

installer as described in Installing ServerFiles. 

To attach the SiriusSQL database to SQL Server 2000: 

1. Open Enterprise Manager application and drill down into the Databases section for the SQL 

Server that is to be used to run the SiriusSQL database. Highlight the Databases section by 

clicking on it to display the installed databases on the left side of the screen. If more than one 

server is listed in the SQL Server Group, double-check to verify which server SiriusSQL is to 

be installed on. 

55

2. Right-click on the right side of the screen in the white area and select All Tasks. Then select 

Attach Database. 

Note: In rare circumstances, you may want to detach a SiriusSQL database and attach a different one 

(as opposed to attaching a SiriusSQL database for the first time). In these cases, you first must detach 

the SiriusSQL database by selecting the SiriusSQL database icon, and then right-clicking on the 

selected icon. From that menu you select All Tasks, and then click on Detach Database… Then click 

OK on the Detach Database – SiriusSQL dialog. After that you can attach the new SiriusSQL 

database you wish to use, as described in steps 2- 4. You need a different license for this database as 

well, and you also need to delete another instance of the sirius user, as described in the note after step 

#6. 

3. The Attach Database dialog opens you are prompted for the location of the 

SiriusSQL.MDF file. Click the ellipses button shown in the following screen capture and 

browse to the location of the stored SiriusSQL files. Select the SiriusSQL.MDF file and 

click OK. 

56

4. You should see the following screen capture, indicating the location of the files that are ready 

to attach. Make sure the Attach As: field is SiriusSQL and the owner of the newly attached 

database is SA. Click on OK to attach the database. 

5. You should see the following screen indicating the database was successfully attached. Click 

OK to clear the dialog. 

57

6. The newly attached database has an orphan user with the name sirius attached to it. This 

orphaned user name must be deleted and recreated. (This process is not required when the 

database is attached by the ServerFiles installer.) Steps 7 and 8 describe how you delete and 

re-create this orphan user. 

Note: The siriusweb user needs to be created as well if you implement the E-Commerce or Rentals 

modules (Rentals needs this for the self-entry functionality). Repeat these directions if that is the case 

at your site. 

Note: In the rare circumstances when you detach a SiriusSQL database and attach a different one (as 

opposed to attaching a SiriusSQL database for the first time), you need to delete an additional 

instance of the sirius user. To delete this additional instance, go to Enterprise Manager again and, on 

the left side of the screen, expand the Databases tab and click on the SiriusSQL database to display 

the characteristics of SiriusSQL. Select the Users icon and the list of users appears on the right side of 

the screen. Right-click on the sirius user and select Delete from the dropdown menu. Then continue 

with steps 7 and 8. 

7. In Enterprise Manager, expand the Security tab on the left side of the screen and click on 

Logins. 

58

8. Right-click on the user sirius and choose Delete. 

59

9. You are given a warning, confirming the deletion of the user sirius. Click on Yes to continue. 

10. The old user sirius has now been deleted and we are ready to create the new sirius user. Rightclick 

on the right side of the screen in the white area and select New Login. 

60

11. The SQL Server Login Properties – New Login dialog is displayed. Perform the following: 

1. Type the name sirius into the Name: field. 

2. Select the SQL Server Authentication radio button and type the password sirius into 

the Password: field. 

3. Select SiriusSQL in the Database: field, and leave the Language: at . 

61

12. Click on the Database Access tab and put a check into the Permit check box next to 

SiriusSQL. The Permit in Database Role should automatically choose public for you − if it 

does not, simply put a check in the check box next to the public role. Click OK. 

62

13. You are prompted to confirm the password you typed in earlier. Type in sirius and click on 

OK to finish creating the user. 

The process is now complete and the database is ready for use. 

Note: It may be necessary for you to run the create_AppRole_SiriusSQL.sql script after 

attaching the database. If you added the siriusweb user, it is required. This script can safely be run any 

number of times. 

63

To attach the SiriusSQL database to SQL Server 2005: 

1. Start SQL Server Management Studio (which is a replacement tool for Enterprise Manager and 

Query Analyzer in SQL 2000). 

Note: If you cannot find an entry to start SQL Server Management Studio from the Program list as 

shown above, go to C:\Program Files\Microsoft SQL 

Server\90\Tools\Binn\VSShell\Common7\IDE and double-click on the file named SqlWb.exe (to 

run the SQL Server Management Studio). 

2. Log into the SQL Server Management Studio by selecting: 

1. Database Engine for Server type. 

2. Server name from the dropdown list. The current Server name should display by default, 

but you can browse to connect to another server too. 

3. SQL Server Authentication for Authentication. Then enter the sa login and password. 

4. Click Connect. 

64

3. Right-click on Databases and select Attach…. 

Note: In rare circumstances, you may want to detach a SiriusSQL database and attach a different one 

(as opposed to attaching a SiriusSQL database for the first time). In these cases, no special steps are 

required beyond those presented in this section. Special steps are required, however, if you are using 

SQL Server 2000, as specified in To attach the SiriusSQL database to SQL Server 2000:. 

65

4. From the Attach Databases dialog, click the Add button, and then browse to the 

SiriusSQL.mdf file. Select the file and click OK. All the data files are displayed. 

5. If you need to change the database name to SiriusSQL, click on the current default name under 

Attach As and type in SiriusSQL. 

6. Click OK to move on after you are sure everything on this dialog is correct. 

7. Now, expand the Databases folder and right-click on SiriusSQL and select Properties. In the 

Database Properties – SiriusSQL dialog, on the left side, select Options. Ensure that sure 

Compatibility level dropdown is set to SQL Server 2000(80). 

66

8. Click OK. Now your database is attached. 

9. Now create the sirius user. A security login for the sirius user needs to be created. 

Note: The siriusweb user needs to be created as well if you implement the E-Commerce or Rentals 

modules (Rentals needs this for the self-entry functionality). Repeat these directions if that is the case 

at your site. The default password for siriusweb is siriusweb. 

10. Delete the existing sirius user: 

1. In SQL Server Management Studio, expand the Databases folder > SiriusSQL folder > 

Security folder. 

2. Go into the Schemas folder and delete the sirius user. 

3. Go into the Users folder and delete sirius user. 

11. Create a new sirius and siriusweb user: 

1. In the SQL Server Management Studio, expand the Security folder and right-click on 

Logins, and then select New Login…. 

2. On the General page of the Login – New dialog, enter sirius in the Login name: field. 

67

3. Select SQL Server Authentication. 

4. Enter sirius in the password field and confirm it. 

5. There are three password control settings (circled in red in the following screen capture) 

that are checked by default. You must un-check these settings or your Salesware 

applications won’t be able to connect to the database. 

6. Select SiriusSQL as default database. 

7. Go to the User Mapping page and check the SiriusSQL database. Ensure that the public 

box also appears as checked under Database role membership for: SiriusSQL. 

68

12. Click OK. 

Your database is now ready for use. 

Note: It may be necessary for you to run the create_AppRole_SiriusSQL.sql script after 

attaching the database. If you added the siriusweb user, it is required. This script can safely be run any 

number of times. 

Installing a training database 

You may wish to use a training database. Training databases are useful for testing as well as training. 

The training database is simply a copy of the actual live database, attached as another name. 

69

The training database should not be created until after the “live” system has been fully installed and 

verified working. Also, when creating the training database you are bringing down the entire live 

system for a few moments and need to verify that everyone is out of the system. 

To install the training database on SQL Server 2000: 

1. First, make of copy of your “live” database. But before you can duplicate it, SQL Services 

must be stopped. To do this, open Enterprise Manager, right-click on the SQL server that is 

running SiriusSQL and select Stop. 

2. You are prompted to confirm the stop of SQL services on the server. Click Yes to continue. 

70

Note: Much of the information you are used to seeing in Enterprise Manager disappears; this is normal 

and returns when the process is complete. 

3. Minimize the Enterprise Manager screen. 

4. You now need to copy the four files that comprise the SiriusSQL database: 

SiriusSQL.MDF 

SiriusSQL.LDF 

SiriusSQL_LOGS.NDF 

SiriuSQLTRANSACT.NDF 

These are usually found in C:\Program Files\Siriusware\SiriusFS\Data. 

5. Create a new folder in the SiriusFS directory called Training Data and copy the four 

database files into this folder. (You should now have the database files in two locations.) 

Note: The training database must reside in a separate folder from the live database. Also, there is no 

need to separate the log file from the primary files. 

Note: Sometimes stopping the database from Enterprise Manager doesn’t work: You get an error 

message stating that the files are in use. In that case, you need to detach the SiriusSQL database 

instead of simply stopping it. To do this, click on Databases, select the SiriusSQL database icon on 

the right side of the screen (where all existing databases are shown), and then right-click on the 

selected icon. From that menu you select All Tasks, and then click on Detach Database… Then click 

OK on the Detach Database – SiriusSQL dialog. 

6. Open the Enterprise Manager application and right-click on the SQL server stopped previously. 

Select the Start option. It may take a few seconds for the services to start back up. 

Note: If you found it necessary to detach the database so that you could copy the files, you need to reattach 

it before you can start it. Do this by right-clicking on Databases, selecting All Tasks and then 

Attach Database. From the Attach Database – (LOCAL) dialog, navigate to your “live” database 

directory (Data), and select the SiriusSQL.MDF file. More detailed directions for attaching are 

provided in the following steps, because you must attach the training database. 

Note: If 15 or so seconds after re-starting the database the screen does not return to normal, click on 

Action at the top of the Enterprise Manager screen and choose refresh. 

At this point the system can once again be used in live mode. 

71

7. The next step is to attach the training database. With the Enterprise Manager application still 

running, expand Databases on the left side of the screen. 

8. Right-click on the right side of the screen in the white area and select All Tasks and then select 

Attach Database. 

72

9. The Attach Database – (LOCAL) dialog opens and prompts you for the location of the 

database files. You want to browse to the location of the duplicated database files that reside in 

your newly created Training Data folder, and select the SiriusSQL.MDF file. 

10. You should see the following dialog, indicating the location of the files that are ready to attach. 

Ensure that the name to attach the database is SiriusSQL_Training (in the Attach as: field) 

and the owner of the newly attached database is still SA. Click OK to attach the database. 

73

11. You should see the following dialog, indicating that the database was successfully attached. 

Click OK to clear the dialog. 

12. The last step is to give the user sirius access to the newly installed database. In Enterprise 

Manager, expand Security on the left side of the screen and click Logins. You should see the 

user sirius listed. 

74

13. Right-click on the user sirius and select Properties. 

75

14. Click on the Database Access tab and put a check in the Permit box for 

SiriusSQL_Training. (You should now have checkmarks for both Siriusware databases, 

allowing this one user access to both databases.) Click OK. 

76

The training database is now in place and ready for use by the training versions of the 4.0 suite of 

applications. 

To install the training database on SQL Server 2005: 

1. First, make of copy of your “live” database. But before you can duplicate it, SQL Services 

must be stopped. To do this, open Microsoft SQL Server Management Studio and log in. 

Right-click on the SQL server name and select Stop. 

77

2. You are prompted to confirm the stop of SQL services on the server. Click Yes to continue. 

3. Minimize the Microsoft SQL Server Management Studio screen. 

4. You now need to copy the four files that comprise the SiriusSQL database: 

SiriusSQL.MDF 

SiriusSQL.LDF 

SiriusSQL_LOGS.NDF 

SiriuSQLTRANSACT.NDF 

These are usually found in C:\Program Files\Siriusware\SiriusFS\Data. 

5. Create a new folder in the SiriusFS directory called Training Data and copy the four 

database files into this folder. (You should now have the database files in two locations.) 

78

Note: The training database must reside in a separate folder from the live database. Also, there is no 

need to separate the log file from the primary files. 

6. Open the Microsoft SQL Server Management Studio application and right-click on the SQL 

server stopped previously. Select the Start option. You are prompted to confirm that you do in 

fact want to re-start the server. 

It may take a few seconds for the services to start back up. At this point the system can once 

again be used in live mode. 

7. The next step is to attach the training database. With the Microsoft SQL Server Management 

Studio application still running, expand Databases on the left side of the screen. 

8. Right-click on the right side of the screen in the white area and select Attach…. 

79

9. The Attach Databases dialog opens and prompts you for the location of the database files. 

Click Add to browse to the location of the duplicated database files that reside in your newly 

created Training Data folder, and select the SiriusSQL.MDF file. Click OK. 

80

10. You should see the following dialog, indicating the location of the files that are ready to attach. 

Ensure that the name to attach the database is SiriusSQL_Training (in the Attach As field) 

and the owner of the newly attached database is still SA. You can modify either of these fields 

by double-clicking on the field and editing it. Click OK to attach the database. 

81

11. The last step is to give the user sirius access to the newly installed database. In Microsoft SQL 

Server Management Studio, expand Security on the left side of the screen and click Logins. 

You should see the user sirius listed. 

82

12. Right-click on the user sirius and select Properties. 

13. Click User Mapping and ensure that there is a checkmark in the Map column next to 

SiriusSQL_Training. (You should now have checkmarks for both Siriusware databases, 

allowing this one user access to both databases.) Click OK. 

83

The training database is now in place and ready for use by the training versions of the 4.0 suite of 

applications. 

Installing with an “execution protection” capable processor 

This section discusses installing SysManager and ReportManager on Windows 2003 with SP 1 or 

Windows XP with SP 2 with an “execution protection” capable processor. 

Windows Server 2003 SP 1 

SP 1 for Windows Server 2003 and SP 2 for Windows XP utilize Data Execution Prevention for 

increased security. Date Execution Prevention, or DEP, as it is referred to, works in conjunction with 

84

some processors that have “execution protection” to mark certain areas of the system’s memory as 

unusable for executable files. In these instances it is necessary to exclude the SysManger and 

ReportManager executable files to allow these programs to function properly on these computers. 

To enable SysManager and ReportManager to work with DEP: 

1. Right-click on My Computer and select properties or go to the control panel and select 

System. (These two actions are equivalent.) You see the following screen: 

2. Click on the Advanced tab. 

3. Click on the Settings button in the Performance section. 

85

4. Click on the Data Execution Prevention tab. 

86

5. Click the radio button for Turn on DEP for all programs and services except those I select:. 

6. Click the Add... button at the bottom of the window and browse to the local SysManager folder 

and select Symanager.exe. Click Open. It adds the entry to the dialog. 

7. Repeat the process for the Reportmanager.exe and click Apply. 

8. A reboot of the system may be required for the changes to take effect. 

Note: Make sure the check boxes next to the application names are checked. 

87

Modifying a Salesware installation 

With the exception of the ServerFiles installer (which is an .EXE), you can run any Salesware .msi 

(Microsoft Installer) again after it has already been used to install the software. For example, if 

something is deleted after an install, it can be restored by using the Repair option of the installer. You 

are presented with options to Modify, Repair or Remove. Do not run the ServerFiles installer again. 

If you need to modify the Siriusware directory structure on the SQL Server, do it manually. If you 

need to attach a different database, do it manually, as described in Manually Attaching the SiriusSQL 

Database. 

Note: Can you run the new Salesware .msi (Microsoft Installer) installers on a system with the old 

(.exe-based) installs on them? Yes, but you must run the new CommonFiles installer first; it is a 

good practice to remove the old CommonFiles first. 

88

Uninstalling Salesware 

There are two steps to completely uninstalling Salesware from any computer: uninstalling the files and 

Windows registry settings that were installed by the installer, and deleting the files that were installed 

by the update file or by Salesware itself. These steps are described in this section. 

Warning: Before deleting Salesware from any computer, ensure that you have backed up any data or 

layouts that you need. This is especially true of your SQL Server database data. 

To uninstall Salesware: 

1. On the computer where Salesware is installed, go to Start > Control Panel > Add or Remove 

Programs. 

2. In the Add or Remove Programs dialog, all Salesware programs are sorted alphabetically in 

the same spot because they all start with “Siriusware.” Select an application that you would 

like to remove and click Remove. 

3. After you have removed all of the applications you wish to delete, close the Add or Remove 

Programs dialog and navigate to the Siriusware directory (usually located at C:\Program 

Files\Siriusware). If you deleted all Salesware programs from the Add or Remove 

Programs dialog, then you should delete the entire directory. If you deleted only certain 

applications, then delete only the associated directory, such as SysManager or Sales. 

Note: ODBC connections and the LOCATION environment variable must be manually un-installed. 

Installing Charge Cards 

The Charge Cards module in Salesware supports four systems: ProtoBase, DirectNET, Ingenico and 

CreditCheq. It also supports EZCharge cards, which are similar to In-House Cards except that the 

guest’s credit card is charged instead of having an amount subtracted from an in-house debit card. This 

section describes how to install and configure these systems. The vast majority of Siriusware clients 

use ProtoBase, so detailed configuration directions are provided for ProtoBase only; installation of the 

other Charge Card systems should follow the steps provided for ProtoBase, modifying where 

necessary (as explained in the DirectNET, Ingenico or CreditCheq section below). If you chose to 

install support for Salesware Charge Cards when you were installing the core Salesware modules (see 

Installation of core Salesware modules) your installation is expecting ProtoBase. If you are not 

implementing ProtoBase, then you need to modify as necessary, as explained in the following in the 

DirectNET, Ingenico or CreditCheq section. 

This section uses the following terminology: 

• Authorization – The process of verifying that the cardholder has sufficient credit left to pay for 

the transaction. This does not actually put the money in your bank. It does allocate the money 

from the person’s credit for 7 days, though. 

• Settlement – The process of collecting the money from all of your authorizations. 

• Issuer – This is the bank from which the cardholder receives his card. 

89

• Acquirer – A bank that has a business relationship with a merchant and receives all credit card 

transactions from that merchant; the acquirer gets the money and deposits it into the 

merchant’s bank. 

• Processor – A company that handles credit card transactions and batches for acquirers (e.g., 

PaymentTech, Moneris, 5 th /3 rd , Vital, etc.). 

• Integration – Siriusware codes to a single spec and the product with which Salesware integrates 

translates the single format that we send to the format required for any given number of 

processors (e.g., Tender Retail CreditCheq, Southern DataComm ProtoBase, etc). 

Installing and using ProtoBase Charge Cards 

General notes 

Follow this list of “to-do’s” to begin your implementation of ProtoBase. More specific information is 

given in Pre-install instructions. 

1. Contact your processing bank and tell them you’re switching to “high-speed ProtoBase” or let 

the new processing bank you choose know that you’ll be using high-speed ProtoBase – they 

may have to create new merchant IDs for this. You’ll need two merchant IDs – one for retail 

sales and one for E-Commerce sales. 

2. Once you have the merchant IDs, complete the MVP form twice – once for each merchant ID – 

and also complete the other two attached documents. 

3. Fax all the completed paperwork to Southern DataComm (ProtoBase’s parent company), 727- 

431-4411. 

4. It takes SDC about 10-12 business days to build and test your new merchant files. Then… 

5. SDC will contact you to schedule the remote implementation. It takes about two hours and 

happens over the phone and with VNC. 

6. SDC will bill you for their products after the implementation has been completed. 

Please observe the following when installing ProtoBase: 

1. Always change the default administrative login/pw (don’t use pbadmin/pbadmin). 

2. pbadm32 usually runs on the ProtoBase Server, but you don’t want everyone in the 

organization running it from there. Use RealVu instead, which runs remotely from other 

Computers but provides much of the same information. 

3. What are the typical reasons why totals don’t match in Salesware and pbadm32 (clients 

should check this when they close out each day)? 

• Someone added a transaction in pbadm32 

• Salespoint times out – transaction went through but Salespoint thinks it didn’t, so CC is 

used again. Change the timeout value with the ProtobaseTimeout .INI setting. 

4. Any network using ProtoBase should be protected by a firewall. 

5. The key technology behind ProtoBase is the “soft-trans module,” which interfaces between 

client networks and the various credit card processors. 

6. It is important that your merchant file is correct. The primary merchant types are: 

• Retail 

90

• Food service (allows tipping) 

• MOTO – Mail Order Telephone Order (E-Commerce) 

Note: If your merchant type is wrong, you may be paying too much for each transaction. 

7. The cost of each transaction ultimately depends on how much risk the credit card companies 

are taking. The more information collected about the credit card and user, the less risk to the 

credit card company, so the less they charge for a transaction. If clients have risky practices, 

they are downgraded, so they pay more per transaction. You definitely need to do address 

verification in E-Commerce. 

8. When you void a transaction, it prevents it from being settled. (Versus a refund.) 

Pre-install instructions 

Scheduling the installation of ProtoBase with Southern DataComm (SDC) 

It is your responsibility to ensure ProtoBase is installed at your site prior to the Salesware 

implementation. 

You should have already received your ProtoBase forms from your Siriusware salesperson, and been 

CCed on an e-mail to SDC initiating the order. If not, please contact your salesperson. 

Submit your ProtoBase forms as soon as possible. Our experience is that it can take up to four weeks 

after submission before SDC schedules an installation. Please follow the ProtoBase MVP instructions 

carefully or delays occur. 

A specific reminder: if changing from dialup to high speed, you must call your processing bank. 

If your Siriusware installation is closer than four weeks away, we advise you to pay SDC to expedite 

($100/MID for 3-5 day service; $300/MID for 48 hour service.) You must do this when you submit 

your forms. 

Once your forms are processed, SDC schedules installation of and training for the ProtoBase system 

with you. Please schedule this prior to the Salesware implementation. SDC needs to know: 

• Date and time of install. Remind them to schedule training, also (about 1.5 hours). 

• Name of onsite contact and phone number. 

• Name and address of person who should receive the modem and welcome packet. 

• IP address, user name and password for your ProtoBase PC. This is explained in SDC’s 

welcome packet. 

91

SDC tells you the ticket number for the installation; please take note of it for future reference. 

For the status of an order, the best contact is siteact@protobase.com. When you receive the 

notification that your order has been received by SDC, they ask you to use this e-mail for status 

reports. 

When SDC does the install, you may want to consider asking them to also install RealVu. RealVu is a 

free ProtoBase product that enables settlement from computers other than the Computer where 

PBAdmin is installed (which is the ProtoBase server). RealVu offloads most of the overhead of 

running PbAdmin directly on the ProtoBase computer. 

SDC provides training on use of PBAdmin; please be sure they schedule that with you. 

If you have questions, please contact: 

Lori Rich 

727-431-4539 

lrich@protobase.com 

10700 76th Court 

Largo, FL 33777 

Fax (727)431-4411 

Setting up your hardware and network prior to the ProtoBase installation date: 

On the ProtoBase PC: 

• Configure the PC with the static IP address that you provided to SDC. 

• Ensure the PC connects with the Internet. 

• Install the latest Windows SP and critical updates. 

• Install WinZip. 

• Install PCAnywhere, Terminal Services, or Remote Desktop Connection. 

• If using a firewall on your network, be sure port 443 is open to allow outgoing traffic. Port 443 

does not need to be open to allow ingoing traffic. 

See the Salesware System Architecture and Specifications document for a diagram showing how the 

ProtoBase server integrates with the rest of the Salesware installation. 

92

ProtoBase Installation 

ProtoBase installation is normally performed by ProtoBase technicians. This section provides a brief 

overview of the installation process and components. 

ProtoBase is installed on a dedicated computer with a static IP address. It is usually installed at the 

root of the C: drive: 

C:\PB 

ProtoBase also implements several Environment variables, as shown in the following screen capture. 

PbAdmin is the primary user interface to ProtoBase. It runs on the ProtoBase server and is used for all 

administrative tasks. However, many clients implement RealVu, which is graphical user interface 

software for PbAdmin that runs on computers remote to the ProtoBase server. You should run RealVu 

in such a way that it doesn’t add to the load on the ProtoBase server, such as over a Virtual Private 

Network (VPN). 

93

Configuring ProtoBase for Salesware 

Once ProtoBase is installed, you need to configure your salespoints to “talk” to ProtoBase. This is 

done by: 

1. Inserting the appropriate settings from ProtoBase into each salespoint. 

2. Inserting the IP address of the ProtoBase computer into the local Sales32c.INI files. 

3. Creating payment types for credit cards. 

Configuring the salespoint credit card settings 

You set the terminal ID for ProtoBase in either SysManager or Sales. In SysManager, go to Activities 

> System Lists > Salespoints and edit each salespoint. From the Salespoint Configuration dialog, 

click the Credit Cards tab. 

In Sales, go to Tools > Credit Cards > General Setup. The Credit Cards Setup dialog is 

displayed. 

94

Enter the appropriate code (typically 3 or 4 characters) provided by ProtoBase in the Credit Card 

Terminal field (in SysManager, this field is called Terminal No). The value in Credit Card 

Terminal cannot be more than 4 characters. Be sure to also enter the appropriate Merchant ID # for 

each salespoint. 

You should also set an “assumed approval” amount for each salespoint. If ProtoBase is offline for 

some reason, this is the amount that the system assumes is approved. See ProtoBase offline 

transactions for a complete description of how Salesware handles transactions when ProtoBase goes 

offline, and how Salesware recovers after ProtoBase comes back online. 

If a card is being charged for an amount that is over the “assumed approval” amount and ProtoBase is 

offline, the operator is prompted to call to get a voice authorization. Once the operator receives the 

voice authorization, she needs to type it into the prompt in Sales that is waiting for the voice 

authorization entry. 

When setting this limit keep in mind the amount you are willing to lose should a card that was 

assumed to be good was declined once it was forwarded for a real authorization. Also, please ensure 

that your operators have access to the phone numbers and information they need for voice 

authorizations. 

95

Inserting the IP address of the ProtoBase server 

Enter the IP address of the ProtoBase computer in the Sales32c.INI file on all salespoints. This 

must be done in the local Sales32c.INI file – not within the global .INI in SysManager > 

Preferences > Miscellaneous > Global Salespoint INI. Browse to the Sales32c.INI file. The 

default location of this file is C:\Program Files\Siriusware\Sales\Sales32c.INI, but 

you can also get to it from Windows Start > All Programs > Siriusware > Settings. In the 

[Server] section there is an entry for Protobase=. Enter the IP address of the ProtoBase server 

followed by the port (default is 4209). If the IP address for the ProtoBase server is set in the 

SiteDefaults.INI file, this setting is automatically assigned when you install Sales on a 

salespoint. See Installing PoolManager for more information. You should also make sure that the 

CreditCardSales setting is set to TRUE. Without this set to TRUE, cards are not processed for 

authorizations when used for payment. This setting can also be automatically assigned when you 

install Sales. See Installing Sales for more information. 

Configure payment types 

96

You use SysManager > Activities > Financial Lists > Payment Types to configure payment types for 

each type of card you accept. With the Sales Point Type tab you can also limit what types of 

payments are available per salespoint type if necessary (this is one of the few remaining uses for the 

Salesware 3.x salespoint type functionality accessible from SysManager > Preferences > Sales Point 

Types – there is no other way to implement this functionality). 

The Process Via should be set to Protobase. The Card Type should be set according to the following 

table: 

Card Type field abbreviation 

AMEX 

CTBL 

DINR 

DISC 

ENRT 

JCB 

MACH 

VISA 

PRIV 

DBTW 

Card type 

American Express 

Carte Blanche 

Diners Club 

Discover 

En Route 

Japan Credit Bureau 

Master Charge 

Visa 

Not implemented yet 

Debitware (In-House Cards) – See the document Salesware 

In-House Cards 

Please use the BIN ranges (Acct Range) described in the following table. Most clients probably don’t 

need/want the JCB or BankCard entries. The table has the card, BIN ranges and the acceptable lengths 

of the card number. Acceptable lengths are provided for informational purposes only. They are 

handled automatically by Salesware; you do not need to configure them manually in Salesware. 

Card BIN range(s) Acceptable lengths of the card number 

American Express 340000-349999 370000- 15 

379999 

Visa 400000-499999 13 or 16 

MasterCard 510000-559999 16 

97

MasterCard (due to 

the new 

MasterCard/Diners 

Club alliance in North 

America) 

360000-369999 14 

Discover Card 601100-601199 650000-650999 16 

Diners Club 300000-305999 380000- 

389999 

Japan Credit Bureau 300000-399999 16 

Japan Credit Bureau 180000-180099 213100-213199 15 

BankCard 560000-561999 16 

14 

You can also enter a Payment Type Group for each payment type configured. This is used on reports 

to subtotal payment types configured with the same group number together. For example, Visa, 

MasterCard, Discover Card and American Express are all in group 3. The Cash Drawer Report shows 

the total for each payment type and it totals all payment types included in group 3 together so that you 

can see your total for these credit cards. 

Sort By impacts how the operator sees the payment types sorted in the finalize dialog in Sales (first by 

the Group number, then by the Sort By number). Even though credit cards are the most common form 

of payment next to cash, you do not need to sort these payment types to the top of the list. When using 

a credit card for payment in Sales, there is no need to select the payment type or even click the finalize 

button. Simply swipe the card and the system selects the appropriate payment type based on the card 

number swiped. 

98

ProtoBase settlement and Salesware reporting 

The basics 

Credit card payments made at a Siriusware salespoint are passed to ProtoBase for authorization from a 

credit card processor. Processors include companies such as Payment Tech, Vital, Moneris (Canadian 

E-Commerce only), etc. 

The settlement (deposit) of credit card transactions happens within ProtoBase via the PBAdmin or 

RealVu applications or within ProtoBase’s web product, WebVu. Settlement is a manual process, but 

is very easy. It requires the operator to enter the “deposit criteria,” which is typically just the current 

date, and click a Deposit Selected or Deposit All button. 

ProtoBase batches and subtotaling 

ProtoBase assigns the same batch number to all transactions deposited at the same time. It is possible 

to get a breakdown within the single large batch based on either Siriusware salespoint name or 

Siriusware operator name. 

By default, Siriusware provides the salespoint name to ProtoBase. The Siriusware salespoint name is 

inserted into the ProtoBase cashier ID field. Thus, by default, within a single ProtoBase batch the 

individual transactions and subtotals per Siriusware salespoint may be viewed. 

99

Instead of using the Siriusware salespoint name for grouping transactions within a ProtoBase batch 

(default functionality), the Siriusware operator name may be sent into ProtoBase as the cashier ID. 

The individual credit card transactions and subtotals would then be viewed by Siriusware operator 

name instead of Siriusware salespoint name within ProtoBase batches. 

To specify sending in the Siriusware operator name instead of the salespoint name, a Sales .INI 

setting must be in place. It is recommended that this setting be inserted in the section 

of the global .INI (SysManager > Preferences > Miscellaneous > Global Salespoint INI tab) so 

that all salespoints follow this setting (the same setting needs to be removed from the local .INI file 

or from the global group sections in order to make the global default setting take effect). The global 

.INI is discussed in detail in the Salesware Modules, Configuration and Maintenance document. 

[Preferences] 

SettleByOperator=TRUE 

Sending in the Siriusware salespoint name or Siriusware operator name is a decision that must be 

made by you – specifically, by your accounting department, as this is the department that typically 

shoulders the responsibility for credit card activity and reconciliation. If a client typically reports by 

operator, then sending in the operator name to ProtoBase as the cashier ID might make sense. If a 

client typically reports by salespoint or salespoint group, then sending in the salespoint name to 

ProtoBase as the cashier ID might make more sense. Again – this decision must be made by the 

client. 

Note: In the past, Cardware (former name of Charge Cards module) batches were always reported by 

salespoint, so if you have used Cardware in the past, there may be more of a comfort level with 

reporting by salespoint name rather than operator name – thus the reason for the default setting of 

using salespoint name as the ProtoBase cashier ID. 

Additional settlement options 

Credit Card transactions in ProtoBase may be settled by Transaction Date or by Business Date: 

• The Transaction Date in ProtoBase is the date that the card was authorized. 

• The Business Date in ProtoBase corresponds to the “sale date” in Sales. Sale date may be 

altered via the set carryover functionality in Siriusware. 

Another option to use in determining what transactions to settle is terminal ID, which is set per 

salespoint in the Sales > Tools > Credit Cards > General Setup menu. One possibility is to give all 

salespoints within a given business area the same terminal ID (for example, tickets could be TIX, ski 

school could be SS, etc.) You can then settle by business date (sale date) and terminal ID, which 

would allow you to settle all transactions for the venue at one time. 

100

Report and selection comparisons options 

Various Siriusware reports can be run via ReportManager to compare with the credit card transaction 

information from ProtoBase. For example, if using the ProtoBase terminal ID to represent an 

operational venue, Siriusware reports such as the Daily Summary Report can be run via the salespoint 

group selection to compare to the settlement information. 

PBAdmin Selection 

Siriusware Designation 

Card Type 

Payment Type 

Business Date 

Sale Date 

Transaction Date 

Date Card was Authorized 

Terminal Credit Card Terminal (in Tools > Credit Cards > 

General Setup) 

Cashier ID 

Salespoint Name or Operator 

ProtoBase offline transactions 

This section describes how Salesware handles the situation when ProtoBase goes offline and when it 

comes back online. 

101

When ProtoBase goes offline, you cannot receive payment. You cannot receive payment without 

authorization, but authorizations do occur once ProtoBase is online again. This process can be 

automated or manual. The following sections describe the differences. 

Automated authorization when ProtoBase comes back online 

You can use the ForwardAuthOnReconnect .INI setting to automatically cause the salespoint 

to seek authorization of all stored credit card transactions upon reconnection with ProtoBase. 

[Preferences] 

ForwardAuthOnReconnect=TRUE 

This setting causes the forwarding of all offline ProtoBase credit card transactions when ProtoBase 

comes back online. This setting causes the operator to be prompted when ProtoBase is back online, 

allowing them to select whether or not to forward the offline transactions at the end of the finalize 

process. The default setting is FALSE. 

For example, if you're offline and collect 10 credit card transactions and then ProtoBase comes back 

online, all 10 transactions automatically get sent for authorization if the operator clicks OK at the 

prompt. The operator is given the choice in order to accommodate the situation where there is a long 

line of customers and the operator probably does not want to stop selling while the outstanding 

transactions process. 

Warning: Each transaction can take up to 2 minutes to process, so the authorization process could take 

quite a bit of time depending on the amount of stored transactions. 

If the operator clicks OK at the prompt, authorizations are sent and come back – good or declined – 

and credit card receipts come spitting out of the receipt printer. 

Note: Credit card receipts don’t automatically print when using ProtoBase. After the transactions 

process, the Processed Off-line Transactions dialog comes up. From there you can choose to print 

the receipts. Cardware, Siriusware’s earlier credit cards product, does automatically print the receipts, 

but any other credit card module behaves this way. 

When ProtoBase is offline and an approval is assumed (the amount depends on the amount of the 

“assumed approval” set for each salespoint), a regular credit card receipt prints (see previous note), but 

without an approval code (look for AP: on the credit card receipt and you see that it does not contain a 

real approval code). When ProtoBase is back online, these “assumed approval” sales are authorized 

and a new credit card receipt prints with the real authorization number (there is an entry next to AP: 

on the receipt), or the word “decline” is printed on the receipt if the transaction was not authorized. 

102

Your operators might think that something “crazy” is happening because they said OK to a prompt to 

forward offline credit card sales and suddenly the receipt printer started printing (see previous note) – 

but this is expected functionality. The operator simply needs to match up the credit card receipts with 

real approvals with those receipts that contain no approval, but have the guest signature. 

Manual authorization when ProtoBase comes back online 

If the operator clicks NO to the message described in the previous section, or if you do not want the 

authorizations to go out automatically, you can perform them manually. This can be done at the 

salespoint through the Tools > Credit Cards > Process Off-line button. When that button is pressed, 

the transactions are sent out for authorization. 

You do not see offline transactions that have not been processed in PbAdmin − but they are stored in 

the local cc_trans table. 

ProtoBase questions 

Is Cardware fully CISP compliant? Is data encrypted on the server? 

The term “Cardware” refers to Siriusware's own credit card processing software. Cardware was built 

for use in versions 3.2 – 3.4, and is not considered 100% CISP compliant. While some clients are still 

using Cardware, it is being phased out, and its functionality is now being provided by ProtoBase. 

ProtoBase offers a CISP compliant solution for both 3.4 and 4.0 users, and all credit card related data 

is encrypted in both Siriusware and ProtoBase applications. 

Who provides training for the new interface? Siriusware? Southern DataCom? What is 

covered by each? 

Training on ProtoBase applications is done by Southern DataCom. The training is usually done shortly 

after ProtoBase is installed. Siriusware provides assistance with setting up the necessary settings in 

Sales and SysManager, as well as basic information on Siriusware credit card/payment reporting. 

Are calls placed to Southern Datacom for technician support responded to immediately or do 

we have to wait for a return call? What is the response time? 

Southern DataCom’s technical support is similar to Siriusware’s in that emergency situations move to 

the front of the queue and are responded to immediately. Non-emergency calls may be responded to 

with a return call. I recommend calling Southern DataCom directly to inquire about their technical 

support process. Their number is 877.732.1799. For more information about troubleshooting 

103

ProtoBase, see the appendix titled “Using and troubleshooting ProtoBase” in the Salesware User 

Guide for Advanced Users. 

For the purpose of redundancy, does the modem service a limited number of salespoints? 

No. 

How is this configured? 

ProtoBase configures this; you must manually switch to the modem if your Internet connection fails. 

This involves double-clicking on a batch file. 

Is it automatic if Internet service fails? 

No, see previous. 

What are your recommendations for transmitting batches to our processor in lieu of not 

having the ability to schedule batches automatically? 

Automated scheduling was required in the old Cardware system due to the limitation that batches 

could not be processed at the same time that authorizations were being actively sought. In other words, 

live authorizations would halt while the batch went out for settlement. 

Using ProtoBase, this is no longer an issue. You are able to simultaneously settle batches and seek 

authorization. This eliminates the need for after-hours auto-settlement. Clients using ProtoBase have 

different processes for batch settlement; some process in the evenings at day close, others process 

batches the next day. 

What if the batch is forwarded to the processor before all sales for the day have been 

completed? 

Remaining sales are included in a new batch. 

Explain the ProtoBase reporting interface with Siriusware. How does the ProtoBase software 

interface differ from Cardware? Is the same information provided? 

ProtoBase users are still able to use Salesware’s Individual Card Search Report in ReportManager to 

look up transactional information by cardholder name or credit card number. The Batch Detail Report 

104

can also be utilized to get a summary report of credit card totals by salespoint/operator. All batch 

settlement reports are done in ProtoBase applications. 

Does each close out’s credit card batch show as a separate batch still in ProtoBase, and if so 

where, if we need to do research? 

All transactions show up in one batch; however, you can get breakout reports by salespoint or 

operator. 

An interruption in service in which the cause could not be identified seems to be a common 

occurrence with existing ProtoBase customers. How do we handle situations when 

ProtoBase is offline? Or when Salesware times out due to not receiving a timely response 

from ProtoBase? What procedures should the seller's institute? 

Please see ProtoBase offline transactions. 

How are offline transactions settled? 

Please see ProtoBase offline transactions. 

What if transactions are lost? How are they retrieved? 

The only way we can think of where a CC transaction would be “lost” is if ProtoBase is offline, and 

the locally stored data was deleted. In that instance, the data has been deleted, so recovery is not 

possible. 

How are specific sales tracked and reported? Can they be identified by salespoint? By 

operator? By date? By item? 

The Cash Drawer Report still provides the same information as always: what was sold, where, by 

whom, and how it was paid for. You can also use the Individual Card Search Report in 

ReportManager. 

If batches are transmitted via one large sum rather than by salespoint, how do we 

troubleshoot and identify batches by terminal and the detail within each terminal’s 

transactions? 

See ProtoBase settlement and Salesware reporting. 

105

Are separate batches submitted for each merchant ID number? We have three merchant ID 

numbers, one for each company. 

Transactions from multiple merchant ID locations are processed as part of the same batch, but are 

marked (and can be reported) by their individual merchant IDs. Please ensure that your multiple 

merchant ID numbers are programmed by ProtoBase. 

Can batches be transmitted by salespoint, transaction date, or filtered any other way? 

See ProtoBase settlement and Salesware reporting. 

What method do you recommend we use for reconciling batches? 

While we do not have a recommend procedure, most clients compare the ProtoBase settlement reports 

against their bank statement and Daily Summary Report. 

What is the reporting process In lieu of seller's not being able to print a close batch report? 

Using ProtoBase, closing the batch at the salespoint is optional. The station’s CC transactions are 

forwarded to ProtoBase, regardless whether the batch is closed or not at the salespoint. 

However, “closing the batch” is something a misnomer. No batch is closed by hitting a button. The 

only reason to “close the batch” with ProtoBase is to get a list of the CC transactions for the logged in 

operator. 

Note: If the previous day’s transactions have not been settled, they show on this list as well as the 

current day’s. This is a very common technical support call from those who use the Close Out button 

in Sales > Tools and ProtoBase. The client calls and says the list doesn't agree with what the operator 

did today. The query that runs to furnish the list is based on the currently open batch in Protobase. 

If you are interested in retrieving a daily summary of a station’s CC activity, going to Sales > Tools > 

Credit Cards > Close Batch gives you a brief printable report. Alternatively, you could run the Batch 

Detail Report in ReportManager and get the same information, but it also includes card numbers and 

other sensitive CC information. 

How are seller's transactions audited at end of day? 

See previous. Also, you can use the Close Drawer Report if you are interested in CC totals. 

106

Can the batches be transmitted while salespoints are live and selling? 

Yes. 

Can the batches be transmitted concurrently while the back-up is running? 

This depends on how you do your backups; we recommend contacting ProtoBase. 

What happens if a batch is transmitted the following day after that day's sales have been 

started? 

This is not a problem – you can use the transaction or business date for settlement. 

What information is printed on the credit card receipt? Salespoint? Date? Customer name? 

Item? Approval code? 

All of the above can still be printed on the credit card receipt. The credit card number is partially 

masked and the expiration date is no longer allowed to be printed per CISP compliancy rules. You 

need a new receipt layout from Siriusware. 

Installing DirectNet Charge Cards 

The basic process for installing DirectNet Charge Cards is similar to installing ProtoBase, in terms of 

the basic configuration steps that are performed in Salesware. See Configuring ProtoBase for 

Salesware and modify as appropriate. In addition, the following sections call out the DirectNetspecific 

information of which you should be aware. 

DirectNet .INI settings 

For more information on these settings, see the Salesware Modules, Configuration and Maintenance 

document. 

Setting .INI file Section Desciption 

DirectNet Sales32c.INI Server The IP address and port of the 

DirectNet server. Port is 3200. 

DirectNetValidate Sales32c.INI Preferences Specifies whether or not to use 

DirectNet to validate passes (if 

107

the pass number qualifies as a 

DirectNet number). Default is 

FALSE. 

CheckAvailableFunds Sales32c.INI Preferences To enable balance inquiry for 

DirectNet private label cards to 

ensure sufficient funds prior to 

finalizing the sale. Must be set to 

TRUE. 

DirectNetGiftCardTotals Sales32c.INI Preferences Used to include the DirectNet gift 

card amounts in the “other” 

category for batch settlement. 

Note: A DirectNet gift card is 

specified by selecting PRIV as 

the card type. 

RangeX Sales32c.INI DirectNet Any card swiped in the validation 

dialog that falls into these ranges 

is treated as a DirectNet card. 

These ranges must be 15 digits in 

length. Any number of ranges 

may be set, but must be set in 

order − e.g., Range1, Range2, 

Range3, etc. 

Note: [Preferences] 

DirectNetValidate=TRUE 

must be set. 

FrontCard=TRUE Sales32c.INI DirectNetLink If FALSE, creates a non-front 

card account (allows DirectNet 

account creation without 

associating a credit card with it). 

IP Sales32c.INI DirectNetLink IP address of the DirectNet nontransactional 

API server. If IP 

setting is present, a file called 

DN_Link.dbf is created and 

holds information about 

DirectNet accounts that need to 

be created through the DirectNet 

non-transactional API. This 

process keys off a field in 

template (t_newdnact) (which 

can be filled in SysManager) if 

the swipe_no field has been 

filled in. 

108

Password Sales32c.INI DirectNetLink Password that accesses DirectNet 

Port Sales32c.INI DirectNetLink Port for DirectNet nontransactional 

API 

Timeout Sales32c.INI DirectNetLink Timeout in call to DirectNet 

UserName Sales32c.INI DirectNetLink Login name that accesses 

DirectNet 

Layouts 

The table below describes the fields available to print for layouts. 

Table name 

ccauth.dbf, 

operators.dbf, 

sales_pt.dbf 

Description 

Tables that are available for CC receipts. In ccauth.dbf there is 

a field called prtmsg that should be used. 

Security 

The following security setting is used with DirectNet. See the Salesware User and Ticketing Guide for 

Beginning Users for a detailed description of security settings and security roles in Salesware. 

SysManager - Menu/Preferences - DirectNet Interface = Allows the operator access to DirectNet 

interface set-up info. 

Licensing 

SysManager > Preferences > Sales Point Licenses > DN column = The number of sales points 

licensed to use DirectNet 

Miscellaneous notes 

• If you use repeat terminal IDs under the same merchant #, you are not able to settle batches 

(but repeat terminal IDs under different merchant #s are OK). For example, 

term ID=102, merch ID=1802 

term ID=102, merch ID=1805 

109

is perfectly fine. 

• Use: 

[Server] 

DirectNet=127.0.0.1:3200 

• You need to close the batch from within Sales (like CreditCheq, but not like ProtoBase, which 

uses PBAdmin). 

• Batches must be settled daily from each salespoint – otherwise, you can’t settle them later. 

Installing Ingenico Charge Cards 

The basic process for installing Ingenico Charge Cards is similar to installing ProtoBase, in terms of 

the basic configuration steps that are performed in Salesware. See Configuring ProtoBase for 

Salesware and modify as appropriate. In addition, the following sections call out the Ingenico-specific 

information of which you should be aware. 

General notes 

• You have to install PCEftpos software ( two pieces - EFTServer and EFTClient) on each 

salespoint (card present transactions) 

• EFTPOS works on a dedicated modem, shared modem or argent line (DSL line with constant 

connection) 

• PinPads are programmed from the bank and must connect without error to EFT software before 

testing in Siriusware. A PinPad, when plugged in, indicates on-creen whether it is 

communicating with the client (via a comm port). Also, PinPad operation can be tested in 

EFTclient by going to the EFT client control panel and hitting the Logon button. If Logon is 

successful, then the PinPad can connect to the bank and get authorizations. This should be 

verified first before trying a transaction is Sales. 

• EFTClient holds merchant and terminal ID information. 

• PinPad is programmed with merchant and terminal ID at the bank – be certain its settings 

match the settings in the EFTClient. 

• Run client diagnostics to troubleshoot setup of the EFTPos system. 

• You have to purchase and install OCV server software for E-Commerce on the “OSC Server” 

(card-not-present transactions). 

• All debit cards can now be processed via EFTPOS − PC-EFTPOS now only parses out track 1 

information (e.g., cardholder name) if the track 1 is encoded properly. 

How Ingenico works with Salesware 

110

1. The operator clicks the Finalize button and selects the payment type (Visa, Master Card, 

American Express, bank card, etc.). 

2. The operator receives a message for the guest to swipe his/her card. 

3. The guest swipes a credit or debit card into the terminal (PinPad). 

4. The operator receives a “select account” message. 

5. The guest selects “account type,” which is basically a bank account (checking) or credit. 

6. The operator may or may not receive a prompt for guest to enter his PIN based on account type 

selected and the guest may or may not need to enter PIN based on account type selected. 

7. If “checking” was selected, then the operator receives a prompt for the guest to enter his PIN 

(same message appears on the PinPad). 

8. If the guest selected “credit,” the operator is prompted to “check signature” and must say OK 

prior to the transaction completion. 

9. There are no Sales > Tools > Credit Cards > General Setup configurations in Salesware 

software except for the Assume Approvals if Invoice Amount Tools > 

Credit Cards > Close Batch (which really just accesses the PCEftpos software – so settlement 

can also be manually done directly through that software). Only one settlement can be done in 

a 24-hour period (either manual or automatic). 

How Ingenico works with SysManager 

Configure credit card payment types to process via Ingenico. See Configuring ProtoBase for 

Salesware for more information on how this is done for Charge Cards in general. 

Bank Cards can use the card type PRIV (although it doesn’t really matter). 

Uses the Salesware credit card layout in SysManager > Preferences > Miscellaneous. 

How Ingenico works with Sales 

Add the following .INI setting. 

[Preferences] 

PCEftpos=TRUE 

Will not work with MOTO=TRUE (you get a message). 

PCEftpos software must be running for everything to work. Some sample screenshots of what this 

looks like: 

111

You can access PCEftpos software configuration from the task tray (red or green depending on server 

connection). 

Sales Host settings for E-Commerce 

112

[Preferences] 

OCV=TRUE 

MOTO=TRUE 

[Server] 

OCV=127.0.0.1:3005 

[Salespoint] 

Interface=Web 

Call center salespoints all talk to an OCV Server. The server has to have the OCV server software 

installed and one supported PinPad installed. The hardware on the server requires two comm. ports – 

one for the PinPad and one for the modem. From one PinPad, many “virtual” PinPads can be installed 

(corresponding to each salespoint that needs to process). Setup in Salesware can include offline 

processing, but there is no override if the Assume Approvals if Invoice Amount

To integrate with web Sales Host for the second part of E-Commerce credit card processing: Added 

OCV=TRUE and MOTO=TRUE to [Preferences] section of Sales32c.INI file; added OCV=< 

IP address and port of OCV server> to [Server] section of Sales32c.INI file; in 

web Sales Host > Tools > Credit Cards > General Setup: Merchant ID Selector set to 00, 

Merchant ID set to 12345678 (must agree with TerminalID registry setting for ww.dll), 

Credit Card Terminal set to 0 (must agree with AccountID registry setting for ww.dll). 

Note: Merchant ID and Merchant ID Selector may need to be set up for the web Sales Host 

Salespoint in SysManager > Activities > System Lists > Salespoints > Salespoint Configuration 

Form > Credit Cards tab if they are greyed out in Sales. 

Web.config settings 

Use device type of 17 for credit card processing. 

Merchant or Account ID setting can be added that overrides the setting in the ww.dll registry 

(important for being able to process web transactions done through different installs of the pages with 

a different merchant number): 

 

 

Installing CreditCheq Cards 

Note: Tender Retail is a third-party application that communicates from Salesware to Moneris and 

back. 

Pre-Install Checklist 

1. You must contact Connections Canada, Inc. to arrange for a VPN tunnel on their existing high 

speed connection from each salespoint. Contact: Roy Grant (905) 844-1661, 

roy.grant@cciint.com This requires you to submit information to CCI on their form and also 

requires the presence of qualified technical help to set the VPN connection once CCI 

establishes it. CCI may provide this help if you have none, available at $150/hour. Ping as 

appropriate Moneris East, 10.250.4.3; Moneris Central 10.250.4.2; Moneris West 10.250.4.4; 

Moneris Test 10.250.4.1 to test the connection. This IP is located at CCI and routes the 

communication to Moneris. 

114

2. From Moneris: Merchant ID; ECR numbers for each PinPad; Ingenico PinSmart devices. 

Contact: Client should already have a contact, but if not, George Smith (604) 658-2055 

george.v.smith@moneris.com. 

3. Tender Retail .dll’s are installed with the Sales32c install and nothing is needed directly 

from them. Contact: Mike Loftus (416) 498-1200 x22 mikel@tender-retail.com should there be 

any problems. 

Install - Setup 

1. In SysManager, make sure all required charge card payment types are set up with number 

ranges and Process Via CreditCheq. See Configuring ProtoBase for Salesware for more 

information on how this dialog is used. 

115

2. Create a Debit Card payment type (Interac cards) with a number range from 000000 to 

999999, Process Via CreditCheq and check Debit Card. See Configuring ProtoBase for 

Salesware for more information on how this dialog is used. 

3. Do not specify a CC layout in SysManager > Preferences > Miscellaneous. The layout is 

taken care of with the CreditCheq install files. 

4. Connect the PinSmart device to power and the salespoint serial port. The display shows a 

version number and other numbers. 

5. Ensure that the computer keyboard is configured for English if a keyboard swipe is being used 

for charge card swiping. A French keyboard configuration will put ? for a separator instead of 

^ and make the swipe unreadable by the software. Note that the keyboard swipe processes 

charge cards faster than if the PinSmart swipe is used. 

6. For each salespoint make the following entries in the Sales32c.INI or global .INI: 

[Preferences] 

CreditCheq=TRUE 

[Server] 

CreditCardSales=TRUE 

7. Start Sales and open Tools > Credit Cards > CreditCheq Setup. 

116

• Host: Processing bank. Is usually as shown above. 

• IP Address: Correct CCI/Moneris IP for that region of Canada from #1 in the Pre-Install 

Checklist. 

• Terminal ID: Enter the Debit ECR number provided by Moneris and linked to the 

PinSmart that is installed on that salespoint. It should start with 6600 or 6601. 

• Aux. Info #1: Enter the 13 digit merchant ID number supplied by Moneris. 

• Aux. Info #2: Enter the floor limit or assume approvals limit for this sales point should it 

go offline. 

• Aux Info #6: Enter the Credit ECR number provided by Moneris and linked to the 

PinSmart that is installed on that salespoint. 

• PINPad Port: The comm port to which the PinSmart is connected on this salespoint. 

• All other entries are as shown above. 

117

• Accepted Card Types: Check as appropriate. 

• Miscellaneous: Check Diagnostic to create a log when troubleshooting errors. Ordinarily 

left unchecked. 

• Printer Settings: Check boxes as appropriate. Enter Trailing Linefeeds to position proper 

receipt cut point. Enter required Number of receipt Copies. Enter your info for receipt 

Header. 

118

• Default Language: Specify the language to be displayed on Sales screen when processing 

credit card authorizations. The receipt language is determined by the bank that issues a 

particular charge or debit card and will print automatically. 

• Cut Code: Check if receipt printer has a cutter and select the printer from the dropdown. 

• Specify any Footer information to match the default language. 

• Save all the entries made to the three tabs. A message at the bottom of the Sales screen 

indicates that the settings are being initialized. 

119

8. After saving the entries to CreditCheq setup, click Initialize PinPad to contact Moneris and 

initialize the PinPad. A successful initialization will show progress for the following at the 

bottom of the Sales screen: 

• Processing. 

• Sending packets with several different sequential numbers (this is for the first ECR 

number. 

• Indication of success. 

• Sending packets with several different sequential numbers (this is for the second ECR 

number). 

• Indication of success. 

If unsuccessful, check for the correct IP address and that the ECR numbers are in the right fields. Also 

switch the ECR numbers between the two fields. 

Once successful, the PinPad display window should show Welcome/BonJour in place of numbers 

previously displayed. 

Credit card transactions can be swiped without clicking Finalize using an external mag swipe or 

Cherry keyboard as with U.S. credit card transactions. They can also be swiped using the PinPad 

although processing tends to be slower. The PinPad must be used for debit card transactions: Finalize 

> select debit card form of payment > follow instruction on Sales screen and PinPad display. 

Configuring EZCharge 

EZCharge cards are similar to In-House Cards except that the guest’s credit card is charged instead of 

having an amount subtracted from an in-house debit card. To set up an EZCharge card, you assign a 

16-digit number to the card as you would with an In-House Cards card, but with a non-In-House Cards 

number so that it doesn’t trigger creation of an In-House Cards account. There are two separate 

sequences of steps to follow to set up EZCharge cards: 

120

1. Set up from SysManager. See To set up EZCharge from SysManager:. 

2. Set up from Sales. To set up EZCharge from Sales:. 

To set up EZCharge from SysManager: 

1. Configure an item to create a pass. 

2. On the Starting Values tab in the Action Specifics, check the box to Assign number from 

basket and specify the basket number you want to use. 

a. You need to ensure that your assignno table is populated with valid numbers for the 

basket you specified. 

b. You need to ensure that the basket you pick is not in the In-House Cards range of numbers 

(beginning with 9840 or 603524 are hard-coded). 

3. On the Auto Pass Validate tab in the Action Specifics, check the box Pass will be Resort 

Charge Capable. 

4. Specify the card range as an EZCharge card: 

a. Go to Activities > System Lists > Card Activity Definitions. 

b. Verify that the card range (basket) that you have selected does not conflict with any 

existing card activity definition. 

c. Create/modify a Card Activity Definition: 

1. Specify a Description (e.g., EZCHARGE). 

2. Specify a Prefix (e.g., the first 8 numbers in the card range). The number of digits you 

specify is a variable and can be set in the Sales32c.INI file − it defaults to 9 digits 

if not specified. 

3. Select EZ Charge from the dropdown box. 

4. Specify the starting and ending values (15 digits) for the card Range (e.g., 

446148500000000, 446144859999999). 

5. Click Save. 

To set up EZCharge from Sales: 

1. Specify the number of digits you used as a prefix in 3.c.2, above, by adding 

CardActionDigits=X (e.g., CardActionDigits=8) to the [Preferences] section 

of your Sales32c.INI file. 

2. Start (or re-start) Sales. 

3. Go to Tools > Data Files and refresh the card_act table. 

4. Sell the pass item you created for an EZCharge card and finalize. 

Note: Make sure you have a credit card associated with the guest (i.e., when you attach a guest to the 

EZCharge item, make sure that the guest has a valid credit card in the box under the CC-Swipe 

button). 

5. Go into your gst_pass table and retrieve the swipe_no value for the newly created 

EZCharge pass. 

6. Create a new sale with any random item. 

7. Bring up the Swipe Injection dialog (%AAAA). 

121

8. Enter your EZCharge number with %B at the begining (e.g., % B4461448500000372?) and 

click OK. 

9. This should bring up the credit card dialog with the credit card number associated with the 

guest. 

10. Finalize the sale. 

11. Perform a guest lookup for that guest and hit the History button. 

12. Find the sale (sort by date to make it easy) and double-click it. 

13. Verify that the item you sold and put on your EZCharge card is there. 

Note: Steps 5 through 13 in Sales are basically for manually testing the program. The swipe_no 

should normally be coded in the mag swipe so you can swipe the EZ charge card (instead of the real 

credit card). 

122

MASTER_40_Salesware_Installation_Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?