Resolving WebSphere Application Server Using Shortname w/out Modifying Name Resolution Setup
 Technote (troubleshooting)
 
Problem(Abstract)
This applies to situations where proper DNS server setup or etc/hosts client setup are NOT possible in customer production environment and shortname is required for Java™ or web client to resolve to IBM® WebSphere® Application Server.

NSLookup can be used to verify shortname, fully qualified hostname and IP address resolution prior.
 
Cause
Client and/or Server name resolution not properly setup.
 
Resolving the problem
The serverindex.xml uses shortname through Interoperable Object Reference (IOR) to register w/ Location Service Daemon (LSD) and can be modified to use fully qualified hostname or IP address on the WebSphere Application Server end.

Additionally, com.ibm.CORBA.LocalHost property in Servers > Application Servers serverName > ORB Service > Custom Properties should be set to the same IP address or fully qualified hostname.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server for z/OS System Management/Repository OS/390, z/OS 5.0, 5.1, 5.3.0 All Editions
Application Servers WebSphere Application Server Enterprise Security All Platforms 5.x All Editions
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1173057
IBM Group: Software Group
Modified date: Sep 18, 2007