All platforms

• Uninstalling fixes for IBM HTTP Server and MQ Series (Embedded Messaging) before installing Fix Pack 2 updates to these features
• Stop all running Java processes before you install or remove fix packs or interim fixes to avoid a corrupted system
• Installing Fix Pack 2 for the security.wssecurity component takes a long time
• WebSphere Application Server, Version 5.0.2 only updates IBM HTTP Server 1.3.26.x
• Uninstall the Web services technology preview before installing Fix Pack 2

• WebSphere Application Server products at level 5.0.0 might not support your operating system

• WebSphere Application Server products at level 5.0.0 might not support your operating system

Tips: For other installation and uninstallation problems associated with WebSphere embedded messaging, see Messaging and Extended Messaging.

Uninstalling fixes for IBM HTTP Server and MQ Series (Embedded Messaging) before installing Fix Pack 2 updates to these features

If you have installed fixes for IBM HTTP Server or MQ Series Embedded Messaging, you need to uninstall these fixes prior to updating these features using the Update Installer. If you do not uninstall these fixes, the updates to IBM HTTP Server or Embedded Messaging made during the fix pack installation might fail or the installation might be faulty. You can choose to skip the updates IBM HTTP Server or Embedded Messaging if they are not required during fix pack installation. See the Update Installer documentation for more information.

Stop all running Java processes before you install or remove fix packs or interim fixes to avoid a corrupted system

Symptom:

The fix pack installer does not warn you to stop all running Java processes before you install or remove fix packs or interim fixes. Your system gets corrupted if you do not manually stop all running processes.

Problem:

It is recommended to stop all applications (IBM and non-IBM) that might be using the Java processes before installing or removing interim fixes or fix packs. For example, in a co-existence scenario, if you have WebSphere Application Server, Version 4 installed, stop its server too. Another example, if you have Tomcat installed, it is recommended to stop this too.

Response:

You must manually stop all running Java processes before installing or removing fix packs or interim fixes. See the Readme files for Fix Pack 1, Fix Pack 2, or the update installer; or see the following InfoCenter articles for more information:

• Installing interim fixes and fix packs
• Removing interim fixes and fix packs
• UpdateSilent command
• UpdateWizard command

Installing Fix Pack 2 for the security.wssecurity component takes a long time

Problem:

Installing Fix Pack 2 for the security.wssecurity component takes a long time.

Description:

During the installation of Fix Pack 2 for the base WebSphere Application Server product, the update installer can take approximately 80 minutes to install service to the security.wssecurity component. Do not cancel the installation during that time.

Response:

Do not cancel the installation while the update installer is applying service to the security.wssecurity component.

Note: This problem does not happen frequently.

WebSphere Application Server, Version 5.0.2 only updates IBM HTTP Server 1.3.26.x

The update installer only updated IBM HTTP Server 1.3.26.x not IBM HTTP Server 2.0. The update installer does not do any IBM HTTP Server version checking so it is important to ensure that you are applying WebSphere Application Server, Version 5.0.2 to the IBM HTTP Server 1.3.26.x.

Uninstall the Web services technology preview before installing Fix Pack 2

Symptom:

The uninstaller for the Web services technology preview does not cancel the registration of the administrative console panels when run.

Problem:

When the installer is created for the Web services technology preview in the WebSphere Application Server, Version 5 stream, the installation process is verified, but the uninstallation process is not. It is now a prerequisite for the Web services technology preview to be uninstalled prior to the application of Fix Pack 2.

Response:

Perform the following steps to work around this problem:

1. Open a command prompt.
2. Change the directory to install_root\bin .
3. Execute the setupCmdLine.bat file (on RedHat Linux, this file is setupCmdLine.sh)
4. Execute the PluginProcessor.bat file (on RedHat Linux, this file is PluginProcessor.sh) with the following syntax:

   PluginProcessor.[bat,sh] -uninstall -pluginID "com.ibm.ws.webservices.console"

WebSphere Application Server products at level 5.0.0 might not support your operating system

Fix Pack 1, which is product level 5.0.1 supports AIX 5.2. Fix Pack 2, which is product level 5.0.2 supports the Solaris Operating Environment 9. To install the product, follow the procedure in the InfoCenter article: Installing the product, to download and use an updated prereqChecker.xml file to install the product level 5.0.0 installation image. After installing the product at level 5.0.0, you can install the appropriate fix pack for your operating system.

The updateWizard interface does not recognize the existing WebSphere Application Server product

On some platforms, the updateWizard interface to the update installer program does not recognize the existing WebSphere Application Server product on Solaris Operating Environment.

Problem:

The problem is due to a limitation in the InstallShield for MultiPlatforms (ISMP) program that the update installer program uses.

The ISMP program does not recognize previous installations of WebSphere Application Server on some operating platforms.

Response:

To work around the problem, click Specify product information and type the fully qualified installation root directory for the existing product in the Installation directory field of the updateWizard panel.

The updateSilent interface fails when installing Fix Pack 2 from a directory with a space in the path

Symptom:

The updateSilent interface fails on Windows platforms when installing Fix Pack 2 from a directory with a space in the path. The failure occurs while applying service to the amjrte component.

Problem:

If you launch the fix pack installer from an path including space (" "), for example, program files

Response:

Use the updateWizard interface to get around the problem, or download and unpack Fix Pack 2 into a non-standard location that does not have a space in the path name. You can then use the updateSilent interface.

If you use a non-standard installation root, it is possible that the update installer cannot set the JAVA_HOME environment variable. If you receive a message that the update installer cannot set JAVA_HOME, set the environment variable yourself, or issue the appropriate command script from the bin directory of the installation root:

1. Open a command-line window.
2. Change directories to the bin directory of the installation root.
3. Issue the following command to set JAVA_HOME:

   install_root\bin\setupCmdLine.bat

Space checking on HP-UX systems can fail even though adequate space is available

Symptom:

A message appears, stating that too little space is available to install Fix Pack 2 even though enough space is available. The symptom is known to occur on the HP-UX systems only.

Problem:

The update installer can fail to check space properly on the HP-UX systems. Verify that there is enough space on your system. If there is adequate space, edit the updateSilent.sh or updateWizard.sh script to bypass space checking.

Response:

Add each highlighted line in the last Java invocation of the appropriate script to bypass space checking.

Edit the updateWizard.sh script:

    "$JAVA_HOME"/bin/java \
    -Xmx256m \
         -Dcom.ibm.websphere.update.space.override=true \
    -cp "$currentDir"/installer.jar:"$currentDir"/lib/extfile.jar \
    -Dswing.defaultlaf="$MotifLAF" \
    -DCURRENT_UPDATE_DIR="${currentDir}" \
           run

Edit the updateSilent.sh script:

     if [ -f /etc/mvl-release ]
         then
              "$JAVA_HOME"/bin/java \
             -Xmx256m \
                     -Dcom.ibm.websphere.update.space.override=true \
              -cp "$currentDir"/installer.jar:"$currentDir"/lib/extfile.jar \
              -DCURRENT_UPDATE_DIR="${currentDir}" \
              com.ibm.websphere.update.launch.Launcher \
              com.ibm.websphere.update.silent.UpdateInstaller $@
         else
              "$JAVA_HOME"/bin/java \
             -Xmx256m \
                     -Dcom.ibm.websphere.update.space.override=true \  
              -cp "$currentDir"/installer.jar:"$currentDir"/lib/extfile.jar \
              -DCURRENT_UPDATE_DIR="${currentDir}" \
               com.ibm.websphere.update.silent.SilentArgsCollector $@
     fi

If you bypass the prerequisite checking, add the highlighted line to other places in each file, just above each -cp ... line.

Add the bypass line only when you verify that space checking is failing when there is adequate space available. Disk space checking provides a critical safeguard; performing an update installation when there is too little space can cause the fix pack installation to fail, which produces an unusable product installation.

WebSphere Application Server, Version 5.0.2 Samples installation and instructions

WebSphere Application Server Version 5.0.2 contains updates for the Samples, translations for all Samples, and a new Web Services Sample. The Samples documentation update is located in the samples50_fp2 directory. You can find this directory in the root directory of WebSphere Application Server. The file name is readme.html and there is a translated Readme file for each supported language. The document contains instructions for uninstalling the WebSphere Application Server, Version 5 and Version 5.0.1 Samples, and installing the new Web Services Sample and the Version 5.0.2 Samples.

Passwords are not compared when creating a new account

When creating a new account, you must provide a new password. The first Password field is not compared for a match with the second Password (Repeat) field.

Add to cart resets the quantity of an item to one

When an item is added to the shopping cart the item is added with an initial quantity of one. You can adjust the quantity to a higher number in the shopping cart. If that same item is added again to the shopping cart, the adjusted quantity is reset to one.

Pet Store pages do not show animal pictures or details when HTTP transport is reconfigured to use a port other than 9080

If the Pet Store pages do not show animal pictures or details when you reconfigure the IBM WebSphere Application Server to use an HTTP transport other than port 9080, update the URL of Pet Store Catalog DAOSQLURL to use the new port.

You can reconfigure the URL resource to use the new port with the IBM WebSphere Application Server administrative console. Go to Resources > URL Providers (set scope to your Server) > Samples URL Provider - HTTPs > URLs > Pet Store Catalog DAO SQL URL. The port number is in the Specification field.

Forceful repopulating of Pet Store database fails

The option to forcefully repopulate the Pet Store database fails with an internal server error HTTP 500 - The page cannot be displayed. Do not use this option.

Installing the Applet Client Samples feature from the Application Clients 1.4 CD-ROM

If you install the Applet Client Samples feature from the Application Clients 1.4 CD-ROM, perform the following steps to update the Java security policy.

Add the following grant blocks into the client.policy file under the properties directory of the Application Clients installation root, for example, C:\Program Files\WebSphere\AppClient\properties\client.policy , if they are not present. Modify the entries for yourserver.yourdomain.com to reflect the complete name of the WebSphere Application Server to which you connect :

grant {
  permission java.io.FilePermission "${was.install.root}/samples/lib/TechnologySamplesAppletClient/BasicCalculatorAppletClient.jar", "read";
  permission java.io.FilePermission "${was.install.root}/samples/lib/TechnologySamplesAppletClient/BasicCalculatorClientCommon.jar", "read";
  permission java.io.FilePermission "${was.install.root}/samples/lib/TechnologySamplesAppletClient/BasicCalculatorEJB.jar", "read";
};

grant codeBase "file:${was.install.root}/samples/lib/TechnologySamplesAppletClient/*" {
  permission java.util.PropertyPermission "*", "read";
  permission java.net.SocketPermission "yourserver.yourdomain.com", "connect";
};

grant codeBase "file:${was.install.root}/lib/*" {
  permission java.security.AllPermission "${was.install.root}/lib/utils.jar";
};

grant codeBase "file:${was.install.root}/samples/lib/TechnologySamplesAppletClient/*" {
  permission java.security.AllPermission "${was.install.root}/lib/utils.jar";
};

Adding the grant blocks to avoid receiving an exception when running Applet Client Samples from the Application Clients Version 5.0.2

Symptom:

When you run the Applet Client Samples from the Application Clients Version 5.0.2, the following exception is logged in the Java console of the browser:

--Looking-up Home... java.lang.ExceptionInInitializerError: java.security.AccessControlException: access denied (com.ibm.websphere.security.WebSphereRuntimePermission AdminPermission)        at java.security.AccessControlContext.checkPermission(AccessControlContext.java:286)        at java.security.AccessController.checkPermission(AccessController.java(Compiled Code))        at java.lang.SecurityManager.checkPermission(SecurityManager.java(Compiled Code))        at com.ibm.websphere.management.AdminServiceFactory.getAdminService(AdminServiceFactory.java:55)

Problem:

Additional access control policy is required for the Application Clients Version 5.0.2 to run the Applet Client Samples.

Description:

You can encounter this problem if you view the log in the Java console of the browser.

Response:

To avoid this exception, add the following grant blocks into the client.policy file under the properties directory of the Application Clients installation root, for example, C:\Program Files\WebSphere\AppClient\properties\client.policy, if they are not present.

grant codeBase "file:${was.install.root}/lib/*" {
  permission java.security.AllPermission "${was.install.root}/lib/utils.jar";
};

grant codeBase "file:${was.install.root}/samples/lib/TechnologySamplesAppletClient/*" {
  permission java.security.AllPermission "${was.install.root}/lib/utils.jar";
};

Information you should know about the Java 2 Platform, Enterprise Edition client samples launchAPI and classLoader

Symptom:

When running the Java 2 Platform, Enterprise Edition (J2EE) classLoader sample, the application output looks like the following:

-----------------------------------------------------------------
Running ClassLoaderClientMain from the 
J2EEAppClientClassLoader.ear file
-----------------------------------------------------------------

IBM WebSphere Application Server, Release 5.0
J2EE Application Client Tool
Copyright IBM Corp., 1997-2002
WSCL0012I: Processing command line arguments.
WSCL0013I: Initializing the J2EE Application Client Environment.
WSCL0100E: Exception received: com.ibm.etools.archive.exception.ArchiveWrappedEx
ception
Stack trace of nested exception:
com.ibm.etools.archive.exception.ResourceLoadException: IWAE0007E Could not load
 resource "META-INF/ibm-application-client-bnd.xmi" in archive "J2EEAppClientCla
ssLoaderClient.jar"
Stack trace of nested exception:
java.lang.NullPointerException
      at com.ibm.etools.archive.impl.InternalModuleHelper.getDDResourceURIIfPr
oxy(InternalModuleHelper.java:60)
      at com.ibm.etools.archive.impl.InternalModuleHelper.getDDResourceIfProxy
(InternalModuleHelper.java:64)
      at com.ibm.etools.archive.impl.InternalModuleHelper.appClientBindingsLoa
ded(InternalModuleHelper.java:146)
      at com.ibm.etools.archive.impl.InternalModuleHelper.fixupBndOrExtRootsIf
Necessary(InternalModuleHelper.java:44)
   ... more

When running the J2EE launchAPI sample, the application output looks like the following:

------------------------------------------------------------------ 
Running LaunchAPIClientMain from the LaunchAPI.ear file 
using launch API 
------------------------------------------------------------------ 
IBM WebSphere Application Server, Release 5.0 
J2EE Application Client Tool 
Copyright IBM Corp., 1997-2002 
WSCL0013I: Initializing the J2EE Application Client Environment. 
launch() failed.  See stack trace for details: 
java.lang.reflect.InvocationTargetException         
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)         
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. 
java:79)         					 
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces 
sorImpl.java:41)       
      at java.lang.reflect.Method.invoke(Method.java:371)         
      at com.ibm.websphere.samples.j2eeappclients.launchapi.LaunchAPIMain.main 
(LaunchAPIMain.java:83) 
Caused by: com.ibm.websphere.client.applicationclient.ClientContainerException: 
com.ibm.etools.archive.exception.ArchiveWrappedException 
Stack trace of nested exception: 
com.ibm.etools.archive.exception.ResourceLoadException: IWAE0007E Could not load  
 resource "META-INF/ibm-application-client-bnd.xmi" in archive "LaunchAPIClient. 
jar" 
Stack trace of nested exception: 
java.lang.NullPointerException         
      at com.ibm.etools.archive.impl.InternalModuleHelper.getDDResourceURIIfPr oxy(InternalModuleHelper.java:60)         
      at com.ibm.etools.archive.impl.InternalModuleHelper.getDDResourceIfProxy 
(InternalModuleHelper.java:64)         
      at com.ibm.etools.archive.impl.InternalModuleHelper.appClientBindingsLoa 
ded(InternalModuleHelper.java:146)         
   ... more

Problem:

The file meta-inf/ibm-application-client-bnd.xmi in the J2EEAppClientClassLoaderClient.jar file in the samples/lib/J2EEAppClients/J2EEAppClientClassLoader.earfile is missing the following line :

<applicationClient href="META-INF/application-client.xml#Application-client_ID"/>

The file meta-inf/ibm-application-client-bnd.xmi in the LaunchAPIClient.jar file in the samples/lib/J2EEAppClients/LaunchAPI.ear file is missing the following line:

<applicationClient href="META-INF/application-client.xml#Application-client_ID"/>

Response:

To solve this problem, complete the following steps:

1. Add line <applicationClient href="META-INF/application-client.xml#Application-client_ID"/> before the line </clientbnd:ApplicationClientBinding> in the file samples\src\J2EEAppClients\ClassLoader\ClassLoaderClient\META-INF\ibm-application-client-bnd.xmi.
2. Add line <applicationClient href="META-INF/application-client.xml#Application-client_ID"/> before the line </clientbnd:ApplicationClientBinding> in the file samples\src\J2EEAppClients\LaunchAPI\LaunchAPIClient\META-INF\ibm-application-client-bnd.xmi.
3. Rebuild these samples by following the instructions in the Application Client Samples Gallery (see the section Client Technology Samples > J2EE application client > Build It Yourself).

Patches needed for correct character display of the installation panel on Asian language platforms

If the installation panel displays garbled characters on Asian language platforms, including Korean, traditional Chinese, Japanese, and simplified Chinese, on the HP-UX 11i platform, verify that the following patches are installed on your HP-UX 11i machine:

Name	Brief 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.

Cannot display newly created Windows domain users during application management for the non-English locales only

The newly created domain users are not retrieved when you perform application management. The newly created groups display correctly and the newly created local users also display correctly. If you map users to roles by clicking A Role > Choose Users > Find Users, only users created on Primary Domain Controller before adding the client machine to the domain are displayed. If a new user is created while the client machine is already on the domain, the getUser function does not retrieve the new users created on Primary Domain Controller. The getUser application programming interface (API) works correctly for the English locales, but does not work correctly for the non-English locales.

A 404 Not Found exception thrown when cells contain nodes on different locales

On UNIX platforms, a com.ibm.websphere.management.filetransfer.client.TransferFailedException: File download failed [404].Message: 404 Not Found exception is thrown when federating nodes with non-matching double-byte character set (DBCS) locales.

All nodes incorporated into the same cell must be located on host machines with an identical locale setting. Cells containing nodes on different locales do not function properly and are not supported.

Help search does not return hits for Latin-1 terms with diacritical markings

The help search in the administrative console does not return search results for Latin-1 terms that contain diacritical markings (for example, German "fur", where the "u" includes an umlaut). To work around this problem, use the decimal representation of the character in the search term (for example, "f&#252;r").

Cannot access the Readme file and PDF installation files for Traditional Chinese and German languages through the LaunchPad

You can view these files through any Web browser.

The Readme file for Traditional Chinese is located at:

<cd drive>\readme\readme_zh_tw.html

The installation PDF file for Traditional Chinese is located at:

<cd drive>\doc\installguide_zh_tw.pdf

The Readme file for German is located at:

<cd drive>\readme\readme_de.html

The installation PDF file for German is located at:

<cd drive>\doc\installguide_de.pdf

Avoid missing characters in license agreement

Before installing the IBM WebSphere Application Server on a Traditional Chinese AIX machine, type the following commands to avoid missing characters within the license agreement:

cd /usr/lib/nls/loc/iconv/
mv IBM-eucTW_CNS11643.1986-1 IBM-eucTW_CNS11643.1986-1.save
mv big5_CNS11643.1986-1 big5_CNS11643.1986-1.save

Product registration displays as English when installing in Brazilian Portuguese

When registering your product from the installation in Brazilian Portuguese, the product registration page displays in English.

To view the registration page in Brazilian Portuguese, you can enter the following URL, <install_root>\prt\PRT_Welcome_ptb.html or register the product using FirstSteps in Brazilian Portuguese.

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

Both the IBM WebSphere Application Server Network Deployment node and the IBM WebSphere Application Server nodes must be on the same code page.

The Java virtual machine cannot translate coded character set identifier used by the embedded messaging queue manager

When running the IBM WebSphere Application Server with global security enabled the embedded messaging provider can fail to start with message MSGS0504E and an UnsupportedEncodingException:

 MSGS0504E: JMS Server Security Service Thread received Socket Exception:
  java.io.UnsupportedEncodingException: Cp5050

This message indicates that the Java virtual machine (JVM) cannot translate the coded character set identifier (CCSID) used by the embedded messaging queue manager.

To work around this problem, complete the following steps:

1. Set a locale and language value that maps to a code page supported by the JVM. Refer to the WebSphere MQ messaging platform-specific books Web site at http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/platspecific.html for a WebSphere MQ Platform Quick Beginnings V5.3 manual that is relevant to your platform.
2. Look for a table in the manual with a list of locale and language to CCSID mappings supported by the queue manager.
3. Select a locale and language that maps to a CCSID that is supported by the JVM. Set the selected locale and language, and restart the IBM WebSphere Application Server.

Insufficient prerequisites cause warning messages during installation with AIX 4.3.3

When installing the Simplified Chinese version of the IBM WebSphere Application Server on AIX 4.3.3, warning messages display because of insufficient prerequisites. The error message indicates that the file levels X11.fnt.ucs.ttf, X11.fnt.ucs.ttf_TW, and X11.fnt.ucs.ttf_KR do not match the level of file X11.fnt.ucs.ttf_CN. The last file has a level of 4.3.3.25, while the others have the level 4.3.3.

To work around this problem, force the installation by modifying the prereqChecker.xml file to the required file level.

Japanese not recommended on Red Hat Advanced Server Version 2.1

The Red Hat Advanced Server Version 2.1 GUI language selection menu displays two selections for Japanese: Japanese (eucJP) and Japanese (SJIS).

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

For reference see the Red Hat Japanese Web site at http://www.jp.redhat.com/support/7.2/sla/rh72faq.html .

Evaluating the product on National Language Version operating systems

The following steps are workarounds to evaluate IBM WebSphere Application Server and IBM WebSphere Application Server Network Deployment, Version 5 on National Language Version operating systems.

• Windows NT platform:
  1. Open Regional Settings from the Windows NT Control Panel.
  2. Change the setting to English (United States) on Regional Settings, and then select the set as system default locale check box.
  3. Add English (United States) on Input Locales, and set the default input locale to English.
  4. Click OK on the Regional Settings Properties window.
  5. Restart the machine with the English locale settings.
  6. Install the IBM WebSphere Application Server, Version 5.

  Tips:Do not change locale settings to original non-English settings until you finish the evaluation.

• Windows 2000 platform:
  1. Open Regional Options from the Windows 2000 Control Panel.
  2. Change the setting Your locale (location): to English (United States) on General, click Default Settings, and then change the system locale to English (United States).
  3. Add English (United States) on Input Locales, and set the default input locale to English.
  4. Click OK on the Regional Options window.
  5. Restart the machine with the English locale settings.
  6. Install the IBM WebSphere Application Server, Version 5.

  Tip:Do not change locale settings to original non-English settings until you finish the evaluation.

• AIX 4.3.3 or AIX 5.1:

  Open Terminal and run the following command before you install the IBM WebSphere Application Server, Version 5. Every time that you open a new terminal, you need to invoke this command:

  # export LANG=en_US

• Solaris Operating Environment 8:

  Open Terminal and run the following command before you install the IBM WebSphere Application Server, Version 5. Every time you open a new terminal, you need to invoke this command:

  # LANG=en_US
  # export LANG

Changing the locale encoding to English to install WebSphere Application Server on SuSE 8.0 SLES for PowerPC

Symptom:

The WebSphere Application Server installation program is corrupted when you start the installation on SuSE SLES 8.0 PowerPC. The double-byte character set (DBCS) languages display the characters incorrectly. The single-byte character set (SBCS) languages display the characters correctly.

Problem:

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

Response:

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

1. Type export LC_ALL=C and click Enter.
2. Type export LANG=C and click Enter.
3. To verify that the locale is properly set to English, type locale to see that all variables are set to C.

Help links for Application Assembly Tool, Application Resource Client Tool and Tivoli Performance Viewer bring up the English files

Symptom:

Help links for Application Assembly Tool, Application Resource Client Tool and Tivoli Performance Viewer bring up the English files.

Response:

To work around this problem, change the path to the preferred language version in your browser location bar to display the appropriate language. For example, replace the <en> directory name with one of the following desired languages: de, es, fr, it, ja, ko, pt, zh, zh_tw.

Persisted Session Time is displayed as a kanji character and ????? in Traditional Chinese locales

Symptom:

The advice name, Persisted Session Time, in the Runtime Performance Advisor (RPA) configuration in the administrative console is shown as a kanji character and ????? in Traditional Chinese locales only.

Problem:

You can access to the advice configuration setting on the administrative console by clicking Servers > Application Servers > server_name > Runtime Performance Advisor Configuration > Advice Configuration.

The advice name, Persisted Session Time, is shown as kanji character and ????? if you select the Traditional Chinese as the language on the Web browser to get access to the administrative console.

Response:

Treat the advice item displayed as a kanji character and ????? as Persisted Session Time.

Editing the image path for the WebSphere Application Server service

Symptom:

When starting the WebSphere Application Server service, the Windows operating system might throw an error containing the phrase "Error 193: ... is not a valid Win32 application. Alternatively, it might report Could not start the ... service on Local Computer Error 193: 0xc1.

Problem:

Certain Windows systems cannot handle spaces in the path to the service executable well.

Response:

If this problem occurs, complete the following steps:

1. Click Start > Run.
2. Enter regedit and click OK.
3. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\IBMWAS5Service.
4. Double-click ImagePath registry value.
5. Edit the path to wasservice.exe in the value data field by adding quotes around the path. For exmaple, "C:\Program Files\WebSphere\AppServer\bin\wasservice.exe" "IBMWAS5Service - server1".
6. Click OK and exit regedit.

The service now starts without any errors.

The service shows incorrect status when the log root is changed

Symptom:

The WebSphere Application Server service might go to the started state and then return to the stopped state when you start the WebSphere Application Server service even though the server starts successfully. This change in state might happen if the default log root is altered in the variables.xml config file.

Problem:

The WebSphere Application Server service cannot find the process ID file (for example, server1.pid) to verify that the server starts successfully. The process ID is created relative to the log root.

Response:

In order for the WebSphere Application Server service to display the correct status, you must modify the log root directory in your variable.xml file back to the default log root directory, for example, C:\WebSphere\AppServer\logs. Otherwise, you must issue the stopServercommand to stop the server, for example,

C:\WebSphere\AppServer\bin\stopServer.bat server1

ImagePath entry not updated in registry when you change the document root

When you change the document root in the IBM HTTP Server Version 1.3.26 administration server, the ImagePath entry in the registry, corresponding to the HTTP server, does not update. There are no reported functionality problems caused by this registry entry.

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.

Using IBM HTTP Server IKEYMAN to create a key database causes a core

Symptom:

A core occurs while using the IKEYMAN or IKEYCMD utility, or during the IBM HTTP Server Secure Sockets Layer (SSL) initialization.

An incompatibility exists between functions in various C or C++ run-time libraries. Depending on the order that the libraries are loaded, a core can occur or the IBM HTTP Server fails to initialize. This problem is seen on various RedHat Intel versions, and SuSE SLES and RedHat on OS/390.

Description:

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 the use of in an incompatible library routine.

Response:

If you encounter this problem, set the environment variable LD_PRELOAD as follows before starting the 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.

Specifying the Listen 0.0.0.0.443 directive to the configuration file when you run the IBM HTTP Server Version 2.0.42.2 on the Linux for PowerPC operating system

Note:This section describes the situation if you want to setup Secure Sockets Layer (SSL) or secure connections.

Symptom:

A PEER_ID_NOT_SET error occurs in the error log if you run the IBM HTTP Server Version 2.0.42.2 on the Linux for PowerPC operating system without specifying the Listen 0.0.0.0.443 directive to the configuration file to enable the SSL.

Response:

You must specify the Listen 0.0.0.0.443 directive to the configuration file when you connect to the IBM HTTP Server Version 2.0.42.2

The plug-in configuration fails for Domino 6 Web server during a full installation

Symptom:

The plug-in configuration fails for Domino 6 Web server during a full installation on Solaris Operating Environment, Windows and AIX platforms. The following example from a full installation on Solaris Operating Environment shows the errors thrown during the configuration phase:

Exception in thread "main" java.lang.UnsatisfiedLinkError: /opt/lotus/notes/60010/sunspa/liblsxbe.so: ld.so.1: /opt/WebSphere/AppServer/java/bin/../bin/sparc/native_threads/java: fatal: libxmlcommon.so: open failed: No such file or directory
       at java.lang.ClassLoader$NativeLibrary.load(Native Method)
       at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1414)
       at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1338)
       at java.lang.Runtime.loadLibrary0(Runtime.java:744)
       at java.lang.System.loadLibrary(System.java:815)
       at lotus.notes.NotesThread.load(NotesThread.java:214)
			at lotus.notes.NotesThread.<client>(NotesThread.java:24)

Problem:

The plug-in configuration fails for Domino 6 Web server during a full installation on Solaris Operating Environment, Windows and AIX platforms. Please note that WebSphere Application Server, Version 5.0.2 is not a full installation on Solaris Operating Environment, Windows and AIX platforms. However, if you currently have a version of WebSphere Application Server product that is older than Version 5, and you want to upgrade your WebSphere Application Server product to Version 5.0.2, you must complete a full installation of Version 5 before installing Version 5.0.2.

Response:

The solution is to manually configure the Domino Web server to use the plug-in. Complete the following steps:

1. Start up the Domino Web server.
2. Access the names.nsf file through your Web browser, for example, http://hostname.raleigh.ibm.com/names.nsf. Then you need to enter the name for the Administrator and the Administrator password.
3. Click the Configuration link on the left side of the page.
4. Click the Servers link on the left side of the page.
5. Click the All Server Documents link on the left side of the page.
6. Click the server you want to work with WebSphere Application Server.
7. Click Edit Server at the top left of the center window.
8. Click Internet Protocols.
9. In the DSAPI section, add the path to the Domino plug-in. The plug-in gets installed in the WebSphere Application Server bin directory.
10. Click Save and Close on the upper left hand corner of the center window.

    Note:If on Windows platforms, add the variable Plugin Config to the registry under the path HKEY_LOCAL_MACHINE > SOFTWARE > IBM > WebSphere Application Server > 5.0.0.0. Set the value for this variable to the location of the plugin-cfg.xml file.

11. Restart the Domino Web server.

Issuing the ls -la command in the IBM HTTP Server directory on the HP platform shows files with 777 permissions

Symptom:

Issuing the ls -la command in the IBM HTTP Server directory on the HP platform shows files with 777 permissions.

Problem:

IBM HTTP Server files with world-writeable permissions on the HP platform run the risk of a security exposure.

Response:

To remove the world-writeable permissions on the files with 777 permissions, issue the following command:

find <IHS install directory> -perm 777 -exec chmod o-w {} \;

For example:

find /opt/HTTPServer -perm 777 -exec chmod o-w {} \; 

You must change the permissions of these files to reduce the risk of security exposures. Also, if you follow these instructions and change the permissions, the functionality of IBM HTTP Server is not adversely affected.

Null pointer exception during interactive installation of IBM HTTP Server on AIX systems

When installing IBM HTTP Server as a standalone GUI installation 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:

1. Exit the installer.
2. Issue the lslpp -l|grep IHS command to see if there are remaining IBM HTTP Server registry entries that should not be there.
3. 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, for example:

java -jar _uninst/uninstall.jar -silent

Cannot start IBM HTTP Server 2.0.42.1 on AIX 5.2 systems

There is a potential IBM HTTP Server 2.0.42.1 startup failure 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 the Listen directives that do not specify an Internet Protocol address. The following is an example of the 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.

In the meantime, 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

Certificate Revocation List is not supported for IBM HTTP Server on HP-UX and Linux/s390

Using Certificate Revocation List (CRL) with IBM HTTP Server HP-UX and Linux/s390 is not supported at this time.

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

The batchUpdate new feature cannot work for an EJB container-managed persistence bean when it mapped to more than one table

WebSphere Application Server, Version 5.0.2 now has a new feature, batchUpdate, for EJB container-managed persistence (CMP) bean. However, the new feature cannot work for an EJB CMP bean when it mapped to more than one table. For example, when mapping inherited enterprise beans as root-leaf to a database, the subclass enterprise beans are mapped to two tables.

A single access-intent read ahead hint might not refer to the same bean type in more than one relationship

A single access-intent read ahead hint might not refer to the same bean type in more than one relationship. For example, if a Department enterprise bean has a relationship employees with the Employee enterprise bean, and also has a relationship manager with the Employee enterprise bean, then a read ahead hint cannot specify both employees and manager.

Enterprise bean deployment and Sybase IMAGE type restrictions

When deploying enterprise beans with container-managed persistence (CMP) types that are non-primitive and do not have a natural Java Database Connectivity (JDBC) mapping, the deployment tool maps the CMP type to a binary type in the database, where it is stored as a serialized instance. For Sybase, the JDBC type LONG VARBINARY is used, which the Sybase driver maps to the native type IMAGE. You cannot use VARBINARY, which has fewer restrictions than IMAGE in Sybase, because it is limited to a size of 255 bytes, which is too small for typical serialized Java objects.

The specific restrictions on the IMAGE type are:

• You cannot use IMAGE type in the WHERE clause of an SQL query.

  You can encounter this restriction whenever an enterprise bean contains an EJB-QL query that has a CMP type in the WHERE clause, which maps to the IMAGE type in the Sybase relational database (RDB).

• You cannot use IMAGE type in select queries marked DISTINCT. This situation arises in these user scenarios:
  • When the DISTINCT key word is specified in an EJB-QL select query having a Java type mapping to IMAGE.
  • Enterprise beans that have finder and ejbSelect() methods returning java.util. Set and having CMP types mapping to IMAGE.

• Change the CMP type mapping from IMAGE or LONG VARBINARY to VARBINARY. Only take this action if you think the serialized instance of the CMP type is never larger than 255 bytes.
• Map the CMP type to multiple RDB fields through a composer. For example, if the CMP type is a Java object X with an int field and a string field, then map X to two RDB fields INTEGER and VARCHAR, using a composer.

Install Application Client features before installing the interim fixes or the fix packs to avoid component regression problems

Problem:

When installing Application Clients V5.0.0 features from the product CD-ROM onto an existing Application Clients V5.0.x system, the installer reinstalls related components at the V5.0.0 level, which is a regression for those components back to the V5.0.0 level.

Response:

There are two possible installation states in regard to the regression problem:

• The system has not regressed because you have not yet installed the interim fixes or the fix packs. If this is true, you can avoid the problem by installing all features you might require before installing the interim fixes and the fix packs.
• The system is already regressed because you have installed the interim fixes or the fix packs, and you then installed additional features from the Application Clients V5.0.0 CD-ROM. If this is true, you can remedy the problem by using the patcher utility to correct product history files and reinstalling the interim fixes or the fix pack. Using the patcher utility is described in the "Installing new features after applying fix packs (patch command)" article in the English version of the InfoCenter.

Preserving an existing Web services gateway configuration when installing the fix pack

The update installer installs the enterprise applications for the Web services gateway in the /installableApps directory of WebSphere Application Server Network Deployment. You then deploy the gateway enterprise applications across the cell as a separate step.

To install Fix Pack 2, complete the following steps:

Note:

• In these steps you use a utility wsgwsave.jar that is supplied in Fix Pack 2 to back up the configuration data from a Version 5 or 5.0.1 gateway.
• You use this utility after you install Fix Pack 2, and before you deploy the Version 5.0.2 gateway enterprise applications.
• This utility does not work with a Version 5.0.2 gateway. To back up a Version 5.0.2 gateway, follow the back up steps given in the product documentation article, "Backing up and restoring a gateway configuration."

1. Install Fix Pack 2 by following the instructions in the product documentation article, "Installing fixes and fix packs."
2. If your Version 5 or 5.0.1 gateway is running in a cell, remove the application server from the cell. This is because the gateway enterprise application needs to be updated with a J2EE client application, and this cannot be done when the application is running in a cell.
3. Locate the wsgwsave.jar file in the WebSphere_DeployMgr_root/WSGW/install directory (where WebSphere_DeployMgr_root is the deployment manager root directory - by default WebSphere/DeploymentManager). Copy this file to a convenient directory on the machine on which the target application server is running.
4. On the machine on which the target application server is running, use the WebSphere Application Server Application Assembly Tool (AAT) to import the wsgwsave.jar utility into the gateway application (for more information on using the AAT, see the product documentation article, "Assembling applications"). To import the wsgwsave.jar utility into the gateway application, complete the following steps:
   1. Start the AAT.
   2. From the File menu, click File > Open, then browse to the install_root/installedApps/node_name directory (where install_root is the root directory of your target application server (by default WebSphere/AppServer) and node_name is the application server node name).
   3. Select the wsgw.ear file, then open the application.
   4. From the pop-up menu for the Application Client folder, click import.
   5. Browse to the location of the wsgwsave.jar file. Select this file and click Open. When asked to confirm values, click OK.
   6. Select File > Save to update the application.
5. On the machine on which the target application server is running, use the WebSphere Application Server launchClient tool to launch the utility wsgwsave.jar and back up the configuration data from the gateway (for more information on using the launchClient tool, see the product documentation article, "Running application clients"). To back up the configuration data from the gateway, complete the following steps:
   1. From a command line, change the directory to install_root/bin.
   2. Type the following command:

      launchClient install_root/installedApps/node_name/wsgw.ear -CCjar=wsgwsave.jar location_to_write_file_to

      where location_to_write_file_to is the full path and file name under which you want the configuration file to be saved (the file name can be any valid Java filename). For example (Windows systems): launchClient C:\WebSphere\ApplicationServer\installedApps\myNode\wsgw.ear -CCjar=wsgwsave.jar C:\gatewayconfig.xml.

6. If necessary, add the target application server back into the cell.
7. Complete the installation of the Version 5.0.2 gateway by following the instructions in the product documentation article, "Web services gateway - Completing the installation." This undeploys the existing applications and deploys the Version 5.0.2 gateway enterprise applications.
8. To restore the data from your back up file, follow the restore steps in the product documentation article, "Backing up and restoring a gateway configuration."

Errors occur if you stop and restart the UDDI registry application from the administrative console and then use the user console

If you stop and restart the UDDI registry application from the administrative console, and then try to access the registry through the user console, an Error 500 - object is not an instance of a declaring class displays on the user console, and the error message SRVE0026E displays in the system log. You cannot access the UDDI registry until you restart the IBM WebSphere Application Server.

To avoid seeing this problem when you restart the UDDI registry application, perform the following steps using the IBM WebSphere Application Server administrative console:

1. Click Applications > Enterprise Applications.
2. In the list of applications, locate and click the UDDI application link.
3. Scroll down to the Related Items section and click Web Modules.
4. Click gui.war.
5. Change the Classload Mode value to PARENT_LAST (instead of PARENT_FIRST).

An UDIN2041I error might occur with the wsadmin appserversetupuddi.jacl command

The following scripting error might display when you run the wsadmin appserversetupuddi.jacl command:

UDIN2041I: Starting UDDI application. UDIN8019E: startApplication command for appname caught exception Exc. Values are: appname=UDDIRegistry, Exc=com.ibm.ws.scripting.ScriptingException: com.ibm.websphere.management.exception.ConnectorException: ADMC0009E: Failed to make the SOAP RPC call: invoke  

During installation, if you see the previous error after running the appserversetupuddi.jacl command, you can ignore the error. It is recommended that you start, or stop and restart the application server and then continue.

The Web services technology preview is not supported on WebSphere Application Server, Version 5.0.1 and Version 5.0.2

The Web services technology preview is not supported on WebSphere Application Server, Version 5.0.1 and Version 5.0.2. WebSphere Application Server, Version 5.0.2 includes Web services support that supersedes the Web services technolog preview

Accessing the Web Services for Java 2 Platform, Enterprise Edition Samples

Symptom:

You cannot locate the Web Services Samples after installing WebSphere Application Server, Version 5 Fix Pack 2.

The new and updated Samples are installed into the samples50_fp2 directory for Fix Pack 2.

Response:

To locate these Samples, inspect the contents of the install_root\samples50_fp2 directory:

• If there is a readme.html file in that directory, follow those instructions to integrate the Web services for Java 2 Platform, Enterprise Edition (J2EE) Samples into the Samples Gallery.
• If the readme.html is not present, the Samples Gallery was not installed with the original installation of WebSphere Application Server, Version 5. In this case, you can install the Web services for J2EE Samples by starting the server and using the administrative console to install the install_root\samples50_fp2\lib\WebServicesSamples\ file. To view the Web services for the J2EE Samples documentation after installation, start the server and open the following URL in your Web browser:

  http://localhost:9080/WebServicesSamples/docs/en/websvcsintro.html 

A Java API XML-based remote procedure call Simple Object Access Protocol handler is unable to access EJB container resources

Symptom:

A Java API XML-based remote procedure call (JAXRPC) Simple Object Access Protocol (SOAP) handler deployed on the server-side to an EJB-based Web service is unable to access the resources of the EJB container. A JAXRPC SOAP handler does not execute in the EJB container.

Problem:

A JAXRPC SOAP handler executes in the Java 2 Platform, Enterprise Edition (J2EE) 1.3 Web container of a router-module. The router module directs the SOAP request to the target enterprise bean. The environment of the router module container is visible to the handler, while the environment of the EJB container is not visible. This lack of visibility might cause unexpected and possibly misleading results to handlers accessing the container environment.

Response:

J2EE 1.3 does not require the execution of Web services JAXRPC SOAP handlers in an EJB container. J2EE 1.4 requires handlers to execute in the context of the target EJB container.

The messages that display are always in English regardless of the locale when the wsdeploy tool is run

Symptom:

The messages that display are always in English regardless of the locale when the wsdeploy tool is run.

Problem:

The translated messages are not available when the wsdeploy tool is run.

Response:

Consult the articles for the wsdeploy tool in the InfoCenter for the usage and message information. The information in the InfoCenter is translated.

A Web Services Description Language file containing a Java Message Service endpoint URL fails the validation in the Web Services Description Language validator inside WebSphere Studio Application Developer

Symptom:

A Web Services Description Language (WSDL) file containing a Java Message Service (JMS) endpoint URL fails the validation in the WSDL validator inside WebSphere Studio Application Developer.

Problem:

If the JMS endpoint URL contains vertical bar ("|") characters as the property delimiters within the URL string, the WSDL validator treats the WebSphere Studio Application Develope document as invalid. The following example illustrates such a URL string:

jms:/queue?destination=jms/Q1|connectionFactory=jms/QCF1|targetService=Method1

The error occurs because the WSDL validator does not treat the "|" character as a valid delimiter within the URL string.

Response:

To avoid this error, use the ampersand ("&") character as the property delimiter within the JMS URL string. For example:

jms:/queue?destination=jms/Q1&connectionFactory=jms/QCF1&targetService=Method1

The following list describes the ways in which the JMS endpoint URL string is entered into the WSDL document :

• The Java2WSDL command-line tool (through the location option) inserts the specified endpoint URL string into the resulting WSDL file. When using this method, you must specify a JMS URL that contains "&" characters for the delimiters.
• You can use the publish WSDL application to publish a WSDL file for your use. When using this application, you must use the "&" character as a delimiter when specifying the JMS URL prefix.
• You can modify the WSDL document manually. If you modify the WSDL file manually, you must use the ampersand entity reference ("&amp;") within the WSDL file. For example, the previous URL string is similar to the following example inside the WSDL file:

  jms:/queue?destination=jms/Q1&connectionFactory=jms/QCF1&targetService=Method1

Editing the HTTP basic authentication and Secure Sockets Layer configuration for the Web or EJB modules

Description:

You need to edit the HTTP basic authentication (user ID and password) and Secure Sockets Layer (SSL) configuration for the HTTP outbound request in the client security bindings of the Web services using the administrative console after you deploy the Web services application.

Response:

You can edit the HTTP basic authentication and SSL configuration for the Web services from the administrative console by performing the following steps:

1. Click Enterprise Applications > application_name.
2. Under Related Items, click Web Module or EJB Module > URI_file_name > Web Services: Client Security Bindings.
3. Once the page is opened, look for HTTP Basic Authentication and HTTP SSL Configuration to the right.
4. To configure the HTTP basic authentication, click edit and enter the user ID and password.
5. Click OK.
6. To configure the HTTP SSL configuration, click edit.
7. Select HTTP SSL Enabled.
8. Select a SSL alias for the HTTP SSL configuration.
9. Click OK.

An error in the i-link help panel for the Publish WSDL files for Web Services administrative console

Problem:

There is an error in the i-link help panel for the Publish WSDL files for Web Services administrative console.

Response:

The i-link help panel incorrectly states that the separator for the name=value pairs in a Java Message Service (JMS) URL prefix is the '|' character instead of the correct "&" character. The last paragraph in the help panel is:

Specify the JMS URL string that you would like to use for each module. Specify the entire URL, including at least the "destination" and "connectionFactory" properties, but do not include "targetService" property. The format of the JMS URL prefix is "jms:/[queue|topic]?destination=target_queue_or_topic|connectionFactory=factory_name ". For example: "jms:/queue?destination=jms/Q1|connectionFactory=jms/QCF". An actual URL that appears in a published WSDL file consists of the prefix prepended to the Web Service's "targetService". For example: "jms:/queue?destination=jms/Q1|connectionFactory=jms/QCF|targetService=StockQuote"

In this paragraph, the '|' characters used as name=value pair separators should be changed to the '&" character.

Migrating applications developed with the WebSphere Application Server, Version 5 Web services technology preview to WebSphere Application Server Version 5.0.2

Problem:

Migrating applications developed with the WebSphere Application Server, Version 5 Web services technology preview to WebSphere Application Server Version 5.0.2.

Response:

This section describes how to migrate from the Web services technology preview to WebSphere Application Server, Version 5.0.2.

You can normally reuse the Web Services Description Language (WSDL) file. If you created the WSDL file using the Java2WSDL command in the Web services technology preview and you encounter problems, regenerate the file. You must regenerate all Java classes generated by the WSDL2Java command in the technology preview. These classes fall into two categories, the development classes and the deployment classes. The development classes include the enterprise beans and exception classes generated by the WSDL2Java command. These classes are regenerated by running the wsdl2java -role develop-client (or -role develop-server) command. The deployment classes include *Stub.java, *Locator.java, *_Ser.java, *_Deser.java, and *_Helper.java classes. After you verify that no deployment class source code is included in the application EAR file, you can regenerate the deployment classes either by using the wsdeploy command, or by selecting Deploy Web Services on the application installation panels of the administrative console. Classes generated by the WSDL2Java command are identified by a comment at the top of the source file. You can reuse the original Web service client code and server implementation code. If you have any JAX-RPC handlers, rewrite the code to conform with SAAJ 1.1 (see http://java.sun.com/xml/saaj/ ). You can reuse the original webservices.xml and webservicesclient.xml deployment descriptors. Any information added to the original ibm-webservices-bnd.xml and ibm-webservicesclient-bnd.xml files need to be migrated to the new ibm-webservices-bnd.xmi and ibm-webservicesclient-bnd.xmi files.

In the Web services technology preview, all application exceptions extended IBM WebServicesFault. Now all application exceptions extend java.lang.Exception to comply with the J2EE specification.

A WebServicesFault exception is thrown by the application server run time for certain Web Services Description Language files

Symptom:

A WebServicesFault exception is thrown by the application server run time for certain Web Services Description Language (WSDL) files that defines operations with the document style and literal use and use the Simple Object Access Protocol (SOAP) header to transmit the input data.

If the WSDL files define an operation with document style and literal use and this operation maps the input to the SOAP header, the Web services run time fails to find the right operation for the target service and a WebServicesFault exception is thrown.

Response:

To solve the problem, you must change the WSDL files so that the previously noted operation does not have any input that uses the SOAP header to transmit the data.

Running Web services that use Generic classes and Web services that use Deployed Java classes on the same instance of the Web services gateway

Web services that use Generic classes and Web services that use Deployed Java classes cannot be run on the same instance of the Web service gateway, unless a further interim fix is applied. Without this fix, when a service is deployed using Generic classes the typemappings that are required by the gateway for Generic classes overwrite the default typemappings for any service that uses Deployed Java classes, then all subsequent invocations of the services that use Deployed Java classes fail. The interim fix package that solves this problem is available from the following Web site: http://www.ibm.com/software/webservers/appserv/was/support/. From the main page, click All code fixes and support tools in the Software downloads section. This takes you to the page to search for a specific download package.

Configuring the Web services gateway channels for successful back up and restore of the gateway

In the gateway, an extended channel end point address is required if the application server on which the channel is running is part of a cluster (for more information see the product documentation article, "Deploying channels to the Web services gateway"). If you want to use the gateway back up and restore features to create a gateway cluster (for more information see the InfoCenter article, "Backing up and restoring a gateway configuration"), then you must configure all the channels with extended end point addresses before you back up the gateway.

Configuring Web service security in the Web services gateway

If you change an existing security configuration for a Web service in the gateway (for more information see the InfoCenter article, "Enabling Web Services Security (WS-Security) for the gateway"), then for the changes to take effect you must restart the application server on which the gateway is running. .

Configuring ID Assertion in the Web services gateway

When you edit the service security configuration for a Web service in the gateway (for more information see the product documentation article, "Enabling Web Services Security (WS-Security) for the gateway"), you cannot select ID Assertion. You can navigate to the section Accepted identification methods, and select the ID Assertion check box, but when you click Apply Changes this change is not applied.

Session management of deployed target services

The Web services gateway does not support session management and maintenance of deployed target services using HTTP cookies. However, you can do this using Simple Object Access Protocol (SOAP) headers.

Help files are viewable only from a locally installed browser

If you access any of the IBM WebSphere Application Server tools from a remote machine, for example, the Application Assembly Tool, the remote browser cannot display the help files. You can only view the help files from a locally installed browser.

To work around this problem, close all the Netscape sessions on the remote machine and click Help. A new Netscape session starts and you can then view the Help files.

Application Assembly Tool displays unsupported type for application client resource reference

When configuring a resource reference for an application client module in the Application Assembly Tool, the Type field menu lists javax.resource.cci.ConnectionFactory as an available resource reference. This type is not supported by the J2EE application client run time. The supported types are:

• java.net.URL
• javax.mail.Session
• javax.jms.QueueConnectionFactory
• javax.jms.TopicConnectionFactory
• javax.jms.Queue
• javax.jms.Topic
• javax.sql.DataSource

The EJB application using container-managed persistence beans might fail to run with the sql syntax

Symptom:

The EJB application using container-managed persistence beans might fail to run with the sql syntax. This is an Oracle syntax error dealing with an SQL CAST operation. You can see the following exception in the system:

log java.sql.SQLException: ORA-00910:specified length too long for its datatype

Problem:

The problem is a bug in the EJBDeploy program.

Description:

An incorrect CAST operator is generated into SQL for EJB entity beans. This happens when there are multiple EJB-RDB mappings in the EJB or JAR file and one of the mappings is for DB2 and another of the mappings is for another database such as Oracle. When there are multiple mappings, the EJBDeploy tool incorrectly assumes that all mappings are for DB2 and generates incorrect sql for the Oracle case.

Response:

You can work around the problem by removing the unused mappings for the EJB or JAR file.

Running the Application Assembly Tool on UNIX platforms causes errors

A sample of the errors that display follows:

...Font specified in font.properties not found [-urw-itc 
zapfdingbats-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific]
Font specified in font.properties not found [-urw-itc 
zapfdingbats-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific]
...

The Application Assembly Tool or installer functions are not affected by these errors. These messages display in the command shell that spawned the Java GUI. You can disregard these messages.

All platforms

• Misleading scope when installing RAR file at the server level
• Embedded Java Message Service provider installation fails
• In the single server environment, the embedded Java Message Service server and IBM WebSphere Application Server run on the same single Java virtual machine
• Selecting the Java Messaging Service resources when deploying the WAR file
• Information you should know about using server-side and client-side selectors
• Component-managed authentication alias not specified
• Stopping the queue manager while running the embedded Java Messaging Service provider stops the IBM WebSphere Application Server
• Limited connection caching available for servlets
• Problems with Xerces versions that are not Java 2 Platform, Enterprise Edition compliant

Misleading scope when installing RAR file at the server level

When installing a RAR file, by clicking Resources > Resource Adapters > Install RAR, the scope you define on the Resource Adapters page has no effect on where the RAR file gets installed. You can only install RAR files at the node level.The scope on the Install RAR page determines the node to install. However, the scope you set on the resource adapters panel determines the scope of the new Resource Adapters, which you can install at the server, node, or cell level.

Embedded Java Message Service provider installation fails

It is possible for the embedded Java Message Service (JMS) provider installation to fail without any visible warning. This situation can occur as a result of the JMS provider prerequisite checker returning an error that the IBM WebSphere Application Server installation is not expecting. The IBM WebSphere Application Server installation completes, but the JMS provider is not installed.

If the JMS installation fails, look for details in the mq_prereq.log file in the /tmp directory and in the create_mq.log and mq_install.log files in the install_root/log directory. When you have corrected the situation, install the embedded JMS provider separately by clicking Custom installation then selecting either one or both of the following options, as required: Embedded Messaging Server and Embedded Messaging Client. For more information about installing the embedded JMS provider, see the InfoCenter article, "Installing WebSphere embedded messaging as the JMS provider."

In the single server environment, the embedded Java Message Service server and IBM WebSphere Application Server run on the same single Java virtual machine

The embedded Java Message Service (JMS) server and the IBM WebSphere Application Server run on the same single Java virtual machine. Due to this architecture, if the MQ process (such as amq*.exe - not JMS process but MQ native process) dies and restarts while the JMS server is running, you must restart the IBM WebSphere Application Server (ordinarily named server1) manually. This shutdown also can affect other installed applications.

In the distributed server environment, the JMS server and the application server run in separate processes. Therefore, the JMS server is not required to restart the application server.

To work around this problem, restart the application server (server1).

Selecting the Java Messaging Service resources when deploying the WAR file

When you deploy a WAR file and select the Java Message Service (JMS) resources that you defined, you receive a warning message without selecting the JMS resources.

Information you should know about using server-side and client-side selectors

The default behavior for the internal JMS broker is to use server-side selectors. The default behavior for external brokers is to use client-side selectors. The reason for the latter is that not all brokers support server-side filtering. Those that do, are not all JMS compliant in their implementation process.

Component-managed authentication alias not specified

When using Java Message Service (JMS), informational messages similar to the following can occur:

[10/31/02 9:13:20:438 EST] 6a55451c ConnectionFac I J2CA0107I: Component-managed authentication

If the named connection factory ends in JMSManagedConnection@nnnn, where nnnn is a multi-digit number, the informational message can be ignored. A connection factory with this type of name is created internally by the JMS server and does not require a component-managed authentication alias.

Stopping the queue manager while running the embedded Java Messaging Service provider stops the IBM WebSphere Application Server

When you run the embedded Java Message Service (JMS) provider and the queue manager stops, IBM WebSphere Application Server is also stopped.

To recover the queue manager and IBM WebSphere Application Server, you must start the application server.

Limited connection caching available for servlets

Caching of connection handles across servlet methods is limited to Java Database Connectivity (JDBC) and Java Message Service (JMS) resources. Other non-relational resources, such as Customer Information Control System (CICS) or IMS, currently cannot have their connection handles cached in a servlet. This limitation only applies to single-threaded servlets since multithreaded servlets do not allow caching of connection handles.

To work around this problem, you need to get, use, and close the connection handle within each method invocation.

Problems with Xerces versions that are not Java 2 Platform, Enterprise Edition compliant

Programs containing the Xerces parser routine that work on IBM WebSphere Application Server, Version 4.0.x might not work on IBM WebSphere Application Server, Version 5.

Versions of Xerces prior to 2.0.0, including the versions shipped with IBM WebSphere Application Server, Version 4.0.x, were not J2EE1.3 compliant. To meet J2EE1.3 certification constraints (DOM2/SAX2/JAXP1.1 (and no higher)), IBM WebSphere Application Server, Version 5 requires XML4J4.0.0 (Xerces 2.0 bug fixes).

In Xerces versions prior to 2.0.0 and Xalan versions prior to 2.2, the DOM, SAX, and JAXP APIs were bundled inside of the xerces.jar and xalan.jar files. In the most recent versions, these non-Apache XML APIs have moved into a separate JAR file in the XML common apache project. These common XML APIs are required by the specifications and contained within the IBM WebSphere Application Server, Version 5 j2ee.jar file.

The cause of the problem is that the class loader behavior mixes the classes that are required by J2EE1.3 with those of the older Xerces implementation.

To work around this problem, use the version that ships with IBM WebSphere Application Server, Version 5.

Uninstalling fix pack fails when External MQ already installed

Symptom:

Consider the scenario on Solaris, where you have installed WebSphere MQ with the CSDs needed for WebSphere Application Server, then install WebSphere Application Server, and one WebSphere Application Server fix pack (for example, WAS 5.0.1 or WAS 5.0.2). If you try to uninstall the fix pack release to return to the GA level of WebSphere Application Server, the uninstall process fails and the following messages appear in the /opt/WebSphere/AppServer/logs/update/..._was50_fpn_solaris_uninstall.log:

PTF Results: ========================================================= Time Stamp (End)      
: dateTtime PTF Result            : failed PTF Result Message: 
========================================================= WUPD0243E: Fix pack uninstall failure: 
The update for component was50_fpn_solaris for fix pack external.mq could not be uninstalled. 
========================================================= 

In addition, the following appears in the date_time_was50_fpn_solaris_external.mq_uninstall.log:

wmservice: date time =============================================================================================
wmservice: date time Date: Tue Jul 1 16:18:10 BST 2003 wmservice: date time 
================================================================================================== 
wmservice: date time Hostname: slipstream wmservice: date time Operating System: SunOS wmservice: date time User: uid=0
(root) gid=1(other) wmservice: date time Command line is: /opt/WebSphere/AppServer/properties/version/backup/external.mq/pt
fs/was50_fpn_solaris/components/external.mq/CSD/wmservice uninstall /opt/WebSphere/AppServer/logs/update/date_time_was50_fp
2_solaris_external.mq_uninstall.log wmservice: date time Function is uninstall wmservice: date time Get_ver_rel mqm.java wm
service: date time Checking for installed product "mqm", class "java" wmservice: date time Check for csd levels expr: syntax
 error wmservice: date time ... mqm.java 5.3.0.2.4 wmservice: date time Uninstall_service .... pkgrm: ERROR: no package ass
ociated with <mqm_upd02> wmservice: date time return code 1 from pkgrm wmservice: date time ... Uninstall_servi
ce returns 1 wmservice: date time Return code 1 from Uninstall_wsm wmservice: date time Exiting - return code 1 wmservice: 
date time ============================================================

The last step of the WebSphere Application Server fix pack uninstallation fails because the external.mq component cannot be uninstalled.

Response

To fix this problem, delete the mqVer.properties file in the /opt/WebSphere/AppServer/properties/version/backup/external.mq/ptfs/was50_fpn_solaris/components/external.mq/directory, where was50_fpn_solaris indicates the fix pack release (for example, was50_fp2_solaris for Fix Pack 2). Then retry the uninstall of the fix pack release (for example, Fix Pack 1 or Fix Pack 1).

Recommended approach to installing WebSphere Application Server on top of WebSphere MQ

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:

1. Ensure that all the WebSphere MQ features required by the WebSphere Application Server embedded messaging are installed:

    - 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

2. Ensure that WebSphere MQ v5.3 has been upgraded to the appropriate prerequisite CSD level:

   - CSD1 for WebSphere Application Server v5.0
   - CSD3 for WebSphere Application Server v5.0.1
   - CSD4 for WebSphere Application Server v5.0.2

3. Install the WebSphere Application Server V5 GM release.
4. Install any appropriate WebSphere Application Server fix packs.

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, you should download and apply the WebSphere MQ V5.3 CSD4 before upgrading your WebSphere Application Server to V5.0.2). This approach helps to avoid failures in uninstalling WebSphere Application Server fix packs.

On Linux/Intel/390/PPC (SLES8 and United Linux V1.0) platforms, logging in appropriately to pick up secondary groups for root

Symptom:

On Linux/Intel/390/PPC (SLES8 and United Linux v1.0), when installing WebSphere Application Server, the following entries appear in the SystemOut.log file:

[date time CDT] 60cf2faf JMSRegistrati A MSGS0601I: WebSphere Embedded Messaging has not been installed
[date time CDT] 60cf2faf JMSEmbeddedPr A MSGS0050I: Starting the Queue Manager
[date time CDT] 60cf2faf JMSEmbeddedPr E MSGS0058E: Unable to start the JMS Server as WebSphere Embedded Messaging has not been installed
[date time CDT] 60cf2faf JMSService    E MSGS0001E: Starting the JMS Server failed with exception: java.lang.Exception: MSGS0058E: Unable to start the JMS Server as WebSphere Embedded Messaging has not been installed

Also, the following associated messages are added to the mq_install.log file:

wmsetup: date time Checking if user "root" is in group "mqm"
wmsetup: date time
wmsetup: date time ERROR: Group "mqm" exists, id "root" is defined to the group but does not
wmsetup: date time have the group in its current set of effective groups.
wmsetup: date time Current group membership is :
wmsetup: date time uid=0(root) gid=0(system) groups=2(bin)
wmsetup: date time You may need to login.
wmsetup: date time
wmsetup: date time ... RC 4 from Check_root
wmsetup: date time ERROR: User "root" not in group "mqm" 
wmsetup: date time Check_root mqbrkrs
wmsetup: date time Checking for group "mqbrkrs" ...
wmsetup: date time lsgroup returned "mqbrkrs id=203 admin=false users=root adms=root registry=files " RC=0
wmsetup: date time Checking if user "root" is in group "mqbrkrs"
wmsetup: date time
wmsetup: date time ERROR: Group "mqbrkrs" exists, id "root" is defined to the group but does not
wmsetup: date time have the group in its current set of effective groups.
wmsetup: date time Current group membership is :
wmsetup: date time uid=0(root) gid=0(system) groups=2(bin)
wmsetup: date time You may need to login.
wmsetup: date time
wmsetup: date time ... RC 4 from Check_root
wmsetup: date time ERROR: User "root" not in group "mqbrkrs"

Response:

To prevent this problem, use ssh instead of telnet to log in.

As a workaround, after logging in and experiencing this problem, run the following command:

su -

On Linux/Intel (RedHat V8) platforms, ensure that the required utilities and compatibility libraries are installed before installing WebSphere Application Server

Symptom:

On Linux/Intel (RedHat V8), during the Application Server startup process, the following entries appear in the SystemOut.log file:

[date time EST] 1cda953b JMSEmbeddedPr A MSGS0052I: Starting the Broker
[date time EST] 1cda953b BrokerManager E MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
[date time EST] 1cda953b JMSService    E MSGS0001E: Starting the JMS Server failed with exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085

The following associated messages are added to the mq_install.log file:

which: no uudecode in (/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin)
  The program uudecode was not found on this system.  This will not prevent
  the installation, however you should run the command "amqiclen -x"
  after the installation has completed, before queue managers are started.

Also, the createMQ log shows the following:

 Issuing: env wempsdeletebroker WAS_redhat801_jmsserver -w
  wempsdeletebroker: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory
  rc=127
  Issuing: env wempscreatebroker WAS_redhat801_jmsserver -i dummy -a dummy -q WAS_redhat801_jmsserver -n "" -u "" -p "" -b -j
  wempscreatebroker: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory
  rc=127
  Issuing: env wempsservice WAS_redhat801_jmsserver -r BrokerUUID=FFFFFFFF-0000-0000-0000-000000000000
  wempsservice: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory
  rc=127

Response:

To prevent this problem, ensure that the required utility package (which includes uuencode/uudecode) and the libstdc++ compatability libraries are installed; for example, RH8.0/RPMS/shareutils. (The RPMS are on the Linux distribution CDs.) The exact name and version number of the package depends on the Linux distribution:

On Linux platforms, embedded messaging broker does not shut down due to libstdc++ problem

Symptom:

On SuSE SLES8 and United Linux V1.0, when shutting down WebSphere Application Server, the last entry in the SystemOut.log file is:

[date time CDT] 1a87ba29 JMSEmbeddedPr A MSGS0054I: Stopping the Broke

Also, a Java core file :javacore29282.1054144121.txtgets created at approximately the same time [date at timeTIFILENAME] as the embedded messaging broker tries to shutdown.

Problem:

On SuSE SLES8 or United Linux V1.0, when shutting down WebSphere Application Server, the embedded messaging broker does not shutdown properly, because of a libstdc++ problem.

Response:

You should upgrade the operating system to the latest Service Pack, which includes the fix for the libstdc++ problem.

On Linux/Intel (RedHat V8) platforms, installation of WebSphere Application Server hangs during the embedded messaging installation stage

Symptom:

On Linux (RedHat v8), the installation of WebSphere Application Server hangs during the embedded messaging installation stage. The last line of the mq_install.log is:

wmsetup: date time Installing MQSeriesClient-5.3.0-1.i386.rpm MQSeriesMsg_Zh_CN-5.3.0-1.i386.rpm 
         MQSeriesMsg_Zh_TW-5.3.0-1.i386.rpm MQSeriesMsg_de-5.3.0-1.i386.rpm MQSeriesMsg_es-5.3.0-1.i386.rpm 
         MQSeriesMsg_fr-5.3.0-1.i386.rpm MQSeriesMsg_it-5.3.0-1.i386.rpm MQSeriesMsg_ja-5.3.0-1.i386.rpm 
         MQSeriesMsg_ko-5.3.0-1.i386.rpm MQSeriesMsg_pt-5.3.0-1.i386.rpm MQSeriesRuntime-5.3.0-1.i386.rpm 
         MQSeriesSDK-5.3.0-1.i386.rpm MQSeriesJava-5.3.0-1.i386.rpm MQSeriesServer-5.3.0-1.i386.rpm:

The last line of the master install log (/tmp/log.txt) is:

(date time), Setup.product.install, com.ibm.wizard.platform.linux.LinuxProductServiceImpl, msg1,installing Exec Action From Directory (mqUnixInstallAction

Problem:

RPM lock files exist that prevent the product installation from continuing.

Response:

For information about solving this problem, see the bugzilla report at http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=74726

Installing WebSphere Application Server, Version 5.0.2 Network Deployment on top of WebSphere Application Server, Version 5.0.1 Network Deployment fails on Linux/Intel

Symptom:

The installation of WebSphere Application Server Network Deployment, Version 5.0.2 on top of WebSphere Application Server Network Deployment, Version 5.0.1 fails on the Linux/Intel platform. The following message displays in the /opt/WebSphere/DeploymentManager/logs/update/20030703_152306_was50_nd_fp2_linux_selective-install.log file.

PTF Results:
=========================================================
Time Stamp (End)      : 2003-07-03T15:23:09Z
PTF Result            : failed
PTF Result Message:
=========================================================
WUPD0218E: Fix pack installation failure: The component external.mq failed to install.

The associated errors in the /opt/WebSphere/DeploymentManager/logs/update/20030703_152306_was50_nd_fp2_linux_external.mq_install.log file are:

wmservice: 03Jul03 15:23:08 Installing MQSeriesServer-U486878-5.3.0-4.i386.rpm MQSeriesJava-U486878-5.3.0-4.i386.rpm MQSeriesSDK-U486878-5.3.0-4.i386.rpm MQSeriesRuntime-U486878-5.3.0-4.i386.rpm MQSeriesClient-U486878-5.3.0-4.i386.rpm
error: failed dependencies:
        MQSeriesServer = 5.3.0 is needed by MQSeriesServer-U486878-5.3.0-4
        MQSeriesSDK = 5.3.0 is needed by MQSeriesSDK-U486878-5.3.0-4
        MQSeriesRuntime = 5.3.0 is needed by MQSeriesRuntime-U486878-5.3.0-4
        MQSeriesClient = 5.3.0 is needed by MQSeriesClient-U486878-5.3.0-4
wmservice: 03Jul03 15:23:08 ERROR: Return code 5 from rpm -i MQSeriesClient-U*-5.3.0-4.i386.rpm MQSeriesMsg_Zh_CN-U*-5.3.0-4.i386.rpm MQSeriesMsg_Zh_TW-U*-5.3.0-4.i386.rpm MQSeriesMsg_de-U*-5.3.0-4.i386.rpm MQSeriesMsg_es-U*-5.3.0.4.i386.rpm MQSeriesMsg_fr-U*-5.3.0-4.i386.rpm MQSeriesMsg_it-U*-5.3.0-4.i386.rpm MQSeriesMsg_ja-U*-5.3.0-4.i386.rpm MQSeriesMsg_ko-U*-5.3.0-4.i386.rpm MQSeriesMsg_pt-U*-5.3.0-4.i386.rpm MQSeriesRuntime-U*-5.3.0-4.i386.rpm MQSeriesSDK-U*-5.3.0-4.i386.rpm MQSeriesJava-U*-5.3.0-4.i386.rpm MQSeriesServer-U*-5.3.0-4.i386.rpm
wmservice: 03Jul03 15:23:08 ERROR: installation of mqm CSD failed - rolling back
wmservice: 03Jul03 15:23:08 Rollback entered - error code 19

Response:

If you require the Embedded Messaging component, uninstall WebSphere Application Server Network Deployment, Version 5.0.1 before installing WebSphere Application Server Network Deployment , Version 5.0.2 on Linux/Intel.

You can ignore some error messages when installing WebSphere Application Server with embedded messaging from the CD-ROM

On HP-UX, when installing WebSphere Application Server with embedded messaging from the CD-ROM, the following warning message is issued despite successful installation:

MQSERIES.MQM-CL-HPUX: A test command parameter is not valid." and "* 
"svthp9:/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." on mq_install.log.  

You can ignore this warning message, because the problem does not affect the successful installation of WebSphere Application Server with embedded messaging.

Installing WebSphere Application Server Network Deployment before WebSphere Application Server (base) creates an exception in SystemOut.log

On HP-UX platforms, if you install WebSphere Application Server Network Deployment first, then later install WebSphere Application Server (base), the following exception is written to the SystemOut logfile when you attempt to start WebSphere Application Server:

[date time CDT]   25491d JMSService    E MSGS0001E: Starting the JMSServer failed with 
exception: java.lang.Exception: MSGS0101E: Start Queue Manager command failed with exit code: 71

In this specific scenario, the/var/mqm/mqs.ini directory needed to start the queue manager is missing.

Generally, you should install WebSphere Application Server (base) before installing WebSphere Application Server Network Deployment on the same host.

As a workaround, after completing the installation, and before starting the WebSphere Application server, run the following command:

ln -s /opt/mqm/lib/nls/C/amq.cat /usr/lib/nls/C/amq.cat

Now, copy the mqs.ini file from the /opt/mqm/samp directory to the /var/mqm directory

Finally, rerun the createMQ script:

./wasHome/bin createmq.sh <wasHome><cellName><nodeName><serverName>

where <wasHome> is the installation directory (that defaults to /opt/WebSphere/AppServer).

If you are not sure about your cellName, nodeName, and serverName, check the first line in the createMQ logfile that can be located in the wasHome/logs directory. The first line identifies the wasHome, cellName, nodeName, and serverName parameters passed to the script.

Uninstalling WebSphere Application Server Network Deployment does not remove the WebSphere MQ Java Client

Symptom:

On UNIX platforms, when uninstalling WebSphere Application Server Network Deployment, the following messages appear in the mq_uninstall.log file:

wmsetup: date time ==================================================================================================
wmsetup: date time Date: Tue Jun 24 12:17:58 PDT 2003
wmsetup: date time ==================================================================================================
wmsetup: date time Hostname: alinppc04
wmsetup: date time Operating System: Linux
wmsetup: date time User: uid=0(root) gid=0(root) groups=0(root),64(pkcs11),500(mqm),501(mqbrkrs)
wmsetup: date time Command line is: /opt/WebSphere/DeploymentManager/_uninst/mq/wmsetup uninstall /opt/WebSphere/DeploymentManager/mq_uninstall.log
wmsetup: date time Function is uninstall
wmsetup: date time Uninstall_wsm
wmsetup: date time Checking for installed wemps-runtime ...
wmsetup: date time package wemps-runtime is not installed
wmsetup: date time WebSphere Embedded Messaging not installed - no action required
wmsetup: date time Checking for installed MQSeriesRuntime ...
wmsetup: date time package MQSeriesRuntime is not installed
wmsetup: date time Return code 0 from Uninstall_wsm
wmsetup: date time Exiting - return code 0
wmsetup: date time ============================================================

Response:

To resolve this problem, manually uninstall the embedded messaging components by following the instructions in the WebSphere Application Server information center, under the topic, "Uninstalling WebSphere Application Server.

Uninstalling WebSphere Application Server, without first removing any fix packs, does not remove the embedded messaging components

Symptom:

After apparently uninstalling WebSphere Application Server successfully, some embedded messaging packages still exist.

Response:

To fix this problem, manually uninstall the embedded messaging components by following the instructions in the WebSphere Application Server InfoCenter, under the topic, "Uninstalling WebSphere Application Server."

Uninstalling a WebSphere Application Server fix pack fails because the external.mq component cannot be uninstalled

Symptom:

On Solaris Operating Environment, consider the scenario where you:

1. Install WebSphere Application Server v5.0 (base or Network Deployment).
2. Install the WAS v5.0.1 fix pack release.
3. Install the WAS v5.0.2 fix pack release.
4. Uninstall the WAS v5.0.2 fix pack release (to return to the WAS v5.0.1 release).

The last step fails and the following messages appear in the /opt/WebSphere/AppServer/logs/update/date_time_was50_fp2_solaris_uninstall.log directory:

Results:
=========================================================
Time Stamp (End)      : dateTtime
PTF Component Result  : failed
PTF Component Result Message:
=========================================================
WUPD0246E: Fix pack update failure: An exception occurred while preprocessing the content of fix pack was50_fp2_solaris, component external.mq
=========================================================

Also, the following appears in the date_time_was50_fp2_solaris_external.mq_uninstall.log directory :

wmservice: date time ==================================================================================================
wmservice: date time Date: Tue Jul 1 16:18:10 BST 2003
wmservice: date time ==================================================================================================
wmservice: date time Hostname: slipstream
wmservice: date time Operating System: SunOS
wmservice: date time User: uid=0(root) gid=1(other)
wmservice: date time Command line is: /opt/WebSphere/AppServer/properties/version/backup/external.mq/ptfs/was50_fp2_solaris/components/external.mq/CSD/wmservice uninstall /opt/WebSphere/AppServer/logs/update/date_time_was50_fp2_solaris_external.mq_uninstall.log
wmservice: date time Function is uninstall
wmservice: date time Get_ver_rel mqm.java
wmservice: date time Checking for installed product "mqm", class "java"
wmservice: date time Check for csd levels
expr: syntax error
wmservice: date time ... mqm.java 5.3.0.
wmservice: date time uninstall of CSD not possible, current level is 5.3.0.
wmservice: date time Exiting - return code 23

Problem:

The last step of the WebSphere Application Server fix pack uninstall fails because the external.mq component cannot be uninstalled.

Response:

To fix this problem, complete the following steps:

1. Delete the mqVer.properties file in the /opt/WebSphere/AppServer/properties/version/backup/external.mq/ptfs/was50_fp2_solaris/components/external.mq/ directory.
2. Remove the upgrade that was applied to the external.mq component by running the following command as root:

   pkgrm mqm-upd04 
   
   Reply y[es] to all prompts.

   Note: Do not remove mqm-upd04 if you have installed IBM WebSphere MQ as a separate product.

3. Retry the uninstallationl of Fix Pack 2.

On Windows 2003 Server, WebSphere Embedded Messaging Publish and Subscribe Edition does not uninstall

On Windows 2003 Server, after using Add and Remove Programs to uninstall WebSphere Application Server, if you close and then reopen Add and Remove Programs, you still see an entry for WebSphere Embedded Messaging Publish and Subscribe Edition (WEMPS). If you then try use Add and Remove Programs to remove WEMPS, you get a notice for Fatal Error during installation.

On Windows 2003 Server, after using Add and Remove Programs to uninstall WebSphere Application Server, the WEMPS product is sometimes not removed.

To prevent this problem, try using Add and Remove Programs to uninstall WEMPS before uninstalling WebSphere Application Server. As a workaround, manually remove the registries of Windows 2003 Server for WEMPS.

To manually remove WEMPS, do the following:

1. Go to www.microsoft.com .
2. Click Downloads in the left panel.
3. Type Windows Installer Cleanup Utility under Keywords (optional) and click Go.
4. Follow the instructions to install the msicuu.exe program.
5. Click Start > Run in your desktop.
6. Select the product IBM WebSphere EMPS and click Remove.
7. Remove the following registry key:

   HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphereEmbeddedMessagingPublishAndSubscribe.

8. Delete the WEMPS directory, by default C:\Program Files\IBM WebSphere EMPS, and all its contents.

For more information about manually uninstalling messaging components, see the InfoCenter article, "Manually uninstalling on Windows platforms." You can find this topic from the navigation panel by All topics by Feature > Getting started > Uninstalling WebSphere Application Server > Manually uninstalling on Windows.

• Databases-DB2
• Databases-IBM Cloudscape
• Databases-Microsoft SQL Server
• Databases-Oracle

Databases-DB2

• No CLOB data is inserted into the database when you use the DB2 UDB V7.2 FP7 client to connect to a DB2 on the z/OS database
• Upgrading to DB2 V8.1 to avoid a memory leak during the stress run using DB2 V7.2 on Windows 2000 platforms
• An error is thrown if you use the ws_ant command to perform the database customization for Structured Query Language in Java on HP platforms
• Enabling batchUpdate when running WebSphere Application Server with the DB2 Legacy CLI-based JDBC driver is ignored by the run time
• Known limitations when you connect a DB2 8.1 client to a back level server using a DB2 XA data source
• The WebSphere Application Server Java virtual machine crashes after you execute the force application command in the DB2 command line
• Upgrading DB2 V8.1 FP2 or a later version to avoid receiving an exception when the Java 2 security is enabled

No CLOB data is inserted into the database when you use the DB2 UDB V7.2 FP7 client to connect to a DB2 on the z/OS database

Symptom:

No CLOB data is inserted into the database when using the DB2 UDB V7.2 FP7 client to connect to a DB2 on z/OS database.

Problem:

This problem happens because of an error in the DB2 UDB Connect code. Instead of inserting the CLOB data into the column, the data inserted is an empty string. The problem is fixed in DB2 UDB V7.2 FP8 or FP9. It is also fixed in DB2 UDB V8.1.

Response:

Update to the correct version of DB2 UDB FP to resolve this problem.

Upgrading to DB2 V8.1 to avoid a memory leak during the stress run using DB2 V7.2 on Windows 2000 platforms

You can upgrade to DB2 V8.1 to avoid a memory leak during the stress runs when you use DB2 V7.2 on Windows 2000 platforms.

An error is thrown if you use the ws_ant command to perform the database customization for Structured Query Language in Java on HP platforms

Symptom:

If you use the ws_ant command to perform the database customization for Structured Query Language in Java (SQLJ) on HP platforms, you can receive an error similar to the following:

[java] [ibm][db2][jcc][sqlj] 
[java] [ibm][db2][jcc][sqlj] Begin Customization
[java] [ibm][db2][jcc][sqlj] encoding not supported!!

Problem:

The cause of this error might be that your databases were created using the HP default character set. The Java Common Client (JCC) driver depends on IBM Software Development Kit to perform the codepage conversions. However, the HP default codepage is not supported by the IBM Software Development Kit shipped with WebSphere Application Server.

Response:

Set your LANG to the ISO locale before creating the databases. It should be similar to the following:

export LANG=en_US.iso88591 

Refer to the DB2 Tech Notes at http://www-3.ibm.com/software/data/db2/udb/ad/v8/bldg/t0004877.htm for details.

Enabling batchUpdate when running WebSphere Application Server with the DB2 Legacy CLI-based JDBC driver is ignored by the run time

Enabling batchUpdate when running WebSphere Application Server with the DB2 Legacy CLI-based JDBC driver is ignored by the WebSphere Application Server run time due to a problem in DB2 which can cause data integrity problems.

If you want to use batchUpdate for WebSphere Application Server, Version 5.0.2, run WebSphere Application Server with the DB2 Universal JDBC driver instead of the DB2 Legacy CLI-based JDBC driver.

Known limitations when you connect a DB2 8.1 client to a back level server using a DB2 XA data source

Problem:

Limitations exist when you connect a DB2 8.1 client to a back level server, for example, DB2 7.2 FP8, using a DB2 XA data source:

• If there is no fix pack installed on the client, testing the connection for the data source crashes the application server with no error log if the connection is tested from the administrative console. If it is tested from the wsadmin tool at the command prompt, you can receive the following exception:

    wsadmin>$AdminControl testConnection 
      TradeDataSource(cells/DefaultNOde/nodes/Def
      aultNode:resources.xml#DataSource_1056390840594)
      WASX7015E: Exception running command: "$AdminControl testConnection 
      TradeDataSource(cells/DefaultNOde/nodes/DefaultNode:resources.
      xml#DataSource_1056390840594)"
      ; exception information:
      com.ibm.websphere.management.exception.ConnectorNotAvailableException
      org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client;     
      msg=Connection reset by peer: socket closed;
      targetException=java.net.SocketsException:
      Connection reset by peer: socket closed]
  

• If you install Fix Pack 2 on a DB2 8.1 client, the application server does not stop, but returns the following error:

    389b0a5 DataSourceCon E DSRA8040I: Failed to connect to the DataSource. 
      Encountered : java.lang.Exception: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI 
      Driver] SQL30070N "0x1055" Command is not supported. SQLSTATE=58014 
      at com.ibm.ws.rsadapter.DSConfigurationHelper.testConnectionForGUI(
      DSConfigurationHelper.java:1786)
      at java.lang.reflect.Method.invoke(Native Method)
      at com.ibm.ws.management.DataSourceConfigHelperMBean.testConnectionToData
      Source2(DataSourceConfigHelperMBean.java:511)
  

Response:

Upgrade the DB2 server level to the same level as the DB2 client.

Consult the document located at http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/v8infocenter.d2w/report?target=mainFrame&fn=r0010969.htm . The document is under the section XA-compliant transaction managers.

The WebSphere Application Server Java virtual machine crashes after you execute the force application command in the DB2 command line

Symptom:

The WebSphere Application Server Java virtual machine (JVM) crashes when you execute force application in DB2 UDB Server.

Problem:

When you use DB2 XA data source in WebSphere Application Server with DB2 UDB Server, the WebSphere Application Server JVM crashes after you execute the force application command in the DB2 command line.

If you use the DB2 Legacy CLI-based JDBC Driver Provider (XA), you can see the WebSphere Application Server JVM crash as soon as you execute the force application command. If you use the DB2 Universal JDBC Driver Provider (XA), you might or might not see the WebSphere Application Server JVM crash right after executing the force application command. However, you might see the WebSphere Application Server JVM crash later.

This problem has been reported to DB2. The APAR number is JR18535.

Upgrading DB2 V8.1 FP2 or a later version to avoid receiving an exception when the Java 2 security is enabled

Problem:

If you enable Java 2 security in WebSphere Application Server and try to use the DB2 Universal JDBC provider to connect to DB2 V8.1 FP1 or an older version, a java.security.AccessControlException exception similar to the following is thrown from the DB2 Java Combined Client (JCC) driver.

java.security.AccessControlException: access denied (java.lang.RuntimePermission 
accessClassInPackage.sun.io)
       at java.security.AccessControlContext.checkPermission(AccessControlContext.java(Comp
iled Code))
       at java.security.AccessController.checkPermission(AccessController.java(Compiled 
Code))
       at java.lang.SecurityManager.checkPermission(SecurityManager.java(Compiled Code))
       at com.ibm.ws.security.core.SecurityManager.checkPermission(SecurityManager.java(Com
piled Code))
       at java.lang.SecurityManager.checkPackageAccess(SecurityManager.java(Compiled 
Code))
       at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java(Compiled Code))
       at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
       at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
       at com.ibm.db2.jcc.c.o.a(o.java:153)
       at com.ibm.db2.jcc.a.d.a(d.java:1069)
       at com.ibm.db2.jcc.a.be.a(be.java:1549)
       at com.ibm.db2.jcc.a.be.m(be.java:513)
       at com.ibm.db2.jcc.a.be.i(be.java:217)
       at com.ibm.db2.jcc.a.be.c(be.java:54)
       at com.ibm.db2.jcc.a.s.c(s.java:53)
       at com.ibm.db2.jcc.a.bq.h(bq.java:118)
       at com.ibm.db2.jcc.c.cf.i(cf.java:893)
       at com.ibm.db2.jcc.c.cg.a(cg.java:1540)
       at com.ibm.db2.jcc.c.cg.executeQuery(cg.java:312)

Problem:

This problem is due to the fact that the DB2 JCC driver does not have a doPrivileged call when it tries to load some classes.

Response:

Upgrade your DB2 server to DB2 V8.1 FP2 or a later version. If you cannot upgrade your DB2 server, grant the permission, java.lang.RuntimePermission "accessClassInPackage.sun.io", to your applications. However, the second solution is NOT recommended.

Databases-IBM Cloudscape

• A NullPointerException occurs when you run WebSphere Application Server against Cloudscape (Version 5 and Version 5.1) and use callable statements
• Cannot see the descriptive error messages when running WebSphere Application Server, Version 5.0.2 against the Cloudscape Network Server or the DB2 universal driver
• Setting the driverType data source custom property to 4 when you run WebSphere Application Server, Version 5.0.2 with Cloudscape using the Network Server framework
• Cloudscape Version 5.0.x is deprecated in WebSphere Application Server, Version 5.0.2
• Information about how to uninstall Cloudscape Version 5.1.x
• The administrative console displays DB2 settings instead of Cloudscape when you create a new Cloudscape JDBC Provider Network Server using the universal JDBC driver provider
• Cloudscape throws an exception when you access the result set after the transaction is committed
• Adding quotes to the installCloudscape51.bat or installCloudscape51.sh file around the if the install_root path includes spaces

A NullPointerException occurs when you run WebSphere Application Server against Cloudscape (Version 5 and Version 5.1) and use callable statements

Symptom:

When running WebSphere Application Server against Cloudscape Version 5 and Version 5.1 and using callable statements, you might receive the following NullPointerException (message text in English only):

Unexpected exception ERROR 38000: The exception 'java.lang.NullPointerException' was thrown while evaluating an expression, possible causes: not calling registerOutputParameter and calling setNull on BIT VARYING output parameter.
       at com.ibm.db2j.protocol.Database.Errors.StandardException.newException(StandardException.java:386)
       at com.ibm.db2j.protocol.Database.Errors.StandardException.unexpectedUserException(StandardException.java:567)
       at com.ibm.db2j.impl.BasicServices.ClassManager.Reflect.ReflectMethod.invoke(ReflectMethod.java:53)
       at com.ibm.db2j.impl.Database.Language.Execution.Generic.CallStatementResultSet.open(CallStatementResultSet.java:75)
       at com.ibm.db2j.impl.Database.Language.Interface.Generic.GenericPreparedStatement.execute(GenericPreparedStatement.java:351)

Problem:

This is a rare case and is usually an application error that is caused by the application not calling registerOutputParameter but calling setNull on the Bit Varying type parameter.

Response:

If you encounter this problem and use callableStatements, ensure that you call the registerOutputParameter Method.

Cannot see the descriptive error messages when running WebSphere Application Server, Version 5.0.2 against the Cloudscape Network Server or the DB2 universal driver

When running WebSphere Application Server, Version 5.0.2 against the Cloudscape Network Server or the DB2 universal driver, you cannot see the descriptive error messages from the database unless the retrieveMessagesFromServerOnGetMessage data source custom property is set to true. By default, the full message text is not returned to the client when a server-side error occurs. This property is disabled by default. See the DB2 release notes for more information on this.

Setting the driverType data source custom property to 4 when you run WebSphere Application Server, Version 5.0.2 with Cloudscape using the Network Server framework

Symptom:

When running WebSphere Application Server, Version 5.0.2 with Cloudscape using the Network Server framework, you can receive the following exception if you either forget to set the driverType data source custom property or set it to 2:

com.ibm..db2.jcc.b.SQLException: Unexpected throwable caught java.lang.UnsatisfiedLinkError:  DBConnect

Response:

To avoid receiving the exception, set the driverType data source custom property to 4.

Consult with InfoCenter articles for more information.

Cloudscape Version 5.0.x is deprecated in WebSphere Application Server, Version 5.0.2

Cloudscape Version 5.0.x is deprecated in WebSphere Application Server, Version 5.0.2 and will not be supported or shipped with any future releases of WebSphere Application Server.

Information about how to uninstall Cloudscape Version 5.1.x

You can issue the java -jar cloudscapeUninstall.jar command to unistall Cloudscape Version 5.1.x if going back to Cloudscape Version 5.0.x after installing Cloudscape Version 5.1.x. You can find the cloudscapeUninstall.jar file in the install_root/cloudscape51/Uninstaller, and the file is only created after installing Cloudscape Version 5.1.x.

See the WebSphere Application Server InfoCenter for the information on how to install Cloudscape Versoin 5.1. You need to be aware of the fact that after migrating your database to run with the new Cloudscape (using upgrade=true connectionAttributes) you can no longer run it with Cloudscape Version 5.0.

The administrative console displays DB2 settings instead of Cloudscape when you create a new Cloudscape JDBC Provider Network Server using the universal JDBC driver provider

Problem:

When creating a new Cloudscape JDBC Provider Network Server using the universal JDBC driver provider through the administrative console in WebSphere Application Server, Version 5.0.2, you need to be aware of the problem that the administrative console fills in the DB2 universal data sources settings by default instead of the Cloudscape Network Server ones. Those settings include:

1. the DataStoreHelper class
2. the data source custom properties

The incorrect settings do not include the implementation class, which is just like the DB2 Universal one.

Response:

If you want to create the Cloudscape JDBC Provider Network Server using the universal JDBC driver provider, you are required to manually modify the entries in the administrative console as follows:

1. You should change the DataStoreHelper class to:

   com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper

2. You only need the following custom properties:

   - driverType       4 (type 4 driver is the only valid value for Network Server)
     - serverName       server TCP/IP address or name.  required
     - databaseName     database name  (e.g. c:\mydb). required
     - retrieveMessagesFromServerOnGetMessage:  required by WAS not the database: Defaults to false by the database, but must be set to true in WAS.
   

   The following data source custom properties are optional:

   portNumber  port number where Network Server listens for connection       
    requests.  required.  (Note: by default Network Server listens on port 1527.) 
       logWriter
       traceLevel       
       traceFile
       traceFileAppend
       deferPrepares              
   Works as documented except that  the prepare on EXECUTE STATEMENT is never deferred (those are cloudscape native stuff)
    resultSetHoldability           Defaults to CLOSE_CURSORS_AT_COMMIT for    Cloudscape.  This is the only valid value for  Network Server. Use the JDBC 3.0 API's for setting holdability.
    securityMechanism           Network Server supports the following   security Mechanisms.
    com.ibm.db2.jcc.DB2BaseDataSource.CLEAR_TEXT_PASSWORD_SECURITY    -- default
    com.ibm.db2.jcc.DB2BaseDataSource.ENCRYPTED_PASSWORD_SECURITY 
   

Cloudscape throws an exception when you access the result set after the transaction is committed

When you run WebSphere Application Server with Cloudscape using the Cloudscape network server framework, Cloudscape throws an exception when you access the result set after the transaction is committed despite the fact that the cursor holdability is false by default.

This problem does not exist when you run in Cloudscape embedded. This problem has been reported to Cloudscape.

Ensure that your application does not rely on an exception that is thrown.

Adding quotes to the installCloudscape51.bat or installCloudscape51.sh file around the if the install_root path includes spaces

If the install_root path includes spaces, for example, c:\program files\WebSphere\AppServe, you must modify the installCloudscape51.bat or installCloudscape51.sh file to add quotes ("") around the install_root path as follows:

• change %install_root%\bin\wsadmin to "%install_root%\bin\wsadmin";
• change %install_root%\cloudscape51\setupCloudscape.jacl to "%install_root%\cloudscape51\setupCloudscape.jacl";
• change $\{%install_root%}/universalDriverForCloudscape to "$\{%install_root%}/universalDriverForCloudscape";
• change $\{%install_root%}/cloudscape51/lib to "$\{%install_root%}/cloudscape51/lib".

Databases-Microsoft SQL Server

• An error occurs when enlisting a global transaction and subsequent calls to the ResultSet.next() method might hang

An error occurs when enlisting a global transaction and subsequent calls to the ResultSet.next() method might hang

Symptom:

An error occurs when enlisting a global transaction. Subsequent calls to the ResultSet.next() method might hang.

The error is an XAException with error code -3 (XAER_RMERR) and is similar to the following:

javax.transaction.xa.XAException
                                                                                                    at com.ddtek.jdbcx.sequelink.SequeLinkImplXAResource.start(Unknown Source)
                                                                                  
     at com.ddtek.jdbcx.slbase.BaseXAResource.start(Unknown Source)
                                                                                              
     at com.ddtek.jdbcspy.SpyXAResource.start(Unknown Source)
                                                                                                         

Problem:

This error is due to a bug in the SequeLink Java Database Connectivity (JDBC) driver. Case 15007076 is opened against DataDirect Technologies for this problem.

Description:

The error on XAResource.start causes the hang in the ResultSet.next() method.

Response:

To work around this problem, switch to the Connect JDBC driver to connect to the Microsoft SQL server.

When a patch is received from DataDirect Technologies, a corresponding patch for the WebSphere embedded SequeLink driver will be available on the DataDirect Driver Updates download page of WebSphere Application Server:

ftp://ftp.software.ibm.com/software/websphere/info/tools/DataDirect/datadirect.htm

Databases-Oracle

WebSphere Application Server security help files incorrectly mapped

Some of the links from the following WebSphere Application Server security windows to their corresponding help files are incorrectly mapped:

Environment > Naming > CORBA Naming Service Users

Environment > Naming > CORBA Naming Service Users > Add

Environment > Naming > CORBA Naming Service Groups

Environment > Naming > CORBA Naming Service Groups > Add

System Administration > Console Groups > Add

Note: In the System Administration > Console Groups > Add window, the links to the help located next to Group Description and Role Description are correct. However, the link to the help text at the top of the help window is incorrect.

If you access a help file that does not correspond to the appropriate WebSphere Application Server window, use the following table to locate the correct help information. When you access the incorrect help file, find the listing of help files located under Core Console on the left side of your current help file window and click the appropriate link.

Window path	Correct Help file
Environment > Naming > CORBA Naming Service Users	CORBA Naming Service users settings
Environment > Naming > CORBA Naming Service Users > Add	CORBA Naming Service users settings
Environment > Naming > CORBA Naming Service Groups	CORBA Naming Service groups
Environment > Naming > CORBA Naming Service Groups > Add	CORBA Naming Service groups
System Administration > Console Groups > Add	Console groups settings

Secure interoperability between WebSphere Application Server, Version 5 and WebSphere Application Server, Version 5.0.1 and Version 5.0.2 fails when the Lightweight Directory Access Protocol base distinguished name in not correctly normalized in the WebSphere Application Server, Version 5 configuration

In WebSphere Application Server, Version 5.0.1 and Version 5.0.2, the distinguished name is normalized according to the Lightweight Directory Access Protocol (LDAP) specification. In WebSphere Application Server, Version 5, the normalization of the distinguished name is not done. The normalization consists of removing spaces in the base distinguished name before or after commas and equal symbols.

An example of a non-normalized base distinguished name is "o = ibm, c = us" or "o=ibm, c=us". .

An example of a normalized base distinguished name is "o=ibm,c=us".

It is preferred that the distinguished name is manually normalized when you enter the base distinguished name in the configuration. In WebSphere Application Server, Version 5.0.1 and higher version, the normalization occurs automatically at the run time.

When a WebSphere Application Server, Version 5.0.1 and Version 5.0.2 system, which always has a normalized distinguished name, sends a security token to a WebSphere Application Server, Version 5 system that contains a non-normalized distinguished name, the request is rejected due to the mismatched distinguished names during authorization. A common example of a request that fails is when a WebSphere Application Server, Version 5 node is synchronizing the configuration from a WebSphere Application Server, Version 5.0.1 and Version 5.0.2 deployment manager. Another example is that a request fails when a WebSphere Application Server, Version 5.0.1 and Version 5.0.2 servlet or enterprise bean makes a downstream request to a WebSphere Application Server, Version 5 enterprise bean. However, a request going from a WebSphere Application Server, Version 5 system to a WebSphere Application Server, Version 5.0.1 and Version 5.0.2 system does not fail.

To ensure the interoperability between WebSphere Application Server, Version 5, Version 5.0.1, and Version 5.0.2, manually normalize the base distinguished name in the LDAP configuration on a WebSphere Application Server, Version 5.0 system by removing all the spaces before and after the commas and equal symbols.

WebSphere Application Server does not start when Java 2 security is enabled using the IBM Software Development Kit 1.4.1 beta release

Symptom:

WebSphere Application Server does not start when Java 2 security is enabled using the IBM Software Development Kit 1.4.1 beta release.

Problem:

WebSphere Application Server goes into a recursion and a final core dump when Java 2 security is enabled using the IBM Software Development Kit 1.4.1 beta release.

Response:

This problem applies to IBM Software Development Kit 1.4.1 beta release of the WebSphere Application Server. This is not a problem for WebSphere Application Server running on the IBM Software Development Kit 1.3.X.

To avoid the error, do not enable Java 2 security.

By default, Java 2 security is disabled, but automatically enabled when global security is enabled through the administrative console. You should disable the Java 2 Security checkbox to disable Java 2 security.

If you fail to do this in the administrative console and have already saved your changes and tried to restart the server, you can use the wsadmin tool to disable Java 2 security.

wsadmin -conntype NONE
wsadmin>$AdminConfig modify "(cells/<node name>/security.xml)" 
{{enforceJava2Security {false}}}

wsadmin>$AdminConfig save
wsadmin>exit

Ignoring the error message about the missing ws-security.xml file in the Java Message Service server

Symptom:

An error or warning message is generated about the missing file %install_root%/bin/wsinstance/configdefaults/templates/system/nodes/servers/jmsserver/ws-security.xml when the Java Message Service server is started.

Problem:

This file is not installed during the WebSphere Application Server, Version 5.0.2 update process.

Response:

You can ignore the error or warning message.

A Web services security enabled application fails to start

Symptom:

A Web services security enabled application fails to start. You can receive an error message similar to the following:

[6/19/03 11:13:02:976 EDT] 421fdaa2 KeyStoreKeyLo E WSEC5156E: An exception while retrieving the key from KeyStore object: java.security.UnrecoverableKeyException: Given final block not properly padded

Problem:

The cause of the problem is that the keypass (password) provided for a particular key in a Key Store is invalid. The Key Store passwords are specified in the KeyLocators elements of the bindings file(s) (ws-security.xml, ibm-webservices-bnd.xmi or ibm-webservicesclient-bnd.xmi).

Response:

Check the keypass values for keys specified in the KeyLocators elements of the bindings file(s) and correct any that are incorrect.

The Federal Information Processing Standards security is enabled through the Secure Sockets Layer settings and the deployment manager cannot communicate with the node agent using the Simple Object Access Protocol connector

Symptom:

The Federal Information Processing Standards (FIPS) security is enabled through the Secure Sockets Layer (SSL) settings and the deployment manager cannot communicate with the node agent using the Simple Object Access Protocol (SOAP) connector

Problem:

The provider is not set properly for the SOAP client connector.

Description:

The SOAP client must use a FIPS (Java Secure Sockets Extension) JSSE provider when the server is listening on a FIPS enabled socket.

Response:

You must modify the java.security file to provide the FIPS properties to JSSE in both the deployment manager and each node.

In the WebSphere/AppServer/java/jre/lib/security/java.security directory and in the WebSphere/DeploymentManager/java/jre/lib/security/java.security directory, modify the following provider list:

security.provider.1=sun.security.provider.Sun
security.provider.2=com.ibm.crypto.fips.provider.IBMJCEFIPS
security.provider.3=com.ibm.crypto.provider.IBMJCE
security.provider.4=com.ibm.fips.jsse.IBMJSSEFIPSProvider
security.provider.5=com.ibm.jsse.IBMJSSEProvider
security.provider.6=com.ibm.security.cert.IBMCertPath
security.provider.7=com.ibm.crypto.pkcs11.provider.IBMPKCS11

Cannot start the application server on Solaris Operating Environment and HP platforms with IBM Software Development Kit 1.4.1

Symptom:

For the IBM Software Development Kit 1.4.1 beta on Solaris Operating Environment and HP platforms only, the application server cannot start after the installation. You see the following error in the SystemOut.log file even before security is enabled:

[6/23/03 17:03:01:543 CDT]   e93999 HttpTransport A SRVE0171I: Transport http is listening on port 9,080.
[6/23/03 17:03:02:542 CDT]   e93999 TraceNLS      u No message text associated with key Unable.to.create.server.socket in bundle com.ibm.ejs.resources.seriousMessages
[6/23/03 17:03:02:539 CDT]   e93999 SSLServerSock E Unable to create server socket
[6/23/03 17:03:02:588 CDT]   e93999 WebContainer  E SRVE0146E: Failed to Start Transport on host , port 9443. 
The most likely cause is that the port is already in use. Please ensure that no other applications are using this port 
and restart the server. com.ibm.ws.webcontainer.exception.TransportException: Failed to start transport https: 
java.io.IOException: java.lang.RuntimeException: Export restriction: SunJSSE only
        at com.ibm.ws.webcontainer.http.HttpTransport.startTransport(HttpTransport.java:132)
        at com.ibm.ws.webcontainer.WebContainer.startTransports(WebContainer.java:634)
        at com.ibm.ws.runtime.component.WebContainerImpl.startTransports(WebContainerImpl.java:319)
        at com.ibm.ws.runtime.component.WebContainerImpl.vetoableChange(WebContainerImpl.java:343)
        at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:300)
        at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:320)
        at java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:217)
        at com.ibm.ws.runtime.component.ComponentImpl.setState(ComponentImpl.java:95)
        at com.ibm.ws.runtime.component.ComponentImpl.setStartState(ComponentImpl.java:132)
        at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:123)
        at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
        at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
        at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
        at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
        at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)

Problem:

On platforms that have the IBM Software Development Kit 1.4.1, the IBM Java Secure Sockets Extension (JSSE) implementation cannot be plugged in due to the export restrictions. The IBM Software Development Kit 1.4.1 implementation prevents other JSSE implementations from being supported, at least in the international version of IBM Software Development Kit 1.4.1 shipped with WebSphere Application Server. Because of this, the out-of-the-box configuration does not allow the server to start on these two platforms, even when security is disabled. This is because the HTTP transports tries to start and they need the Secure Sockets Layer (SSL) implementation to function. For the IBM Software Development Kit 1.4.1 beta, there is not enough time to modify the configuration correctly to bypass this problem.

Response:

To start the server, you must edit the security.xml file (even if security is disabled) to change the SSL configuration to use the Sun JSSE, the Java TM Cryptography Extension (JCE) and the SunX509 providers. You need to add the following properties into the security.xml at the following location:

${install_root}/config/cells/cellname/security.xml

The following is what the DefaultSSLSettings default configuration entry looks like after the edits.

<repertoire xmi:id="SSLConfig_1" alias="wsbpc11/DefaultSSLSettings">
<setting xmi:id="SecureSocketsLayer_1" keyFileName="${install_root}/etc/DummyServerKeyFile.jks" keyFilePassword="{xor}CDo9Hgw=" keyFileFormat="JKS" tr
ustFileName="${USER_INSTALL_ROOT}/etc/DummyServerTrustFile.jks" trustFilePassword="{xor}CDo9Hgw=" trustFileFormat="JKS" clientAuthentication="false" securityLev
el="HIGH" enableCryptoHardwareSupport="false">
        <cryptoHardware xmi:id="CryptoHardwareToken_1" tokenType="" libraryFile="" password=""/>
        <properties xmi:id="Property_4" name="com.ibm.ssl.protocol" value="SSLv3"/>
        <properties xmi:id="Property_5" name="com.ibm.ssl.contextProvider" value="SunJSSE"/>
        <properties xmi:id="Property_6" name="com.ibm.ssl.trustManager" value="SunX509"/>
        <properties xmi:id="Property_7" name="com.ibm.ssl.keyManager" value="SunX509"/>
        <properties xmi:id="Property_8" name="com.ibm.ssl.enabledCipherSuites" value="SSL_RSA_WITH_RC4_128_MD5 SSL_RSA_WITH_RC4_128_SHA SSL_RSA_WITH_DES_CBC_SHA SSL_RSA_WITH_3DES_EDE_CBC_SHA SSL_DHE_DSS_WITH_DES_CBC_SHA SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA SSL_RSA_EXPORT_WITH_RC4_40_MD5 SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA"/>
        <properties xmi:id="Property_9" name="com.ibm.ssl.keyStoreProvider" value="SUN"/>
        <properties xmi:id="Property_10" name="com.ibm.ssl.trustStoreProvider" value="SUN"/>
      </setting>
    </repertoire>

The following are the properties which you add or modify. All other information is left the same.

<properties xmi:id="Property_5" name="com.ibm.ssl.contextProvider" value="SunJSSE"/>
        <properties xmi:id="Property_6" name="com.ibm.ssl.trustManager" value="SunX509"/>
        <properties xmi:id="Property_7" name="com.ibm.ssl.keyManager" value="SunX509"/>
        <properties xmi:id="Property_8" name="com.ibm.ssl.enabledCipherSuites" value="SSL_RSA_WITH_RC4_128_MD5 SSL_RSA_WITH_RC4_128_SHA SSL_RSA_WITH_DES_CBC_SHA SSL_RSA_WITH_3DES_EDE_CBC_SHA SSL_DHE_DSS_WITH_DES_CBC_SHA SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA SSL_RSA_EXPORT_WITH_RC4_40_MD5 SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA"/>
        <properties xmi:id="Property_9" name="com.ibm.ssl.keyStoreProvider" value="SUN"/>
        <properties xmi:id="Property_10" name="com.ibm.ssl.trustStoreProvider" value="SUN"/>

If the ${USER_INSTALL_ROOT}/java/jre/lib/security/java.security file does not get updated, the following is what the provider list should be:

security.provider.1=sun.security.provider.Sun
security.provider.2=com.sun.crypto.provider.SunJCE
security.provider.3=com.ibm.security.cert.IBMCertPath
security.provider.4=com.sun.net.ssl.internal.ssl.Provider
security.provider.5=com.sun.rsajca.Provider
security.provider.6=sun.security.jgss.SunProvider
security.provider.7=com.ibm.crypto.provider.IBMJCE
security.provider.8=com.ibm.crypto.pkcs11.provider.IBMPKCS11

You should also add the following to the ${USER_INSTALL_ROOT}/properties/sas.client.props file after the existing SSL information:

com.ibm.ssl.contextProvider=SunJSSE
com.ibm.ssl.keyManager=SunX509
com.ibm.ssl.trustManager=SunX509
com.ibm.ssl.keyStoreProvider=SUN
com.ibm.ssl.trustStoreProvider=SUN

Note: Global security cannot be enabled without a fix and is not supported in this beta for Solaris Operating Environment and HP platforms.

Problems with the Java Message Service protocol within Web services when security is enabled

Symptom:

The following exception occurs when you are creating a URL connection using the Java Message Service (JMS) protocol within Web services when global security is enabled:

java.security.AccessControlException: access denied (java.lang.RuntimePermission accessClassInPackage.sun.net.www.protocol.jms)
 at java.security.AccessControlContext.checkPermission(AccessControlContext.java(Compiled Code))
 at java.security.AccessController.checkPermission(AccessController.java(Compiled Code))
 at java.lang.SecurityManager.checkPermission(SecurityManager.java(Compiled Code))
 at com.ibm.ws.security.core.SecurityManager.checkPermission(SecurityManager.java(Compiled Code))
  at java.lang.SecurityManager.checkPackageAccess(SecurityManager.java(Compiled Code))

If this permission is granted into the was.policy file of the application, the error that occurs is a MalformedURLException.

Problem:

Some security code sets the java.protocol.handler.pkgs system property, overriding what is already specified for the JMS protocol.

Response:

You can disable the global security to avoid receiving the exception. You can also programmatically add the protocol back to the java.protocol.handler.pkgs system property by appending the following string to the end of the value already set in this system property using a | character as a delimiter:

com.ibm.ws.protocol

A 500 type error is thrown when you click Import Keys in the Lightweight Third Party Authentication panel multiple times and save the changes each time in the administrative console

Symptom:

In the administrative console, when you click Import Keys in the Lightweight Third Party Authentication (LTPA ) panel multiple times in the same session and save it each time, the following message might be displayed on the console intermittently:

Error 500
An error occurred while processing request: /syncworkspace.do
Message: Server caught unhandled exception from servlet [action]: 
java.lang.IllegalStateException

Note: When you enter a wrong password in the LTPA panel during importing the keys and save the password, the save operation displays error messages in the WebSphere Status Window at the bottom of the administrative console. The keys are not updated in the run time and the old set of keys is used. However, the keys and the wrong password are saved in the configuration. This configuration is used during the next startup of the server(s)

Therefore, if you save a wrong password accidentally, do not restart the server(s) unless the password is changed because the server(s) can fail to start if the keys and the password do not match.

Problem:

The cause for this error is that an invalidated session is referred to under some circumstances.

Response:

To avoid receive this error, log out and log in back to the administrative console using a new window. Import the keys if necessary. If the problem persists, use the wsadmin tool.

If you enter a wrong password and save the passowrd during importing the keys, you can use the following wsadmin commands to change the password to the correct value (the keys should be saved during the save operation). Do not restart any servers unless the password is changed for each of them.

set LTPA [$AdminConfig list LTPA]

set ltpaPw theCorrectPassword

$AdminConfig modify $LTPA [list [list password $ltpaPw]]

$AdminConfig save

Web services security is not supported in a pure Java client (also known as a non-managed client)

Symptom:

Web services security is not supported in a pure Java client (also known as a non-managed client). Web services security is only supported in a managed client in Fix Pack 2.

Problem:

The Web services security constraints do not apply to the outbound client or Web services acting as the client Simple Object Access Protocol (SOAP) message if the application code does not use the Java 2 Platform, Enterprise Edition (J2EE) programming model, so the J2EE environment (including security handlers) is not available to the client. This includes Web services security. You might configure to digitally sign, encrypt, and generate the security tokens. For the outbound message for a client or Web services acting as a client, the SOAP message is not digitally signed, encrypted or the security is not token inserted into the message.

Response:

Change the application to a managed client application and use the J2EE programming model to invoke Web services.

The JavaMail-related Java 2 security exceptions might be reported in the system log file when the Web services applications run with attachments in the Simple Object Access Protocol messages

Symptom:

The following JavaMail-related Java 2 security exceptions might be reported in the system log file when the Web services applications run with attachments in the Simple Object Access Protocol (SOAP) messages.

java.security.AccessControlException: access denied (java.io.FilePermission c:\WebSphere\AppServer\java\jre\lib\javamail.providers read)
java.security.AccessControlException: access denied (java.io.FilePermission c:\WebSphere\AppServer\java\jre\lib\javamail.address.map read)

Problem:

These exceptions are benign. This is not an application or system problem because the JavaMail anticipates the exceptions and handles them appropriately. The WebSphere SecurityManager is rather verbose in logging possible violations of the Java 2 security access control exceptions.

Response:

If this situation is a problem, add the following permission settings to the <install_root>\config\cells\<node_name>\nodes\<node_name>app.policy.

The permission settings grant the permissions that the SecurityManager is falsely warning about.

permission java.io.FilePermission "${was.install.root}${/}java${/}jre${/}lib${/}javamail.providers", "read";    
permission java.io.FilePermission"${was.install.root}${/}java${/}jre${/}lib${/}javamail.address.map", "read";

For further details, consult with the InfoCenter article, "JavaMail security permissions best practices."

An error occurs when you use the wsadmin tool with the Remote Method Invocation connector and security enabled if only the administrative scripting client is installed during a WebSphere Application Server base installation

Symptom:

The following error occurs whey you try to use the wsadmin tool with the Remote Method Invocation (RMI) connector and security enabled if only the administrative scripting client is installed during a WebSphere Application Server base installation.

C:\WebSphere\AppServer\bin>wsadmin  -host smhardh1   -conntype  RMI -port  9809
WASX7023E: Error creating "RMI" connection to host "smhardh1"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException
WASX7213I: This scripting client is not connected to a server process; please refer to the log file
C:\WebSphere\AppServer\logs\wsadmin.traceout for additional information.
WASX7029I: For help, enter: "$Help help"  
wsadmin>exit

Problem:

When you install the administrative scripting feature from the WebSphere Application Server base installation, the certpath.jar file is missing in thejava/jre/lib/ext directory. When you use the RMI connector, you need this JAR file.

Response:

To solve this problem, perform a WebSphere Application Server full installation and get the certpath.jar file from the ${install_root}/java/jre/lib/ext directory and copy it to the administrative scripting ${install_root}/java/jre/lib/ext directory.

An alternative is to install the full WebSphere Application Server base installation which includes the certpath.jar file.

Federal Information Processing Standards are supported in WebSphere Application Server, Version 5.0.2

WebSphere Application Server, Version 5.0.2 supports a configuration option to use only Federal Information Processing Standards (FIPS) 140-2 certified cryptography modules including IBM Java Cryptography Extension Federal Information Processing Standards (IBMJCEFIPS) and IBM Java Secure Socket Extension Federal Information Processing Standards (IBMJSSEFIPS).

When enabled to use FIPS certified cryptography modules, WebSphere Application Server, Version 5.0.2 uses IBMJCEFIPS exclusively and does not use IBMJCE.

When enabled to use FIPS certified cryptography modules, WebSphere Application Server, Version 5.0.2 can be configured to use IBMJSSEFIPS on a per port basis.

IBMJCEFIPS and IBMJSSEFIPS that are packaged in WebSphere Application Server, Version 5.0.2 are currently in the FIPS certification process. The IBMJCEFIPS and IBMJSSEFIPS modules in WebSphere Application Server, Version 5.02, are being certified on IBM Software Development Kit 1.3.1. The modules are certified for Windows and AIX platforms and Solaris Operating Environment only.

IBM is firmly committed to FIPS certification and to meet the Government Security Standards.

System administration

• Issuing the addNode command can replace the plugin-cfg.xml file
• Empty NetworkDeploymentCell directory is left in the configuration directory
• Enabling authentication in the file transfer service
• System performance degrades when you configure the nodeagent failover with a certain script

wsadmin -profile redeployFileTransfer.jacl -c "fileTransferAuthenticationOn ear_file_path"

wsadmin -profile redeployFileTransfer.jacl -c "fileTransferAuthenticationOn c:/WebSphere/DeploymentManager/installableApps"

wsadmin -profile redeployFileTransfer.jacl -c "fileTransferAuthenticationOff ear_file_path"

Feb 28 14:48:37 wastst12 init: Id "was" respawning too fast: disabled for 5 minutes

Console

All platforms

• Resolve the administrative console port conflict

Netscape browser

All platforms

• Resizing the Netscape browser results in an error
• Resizing the Netscape browser causes an error 404 message
• Netscape screen blanks out while using the administrative console
• Resizing Netscape Version 4.7 causes errors
• Netscape browser displays ---???--- instead of a blank line for the drop down lists

• Enabling Netscape Version 4.7 to display double-byte character set correctly

• Using Netscape Version 4.79 on a Solaris Operating Environment causes problems
• Limitations occur when using Netscape with Solaris Operating Environment

• Netscape browser must be capable of launching from a terminal window on all UNIX platforms

Error 0
  An error occurred while processing request: http://localhost:9090/admin/upload.do

  message:

  Details
  com.ibm.webshpere.servlet.error.ServletErrorReport:
         at java.lang.Class.newInstance0(Native Method)
         ... 

Enabling Netscape Version 4.7 to display double-byte character set correctly

When using Netscape on AIX platforms without the translated package, the English version of Netscape is available for all locale environments as the default package. However, the English version of Netscape does not display double-byte character set (DBCS) characters on the browser radio buttons and title bars because the fonts are mismatched.

To work around this problem, you can install the message resource to make the translated version of Netscape available on a DBCS environment. Use the translated version of Netscape to display the corrupted DBCS correctly. Change the locale from English to the expected DBCS locale before starting Netscape. For example, issue the following commands to display the Japanese contents on Ja_JP (AIX Shift JIS locale):

$ export LANG=Ja_JP 
$ netscape&

How to check the installed package

For the AIX platform:

1. Execute the lslpp -aL | grep Netscape.msg command.
2. Check the language and locale information using Netscape.msg package. For example, the result of the command executed in step 1 is as follows for the system having Japanese-translated Netscape:

   # lslpp -aL | grep Netscape.msg
   Netscape.msg.Ja_JP.communicator.rte
   Netscape.msg.ja_JP.communicator.rte 

For the Red Hat Linux Version 7.2 platform:

Execute the rpm-ql netscape-common command to get the list of installed files.

In case of Netscape Version 4.78 on Red Hat Linux Version 7.2, the translated packages for seven languages including four DBCS languages (Japanese, Korean, Simplified Chinese, and Traditional Chinese) are included in a common package.

How to install the package

For the AIX platform:

Install the Netscape.msg.%L.communicator.rate package where %L is the locale information for the System Management Interface Tool (SMIT) or SMITTY to use. This message resource is provided by the Bonus Pack CD or the Expansion Pack CD for AIX platform, which provides the Netscape common package.

Perform the following steps to install the package:

1. Set the media which has the Netscape installation image. For AIX 5L platform, set the Expansion Pack media.
2. Go to the directory which has the Netscape installation package. For AIX 5L platform Expansion Pack, go to the installp/ppc directory.
3. Start SMIT or SMITTY.
4. Click System Environments > Manage Language Environment > Change/Show Applications for a Language > Add Language for Application Already Installed.
5. In the Add Language for Application Already Installed field select a language (locale) from the drop-down menu list for the Language translation to install field.
6. Click OK.
7. In the Add Language for Application Already Installed field enter the directory location. Enter "." for the current directory or /cdrom/installp/ppc for the full path as input directory for the software. Do not select cdrom as the input device because the installation package does not exist on the root directory of the CD-ROM.
8. Click OK.
9. Click List to check if the configuration is correct. The configuration is correct if Netscape is on the list of installed application. Execute the installation now.
10. Click OK.
11. Exit SMIT or SMITTY.

For Red Hat Linux Version 7.2 platform:

The default Netscape installation can install each translated resource as part of the common package. There is no way to install the translated package individually. However, TrueType fonts (TTF packages) require installation for each language to correctly display the translated resources on Netscape. Use the following to check if the required font files are correctly installed:

$ rpm -qa | grep ttf
resources.0-4
ttfm-0.9.1-8
ttfonts-ja-1.0-6
ttfonts-ko-1.0-10
ttfonts-zh_CN-2.11-5
ttfonts-zh_TW-2.11-5

Using Netscape Version 4.79 on a Solaris Operating Environment causes problems

Using Netscape Version 4.79 on a Solaris Operating Environment to access the administrative console causes problems with some key text translations with the zh_TW.EUC locale. This situation is not a problem when you use Netscape Version 4.7. The officially supported version of Netscape on a Solaris Operating Environment is Version 4.79, but in this case the workaround is to use Netscape Version 4.7.

Limitations occur when using Netscape with Solaris Operating Environment

If you click Troubleshooting > Logs and Trace > <server> > Diagnostic Trace > Modify, the window that pops up allowing you to select the Components and Groups to trace might not display a scroll bar, preventing you from viewing all the components and groups.

The text area displaying the selected components, groups, and trace levels does not have a vertical scroll bar. This omission is a limitation of Netscape on a Solaris Operating Environment.

To work around this problem, refresh the window to show the scroll bar.

PATH=$PATH:/opt/Netscape
export PATH

Scripting

• An error occurs when you use the wsadmin tool with the Remote Method Invocation connector and security enabled if only the administrative scripting client is installed during a WebSphere Application Server base installation
• Cannot install an EAR file remotely using the wsadmin tool
• Commands testConnection and getPropertiesForDataSource are deprecated
• Using a WebSphere Application Server, Version 5.0.2 wsadmin scripting client to connect to a Version 5.0.2 server to create or update the native type configuration data

WASX7390E: Operation not supported - testConnection command with config id
and properties arguments is not supported. Use testConnection command with
config id argument only.

WASX7389E: Operation not supported - getPropertiesForDataSource command is not supported.

WASX7015E: Exception running command: "$AdminConfig modify $targetMappings {{enable false}}"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7239E: Unexpected error setting attribute "enable" of type "boolean" to value "false."  Additional information may be found in the trace log.

Performance data and tools

• Editing the plugin-cfg.xml file and changing the value of the ESIEnable variable
• Setting the maximum pool size to the advised value and set the minimum pool size to half of the advised value
• The prepared statement recommendation might be too large
• The Tivoli Performance Viewer Advisor and the Runtime Performance Advisor might give contradictory advice on shared resources
• Ignoring the advice to set the configuration for the Java virtual machine heap size maximum on iSeries
• Removing the Performance Advisors Technology Preview JAR files after upgrading to Fix Pack 2 from a previous installation with the Performance Advisors Technology Preview installed
• The fix pack installer does not update the files that are transferred during federation
• Tivoli Performance Viewer cannot connect to a running server if security is enabled
• Tivoli Performance Viewer cannot set all Performance Monitoring Infrastructure levels to None if the Runtime Performance Advisor is enabled
• Ignoring the NotSerializableException when setting a servlet session manager Performance Monitoring Infrastructure module to level maximum
• Setting the monitoring level for the the Servlet Session Manager modules to Medium or higher

"TUNE5003W: The JVM maximum heap size is unusually small.  Typically, the maximum heap size is greater than or equal to..." 

"TUNE5005W: The initial JVM  heap size is greater than the maximum heap size."

"[ServletException in:/secure/layouts/detailTitleLayout.jsp] Cannot find bean com.ibm.ws.console.pertuningAdmin.RPAAdviceDetailForm in scope Null"

"An error occurred while processing request: /com.ibm.ws.console.perfTuningAdmin.forwardCmd.do.  Message com.ibm.ws.performance.tuning.rule.RuleLookup: method <init>=(Ljava/io/InputStream;) V not found"

"RPARuleEngineController caught unexpected exception java.lang.Exception: could not  get input stream for perftuners.xml from ..." 

"[ServletException in:/secure/layouts/tabsLayout.jsp]  Error - Tag Insert : At least one of the following attribute must be defined :  template|page|attribute|definition|name|beanName. Check tag syntax'" 

SECJ0305I: Role based authorization check failed for security name <null>, accessId 
no_cred_no_access_id while invoking method.

"SessionContex E Exception is: java.io.NotSerializableException: ....."

"TUNE0324W: There was an unknown error  detected in the Runtime Performance Advisor.  Check the application server logs and  enable trace."

Diagnosing and fixing problems and troubleshooting

• The nodeagent SystemOut.log message repeats continuously on an AIX platform when the Performance Monitoring Infrastructure is enabled
• The correct directory of the pwbs_GetUrlPrefixesHelp.html file

No PMI Module found for the Mbean systemModule

Documentation

• More information on configuring the Edge-Side Include processor is located in the documentation article, "Configuring Edge Side Include caching"