Server connection or publishing problems when connecting to a remote WebSphere Application Server
Important: Applicable to WebSphere®
Application Server traditional
An incorrect host name that is specified to a remote WebSphere Application Server
can cause unexpected behavior from the workbench:- When you use the remote method invocation (RMI) port to connect to the server, the status of the server displays Stopped in the Servers view; given the server is started.
- When you are using the SOAP port to connect the server, the status of the server displays correctly in the Servers view; however when you attempt to publish, the server becomes unresponsive.
To troubleshoot and determine that the host name is configured
correctly, complete the following steps:
- Verify that the correct host name is specified by matching the
values that are specified in the server editor and the serverindex.xml configuration
file.
- In the Servers view, right-click the server and select Open. The server editor opens.
- Under the General Information section,
verify the value that is specified in the Host name field
matches the value that is specified for the hostName parameter
in the serverindex tag that is defined in the serverindex.xml file.
The serverindex.xml file can be found on the
remote machine that is running the WebSphere Application
Server in the following directory: <WAS_install_directory>\profiles\<profileName>\config\cells\<cellName>\nodes\<nodeName>,
where WAS_install_directory is the installation
directory of the remote WebSphere Application
Server.Tip: If you notice that the actual host name of the remote machine is different from the host name that is specified in the serverindex.xml file, see the Limitation on the workbench to work with a WebSphere Application Server that changed its host name topic for details on updating the host name in the server configuration files.
- If the Domain Name System (DNS) is not available or you see problems when you resolve host names into IP addresses, try configuring the hosts file from the operating system that runs the workbench. In the hosts file, add a mapping of the IP address and host name of the remote machine that runs the server. The location of the hosts file in the file system varies between operating systems. See the publications of the operating system for information on where to find the hosts file and how to add the mappings.
- Verify that there is a connection between the local and remote
machine by testing the connection with a ping request.
- In the local machine that is running the workbench:
Open a command prompt
Open a terminal window
- Type:
Where host name is the name of the remote computer that is running the server:ping <host name>
- The ping command displays whether there is a reply from the host
and how long it takes to receive a reply. If there are network connection
problems, the response from the ping command returns an error message,
for example.
Ping request could not find host <hostname>. Please check the name and try again.
- In the local machine that is running the workbench: