Differences between revisions 1 and 6 (spanning 5 versions)
⇤ ← Revision 1 as of 2007-06-22 02:57:32 →
Size: 1708
Editor: DannyCheung
Comment:
← Revision 6 as of 2008-11-07 05:12:12 → ⇥
Size: 3779
Editor: DannyCheung
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Integrated EFTPOS = ## page was renamed from Integrated Eftpos
= Installing PC-EFTPOS drivers =
Line 3: Line 4:

'''The pinpad MUST be configured to work with the PC-EFTPOS drivers. Standard units handed out from the bank will NOT have this feature. '''
Line 7: Line 10:
Line 11: Line 13:
|| CONTROL server || The computer from which CONTROL is being run from. ||
||Ingenico TCP/IP driver || The piece of software on the POS Terminal that allows the Pinpad Driver to commnuicate over a network ||		 || 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 ||
Line 15: Line 17:
== Windows ==
The terminal should have:
Line 16: Line 20:
 * 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.
Line 17: Line 25:
== Windows ==
The terminal should have the Pinpad drivers(EFTCLT.exe), the Eftpos Server program (EFTSRV.exe) and the Ingenico TCP/IP drivers installed. 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,
Line 20: Line 27:
 1. Run the install programs
 1. Create a rule in the firewall to allow incoming connections to TCP port 6005
Line 21: Line 30:
 1. 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 .
}}}
 1. Install Java
 {{{
# rpm -i j2re-1_4_2_01-i586.rpm}}}
 1. Copy the eftpos tarball from sam
 {{{
# scp sam.crecom.com.au:/u/ccdev/eftpos/neweftposinstall.tgz .}}}

 1. Unpack the tarball
 {{{
# tar xvzf neweftposinstall.tgz}}}
 1. Copy the drivers into place
 {{{
# cp -r ./u/eftpos /u/}}}
 1. Find the location of the java executable
 {{{
# type java }}}
 1. Edit the /u/eftpos/eftclt/run script
 {{{
# Ensure that the driver script knows where the java executable is. /usr/local/java/bin/java .....}}}
 1. Run the eftpos client driver script. Nothing will happen. If anything, it will give errors
 {{{
# /u/eftpos/eftlclt/run}}}
 1. Check the eftpos client error file
 {{{
# tail /u/eftpos/eftclt/eftpos.log}}}
 1. 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}}}
 1. 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/}}}
 1. 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/}}}
 1. Run the eftpos driver script, test and troubleshoot
 {{{
# /u/eftpos/eftclt/run}}}
 1. Add the following line to {{{ /etc/X11/xinit/Xclients}}}
 {{{
...
# Add this line
exec /u/eftpos/eftclt/run &
exec fvwm}}}

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,

  1. Run the install programs
  2. Create a rule in the firewall to allow incoming connections to TCP port 6005

Linux

  1. 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 .
  2. Install Java 
    # rpm -i j2re-1_4_2_01-i586.rpm
  3. Copy the eftpos tarball from sam 
    # scp sam.crecom.com.au:/u/ccdev/eftpos/neweftposinstall.tgz .
  4. Unpack the tarball 
    # tar xvzf neweftposinstall.tgz
  5. Copy the drivers into place 
    # cp -r ./u/eftpos /u/
  6. Find the location of the java executable 
    # type java
  7. Edit the /u/eftpos/eftclt/run script 
    # Ensure that the driver script knows where the java executable is. /usr/local/java/bin/java .....
  8. Run the eftpos client driver script. Nothing will happen. If anything, it will give errors 
    # /u/eftpos/eftlclt/run
  9. Check the eftpos client error file 
    # tail /u/eftpos/eftclt/eftpos.log

  10. 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

  11. 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/

  12. 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/
  13. Run the eftpos driver script, test and troubleshoot 
    # /u/eftpos/eftclt/run

  14. Add the following line to  /etc/X11/xinit/Xclients 

    ...
# Add this line
exec /u/eftpos/eftclt/run &
exec fvwm

Installing_Eftpos_Drivers (last edited 2023-04-16 23:39:57 by JonCo)