A separate middleware server is required. That server adheres to the following requirements. In addition, a common strategy to increase middleware response is to partition middleware components across multiple servers.

 

SalesEZ application can be deployed on one server while BookEZ application is deployed on another. Using this approach, each server adheres to the following requirements.

 

 

Note: If you use ScanMan and/or GateKeeper modules, a separate Pool/SalesEZ application is used for those devices so they do not compete for CPU time with regular salespoints.

 

For larger installations, we feel that having roughly twenty connections per CPU core are the maximum saturation. Some clients have a higher ratio, but to find the magic number requires knowing what kind of transactions a typical. For instance, extensive use of Max4Sale capability forces you to keep a lower ratio. You may be able to increase this number with experimentation, but be aware that the risk is slowing down the response times of your salespoints.

 

Note: for the purpose of calculating the number of connections, you must add SalesEZ and BookEZ connections together. Therefore, a single salespoint with bookings enabled connecting to a single middleware server counts as two connections.

 

Important: accesso recommends that your Middleware server be placed on a battery backup system (UPS) capable of lasting at least forty-five minutes. This ensures that your operation continues to run smoothly when you experience power issues.