This component encompasses the Transaction server, and is responsible for both job routing and transactional lock handling and commit.
The M3Coordinator node is a singleton, that is, only one M3Coordinator node can operate at any time. The secondary running node takes over if the primary node is unavailable, but the two nodes cannot share the load.
The M3UIAdapter connections are routed through the M3Coordinator. If the primary node fails, all interactive sessions with M3 BE are lost, and the secondary node is available for re-logon.
To create an M3Coordinator binding for an additional host:
Click "+Add Binding"
For Grid 184.108.40.206:
Click "Bindings +Add"