You can run an engine on one or more remote hosts (instead of, or in addition to, on the database server). Ensure that the server has trusted access to and from the engine hosts as ccm_root.
Procedure
- To test trusted access, log on remotely, as ccm_root, to and from each database server host, engine host, and client host machine.
- If you cannot log on, edit the hosts file.
- If you cannot log on without being prompted for a password, edit the hosts.equiv (or .rhosts) file.
- For a comparison of NIS and non-NIS files used to support remote access, see Routing, services, hosts, passwords, and groups.
The following files are used to define remote engine hosts:
- The hosts file must contain the names of all database servers and the Rational® Synergy engine hosts, on every engine host or in the /etc/host file equivalent NIS file.
Host entry in the /etc/hosts file has the following syntax:
IP_address official_host_name [aliases]
The host names and aliases must be consistent among all machines.
- The /etc/hosts.equiv or .rhosts files, and its NIS equivalent, contain the names of remote hosts that are trusted on or equivalent to the local host. Equivalent hosts are given access to the local machine using rcp, remsh, and rlogin commands without a password. All client machines that perform DCM transfers must be equivalent hosts on the DCM destination machines.
Each host entry in the /etc/hosts. equiv file has a syntax like the following example:
hostname
hostname.domain_name.com
hostname.other_domain_name.com
If you are running NIS, update the NIS master hosts.equiv map. If you are not running NIS, you must edit the /etc/hosts.equiv file on every engine, client, and build machine.
Also, ensure that ccm_root is a trusted user on the database server, from each engine machine. Doing so ensures that ccm_root can log on remotely without a password in either direction.
For example, type
ccm_root in the database server
hosts.equiv file as a trusted user from machines
solaris1 and
aix1, as follows:
aix1 ccm_root
solaris1 ccm_root
Use either /etc/hosts.equiv or each user .rhosts, whichever is appropriate for your network security requirements.