![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Before you can use the mm-tools utility you must configure it. Optionally, you can authenticate a user using certificates when performing deploy and remote start and stop operations, which requires additional configuration.Before you can use the mm-tools utility, you must configure the mm-tools.tra file to reference the cluster’s site topology file.
•
• The site topology file (and its prerequisites) must also be configured correctly. See Site Topology Overview and sections following for details.In addition, the mm-tools.tra file must be configured as explained in this section.BE_HOME/mm/bin/mm-tools.tra
2. September 10, 2014 2:05 pm.topology.file pathToTopology/toplogy.st
3. For remote start, if the start-pu-method in the site topology file is Hawk, and you use non-default values, uncomment and specify the following Hawk properties. Use the values that are configured for the Hawk agent running on the remote machine:
#be.mm.tools.Domain=TIBCO Hawk Domain#be.mm.tools.TIBHawkService=Rendezvous daemon used by Hawk#be.mm.tools.TIBHawkNetwork=Rendezvous network used by Hawk#be.mm.tools.TIBHawkDaemon=Rendezvous service used by Hawk
If Hawk is also used for machine level metrics, the values specified would be the same as those specified in the MM.cdd See Install and Configure TIBCO Hawk for Machine Level Metrics.To authenticate a user using certificates when performing deploy and remote start and stop operations, do the following.
1. On the computer hosting the MM server, use a utility to create a public/private key pair. The ssh-keygen utility is widely available. Two files are generated. They are referred to as follows:PK_FILE_NAME: The file containing the private keyPK_FILE_NAME.pub: The file containing the public keyPlace both generated files in the same directory on the computer hosting the MM server. For example, put them in BE_HOME/mm/certificates.
2. On computers hosting the to-be-monitored cluster PUs that you want to remotely deploy, start, or stop, copy the contents of the PK_FILE_NAME.pub file to the file containing the list of authorized keys for the user who will be logging in remotely.For example, for SSH using certificates for authentication, the authorized keys file is called 'authorized_keys' and it is stored in the .ssh directory of the user who will be logging in remotely, that is, in ~/.ssh/authorized_keys.-pkf The fully qualified path to the PK_FILE_NAME file, that is, the file with the private key.-pph The passphrase, if you specified one when creating the public/private key pair. (One example below shows the -pph option.)mm-tools --propFile mm-tools.tra -op deploy -m 100.100.100.101 -pkf BE_HOME/mm/certificates/PK_FILE_NAMEmm-tools --propFile mm-tools.tra -op deploy -m 100.100.100.101 -pkf BE_HOME/mm/certificates/PK_FILE_NAME -pph passphrasemm-tools --propFile mm-tools.tra -op start -puc CS -m 100.100.100.101 -pkf BE_HOME/mm/certificates/PK_FILE_NAMEmm-tools --propFile mm-tools.tra -op stop -puc CS -m 100.100.100.101 -pkf BE_HOME/mm/certificates/PK_FILE_NAMEDeployment is done through SSH. Remote start is done using the method configured in the site topology file start-pu-method setting.
BE_HOME/mm/bin/mm-tools [-h] [--propFile StartupProperty File] -op [deploy | start | stop] -m MachineHostName [-puc ProcessingUnitConfig] [-user UserName] [-pwd Password>]
Table 18 mm-tools Utility Options When you execute mm-tools, by default it looks in the working directory (the directory where you execute the command) for a property file of the same name (mm-tools.tra). This property file provides startup values and other parameters to the executable.You can specify the path and filename of a startup property file explicitly using the --propFile parameter.For example, if you execute the command from a directory other than BE_HOME/mm/bin, then you would generally use --propFile to specify BE_HOME/mm/bin/mm-tools.tra. deploy: The deploy operation is done through SSHstart: The start operation is done using the mechanism defined in the site topology file start-pu-method setting.stop: The stop operation is done using the mechanism defined in the site topology file start-pu-method setting. For the deploy option: The username used by SSH on the remote machine.For the start option: The user name used to log on to the remote machine for remote start. For the deploy option: The password for the username used by SSH on the remote machine.For the start option: The password for the username used to log on to the remote machine for remote start.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |