![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
BE_HOME/mm/config/site_topology_template.stThe output of this activity is an XML file used in MM. Summary steps are shown below. Detailed steps are provided in Configure the Site Topology in TIBCO BusinessEvents Studio.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:
•
See the note in Project, Master, and Deployed Locations of CDD and EAR Files for an important limitation when deploying multiple DUs on one machine.
• One or more processing unit configurations (PUCs). You’ll configure the PUCs in the next step.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 processes remotely. To deploy a DU to a host, connect the DU to that host in the canvas editor. Multiple hosts can use the same deployment unit, if the intent is to reuse an identical configuration on more than one machine.In the topology file, you reference three locations for the CDD and EAR files. The files in each location must be exact copies:
Processing units can host-specific settings. If a deployment unit contains a PUC that references such a processing unit, you must link it only to the appropriate host for deployment. For example, the Coherence cache provider property tangosol.coherence.localhost property is a host-specific setting, and so is the TIBCO BusinessEvents DataGrid property be.engine.cluster.as.listen.url.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |