Skip to main content

Enactor Application Installation

Enactor Application Installation

Slide 1


Configuration Topics

  • MSI Installation process
  • Installer.ini
  • Enactor Installation Footprint
  • Key Enactor Installation Components

Installer.ini Settings

The Installer.ini file is used by the MSI package to set all the key local settings for the POS Terminal, e.g.:

  • Device ID
  • Location ID
  • Database Connection String
  • Endpoint Addresses

Usually it is highly common across an estate, with only a few settings that differ from one POS to another (e.g. Device ID and Location ID).

Variable settings are often provided using a setup script that captures info from a user and substitutes in the captured data.


Other Local Data

Most data (Master Data, Configuration etc.) is handled by the Enactor Application and stored in the POS Database.

Some components need to be installed directly on the POS/Store Server/Mobile Server drive:

  • Device Drivers
  • JPOS Configuration
  • Certificates

Exercise 4: POS Installation

Store Setup - Exercise 4

  1. Edit the Installer.ini (right click and choose "Edit")
  2. Find the following entries: DEVICE_ID - set to the Device ID you created in the previous exercise; LOCATION_ID - set to the Location ID you created in the previous exercise
  3. Save the Installer.ini file
  4. Run the POS installation MSI
  5. When the Enactor Installation wizard appears, make sure the installation location is set to: C:\Enactor
  6. Confirm the dialog boxes and wait for the installation to complete

Exercise 5: Check POS Installation

Store Setup - Exercise 5

  1. Once the installation has completed, check two things: Has the POS created all the database tables?; Has it connected to the Estate Manager?
  2. Check the database creation progress by looking in the C:\Enactor\Pos\Logs folder at the common.log file
  3. Once the DB tables have been created, go to the Estate Manager and check the Active Subscriptions screen to verify the POS has connected
  4. Once the POS is connected, you are ready to send down the configuration data it needs to operate

Exercise 6: POS Data Broadcast

Store Setup - Exercise 6

  1. Send out a single broadcast to all devices with all the master data needed: Broadcast ID: NEW_DEVICE; Date Range: since 1/1/2000 (all data will be sent); Target: All Stores
  2. Once the broadcast has been received and processed by your device, try launching your POS. There is a shortcut on your desktop that you can double-click
  3. A Firewall Alert may be generated when your POS starts. OK the message
  4. Does your POS start as expected? Can you log in and carry out a sale?

Further Reading

For additional information and further reading on Application Installation, please see the following guides:

DocumentDescription
How to: POS Installation (Windows)Full POS installation guide for Windows
How to: Store Server Installation (Windows)Store Server installation on Windows
How to: Native POS Android InstallationNative Android POS installation
How to: Native POS iOS InstallationNative iOS POS installation
How to: Native POS Swing InstallationNative Swing POS installation on Windows
How to: Store Application UpdatesDeploying application updates to store devices
How to: Data and Regional BroadcastingBroadcasting configuration data to POS