PM45269: WEBSPHERE APPLICATION SERVER V7.0 INSTALLATION CHANGES FROM 64-BIT TO 32-BIT WHEN A FEATURE PACK IS INSTALLED.

Fixes are available

APAR status

Closed as program error.

Error description

After installing a new instance of WebSphere Application Server
V7.0, 64-bit edition, the product appears to change to the
32-bit edition.  After this occurs, application servers may not
start or function properly.  Additionally, the Profile Managment
Tool (PMT) appears to become available, even though it is not
normally available in the 64-bit edition.  The tool will not
start up properly under these conditions.

Note that this does not affect the orignal version V7.0.0.0
installer program (sometimes called the "ISMP installer") or
Custom Install Packages created by Installation Factory.  This
only affects installations delivered using IBM Installation
Manager.

This problem occurs under these circumstances:
- You have installed WebSphere Application Server V7.0
(V7.0.0.17) delivered as part of a larger product suite, such as
with WebSphere Process Server.
- WebSphere Application Server V7.0 is installed using IBM
Installation Manager, using the graphical wizard (GUI).
- During the installation process, you chose to use the 64-bit
edition of WebSphere Application Server.
- After the installation process completes, you do not exit the
Installation Manager.  Instead, you choose to install a
WebSphere Application Server Feature Pack.

Due to this defect, under those circumstances, some 64-bit
portions of the WebSphere Application Server product are
uninstalled and replaced with 32-bit portions.

Local fix

If an installation instance of WebSphere Application Server V7.0
has been affected by this problem, then it will need to be
uninstalled and reinstalled.

In order to avoid triggering this defect, there are some
alternative steps you can follow:

Solution 1:
Choose to install the WebSphere Application Server V7.0 product
using the Installation Manager graphical wizard (GUI).  Once it
has completed, exit the Installation Manager.  You may
immediately restart Installation Manager to perform further
operations such as installing Feature Packs.


Solution 2:
Choose to install the WebSphere Application Server V7.0 product
and Feature Packs during the same installation operation using
the graphical wizard (GUI).  You will need to create a special
response file before starting Installation Manager.  This is
necessary to help avoid a second issue documented in APAR
PM42458.

This solution is documented outside the APAR for readability.
For complete details of this solution, please refer to technote
1508509, available here:

http://www.ibm.com/support/docview.wss?uid=swg21508509


Solution 3:
Choose to install the WebSphere Application Server V7.0 product
using silent mode.  This defect does not affect silent
installation mode.

Problem summary

****************************************************************
* USERS AFFECTED:  All users who install IBM WebSphere         *
*                  Application Server Network Deployment       *
*                  edition, Version 7 and Version 7 Feature    *
*                  Packs together using IBM Installation       *
*                  Manager GUI.                                *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere Application Server Network    *
*                      Deployment edition V7.0 64 bit          *
*                      Installation contains a 32 bit SDK      *
*                      after installing a feature pack.        *
*                      After this occurs, application          *
*                      servers may not start or function       *
*                      properly.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Installation process fails to detect the WebSphere
Application Server Network Deployment edition V7 installation
is a 64 bit installation when it tries to install a feature
pack with it in the GUI mode.  As a result, Installation
Manager uninstalls the 64-bit binary library and SDK from the
WebSphere Application Server Network Deployment edition V7 and
replaces it with the 32-bit version.

Problem conclusion

The bitmode detection logic has been changed to look for the
is64bit property under the same install profile (that is, the
installation root) for all offering packages to determine the
bitness of the existing installation.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.19.  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
PM45269
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-08-08
Closed date
2011-08-19
Last modified date
2011-08-19

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

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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM45269: WEBSPHERE APPLICATION SERVER V7.0 INSTALLATION CHANGES FROM 64-BIT TO 32-BIT WHEN A FEATURE PACK IS INSTALLED.

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

R700 PSY

Document Information

Share your feedback

Need support?