Some WebSphere MQ Everyplace queue managers are capable of exchanging messages with WebSphere MQ, and some are not. Those which can are said to be bridge-enabled or bridge-capable. Put simply, a bridge-enabled queue manager is one which runs in an environment capable of supporting theWebSphere MQ Java classes, and when the WebSphere MQ bridge software is available for the JVM to load.
When a WebSphere MQ Everyplace queue manager is activated, it attempts to load the WebSphere MQ bridge software component. If you can load all of the WebSphere MQ Everyplace classes and dependent software, the queue manager can later report that it is bridge-capable. If you cannot load the required Java classes, error information is traced at that point, but the queue manager continues to activate, resulting in a queue manager which reports that it is not bridge-capable.