MASTER_40_Salesware_Installation_Guide

More documents

Recommendations

Info

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
Page 1 and 2:
Salesware Installation Guide SALESW
Page 3 and 4:
Siriusware examined the worst probl
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 31 and 32:
Page 33 and 34:
7. After PoolManager installation b
Page 35 and 36:
After PoolManager is installed, you
Page 37 and 38:
Page 39 and 40:
7. After SysManager installation be
Page 41 and 42:
directly from the \SiriusFS\Install
Page 43 and 44: 6. You are presented with the follo
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: ProtoBase Installation ProtoBase in
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?