Resolution:

Title:

= = =

When configuring TIBCO BusinessEvents Monitoring and Management (MM) to monitor a TIBCO BusinessEvents (BE) project that uses well-known-address (WKA) discovery, why does BEMM always connect to the to be monitored BE Cluster metaspace with the default tibpgm discovery method?

Description:
=========
A user has a BE project that uses WKA discovery and also use BEMM. They have the following property defined at the cluster level in the to-be-monitored project's Cluster Deployment Descriptor(CDD) file:
>>>>>>>>>>>>
<property name="be.mm.cluster.as.listen.url" value="tcp://127.0.0.1:8224"/>
<<<<<<<<<<<<

Also added is the value of the be.mm.cluster.as.listen.url property to the list of addresses in the be.engine.cluster.as.discover.url property. The be.engine.cluster.as.discover.url property is defined for each PU at the PU level. For example, each PU has the following properties defined:

>>>>>>>>>>>>>>>
        <property name="be.mm.cluster.as.listen.url" value="tcp://127.0.0.1:8224"/>
        <property name="be.engine.cluster.as.discover.url" value="tcp://127.0.0.1:8222;127.0.0.1:8223;127.0.0.1:8224/"/>
<<<<<<<<<<<<<<<

Why does BEMM always connect to the to be monitored BE cluster metaspace with the default tibpgm discovery method at the default port (50000)?

>>>>>>>>>
Connected metaspace name=[mi3mon], listen=[tcp://127.0.0.1:8224], discovery=[tibpgm]
member joined: 127.0.0.1:8224
2012 Jun 07 21:53:04:917 GMT -5 mm Info [main] - [com.tibco.cep.runtime.service.dao.impl.tibas.ASDaoProvider] Connecting to [Metaspace:be_internal_mm] on ports [default] and [default]
ip_address=192.168.1.108 port=50000
Connected metaspace name=[be2012 Jun 07 21:53:11:032 GMT -5 mm Info [main] - [com.tibco.cep.runtime.service.dao.impl.tibas.ASDaoProvider] Connected to [Metaspace:be_internal_mm] member-id=c0a8016c-c35
0-4fd16910-3a5 on ports [tcp://192.168.1.108:50000] and [tibpgm] - version 1.1.1.V33
_internal_mm], listen=[tcp://192.168.1.108:50000], discovery=[tibpgm]
member joined: 192.168.1.108:50000
<<<<<<<<<

Environment:
=========
TIBCO BusinessEvents 5.0.1

Cause:
=====
BEMM always loads the Cluster configuration defined at the cluster level. PGM multicast is the default discovery method. If BEMM does not find the be.engine.cluster.as.discover.url at the cluster level, it considers the default setting and connects with default PGM multicast discovery method (tibpgm) to the default port (50000).

Resolution:
========
Add the be.engine.cluster.as.discover.url property at the cluster level of the to be monitored project’s CDD file.

<property name="be.engine.cluster.as.discover.url" value="tcp://127.0.0.1:8222;127.0.0.1:8223;127.0.0.1:8224/"/>

Why does BEMM always connect to the to-be-monitored BE Cluster metaspace with the default tibpgm discovery method?