| Oracle® Retail EFTLink Xstore Compatibility Guide Release 20.0 F35883-01 |
|
 Previous |
 Next |
This chapter provides an EFTLink and Xstore Compatibility Guide Overview.
EFTLink provides many features through its API which earlier versions of Xstore will not support. This guide provides the historical information about when Xstore integrated with each specific EFTLink feature in order to help our System Implementation (SI) Partners understand how best to make the choice of which EFTLink version they should adopt for their Xstore implementation. Due to the nature of the Xstore and EFTLink integration, SI Partners and their customers may feel more comfortable making customizations on earlier versions of Xstore to bring in additional EFTLink features from later versions of EFTLink in order to facilitate a faster implementation.
Oracle Retail EFTLink was officially brought into the Oracle Retail Xstore Suite for GA Version 15.0. The following chapters will detail features that have been introduced for each GA version since GA version 15.0 in order to make it clear what each version of EFTLink has brought to the market for each GA version since GA 15.0.
Xstore/EFTLink Core Compatibility
EFTLink Xstore GA 15.0 Compatibility
EFTLink Xstore GA 16.0 Compatibility
EFTLink Xstore GA 17.0 Compatibility
EFTLink Xstore GA 18.0 Compatibility
Oracle Retail EFTLink has always been backwards compatible with earlier versions of Xstore. The following table clearly illustrates which versions of Xstore can communicate with which versions of EFTLink. Please note that in each case the EFTLink client library must be imported into the Xstore\lib\ext folder.
Table 1-1 Xstore POS/EFTLink Version Compatibility
| Oracle Retail Xstore POS | Oracle Retail EFTLink |
|---|---|
|
v15.0, v15.0.1, v15.0.2, v15.0.3 |
v15.0, v15.0.1, v15.0.2 |
|
v16.0, v16.0.1, v16.0.2, v16.0.3 |
|
|
v17.0, v17.0.1, v17.0.2 |
|
|
v18.0, v18.0.1 |
|
|
v19.0, v19.0.1 |
|
|
v15.0, v15.0.1, v15.0.2, v15.0.3* |
v20.0* |
|
v16.0, v16.0.1, v16.0.2, v16.0.3, v16.0.4 |
v16.0, v16.0.1, v16.0.2, v16.0.3 |
|
v17.0, v17.0.1, v17.0.2 |
|
|
v18.0, v18.0.1 |
|
|
v19.0, v19.0.1 |
|
|
v16.0, v16.0.1, v16.0.2, v16.0.3, v16.0.4* |
v20.0* |
|
v17.0, v17.0.1, v17.0.2, v17.0.3 |
v17.0, v17.0.1, v17.0.2 |
|
v18.0, v18.0.1 |
|
|
v19.0, v19.0.1 |
|
|
v17.0, v17.0.1, v17.0.2, v17.0.3* |
v20.0* |
|
v18.0, v18.0.1, v18.0.2 |
v18.0, v18.0.1 |
|
v19.0, v19.0.1 |
|
|
v18.0, v18.0.1, v18.0.2* |
v20.0* |
|
v19.0, v19.0.1 |
v19.0, v19.0.1 |
|
v19.0, v19.0.1* |
v20.0* |
|
v20.0 |
v20.0 |
*Even though earlier versions of Xstore will be able to communicate with EFTLink v20.0 they will not be able to consume all the new features introduced in EFTLink v20.0 as they will have to use the last v19.0.1 EFTLink library. This library is compatible with earlier versions of Xstore but for v20.0 onwards Xstore and EFTLink had to change the way the XML was consumed as a result of removing the dependency on the JDOM2 library.
