Hospitality application supports configuration and initialisation of multiple instances simultaneously.
Hospitality application supports two different modes of initialisation:
Manual start through batch file
Run as a Service
After successful installation of hospitality application, Hospitality can be started manually by running StartHospitalityServer.bat.
Note: The Hospitality application did not have the option of closing on system tray as there is no GUI and if user wanted to close the hospitality application then press Ctrl+C on both screens.
Steps to hide CMD shells of Hospitality application:
Note: Once console is hidden then Hospitality Application can only be killed form Task Manager. To kill application from Task Manager search for javaw process running and stop both of them.
To find process-id of hospitality application:
Run jdk installation directory\jdk1.8.xx\bin\jps
Processes with above description should be closed for stopping hospitality application.
For Hospitality Server:
For EVT Server:
After successful installation of hospitality application, Hospitality provides Start as Service configuration functionality to run or initialize application by registering it as a windows service. There is no GUI in hospitality and also there is no console when start as a service initialisation of hospitality application is done. When we need to stop application then it will b stopped by closing services manually as shown in further screens.
At the time of system start-up this service will automatically be trigged.
To unregister, Run UninstallService.bat file.
Hospitality, when it runs as service uses a 'Local System' account, which has administrative rights.
For more details about privileges see the
Set username/password of 'low privilege service account' with below attributes on ivt wrapper properties and evt-interface.wrapper.properties file:
Install hospitality as service using InstallService.bat
Run the services
Delete password tag ‘wrapper.ntservice.password=**’ from files jvt.wrapper.properties and evt-interface.wrapper.properties after successfully running application (services).
Note: Password needs to be added again if re-installing application.
Feedback or bugs to report?
Ask our developer community.
Search our documentation, API references and articles.