4 EFTLink General Information
This chapter provides general information about EFTLink:
Tender Mapping
EFTLink provides a table - CardRange.xml - for mapping EFT cards to POS tenders. This is done by card IIN range, or, where that is not possible, by card name (also known as card circuit). The resulting numeric code is returned to the POS so that it can determine which tender to allocate the payment to. By default, the table maps all card to a single "type" (or tender) by a simple wildcard catchall. This can be used as-is, but if a more detailed breakdown of card type is needed; the relevant card ranges must be added to the file.
CardRange.xml can also be used to map cards by range to a suitable description for display on the receipt. CardRange.xml includes comments to explain the layout.
It is anticipated that each POS development team will want to prepare a suitable CardRange.xml for their specific POS requirements, in which case the file can be replaced as required.
Note:
For more information, see the Oracle Retail EFTLink CardRange.xml Guide available on My Oracle Support (Doc ID 2266221.1) using the following link:
Logging - EFTLink Framework and Core
EFTLink uses a standard java logging package - log4j2. It maintains a daily log file - eftlink_YYYY-MM-DD.log - and deletes log files after 30 days. Both the framework and the
core log into this file.
Log files are in the log subdirectory and are created as soon as EFTLink starts. By default, info level logging is enabled. This means that key information is logged but the files are kept as small as possible.
To keep files for longer, or increase the logging level, set log4j2.xml appropriately. Edit the log4j2.xml configuration file which is in the main EFTLink directory.
For debug logging change the following entry:
<Root level="info">
to
<Root level="debug">
Logging at debug level does not noticeably affect system performance but does generate larger log files. To retain log files for longer, edit:
<Delete basePath="log" maxDepth="1"> <IfLastModified
age="30d" /></Delete>
and alter the age parameter to several days to keep files after the current day (default is 30d).
Consider available disk space when choosing several days to retain log files.
Multiple log files are configured in the standard log4j2.xml configuration file:
-
EFTLinkGlobal - contains log information from all sources
-
EFTLink - contains log information from the framework
A core may have its own log4j2.xml configuration
file copied in during install to log to additional files for 3rd party
libraries.
After installing EFTLink as a service, then starting the service, the log file will show about 16 lines, with some basic information, and log that it is deferring all initialization until POS type is known. Once a POS starts, you see details of the core started, with the settings used by the core and initialization progress logged, along with subsequent processing data.
In the case of a MultiServerLauncher / PedPooling installation,
the standard log4j2.xml file requires alteration
to include server appenders/loggers. See installation document for
further details.
Translation
Translation is the process of interpreting and adapting text from one language into another. Although the code itself is not translated, components of the application that are translated may include the following, among others:
-
Graphical user interface (GUI)
-
Error messages
The following components are not usually translated:
-
Documentation (for example, Online Help, Release Notes, Installation Guide, User Guide, Operations Guide)
-
Batch programs and messages
-
Log files
-
Configuration Tools
-
Reports
-
Demo data
-
Training Materials
Most display messages are generated by the core in use or by the
host, in which case they are displayed without change. There are also
some display messages generated by EFTLink itself. These are defined
in LangEN.properties, which is held externally in
the root folder of EFTLink - if necessary, the file in the EFTLink
root folder can be edited.
The EFTLink framework supports several other languages. Setting
EFTLink framework to use one of these is in EftLinkConfig.properties
DisplayLanguage = EN
Possible values include:
Table 4-1 Display Language Settings
| Language | Setting |
|---|---|
|
Chinese (Simplified) |
CN |
|
German |
DE |
|
English |
EN |
|
Spanish |
ES |
|
French |
FR |
|
Italian |
IT |
|
Japanese |
JP |
|
Dutch |
NL |
|
Portuguese |
PT |
|
Russian |
RU |
|
Swedish |
SV |
Each of these has its own language property file, for example LangDE.properties. The file is held in the root EFTLink
folder where it can be edited.
Note:
The languages that do not use the Latin alphabet have the characters defined in Unicode in their property file. To display messages in Chinese, Japanese or Russian the operating system must support those languages.
Setting the value DisplayLanguage =
in EftlinkConfig.properties will also control
which language a core will use for core specific translations.
Table 4-2 Core Specific Translations
| Core | Language Included |
|---|---|
|
Adyen |
Chinese (Simplified) German English Spanish French Italian Japanese Dutch Portuguese Russian Swedish |
|
AJB FiPay |
Chinese (Simplified) German English Spanish French Italian Japanese Dutch Portuguese Russian Swedish |
|
Cayan |
Chinese (Simplified) German English Spanish French Italian Japanese Dutch Portuguese Russian Swedish |
|
OPI Retail |
Chinese (Simplified) German English Spanish French Italian Japanese Dutch Portuguese Russian Swedish |
|
PaybyLink |
Chinese (Simplified) German English Spanish French Italian Japanese Dutch Portuguese Russian Swedish |
|
PayPal |
Chinese (Simplified) German English Spanish French Italian Japanese Dutch Portuguese Russian Swedish |
|
SixPayment Services MPD |
Chinese (Simplified) German English Spanish French Italian Japanese Dutch Portuguese Russian Swedish |
|
Tender Retail |
Chinese (Simplified) German English Spanish French Italian Japanese Dutch Portuguese Russian Swedish |
|
The Logic Group SolveConnect |
Chinese (Simplified) German English Spanish French Italian Japanese Dutch Portuguese Russian Swedish |
|
Verifone Ocius Sentinel |
No translation included |
|
Verifone Point US |
Chinese (Simplified) German English Spanish French Italian Japanese Dutch Portuguese Russian Swedish |
|
World Pay |
No translation included |