Understanding IMM Architecture and Terminology (Magic xpi 4.14)

Magic xpi infrastructure is inbuilt over an In-Memory Middleware provided with the xpi installer and this is used as an underlying messaging layer for the infrastructure.

IMM-Agent: Each host running the xpi project servers (also interchangeably referred as xpi servers in this document) will need the IMM-Agent running. This agent is responsible for handling requests to stop and start xpi servers, and do health check of those servers. These IMM-Agents from multiple hosts are unified and connected via an IMM.

Let’s learn more about the components that define In-memory Middleware:

· IMM-Controller - The IMM-Controller is the process that the IMM-Agent communicates with and accepts engine start and stop requests.

· IMM-DB - The IMM-DB is the central repository where all operational data required for the IMM to func-tion is stored. This includes all xpi related runtime data, project metadata and real time execu-tion data.

· LOGDB - The LOGDB serves as a container for all activity logs generated by the xpi server.

· IMM_Tunnel - This is the Web service that resides within the IMM architecture. It handles all your external re-quests (for example, HTTP requests, TCP requests) and redirects those into the IMM-Controller.

· Monitor - The monitor serves as your central interface to provide you information and health related data about the IMM and the xpi projects running under it. This also includes the data like the graphs of your license usage, the server load, the workers and so on.