InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.2: Command line administration >
6.6.0.2.2: WebSphere Control Program (wscp) >
6.6.0.2.2.2: Command syntax and usage >
6.6.0.2.2.2.4: Connecting to local and remote nodes
6.6.0.2.2.2.4: Connecting to local and remote nodes
When you invoke wscp, you are automatically connected to the
administrative server running on the local machine. (The host name is
defined in the default .wscprc property file.) To connect to a
remote node (that is, to specify the host name of a remote administrative
server), set the property wscp.hostName to the name that a domain name
system (DNS) server can resolve. For example, the following property
specifies that the administrative server running on myHost is to be
used:
wscp.hostName=myHost
This property can be set in the default .wscprc file. You can also
use the -p option of the wscp command to specify a different
property file to use. See 6.6.0.2.2.2.2: Invoking and terminating wscp for information on the .wscprc property file.
Note: Communication problems between Linux nodes
On some Linux installations, WebSphere Application Server Version 4.0.x
might have difficulty communicating between nodes. In particular, the difficulty communicating between
nodes affects the ability of the administrative console to control the remote WebSphere administrative servers.
This is due to the way some Linux distributions configure the /etc/hosts
file to map the host name to the loopback port instead of the external Internet Protocol (IP)
address.
If you encounter communication problems between nodes, update the /etc/hosts
file to map the host name to the proper external IP address. For example:
127.0.0.1 localhost
9.x.x.x yourhostname.yourdomain yourhostname
|