The underlying Embedded Messaging component delivered with
the WebSphere Application Server V5.0 or V5.1 fails to install due to the
failure of certain language fileset installations. This is caused by
non-UNIX® or other case-insensitive filesystems.
The following is an example of a failing fileset in the
install_root/logs/mq_install.log:
installp: APPLYING software for:
mqm.msg.Zh_TW 5.3.0.1
installp: Cannot change to directory /usr/lpp/mqm.msg.Zh_TW.
Check path name and permissions.
installp: CANCELLED software for:
mqm.msg.Zh_TW 5.3.0.1
Filesets processed: 3 of 22 (Total time: 8 secs).
installp: APPLYING software for:
mqm.msg.zh_TW 5.3.0.1
|
Many language filesets for Embedded Messaging on WebSphere Application
Server V5.0 or V5.1 CDs have small differences in capitalization of a
single character. These filesets are found in the CD's
operating_system/WAS/messaging/images/ directory.
Copying a CD or expanding a zipped or tarred WebSphere Application Server
installation image intended for a case-sensitive system such as UNIX to a
case-insensitive one such as Microsoft® Windows® or Macintosh OS X will
result in these slightly-differing filesets being overwritten.
In the preceding example, the file mqm.msg.Zh_TW 5.3.0.1 was
overwritten by the mqm.msg.zh_TW 5.3.0.1 in the installation
image. So, when Embedded Messaging is installed, it can only install one
of these similar filesets instead of both, causing the entire Embedded
Messaging installation to fail.
|