Table 18 Site Topology — Site Settings Read-only field. Only one cluster per site is supported in this release. (Not present in the site topology XML file.) Read-only field displaying the number of hosts in this topology. (Not present in the site topology XML file.)
Table 19 Site Topology — Cluster Settings Read-only field displaying the cluster name specified in the CDD. This name is set in the Cluster Name field of the CDD editor. Read-only field displaying the version of BusinessEvents. Must match the Host Settings field of the same name.Note If you copy a site topology from a prior release into a project and open it in the current release, this field value displays the prior release version number, the field is red and it is editable. Update the field value to the current version. It again becomes a read-only field. Also change the host-level BusinessEvents Version field in a similar way: both must match. Location and name of project CDD. This is the location used by TIBCO BusinessEvents Studio for configuration of the site topology. See Project, Master, and Deployed Locations of 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.Note Paths in different operating systems are specified using different tokens. Even if the DUs are identical in all other respects, you must create different DUs for different operating systems.Default value is DU_n where n is a number that increments each time you add a DU to the diagram.
The name that identifies this configuration of the processing unit, as 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 CDD selected as the Project CDD appear in the list. The same processing unit can be used in multiple PUCs. Displays the number of agents in the selected processing unit. (Not present in the site topology XML file.) 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.See How the JMX Remote Port Number is Set at Runtimefor more details.
Table 22 Site Topology — Host Settings Machine name of the host. Used for remote access. Used to identify the host in the MM user interface. Required.Note: Specify the exact name of the host. Errors in the host name result in the host appearing in the MM Console UI as an unpredefined machine. Do not, for example, use localhost. You can use 127.0.0.1 (localhost loop back IP address) for engines running on the same machine as the MM server. The user credentials are used for remote deployment and execution, including starting a process unit.At runtime, a dialog box pops up to authenticate the user, for example when deploying a PU. If you provide a username and password here, then the dialog is prepopulated with these values. You can enter different values as needed.Enter details for the user you specified for the remote connection utility you are using. For example, if you use PsTools, you would specify domain\user for domain users.Note If you use copSSH, you must specify the same user credentials here that you use when activating a user for copSSH. See Installing and Configuring Copssh — Activating a Local User for details. Operating system of the host machine. See the product readme for a list of supported platforms. Read-only field displaying the version of BusinessEvents. Must match the Cluster Settings field of the same name.Note If you copy a site topology from a prior release into a project and open it in the current release, this field value displays the prior release version number, the field is red and it is editable. Update the field value to the current version. It again becomes a read-only field. Also change the cluster level BusinessEvents Version field in a similar way: both must match.
•
• Use SSH. If you choose Use SSH, and do not want to use the default port number of 22, then also enter the port. The host must accept a secure connection through this port. Using the default port is generally recommended because it is also the default port used by most Linux SSH servers.Note that a username and password for the remote machines are required for MM to connect (see notes for User Name and Password fields).See Install and Configure Software for Remote Start and Deployment for details on each option.
Copyright © TIBCO Software Inc. All Rights Reserved.