Remote Hosts

A Remote Host is a Control-M component that enables you to submit and execute jobs on a computer without installing a Control-M/Agent. The remote host runs all jobs assigned to its specific host ID and does not require version updates. This reduces the need to install, update, and maintain Control-M/Agents in your organization.

Remote hosts are connected to and managed by a specific Control-M/Agent. You can define multiple remote hosts from one Control-M/Agent.

The remote host connects to the Control-M/Agent using one of the following connection methods:

• SSH: Supports UNIX, Windows, z/OS USS, and PASE on AS/400. If you will be using more simultaneous connections than your current SSH server settings allows, you must increase the value for these settings accordingly.
• WMI: Supports Windows. For more information, see WMI requirements.

The following procedures describe how to set up remote hosts in your Control-M environment:

• Defining a remote host
• Converting a Control-M/Agent to a Remote Host
• Converting multiple Control-M/Agents to remote hosts

If you want to convert a Remote Host to Control-M/Agent, delete the remote host and then define the Agent, as described in Defining a Control-M/Agent component. You can also use the ctm_menu utility as described in Converting a remote host to a Control-M/Agent using the ctm_menu.

You can map remote hosts to Control-M/Agents and define default connection settings in the CCM, by right clicking the Control-M/Server and clicking Default Remote Settings. You can also use the ctmhostmap utility, as described in ctmhostmap. To list remote hosts which a Control-M/Agent can route, use the ctm_diag_comm utilty as described in ctm_diag_comm.