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 and IP address.
When possible, use the graphical site topology file editor in TIBCO BusinessEvents Studio. It provides validation and structure that are helpful.
When working on runtime installations, however, it may not be possible to use TIBCO BusinessEvents Studio. An annotated site topology file template is available, so you can edit the XML-based topology file in a text editor. It is located here:
Using the canvas-based editor in TIBCO BusinessEvents Studio, you create a visual representation of the desired site topology. Property sheets let you configure each item represented by the topology diagram icons: the cluster, hosts, deployment units, and processing unit configurations.
1. Configure Cluster Properties In the Cluster Properties tab, reference the fully configured CDD and EAR files for your project. See
Project, Master, and Deployed Locations of CDD and EAR Files for more on the use of these files.
2. Add Deployment Units (DUs) Add DUs to the canvas as needed. For each DU, specify the following:
3. Add Processing Unit Configurations (PUCs) to DUs For each PUC, select one processing unit (PU) from the list of PUs defined in the CDD file. Set deploytime properties such as the JMX ports used by MM to communicate with the deployed engine.
4. Add Hosts Here you specify the machine configuration, including the software used on the remote machines to start remote machines. Connect hosts to the DUs you want to deploy on them. Multiple hosts can use the same deployment unit, as long as the configuration is the same in each case.
The project and master CDD can be in the same location if you are using one machine to configure the topology file and to run MM server. These two sets of fields are available in case you are configuring the topology on a different machine from the MM server machine.
In general, you can reference one processing unit multiple times to create different processing unit configurations (PUCs). However processing units that have deployment-specific settings cannot be used in this flexible manner.
If a processing unit contains agent-instance-specific properties (such as agent key and priority settings), you must use it in only one PUC, which is used in only one DU, that is itself used only once in the deployment.
PUs whose tangosol.coherence.localhost property is set to a specific IP value are host-specific. If a deployment unit contains a PUC that references such a PU, you must link it only to the host with that IP address.