Instead simple scripting interfaces are provided to allow you to script remote deployment across your integration nodes, and a Java API is also available for remote administration and deployment.
While a small amount of planning is needed to design your operation procedures for deployment, the decentralized approach has benefits.
From an operational perspective, you can perform hot rollout of new versions selectively to only some integration nodes.
From a functional perspective, you can choose to deploy different sets of Integration flows to each node, which is important for certain stateful integration flows, or sequence sensitive flows.
It is suitable for stateless integration flows exposed over HTTP or JMS, that do not require strict ordering, do not use XA transactions, and are externally load balanced.
Most WebSphere ESB deployments have some Integration flows that are suitable for an active/active deployment.