This topic is a collection of platform-specific tips that can help you install and migrate the base WebSphere Application Server product and the Network Deployment product.
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.
For information related to installing the embedded messaging feature, refer to Tips for installing the embedded messaging feature.
The following sections contain applicable tips:
All platforms
Summary of tips that apply to all platforms
Tips that apply to all platforms
Both the IBM WebSphere Application Server Network Deployment node and the IBM WebSphere Application Server nodes must be on the same code page.
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.
Do not use non-ASCII special characters or double-byte characters in the directory name. This problem is a known limitation.
Verify that the CD-ROM that you are using is a good copy, by verifying the Java 2 SDK on the CD-ROM.
To verify that the Java 2 SDK on the product CD-ROM is working correctly:
For example, on an IBM AIX platform:
cd /mnt/aix/WAS/jdk/java/bin
On a Windows platform, type the following command:
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.
When installing the embedded messaging feature of the WebSphere Application Server product and the Network Deployment product on the same machine, install the WebSphere Application Server product first. Then install the Network Deployment product. Otherwise, embedded messaging installation can fail, or can install with errors.
To install WebSphere Application Server Version 5.0.x or Version 5.1.x Base on the same machine as Version 5.x Network Deployment , and to use WebSphere MQ Version 6.0 as the embedded WebSphere JMS provider, follow the steps listed below:
If you upgrade the Embedded Messaging Server and Client prior to installing WebSphere Application Server Network Deployment, the Network Deployment installation will fail.
You might get an exception while starting the jmsserver process when you install Network Deployment first and then install the base WebSphere Application Server 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 WebSphere Application Server product. The workaround is to uninstall both products, reinstall the base WebSphere Application Server product, and then reinstall the Network Deployment product.
If you make any changes to the configuration, restart the server as noted in the messages section of the administrative console.
Port updates for coexistence require the installation of WebSphere Application Server. 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.
You might experience problems if portions of the beta product remain.
To make sure that you get a clean uninstall, follow these steps:
Refer to Uninstalling the product for more information.
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.
Installing WebSphere Application Server Version 5 from a folder that begins with the word disk results in an error. Provide another name for the folder.
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 Version
5 product. One example of this situation is where you must upgrade the operating
system as part of the Version 5 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, and complete the migration.
You
can also use the migration directory on the CD-ROM to back up a Version 5
configuration in the event of an operating system upgrade. After the upgrade,
you can restore the Version 5 configuration using the WASPostUpgrade tool.
Use the graphical installation interface to avoid this problem.
The migration tools use the XMLConfig utility to export the configuration of V4.0 Advanced Edition. You can install any of the following fixes:
Three different sites contain service for WebSphere Application Server products and features:
Installing 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.
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.
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 WebSphere Application Server 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:
Upgrading the embedded messaging CSD level by applying a WebSphere MQ CSD is supported only for customers with a full WebSphere MQ license.
When planning to install a WebSphere Application Server, Version 5 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:
- on UNIX: - for WebSphere Application Server Network Deployment or Client: Java Messaging - for WebSphere Application Server (base): Runtime, Base (or SDK), Server, Client, Java Messaging and All Message Catalogs - on Windows: - for WebSphere Application Server ND or Client: Java Messaging - for WebSphere Application Server (base): Server and Java Messaging
- CSD1 for WebSphere Application Server V5.0 - CSD3 for WebSphere Application Server V5.0.1 - CSD4 for WebSphere Application Server V5.0.2 and later, including V5.1
After the initial installation of WebSphere MQ and WebSphere Application Server, you should service WebSphere MQ independently of the WebSphere Application Server fix packs. For example, download and apply the WebSphere MQ V5.3 CSD4 before upgrading your WebSphere Application Server to V5.0.2 or before installing V5.1. This approach helps to avoid failures in uninstalling WebSphere Application Server fix packs.
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
The installation verification test is not supported on node names that contain double-byte characters. See Troubleshooting the installation for more information.
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.
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 WebSphere Application Server 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.
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:
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, you must 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.
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.
This collection of fixes for Version 5.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 WebSphere Application Server V5.0 and V5.1 for more information.
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 WebSphere Application Server 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.
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.
Installing 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 /mntRefer 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 zSeries platforms is particularly sensitive to this problem, but the recommendation applies to all Linux platforms.
If you must 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.
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 WebSphere Application Server 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.
On Windows platforms, the size of the embedded messaging feature code for both the client and the server subfeatures is approximately 40 MB. Linux on xSeries servers requires approximately 60 MB. AIX platforms require approximately 40 MB. HP-UX platforms require approximately 70 MB. Solaris Operating Environment platforms require approximately 40 MB.
The Installing WebSphere embedded messaging as the JMS provider topic describes space requirements in detail.
Although you might install the base product in combination with the Network Deployment product or the Enterprise product, installing the server and client subfeature or the client subfeature more than once is not necessary.
If you plan to install the base and Network Deployment products, or the base and the Enterprise products on a single Windows machine, install the base product embedded messaging subfeatures instead of the Network Deployment client feature, or instead of the Enterprise server and client subfeatures. Using the base product features avoids a potential problem caused by a problem in the Microsoft Software Installer utility.
For more information about the actions to take before installing the embedded messaging feature, refer to Installing the WebSphere Application Server embedded messaging feature as the JMS provider. For more information about installing JMS providers, refer to Installing and configuring a JMS provider.
For information about installing the WebSphere MQ Version 5.3 product, or migrating to WebSphere MQ Version 5.3 from an earlier release, refer to the appropriate WebSphere MQ Quick Beginnings book:
These books are available at the WebSphere MQ messaging platform-specific books Web page .
You have a choice if WebSphere MQ Version 5.3 is already installed:
To use WebSphere MQ Version 5.3 as the JMS provider, install the IBM WebSphere Application Server product with only the embedded messaging client feature. The Network Deployment product has only the embedded messaging client feature. Installing and using the WebSphere Application Server embedded messaging client feature is recommended with either the server feature or the full WebSphere MQ Version 5.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 Version 5.3 Java messaging feature.
To install the embedded messaging server feature when WebSphere MQ Version 5.3 is already installed, upgrade WebSphere MQ Version 5.3:
If you install WebSphere MQ Version 5.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 Version 5.3 features or to install the refresh release of WebSphere MQ Version 5.3 for use with the Enterprise product.
If you uninstall the embedded messaging feature, log off and back on, or reboot a Windows machine before reinstalling.
Terminal services is not supported as a valid installation scenario when installing WebSphere Application Server and the embedded messaging feature.
The IBM WebSphere Studio Application Developer Integration Edition and IBM WebSphere Application Server 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.
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.
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:
This change forces the library to load first when the application starts.
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.
When defining your WebSEAL HTTP Server in the administrative console, you must 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.
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 WebSphere Application Server 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 WebSphere Application Server.
For example:
If you cannot bring up IKEYMAN after the previous steps, perform the following steps:
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.
To bring up IKEYMAN, run the<IHS install root>/bin/ikeyman, or <WAS_HOME>/bin/ikeyman.sh command, from a command prompt.
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.
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.
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
Tips that apply to all Linux and UNIX platforms
Perform this step only if you are installing the Java Message Service (JMS) provider for WebSphere Application Server on a Linux or UNIX operating system. You must install the embedded messaging feature to use the JMS provider that WebSphere Application Server provides.
If you are installing the embedded messaging feature, you must create two operating system groups as described in Installing WebSphere embedded messaging as the JMS provider.
The Solaris Operating Environment and HP-UX also require that you increase kernel settings as described in Installing 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.
On Linux and UNIX platforms , the embedded messaging feature installs to fixed locations that you cannot override. The default locations are:
The Installing WebSphere embedded messaging as the JMS provider topic describes directory locations in detail.
Before you install the embedded messaging component on UNIX or Linux platforms, you must define the operating system groups mqm and mqbrkrs, and the user IDs needed for WebSphere embedded messaging. For detailed information, see Installing WebSphere embedded messaging as the JMS provider.
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.
After installing WebSphere embedded messaging, you must 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 Installing WebSphere embedded messaging as the JMS provider and Securing messaging directories and log files.
If you have emacs or other freeware installed on your Linux or UNIX system, verify that the system cp command is being used.
To verify that the Java 2 SDK that WebSphere Application Server installs is working correctly:
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"
WebSphere Application Server 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 WebSphere Application Server 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.
Do not use spaces in the installation directory name. Spaces in directory names are not supported on Linux and UNIX.
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.
To run Samples that use JMS APIs, you must manually start the JMS server (jmsserver) before running the samples on UNIX platforms.
To start the jmsserver process, complete the following steps:
stopServer.sh server1 followed by startServer.sh server1
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.
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.
If you upgrade the Java 2 SDK that ships with the WebSphere Application Server product, and you intend to use the migration tools to migrate the configuration of a Version 4.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:
When you call the .java_wrapper, the Java 2 SDK assumes that the Java code is called and the migration can continue.
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.
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:
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.
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/wasv502base_gs.pdf
.
See Using the Launchpad to start the installation for more information about the Launchpad program.
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 zSeries platforms is particularly sensitive to this problem, but the recommendation applies to all Linux platforms.
Installing 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: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
#ls /mnt/linuxs390/WAS/jdk/java/jre/lib ls.: :stale NFS file handle
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:
Copying cumulative fix and update installer application failed. Cumulative fix or interim fixes cannot be applied. This installation is terminating.
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 Linux for zSeries 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.
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 accessedThe 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:
CD /cdrom/cdrom0
tar cvf * /workarea/filename.tar
CD /workarea
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
Tips that apply to AIX platforms
Space requirements for the embedded messaging feature are described in the Installing WebSphere embedded messaging as the JMS provider topic.
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 |
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.
The X11.base.rte fileset is required on AIX 5.1 to successfully install a fix pack. To verify that the fileset in installed, type:
lslpp -l | grep X11.base.rte
If you do not see details about the fileset on your system, you must install the fileset from the AIX 5.1 product CD-ROM. Install the fileset before installing a fix pack for WebSphere Application Server products.
On AIX Version 4.3.3 and AIX Version 5, you must install Java130.rte.lib Version 1.3.0 to verify that the embedded messaging feature installs correctly. To download a copy of Java 1.3.0:
To correct an existing problem:
After manually uninstalling the WebSphere Application Server product and before reinstalling the product with the embedded messaging component, look for the following directory: /var/mqm/log/WAS_system_name_server_name. 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_name.log file.If this error occurs, the installation of the embedded messaging component fails.
A core dump might occur when you are running WebSphere Application Server with DB2 V7.2 FP8 client in AIX 5.2 having all of the following configurations:
A java core dumped error displays when you start the WebSphere Application Server. This error is from a known DB2 problem.
To solve this problem, rename the libdb2lai.a file on your DB2 client machine as follows:
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
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:
lslpp -l|grep IHS
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
While installing any WebSphere Application Server 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
You can download the fix from the AIX Fix Distribution Service Web site at Web address: http://techsupport.services.ibm.com/rs6k/fixdb.html. Search the AIX Version 4 database for APAR number IY22531. You can find a link to the site in the Installation: Resources for Learning topic.
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.
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.
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.
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 WebSphere Application Server. 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 WebSphere Application Server to coexist, change the WebSphere Application Server administrative console port when installing WebSphere Application Server, 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 -disableThe command permanently disables WebSM server startup.
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.
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.
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 WebSphere Application Server 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 WebSphere Application Server 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.
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:
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
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:
hosts = local = auth , bind
to
hosts = local = auth , bind , local
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, you must 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
Tips that apply to 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 Installing WebSphere embedded messaging as the JMS provider topic.
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 .
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 WebSphere Application Server 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.
The mount command can fail on any CD-ROM that contains files with long file names. Two methods exist for working around the problem and mounting the product CD-ROM:
Editing the pfs.fstab file
To avoid the mount problem, perform the following steps:
/dev/dsk/c0t2d0 mount_point pfs-rrip ro,hardThe mount_point variable represents the mount point of the CD-ROM.
/usr/sbin/pfs_mountd & /usr/sbin/pfsd 4 &
mkdir /cdrom /usr/sbin/pfs_mount /cdromWhere /cdrom represents the mount point of the CD-ROM.
Using pfs_mount to read the Rock Ridge system type
pfs_mountd& pfsd&
pfs_mount -x unix device /mntpnt
/remotemnt -access=server
pfs_exportfs -aRun the remaining steps in this procedure on the local HP-UX system:
pfs_mountd& pfsd&
pfs_mount -x unix remote_server:/remotemnt /localmnt
cd /localmnt/tas
To set kernel parameters, perform the following steps:
Alternatively, rebuild the boot.config file with the following command:
# /usr/sam/lbin/getkinfo -b
Some kernel values for WebSphere Application Server with the embedded messaging feature are higher than those shown in the following table. See the Installing WebSphere embedded messaging as the JMS provider topic for more information.
Some kernel values for WebSphere Application Server IBM DB2 on the same machine, are higher than those shown in the following table.
Typical kernel settings for running WebSphere Application Server 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 |
Follow on-screen instructions to restart your machine and to enable the new settings.
# locale -a
# export LANG=en_US.iso8859
In some cases, the InstallShield for MultiPlatforms (ISMP) program does not detect a previously installed version of WebSphere Application Serve 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.
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.
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.
Certificate revocation lists are not supported for IBM HTTP Server on HP-UX and Linux for S/390 platforms.
The following warning messages are issued despite successful installation. You might see the following messages in the mq_install.log file when installing WebSphere Application Server 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
Tips that apply to 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 Installing WebSphere embedded messaging as the JMS provider.
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 WebSphere Application Server. 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 WebSphere Application Server, 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), WebSphere Application Server 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.
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:
The Red Hat Advanced Server Version 2.1 GUI language selection menu displays two selections for Japanese:
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.
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.
If you are installing on the SuSE Linux Enterprise Server 8.0 - Powered by UnitedLinux 1.0 operating platform, use the installation instructions in the following Support site document: Installing WebSphere Application Server 5.0.1 (or 5.0.2) on SuSE Linux SLES 8 .
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)
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.
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 WebSphere Application Server 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.
Do not use the certificate revocation list (CRL) function on Linux for S/390 at this time.
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.3This 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.
The error can occur when the migration tools cannot find the JAVA_HOME. The WASPreUpgrade command reports the error while backing up the WebSphere Application Server 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:
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
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/desktopRestart your system to solve the problem.
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.
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.
When you select the following features from the First Steps panel, the Web browser window does not open:
To access these features:
Editing the ikeyman script to bring up IKEYMAN for the IBM HTTP Server 1.3.28 shipped with WebSphere Application Server
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 WebSphere Application Server, 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:
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 WebSphere Application Server 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 you must 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.
WebSphere Application Server, Version 5.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 WebSphere Application Server, 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, Version 3.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
When starting the Launchpad program for WebSphere Application Server 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, you should 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.
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
Tips that apply to 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 Installing WebSphere embedded messaging as the JMS provider.
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.
When installing WebSphere Application Server 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.
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.
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 WebSphere Application Server or Domino Server plug-in manually using the Domino Server Web administration tool. The workarounds include:
If DSAPI filter files are already specified, use a space to delimit the WebSphere Application Server plug-in file.
If you use the embedded JMS provider in WebSphere Application Server 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 application servers. Set the LANG and LC_ALL variables to zh_TW instead of zh_TW.EUC.
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.
# /cdrom/cdrom0/sun/launchpad.sh
Windows platforms
Summary of tips that apply to Windows platforms
Tips that apply to 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 |
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.
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.
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.
If you are using the downloadable archive file to install the WebSphere Application Server product, the PKWARE pkunzip utility might not decompress the download image correctly. Use another utility (such as WinZip) to unzip the image.
Installing WebSphere Application Server on some international computers might result in an installation failure or in font problems. Use the following procedure to work around this problem:
For example, C:\WINDOWS or C:\WINNT on a Windows system.
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.
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 WebSphere Application Server shares the AFPA driver with any coexisting IBM HTTP Server. Uninstalling a coexisting Version 1.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
If you uninstall the embedded messaging feature on a Windows machine, you must reboot the machine before reinstalling.
When you change the document root in the IBM HTTP Server 1.3.26.x administrative server, the ImagePath entry in the registry that corresponds to the HTTP server is not updated. There have been no reported functionality problems caused by this incorrect registry entry.
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.
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.
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 Version 1.3.28 or Version 2.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:
apache -k install -n "IHS 1.3.28(1)" apache -k install -f conf\admin.conf -n "IHS 1.3.28 Administration (1)"
apache -k uninstall -n "IBM HTTP Server 1.3.28" apache -k uninstall -n "IBM HTTP Administration 1.3.28"
The custom service names previously mentioned must be unique on your system and are not required to be those exact strings.
After using the Add or Remove Programs utility on Windows 2003 Server to uninstall WebSphere Application Server, 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.
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:
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.