EFTLink - Server – PEDPool (dynamic)

Note:

It is important to point out that the EFTLink PED pooling functionality is restricted by Core compatibility. Therefore please check the core guide documentation. Also note the following restrictions:

PED pooling out of the box is only applicable within the <CardServiceRequest> context, that is, this is when the actual payment is initiated and finalized.

<SaleStateNotification> are supported in limited capacity and only when a server instance is marked “*” as a dedicated default to a POS through the pos<ws Id>.subpool list. In addition, while using <SaleStateNotification>, that server instance cannot be included in any other sub pool list.

<DeviceRequest> from release 24 is now also supported when running in pedpooling mode. However, this needs to be enabled in the eftlinkconfig.properties file by setting the property key DeviceRequestInPedPoolModeEnabled to true. In addition to enabling this, it is also important that customization has been done within the POS so that it listens on channel 1 for any interim device requests initiated from EFTLink.

If the Oracle Retail EFTLink Framework Installation and Configuration Guide was followed whereby the choice of the installation type was “Server + PedPooling” then some of the configuration would have been completed automatically. However, further information is required.

Please confirm that there is the correct number of Server<n> folders created and the eftlinkconfig.properties file and the core properties file exist and are configured.

In PED Pooling mode, it is mandatory that you assign a friendly name/description to each EFTLink instance as this is the text that will be display to the operator upon the pool list.

For the number servers specified (“NumServers”) ensure there is a “server<n>.description” key and that each value is set to your preferred descriptive choice.

To do this, please edit the eftlinkconfig.properties within the EFTLink installation root.

For example,

NumServers = 4

server1.description = Menswear Suits - Terminal 1

server2.description = Menswear Suits - Terminal 2

server3.description = Menswear Suits - Terminal 3

server4.description = Menswear Suits - Terminal 4

When PED pooling has been enabled, the system uses the standard channel 1 display messages to present each POS operator with a list of available payment terminals. By default, the list will include all available terminals, but this can be confusing in a large store, so there is an option to limit each POS to a subset of the full list to show just the terminals in one department. The subset is defined using the descriptive names from EFTLink Instance Set Up and specified as a comma-separated list. A default association can be set by prefixing the descriptive name with '*'. If that payment terminal is available, it will be automatically used without any operator prompting.

For example,

pos1.subpool = *Menswear Suits - Terminal 1, Menswear Suits - Terminal 3, Menswear Suits - Terminal 4

pos2.subpool = *Menswear Suits - Terminal 2, Menswear Suits - Terminal 3, Menswear Suits - Terminal 4

pos3.subpool = Menswear Suits - Terminal 3, Menswear Suits - Terminal 4

…

pos10.subpool = Menswear Suits - Terminal 3, Menswear Suits - Terminal 4