PK86318: ConfigureWebserverDefinition does not correctly create webserver definition when Web Server hostname is IP address

Fixes are available

APAR status

Closed as program error.

Error description

If the webserver hostname is specified as 172.168.1.5 (for
example) in configure<WEBSERVER_NAME>  script and
webserverNodeType is unmanaged and a node with name like 172%
(172.168.20.25 for example) already exists on WebSphere
App. Server, configureWebserverDefinition.jacl script which
consumes the parameters in the batch script incorrectly parses
the webserver hostname and then creates the webserver
definition under 172.168.20.25-node instead of 172.168.1.5-node.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0 who use an IP Address  *
*                  instead of the Fully Qualified Domain Name  *
*                  to specify the Web Server hostname in the   *
*                  configure<WEBSERVER_NAME> script which is   *
*                  used to create a Webserver Definition       *
****************************************************************
* PROBLEM DESCRIPTION: When the Web Server Hostname in         *
*                      configure_<WEBSERVER_NAME> script is    *
*                      specified as a numeric IP and           *
*                      nodeType is unmanaged, the webserver    *
*                      definition created in WebSphere         *
*                      Application Server may be on the        *
*                      incorrect node.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the Web Server Hostname in configure_<WEBSERVER_NAME>
script is specified as a numeric IP and nodeType is unmanaged,
the webserver definition created in WebSphere Application
Server may be on the incorrect node. This problem only occurs
if there is an existing node with the same prefix as the
WebServer IP address. For example, if Web Server Host IP is
172.168.1.5 but WebSphere Application Server already has a
nodename 172.200.1.33(for example), the webserver gets created
in the 172.200.1.33-node instead of the 172.168.1.5-node. The
configureWebserverDefiniton.jacl scripts incorrectly stops the
IP Address comparison at the first dot (.)

Problem conclusion

The configureWebserverDefintion script now checks the format of
the Web server host name, if it is an IP address the short-name
is not extracted but if it is a fully qualified host name, the
short name is extracted.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.29 and 7.0.0.7.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK86318
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-11
Closed date
2009-08-03
Last modified date
2009-12-10

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

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK86318: ConfigureWebserverDefinition does not correctly create webserver definition when Web Server hostname is IP address

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?