Hi Imran,
In short, the answer is no, but the terminology in your question implies you may have misunderstood the concept of an integration node in ACE terminology and what its intended use is ... let me explain ...
ACEv11 lets users define integration servers which are "stand alone" - as in they are not affiliated with an integration node at all. This would be the most appropriate choice for someone looking to run ACEv11 inside containers - the container lifecycle can then be directly affiliated with the integration server's lifecycle. The container orchestration framework (such as Kubernetes or IBM Cloud Private etc.) is then responsible for looking after the containers.
For users who are not using containers, you can run integration servers in VMs or directly in the software installed "on the metal" of a machine. In these circumstances, the servers should be affiliated with an integration node which "looks after them" ... ie The node process starts the server process and restarts them should it be needed. The node can also be configured to be highly available across physical LPARs etc. too. This approach (using servers which are owned by a node) is the traditional approach used by customers of earlier ACE versions such as IBM Integration Bus v10 and is often referred to as the Enterprise Service Bus architectural pattern.
Regardless of whether you choose to use servers which are standalone or owned by an integration node, you can still manage a network of remote servers using the REST API which they expose. The ACE product also provides a web browser dashboard which can be configured to look after multiple servers and nodes spread across multiple machines ... and you can also use the ACE Toolkit (Eclipse based IDE) for connecting to the runtime on multiple machines too.
Cheers,
Ben
------------------------------
Ben Thompson
IBM UK
------------------------------