Basic MM Configuration : Site Topology Reference

Site Topology Reference
Site Settings
 
Cluster Settings
 
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.
Deployment Unit Settings
 
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.
Processing Unit Settings
 
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.
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.
 
Host Settings
 
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.
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.
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).