Install and Configure Software for Remote Start and Deployment

The following table shows which software utilities can be used to perform remote operations. Information about installation and configuration of each software utility follows. Use the software utility’s documentation for more details.

Software Options for Deployment, Remote Start, and Remote Method Invocation
Software Deployment Remote Start, Stop Remote Method Invocation
SSH Yes Yes  
PsTools (Windows)   Yes  
TIBCO Hawk®   Yes Yes
JMX (required)     Yes

Although it is possible to use more than one utility for the machines in the cluster, it is good practice to use only one across all the machines. Ensure that the software is installed and running on all relevant machines.

Tip: The software you use on each machine in the monitored cluster is specified in the cluster’s site topology file. See Start PU Method Setting.

SSH

Only SSH software enables MM to deploy Core Engine to the predefined hosts, that is, those configured in the monitored cluster’s site topology file. SSH can also be used to start remote engines.

The SSH utility is available on UNIX machines by default. No action is required. On Windows machines you must install an SSH server, as explained below.

Installing and Configuring an SSH Server

If you want to use SSH on Windows machines, download the software and install it. Many SSH servers are available. For Windows, OpenSSH and Copssh are supported.

Tip: Configuring OpenSSH

TIBCO has tested with OpenSSH software. See the TIBCO API Exchange Gateway readme file for specific versions that are supported.

If you use the OpenSSH server, note the following when installing OpenSSH:

  • The OpenSSH package is not a part of the default Cygwin installation. During its installation, select the OpenSSH package. Also select the option "Select required packages (RECOMMENDED)" to install all the required packages to satisfy the dependencies. See OpenSSH server documentation for details.
  • Accept the default user name suggested when configuring the OpenSSH server and provide a password for the user name.
  • For deployment and starting PUs, use a user name that is SSH enabled to login to the remote host. For example, ssh username@hostname. The credentials of the user name can be specified in the host settings of the site topology file, Host Settings User and Password fields. See Host Settings.

    However, if you choose to use a different user name, ensure that the user name is added to the SSH server.