See startup log 11:08:23,987 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named EventProcessorManager in deployment unit deployment "overlord-rtgov.war" are as follows: java:global/overlord-rtgov/EventProcessorManager!org.overlord.rtgov.internal.switchyard.EventProcessorManager java:app/overlord-rtgov/EventProcessorManager!org.overlord.rtgov.internal.switchyard.EventProcessorManager java:module/EventProcessorManager!org.overlord.rtgov.internal.switchyard.EventProcessorManager java:global/overlord-rtgov/EventProcessorManager java:app/overlord-rtgov/EventProcessorManager java:module/EventProcessorManager
This component is different from the EventProcessorNetwork Manager - this component is responsible for listening for events from switchyard, so is fine in the rtgov client installation.
I overlook it is not EventProcessor-NETWORK-Manager