Platform-specific tips for installing and migrating: WAS Network Deployment

	Base product	Network Deployment	IBM HTTP Server	Tivoli Global Security Kit	Temp space
Installation directory	/opt/ WebSphere/ AppServer	/opt/ WebSphere/ Deployment Manager	/opt/ IBM Http Server	/opt/ ibm/ gsk7	/tmp
Minimum free space for installation	539 MB	539 MB	18.6 MB	15.9 MB	At least 100 MB

Name	Description
B6848BA	Ximian GNOME 1.4 GTK+ Libraries for HP-UX 11.00 and 11i
BUNDLE11i	Required Patch Bundle for HP-UX 11i, February 2001 or later
PHSS_26974 (for 11.0) or PHSS_26973 (for 11i)	Korean TrueType fonts
PHSS_24937 (for 11.0) or PHSS_26977 (for 11i)	Traditional Chinese TrueType fonts
PHSS_26972(for 11.0) or PHSS_26971 (for 11i)	Japanese TrueType fonts
PHSS_26976(for 11.0) or PHSS_24975 (for 11i)	Simplified Chinese TrueType fonts
PHSS_25091(for 11.0) or PHSS_25092 (for 11i)	Common TrueType fonts

Parameter	Value
dbc_max_pct	25
maxdsiz	805306358
maxdsiz	2048000000 (when the base and Network Deployment products are on one machine)
maxfiles_lim	8196 (Change this setting before changing the maxfiles setting.)
maxfiles	8000
maxssiz	8388608
maxswapchunks	8192
max_thread_proc	3000
maxuprc	512
maxusers	512
msgmap	2048
msgmax	65535
msgmax	131070 (when the base and Network Deployment products are on one machine)
msgmnb	65535
msgmnb	131070 (when the base and Network Deployment products are on one machine)
msgmni	50
msgseg	32767
msgssz	32
msgtql	2046
nfile	58145
nflocks	3000
ninode	60000
nkthread	7219
nproc	4116
npty	2024
nstrpty	1024
nstrtel	60
sema	1 (with embedded messaging)
semaem	16384 (with embedded messaging)
semmap	514
semmni	2048
semmns	16384 (with embedded messaging)
semmnu	1024
semume	200
semvmx	32767 (with embedded messaging)
shmmax	2147483647
shmem	1 (with embedded messaging)
shmmni	1024
shmseg	1024
STRMSGSZ	65535

	Base product	Network Deployment	IBM HTTP Server	Embedded massaging	Tivoli Global Security Kit	Temp space
Installation directory	/opt/ WebSphere/ AppServer	/opt/ WebSphere/ Deployment Manager	/opt/ IBM Http Sever	/opt/ wemps and /opt/ mqm	/opt/ ibm/ gsk7	/tmp
Minimum free space for Linux for xSeries installation	470 MB	390 MB	20.4 MB on base	6 MB; 60 MB on base	11.8 MB	At least 150 MB
Minimum free space for Linux for S/390 installation	470 MB	390 MB	20.4 MB on base	6 MB; 60 MB on base	13.2 MB	At least 150 MB

	Base product	Network Deployment	IBM HTTP Server	Embedded messaging	Tivoli Global Security Kit	Temp space
Installation directory	/opt/ WebSphere/ AppServer	/opt/ WebSphere/ Deployment Manager	/opt/ IBM Http Server	/var/ mqm and /opt/ mqm	/opt/ ibm/ gsk7	/tmp
Minimum free space for installation	530 MB	460 MB	20 MB	4 MB; 40 MB on base	23.1 MB (GSKit 7); 23.1 MB (GSKit 5)	At least 150 MB

	Base product	Network Deployment product	IBM HTTP Server	Embedded messaging	Tivoli Global Security Kit	Temp space
Installation directory	C:\Program Files\ WebSphere\ AppServer	C:\Program Files\ WebSphere\ Deployment Manager	C:\Program Files\IBM Http Server	C:\Program Files\ IBM\ WebSphere MQ	C:\Program Files\ IBM\ gsK7	C:\temp
Minimum space for installation	422 MB	360 MB	20 MB	4 MB; 40 MB on base	16.8 MB	At least 150 MB

Platform-specific tips for installing and migrating

Contents

All platforms
All Linux and UNIX platforms
AIX platforms
HP-UX platforms
Linux platforms
Solaris Operating Environment
Windows platforms

See also

Install the embedded messaging feature

All platforms

If you encounter a problem such as not having enough disk space or temporary space or not having the right packages on your Linux or UNIX system, cancel the installation, make the required changes, and restart the installation.

Running servers in different code pages within a single cell is not supported

Updating all of the cluster members to the same service level

Avoiding non-ASCII special characters or double-byte character set (DBCS) characters in the name of the installation directory

Verify the SDK that WAS products install

Avoiding the use of a V5.0.x deployment manager after migrating to V5.1

Migrating from embedded messaging to WebSphere MQ requires setting the MQ_INSTALL_ROOT variable to the location of the installation root of WebSphere MQ

Ignoring the Registration panel when installing only IBM HTTP Server

Install WAS products in order on the same machine, when installing the embedded messaging component

Recovering from configuration errors when the deployment manager was not running during migration.

Install all of the Web server plug-ins during the initial installation

Recovering from an InvalidExecutableException error while starting the jmsserver process

Restarting the server after a configuration change

Updating ports for coexistence requires a WAS installation

Manually uninstalling all of the beta products before installing WAS

Install from a directory with a name beginning with the word disk fails

Accessing migration tools in the migration subdirectory on the WAS product CD-ROM

Avoiding license files with bad characters in certain languages

Planning to not use the launchClient command on the WAS Network Deployment product

Install interim fixes for the IBM HTTP Server feature and the embedded messaging feature

Uninstalling interim fixes for the IBM HTTP Server feature and the embedded messaging (WebSphere MQ) feature before installing fix pack updates to the features

Apply interim fixes and fix packs to the embedded messaging feature

Install the WebSphere Application Server product on top of WebSphere MQ

Editing the port number when choosing the coexistence option during installation

Avoiding using the installation verification test on node names that contain double-byte characters

Avoiding the use of hot keys in the Installation wizard

Downloading a refreshed PDF from the WAS Library page, or refer to the information in the information center

Logging in appropriately to pick up secondary user groups for root

Retaining the embedded messaging feature when uninstalling an instance that does not have the feature installed

Install WAS 5.1 Cumulative Fix 3

Verify that no files exist in the install_root/classes directory during installation

Platform-specific issues when dealing with network file systems

Avoiding the underscore (_) character in machine names

Avoiding the installation of the server and client feature or the client feature more than once

Locating more information about the embedded messaging feature or WebSphere MQ

Install the embedded messaging server feature if WebSphere MQ V5.3 is already installed

Logging off and back on, or rebooting a Windows machine, after uninstalling the embedded messaging feature

Planning to not use terminal services with the embedded messaging feature

Avoiding a coexistence problem between embedded messaging, IBM WebSphere Studio Application Developer Integration Edition, and IBM WAS

Using a version of Internet Explorer other than V6.0 to view the IBM HTTP Administration server

Avoiding a core that is caused by an incompatibility between functions in various C or C++ run-time libraries

Hiding one copy of the OpenSSL module so that the Apache Web server can start

Defining the name of the WebSEAL HTTP server in lower case

Bringing up the IKEYMAN administrative console with the Conversational Monitoring System option for IBM HTTP server 1.3.28 and IBM HTTP Server 2.0.47

Enabling cryptographic hardware

Using the WebSphere MQ client instead of the embedded messaging client feature

Tips that apply to all platforms

Running servers in different code pages within a single cell is not supported.
Both the IBM WAS Network Deployment node and the IBM WAS nodes must be on the same code page.

Updating all of the cluster members to the same service level
Apply the same interim fixes and fix packs to all of the WebSphere Application Server nodes in a cluster. When all of the cluster members are not at the same service level, the following exception can occur:

DRSCacheApp E DRSW0008E: Exception is: com.ibm.disthub.impl.jms.JMSWrappedException: {-1361012295|unknown|java.io.OptionalDataException|}

This error can cause memory replication to not function properly.

Avoiding special non-ASCII characters or double byte character set (DBCS) characters in the name of the installation directory.
Do not use non-ASCII special characters or double-byte characters in the directory name. This problem is a known limitation.

Verify the Java 2 SDK that WAS products install.
To verify that the Java 2 SDK on the product CD-ROM is working correctly:

Change directories to the /WAS/jdk/java/bin directory in the OS root directory on the product CD-ROM.
For example, on an IBM AIX platform...
cd /mnt/aix/WAS/jdk/java/bin

On a Windows platform...
cd CD-ROMDrive:\win\WAS\jdk\java\bin

On a Linux or UNIX platform, type the following command:
./java -version

On a Windows platform, type the following command:
.\java -version

The command completes successfully with no errors when the Java 2 SDK is intact.

Avoiding the use of a V5.0.x deployment manager after migrating to V5.1.
After a deployment manager configuration has been migrated to V5.1.x, avoid using the V5.0.x deployment manager node. Using the V5.0.x node results in an inconsistent configuration and creates an unsupported environment. Use the V5.1.x deployment manager node to manage all of the the federated nodes in that cell.

If you inadvertently start the V5.0.x deployment manager node, the deployment manager attempts to manage the same cell as the V5.1.x deployment manager, but with an older version of the configuration. Any changes made through the Version 5.1.x deployment manager can disappear after the nodes synchronize with the V5.0.x deployment manager. This problem can cause major disruptions to the operation of your cell.

It is advisable to disable the Version 5.0.x deployment manager node. Be sure to perform a backup of the configuration using the backupConfig command before proceeding. You can disable the V5.0.x deployment manager node in a number of ways. The recommended approach is renaming the config directory to something else.

Migrating from embedded messaging to WebSphere MQ requires setting the MQ_INSTALL_ROOT variable to the location of the installation root of WebSphere MQ.
When installing V5.1.x with the WebSphere MQ product as the JMS provider, use the administrative console to set the MQ_INSTALL_ROOT variable to the proper path. The installation program does not set the path when you use the WebSphere MQ product. Although WebSphere MQ is a supported JMS provider, migrating from V5.0.x with embedded messaging does not reset the variable, which still points to the installation root of the V5.0.x embedded messaging code.

Use the administrative console to set the MQ_INSTALL_ROOT to the installation root of the WebSphere MQ product.

Click Environment > Manage WebSphere Variables > MQ_INSTALL_ROOT.

Type the fully qualified file path for the installation root of the WebSphere MQ product in the Value field.

Click Apply > Save > Save to apply and save your changes.

Ignoring the Registration panel when installing only IBM HTTP Server.
If you install IBM HTTP Server on another machine by installing WAS, V5.1 and clearing all of the features but the one for IBM HTTP Server and its plug-in, the installer program displays the Registration panel. Select the check box to clear it and click Next to avoid registration, which is not required when installing only the Web server. If you do attempt to register the feature when you have not installed WAS, V5.1, you can ignore the following error:
java.io.FileNotFoundException: C:\Program Files\WebSphere\AppServer\prt\PRT_Welcome.html (the system cannot found the path specified)

Install WAS products in order on the same machine, when installing the embedded messaging component.
When installing the embedded messaging feature of the WAS product and the Network Deployment product on the same machine, install the WAS product first. Then install the Network Deployment product. Otherwise, embedded messaging installation can fail, or can install with errors.

Recovering from configuration errors when the deployment manager was not running during migration.
During migration of federated nodes, the V5.1 deployment manager must be running for the migration tools to:

Update the configuration for each federated node

Request full synchronization

If the V5.1 deployment manager is not running, failures can occur. You can correct the failures by starting the V5.1 deployment manager, running the updateVariables.jacl command in the /migration-specific-backup/variables_files directory that the migration tools create, and performing a full synchronization for the cell.

Use the following procedure to correct the problem:

Start the deployment manager with the startManager command.

Update the variables.xml files:

>cd /websphere/appserver/bin >wsadmin -f /..../websphereBackup/variables_files/updateVariables.jacl

Use the administrative console or the scripting facilities of the deployment manager to perform a full synchronization for the node.
For example, you can use the syncNode.sh or syncNode.bat script to synchronize the node.

Install all of the Web server plug-ins during the initial installation.
You must select all of the plug-ins that you require during the initial installation of the WAS product to automatically control the configuration of the Web servers. If the installer program configures the Web servers, the uninstaller program can remove the configuration from each Web server when you uninstall WebSphere Application Server. If you install the product again to add features, any Web server plug-ins that you select get configured but the uninstaller program is already configured. The uninstaller program does not remove the configuration from each additional Web server whose plug-in that you selected during the second installation.

Install a new instance of the WAS to create an uninstaller program that can remove the configuration from all of the Web servers whose plug-ins that you select. Or you can remove the configuration manually.

Recovering from an InvalidExecutableException error while starting the jmsserver process
You might get an exception while starting the jmsserver process when you install Network Deployment first and then install the base WAS product and its embedded messaging feature on the same node. The error message is recorded in the install_root/logs/jmsserver/SystemOut.log file:

[9/5/02 14:35:37:818 EDT] 36349b90 JMSService E MSGS0001E: Starting the Server failed with exception: com.ibm.ws.process.exception. InvalidExecutableException: Error creating new process. 002: No such file or directory

In addition, although the mq_install.log file might appear to contain no errors, the createMQ.nodeName_jmsserver.log file can contain I/O exceptions. These exceptions result from a corrupted installation of the embedded messaging feature caused by installing the Network Deployment product before the base WAS product. The workaround is to uninstall both products, reinstall the base WAS product, and then reinstall the Network Deployment product.

Restarting the server after a configuration change.
If you make any changes to the configuration, restart the server as noted in the messages section of the administrative console.

Updating ports for coexistence requires installing WebSphere Application Server.
Port updates for coexistence require the installation of WAS. This requirement affects port updates for IBM HTTP Server coexistence. Port updates do not occur if only the IBM HTTP Server is installed. In this case, manually update the httpd.conf file. Verify that the ports that you use are available. For example, use the netstat -a command to see ports that are being used.

Manually uninstalling all of the beta products before installing WAS.
You might experience problems if portions of the beta product remain.

To make sure that you get a clean uninstall, follow these steps:

Uninstall the beta version of WAS.
Refer to Uninstalling the product for more information.

Confirm that WebSphere MQ and WebSphere embedded messaging Publish and Subscribe (WEMPS) are uninstalled.
If not, uninstall them by using the Windows Add/Remove programs tool or Smitty/installp, whichever is appropriate. Refer to Uninstalling the product for more information about manually uninstalling on specific platforms.

Remove all of the directory trees from the earlier installations of WebSphere Application Server products.
If the stand-alone WebSphere MQ V5.3 is installed, remove the WEMPS directory only. Do not uninstall or remove other WebSphere MQ Version 5.3 items.

Install from a directory with a name beginning with the word disk fails.
Install WAS Version 5 from a folder that begins with the word disk results in an error. Provide another name for the folder.

Accessing migration tools in the migration subdirectory on the WAS product CD-ROM.
A migration subdirectory on the installation image on the CD-ROM contains the WASPreUpgrade migration tool. The WASPreUpgrade migration tool is intended for scenarios where you might save the currently installed configuration before installing the V5.1 product. One example of this situation is where upgrade the operating system as part of the V5.1 installation. You can migrate the earlier version, copy the migrated files in the backup directory to another system, update the operating system, restore the migrated files in their backup directory, install Version 5.1, and complete the migration.

You can also use the migration directory on the CD-ROM to back up a V5.1 configuration in the event of an operating system upgrade. After the upgrade, you can restore the V5.1 configuration using the WASPostUpgrade tool.

Avoiding license files with bad characters in certain languages.
Use the graphical installation interface to avoid this problem.

Planning to not use the launchClient command on the WAS Network Deployment product.
The launchClient command works on a base WAS node and on a WebSphere Business Integration Server Foundation node, where the Integration Server product extends the base product. The WAS client program does not work on a Network Deployment node.

Install interim fixes for the IBM HTTP Server feature and the embedded messaging feature.
Three different sites contain service for WAS products and features:

Download interim fixes for the IBM HTTP Server feature from the IBM Support site for IBM HTTP Server . The readme file that is bundled with the interim fix describes how to install the interim fix. You do not use the update installer program for the WAS (also known as the updateInstaller program or the Update Installation wizard) to install interim fixes for the IBM HTTP Server feature.

Download interim fixes for the embedded messaging feature from the WebSphere MQ Service download site . Download the readme file for a description of how to install the interim fix. You do not use the update installer for the WAS to install interim fixes for the embedded messaging feature.

Download any interim fixes, cumulative fixes, and fix packs for the WebSphere Application Server family of products from the IBM Support site for WAS . Cumulative fixes and fix packs do include service for the IBM HTTP Server feature and for the embedded messaging feature. Interim fixes for a WebSphere Application Server product do not include service for the IBM HTTP Server feature or the embedded messaging feature. The readme file that is bundled with the WAS interim fix, the cumulative fix, or the fix pack describes how to use the update installer program for WebSphere Application Server products to install the interim fix, the cumulative fix, or the fix pack.
Install a cumulative fix or a fix pack removes all of the interim fixes for serviceable components, except for interim fixes for the IBM HTTP Server feature or the embedded messaging feature. You must remove those manually as described in the following tip.

Uninstalling interim fixes for the IBM HTTP Server feature and the embedded messaging (WebSphere MQ) feature before installing cumulative fixes and fix packs to the features
If you have installed interim fixes for the IBM HTTP Server feature from the IBM Support site for IBM HTTP Server , or if you have installed interim fixes for the embedded messaging feature from the WebSphere MQ Service download site , the update installer program cannot uninstall interim fixes for these feature components before installing a cumulative fix or a fix pack that might include service for the features. The update installer program does uninstall interim fixes for all of the other components. If the interim fixes for the IBM HTTP Server feature and the embedded messaging feature are not uninstalled for some reason, installing a cumulative fix or a fix pack to the IBM HTTP Server feature or to the embedded messaging feature might fail, or the updated features might fail when you begin using them.

If you reinstall all of the interim fixes for either feature that are more current than the cumulative fix or the fix pack, there is no problem.

You can also choose to have the update installer skip applying cumulative fix or fix pack updates to IBM HTTP Server or embedded messaging if you do not require the updates. You can skip these updates and still apply updates to the rest of the product.

Apply interim fixes and fix packs to the embedded messaging feature.

The IBM WebSphere MQ product can coexist with the embedded messaging feature, if they are at compatible service levels. Always apply any outstanding corrective service to the stand-alone WebSphere MQ product, before installing an interim fix (from the WebSphere MQ Support site) or installing a cumulative fix or a fix pack (from the WAS Support site) that might include a service update for the embedded messaging feature.

In each of the following cases, use the readme file associated with the interim fix or with the cumulative fix or the fix pack to install the service. Do not use the update installer program (also known as the updateInstaller program or the Update installation wizard) to install interim fixes for the embedded messaging feature. Download interim fixes for the embedded messaging feature from the WebSphere MQ Service download site .

For example:

If you have the embedded messaging server and client feature and do not have WebSphere MQ, do not attempt to apply a corrective service diskette (CSD) for WebSphere MQ. Instead, go to the WebSphere MQ Service download site and download the WebSphere Embedded Messaging interim fixes for WAS V5.1.
Upgrading the embedded messaging CSD level by applying a WebSphere MQ CSD is supported only for customers with a full WebSphere MQ license.

If you have the embedded messaging client feature and a stand-alone WebSphere MQ product, apply any outstanding corrective service to the WebSphere MQ product before installing the interim fix (from the WebSphere MQ Support site) for the embedded messaging client feature or installing a fix pack (from the WebSphere Application Server Support site) for the product that includes service for the embedded messaging client feature.
If you have the embedded messaging client feature and the stand-alone WebSphere MQ product is already at the latest corrective service level, install the interim fix (from the WebSphere MQ Support site) for the embedded messaging client feature or install a fix pack (from the WAS Support site) for the product that includes service for the embedded messaging client feature.

Install the WAS product on top of WebSphere MQ.

When planning to install a WAS, V5 release on a machine that already has a copy of WebSphere MQ V5.3 installed on it, you are recommended to complete the following steps:

Ensure that all the WebSphere MQ features required by the WAS embedded messaging are installed:

- on UNIX: - for WAS Network Deployment or Client: Java Messaging - for WAS (base): Runtime, Base (or SDK), Server, Client, Java Messaging and All Message Catalogs - on Windows: - for WAS ND or Client: Java Messaging - for WAS (base): Server and Java Messaging

Ensure that WebSphere MQ v5.3 is upgraded to the appropriate prerequisite CSD level:

- CSD1 for WAS V5.0 - CSD3 for WAS V5.0.1 - CSD4 for WAS V5.0.2 and later, including V5.1

Install the WAS V5 GM release.

Install any appropriate WAS fix packs.

After the initial installation of WebSphere MQ and WAS, service WebSphere MQ independently of the WAS fix packs. For example, download and apply the WebSphere MQ V5.3 CSD4 before upgrading your WAS to V5.0.2 or before installing V5.1. This approach helps to avoid failures in uninstalling WAS fix packs.

Editing port numbers that First Steps uses after selecting the coexistence option during installation.
Change the First Steps port number for the administrative console to match the port number in a coexistence scenario.

Edit the administrative console address when First Steps attempts to open the administrative console Web address. Change the port to match the coexistence port number for the administrative console port. The following example shows how to change the address to the default coexistence port number for the administrative console port:

http://localhost:9091/admin

Avoiding using the installation verification test on node names that contain double-byte characters.
The installation verification test is not supported on node names that contain double-byte characters. See Troubleshooting the installation for more information.

Avoiding the use of hot keys while using the Installation wizard.
The Installation wizard does not support hot keys.

Hot keys do not work for any languages on any operating system platforms. For example, on the Cancel Confirmation panel, you cannot type Alt - Y or Alt - N to say Yes or No to cancel the installation.

Downloading a refreshed PDF from the WAS Library page, or refer to the information in the information center.
The Getting Started PDF on the product CD-ROM is back level. The information in the information center is more current. This is particularly true for the information related to migrating or uninstalling a migrated or coexisting node that uses the embedded messaging feature.

Download a refreshed PDF from the WAS Library page, or refer to the information in the information center before migrating, uninstalling a node after migration, or uninstalling a coexisting node that has the embedded messaging feature installed.

Logging in appropriately to pick up secondary user groups for root
When the root user on all platforms (except Windows platforms) does not belong to the mqbrkrs and mqm user groups, errors occur when installing the embedded messaging feature.

On many systems, such as SuSe Linux, if you telnet and issue the id command or the groups command, you cannot see the groups mqm or mqbrkrs even though they might exist. Solve this problem in one of two ways:

Use the ssh command to log in

Issue the su - command

After using one of the commands, verify the required groups with the id command or the groups command.

In a normal root login, issue the su command. For a real root login, issue the su - command.

Display settings for a normal root login are automatic. For a real root login, set your display environment properly to successfully view the GUI installation wizard. Otherwise, you see a message about Preparing Java(tm) Virtual Machine... and seven rows of dots, but no installation GUI and no further messages. Refer to the documentation for your platform to determine proper display settings.

See Troubleshooting the installation for a description of the error messages that you might receive if you have not picked up the required secondary groups for root.

Retaining the embedded messaging feature when uninstalling an instance that does not have the feature installed.
The wizard prompts you to uninstall the embedded messaging feature, if the feature is installed. To obey licensing rules, always remove the embedded messaging feature unless other product instances share the code.

This panel can appear whenever the embedded messaging feature is installed on the node and not just when you are uninstalling an instance that has the feature installed. For example, assume that you install the embedded messaging feature when you install the base product. Assume that you install a second instance of the base product, but do not install the embedded messaging feature with the product. If you uninstall the second instance, the Installation wizard displays the prompt to uninstall the embedded messaging feature.

Install WAS 5.1 Cumulative Fix 3.
This collection of fixes for V5.1 updates the WebSphere Application Server base product or the Network Deployment product to Version 5.1.0.3. Cumulative Fix 3 includes all of the interim fixes in Cumulative Fix 2. Cumulative Fix 3 is available at the http://www-1.ibm.com/support/docview.wss?uid=swg24006675 Web address.

Always install the latest cumulative fixes as they are released. See Cumulative Fix Strategy for WAS V5.0 and V5.1 for more information.

Verify that no files exist in the install_root/classes directory during installation.
The install_root/classes directory is reserved for testing and debugging fixes when customers call IBM Support. Having files in the directory during installation can cause various problems depending on the fix left in the directory. Verify that no files exist in the install_root/classes directory.

When IBM Support queues work for you and provides you test or debug fixes, you put the fixes in the install_root/classes directory. By default, the install_root/classes directory is picked up first in the WAS class path to let it override other classes.

This directory lets you verify or debug a fix. After accepting the test fix or finishing with the debugging of the debug fix, delete the fix from the install_root/classes directory to return the system to a working state. If you do not remove such fixes from the install_root/classes directory, you can experience errors.

Platform-specific issues when dealing with network file systems.
The installation CDs are platform specific. Each CD label identifies the platform for which it is designed to be used. The CDs for a particular platform should only be inserted and run from a CD drive that is mounted on the platform that is identified on the CD.

Install with a network file system mount:

When installing from a drive mounted on a network file system (NFS), use NFS client and server platforms with identical versions of the operating system and a well-tuned NFS, if possible. For example, if installing on an xSeries (i386) RHEL3 machine, the recommended NFS server is also an xSeries (i386) RHEL3 machine.

If you are forced to use a cross-platform NFS mount, such as when installing from CD on a Linux for S/390 system, mount the drive with the -o tcp option if the option is available. For example:

mount -o tcp mycdrom.hostname:/media/cdrom /mnt

Refer to the man pages for the mount command to see if the tcp option is available. Using a CD drive or a disk drive mounted with the default mount option (udp) is known to cause errors on some versions of Linux. Red Hat Enterprise Linux 3.0 UL1 on zLinux platforms is particularly sensitive to this problem, but the recommendation applies to all Linux platforms.

If copy CD images for one platform to an NFS disk on another operating system platform, use a command that preserves symbolic links. For example, on an AIX platform use the cp -hrp command to copy data from an HP-UX disk and preserve the symbolic links. Without the -h option, the cp command on an AIX platform attempts to resolve symbolic links when copying an HP-UX disc instead of preserving the links.

Even with the -h option, the cp command on a Solaris platform does not preserve symbolic links when copying an HP-UX disc. On a Solaris platform, use the tar -cvf command to copy data from an HP-UX disk and preserve the symbolic links.

Consult the man page for the copy command on the NFS system to understand how the platform supports copying symbolic links.

Because many NFS incompatibilities can exist among various platforms, do not use a drive mounted on a network file system to install from one operating system platform to another without first verifying that the NFS configuration is robust. For example, if your mounted CD is /mnt, issue the following command on a Linux for S/390 system to see if you have an NFS problem:

unzip -l /mnt/linuxs390/WAS/setup.jar

The proper output from the command lists all the files in the setup.jar file without error. If you encounter problems in running the command, verify that your /etc/exports file includes the no_root_squash option.

See http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/s1-nfs-mount.html for more information about the -o tcp option.

See Troubleshooting the installation for more information about possible symptoms when installing with a faulty NFS mount. Contact your system administrator for help if you continue to have NFS problems.

Avoiding the underscore (_) character in machine names.
Internet standards dictate that domain names conform to the host name requirements described in Internet Official Protocol Standards RFC 952 and RFC 1123. Domain names must contain only letters (upper or lower case) and digits. Domain names can also contain dash characters ( - ) as long as the dashes are not on the ends of the name. Underscore characters ( _ ) are not supported in the host name.

If you have installed WAS on a machine with an underscore character in the machine name, access the machine with its IP address or the localhost designator until you rename the machine.

Locating more information about the embedded messaging feature or WebSphere MQ.
For more information about the actions to take before installing the embedded messaging feature, refer to Install the WAS embedded messaging feature as the JMS provider. For more information about installing JMS providers, refer to Install and configuring a JMS provider.

For information about installing the WebSphere MQ V5.3 product, or migrating to WebSphere MQ Version 5.3 from an earlier release, refer to the appropriate WebSphere MQ Quick Beginnings book:

WebSphere MQ for Windows, V5.3 Quick Beginnings, GC34-6073

WebSphere MQ for AIX, V5.3 Quick Beginnings, GC34-6076

WebSphere MQ for Solaris, V5.3 Quick Beginnings, GC34-6075

WebSphere MQ for Linux for iSeries and Linux for zSeries, V5.3 Quick Beginnings, GC34-6078

These books are available at the WebSphere MQ messaging platform-specific books Web page .

Install the embedded messaging server feature if WebSphere MQ V5.3 is already installed.
You have a choice if WebSphere MQ V5.3 is already installed:

You can install only the embedded messaging client feature on a machine that already has WebSphere MQ V5.3.
To use WebSphere MQ Version 5.3 as the JMS provider, install the IBM WAS product with only the embedded messaging client feature. The Network Deployment product has only the embedded messaging client feature. Install and using the WAS embedded messaging client feature is recommended with either the server feature or the full WebSphere MQ V5.3 product.

WebSphere Application Server messaging applications can use the WebSphere MQ Version 5.3 product as the JMS provider. Using the client feature, however, requires that you install the WebSphere MQ V5.3 Java messaging feature.

You can install the embedded messaging server and client features on a machine that already has WebSphere MQ V5.3.
To install the embedded messaging server feature when WebSphere MQ V5.3 is already installed, upgrade WebSphere MQ V5.3:

Apply the CSD04 update to the original WebSphere MQ V5.3 release if you are running V5.0.2 of WAS.

Install the WebSphere MQ V5.3 features, server and Java messaging, which the WAS embedded messaging server feature requires.

If you install WebSphere MQ V5.3 without the required features, the installation of either embedded messaging feature of IBM WebSphere Application Server is unsuccessful because of prerequisite check errors. The Enterprise package includes installation images of the WebSphere MQ Version 5.3 product and the WebSphere MQ Event Broker product, with restricted licensing. You can use the products to install the required WebSphere MQ V5.3 features or to install the refresh release of WebSphere MQ V5.3 for use with the Enterprise product.

Logging off and back on, or rebooting a Windows machine, after uninstalling the embedded messaging feature.
If you uninstall the embedded messaging feature, log off and back on, or reboot a Windows machine before reinstalling.

Planning to not use terminal services with the embedded messaging feature.
Terminal services is not supported as a valid installation scenario when installing WAS and the embedded messaging feature.

Avoiding a coexistence problem between embedded messaging, IBM WebSphere Studio Application Developer Integration Edition, and IBM WAS.
The IBM WebSphere Studio Application Developer Integration Edition and IBM WAS both include an option to install embedded messaging. The embedded messaging option in these two products is incompatible.

To avoid this problem, do not install embedded messaging for both products on the same machine.

Using a version of Internet Explorer other than Version 6.0 to view the IBM HTTP Administration server.
Forms Proxy Settings and Proxy Cache do not behave correctly When using Internet Explorer Version 6.0 to view the IBM HTTP Administration server, the Forms Proxy Settings and Proxy Cache do not behave correctly. If you select the radio buttons that display editable fields, the fields do not display.

To work around this problem, use another version of the browser.

Avoiding a core that is caused by an incompatibility between functions in various C or C++ run-time libraries.
Depending on the order that the libraries are loaded, a core can occur or IBM HTTP Server fails to initialize. This problem is seen on various Red Hat Intel versions, and SuSE SLES and Red Hat on S/390 platforms.

Note: SLES 9 runs on 64-bit VM/ESA and z/VM zSeries environments only.

The GSKit libraries used by the IKEYMAN utility and the IBM HTTP Server SSL module require the C++ library libstdc++-libc6.1-1.so.2 file on the Intel platform and the libstdc++-libc6.1-2.so.3 file on the OS/390 platform. If the libraries do not exist, the IKEYMAN utility might provide only limited functionality and the IBM HTTP Server SSL fails to initialize. If another version of this library, or another library with a common function, loaded first, it might result in the use of an incompatible library routine.

If you encounter this problem, set the environment variable LD_PRELOAD to the following values before starting IBM HTTP Server or IKEYMAN:

Intel: export LD_PRELOAD=/usr/lib/libstdc++-libc6.1-1.so.2

OS/390: export LD_PRELOAD=/usr/lib/libstdc++-libc6.1-2.so.3

This change forces the library to load first when the application starts.

Hiding one copy of the OpenSSL module so that the Apache Web server can start.
Apache Web server fails to start when using the mod_ssl plug-in module and issuing the following command:

apachectl startssl

A problem exists with a single process that has two copies of the OpenSSL modules.

Hide the Global Security Kit (GSKit) copy of the OpenSSL modules by renaming the opt/ibm/gsk7/icc directory to opt/ibm/gsk7/icc_save.

Defining the name of the WebSEAL HTTP server in lower case.
When defining your WebSEAL HTTP Server in the administrative console, define the name of the WebSEAL HTTP Server all in lower case.

To define the name of the WebSEAL server name, click...
LTPA | Trust Association | Interceptors | com.ibm.ws.security.web.WebSealTrustAssociationInterceptor | Custom Properties | com.ibm.websphere.security.webseal.hostnames

Bringing up the IKEYMAN administrative console with the Conversational Monitoring System option for IBM HTTP server 1.3.28 and IBM HTTP Server 2.0.47

You cannot bring up IKEYMAN.

IKEYMAN does not have the Conversational Monitoring System (CMS) database option to choose from when creating a key database for IBM HTTP Server.

IKEYMAN is changed in Global Security Kit (GSKit) 7 to integrate IKEYMAN for Java Secure Socket Extension (JSSE) that is Java-based and GSKit that is C++-based. IKEYMAN is a tool used to manage digital certificates. You can now use the same IKEYMAN for WAS and IBM HTTP Server. For example, creating a Java Key Store (JKS) or a CMS key database from the same panel within IKEYMAN.

A key database enables a client application to connect to those servers that have digital certificates signed by those certificate authorities (CAs). You must perform extra steps to use the same IKEYMAN with the CMS option in addition to the JKS option. The CMS option is needed when you set up IBM HTTP Server for Secure Sockets Layer (SSL) transactions.

Set the JAVA_HOME variable to the location of the IBM Software Development Kit on the machine. If you are using WebSphere Application Server, set the JAVA_HOME variable to the Java Runtime Environment (JRE) that is shipped with WAS.

For example:

On the Linux platform: Export the JAVA_HOME=/opt/WebSphere/AppServer/java variable.

On the UNIX platform: Run the <IHS install root>/bin/ikeyman, or <WAS_HOME/>bin/ikeyman.sh command, from a command prompt to bring up the IKEYMAN administrative console.

On the Windows platform: To bring up IKEYMAN, click Start > Programs > IBM HTTP Server 1.3.28 (or IBM HTTP Server 2.0.47) > Start Key Management Utility, or run <WAS_HOME>/bin/ikeyman.bat at a command prompt.

If you cannot bring up IKEYMAN after the previous steps, perform the following steps:

Set the JAVA_HOME variable to the home of the IBM Software Development Kit for the Java platform located on your machine. If you are using WebSphere Application Server, set the JAVA_HOME variable to the JRE that is shipped with WAS.

If you are not using the JRE that comes with WAS, and the gskikm.jar file exists in your JAVA_HOME directory, rename and move the $JAVA_HOME/jre/lib/ext/gskikm.jar file to a directory that is not visible to the IBM Software Development Kit class path, external directory, and the bootstrap class path. For example, on the Linux platform: mv $JAVA_HOME/jre/lib/ext/gskikm.jar/gskfiles/gskikm.jar.org.

Ensure that the java.security file has the following providers:

You can find the java.security file in the security directory path. For example, the full path to the file on the Windows platform is C:\Program Files\IBM\Java141\jre\lib\security\java.security.

security.provider.2=com.ibm.crypto.provider.IBMJCE security.provider.3=com.ibm.spi.IBMCMSProvider

If you try to use cryptographic hardware with IBM HTTP Server, ensure that the file contains the following lines in the order that is shown here:

security.provider.1=com.ibm.spi.IBMCMSProvider security.provider.2=com.ibm.crypto.provider.IBMJCE security.provider.3=com.ibm.jsse.IBMJSSEProvider security.provider.4=com.ibm.crypto.pkcs11.provider.IBMPKCS11

If you are not using an IBM Software Development Kit or if the IBM Software Development Kit files in the lib\ext directory are older than the ones that come with the GSKit, you have to copy all the Java archive (JAR) files from the ibm\gsk7\classes\jre\lib\ext directory to the Java141\jre\lib\ext directory.

On the UNIX platform:
To bring up IKEYMAN, run the<IHS install root>/bin/ikeyman, or <WAS_HOME>/bin/ikeyman.sh command, from a command prompt.

On the Windows platform:
To bring up IKEYMAN, click Start > Programs > IBM HTTP Server 1.3.28 (or IBM HTTP Server 2.0.47) > Start Key Management Utility, or run WAS_HOME/bin/ikeyman.bat at a command prompt.

Enabling cryptographic hardware
The cryptographic token is no longer a separate item on the IKEYMAN GUI menu. It is treated as one of the key store types. You can specify the PKCS11 module name by specifying the property of DEFAULT_CRYPTOGRAPHIC_MODULE in the ikmuser.properties file as before. However, IKEYMAN no longer tries to load the dynamic link lists (DLL) or Library (LIB) at startup time to decide whether to support the cryptographic token. The value of the DEFAULT_CRYPTOGRAPHIC_MODULE property is used only for the default value shown on the GUI.

When you open the Cryptographic Token, IKEYMAN first retrieves the value of the DEFAULT_CRYPTOGRAPHIC_MODULE property in the ikmuser.properties file and pre-fill the value in the File Name and Location fields in the Key Database File > Open dialog box of IKEYMAN GUI. You can modify the value in the File Name and Location fields or click the Browse button.

Once the specified DLL or LIB is loaded successfully, you can use IKEYMAN. After opening a cryptographic token successfully, IKEYMAN displays the certificates stored in the cryptographic token.

Using the WebSphere MQ client instead of the embedded messaging client feature.
Use the client from the full WebSphere MQ installation and do not use the embedded messaging client feature. It is not necessary to install the embedded messaging client feature. Both clients are the same, except that the embedded messaging client has a licensing restriction that prohibits it from communicating with queue managers outside of the WebSphere Application Server environment.

All Linux and UNIX platforms

Summary of tips that apply to all Linux and UNIX platforms

Preparing a Linux or UNIX operating platform for the embedded messaging feature
Install to fixed locations on Linux and UNIX operating systems
Defining the prerequisite Linux or UNIX operating system groups, mqm and mqbrkrs
Creating and mounting the required journalized file system, /var/mqm, before installing WAS
Restricting access to the var/mqm/errors directory and to the messaging logging files
Verify the system cp command when using emacs or other freeware
Ignoring the desktop icon messages from InstallShield for Multiplatforms (ISMP) during installation
Avoiding setting WAS environment variables in the user profile or in the system profile
Avoiding spaces in the name of the installation directory on Linux and UNIX platforms
Moving all of the core dump files from the var/sadm/pkg directory
Starting the jmsserver process before running some Samples on UNIX platforms
Using an option on the install or uninstall commands to identify a temporary directory other than the default /tmp directory
Adding additional name space bindings with a new console user
Migrating when the SDK that ships with the product is not available
A delay occurs before the Installation wizard displays its first panel
Manually entering Launchpad Web addresses to launch the links directly from your browser
Using the tcp option to mount CD drives or disk drives in a network file system mount if the option is available
Preserving symbolic links when copying product CDs to network file server disks

Tips that apply to all Linux and UNIX platforms

Preparing a Linux or UNIX operating platform for the embedded messaging feature.
Perform this step only if you are installing the JMS provider for WAS on a Linux or UNIX operating system. You must install the embedded messaging feature to use the JMS provider that WAS provides.

If you are installing the embedded messaging feature, create two operating system groups as described in Install WebSphere embedded messaging as the JMS provider.

The Solaris Operating Environment and HP-UX also require that you increase kernel settings as described in Install WebSphere embedded messaging as the JMS provider.

For an index of platform-specific information about using the embedded messaging feature, see Tips for installing the embedded messaging feature.

Install to fixed locations on Linux and UNIX platforms
On Linux and UNIX platforms , the embedded messaging feature installs to fixed locations that you cannot override. The default locations are:

Linux and UNIX platforms other than AIX: /var/mqm, /var/wemps, /opt/mqm, /opt/wemps

AIX platforms: /var/mqm, /usr/opt/wemps, /usr/mqm

The Install WebSphere embedded messaging as the JMS provider topic describes directory locations in detail.

Defining the prerequisite Linux or UNIX operating system groups, mqm and mqbrkrs
Before you install the embedded messaging component on UNIX or Linux platforms, define the operating system groups mqm and mqbrkrs, and the user IDs needed for WebSphere embedded messaging. For detailed information, see Install WebSphere embedded messaging as the JMS provider.

Creating and mounting the required journalized file system, /var/mqm, before installing WAS
On UNIX platforms, use a partition strategy with a separate volume for the messaging data. A separate partition prevents other system activity from being affected when a large amount of messaging work builds up in the /var/mqm directory.

The /var file system is used to store all of the security logging information for the system, and is used to store the temporary files for e-mail and printing. Therefore, it is critical that you maintain free space in the /var directory for these operations. If you do not create a separate file system for messaging data, and the /var directory fills up, all of the security logging, e-mail, and printing is stopped on the system until some free space is available in the /var directory.

Restricting access to the /var/mqm/errors directory and messaging logging files
After installing WebSphere embedded messaging, restrict access to the /var/mqm directories and to the log files needed for WebSphere embedded messaging, such that only the mqm user ID or members of the mqm user group have write access. For detailed information, see Install WebSphere embedded messaging as the JMS provider and Securing messaging directories and log files.

Verify the system cp command when using emacs or other freeware.
If you have emacs or other freeware installed on your Linux or UNIX system, verify that the system cp command is being used.

Type which cp at the command prompt before running the installation program for a WAS product.

Remove the freeware directory from your PATH if the resulting directory output includes freeware. For example if the output shows /opt/freeware/bin/cp, remove the directory from the PATH.

Install the WAS product.

Add the freeware directory back to the PATH.
If you install with a cp command that is part of a freeware package, the installation completes but the Java 2 SDK that the WAS product installs, which is install_root/java, can have missing files. Some required symbolic links can be destroyed. If you remove the freeware cp command from the PATH, you can install the WAS product successfully.

To verify that the Java 2 SDK that WebSphere Application Server installs is working correctly:

Go to install_root/java/bin.

Type ./java -version.
The command completes successfully with no errors when the Java 2 SDK is intact.

Ignoring the desktop icon messages from InstallShield for Multiplatforms (ISMP) during installation.
You can ignore any messages in the log.txt file about not being able to create a desktop icon on Linux and UNIX platforms.

For instance, ignore messages that are similar to the following example when installing Network Deployment:

Setup.product.install, com.installshield.product.actions.DesktopIcon, msg1, Unable to find platform specific desktop icon information. Could not create desktop icon "Start the deployment manager" Setup.product.install, com.installshield.product.service.product.PureJavaProductServiceImpl, msg1, installing Desktop Icon (StopCellMgrIconBean) Setup.product.install, com.installshield.product.actions.DesktopIcon, msg1, Unable to find platform specific desktop icon information. Could not create desktop icon "Stop the deployment manager" Setup.product.install, com.installshield.product.service.product.PureJavaProductServiceImpl, msg1, installing Desktop Icon (AdminConsolIconBean) Setup.product.install, com.installshield.product.actions.DesktopIcon, msg1, Unable to find platform specific desktop icon information. Could not create desktop icon "Administrative Console" Setup.product.install, com.installshield.product.service.product.PureJavaProductServiceImpl, msg1, installing Desktop Icon (LogAnalyzerIconBean) Setup.product.install, com.installshield.product.actions.DesktopIcon, msg1, Unable to find platform specific desktop icon information. Could not create desktop icon "Log Analyzer"

Avoiding setting WAS environment variables in the user or system profile.
WAS products use environment variables to control many dynamic settings, such as the path to the product in the $WAS_HOME variable, the path to the /logs directory in $LOG_ROOT, or the path to the IBM Development Kit in $JAVA_HOME. Avoid setting these variables in the system profile or in user profiles. You might have a setting in a profile that overrides the proper setting. If you reset variables that the products use to function, you can produce unpredictable results, or even failure. To view WAS environment variables, open the administrative console and click Environment > Manage WebSphere Variables. Scroll down to see the variables. You can also click Next and Previous to see other pages of variables. Click a variable to see more information, including its description. Other variable settings are described on other administrative console pages.

Avoiding spaces in the name of the installation directory on Linux and UNIX platforms.
Do not use spaces in the installation directory name. Spaces in directory names are not supported on Linux and UNIX.

Moving all of the core dump files from the var/sadm/pkg directory.
The InstallShield for MultiPlatforms (ISMP) Installation wizard iterates through all of the directories in the /var/sadm/pkg directory, assuming that each entry that the wizard finds is a directory. The wizard tries to open the pkginfo file within the directory. The ISMP wizard fails when it cannot find an entry under the core file. Remove the core file from the directory to avoid the problem.

Starting the JMS server before running some Samples on UNIX platforms.
To run Samples that use JMS APIs, manually start the JMS server (jmsserver) before running the samples on UNIX platforms.

To start the jmsserver process, complete the following steps:

Open the administrative console: http://localhost:9090/admin.

Click Servers > Application Servers > server1 > Server Components > JMS Servers.

Change the Initial State from STOP to START.

Save the configuration and log out of the administrative console.

Stop and restart the Application Server from the command line. For example,

stopServer.sh server1 followed by startServer.sh server1

Using an option on the install or uninstall command to identify a temporary directory other than the default /tmp directory.
If the tmp disk does not have a large enough allocation, this message appears:

Error writing file = There may not be enough temporary disk space. Try using -is:tempdir to use a temporary directory on a partition with more disk space.

Use the -is:tempdir installation option to specify a different temporary disk to use. For example, the following command uses the /swap file system as a temporary disk during installation:

./install -is:tempdir /swap

Some space in the /tmp directory is required for a copy of the native install launcher program, the Java virtual machine (JVM), and some utility programs. ISMP uses the location you specify with the -is:tempdir parameter for its temporary work area.

Adding additional name space bindings with a new console user.
On UNIX platforms, when you click Name Space Bindings, you receive an Error 500 message on the browser. When you click Show Details, a NullPointerException displays. This only occurs with the administrative ID that was configured as the server ID.

To solve the problem, add a different user to System Management > Console Users and login with that user to add additional name space bindings.

Migrating when the Java 2 SDK that ships with the product is not available.
If you upgrade the Java 2 SDK that ships with the WAS product, and you intend to use the migration tools to migrate the configuration of a V4.0.x installation to Version 5.0.x, you can work around any Java wrapper errors that you might receive.

For example, if you upgrade to Java 2 SDK 1.3.1_08 and attempt to migrate V4.0.4 to V5.0.2, you receive a Java wrapper not found error when you issue the following command, which is shown on more than one line for clarity:

./WASPreUpgrade.sh /tmp/WAS40Backup /opt/WebSphere/AppServer wassun3 -traceString "*=all=enabled" -traceFile /tmp/PreUpgradeTrace.log

The error that you receive is about a Java wrapper not found. Create a soft link to get around the problem:

cd install_root/java/bin/aparc/native_threads
ln -s java .java_wrapper

When you call the .java_wrapper, the Java 2 SDK assumes that the Java code is called and the migration can continue.

A delay occurs before the Installation wizard displays its first panel.
The default installation method is to open a command window to a read/write directory, issue the fully qualified command to start the Launchpad tool, and click the Install the product option. This option launches the Installation wizard, which is an InstallShield for MultiPlatforms (ISMP) application. This action launches the Installation wizard in the language of your machine locale unless no translation exists for your locale, in which case you receive the English version. A short delay occurs before the ISMP wizard displays.

You do not need to click the Install the product option more than once to cause the wizard to display the first panel. The delay is particularly noticeable on x-windows platforms.

Manually entering Launchpad Web addresses to launch the links directly from your browser.
A known problem with the Launchpad can prevent it from using Netscape to open the documentation links on some operating system platforms.

If you use the Mozilla browser, some Launchpad links do not work. The Launchpad attempts to call the Netscape browser in the /usr/bin/netscape directory. Try a symbolic link to the Mozilla browser to fix the problem as shown in the following example:

ln -sf /usr/bin/mozilla /usr/bin/netscape

You can also launch the following links directly from your browser:

Product Overview

http://www.ibm.com/software/webservers/appserv/
Your security options might prevent redirection, such as to the http://www-306.ibm.com/software/info1/websphere/index.jsp?tab=products/appserv Web site. If so, you can identify the IBM Web site as a trusted site to allow the redirection. For example, on Internet Explorer, add http://www-306.ibm.com to the list of Trusted Sites by selecting Tools > Internet Options > Security (tab) > Trusted Sites.

Readme File

CDROM/readme/readme_en.html

Installation Guide

CDROM/docs/InstallGuide_en.PDF
The Installation Guide is in Adobe PDF format. Viewing this document requires you to have Adobe Acrobat Reader, which is a free download from the Adobe Acrobat Web site.

Download a new installation guide at ftp://ftp.software.ibm.com/software/webserver/appserv/library/wasv51base_gs.pdf .

See Using the Launchpad to start the installation for more information about the Launchpad program.

Using the tcp option to mount CD drives or disk drives in a network file system mount if the option is available.
Refer to the man pages for the mount command to check if the tcp option is available. Using a CD drive or a disk drive mounted with the default mount option (udp) is known to cause errors on some versions of Linux.

Red Hat Enterprise Linux 3.0 UL1 on zLinux platforms is particularly sensitive to this problem, but the recommendation applies to all Linux platforms.
Install with product CDs that are physically located on an NFS server can fail. Symptoms that occur when installing with disk 1 on an NFS server include:

An indication that the /tmp/_wbi_/jdk/java/bin/java file does not exist after issuing the launchpad.s command or the install command and the installation fails.

An indication of copy errors in the /tmp/wbisf_launcher.log file:

cp: cannot stat `/mnt/linuxs390/WAS/jdk/java/jre/lib/images': No such file or directory cp: cannot stat `/mnt/linuxs390/WAS/jdk/java/jre/lib/security': No such file or directory cp: cannot stat `/mnt/linuxs390/WAS/jdk/java/lib': No such file or directory

An indication of stale NFS file handle errors when trying to list the files under the NFS-mounted file system:

#ls /mnt/linuxs390/WAS/jdk/java/jre/lib ls.: :stale NFS file handle

An indication of server-not-responding errors in the /var/log/messages file on the NFS client:

Mar 15 16:29:59 aushat178 kernel: nfs: server svtlnx4 not responding, still trying

Symptoms that occur when installing with disk 2 on the NSF server include:

After clicking Next on the Prompt for disk 2 panel, the Installation wizard fails while copying the update installer application with an error that is similar to the following example:

Copying cumulative fix and update installer application failed. Cumulative fix or interim fixes cannot be applied. This installation is terminating.

After the failure of the installation of the cumulative fix, there are missing directories in the install_root/WAS_update directory. You can verify missing directories by comparing the directory structure to the directory structure on disk 2.

Before installing with an NFS-mounted CD or hard disk, verify that the NFS is working correctly. For example, if your mounted CD is /mnt, issue the following command on zLinux to see if you have an NFS problem:

unzip -l /mnt/linuxs390/WAS/setup.jar

The proper output from the command lists all the files in the setup.jar file without error. If you encounter problems in running the command, verify that your /etc/exports file includes the no_root_squash option. Also mount the NFS drive with the -o tcp option. For example:

mount -o tcp mycdrom.hostname:/media/cdrom /mnt

See http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/s1-nfs-mount.html for more information about the -o tcp option.

Contact your system administrator for help if you continue to have NFS problems.

Preserving symbolic links when copying product CDs to network file server disks
When copying a CD for one operating system platform to a network file system (NFS) disk on another type of operating system using the cp command, you can encounter errors such as those in the following example:

a file is bad no such file or directory exists libCSup.2 cannot be accessed
The copy error occur when incorrectly copying symbolic link files.

An example of such an error occurs when copying an HP-UX CD image onto an AIX platform with the cp -frp command. The default cp command behavior on an AIX platform is to resolve the symbolic links by copying the files to which the symbolic links point. Errors occur when a symbolic link resolves to a platform-specific library or file that is not present on the NFS operating system.
Use options on the copy command of the NFS system to copy symbolic links instead of resolving them. For example, the -h option on the cp command of the AIX platform copies symbolic links from the HP-UX CD to the NFS disk on the AIX platform.
Even with the -h option, the cp command on a Solaris platform does not preserve symbolic links when copying an HP-UX disk. On a Solaris platform, use the tar -cvf command to copy data from an HP-UX disk and preserve the symbolic links:

Insert disk 2 for HP-UX platforms into the drive on the Solaris system.

Close the file explorer window if one opens.

Open a command window.

Change directories:

CD /cdrom/cdrom0

Issue the following command:

tar cvf * /workarea/filename.tar

Change directories:

CD /workarea

Issue the following command:

tar -xvf filename.tar

Consult the man page for the copy command on the NFS system to understand how the platform supports copying symbolic links.

AIX platforms

Summary of tips that apply to AIX platforms

Provide adequate disk space for installation
Unmounting file systems with broken links to avoid java.lang.NullPointerException errors
Install the prerequisite Java130.rte.lib V1.3.0 on AIX V4.3.3 or AIX V5
Correcting directory permissions on AIX platforms before reinstalling WAS with the embedded messaging feature
A core dump might occur when running WAS with DB2 V7.2 FP8 client in AIX 5.2
Avoiding a segmentation fault problem when installing or uninstalling
Avoiding a null pointer exception during the interactive installation of the IBM HTTP Server product on AIX platforms.
Ignoring DBCS messages when you do not require DBCS support. Otherwise, install the necessary patches.
Using UNIX line-end characters (0x0D0A) to terminate each line of the options response file for silent installation
Navigating if the scroll bar disappears on the Feature panel of the Installation wizard
Ignoring error messages that appear in the log.txt installation log
Avoiding a potential port conflict between the administrative console and the WebSM system management console on AIX 5.1, with maintenance level 2.
Canceling the installation and updating your operating system before restarting the installation, if you install on an AIX machine and receive a message that a fileset is missing, such as the X11.fnt.ucs.ttf fileset
Setting up the display environment for a real root login on AIX systems
Avoiding a DSAPI filter-loading error when the Lotus Domino Server starts
Avoiding a null pointer exception during the interactive installation of the IBM HTTP Server on AIX platforms
Starting IBM HTTP Server 2.0.47 on AIX 5.2 systems
Using the AIX 5.1 and AIX 5.2 Fast Response Cache Accelerator feature with IBM HTTP Server 2.0.47

Tips that apply to AIX platforms
Provide adequate disk space for AIX platforms.
Space requirements for the embedded messaging feature are described in the Install WebSphere embedded messaging as the JMS provider topic.

Installed sizes of installation directories for AIX platforms

Base product Network Deployment IBM HTTP Server Embedded messaging Tivoli Global Security Kit Temp space
Installation directory /usr/ WebSphere/ AppServer /usr/ WebSphere/ Deployment Manager /usr/ IBM Http Server /usr/ mqm and /opt/ wemps /usr/ ibm/ gsk7 /tmp
Minimum free space for installation 450 MB 370 MB 20 MB 17 MB; 40 MB on base 32.5 MB on base 150 MB

Unmounting file systems with broken links to avoid java.lang.NullPointerException errors.
Unmount file systems with broken links before installing on an AIX system. The installation of the cumulative fix pack can fail with the following error when broken links to file systems occur:

An error occurred during wizard bean change notification: java.lang.NullPointerException at com.ibm.wizard.platform.aix.AixFileUtils. getFileSystemData(AixFileUtils.java:388) at com.ibm.wizard.platform.aix.AixFileUtils. getPartitionDataWithExecs(AixFileUtils.java:172) at com.ibm.wizard.platform.aix.AixFileUtils. getPartitionData(AixFileUtils.java:104) at com.ibm.wizard.platform.aix.AixFileServiceImpl. getPartitionNames(AixFileServiceImpl.java:397) ...

Use the df -k command to check for broken links to file systems. Look for file systems that list blank values in the 1024-blocks size column. Columns with a value of "-" (dash) are not a problem. A problem with the /dev/lv00 file system is illustrated in the following example:

> df -k Filesystem 1024-blocks Free %Used Iused %Iused Mounted on /dev/hd4 1048576 447924 58% 2497 1% / /dev/hd3 4259840 2835816 34% 484 1% /tmp /proc - - - - - /proc /dev/lv01 2097152 229276 90% 3982 1% /storage /dev/lv00 /dev/hd2 2097152 458632 79% 42910 9% /usr iw031864:/cdrom/db2_v72_eee_aix32_sbcs

The /proc file system is not a problem. The iw031864:/cdrom/db2_v72_eee_aix32_sbcs file system is a definite problem. The /dev/lv00 file system is also a likely problem. Use one of the following commands to solve this problem:

> umount /cdrom/db2_v72_eee_aix32_sbcs > umount /cdrom

Start the installation again. If the problem continues, unmount any file systems that have blank values, such as the /dev/lv00 file system in the example. If you cannot solve the problem by unmounting file systems with broken links, reboot the machine and start the installation again.

Install the prerequisite Java130.rte.lib V1.3.0 on AIX V4.3.3 or AIX V5.
On AIX V4.3.3 and AIX V5, you must install Java130.rte.lib V1.3.0 to verify that the embedded messaging feature installs correctly. To download a copy of Java 1.3.0:

Go to www.ibm.com\java: Java Technology Zone.

Go to the bottom of the page: Most popular links.

Click IBM Developer Kit for AIX.

Click Download.

Click Java 1.3.0 from the Java Version column in the table.

(Optional) Register for a user ID and password.

To correct an existing problem:

Uninstall the following components, if present:

WAS

WebSphere MQ (MQSeries)

WebSphere MQ (MQSeries) Java classes and classes for WebSphere MQ for the Java Message Service

IBM HTTP Server

WebSphere Embedded Messaging Publishing and Subscribe Edition

Edit the vpd.properties file and remove any entry related to WAS. WAS-related entries begin with:

WSB for the base WAS, V5.0.x product
WSBAA51 for the base WAS, V5.1 product
WSC for the WAS Application Clients
WSE for the Enterprise product, V5.0.x
WSN for the Network Deployment product, V5.0.x
WSNAA51 for the Network Deployment product, V5.1
WSM for the WebSphere MQ product
Reinstall the WAS product.

Correcting directory permissions on AIX platforms before reinstalling WAS with the embedded messaging feature
After manually uninstalling the WAS product and before reinstalling the product with the embedded messaging component, look for the following directory: /var/mqm/log/WAS_system_name_server. If this directory exists, confirm that the directory is empty and that the user, mqm, can open and write to it. If it is not accessible, the embedded messaging installation program throws the following error:

AMQ7064: Log path not valid or inaccessible is written in the createMQ.system_name_server.log file.
If this error occurs, the installation of the embedded messaging component fails.

Avoiding a segmentation fault problem when installing or uninstalling.
If a core dump causes the desktop to disappear while installing or uninstalling the product and leaves only the log in prompt, run the DBX utility on the resulting core file.

If you see the following output, apply the AIX PTF fix for PMR:82869,004 to solve the problem:

dbx /usr/bin/X11/X core Type 'help' for help. reading symbolic information ...warning: no source compiled with -g [using memory image in core] Segmentation fault in . at 0x10040aac 0x10040aac (???) 931d0000 stw r24,0x0(r29) (dbx) where SetFontPathElements(??, ??, ??, ??) at 0x10040aac SetFontPath(??, ??, ??, ??) at 0x10042e58 SetFontPath(??, ??, ??, ??) at 0x10042e80 ProcSetFontPath(??) at 0x10015ce4 DeleteClientFromAnySelections(??) at 0x1001e8a8

Avoiding a null pointer exception during the interactive installation of the IBM HTTP Server product on AIX platforms.
When installing IBM HTTP Server using the wizard on an AIX platform, you might receive a null pointer Java error on the installation panels when the installer begins to copy files to your machine. This error is caused by an unstable AIX ODM registry.

To work around this problem:

Exit the installer.

Issue the following command to see if any remaining registry entries for IBM HTTP Server are present:

lslpp -l|grep IHS

If registry entries for IBM HTTP Server remain, install IBM HTTP Server silently by running the following command:

java -jar setup.jar -silent -P ihs.installLocation=the desired installation location

Note: To remove the installation silently, use the -silent parameter on the uninstall command. For example, run this command from the IBM HTTP Server installation root:

java -jar _uninst/uninstall.jar -silent

Ignoring DBCS messages or installing necessary patches when you do not require DBCS support.
While installing any WAS product, you might see the following messages on AIX 5.1 and AIX 4.3.3 until you install the missing filesets.

Operating system patches of particular concern: Fileset X11.fnt.ucs.ttf_KR was not found on the system. v5.1.0.0 - Font required for Korean character display Fileset X11.fnt.ucs.ttf_TW was not found on the system. v5.1.0.0 - Font required for Taiwanese character display Fileset X11.fnt.ucs.ttf_CN was not found on the system. v5.1.0.0 - Font required for Chinese character display

Using UNIX line-end characters (0x0D0A) to terminate each line of the options response file for silent installation.
During a silent installation on AIX machines, the response file passed to the installer program must not contain ASCII line-end characters (0x0D0A). The response file must contain UNIX line-end characters only. When the options response file contains ASCII line-end characters, the install command is unsuccessful and does not log or display an error. To verify the cause of failure, use the Java argument -Dis.debug=1 on the install command. The debug information describes a service exception about invalid characters in the options response file.

Navigating if the scroll bar disappears on the Feature panel of the Installation wizard.
If the scroll bar disappears, use the up and down arrow keys to navigate the features in the Feature panel. Use the tab key to move the focus to the navigation. You can also use the mouse.

Ignoring the following error messages that appear in the log.txt installation log.
You can ignore the following error messages that might appear during installation of the base product in an umbrella installation:

WASBase, com.ibm.wizard.platform.aix.AixProductServiceImpl, wrn, - WARNING: Got invalid size of 0 for file: /usr/WebSphere/AppServer/ config/cells/ BaseApplicationServerCell/ nodes/ DefaultNode/ spi.policy: WASBase, com.ibm.wizard.platform.aix.AixRegistryServiceImpl, wrn, AixRegistryServiceImpl: Error attempting to modify AIX VPD.

Avoiding a potential port conflict between the administrative console and the WebSM system management console on AIX 5.1, with maintenance level 2.
The AIX WebSM system management server listens on port 9090 by default. If you suspect that you have a port conflict, verify it by shutting down WAS. Then issue this command:

netstat -an |grep 9090

If you get a match, another process is already listening on port 9090. If you want the WebSM server and WAS to coexist, change the WAS administrative console port when installing WAS, or after installation. Although not recommended, you can also disable the WebSM server. To disable the WebSM server, issue this command:

/usr/websm/bin/wsmserver -disable
The command permanently disables WebSM server startup.

Canceling the installation and updating your operating system before restarting the installation, if you install on an AIX machine and receive a message that a fileset is missing, such as the X11.fnt.ucs.ttf fileset.
Update your operating system if it is missing required filesets. If you receive a message that a fileset is missing, such as the X11.fnt.ucs.ttf fileset, cancel the installation, update the operating system, and restart the installation.

Setting up the display environment for a real root login on AIX systems.
In a normal root login, issue the command su. For a real root login, issue the command su -.

Display settings for a normal root login are automatic. For a real root login, you must set your display environment properly to successfully view the Installation wizard. Otherwise, you see a message about Preparing Java(tm) Virtual Machine..., and seven rows of dots, but no Installation wizard and no further messages. Refer to the documentation for your AIX platform to determine proper display settings.

Avoiding a DSAPI filter-loading error when the Lotus Domino Server starts.
On a UNIX operating system, if you start the Lotus Domino Web server from a non-root user, you are likely to generate a DSAPI filter-loading error:

Error loading DSAPI filter. Filter not loaded: /usr/WebSphere/AppServer/bin/libdomino5_http.a

Manually change the WAS bin directory permissions from 750 to 755 to run Lotus Domino Server as a non-root user and not generate the error. This change does, however, pose a security risk.

You must also change permissions on the WAS logs directory to 777 to let Lotus Domino Server write to the log.

If the Lotus Domino Server is started as root, the problem does not occur.

Avoiding a null pointer exception during the insteractive installaton of the IBM HTTP Server on AIX platforms.
A null pointer exception is thrown during the interactive installation of IBM HTTP Server on AIX systems

When installing IBM HTTP Server as a standalone installation through the administrative console on the AIX platform, you can receive a null pointer Java error on the installation panels, when the installer begins to copy files to your machine.

This situation is caused by an unstable AIX Object Data Manager (ODM) registry.

To work around this problem:

Exit the installer.

Issue the lslpp -l|grep IHS command to check if there are remaining IBM HTTP Server registry entries that cannot exist.

If there are remaining IBM HTTP Server registry entries, do a silent installation of IBM HTTP Server by running the following command:

java -jar setup.jar -silent -P ihs.installLocation=<the desired install location>

Note: To remove the installation silently, add the -silent parameter to the regular uninstall command from the IBM HTTP Server installation location, for example:

java -jar _uninst/uninstall.jar -silent

Starting IBM HTTP Server 2.0.47 on AIX 5.2 systems.
A potential IBM HTTP Server 2.0.47 startup failure exists on AIX 5.2 systems when a non-default AIX resolver configuration is used (for example, in /etc/netsvc.conf), and the IBM HTTP Server configuration file (for example, httpd.conf), uses Listen directives that do not specify an Internet Protocol address. The following example shows error messages issued by IBM HTTP Server:

[crit] (78) A remote host did not respond within the timeout period.: alloc_listener: failed to set up sockaddr for :: Syntax error on line 130 of /usr/IBMIHS/conf/httpd.conf Listen setup failed.

This error is caused by a defect in the AIX resolver library.

The defect is fixed by APAR IY40908 for AIX 5.2. The fix is shipped with AIX52B Gold and later.

Alternatively, you can take one of the following actions to solve the problem:

Use the IPv4-specific Listen directive in the IBM HTTP Server configuration file, for example, "Listen 0.0.0.0:80"

Do not override the default AIX resolver configuration.

Change the following line in the /etc/netsvc.conf file from:

hosts = local = auth , bind

to

hosts = local = auth , bind , local

Using the AIX 5.1 and 5.2 Fast Response Cache Accelerator feature with IBM HTTP Server 2.0.47.
IBM HTTP Server 2.0.47 supports the AIX 5.1 and 5.2 Fast Response Cache Architecture (FRCA) feature through the mod_afpa_cache.so plug-in module. However, install the interim fix IY49388 for AIX 5.2. IBM HTTP Server 1.3.28 does not support the AIX FRCA feature.

HP-UX platforms

Summary of tips that apply to HP-UX platforms

Provide adequate disk space for installation
Install required patches for correct character display of the installation panel on Asian language platforms
Ignoring a prerequisite checker error for a patch when a superset of the patch has been installed.
Uninstalling a V5.1 instance on HP-UX platforms before reinstalling the instance

Mounting the product CD-ROM

Configuring HP-UX kernel settings before installing WAS

Migrating or coexisting with an existing WAS node that HP-UX does not recognize

Avoiding using Netscape 4.79 on HP-UX 11 in Japanese, to avoid problems in viewing the administrative console

Configuring the converter.properties file to use EUC-JP (Japanese) encoding on HP-UX

Using certificate revocation lists (CRLs) with IBM HTTP Server on HP-UX and Linux for S/390 platforms is not supported at this time

Ignoring certain error messages when installing WAS with embedded messaging from the CD-ROM

Provide adequate disk space for HP-UX platforms.

Installed sizes of installation directories for HP-UX platforms

Base product Network Deployment IBM HTTP Server Tivoli Global Security Kit Temp space
Installation directory /opt/ WebSphere/ AppServer /opt/ WebSphere/ Deployment Manager /opt/ IBM Http Server /opt/ ibm/ gsk7 /tmp
Minimum free space for installation 539 MB 539 MB 18.6 MB 15.9 MB At least 100 MB

Space requirements for the embedded messaging feature are described in the Install WebSphere embedded messaging as the JMS provider topic.

Install required patches for correct character display of the installation panel on Asian language platforms.
The installation panel displays garbled characters on Asian language platforms, including Korean, traditional Chinese, Japanese, and simplified Chinese, for the HP-UX 11i operating system.

Verify that the following patches are installed on your HP-UX 11i machine:

Name Description
B6848BA Ximian GNOME 1.4 GTK+ Libraries for HP-UX 11.00 and 11i
BUNDLE11i Required Patch Bundle for HP-UX 11i, February 2001 or later
PHSS_26974 (for 11.0) or PHSS_26973 (for 11i) Korean TrueType fonts
PHSS_24937 (for 11.0) or PHSS_26977 (for 11i) Traditional Chinese TrueType fonts
PHSS_26972(for 11.0) or PHSS_26971 (for 11i) Japanese TrueType fonts
PHSS_26976(for 11.0) or PHSS_24975 (for 11i) Simplified Chinese TrueType fonts
PHSS_25091(for 11.0) or PHSS_25092 (for 11i) Common TrueType fonts

You can find these patches at the following URL: http://www.hp.com/products1/unix/java/infolibrary/patches.html#1 .

Ignoring a prerequisite checker error for a patch when a superset of the patch has been installed.
If you apply a superset patch that includes a specific patch that the prerequisite checker program requires, you can ignore the message from the installer program and continue the installation. You can always continue the installation whenever you see an error message about a missing prerequisite. Your can ignore the messages and continue the installation. Although the list of prerequisite patches that the installer program checks is extensive, the list does not include all of the superset patches.

For example, the installer program checks for patch PHCO_29109. The HP-UX Web site recommends that you install a superset patch, PHCO_29960, instead of PHCO_29109. After installing the patch and rebooting the machine, reinstalling the base WAS results in the same message about the missing PHCO_29109 prerequisite. You can ignore the error because you know that you have installed a superset patch.

Uninstalling a V5.1 instance on HP-UX platforms before reinstalling the instance.
If you uninstall a V5.1 instance, but leave the embedded messaging feature installed because of other WAS instances on the machine, rename the /opt/WebSphere/AppServer51 directory so that HP-UX cannot locate the earlier installation that is still registered. Reinstall into a directory other than the /opt/WebSphere/AppServer51 directory or the renamed directory. Use a new directory name for reinstalling the V5.1 instance.

If you uninstall every WAS product on the machine and are now reinstalling, follow the procedure in Manually uninstalling on HP-UX platforms instead.

For example, assume that V5.0.2 exists in the /opt/WebSphere/AppServer502 directory with the embedded messaging server and client feature. You then install V5.1 to the /opt/WebSphere/AppServer51directory, but later you uninstall the product with the uninstall command and select to leave the embedded messaging feature installed. And now you decide to reinstall V5.1.

Rename the /opt/WebSphere/AppServer51 directory to the /opt/WebSphere/AppServer51_bk directory before reinstalling V5.1 into the /opt/WebSphere/AppServer51New directory.

This step is required before you can reinstall the product onto the same system. To correct the registry entries and uninstall all of the WAS products on the machine, follow the procedure in Manually uninstalling on HP-UX platforms instead.

Configuring HP-UX kernel settings before installing.
To set kernel parameters, perform the following steps:

Log into the host machine with superuser (root) privileges.

Determine the physical memory to avoid setting certain kernel parameters above the physical capacity:

Start the HP-UX System Administration Manager (SAM) utility.

Click Performance Monitors > System Properties > Memory.

Note the value for Physical Memory and click OK.

Exit from the SAM utility.

Set the maxfiles and maxfiles_lim parameters to at least 4096. (The following table recommends 8000 and 8196, respectively. You must first edit the /usr/conf/master.d/core-hpux file, to allow the SAM utility to set values greater than 2048:

Open the file /usr/conf/master.d/core-hpux in a text editor.

Change the line, *range maxfiles<=2048 to *range maxfiles<=60000

Change the line, *range maxfiles_lim<=2048 to *range maxfiles_lim<=60000

Save and close the file. Old values might be stored in the /var/sam/boot.config file. Force the SAM utility to create a new boot.config file:

Move the existing version of the /var/sam/boot.config file to another location, such as the /tmp directory.

Start the SAM utility.

Click Kernel Configuration > Configurable Parameters. When the Kernel Configuration window opens, a new boot.config file exists.
Alternatively, rebuild the boot.config file with the following command:

# /usr/sam/lbin/getkinfo -b

Set new kernel parameter values:

Start the SAM utility.

Click Kernel Configuration > Configurable Parameters.

For each of the parameters in the following table, perform this procedure:

Highlight the parameter to change.

Click Actions > Modify Configurable Parameter.

Type the new value in the Formula/Value field.

Click OK.

Some kernel values for WAS with the embedded messaging feature are higher than those shown in the following table. See the Install WebSphere embedded messaging as the JMS provider topic for more information.

Some kernel values for WAS IBM DB2 on the same machine, are higher than those shown in the following table.

Recommended HP-UX kernel configuration parameters for DB2 V8

Recommended HP-UX kernel configuration parameters for DB2 V7

Typical kernel settings for running WAS appear in the following table:

Parameter Value
dbc_max_pct 25
maxdsiz 805306358
maxdsiz 2048000000 (when the base and Network Deployment products are on one machine)
maxfiles_lim 8196 (Change this setting before changing the maxfiles setting.)
maxfiles 8000
maxssiz 8388608
maxswapchunks 8192
max_thread_proc 3000
maxuprc 512
maxusers 512
msgmap 2048
msgmax 65535
msgmax 131070 (when the base and Network Deployment products are on one machine)
msgmnb 65535
msgmnb 131070 (when the base and Network Deployment products are on one machine)
msgmni 50
msgseg 32767
msgssz 32
msgtql 2046
nfile 58145
nflocks 3000
ninode 60000
nkthread 7219
nproc 4116
npty 2024
nstrpty 1024
nstrtel 60
sema 1 (with embedded messaging)
semaem 16384 (with embedded messaging)
semmap 514
semmni 2048
semmns 16384 (with embedded messaging)
semmnu 1024
semume 200
semvmx 32767 (with embedded messaging)
shmmax 2147483647
shmem 1 (with embedded messaging)
shmmni 1024
shmseg 1024
STRMSGSZ 65535

click Actions > Process New Kernel.

Click Yes on the information window to confirm your decision to restart the machine.
Follow on-screen instructions to restart your machine and to enable the new settings.

If you plan to redirect displays to non-HP machines, do the following steps before running the WAS Installation wizard:

Issue the following command to obtain information on all of the public locales accessible to your application:

# locale -a

Choose a value for your system from the output that is displayed and set the LANG environment variable to this value. Here is an example command that sets the value of LANG to en_US.iso88591

# export LANG=en_US.iso8859

Migrating or coexisting with an existing WebSphere Application Server node that HP-UX does not recognize.
In some cases, the InstallShield for MultiPlatforms (ISMP) program does not detect a previously installed version of WAS because of a failure to read the registry keys on HP-UX.

You can force the Migration panel or the Coexistence panel to display, by starting the installation with an option on the Install.exe or install command. For example, use this command:

./install -W previousVersionDetectedBean.previousVersionDetected="true"

You can also force the display of the Coexistence panel to change conflicting port number assignments. For example, force the Coexistence panel to display using this command:

./install -W coexistenceOptionsBean.showCoexistence="true"

On either panel, identify the location of the existing product instance that is not being recognized.

Avoiding using Netscape 4.79 on HP-UX 11 in Japanese, to avoid problems in viewing the administrative console.
It is possible that you cannot view the menu or areas of the console that scroll. Only certain portions of the administrative console are visible. You cannot scale the administrative console.

The workaround for the problem is to use another supported browser or another browser and operating system platform. You can also open the menu frame in a separate window, to avoid the problem.

Configuring the converter.properties file to use EUC-JP (Japanese) encoding on HP-UX.
The install_root/java/jre/lib/i18n.jar file on HP-UX platforms does not have the coverters for Cp33722C, but does have the converter for Cp33722. To use EUC-JP encoding on HP-UX platforms, change the EUC-JP=Cp33722C entry in the converter.properties file to EUC-JP=Cp33722 or EUC-JP=EUC_JP.

Using certificate revocation lists (CRLs) with IBM HTTP Server on HP-UX and Linux for S/390 platforms is not supported at this time.
Certificate revocation lists are not supported for IBM HTTP Server on HP-UX and Linux for S/390 platforms.

Ignoring certain error messages when installing WebSphere Application Server with embedded messaging from the CD-ROM.
The following warning messages are issued despite successful installation. You might see the following messages in the mq_install.log file when installing WAS with embedded messaging from the CD-ROM:

MQSERIES.MQM-CL-HPUX: A test command parameter is not valid." and "* "hostname:/cdrom/hpux/messaging/images": Cannot open the logfile on this target or source. Possibly the media is read-only or there is a permission problem."
You can ignore the warning messages. The problem does not affect the successful installation of WebSphere Application Server with embedded messaging.

Linux platforms

Summary of tips that apply to Linux platforms

Provide adequate disk space for installation
Provide prerequisites for Red Hat Enterprise Linux V3.0
Upgrading Red Hat Enterprise Linux V3.0 to service level 1 (update 1)
Preparing Linux for S/390 for better performance
Changing the locale encoding to English to install WAS on SuSE SLES 8.0 for PowerPC platforms
Japanese not recommended on Red Hat Enterprise Linux (RHEL) Advanced Server V2.1
Ignoring YAST2 dependency conflicts for embedded messaging packages
Preparing the SuSE Linux Enterprise Server 8.0 - Powered by UnitedLinux 1.0 platform for WAS installation
Configuring Apache 1.3 to run on SuSE Linux Enterprise Server 8.0
Correct font problems on SuSE Linux Enterprise Server 8.0 in Simplified Chinese and Traditional Chinese locales
Avoiding the certificate revocation list (CRL) function, which is not supported for IBM HTTP Server on Linux for S/390
Using the ikeycmd command line interface for ikeyman from IBM HTTP Server on Linux for S/390
Avoiding utility hangs and accessing the deployment manager
Using the GNOME desktop on Red Hat Linux Advanced Server V2.1 in the Korean locale
Upgrading Red Hat Enterprise Linux V3.0 to service level 1 (update 1)
Changing the Chinese locale on a Red Hat Enterprise Linux 3.0 platform from zh_CN.gb18030 to zh_CN.gbk
Accessing First Steps items on Linux for S/390 systems
Using certificate revocation lists (CRLs) with IBM HTTP Server HP-UX and Linux for S/390 platforms is not supported at this time
Editing the keyman script to bring up IKEYMAN for IBM HTTP Server 1.3.28 shipped with WAS
Ignoring messages from the prerequisites checker when your operating system is at the level specified by the WAS supported hardware, software, and APIs Web site
Using the LinuxThreads threading mode instead of the Native POSIX Threading Library (NPTL)
Avoiding an error that occurs when starting the Launchpad program for WAS clients, V5.1 using the Konqueror file in the K Desktop Environment on SuSE Linux Enterprise Server (SLES)
Avoiding a segmentation fault on RHEL V3.0 Update 1

Tips that apply to Linux platforms

Provide adequate disk space on Linux platforms.

Installed sizes of installation directories for Linux platforms

Base product Network Deployment IBM HTTP Server Embedded massaging Tivoli Global Security Kit Temp space
Installation directory /opt/ WebSphere/ AppServer /opt/ WebSphere/ Deployment Manager /opt/ IBM Http Sever /opt/ wemps and /opt/ mqm /opt/ ibm/ gsk7 /tmp
Minimum free space for Linux for xSeries installation 470 MB 390 MB 20.4 MB on base 6 MB; 60 MB on base 11.8 MB At least 150 MB
Minimum free space for Linux for S/390 installation 470 MB 390 MB 20.4 MB on base 6 MB; 60 MB on base 13.2 MB At least 150 MB

Space requirements for the embedded messaging feature are described in Install WebSphere embedded messaging as the JMS provider.

Provide prerequisites for Red Hat Enterprise Linux V3.0
A known limitation in the prerequisites checker program prevents correctly examining prerequisite packages on Linux platforms. If you plan to install WAS V5.1.x products on a Red Hat Enterprise Linux 3.0 system, install the following prerequisite packages on the RHEL 3.0 system.

You must install the following packages on Red Hat Enterprise Linux V3.0 for xSeries platforms:

compat-gcc-7.3-2.96.122
compat-libstdc++-7.3-2.96.122
compat-libstdc++-devel-7.3-2.96.122
compat-glibc-7.x-2.2.4.32.5
compat-gcc-c++-7.3-2.96.122
compat-db-4.0.14-5
rpm-build-4.2.1-4.2

The following package is required for Red Hat Enterprise Linux V3.0 for pSeries platforms: rpm-build-4.2.1-4.2.

You must install the following packages on Red Hat Enterprise Linux V3.0 for S/390 (z/OS and S/390 in 31-bit mode) platforms:

compat-db-4.0.14-5
compat-pwdb-0.62-3
compat-libstdc++-7.2-2.95.3.77
rpm-build-4.2.1-4.2

You can install a later release of any of these packages.

Upgrading Red Hat Enterprise Linux V3.0 to service level 1 (update 1).
Upgrade RHEL 3.0 to service level 1 by downloading and installing the service updates from Red Hat.

If you do not upgrade to service level 1, certain national language issues in the released version of GLIBC included in Red Hat Enterprise Linux V3 might cause Java virtual machine (JVM) failures due to segmentation faults. These failures can occur during installation when the locale is set to anything other than an English locale.

The prerequisites checker program for the base V5.1.0.0 product does not recognize Red Hat Enterprise Linux 3.0 as a supported operating system. If you receive a message from the prerequisites checker program that RHEL 3.0 is an unsupported operating system, ignore the message and continue the installation if you installed all prerequisite packages from the previous step and downloaded and installed the service level 1 update.

Preparing Linux for S/390 for better performance
Linux for S/390 (which refers to the Linux distributions available from Linux distributors that run on IBM eServer zSeries and S/390 systems in 31-bit mode) provides a configuration technique that affects the installation and run time performance of WAS. The technique configures the environment where the Linux image runs to use swap space efficiently. Some performance guidelines recommend running Linux with the VM/ESA or z/VM swap turned off because of VM/ESA or z/VM virtualization of hardware. Virtualization can produce double-swapping situations where VM/ESA or z/VM swaps storage and Linux also swaps storage, which degrades performance.

Excessive swapping affects the performance of WAS, which might require 200 MB when all of the Sample applications are loaded. On a system without swap space configured for use, and with a relatively small amount of memory (such as 256 MB), WAS might encounter problems obtaining enough free memory to work properly, particularly when competing for resources against other applications and products that run in the Linux environment.

The solution is to disable swapping in Linux, but to enable swapping in VM/ESA or z/VM. You can increase performance by letting VM/ESA or z/VM handle the swapping. Double or triple the specification for physical memory for the Linux image. For example, if the physical memory allocation as seen by the Linux image is 256 MB, disable swap in Linux, enable swap in VM/ESA or z/VM, and increase the physical memory specification as seen by Linux to 512 MB or 768 MB. This amount of memory handles any large spikes in application memory usage that might occur.

You can fine tune the amount of physical memory to allocate to each Linux guest operating system. Size the JVM heap size for the application running in the Application Server, add 90 MB to that amount for the Application Server, 20 MB for Linux, and another 10-20% to handle peak usage. This measurement provides better memory management from a VM/ESA or z/VM perspective.

Avoid socket timeout exceptions (SocketTimeoutExceptions) when running WebSphere Business Integration Server Foundation on a Network Deployment node on a Linux for S/390 guest operating system on z/VM or VM/ESA. The exceptions are an indicator that too many processes are running and that the Linux system is being overloaded. If the deployment manager is under a heavy load, 1 GB of memory is required. In addition, move all base nodes to other Linux for S/390 guests to allow the deployment manager to run by itself on the Linux for S/390 system.

See the Linux on IBM eserver zSeries and S/390: ISP/ASP Solutions IBM Redbook and the Performance Analysis for Java Web sites book for more information.

Note: SLES 9 runs in 64-bit zSeries environments only.

Changing the locale encoding to English to install WebSphere Application Server on SuSE 8.0 SLES for PowerPC platforms.
The WebSphere Application Server installation program is corrupted when you start the installation on SuSE Linux Enterprise Server (SLES) 8.0 for a PowerPC platform in a double-byte character set (DBCS) language. The double-byte character set languages display the characters incorrectly. The single-byte character set (SBCS) languages display the characters correctly.

The reason for this problem is either missing fonts on the system, incorrectly called fonts, or incorrectly displayed fonts.

Change the locale encoding to English to properly install WebSphere Application Server on SuSE SLES 8.0 for PowerPC platforms. To change the locale, open a terminal or window and complete the following steps:

Type export LC_ALL=C and press Enter.

Type export LANG=C and press Enter.

To verify that the locale is properly set to English, type locale to see that all variables are set to C.

Japanese not recommended on Red Hat Enterprise Linux (RHEL) Advanced Server V2.1.
The Red Hat Advanced Server V2.1 GUI language selection menu displays two selections for Japanese:

Japanese (eucJP)

Japanese (SJIS)

Click Japanese (eucJP) to install and run the IBM WebSphere Application Server in a Japanese environment. Do not use Japanese (SJIS).

See the Red Hat Japanese Web site at http://www.jp.redhat.com/support/7.2/sla/rh72faq.html for more information.

Ignoring YAST2 dependency conflicts for embedded messaging packages
The YAST2 utility on SuSE Linux Enterprise Server 8.0 has a known problem reporting dependency conflicts. If you use the utility, you can ignore the Dependency conflict panel that reports conflicting packages for the embedded messaging feature. Two examples from such a report might appear like this:

MQSeriesClient MQSeriesClient-U486878 MQSeriesJava MQSeriesJava-U486878

Many packages, such as the embedded messaging packages in the WAS products, specify a conflict to control incompatible package levels. In this case, the conflict identifies a WebSphere MQ-related package level that is less than 5.3.0. YAST2 seems to be misinterpreting the specification and flagging a conflict for WebSphere MQ packages that are less than or equal to 5.3.0.

Preparing the SuSE Linux Enterprise Server 8.0 - Powered by UnitedLinux 1.0 operating platform for WAS installation.

Install SP2 for the UnitedLinux 1.0 operating platform to let you use the WAS LaunchPad.
It is your responsibility to install this service pack. No definitive way is available for the prereqChecker function of the installer to detect service pack versions on UnitedLinux. Kernel uname/versions between 8.0 and 8.0.2 are identical. signature RPM exists for denoting a service pack installation.

Use the IBM Developer Kit that WAS provides to support the Java 2 SDK on the SuSE SLES 8.0 operating system to avoid potential problems when uninstalling an interim fix or a fix pack. To use the IBM Developer Kit, remove the java2-jre-1.3.1-524 and java2-1.3.1-524 RPMs from the machine before installing WAS.

Configuring Apache 1.3 to run on SuSE Linux Enterprise Server 8.0.
Using the following directive in an otherwise unmodified httpd.conf file can result in an error:

LoadModule app_server_http_module /opt/WebSphere/AppServer/bin/mod_app_server_http.so

The error is indicated by a message similar to the following example:

[warn] Loaded DSO /opt/WebSphere/AppServer/bin/mod_app_server_http.so uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI) [notice] Apache/1.3.26 (Linux/SuSE) mod_python/2.7.8 Python/2.2.1 PHP/4.2.2 mod_perl/1.27 configured -- resuming normal operations [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [notice] Accept mutex: sysvsem (Default: sysvsem) [notice] child pid 3383 exit signal Segmentation fault (11)

Edit the /etc/sysconfig/apache file and change the value of the following parameters from yes to no to remove PHP and Python from the Web server:

HTTPD_SEC_MOD_PYTHON

HTTPD_SEC_MOD_PHP

Run the SuSEconfig utility to enable your changes.

Do not attempt to use the EAPI module with the version of Apache 1.3 that ships with SuSE Linux Enterprise Server 8.0. An error in this version of Apache prevents using the EAPI module. Obtain an updated version of Apache 1.3 from SuSE, or download an updated version of Apache 1.3 from another source to use the EAPI plug-in module.

Edit the /etc/sysconfig/apache file if you download a new version, remove PHP and Python from the Web server, and run the SuSEconfig utility.

Correct font problems on SuSE Linux Enterprise Server 8.0 in Simplified Chinese and Traditional Chinese locales.
On the Linux for Power platform that SuSE Linux Enterprise Server 8.0 provides, there is a font problem caused by a missing package. There is no ttf-hanyi package installed during the normal product installation of the SuSE 8.0 operating system. This causes the Installation wizard for WAS products to display garbled characters on the Simplified Chinese locale and the Traditional Chinese locale.

Copy the ttf-hanyi-2021016-0.noarch.rpm package on the SuSE 8.0 for i386 CD-ROM to the Power PC system. Install the package on the Power PC machine and reboot the machine to solve the problem.

Avoiding the certificate revocation list (CRL) function, which is not supported for IBM HTTP Server on Linux for S/390.
Do not use the certificate revocation list (CRL) function on Linux for S/390 at this time.

Using the ikeycmd command line interface for ikeyman from IBM HTTP Server on Linux for S/390.
You might see a Java core dump after running an ikeyman command function, such as creating the stash file. This error occurs on both RedHat and SuSE releases as the result of a conflict in library routines caused by the default loading sequence.

To work around this problem, set the LD_PRELOAD environment variable before running the following command:

LD_PRELOAD=/usr/lib/libstdc++-libc6.1-2.so.3
This command loads the library first when the application is started. Setting this environment variable is also necessary to support Secure Sockets Layer (SSL) on Linux for S/390.

Migrating from WAS, V3.5 on Linux platforms.
The error can occur when the migration tools cannot find the JAVA_HOME. The WASPreUpgrade command reports the error while backing up the WAS V3.5 environment. The error appears in the WASPreUpgrade log as:

MIGR0257E:Environment variable JAVA_HOME was not set is generated

To work around the problem:

Create a directory link to one of the following directories:

$WAS_HOME/IBMJavaLink

/opt/IBMJava2-122

$WAS_HOME/IBMJava2-122

WAS_HOME is the WAS 3.5 WAS_HOME.

Run the WASPreUpgrade command again, followed by the WASPostUpgrade command, to migrate the environment correctly to WAS, Version 5.

Avoiding utility hangs and accessing the deployment manager.
The default Red Hat installation creates an association between the host name of the machine and the loopback address, 127.0.0.1. In addition, the /etc/nsswitch.conf file is set up to use the /etc/hosts file before trying to look up the server using a name server (DNS). This loopback processing can hang utilities that start and stop a server, such as the startServer command, the stopManager command, and others, even though the server might successfully start or stop.

The stop can also cause failures when adding nodes on a Linux deployment manager. If you have trouble synchronizing new nodes with the Linux deployment manager during addNode processing, ensure that the host name is defined properly. The default configuration has local host defined in the /etc/hosts file. The default /etc/nsswitch.conf looks only at the host file and not the DNS server.

To correct this problem, remove the 127.0.0.1 mapping to localhost in the /etc/hosts file or edit the name service configuration (/etc/nsswitch.conf) file to resolve the proper host name by using the name server.

For example, remove the 127.0.0.1 mapping from the /etc/hosts file, which might look like the following example:

# IP Address name of machine n.n.n.n hostname.domain.com hostname 127.0.0.1 localhost

Otherwise, change the etc/nsswitch.conf file to search DNS before searching the hosts file.

For example, hosts : dns files

Using the GNOME desktop on Red Hat Linux Advanced Server V2.1 for i386 Update3 in the Korean locale.
You cannot start the deployment manager on a Network Deployment system when Korean characters are in the cell name. This is true in the Korean locale when running the KDE desktop on a Red Hat Linux Advanced Server V2.1 for i386 Update3 system.

This problem is caused by the default system desktop being set to "KDE", which means that file /etc/sysconfig/desktop has the value desktop="KDE".

Run the following command on your RedHat 2.1 system to change the default system desktop to GNOME:

#echo "DESKTOP=\"GNOME\"" >/etc/sysconfig/desktop
Restart your system to solve the problem.

Upgrading Red Hat Enterprise Linux V3.0 to service level 1 (update 1).
Upgrade RHEL 3.0 to service level 1 by downloading and installing the service updates from Red Hat.

If you do not upgrade to service level 1, certain national language issues in the released version of GLIBC included in Red Hat Enterprise Linux V3 might cause Java virtual machine (JVM) failures due to segmentation faults. These failures can occur during installation when the locale is set to anything other than an English locale.

Changing the Chinese locale on a Red Hat Enterprise Linux 3.0 platform from zh_CN.gb18030 to zh_CN.gbk.
A known problem with RHEL V3 before installing service level 1 (update 1) is that one of the Chinese locales and its codepage, zh_CN.gb18030, causes the Installation wizard to render several input fields uneditable. Change the locale and its codepage to zh_CN.gbk to allow the Installation wizard to work correctly.

Accessing First Steps items on Linux for S/390 systems.
When you select the following features from the First Steps panel, the Web browser window does not open:

WebSphere information center

Register the Product

Samples Gallery

Administrative Console

To access these features:

Open a Web browser window on another machine.

Type the browser Web address that displays in the First Steps status window into the address field of the Web browser.

Press Enter to open the page in the Web browser.

Editing the keyman script to bring up IKEYMAN for IBM HTTP Server 1.3.28 shipped with WAS
Editing the ikeyman script to bring up IKEYMAN for the IBM HTTP Server 1.3.28 shipped with WAS

You cannot bring up IKEYMAN by typing the ikeyman script under the IHS_HOME/bin directory for IBM HTTP Server 1.3.28 shipped with WAS, Version 5.1 on the Linux PowerPC 64 bit platform. The following error is thrown:

Line 139: /usr/local/ibm/gsk7_gcc295/bin/gsk7ibm_gcc295: No such file or directory

To work around this problem, perform the following steps:

Use WAS IKEYMAN to create the CMS keystore. You can invoke the WAS IKEYMAN from the WAS_HOME/bin directory.

Edit the IBM HTTP Server ikeyman script: remove 2 references of "gcc295" from next to the last line.

Ignoring messages from the prerequisites checker when your operating system is at the level specified by the WebSphere Application Server supported hardware, software, and APIs Web site.
The installation prerequisites checker checks for prerequisites that might have changed since the release of the product CD.

The prerequisites checker for the installation program is fixed at the time the product CDs are created. It is possible that more operating system patches are required since the time the product CDs were created. It is also possible that new versions of operating systems are supported even though the prerequisites checker identifies the new operating system level as unsupported.

Always consult the IBM WAS supported hardware, software, and APIs Web site to determine whether your operating system is supported when you receive a message from the prerequisites checker program during installation.

The Web site lists all supported operating systems and the operating system fixes and patches that install to have a compliant operating system. After confirming that your operating system is supported and that you have installed all the necessary patches, you can click Next to continue an installation when you receive an error message from the prereqChecker program.

Using the LinuxThreads threading mode instead of the Native POSIX Threading Library (NPTL).
WAS, V5.1.0 products run under the LinuxThreads threading mode because of program dependencies on specific behavior within the LinuxThreads mode. The WAS 5.1.0 run time automatically sets up LinuxThreads mode for you. Do try to force the NPTL mode because errors are thrown by the run time when the WebSphere embedded messaging broker and queue servers are started.

If you set LD_ASSUME_KERNEL=2.4.19 or LD_ASSUME_KERNEL=2.2.5 to switch to LinuxThreads outside the context of WAS, it is recommended that you also set the RPM_FORCE_NPTL=1 environment variable.

Unusual behavior occurs with Red Hat Package Manager (RPM) when running under LinuxThreads on Red Hat Enterprise Linux, V3.0. Corruption of the RPM database can occur. Setting the environment variable forces the RPM program to always run under NPTL threading and protects the RPM database from corruption.

Set the value in the environment using the following command:

export RPM_FORCE_NPTL=1

Avoiding an error that occurs when starting the Launchpad program for WAS clients, V5.1 using the Konqueror file in the K Desktop Environment on SuSE Linux Enterprise Server (SLES).
When starting the Launchpad program for WAS clients, Version 5.1 using the Konqueror file manager in the K Desktop Environment (KDE) on Linux systems, a "Couldn't find the program launchpad.sh" error occurs.

Because the launchpad.sh command uses a relative path to locate the Java program, run the launchpad.sh command from the directory where the launchpad.sh command is located for the client program. When using the Konqueror file manager to issue the launchpad.sh command, the current directory is your home directory. Therefore, the launchpad.sh command cannot work.

Do not use the Konqueror file manger to issue the launchpad.sh command for the client. Open a Konsole session in the KDE, change the current directory to where the launchpad.sh command is located, and run the launchpad.sh command.

Avoiding a segmentation fault on RHEL V3.0 Update 1.
An "A suitable JVM could not be found" message is displayed when installing WebSphere Business Integration Server Foundation on Red Hat Enterprise Linux 3 U1.

When installing from an operator console attached to the server (not telnet), the "A suitable JVM could not be found" message displays and the installation fails with a segmentation fault.

You might have previously installed, logged off, logged back on, and are running the installation again on the operator console attached to the server.

This is a known limitation of Red Hat Enterprise Linux V3.0 that causes a segmentation fault when calling the JVM.

Test if the JVM is failing by running the following command:

/mnt/cdrom/platform/linuxi386/jdk/java/jre/bin/java -version

If you receive a "Segmentation Fault" message, reboot your machine or press Ctrl-X to reinstall. Rebooting the machine resolves the problem.

Solaris Operating Environment

Summary of tips that apply to Solaris platforms

Provide adequate space for Solaris platforms

Uninstalling a V5.1 instance on a Solaris platform before reinstalling the instance

Using the unzip function, not the jar command, to decompress downloaded files

Closing the terminal window that remains open after the installation finishes

Configuring the converter.properties file to use EUC-JP (Japanese) encoding

Configuring the Domino Server plug-in

Avoiding problems starting appservers in zh_TW.EUC locale on Solaris

Using the correct mount point for the product CD

Provide adequate disk space for Solaris platforms.

Installed sizes of installation directories for Solaris platforms

Base product Network Deployment IBM HTTP Server Embedded messaging Tivoli Global Security Kit Temp space
Installation directory /opt/ WebSphere/ AppServer /opt/ WebSphere/ Deployment Manager /opt/ IBM Http Server /var/ mqm and /opt/ mqm /opt/ ibm/ gsk7 /tmp
Minimum free space for installation 530 MB 460 MB 20 MB 4 MB; 40 MB on base 23.1 MB (GSKit 7); 23.1 MB (GSKit 5) At least 150 MB

Space requirements for the embedded messaging feature are described in Install WebSphere embedded messaging as the JMS provider.

Uninstalling a V5.1 instance on a Solaris platform before reinstalling the instance.
If you uninstall a V5.1 instance but leave the embedded messaging feature because of other WAS instances, clean up the /var/sadm/pkg directory before reinstalling V5.1.

If you uninstall all of the WAS products on the machine and are now reinstalling, follow the procedure in Manually uninstalling on Solaris platforms instead of this procedure.

You must perform this procedure before you can reinstall the product into the same installation root directory on Solaris platforms. Otherwise, reinstall the product into another directory and you might have a problem reinstalling the embedded messaging feature.

Assume that V5.0.x exists in /opt/WebSphere/AppServer50 with the embedded messaging server and client feature. You then install V5.1 to the following directory, /opt/WebSphere/AppServer51, but later you uninstall the product and leave the embedded messaging feature installed. And now you decide to reinstall V5.1.

Make the /var/backupForWAS51Reinstall backup directory.

Change directories to /var/sadm/pkg, and type ls -lt | grep WSBAA51 to find packages that contain the base WAS.
The directory for Network Deployment is WSNAA51.

If the WSBAA51 directory exists, change directories to the WSBAA51 directory and read the pkginfo file in the /var/sadm/pkg/WSBAA51 directory.
Find the installation location for V5.1. If the location is the same installation location as the V5.1 product that you uninstalled, move the /var/sadm/pkg/WSBAA51 folder to the /var/backupForWAS51Reinstall directory.

The following example shows how to display the pkginfo file:

# pwd /var/sadm/pkg/WSBAA51 # ls -lt total 6 -rw-r--r-- 1 root other 591 Oct 27 15:46 pkginfo drwxr-xr-x 2 root other 512 Oct 27 15:46 install drwxr-xr-x 2 root other 512 Oct 27 15:46 save # cat pkginfo # VPD created by InstallShield MultiPlatform Edition # Mon Oct 27 15:46:34 EST 2003 ARCH=sparc BASEDIR=/opt/WebSphere/AppServer51 CATEGORY=application CLASSES=none DESC= ISJE_INSTALL_STATUS=3 ISJE_IS_ACTIVE=true ISJE_IS_PUBLICLY_SHAREABLE=false ISJE_NAME=IBM WAS ISJE_PARENTS=WSBAA51:5.1.0.0.DSP=:1 ISJE_PRODUCT_NUMBER=5.1.0.0 ISJE_REQUIRED_COUNT=0 ISJE_SOURCES= ISJE_UID=WSBAA51 ISJE_UNINSTALLER="_uninst" "uninstall.jar" "uninstall.dat" "" ISJE_VPD_VERSION=4.5 ISJE_WEB= NAME=WAS PKG=WSBAA51 PKGINST=WSBAA51 VENDOR= VERSION=5.1.0.0.DSP=

When two instances of V5.1 WAS exist, such as with one instance installed and one instance uninstalled, for example, two files exist in the /var/sadm/pkg directory. One is the /var/sadm/pkg/WSBAA51 file, the other is the /var/sadm/pkg/WSBAA51.2 file. For example:

# ls -lt | grep WSBAA drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBAA51.2 drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBAA51 drwxr-xr-x 3 root other 512 Oct 21 13:32 WSBAA

Verify that you are moving the correct file to the backup directory.
Examine the pkginfo files. Do not touch entries for other WAS products that might be present on the platform, such as WS entries for existing WAS V5.0.x.

Run the ls -lt | grep WSBM command to get all of the embedded messaging packages.
For example:

# # ls -lt | grep WSBM drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBMQ1AA.2 drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBMQ2AA.2 drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBMS4AA.2 drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBMS6AA.2 drwxr-xr-x 4 root other 512 Oct 27 18:52 WSBMQAA.2 drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMS4AA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMS6AA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMQ1AA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMQ2AA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMQ3AA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMQAA drwxr-xr-x 4 root other 512 Oct 27 15:46 WSBMSAA

Identify entries that are related to the V5.1 product that you uninstalled.
Examine the pkginfo file for each entry. In the previous example, ".2" entries relate to the product that you uninstalled, which was originally in the /opt/WebSphere/AppServer51 directory. Use a command to move all of the ".2" entries into the backup directory. For example, run the following command from the /var/sadm/pkg/ directory:

mv WSBM*.2 /var/backupForWAS51Reinstall
For V5.1 of Network Deployment, all of the related embedded messaging entries start with WSNM. Run the following command to show the Network Deployment entries:

ls -lt | grep WSNM

Rename /opt/WebSphere/AppServer51 to /opt/WebSphere/AppServer51_bk before reinstalling V5.1.

Using the unzip function, not the jar command, to uncompress downloaded files.
To uncompress downloaded installation files for the Solaris operating system, use the unzip function and not the jar command. Using the jar function sets file permissions incorrectly, which causes the installation to fail.

Closing the terminal window that remains open after the installation finishes.
When installing WAS from the product CD onto a Solaris system, the ISMP Installation wizard launches a terminal window, which remains open after the installation is complete. This window contains the following text:

InstallShield Wizard Initializing InstallShield Wizard... Searching for Java(tm) Virtual Machine... .....
Close the window after the installation completes.

Configuring the converter.properties file to use EUC-JP (Japanese) encoding.
The install_root/java/jre/lib/i18n.jar file on Solaris platforms does not have the coverters for Cp33722C, but does have the converter for Cp33722. To use EUC-JP encoding on Solaris platforms, change the EUC-JP=Cp33722C entry in the converter.properties file to EUC-JP=Cp33722 or EUC-JP=EUC_JP.

Configuring the Domino Server plug-in.
During installation, a dsapi_stderr.txt file is created in the logs directory and you can get the following error messages:

lotus.notes.NotesException: Could not load dll for system name SUNOS at lotus.notes.NotesThread.load(NotesThread.java:210) at lotus.notes.NotesThread.<clinit>(NotesThread.java:24) java.lang.UnsatisfiedLinkError: NnotesInitThread at lotus.notes.NotesThread.NnotesInitThread(Native Method) at lotus.notes.NotesThread.initThread(NotesThread.java:99) at lotus.notes.NotesThread.run(NotesThread.java:133)

You can configure the IBM WAS or Domino Server plug-in manually using the Domino Server Web administration tool. The workarounds include:

Start the Domino Server.

Enter the Web address for the Domino Server Web Administration site using a browser. For example, http://hostname/names.nsf. Enter the administrator user name and password.

Double-click Server-Servers.

Double-click WebServer to configure.

Double-click Edit Server.

Double-click Internet Protocol.

Add the IBM WAS DSAPI plug-in to the DSAPI field. For example, /opt/WebSphere/AppServer/bin/libdomino5_http.so
If DSAPI filter files are already specified, use a space to delimit the WebSphere Application Server plug-in file.

Double-click Save and Close.

Restart the Domino Server.

Avoiding problems starting appservers in the zh_TW.EUC locale on Solaris platforms.
If you use the embedded JMS provider in WAS products or WebSphere MQ as the JMS provider on Solaris, do not set the LANG and LC_ALL variables to zh_TW.EUC (Traditional Chinese locale) to avoid problems when starting appservers. Set the LANG and LC_ALL variables to zh_TW instead of zh_TW.EUC.

Using the correct mount point for the product CD.
If the Solaris Volume Manager (vold) is running, Solaris automatically mounts the product CD as the /cdrom/was_wbisf_sun_cd1 device.

Do not run the launchpad.sh command or the install command from the automatically generated mount point. For example, do not run the /cdrom/was_wbisf_sun_cd1/sun/install command.

Close the File explorer window that Solaris automatically opens so that you can define a correct mount point.

Open a shell window and use the window throughout the installation.

Verify that you are in a read/write directory and not the CD-ROM directory or another read-only directory before you start the installation.

Start the installation using the mount point specification in the following command:

# /cdrom/cdrom0/sun/launchpad.sh

Windows platforms

Summary of tips that apply to Windows platforms

Provide adequate space for installation

Provide the required msvcp60.dll file for Windows 2000 Server

Planning for the default installation path

Viewing accurate migration messages

Decompressing a WAS eImage that you download

Editing or removing the vpd.properties file

Preparing for Adaptive Fast Path Architecture (AFPA) driver availability when migrating from IBM HTTP Server V1.3.19.x, or earlier

Rebooting the machine after uninstalling the embedded messaging feature

Ignoring an incorrect ImagePath entry in the registry after changing the document root

Avoiding a user ID with spaces when installing the WAS as a Windows service

Changing the display settings from high-contrast black to high-contrast white to view panels with hypertext links

Avoiding using the default service names created by the installer because they are common

Uninstalling WebSphere Embedded Messaging Publish and Subscribe Edition on Windows 2003 Server

Lowering the Internet Explorer security level from High to Medium to view the Product overviews from the Launchpad on Windows 2003 machines

Expecting a delay before the Installation wizard displays its first panel

Tips that apply to Windows platforms

Provide adequate disk space for installation.

Installed sizes of installation directories for Windows platforms

Base product Network Deployment product IBM HTTP Server Embedded messaging Tivoli Global Security Kit Temp space
Installation directory C:\Program Files\ WebSphere\ AppServer C:\Program Files\ WebSphere\ Deployment Manager C:\Program Files\IBM Http Server C:\Program Files\ IBM\ WebSphere MQ C:\Program Files\ IBM\ gsK7 C:\temp
Minimum space for installation 422 MB 360 MB 20 MB 4 MB; 40 MB on base 16.8 MB At least 150 MB

Space requirements for the embedded messaging feature are described in the Install WebSphere embedded messaging as the JMS provider topic.

Provide the required msvcp60.dll file for Windows 2000 Server platforms.
The embedded messaging feature requires a DLL file on Windows 2000 Server platforms. The DLL file is already installed on Windows 2000 Advanced Server and other Windows platforms that are supported. If you see a message similar to the following example, download the msvcp60.dll file:

wempsdeletebroker.exe - Unable To Locate DLL The dynamic link library MSVCP60.dll could not be found in the specified path...

The prereq checker in the installer program does not check for this DLL file on the Windows 2000 Server platform. If you select the Windows 2000 Support Tools during Windows 2000 Server installation, the installation program for Windows 2000 Server installs the DLL file in the C:\Program Files\Support Tools directory. The DLL file is installed during the installation of Windows 2000 Advanced Server in the C:\WINNT\system32 directory.

You can download the DLL file from the Microsoft Web site.

Planning for the default installation path
On Windows platforms, the default installation path is drive:\Program Files\IBM\WebSphere MQ\. You can specify a different directory during installation. On Linux and UNIX platforms, the path is fixed.

Viewing accurate migration messages.
When migration is running during installation, the information displayed in the pre-migration and post-migration processing might display corrupted national characters. Use the PreUpgrade and PostUpgrade logs in the backup/logs directory, where backup is the backup directory specified during installation.

Decompressing a WAS eImage that you download.
If you are using the downloadable archive file to install the WAS product, the PKWARE pkunzip utility might not decompress the download image correctly. Use another utility (such as WinZip) to unzip the image.

Editing or removing the vpd.properties file.
Install WAS on some international computers might result in an installation failure or in font problems. Use the following procedure to work around this problem:

Locate the vpd.properties file in the operating system installation directory.
For example, C:\WINDOWS or C:\WINNT on a Windows system.

Remove all of the lines containing one of these strings:

WSE
WSN
WSB
WSM

Do not delete or rename the vpd.properties file because the InstallShield for MultiPlatforms (ISMP) program uses it for other products that it installs. If you are sure that no other entries exist in the file, you can delete the file.

Preparing for Adaptive Fast Path Architecture (AFPA) driver availability when migrating from IBM HTTP Server V1.3.19.x, or earlier.
The AFPA driver controls the fast response cache accelerator function, which is also known as the cache accelerator. The version of IBM HTTP Server installed with WAS shares the AFPA driver with any coexisting IBM HTTP Server. Uninstalling a coexisting V1.3.19.x (or earlier) IBM HTTP Server also uninstalls the common AFPA driver.

When configured to use an AFPA driver that is no longer present, the cache accelerator does not provide a response improvement. IBM HTTP Server generates errors as it starts. For example:

[error] (9) Bad file descriptor: Afpa Device Driver open failed.

You can either restore the driver or disable the cache accelerator configuration. Restore the driver by reinstalling the later version of IBM HTTP Server after you uninstall the earlier version. To verify that the AFPA driver is installed and working, see if it is listed in device manager under Non-Plug and Play Drivers. Select the Show hidden devices option in the device manager view on Windows 2000 or later platforms.

You can disable AFPA by commenting out the following directives in the httpd.conf configuration file:

AfpaEnable AfpaCache on AfpaLogFile "C:\Program Files\IBM HTTP Server\log\afpalog" V-ECLF

Rebooting the machine after uninstalling the embedded messaging feature.
If you uninstall the embedded messaging feature on a Windows machine, reboot the machine before reinstalling.

Avoiding a user ID with spaces when installing the WebSphere Application Server as a Windows service.
When installing the WebSphere Application Server as a Windows service, do not use a user ID that contains spaces. A user ID with spaces cannot be validated. The user is not allowed to proceed with the installation. To work around this problem, install with a user ID that does not contain spaces, or do not choose to install services.

Changing the display settings from high-contrast black to high-contrast white to view panels with hypertext links.
For Installation wizard panels that contain hypertext links, a display setting of "high-contrast black" causes some of the text to display in the same color (black) as the background color. This makes the text impossible to display. Change your settings to "high-contrast white" to see all of the text in every Installation wizard panel.

Avoiding using the default service names created by the installer because they are common
Unable to use the default service names created by the installer because they are common

In a same version coexistence scenario for IBM HTTP Server V1.3.28 or V2.0.47 on a Windows platform, you are unable to use the default service names created by the installer because they are common.

To work around this problem, perform the following steps:

Install the first copy of IBM HTTP Server, either by itself or with IBM WAS.

Customize the service names for the first install by running the following commands from the first install location:

apache -k install -n "IHS 1.3.28(1)" apache -k install -f conf\admin.conf -n "IHS 1.3.28 Administration (1)"

Edit the AdminAlias directive in the <installLocation 1>\conf\admin.conf file to point to the new service name, for example "IHS 1.3.28(1)".

Remove the default service names installed by the first installation by running:

apache -k uninstall -n "IBM HTTP Server 1.3.28" apache -k uninstall -n "IBM HTTP Administration 1.3.28"

Install the second copy of IBM HTTP Server, either by itself or with IBM WAS. The default service names correspond to the second installation.

The custom service names previously mentioned must be unique on your system and are not required to be those exact strings.

Uninstalling WebSphere Embedded Messaging Publish and Subscribe Edition on Windows 2003 Server.
After using the Add or Remove Programs utility on Windows 2003 Server to uninstall WAS, the entry for WebSphere Embedded Messaging Publish and Subscribe Edition persists. Using the Add or Remove Programs utility to remove WebSphere Embedded Messaging Publish and Subscribe Edition generates a Fatal Error during installation message.

As a work around, manually remove the WEMPS entry in the Windows 2003 Server registry. See Manually uninstalling on Windows platforms for more information about manually uninstalling messaging components.

Lowering the Internet Explorer security level from High to Medium to view the Product overviews from the Launchpad on Windows 2003 machines.
You might see a blank page when trying to view Product overviews from the WebSphere Launchpad on Windows 2003 machines. The default security level setting for the Internet Zone on Internet Explorer is High. Use the following techniques to lower the Internet zone security level to Medium:

Right-click the Internet Explorer icon on the desktop.

Click Properties > Security > Internet Zone.

In the Security level for this zone area, move the slider from High to Medium.

Click OK to save the change.

Expecting a delay before the Installation wizard displays its first panel
The default installation method is to open a command window to a read/write directory, issue the fully qualified command to start the Launchpad tool, and click the Install the product option. This option launches the Installation wizard, which is an InstallShield for MultiPlatforms (ISMP) application. This action launches the Installation wizard in the language of your machine locale unless no translation exists for your locale, in which case you receive the English version. A short delay occurs before the ISMP wizard displays.

You do not need to click the Install the product option more than once to cause the wizard to display.

See Also

Install the product
Configuring the IBM HTTP Server for distributed platforms and the Web server plug-in for Secure Sockets Layer

WASPreUpgrade command
WASPostUpgrade command
Tips for installing the embedded messaging feature
Installation: Resources for learning

	Base product	Network Deployment	IBM HTTP Server	Embedded messaging	Tivoli Global Security Kit	Temp space
Installation directory	/usr/ WebSphere/ AppServer	/usr/ WebSphere/ Deployment Manager	/usr/ IBM Http Server	/usr/ mqm and /opt/ wemps	/usr/ ibm/ gsk7	/tmp
Minimum free space for installation	450 MB	370 MB	20 MB	17 MB; 40 MB on base	32.5 MB on base	150 MB