Skip to main content

Dinerware Install Handbook

  • Updated

 

In a basic Dinerware setup, there is no configuration needed for Omnivore to communicate with the POS system. However, based on app partner needs and Dinerware database specific parameters, there could be individual setups. Please read through the whole document to determine if your integration needs additional setup. 

 

Connecting Locations

Dinerware POS requires an agent to be installed at the location level. Once the services are installed, the location will appear "online" in the Omnivore Dashboard. To get a detailed walkthrough of how to install the Omnivore agent, please refer to the Omnivore installation guide. Also, please ensure to download the Omnivore agent onto the BRAIN machine of the Dinerware POS System.

 

Prior to Install

Before installing, it is always good to double check POS versions and database names to ensure a smooth integration process

  • Dinerware version 3.3 or higher (3.7.5.4849 for ordering/printing integrations)
  • Database Name
  • Available RAM (At least 700MB)

Dinerware Integration form 

Employee Creation (Optional)

If an app partner is planning to do 3rd party ordering or any type of order injection, an employee will need to be made. 

  • Login to Workstation with a MANAGER number
  • Select the Manager tab at the top of the screen
  • Navigate to the employee list
  • Select New
  • Create an Omnivore API employee
    • Employee needs to have all permissions in the system
    • Login PIN does not matter
  • Create a second employee 
    • Name of the App partner
    • Employee needs to have all permissions in the system
    • Login PIN does not matter

 

Payment Tenders (Optional)

If an app partner is planning on doing order injection along with payments, a tender will need to be created in the Dinerware database.

  • Login to Workstation with a Manager code
    • Select the Manager tab at the top of the page
    • From this screen, select “Advanced”
    • Select “Tender” or “Tender Setup”
    • Add a name, and make sure to allow tips. 
    • Flag on overages to go to tip
    • Make sure no job is set for the tender so all jobs have access
    • Make sure no other flags are checked

Menu Item Creation (Optional)

Sometimes an app partner will need a ghost item in the database for name injection or other details on the order

  • Login to Workstation with a manager code
    • Select the Manager tab at the top of the page
    • Select “Menu” and follow until you reach menu items
    • Add a new item and make sure it is a $0.00 priced item. 




 

Running Price Checks (Optional)

Sometimes an app partner will need to do price checks in order to receive an accurate amount of the bill from the POS system. To do this, the Omnivore API employee created above will need to be designated in the Omnivore config files

  • Navigate to C:\ProgramFiles(x86)\PosAgent folder in Windows explorer
  • Open the general.ini file
  • In the [Dinerware] header, add the following directive
    • PriceCheckEmployee = XXX
    • The “XXX” will be the SQL id pulled from the system in the app partners API testing tool. This WILL NOT be the login PIN created. 

 

Upgrades

As stated previously, a local Omnivore agent is required for the Omnivore Dinerware integration. We always recommend having the agent running on the latest version. If an agent agent upgrade is needed, please contact the Omnivore support team. Otherwise, using the Omnivore link to download will always provide the latest release.

Testing

Use the Basic Menu Testing for POS Integrations article that outlines recommended testing steps to verify orders are flowing through successfully to POS.

Troubleshooting

Omnivoreites have taken time and effort to document errors and issues and how to resolve in the articles below. These are the main issues that have been seen and resolved in the past. 

Check Virtual Client

Open a browser window and see if you can connect to the Virtual Client (this may take several minutes)

 

Dinerware Database Name

In the Brain software, the typical database name is “Dinerware”, and is located in the top right of the brain program. If it is different from the default name, follow the steps below.

  • Navigate to C:\ProgramFiles(x86)\PosAgent and open the general.ini file
  • In the [Dinerware] section, change the Connection String to one of the following
    • ConnectionString = mssql://localhost\DINERWARE/(Insert the name of the database here)
    • ConnectionString = mssql://<sql_server_name>/<dbname>
    • ConnectionString = mssql://<pc_name>\<sql_server_name>/<dbname>

If the database name matches, you may have to set permissions in the SQL server management studio

  • In Microsoft SQL Server Management Studio (SSMS)
    • Connect using default credentials
    • Expand the Databases list on the left and right click the active Dinerware database, then select Properties
    • Switch to the Permissions tab on the right and click the “View server permissions” hyperlink
    • Select Permission on the left, NT AUTHORITY\SYSTEM on the upper right, then apply the following changes:
      • Don't alter existing granted permissions
      • Check Grant "Connect Any Database"
      • Check Grant "External access assembly"
      • Check Grant "Select All User Securables"
      • Check Grant "View any database"
      • Check Grant "View any definition"
      • Click [OK] to save/apply changes and close
    • Verify that the permissions changes have been inherited by the System user 

Related articles