Starting multiple TIBCO BusinessEvents Management (BEMM) Servers on same network.

Starting multiple TIBCO BusinessEvents Management (BEMM) Servers on same network.

book

Article ID: KB0093420

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Description:
Starting multiple TIBCO BusinessEvents Management (BEMM) Servers on same network.

Resolution

Each BEMM Server creates its own TIBCO ActiveSpaces (AS) cluster and joins the AS cluster as a member for each deployed application. It is required to update the default discoveryURL for the BEMM Server and the deployed applications to avoid agents joining the wrong cluster. To do this, update the MM.cdd and define a unique discoveryURL (CDD-> Cluster -> Object Management [Cache] -> DiscoveryURL)

Example:

test system: tibpgm://9997
dev system: tibpgm://9998

Additionally update the discoveryURL for each application (<application>.cdd)

Example:

app1 test system: tibpgm://9912
app2 test system: tibpgm://9913

app1 dev system: tibpgm://9922
app2 dev system: tibpgm://9923


Note:

When unicast communication is used, add an additional discovery node for the BEMM Server to the discoveryURL in the application CDD (cluster area) to define the TCP connection used by the BEMM server to connect to the AS cluster.

be.mm.cluster.as.listen.url = <listenURL>

Example:

be.mm.cluster.as.listen.url = tcp://serverProd:53100

Upon BEMM server starup, the BEMM server connects to the cluster using the discovery address defined in CDD.

Issue/Introduction

Starting multiple TIBCO BusinessEvents Management (BEMM) Servers on same network.