Run Rule Engine in Docker

This topic describes how to run a Rule Engine in Docker. It provides an overview of the main steps and describes the recommended default topology.

Docker containers wrap software in a complete file system that contains everything required to run (for example, code, runtime, system tools, and system libraries). This guarantees that the software always runs the same way, regardless of environment. For more details, see

Specific accounting flows may need new Rule Engine installations that can be difficult, time-consuming and costly. Running your Rule Engine system in Docker makes it easy to quickly install, build, test, and run Rule Engine instances in containers. AccountingIntegrator supports Docker version 1.17.x.

Note   By default, a container does not have resource constraints and can use as much of a given resource as the host’s kernel scheduler allows. If you need to set constraints, ask your system engineers .

This topic assumes that you have working knowledge of AccountingIntegrator architecture and Docker. For more details, see the following:

In this section:

  • Run pre-built Docker images
  • Axway provides pre-built Docker images (CentOS Linux 7 base image only), which you can download from Axway Support.
  • For more details, see Run pre-built Rule Engine images.
  • Create custom Docker images using scripts
  • Axway provides Docker files to enable you to create custom Docker images for Rule Engine. You can deploy these images in Docker containers on any host operating system or cloud platform that supports Docker (for example, IBM Bluemix or Amazon Web Services).
  • For more information, see Generate custom Rule Engine Docker images.

For more details on Docker, see the following:

Related Links