Site Topology File

The topology file contains deploytime information such as what processing units to deploy to specific machines in your environment. You need to know information about the machines that will host the agents you plan to deploy, for example information about the machines’ operating system, IP address, and login credentials.

Instructions in this section are for the tutorial scenario: all components running on one Windows machine.

Learning Points

What is a processing unit configuration?
 You define processing units in the CDD file. One PU deploys as one engine. In the site topology file you select processing units and add deploy-time configuration settings to them. They are then known as processing unit configurations (PUCs).
What is a deployment unit
 A deployment unit deploys as one or more engines. It consists of one or more processing unit configurations. It also specifies the location of the deployed EAR file and CDD file, generated by MM at deploy time. A DU can be re-used for different machines, unless it has machine-specific settings.
What is a predefined engine?
 A predefined engine is one that is configured in the site topology file. You can deploy predefined engines and monitor and manage them using MM. Unpredefined engines can be monitored if they are running but cannot be started or deployed if they are not running.
Can I edit the site topology file in a text editor?
 Editing in TIBCO BusinessEvents Studio is always preferable because it can validate the file, and the graphical editor maintains the correct structure. However, when you cannot use the graphical editor, you can use the template file to help you work with the settings in a text editor:
BE_HOME/mm/config/site_topology_template.st

More Information

See these sections in TIBCO BusinessEvents Administration:

  • Site Topology
  • Configuring the Site Topology with TIBCO BusinessEvents Studio
  • Site Topology Reference