Run IPC as a Service

IPC may be run as a Windows service when using HostedEVT mode i.e. IPC communicates with POS using IntraMessages and no IPC UI is displayed.

When IPC runs as Windows Service the merchant application is enabled to gracefully start/stop IPC and/or to abort execution of IPC by using appropriate scripted commands.

To enable this option IPC should be configured with options ‘Run IPC as Service’ and ‘Is HostedEVT’ selected in IPC Configuration -> Hosted IPC tab. using appropriate .bat/.sh files.

Note : IPC as a Service is not yet supported for United States geography.

Windows

  1. Steps to run IPC as Service**

    1. Run Emboss set up as same as normal IPC Application

    2. Select ‘IPC as a Service’ option present in Hosted IPC tab in YESEFT Configuration.

    3. Select Pinpad.

    4. Go to bin folder,

      • Run installIPCService.bat to install Application Service.
      • Run startIPCService.bat to start IPC Application and check logs yescps.log and wrapper.log (for console logs) in YESEFT\logs folder.
      • Run stopIPCService.bat to exit IPC Application.
      • Run uninstallIPCService.bat to uninstall Application Service.
  2. YESEFT Folder contents:**

    IPC as a Windows service has been enabled through the Yet Another Java Service wrapper i.e. yajsw software.

    The yajsw jars i.e. wrapper and wrapperApp jars are present within in the YESEFT folder

    a) YESEFT/bin Folder

    This folder contains some additional necessary scripts used for running IPC application as service.

    ipcasaservice1.png

    The following Windows bat files are present inside this folder:

    • installIPCService: To install IPC application and register it as windows service. Check task manager as shown below:

ipcasaservice2.png

  • IPCServiceSetenv: This file is called from installIPCService bat file for setting necessary environment

     and configuration parameters.
    
  • startIPCService: To start IPC Application as windows service. Check task manager as shown below:

    Every time any configuration changes are made, the IPC application must to be stopped and then started again for the changes to take effect.

ipcasaservice3.png

  • stopIPCService: To stop IPC Application as windows service. This will remove PID of service from task manager.

  • uninstallIPCService: To uninstall IPC application and de-register it as windows service.

     This will remove service from task manager.
    
  • Wrapper and wrapperw: To include necessary jars for running wrapper.

b) Properties Folder

The following property and configuration files are present inside the properties folder:

  • evt.properties: Added Boolean key RUN_AS_IPC_SERVICE.

  • Ipcprocessid.txt: This contains process id of the running IPC Service.

  • wrapper.conf: This is the main configuration file of the wrapper to set all the functional parameters of the service.

    c) Logs Folder

    The following log files are present in logs folder:

  • wrapper.log: Log file to which all output to the console will be logged.

  • yescps.log: Logs related to the flow of IPC application.

d) YESEFT Configuration Changes

Please see below configuration changes related to run IPC as service.

  • When “Is HostedEVT” inside Hosted IPC tab is selected then Software and firmware upgrade checks are selected and no further changes are allowed.
  • If IPC As a Service checkbox with hosted EVT inside Hosted IPC tab is selected then
  • EnableGUI present inside LooknFeel tab is disabled.
  • Printer dropdown and Print receipt checkbox inside Receipt tab is disabled.
  • The behaviour of autosensing Comport functionality will be same as UI Mode. In case of Hosted Mode, the messages will be displayed in the intra message port. Please refer to Autosensing comport points in 4.3.1 for default instance and 4.3.3 for multiple instances. All the related messages can be seen in the intra message port.