Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Basic MM Configuration : Configure the Site Topology in TIBCO BusinessEvents Studio

Configure the Site Topology in TIBCO BusinessEvents Studio
Before you begin ensure that you have a valid CDD file. The processing units that you will deploy to the various hosts are defined in the CDD. See Site Topology Overview for important information. See Site Topology Reference for detailed information on the settings.
To Add a Site Topology Diagram
Disable Animation to Avoid Display Issues  Animation can cause display problems. To disable animation, go to Windows > Preferences > TIBCO BusinessEvents > Diagram. In the Animation section, uncheck the Allow checkbox.
1.
2.
3.
4.
Click Finish. You see the site topology editor, showing the cluster bar icon and site globe icon, ready for you to build the site topology diagram:
To Configure the Site Topology
1.
2.
See Project, Master, and Deployed Locations of CDD and EAR Files for details.
3.
A connection arrow appears automatically, connecting each deployment unit to the cluster.
4.
Click Add and add one or more processing unit configurations (PUCs) to the deployment unit.
See Deployment Unit Settings for details.
5.
See Processing Unit Settings for details, especially on JMX port.
6.
7.
See Host Settings for details.
8.
Right-click to stop connecting.
To remove a connection, right-click to stop connecting, then right-click a connection arrow and click the Delete option.
9.
Specifying the Site Topology Files for the MM Server
The MM server parses and loads all the site topology files, except the template file site_topology_template.st, located at BE_HOME\mm\config.
For backward compatibility, MM server loads the site topology file specified using the property be.mm.topology.file in the MM.cdd file. However, this property is deprecated in 5.1. TIBCO recommends that you put the site topology file to the BE_HOME\mm\config location.
If the location BE_HOME\mm\config does not contain any site topology file, the MM server fails to start with an appropriate message in the log file.
If a site topology file (with the same name) is present under BE_HOME\mm\config and is also specified using the property be.mm.topology.file in the MM.cdd file, only the site topology file specified in the property will be parsed and loaded by the MM server.
In a multicluster configuration, all the Master CDD files defined on every site topology file (STF) loaded by the MM server must have the same Cache Object Model. You cannot load one STF pointing to a Master CDD using Coherence Cache/DataGrid and another STF pointing to a Master CDD using TIBCO Cache/DataGrid.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved