Configure a Receipt Server Node

   Journey Manager (JM) The transaction engine for the platform. |   System Manager / DevOps |   18.05 This feature was updated in 18.05.

Manager can utilize several server nodes to generate receipts. To optimize receipt generation, create at least one server node that is solely dedicated for receipt generation by selecting the Transact PDF Receipt Server checkbox only.

Manager has a Transact Receipts module, which can be deployed on a dedicated receipt server node.

You can tune a receipt server node performance by:

  • Creating more dedicated receipt server nodes that will process the receipt queue quicker.
  • Creating more threads on each server node to increase concurrent processing. This is configured in the Receipt Core Global Service.
  • The maximum queue length of submissions to process for each node.
  • The maximum number of attempts for rendering any PDF receipt before abandoning.

For low throughput systems, receipt rendering can be performed on server nodes that are shared as opposed to dedicated. However, on high throughput systems with complex receipts, dedicating server nodes for receipt generation may be a better option.

With this approach, each receipt server node can be configured to have multiple threads running. The queue for these threads is updated every minute. This provides the ability to spread the receipt rendering over several nodes and dedicating some server nodes to just rendering receipts, effectively building a server farm for receipt rendering. The use of a farm for receipt rendering means these nodes are not affected by user web traffic and other system processes. As a result, they can be tuned to maintain an optimum level of throughput.

Next, learn how to configure receipt delivery mode.