PQ46386: TRYING TO BIND THE ADMINSERVER AND NODE AGAINST A VIRTUAL HOSTNAME TO A IP ADDRESS ON AN SP NODE.


APAR

APAR status
Closed as user error.

Error description
Often as is the case with SP nodes one wants the node name
to resolve a name associated with NIC other than the primary.
.
This can be achieved by adding the following directive to the
top of<WAS_ROOT>/bin/admin.config before STARTING THE ADMIN
SERVER FOR THE FIRST TIME AND POPULATING THE ADMIN REPOSITORY:
.
com.ibm.ejs.sm.adminServer.nodeName=someSpecificNodeName.
.
After doing this I *cannot* run 'adminclient.sh
someSpecificNodeName' on the WAS host *and* the nanny process
dies with the errors as copied to you.
An NT client *can* run
'adminclient.bat someSpecificNodeName' so long as primaryNode is
set to someSpecificNodeName.
SERVER FOR THE FIRST TIME AND POPULATING THE ADMIN REPOSITORY:.com.ibm.ejs.sm.adminServer.nodeName=someSpecificNodeName..After doing this I *cannot* run 'adminclient.shsomeSpecificNodeName' on the WAS host *and* the nanny processdies with the errors as copied to you.An NT client *can* run'adminclient.bat someSpecificNodeName' so long as primaryNode isset to someSpecificNodeName.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
If the admin server is configured to run(listen) on IP address
a.a.a.a then in order for the admin console to connect it *MUST*
be given the same IP address as below,
.
adminclient.sh a.a.a.a or
adminclient.sh <hostname string> where "hostname string"
resolves to IP address a.a.a.a
.
There is *NO* way for the admin console to connect via
adminclient.sh B
.
where B resolves to b.b.b.b even though it is an IP address
for an NIC on the same physical box.
.
Admin servers are bound(listen) to an IP address and can
receive requests directed to only that IP address.
APAR information
APAR numberPQ46386
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED USE
PENoPE
HIPERNoHIPER
Submitted date2001-02-23
Closed date2001-03-29
Last modified date2001-03-29

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros

Fix information
APAR is sysrouted TO one or more of the following:Modules/Macros

Applicable component levels











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ46386
IBM Group: Software Group
Modified date: 2001-03-29