Installing PC-EFTPOS drivers
Control has an integrated EFTPOS feature that communicates with the PC-EFTPOS drivers for Ingenico EFTPOS equipment.
The pinpad MUST be configured to work with the PC-EFTPOS drivers. Standard units handed out from the bank will NOT have this feature.
The POS terminal (that the pinpad is connected) can be running either Linux or Windows.
Terminology
POS Terminal |
The PC that the Pinpad is directly connected to. This is usually the terminal that the sales transaction was performed on. It should be noted that most of the EFTPOS intelligence and settings are stored here. |
Pinpad |
The device that swipes the customer's card and asks for the PIN number. |
Eftpos Modem |
The phone line modem that rings the bank's server and opens up the link to the bank. |
CONTROL server |
The computer from which CONTROL is being run on. |
PC-EFTPOS TCP/IP driver |
The piece of software on the POS Terminal that allows the Pinpad Driver to commnuicate over a network |
Eftpos Server |
The piece of software on the POS Terminal that talks to the bank via the Eftpos Modem |
Eftpos Docket Printer |
The Ingenico thermal docket printer. It's only purpose is to print EFTPOS receipts. Not really necessary as CONTROL dockets should have EFTPOS details printed on them. |
Windows
The terminal should have:
- the Pinpad drivers(EFTCLT.exe)
- the Eftpos Server program (EFTSRV.exe) and
- the PC-EFTPOS TCP/IP drivers
The CONTROL server will talk to the Pinpad driver via the Ingenico TCP/IP drivers. The drivers then talk to the Pinpad via the serial port. If the Pinpad does not have a built-in modem, it will need to use the Eftpos Server program to communicate with the bank or an upstream Eftpos server.
To install, simply run the install programs.
Linux
- Download Sun's Java version 1.4.2_01. This MUST be the one from Sun Microsystems and not the one from Gnu.
# scp sam.crecom.com.au:/u2/programs/j2re-1_4_2_01-linux-i586.rpm .
- Install Java
# rpm -i j2re-1_4_2_01-i586.rpm
- Copy the eftpos tarball from sam
# scp sam.crecom.com.au:/u/ccdev/eftpos/neweftposinstall.tgz .
- Unpack the tarball
# tar xvzf neweftposinstall.tgz
- Copy the drivers into place
# cp -r ./u/eftpos /u/
- Find the location of the java executable
# type java
- Edit the /u/eftpos/eftclt/run script
# Ensure that the driver script knows where the java executable is. /usr/local/java/bin/java .....
- Run the eftpos client driver script. Nothing will happen. If anything, it will give errors
# /u/eftpos/eftlclt/run
- Check the eftpos client error file
# tail /u/eftpos/eftclt/eftpos.log
- Look for errors relating to the file javax.com.properties and where Java expects the file to be. In the following examples, we will assume that place to be /usr/share/jvm/java-1.4.2/jre/lib
- Copy javax.com.properties to where Java wants it to be
# cp ./usr/java/j2re1.4.2_01/lib/javax.com.properties /usr/share/jvm/java-1.4.2/jre/lib/
Copy the RxTx serial and comm modules for Java
# cp -r ./usr/java/j2re1.4.2_01/lib/ext/ /usr/share/jvm/java-1.4.2/jre/lib/ # cp -r ./usr/java/j2re1.4.2_01/lib/i386/librxtx* /usr/share/jvm/java-1.4.2/jre/lib/
- Run the eftpos driver script, test and troubleshoot
# /u/eftpos/eftclt/run
- Add the following line to /etc/inittab
eft:345:respawn:/u/eftpos/eftclt/run