Remote Engines (PUs) and the MM-tools Utility
You can deploy engines and start and stop remote engines (PUs) at the command line using the MM command line utility named mm-tools.
All engines have to be predefined in the site topology file.
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.
Prerequisite Configuration
- For deployment, SSH must be running on the remote machine.
- For remote start, the software that MM uses to start a processing unit on remote machines must be running: TIBCO Hawk, PsTools or SSH. See Software for Remote Start and Deployment for details.
- The site topology file (and its prerequisites) must also be configured correctly. See Site Topology and sections following for details.
In addition, the mm-tools.tra file must be configured as explained in this section.
- Configuring the mm-tools.tra File
The mm-tools.tra file is used to reference the cluster’s site topology file. - Using Public Private Key Authentication with mm-tools
Users are authenticated using certificates when performing deploy and remote start and stop operations. - Deploying Starting or Stopping a Remote Engine
When deployment is done through SSH, remote start is done using the method configured in the site topology file start-pu-method setting.
Copyright © TIBCO Software Inc. All rights reserved.