Implementation Process

Unless noted, the steps in this Implementation Guide apply to both NAB OPI Pay and NAB RES 3700 Driver products. The NAB RES 3700 Driver may also be referred to as the Canab Driver.

For information about reading logs, please refer to the Log Reading Guide.

Terminology

Terminal: PIN-pad/card reader device that accepts payment card input.
Workstation: The location of the computer with POS software where restaurant orders are entered.

The following steps should be completed prior to beginning the installation.

Before you start:

To request access to installation files, please submit a request to hospitality-support@nabancard.com.
This process includes content and files that must not be shared after installation is complete. Unless strictly necessary, do not share the installation files at all, and delete them after installation is complete.
This process is intended for users with some familiarity with RES.
Basic protocol should be followed, such as saving after each step and reloading the Micros control panel. If more information is needed about the Micros POS Configurator operation, please see the user guide published by Micros.
Though OPI installation is outside the scope of this guide, there are several items to note when dealing with setup and configuration. For information about OPI installation, please consult Oracle documentation.

IMPORTANT:

The current Oracle OPI version is 19.2
The object numbers must match those specified in this guide. If something else is already using that object number, its object number needs to be changed to something else.
The NabOpiPay (NOP) service may give errors when either starting or stopping. If Windows gives an error when you stop or start the service, push OK to the error, wait a moment, then refresh (F5 button) the services window. The service should have either started or stopped by that point.
NAB Micros RES 3700 does not currently support unique MIDs per Revenue Center (RVC), or Multi-MIDs per System.
Ingenico devices must be running EPXPay 4.65.
Ensure the API call for refunds is enabled in EPI.
If a PAX device is being used, the steps in the BroadPOS Setup section must be followed. This is required whether NAB OPI Pay and/or RES 3700 is being used. Only when a PAX device is not being used can the BroadPOS Setup section be skipped.

OPI Patching

OPI patches are not cumulative, but are instead additive. Therefore each patch must be run in order. To confirm that OPI was patched correctly, find the checkbox called "Enable TLS" on the PSP Configuration tab while Communication Mode is set to Terminal. If this checkbox is not visible, OPI was not patched correctly.

Mode Options

Our software can support either terminal mode or middleware mode. In either terminal or middleware mode, unless you've enabled Tls in NabOpiPay, Enable TLS in OPI must be unchecked. To do this in middleware mode, you must switch to terminal mode, uncheck Enable TLS, save, and then swap back to middleware mode.

Terminal Mode

If you choose to use terminal mode, NabOpiPay must be installed on every Micros workstation that is using a terminal. Every instance of NabOpiPay should have a separate terminals.json file that contains the necessary setup information for the PIN-pad that would be used by that Micros workstation. The terminal setup in OPI configuration should not be setup with the IP addresses of the PIN-pads, but instead with the IP addresses of the workstations that have NabOpiPay installed on them. The Terminal Port must be set to 6443. If a workstation is not running a Windows 64 bit operating system, or lacks the computing power (i.e., the Workstation 6 model 610), running NabOpiPay on it may be slow or not possible.

Middleware Mode

If you choose to use middleware mode, NabOpiPay must be installed on a single Win64 machine (typically the CAPS machine). The terminals.json file on that machine should include every workstation and PIN-pad. The Primary Host in OPI configuration should be http://{IP Address of the NabOpiPay machine}:6443, i.e., something like http://192.168.100.250:6443. Installation of NOP on Oracle Linux Workstations is not supported as is.

BroadPOS Setup

Navigate to https://secure.broadpos.com and log in.
Select My Terminals, then Add Terminal(SN).
Enter the terminal’s information.
Select the EPX Direct Restaurant Template and click Submit.
Make the following changes:
1. On EPX EMV fill in:
  1. CUST_NBR
  2. MERCH_NBR
  3. DBA_NBR
  4. TERMINAL_NBR
2. On the EMV tab:
  1. Set EMV Features/EMV Card Remove Beep to No Beep
  2. Set Credit EMV Parameters/PIN Bypass to Auto Bypass
3. On Industry/Host Features:
  1. For CANAB/RES 3700 systems set Local Duplicate Check to Enabled
  2. For OPI/Simphony systems set Local Duplicate Check to Disabled
4. On Misc/Signature Settings set EMV Signature Capture to Disabled
5. On Communication/General set Backup Comm. Type to Disabled
6. On Communication/LAN:
  1. If you know what the network information should be set to, set DHCP to disabled, and specify the Local IP / Netmask / Gateway IP.
  2. If you don’t know, leave DHCP as enabled and make note that it will need to be updated later.
7. On Communication/Communication between ECR/POS and PAX terminal set Protocol Type as HTTP GET
Click Submit.
Once a terminal is connected to the Internet and power cycled it should download these database settings.

Installation Preparation

Installation Preparation steps apply to Canab only, except where specified.

This guide is written for the software versions specified below. Using this guide for other versions, or other guides for this version will result in problems. To check the versions of the software right click the installer, click on properties, and then click on details and check the File version.

If there is an error message about password requirements while running an installer then cancel/abort the installation, go to start/run/gpedit.msc/Computer Configuration/Windows Settings/Security Settings/Account Policies/Password Policy and set "Password must meet complexity requirements" to disabled. Rerun the installer, then after installation is complete set "Password must meet complexity requirements" back to enabled.

Copy over all the installation files to the RES server.
Run Installation Programs in the order shown here:
1. NabOpiPay and Canab: Install NopSetup.exe (File version: 2020.3.720.0)
2. Install caNabSetup.exe (File version: 2020.4.1116.0)
3. Install NabHospMonSetup.exe (File version: 2020.4.1221.1)
  At some point before the site goes live with the new solution, you will need to reboot the server.
Create a credit card driver:
1. POSCFG / Devices / CA/EDC Drivers
2. Driver Tab Name: NAB Driver Code: NAB
3. System Tab Top Half
  AuthChan: 0
  SettleChan: 0
  Port Arbitration Enabled: 0
  Communications Channel: 2
  FutureAvilOpt: 0
  UseAuthThreading: 0
  EMVSystem: 0
  NabHwhEmv: 1
  NabOpiPayPort: 6443
  NabOpiPay UseHttps: 0
4. System Tab Bottom Half
  AuthIPAddrPort: 443
  BkupIPAddrPort: 443
  CurrencyCode: 840
  CountryCode: 840
  CityCode: 0
  TimeZone: 7
  MerchCity: Detroit (Or wherever)
  MerchState: MI (Or wherever)
  NabOpiPay URL: (Server's Static IP Address, like 192.168.100.250)
5. Merchant Tab Authorization Sub Tab Top Half (you may need to drag the middle divider bar down to see all the options.)
  Merchant Category: 5812
  Currency Code: 840
  Country Code: 840
  Card not present enabled: 0
  IndCode: 1
  LangCode: 0
  BankEndDayTime: 300
  CardAcceptorBusinessCode: 0
  CallNopEod: 1
6. Merchant Tab Authorization Sub Tab Bottom Half
  EPX Url: epi.epx.com
  Merchant Number: 2626 (Merchant's real MID here)
  Customer Number: 3001
  DBA Number: 1
  Terminal Number: 88888888
  EPI Key Part 1: (First half of EPI Key here)
  EPI Key Part 2: (Second half of EPI Key here)
  AcquirerIdCode: 0
  StoreNo: 0
  MerchPostalCode: (Customer Zip Code, like 48067)
7. Reload the database in Micros Control Panel.
8. Click on Start, type services.msc and push Enter.
9. Stop and start the Micros Credit Card Server.
Preliminary Setup for Batching CCs:
1. POSCFG / System / External Programs
2. Create a new external program
  Name: Inspect Batch with NabHospMon
  Number: (Doesn't matter)
  Working Directory: C:\Nabancard\NabHospMonitor
  Command Line: C:\Nabancard\NabHospMonitor\StartBatchClose.bat
  User Interface: None Run Style: Minimized
3. Create a new external program
  Name: Settle Credit Cards
  Number: (Doesn't matter)
  Working Directory: $(MICROS_DIR_COMMON_BIN)
  (Click the Dir button on the left to select this)
  Command Line: $(MICROS_DIR_COMMON_BIN)\settle.exe -b
  (Again Click the Dir button to select MICROS_DIR_COMMON_BIN, and then type in the rest)
  User Interface: None
  Run Style: Minimized
Create Reporting Autosequences:
POSCFG / Reports / Autosequences
Create autosequence
Number: 313120
Name: Create & Settle CC Batch
Privilege: 0
POSCFG / Reports / Autosequence Steps
1. Find the autosequence 313120
2. Create step 1
  Type: Stored Procedure
  Skip Step: False
3. Stored Proc Tab
  Stored Procedure: 136 Credit Card Batch Create
4. Create step 2
  Type: External Program
  Skip Step: False
5. Call / Ext. Prog Tab
6. External Program: Settle Credit Cards (Created earlier in the guide.)
7. Create step 3 Type: Report
  Skip Step: False
8. Report Tab
  Report Template: 200 Credit Card Batch Detail
  Title: Credit Card Batch Detail
  Print To Disk Filename: C:\Nabancard\CreditCardBatchDetail.pdf
9. Ranges Tab
  Date Range Source: Specified
  Date Range Selection: Today (Assuming this autosequence will be scheduled to run before the business day is incremented.)
10. Create step 4
  Type: Report
  Skip Step: False
11. Report Tab
  Report Template: 201 Credit Card Batch Transfer Status
  Title: Credit Card Batch Batch Transfer Status
  Print To Disk Filename: C:\Nabancard\CreditCardBatchTransferStatus.pdf
12. Ranges Tab
  Date Range Source: Specified
  Date Range Selection: Today (Assuming this autosequence will be scheduled to run before the business day is incremented.)
13. Create step 5 Type: External Program
  Skip Step: False
  Call / Ext. Prog Tab
  External Program: Inspect Batch with NabHospMon (Created earlier in the guide.)
Create Sending Tender Medias:
1. POSCFG / Sales / Tender/Media
2. Create a Tender/Media
3. Number: 313707
4. Name SEND & STAY
5. General Tab Type:
  Service Total Privilege: 0
  Menu Level Class: ALL LEVELS
6. Service TTL Tab Send Order Keep Held Status (Leave all other values alone or blank)
7. Create another Tender/Media
8. Number: 313708
9. Name SEND
10. General Tab Type:
  Service Total Privilege: 0
  Menu Level Class: ALL LEVELS
11. Service TTL Tab Keep Held Status (Leave all other values alone or blank)
12. POSCFG / Sales / DescriptorsFind any and all of the CA Merchant Trailers
13. For each of them, change a line at the bottom to @@SEND_AND_STAY
NabOpiPay and Canab: Edit the appsettings.json file:
1. Go to c:\Nabancard\NOP\NOPWS
2. Open appsettings.json with Notepad
3. Change the value of MerchNbr to whatever the merchant ID of the store is
4. After you are finished making the changes, save and put a copy of the in the directory c:\Nabancard
5. If you are using Ingenico terminals change VendorTypeStr to “Ingenico” instead of “Pax”
6. If you are using Ingenico terminals change NopsVendorTargetPortStr to “6200” instead of “10009”
NabOpiPay and Canab: Edit the terminals.json file:
1. Go to c:\Nabancard\NOP\NOPWS
2. Open Terminals.json with Notepad
3. In every instance where it says: "WsInstanceDnsHostName": "Micros1" change it to have the server windows name on the right, like: "WsInstanceDnsHostName": "MICROS3700SERVER" (It is recommended to use find and replace to do this.)
4. In every instance the TerminalNbr field should be “88888888“
5. Either edit the terminals file to correspond the terminals to the workstations
  OR
  Change the workstations object numbers in POSCFG / Devices / Network Nodes and Devices to match the numbers in the json file, and then have the terminals match those numbers.
  Whatever was workstation #1 should be made workstation #181, and then later physically give it the terminal that has an IP address that ends in 181.
  After you are finished making the changes, save and put a copy of the file in the directory c:\Nabancard
6. It is possible to generate a report with terminal status. This can assist in troubleshooting issues(like verifying communication and the terminal’s MID). In order to generate the report, the terminals.json file must already be set up with the proper workstation id’s and terminal ip addresses. Then both the terminals.json and appsettings.json file must be read into the NabOpiPay service(The files are only read when the service is starting. If the service is already started you must stop and start it again). This is covered in step 10.
7. If you are using Ingenico terminals change every instance of VendorTargetPortStr from “10009” to “6200”
NabOpiPay and Canab: Start the NabOpiService (Windows errors are fine when stopping/starting the NabOpiPay service. Wait a moment and F5 refresh.)
1. Click on Start, type services.msc and push Enter.
2. Start NabOpiPay(NOP) service. (NabOpiPay is going to create some database tables the first time it runs. The process usually takes about 3 minutes; you can continue working on other things during this time.)
3. After 5 minutes, stop the NabOpiPay (NOP) service.
4. Start the NabOpiPay (NOP) service
5. After a minute, open the newest log file inside c:\Nabancard\NOP\NOPWS\logs and scroll the bottom. If you see exceptions or errors at the bottom, reach out to the development team.
NabOpiPay and Canab: It is possible to generate a report with terminal status. This can assist in acquiring troubleshooting issues(like verifying communication and the terminal's MID). In order to generate the report, the terminals.json file must already be set up with the proper workstation id’s and terminal ip addresses. Then both the terminals.json and appsettings.json file must be read into the NabOpiPay service (The files are only read when the service is starting. If the service is already started you must stop and start it again).
1. First open terminals.json and get the right workstation numbers and pinpad ip addresses in there.
2. Using a browser go to 192.168.100.250:6443/swagger (substitute the RES server's IP address there if it's something different)
3. Scroll down and click /api/MainOpi/GetAllTerminalStatus
4. Click Try it out
5. Click Execute (this can take a minute or two or run)
6. The report provides an easy to read status message on each terminal. The bolded information here is what’s programmed in terminals.json. The information below that is what the real terminal actually provided.
  { "terminalInfo": { "terminalNbr": "88888888", "wsNo": 98, "wsInstanceDnsHostName": "BarnyardDog", "vendorTargetUrl": "192.168.1.100", "vendorTargetPortStr": "10009" }, "terminalLocalTid": "5", "terminalLocalMid": "711000", "terminalLocalDbaNbr": "UNKNOWN", "terminalLocalCustNbr": "UNKNOWN", "statusMessage": "PAX never provides the DBA or Customer Number, check it directly on the terminal(s) under F1 / Host Settings / Host Parameters "communicationSuccess": true, "everythingIsOk": true },
Start the NabHospMonitor service:
1. Click on Start, type services.msc and push Enter.
2. Start the NabHospMonitor service.
3. Wait a moment, then look at C:\Nabancard\NabHospMonitor\NabHospMonitor.log and make sure there are no errors or exceptions inside (TICK is not an error).
Test the Canab driver:
1. Open the Micros Credit Card Utility
2. Go to the Diagnostics tab
3. Select NAB in the lower left, and then while Get Version is selected in the upper left, click Begin Test. Make sure you get a version, like "CaNAB.dll 5.7.0123.4326, (c), NAB LLC."
4. While NAB is still selected, select Test Auth Connection and click Begin Test. You should get something like:
  
  Ping test using valid endpoint, status = 200 success=1 '192.168.100.250':6443;Emv=F;hwhEmv=T;nopOnline=T
  
  Status not equal to 200, success=0, and nopOnline=F are all signs that something is wrong.
  If nopOnline=F double check the setup, especially the IP address in POSCFG / Devices / CA/EDC Drivers/ NAB /System Tab / NabOpiPayURL, and make sure the NabOpiPay(Nop) service is started. If this is all correct then reach out to the development team. If status is not equal to 200 it may be necessary to work with EPX to resolve this.
Set the Credit Card Server verbosity to 10:
1. Open the Micros Control Panel.
2. Click View / Show Verbosity.
3. Select the server.
4. Select the verbosity tab.
5. Set Credit Card Server verbosity to 10

Installation

Installation steps apply to Canab only. For installs without Canab, please consult Oracle documentation for OPI setup.

The steps in this section must be completed during the installation. These steps are intended to be somewhat generic so they apply to various types of sites, as we don't know what the site was doing beforehand or how the database is programmed.

Settle all outstanding transactions.
Create and configure the interface:
1. Inside (Micros Drive):\Micros\Res\Pos\Etc find the file Canab.isl and rename it to pms313181.isl.POSCFG / Devices
2. Place pms313181.isl into (Micros Drive):\Res\CAL\Win32\Files\Micros\Res\Pos\Etc and any other necessary cal folders.
3. POSCFG / Devices / Interfaces
  General Tab
  Name: CanabISL
  Object Number: 313181
  Outgoing Message Name: CanabISL (Must be exactly this!)
  Timeout: 5
  Network Node: (Micros Server)
  Number of ID Digits: 9
  Interface Type: TCP
  Interface Tab
  TCP Server Name (Static IP Address of Server)
  TCP Port Number 9695 (If there is a Load ISL File button click it and add the pms313181 isl.)
Touchscreen Editing:
1. Replace all authorization buttons with the 313181 interface and inquiry 7. Name the buttons Term Auth CC.
2. Replace all purchase (cc lookup) buttons with the 313181 interface and inquiry 6. Name the buttons Term Purchase CC.
3. Make sure there is a button available to the site called Re Auth/Print CC. Have the button linked to Category: Function: Transaction and Function: Credit Authorize.
4. Currently no initial auth's, manual auth's, or other versions of authorizations should be used, except for the auth from interface 181 inquiry 7 and purchase (CC lookup) from interface 181 inquiry 6.
5. All transactions should be closed with Function: Transaction / Credit Finalize.
6. Remove any existing buttons from the previous solution.
7. Edit any macro steps to remove references to previous solutions.
Right now no initial auth's, manual auth's, or other versions of authorizations, except for the auth from interface 181 inquiry 7 and purchase (cc lookup) from interface 181 inquiry 6. All transactions should be closed with Function: Transaction / Credit Finalize.
Leave a MCR Auth CC button (Function: Transaction / Credit Authorize) somewhere to handle slip reprints and some debugging scenarios, but we don't want servers using that button by accident.
Autosequence 313120 should be created earlier in the setup process. Schedule it to run nightly. If they don't already, try to get the cards to settle well before 4am (like 3am). Batches settled after 4am may take another 24 hours to be deposited. Also we recommend not scheduling between 2am and 3am, as that period is skipped when daylight savings leaps forward. After scheduling the autosequence, be sure to reload in Micros control panel.
Create a shortcut to services in the task bar. If something goes wrong, the first thing to do is ask the customer to start/restart a service.
Change over driver:
1. POSCFG / Tender/Media
2. For all credit card tenders
3. Credit Auth Tab
4. Change CA Driver and EDC Driver to the NAB Driver
Reload the Micros control panel, restart the Micros Credit Card Server.

New Setup Checklist

IMPORTANT: On each WS/Terminal combination, the following tests must be performed to identify potential problems immediately. Open the New Setup Checklist and log the tests performed.

Canab installs:

Perform a test transaction, then settle the batch using the autosequence 313120.
Perform an incremental auth, then settle the batch using the autosequence 313120.
Perform a refund, then settle the batch using the autosequence 313120.

NabOpiPay-only installs:

Perform a test transaction, then finalize the transaction.
Perform an incremental auth, then finalize the transaction.
Perform a refund.

Example of Terminals.json File Contents

The terminals.json file is located in C:\Nabancard\Nop\Nopws\. If you make any changes to it you need to save the file, and then restart the NabOpiPay (NOP) service. In this example the site is using Pax terminals, so their VendorTargetPortStr for each workstation is “10009”. If they were using Ingenico the VendorTargetPortStr would be “6200” instead.

Workstation 1 (determined in POSCFG / Devices / User Workstations) is using a Pax terminal with a TID of 181, and that Pax terminal has an ip address of 192.168.100.181. Even though workstation 1 has a windows name of PCWS01 the software resides on the Micros server, which is named MICROS1, and that is the name that goes into WsInstanceDnsHostName.

[

{

"TerminalNbr": "88888888",

"VendorTargetPortStr": "10009",

"VendorTargetUrl": "192.168.100.181",

"WsInstanceDnsHostName": "MICROS1",

"WsNo": 1

},

{

"TerminalNbr": "88888888",

"VendorTargetPortStr": "10009",

"VendorTargetUrl": "192.168.100.182",

"WsInstanceDnsHostName": "MICROS1",

"WsNo": 2

},

{

"TerminalNbr": "88888888",

"VendorTargetPortStr": "10009",

"VendorTargetUrl": "192.168.100.183",

"WsInstanceDnsHostName": "MICROS1",

"WsNo": 99

}

]

Example of appsettings.json File Contents

The appsetting.json file is located in C:\Nabancard\Nop\Nopws\. If you make any changes to it you need to save the file, and then restart the NabOpiPay (NOP) service for the changes to take effect. In this example the site has a merchant id of “123456789”. Obviously that needs to be changed to match the real site. Also in this example the site is using Pax so VendorTypeStr is set to “Pax” and NopsVendorTargetPortStr is set to "10009". If they were using Ingenico terminals VendorTypeStr would be set to “Ingenico” and NopsVendorTargetPortStr would be set to “6200”.

{

"Serilog": {

"MinimumLevel": {

"Default": "Debug",

"Override": {

 "System": "Information",

 "Microsoft": "Information"

}

},

"AllowedHosts": "*",

"StartupServerParams": {

//global

"Version": "faeeacb4-4853-4d89-80d3-ecb8e08df7c4",

"UseTls": "false",

"Port": "6443",

"ClientCertificateMode": "NoCertificate",

"SslProtocols": "Tls12",

"CheckCertificateRevocation": "false",

//local

"HandshakeTimeoutMs": "1000",

"UsePing": "true",

"UsePmsOpiMethods": "false",

"TrimFromBodyStartText": "<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>",

"VendorTypeStr": "Pax",

"VendorTimeoutMs": "65000",

"RefundRequiresCard": "false",

"EpxUrl": "https://epi.epx.com/",

"CustomerReadableName": "PleaseChangeMe",

"MerchNbr": "123456789",

"CustNbr": "3001",

"DbaNbr": "1",

//unencrypted "EpiKey": 98...", Production Key!

"EpiKey": "xNtdx2bZeXYCCQDVvsYO0BVy3/4BqN0ykZB2BymJa8zI10bgL975ApjEsk19DR75",

"EmulateEndOfDay": "false",

"UseUserDefinedPrintData": "false",

"UseCreditCardPreamblesToDetermineIssuer": "false",

"StandaloneWsInstance": "true",

"UseNopInformer": "true",

"NabHospMonPort": "9696",

"NabHospMonUrl": "/api/NopInformerMessage",

"NopsTerminalNbr": "88888888",

"NopsVendorTargetUrl": "192.168.100.181",

"NopsVendorTargetPortStr": "10009",

"EnableApiCardType": "false",

"EnablePosTenderObjNum": "0", //0=disabled, else starting index for Visa, MC, Amex, Discover

"EnableStandardReportEmails": "false",

"EnableExceptionReportEmails": "false",

"EnableCustomerTipPrompt": "false",

"OpiTimeoutMs": "100000",

"TipPercentCap": "50",

"TipPresetPercent1": "18",

"TipPresetPercent2": "25"

}

Example of Full NabHospMonitor Config File Contents

The NabHospMonitor.exe.config file is located in C:\Nabancard\NabHospMonitor\. As a general rule we want the values here to remain consistent across all sites, and you shouldn’t change anything in here. The two exceptions are the upload file paths and emails addresses. If the site does not have Micros installed on the D: drive, change the paths in the section marked

<add key="FullFilesOrDirectoriesToUploadSeparatedBySemicolons" value="C:\Nabancard\Nopws\Logs;C:\Nabancard\Nop\Nopws\logs;D:\Micros\res\pos\etc\3700d.log;D:\Micros\res\pos\etc\CaNab.log;C:\Nabancard\CreditCardBatchDetail.pdf;C:\Nabancard\CreditCardBatchTransferStatus.pdf"/>

To reflect whatever drive Micros is installed on. (The nabancard directory should always be on C:, so those paths do not need changing, just the D: Micros paths.)

In this example file email warnings are set to email hospitality-support@nabancard.com and logs@cditech.com when certain errors occur.

<add key="primaryEmailRecipient" value="<a href="mailto:hospitality-support@nabancard.com">hospitality-support@nabancard.com</a>;logs@cditech.com"/>

Please leave hospitality-support@nabancard.com in place, but you can replace logs@cditech.com with another address if necessary. Be sure to not have any spaces!

(Example file contents below)

<?xml version="1.0" encoding="utf-8"?>

<configuration>

<configSections>

 <section name="custom" type="NabHospMonitor.CustomConfigurationSection, NabHospMonitor"/>

</configSections>

<appSettings>

 <add key="wirelessTerminalLabelCommaVirtualWorkstationNumberSeparatedBySemicolons" value=""/>

 <add key="posType" value="3700"/>

 <add key="uploadToSftpTorF" value="T"/>

 <add key="sendEmailTorF" value="T"/>

 <add key="sendEmailOnlyOnErrorTorF" value="T"/>

 <add key="enableRemoteAuthsTorF" value="F"/>

 <add key="closeRemoteAuthsDuringIdleTorF" value="F"/>

 <add key="workstationIdlePeriodInSeconds" value="30"/>

 <add key="idleOperationsEmployeeObjNum" value="313181"/>

 <add key="doSetupInspectionTorF" value="T"/>

 <add key="rotateInternalLogsTorF" value="T"/>

 <add key="creditCardServerTimeoutInMinutes" value="1"/>

 <add key="daysBackEvaluatingEventLogs" value="1"/>

 <add key="tenderMaxThresholdPercent" value="20"/>

 <add key="tenderMaxThresholdDollars" value="2"/>

 <add key="daysSinceFirstTransactionToAlwaysSendEmail" value="7"/>

 <add key="lookForMissingAuthsTorF" value="T"/>

 <add key="secondsBeforeLookingForMissingAuth" value="15"/>

 <add key="secondsBeforeReexaminingMissingAuth" value="60"/>

 <add key="nabHospMonWebListenerPort" value="9696"/>

 <add key="pmsCommunicatorPort" value="9695"/>

 <add key="interfaceOutgoingMessageName" value="CanabISL"/>

 <add key="nopwsPort" value="6443"/>

 <add key="NopPath" value="C:\Nabancard\NOP\NOPWS"/>

 <add key="remoteNop" value=""/>

 <add key="FullFilesOrDirectoriesToUploadSeparatedBySemicolons" value="C:\Nabancard\Nopws\Logs;C:\Nabancard\Nop\Nopws\logs;D:\Micros\res\pos\etc\3700d.log;D:\Micros\res\pos\etc\CaNab.log;C:\Nabancard\CreditCardBatchDetail.pdf;C:\Nabancard\CreditCardBatchTransferStatus.pdf"/>

 <add key="primaryEmailRecipient" value="hospitality-support@nabancard.com;logs@cditech.com"/>

 <add key="emailSmtpSite" value="email-smtp.us-east-1.amazonaws.com"/>

 <add key="emailPort" value="25"/>

 <add key="cipher" value="4s7YaNh3NObRBiR"/>

 <add key="encryptedSftpUser" value="jdxS+K1Wy9PPEUmsBlWy8g=="/>

 <add key="encryptedSftpSiteUrl" value="lqosEHRDEydRiFxwULXdrOyrW+52iWNTlSUYYn8Wt0g="/>

 <add key="encryptedSftpSiteIp" value="W959oISxP1wCJF4WvpBfnQ=="/>

 <add key="encryptedEmailUsername" value="zNcnaHyfPeZ/DXiL6aL+Q5r4CfNpIC+op1spP6zvW/U="/>

 <add key="encryptedEmailPassword" value="pVznjHUj1gcl7n20uw6BAH4+j6V9Myb8xFq82ECfwsfa2t+0zMKuP0dg+DlHdMKe"/>

 <add key="ClientSettingsProvider.ServiceUri" value=""/>

</appSettings>

<startup>

 <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8"/>

</startup>

<system.web>

 <membership defaultProvider="ClientAuthenticationMembershipProvider">

 <providers>

 <add name="ClientAuthenticationMembershipProvider" type="System.Web.ClientServices.Providers.ClientFormsAuthenticationMembershipProvider, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" serviceUri=""/>

 </providers>

 </membership>

 <roleManager defaultProvider="ClientRoleProvider" enabled="true">

 <providers>

 <add name="ClientRoleProvider" type="System.Web.ClientServices.Providers.ClientRoleProvider, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" serviceUri="" cacheTimeout="86400"/>

 </providers>

 </roleManager>

</system.web>

</configuration>

Preambles

Card Brand	Start	End
Visa	4*
Mastercard	2*
Mastercard	51*	55*
Amex	34*
Amex	37*
Discover	30*
Discover	35*
Discover	36*
Discover	38*
Discover	39*
Discover	6011*
Discover	62*
Discover	64*
Discover	65*

Request Integration/Certification

Login

Sign Up

Change Password

Forgot Password

Success

Error

Information

Warning

Implementation Process

Terminology

OPI Patching

Mode Options

Terminal Mode

Middleware Mode

BroadPOS Setup

Installation Preparation

Installation Preparation steps apply to Canab only, except where specified.

Installation

Installation steps apply to Canab only. For installs without Canab, please consult Oracle documentation for OPI setup.

New Setup Checklist

Example of Terminals.json File Contents

Example of appsettings.json File Contents

Example of Full NabHospMonitor Config File Contents

Preambles