MASTER_40_Salesware_Installation_Guide

More documents

Recommendations

Info

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
Page 1: Salesware Installation Guide SALESW
Page 5 and 6: files associated with each module,
Page 7 and 8: ports.INI file PDF documentation se
Page 9 and 10: Note: If you want to install SQL Se
Page 11 and 12: Note: If SQL Server Management Stud
Page 13 and 14: The SQL service pack level is liste
Page 15 and 16: Verifying mixed mode authentication
Page 17 and 18: If Windows only was selected, you n
Page 19 and 20: If Windows Authentication mode was
Page 21 and 22: 7. You are presented with the follo
Page 23 and 24: 10. You are presented with the foll
Page 25 and 26: 13. You are presented with the foll
Page 27 and 28: • Writes shared information to th
Page 29 and 30: 7. When CommonFiles is finished ins
Page 33 and 34: 7. After PoolManager installation b
Page 35 and 36: After PoolManager is installed, you
Page 39 and 40: 7. After SysManager installation be
Page 41 and 42: directly from the \SiriusFS\Install
Page 45 and 46: You can launch ReportManager from t
Page 51 and 52: 8. When the Sales installation comp
Page 53 and 54:
The next screen can prompt you in o
Page 55 and 56:
Note: The directions provided in th
Page 57 and 58:
4. You should see the following scr
Page 59 and 60:
8. Right-click on the user sirius a
Page 61 and 62:
11. The SQL Server Login Properties
Page 63 and 64:
13. You are prompted to confirm the
Page 65 and 66:
3. Right-click on Databases and sel
Page 67 and 68:
8. Click OK. Now your database is a
Page 69 and 70:
12. Click OK. Your database is now
Page 71 and 72:
Note: Much of the information you a
Page 73 and 74:
9. The Attach Database - (LOCAL) di
Page 75 and 76:
13. Right-click on the user sirius
Page 77 and 78:
The training database is now in pla
Page 79 and 80:
Note: The training database must re
Page 81 and 82:
10. You should see the following di
Page 83 and 84:
12. Right-click on the user sirius
Page 85 and 86:
some processors that have “execut
Page 87 and 88:
5. Click the radio button for Turn
Page 89 and 90:
Uninstalling Salesware There are tw
Page 91 and 92:
• Food service (allows tipping)
Page 93 and 94:
ProtoBase Installation ProtoBase in
Page 95 and 96:
Enter the appropriate code (typical
Page 97 and 98:
You use SysManager > Activities > F
Page 99 and 100:
ProtoBase settlement and Salesware
Page 101 and 102:
Report and selection comparisons op
Page 103 and 104:
Your operators might think that som
Page 105 and 106:
can also be utilized to get a summa
Page 107 and 108:
Can the batches be transmitted whil
Page 109 and 110:
Password Sales32c.INI DirectNetLink
Page 111 and 112:
1. The operator clicks the Finalize
Page 113 and 114:
[Preferences] OCV=TRUE MOTO=TRUE [S
Page 115 and 116:
2. From Moneris: Merchant ID; ECR n
Page 117 and 118:
• Host: Processing bank. Is usual
Page 119 and 120:
• Default Language: Specify the l
Page 121 and 122:
1. Set up from SysManager. See To s
show all

MASTER_40_Salesware_Installation_Guide

Create successful ePaper yourself

Delete template?

Save as template?