EFTLink Server Compatibility

When deployed in Server mode, there will be multiple instances of the EFTLink main application class (OPIServer) and multiple instances of the core class, all in memory at the same time. Each instance runs from its own set of configuration files in a sub-folder under the main EFTLink folder.

This imposes rules/restrictions on the core:

• No hard-coded file paths. Always access files relative to INSTANCE_ROOT() or DATA(). Only use PRIMARY_ROOT for files that are intentionally the same for all instances.

  Note:

  When using framework file access helper classes such as EPSFileProperties, EPSSecureFile, and so on, the use of INSTANCE_ROOT() is automatically applied by the framework.

• Do not store instance-specific data in static storage. Static storage will in effect be shared between all instances.

• No passing files (for example signature images) by name. The POS will be on a remote system.