Multiple Core Folder Structure Settings

The OPI Core can be configured to run multiple instances of itself. Therefore, each iteration is required to run under its own subfolder within the EFTLink installation directory. For example, C:\EFTLink\EPSCore_OPI_0 and C:\EFTLink\EPSCore_OPI_1.

This allows a unique opiretail.json file to be held and configured for each instance of the core.

EFTLink needs to be informed what the working folder names are and to achieve this, the following configuration changes are required within the EFTLink framework configuration file.

Depending on the operational mode, EFTLink may use either a JSON configuration file or a properties file.

In property-based configurations (eftlinkconfig.properties), this is done using the EPSCore<n> key, where parameters are appended after the core’s fully-qualified class name.

In JSON-based configurations (eftlinkserver.json), the same values are defined under the epsCores.cores section.

Properties example:

EPSCore0 = oracle.eftlink.opiretail.OPIRetailCore WorkingFolder:./ EPSCore_OPI_0

EPSCore1 = oracle.eftlink.opiretail.OPIRetailCore WorkingFolder:./ EPSCore_OPI_1

JSON example:

"epsCores": {
    "cores": {
      "0": "oracle.eftlink.opiretail.OPIRetailCore WorkingFolder:./EPSCore_OPI_0",
      "1": "oracle.eftlink.opiretail.OPIRetailCore WorkingFolder:./EPSCore_OPI_1"
    }
}

Please refer to Multiple Core Feature section within the Oracle Retail EFTLink Framework Advanced Features Guide for further information on multiple core use cases.