Table 16 Site Topology — Site Settings
Table 17 Site Topology — Cluster Settings Read-only field displaying to the CDD name specified in the master CDD. This name is set in the Cluster Name field of the CDD editor. Location and name of the CDD local to BusinessEvents Studio. If BusinessEvents Studio Explorer is running on the same EAR. This is the location used by the MM server. See Project, Master, and Deployed CDD and EAR Files.
Name of the deployment unit. It can be helpful to include the operating system of the host to which you will deploy this DU in the DU name. If a DU contains any host-specific settings, it’s also a good idea to put the host name in the DU name.Default value is DU_n where n is a number that increments each time you add a DU to the diagram. Displays a list of processing unit configurations. See Configuring the Site Topology for the procedure of adding and configuring processing unit configurations.
The name that identifies this configuration of the processing unit specified in the Processing Unit setting (see below). Check this checkbox to use the value of the Processing Unit Configuration Name field as the engine name. Select the processing unit you want to use. Only processing units configured in the master CDD display in the list for selection. When more than one PU is deployed on the same host (in one DU or multiple DUs), you must ensure the JMX port in each of these PUs is different.MM passes this JMX Port number to the variable in the command line it composes when starting a BusinessEvents engine:The JMX port number in turn is passed to the following property in the be-engine.tra file:However, if you start a BusinessEvents engine from command line outside of MM and you use a different JMX port from the one specified in the topology file then the engine starts as an undefined engine.
Copyright © TIBCO Software Inc. All Rights Reserved.