Database.exe

3 | Set Application Keep-Alives

This article provides an overview of the Set Application Keep-Alives function in database.exe which allows for monitoring the TCP ports for inactivity. Note: As of v4.6, The 'Set Application Keep-Alives' button in database.exe replaced the 'Send Application Keep-Alives' flag in the Flags Tab in Global Settings in BackOffice. This function button can be set to send Keep-Alives packets at a defined interval of time to keep the TCP ports active.

This article provides an overview of the Set Application Keep-Alives function in database.exe which allows for monitoring the TCP ports for inactivity.

Note: As of v4.6, The 'Set Application Keep-Alives' button in database.exe replaced the 'Send Application Keep-Alives' flag in the Flags Tab in Global Settings in BackOffice.

This function button can be set to send Keep-Alives packets at a defined interval of time to keep the TCP ports active.

If no data packets are sent for 120 seconds, a KeepAlive message packet will be sent to the SmartController to prevent the router from closing down the TCP Port.

Prerequisite

  • Minimum Bepoz version of 4.6 is required for this functionality/feature

Send Application Keep-Alives Setup

  • To set up the Send Application Keep-Alive, log into database.exe and navigate to the Modify Database tab 
  • Click on the 'Set Application Keep-Alives' button under the Other Functions section
    • This will open a new pop-up window requesting to enter the authorization code/password
  • Enter the authorization code and click on OK to continue
    • This will then open another pop-window requesting to enter a Parameter to set Application Keep-Alives time duration
  • The three different parameters include
    • 0 - No Keep Alives
    • 1 - Two minutes
    • 2 - Ten minutes
  • Once done click on OK to save the settings
  • This will set KeepAlives for the following applications
    • SmartPOS
    • SmartController
    • EConnect
    • Bematech Send 8000 job
  • Send VenueDatatabase to All Venues if within Multivenue as the change is within the Global table  
  • Restart SmartControllers at all remote sites once the database has been processed