Docstoc

Release Notes for

Document Sample
Release Notes for Powered By Docstoc
					             Release Notes for
         WebSphere Application Server
           Version 5.0.1 for iSeries
                                         Last Update: 06/26/2003


This document contains Release Notes for WebSphere Application Server Version 5.0.1 for iSeries.
The Release Notes contain information about known problems and the work arounds. This
document also includes some supplemental information for topics covered in the WebSphere
Application Server documentation. This version replaces all earlier versions of the release notes.
These notes will be updated periodically. Please see the WebSphere Application Server for iSeries
Web site for the most up-to-date information.
When troubleshooting, be sure to search the WebSphere Applicati on Server for iSeries FAQ
(Frequently Asked Questions) database.


        See the Installation documentation for the most up-to-date, step by step instructions on installing
         the product and creating the initial configuration.




Documentation
The most up-to-date documentation can be found on the WebSphere Application Server for iSeries
Web site documentation page.
The WebSphere Application Server for iSeries Documentation Center is now available for
download from the WebSphere for iSeries Web site. This downloadable version can be installed
and viewed on a local system rather than remotely from the WebSphere for iSeries Web site.
The following instructions describe how to download and install the WebSphere for iSeries
Documentation Center:


    1.   Download the zip file for the Documentation Center from the Documentation page on the
         WebSphere for iSeries Web site.
    2.   Create a new directory, called WAS50BDocs, on the local system.
    3.   Extract the contents of the downloaded zip file to this new directory.


Then you can access the Documentation Center by opening the index.html page in the
documentation subdirectory in a browser:


         <install_drive>\WAS50BDocs\docs\index.html
Installation Instructions

Installation Instructions for WebSphere Application
Server for iSeries V5.0.1 Group PTF

WebSphere Application Server for iSeries ("Base Edition") V5.0.1 is a fix release that is shipped in
the form of a Group PTF (Program Temporary Fix). Please see the Install section in the Known
Problems and Restrictions section of this document before beginning the install.
The following instructions describe how to install the V5.0.1 group PTF:


    1.   Installation of Group PTF on systems with multiple instances may notice an increase in amount
         of time required to apply PTFs. You may notice a group ptf install time increase of several
         minutes per instance.
    2.   Verify that WebSphere Application Server ("Base Edition") V5.0 is installed on the server before
         proceeding with the V5.0.1 installation. V5.0 must be installed on the system before the V5.0.1
         group PTF can be installed. The following instructions describe how to determine if WebSphere
         Application Server ("Base Edition") V5.0 is installed:
             a.   Run the following command from an iSeries command line:


                        DSPSFWRSC


             b.   Page down until you find 5733WS5. There should be at least option 1 of the 5733WS5
                  product listed. If just options *BASE and 5 are displayed, the base edition product is
                  not installed.
             c.   Press PF11 to display the Release column. A release value of V5R0M0 indicates that
                  version 5.0 is installed.
    3.   Stop all WebSphere application servers on the server.
             o    Please see Ending all WebSphere Application Server jobs running on your iSeries in
                  the   Shutting   down WebSphere Application Server          section   of   the   product
                  documentation for instructions.
             o    Stop all the active Queue Mangers using ENDMQM CL command. You must specify
                  ENDCCTJOB(*YES) for ENDMQM command to ensure all the processes connected to
                  the queue manager are terminated. The "WRKMQM MQMNAME(*ALL)" CL command
                  can be used to find out which queue managers are active.
    4.   A pre-condition as been set on all WAS 5.0.1 PTFs. The PTFs will not apply if the QEJBAS5 or
         QEJBASND5 subsystem is active. Use the WRKSBS CL command to determine if either of
         these subsystems is active. Refer to the previous step for information on shutting down the
         WebSphere Application Server environments.
    5.   End any HTTP Server instances that are used for WebSphere V5. For the IBM HTTP Server
         powered by Apache, use the following command:


           ENDTCPSVR SERVER(*HTTP) HTTPSVR(instance_name)
6.   Install the Group PTF. The recommended steps for installing the group PTF are:
          .   Insert the group PTF CD (the first CD if more than one) into the CD-ROM drive of your
              iSeries system.
         a.   End the WebSphere environment as described above.
         b.   Place the system in restricted state (ENDSBS SBS(*ALL) OPTION(*IMMED)) .
         c.   Go to the Work with PTFs menu (GO PTF).
         d.   Select option 8 .
         e.   Enter the appropriate information so that all PTFs for all products on the CDs are
              loaded and applied, and the system is automatically IPL'd.


     Notes:


         o    The WebSphere Application Server PTFs that are part of the group PTF are all
              corequisites of each other. Do not install or remove individual WebSphere Application
              Server PTFs. Instead, all of the WebSphere Application Server PTFs that are part of
              the Group PTF must be installed or removed in their entirety.
         o    The group PTF also includes PTFs for other products. If you install or re-install one of
              these products after applying the WebSphere Application Server group PTF, you must
              re-apply the group PTF to pick up the PTFs for the newly installed product.
         o    If you also have WebSphere Application Server Network Deployment V5 for iSeries
              (Network Deployment) installed on you iSeries and are using it, you should load and
              apply the Network Deployment group PTF. This group PTF includes the Base Edition
              group PTF. Because these two products share a common option (*BASE), they should
              be updated at the same time. Additionally, if you are using Network Deployment
              installed on a different system to manage your Base Edition nodes on the iSeries
              system you are updating to V5.0.1, you must also obtain and install the WebSphere
              Application Server V5 for Distibuted Platforms Fix Pack 1 on the Network Deployment
              system.




     Please see the PTFs section in this document for more information on the WebSphere
     Application Server for iSeries ("Base Edition") V5.0.1 group PTF.


7.   (Optional) Install the WebSphere Application Server V5, Fix Pack 1 on any workstations on
     which you installed the workstation components (such as Application Development and Assmbly
     Tools or Tivoli Performance Viewer).


     The fix packs for the distributed platforms are shipped with the WebSphere Application Server
     for iSeries group PTF. Once you have applied the group PTF on your iSeries server, the fix
     packs can be found in the /QIBM/ProdData/WebAS5/Base/ClientFixPacks directory. See the
     table below for the name of the fix pack file for your workstation platform:


       Platform            Fix pack File
         Windows            was50_fp_win.zip

         Sun Solaris        was50_fp_solaris.zip

         AIX                was50_fp_aix.zip

         Linux on Intel     was50_fp_linux.zip

         Linux on 390       was50_fp_linux390.zip


    8.
         Follow these steps to install Fix Pack 1 on your workstation:
                .   Create directory was_install_root/update if it does not already exist, where
                    was_install_root is the destination directory you specified when installing the
                    workstation components.
               a.   Extract the contents of the zip file into the update directory created in the previous
                    step.
               b.   From a command window on the workstation, change directory to the update directory
                    created above.
               c.   Invoke the updateWizard.bat or updateWizard.sh script to start the installation. The
                    update wizard tool is a graphical user interface which guides you through installing the
                    fix pack. Generally you should be able to take the default options presented on the
                    update wizard screens. For more information on the update wizard and for other
                    options for installing the fix pack, read the readme_updateinstaller.html (or .pdf or .txt)
                    file located in the docs subdirectory of the update directory created in the previous
                    step.
    9.   Start the WebSphere Application Server environment (STRSBS QEJBAS5/QEJBAS5).
    10. Restart any HTTP Server instances you are using with WebSphere Application Server.



Fix Warning:
The WebSphere Application Server - Support Web site provides individual fixes for critical problems
that are not part of a WebSphere Fix Pack. These fixes have not been tested against WebSphere
Application Server Version 5.0.1 for iSeries. Unless otherwise noted, these fixes should not be
applied to your iSeries server. These fixes will be included in official fix packs for the product.
If you have a critical requirement for a fix, then please contact IBM Service.




PTF Information:
        Group PTFs SF99243 (V5R1) and SF99245(V5R2) are available. The preferred time to apply
         them is after installing WebSphere Application Server Version 5.0 for iSeries and preferably
         before the WebSphereApplication Server environment is first started or any additional
       WebSphere instances are created.
      If the group PTF for WebSphere Application Server Version 5.0.1 is installed, it will upgrade the
       WebSphere MQ V5.3 for iSeries product (5724B41) and the WebSphere MQ Classes for Java
       and JMS V5.3 for iSeries product (5639C34) to the CSD03 service level provided these
       products were already installed.


      PTF requirements for WebSphere Application Server Version 5.0.1 for iSeries are posted to the
       product Web site:


           o    V5R1
           o    V5R2


       Check this site often to verify that you are running the product with the latest required PTFs.




Known Problems and Restrictions:

Product Installation

WebSphere Application Server for iSeries Installation

  1.   The default install options for WebSphere Application Server include installing WebSphere MQ
       V5.3 for iSeries product and the WebSphere MQ Classes for Java and JMS V5.3 for iSeries
       product. If you have previous versions of the MQ Series for iSeries product or the MA88 MQ
       Classes for Java product installed, see the two bullets below for important information.
           o    If MQSeries for iSeries has been installed on your system, then you must migrate it to
                WebSphere MQ V5.3 for iSeries in order to use JMS with WebSphere Application
                Server. MQSeries for iSeries V4.2 (5769MQ2) and MQSeries for iSeries V5.1/V5.2
                (5733A38) are incompatible for use with WebSphere Application Server.


                For more information, see the Plan the Installation


           o    If MQSeries classes for Java and JMS (5648C60) has been installed on your system,
                then you must uninstall it before installing WebSphere MQ classes for Java and JMS
                (5639C34).


                For more information, see the Plan the Installation
  2.   When performing a local install of WebSphere Application Server from the CD-ROM drive of
       your iSeries server and IBM Developer Kit for Java(TM) (5722-JV1), Version 1.3 (option 5) is not
       installed it fails immediately without a error message. For more information, see the iSeries
       prerequisites for installing and running WebSphere Application Server
  3.   The update installer for the client cannot be launched concurrently with itself. Performing more
       than one update at the same time can lead to a failed or faulty installation. Currently, there is no
       solution for this problem.




WorkStation Components Installation

  1.   When installing the workstation components, if you wish to use the Application Assembly Tool
       (AAT) to generate deployment code for your enterprise application, you must select the
       Application Assembly and Development Tools option and all of its sub options. The Application
       Server option is automatically selected for you. Installing all of these options installs the
       necessary jar files for generating the deployed code for enterprise applications.
  2.   The pluggable client cannot be installed from the WebSphere Application Server client CD on a
       Windows system. To work around this problem, do one of the following:
           o    Copy the WebSphere Application Server client CD for Windows install image to your
                local temp directory and install it from your local temp directory.
           o    Run the installer manually from a command line with the following options:


                <cd Drive>\nt\install.exe -P
                OrbPropertiesFileCopy.installLocation="<SUNJrePath>/lib"




                Where <cd Drive> is the CD drive and <SUNJrePath> is the location of the SUN
                Operating Environment jre installed on your machine, for example:


                F:\nt\install.exe -P
                OrbPropertiesFileCopy.installLocation="C:/JavaSoft/JRE/1.3.1_04
                /lib"


  3.   Leaving the installation directory blank stops you from continuing the installation process. If the
       installation directory is left blank, the installation does not indicate an installation directory must
       be entered, but the installation does not allow you to proceed when you click Next.
       To workaround this problem, enter a directory destination in the installation directory field. Then,
       you are able to proceed to the next panel.
  4.   Do not delete vpd.properties file after uninstallation. If you have a problem with uninstallation or
       need to clear the WebSphere Application Server registry entries, do the following:


       Edit the vpd.properties file. On Windows platforms, this file is found in the directory C:\WINNT.
       On Linux platforms, this file is found in the /root directory. If you are uninstalling WebSphere
       Application Server, remove all the lines containing the string WSB. If you are uninstalling
       WebSphere Application Server Network Deployment, remove all the lines containing the string
       WSN. Do not delete the vpd.properties file if other products besides WebSphere Application
       Server have used ISMP for their installation.
QShell Scripts

  1.   The -copyto parameter on the createClientRuntime script does nothing.
       Do the following steps if you wish to copy the save file created by the createClientRuntime script
       to an IFS file:


       From the OS/400 command line, invoke the CPYTOSTMF CL command:
       CPYTOSTMF                                FROMMBR('/QSYS.LIB/YOURLIB.LIB/YOURFILE.FILE')
       TOSTMF('/directory/filename.savf') STMFOPT(*REPLACE)


  2.   Using the -help or -? parameter on the restoreConfig script prints the help text in addition to
       "java.lang.NullPointerException". The problem does not affect the proper functioning of the
       script if you do not use the -help or the -? parameter.




Administrative Console (GUI) and Command Line
Tools

  1.   The administrative console displays Network Deployment inform ation in the About section of
       the Home page for an instance (node) which has not been added to a Network Deployment cell.


       There is no workaround for this problem. The problem only occurs on a system which has had
       at least one instance added to a Network Deployment cell. Even if the instance is later removed
       from the cell, the About information is still incorrect. To view the current installed level of
       WebSphere         Application     Server       V5         on   you     system,       view      file
       /QIBM/ProdData/WebAS5/Base/properties/version/BASE.product.


  2.   When viewing the Product Information for an application server from the administrative console
       (Servers->Application servers->yourServer->Runtime tab->Product Information), you may see
       information displayed for Network Deployment (ND). This happens if you have added any
       instance to a Network Deployment cell, even if the instance you are currently viewing has not
       been added to a Network Deployment cell.


       There is no workaround to this problem. The information displayed for IBM WebSphere
       Application Server (ID=Base) is correct for the instance.


  3.   The administrative console does not support using the browser Back and Forward buttons. Use
       of these buttons can cause intermittent problems. Use the Back or Cancel buttons on the
       administrative console panels instead.
  4.   Attaching wsadmin to a remote server process running the following AdminApp commands
       results in an error:
     edit
     editInteractive
     export
     exportDDL
     install
     installInteractive uninstall


     To work around this problem, do one of the following:


            o   Invoke the AdminApp command with the server process connected locally.
            o   Specify the cell option when running these commands against a remote server.
                For example:


                $AdminApp uninstall samples {-cell myCellName}


                Note: This work around does not work for edit, editInteractive, install, and
                installInteractive commands if wsadmin is running from a system with only the
                standalone scripting client install.


5.   When any LDAP user or group filter is modified in the Advanced LDAP settings panel it is
     recommended that you click Apply instead of OK. Clicking OK takes you to the LDAP user
     registry panel, which contains the previous type (LDAP directory type) and not the Custom type
     as it is supposed to. Therefore, if you click OK or Apply in this panel (LDAP user registry), the
     old LDAP directory type (and hence the default filters of that directory) is saved resulting in your
     changes to the filters being overwritten. To avoid this you can do either of the following:
            o   Click Apply in the Advanced LDAP settings panel. Then, to proceed to another panel,
                use the navigation on the left. If the navigation is used to access the LDAP user
                registry panel you should see that the directory type is changed to Custom.
            o   Choose Custom type in the LDAP user registry panel. Click Apply and then change
                the filters by clicking the Advanced LDAP settings panel. In this scenario once the
                changes are completed you can click Apply or OK.
6.   The administrative console Lightweight Third Party Authentication help panel is not correct. See
     the security section for the correct information.
7.   When using the administrative console, do not change the name of the JDBC provider if you
     create it by selecting an existing JDBC provider from the menu. If you use a custom JDBC
     provider, for which you supply the provider information, this restriction does not apply.

8.   When you click Test Connection for a 4.0 data source that is created by WASPostUpgrade

     during a migration from WAS V4.0.x, the following exception displays:


     DSRA8040I: Failed to connect to the Data Source. Encountered:
     java.lang.NullPointerException


     This exception occurs with 4.0 data sources created by the WASPostUpgrade tool during
     migration which do not have any custom properties.
     To avoid receiving the exception, create a valid DB2 custom property on the data source. For
     example, create a description in the Custom Property panel.


9.   If you resize your Netscape browser, you could get a "Data Missing" error.


     The error message disappears in 60 seconds.


10. When connecting to the IBM WebSphere Application Server administrative console from a

     Netscape browser, resizing the browser can cause an error 404 message to occur. This

     situation occurs because the browser reloads the frame when resizing the window.


     To avoid getting the error message, you can refrain from resizing the Netscape browser window,
     or you can connect to the IBM WebSphere Application Server administrative console using an
     Internet Explorer browser.


11. You receive the following error messages when resizing Netscape Version 4.7:


     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)
                   ...


     After resizing Netscape 4.7, Netscape has to reload the page just as it initially loads the page on
     the first request. For pages that do not expect POST data, it is not a problem. But for pages that
     do, Netscape 4.7 cannot retain the data.




12. An error can occur when setting a trace specification from the administrative console if
     selections are made from both the Groups and Components lists. In certain cases, the
     selection made from one list is not lost when adding a selection from the other list. To work
     around this problem, enter the desired trace specification directly into the Trace Specification
     entry field.
13. If       you         need     to     create      a      Java      virtual     machine        (JVM)

     com.ibm.websphere.sendredirect.compatibility custom property and set it to true, create an

     additional server and install the application on the new server. The administrative application
     does not function properly when the com.ibm.websphere.sendredirect.compatibility property is
     set to true. The administrative application fails because the login URL is modified by adding a
    second /admin.


         o   To work around this problem, delete the second /admin from the URL in the browser.

14. While working with the right-hand panel of the administrative console to do administrative tasks,
    the browser screen blanks out intermittently.


    To work around this problem, do one of the following:


                  o After the problem occurs, close the Netscape browser, log in again,
                      and continue working.
                  o Use the Internet Explorer browser from a Windows machine.
                  o Use Netscape 7.x, Mozilla 1.x, Opera 5, or Konquerer browsers on
                      the platform, depending on which is available. Although there is not
                      formal support for these browsers, they have all been used
                      successfully with the product and in many cases work better than
                      the previous 4.7.x series of Netscape browsers.
15. If you create or update a data source that points to a newly created J2C authentication data
    alias, Test Connection fails to connect until you have restarted the deployment manager so
    that the J2C authentication data is reflected in the run-time configuration. Any changes to the
    J2C authentication data fields require a application server restart for the changes to take effect.
16. The ivt script fails when running under CCSID 5035 and the application server has not been
    started. The server is started, but the ivt tool fails to realize this and outputs failure messages.
    The workaround to this problem is to start the application server before invoking the ivt script.
17. When creating a new application server from an adminconsole of a server running under a
    profile other than QEJBSVR (for example, MYUSERID), the new application server's server
    directory and server configuration files are owned by the profile under which the application
    server is running (for example, MYUSERID), not QEJBSVR. When you attempt to start the new
    application server, it fails to start. The error message in the joblog states that the file
    variables.xml cannot be accessed.
    There are two possible workarounds for this problem:


         o   Use the administrative console to change the run-as profile for the new application
             server to the same userid being used for the first application server:
                  2. Expand Servers and click Application Servers
                  3. Click the link for the new application server
                  4. Scroll down and click Process Definition
                  5. Change the Run as user field
                  6. Click the Ok button
                  7. Save your configuration changes.
         o   Use the QShell command chown to make QEJBSVR the owner of the new directories
             and files created when you created the new application server:
                  9. STRQSH
                  10. chown                            -R                          QEJBSVR
                      instance_root/config/cells/cellname/nodes/nodename/servers/server
                          name where instance_root is the fully qualified IFS path name to
                          your instance (for example, /QIBM/UserData/WebAS5/Base/default),
                          cellname is the cell name for your instance (for example,
                          MYISERIES), nodename is the node name for your instance (for
                          example, MYISERIES), and servername is the name you specified
                          for the new application server when you created it.



Workstation Tools

  1.   When you are using the Application Assembly Tool (AAT) at an application level (EAR file),
       security roles are synchronized with the security roles defined for the application's embedded
       modules. If a security role is manually added to the EAR file, it can be automatically removed
       when the file is saved, if an embedded module does not reference the role or the role is in
       conflict with an existing role. In this case, the manually added role should be removed, but then
       all roles with the same name are removed. The role is automatically added again when the file is
       saved if it is still being referenced in an embedded module file. If a duplicate role is added in an
       embedded module file, all roles with the same name should be deleted by the user and the
       correct role manually read again.
  2.   When using the AAT to modify a session bean, if you change the bean type (stateful versus
       stateless), then you must click Apply before making any other changes to the same bean.
       Otherwise, various input fields on the GUI become inactive. You will know they are inactive,
       because they are grayed out on the GUI. After all the changes are made, click Apply again to
       commit the changes.
  3.   Read ahead hints are defined in the WebSphere Application Server Enterprise Assembly Tool
       by defining a path of container-managed relationships. The Version 5 and Version 5.0.1 of this
       tool incorrectly disallow the configuration of one-way relationships for read ahead hints. If an
       application has defined one-way relationships, these relationships will not be exposed in the list
       of available relationships to configure into a read ahead hint. This limitation is corrected in
       WebSphere Application Server, Version 5.0.2. Apply interim fix PQ73432 to the client machine
       to enable the configuration of one-way relationships into read ahead hints in WebSphere
       Application Server, Version 5 and Version 5.0.1.
  4.   When configuring a resource reference for an application client module in the Application
       Assembly Tool, the Type field pull-down menu lists javax.resource.cci.ConnectionFactory as an
       available resource reference. This type is not supported by 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
Data Access

  1.   When a new Websphere Application Server instance is created, a copy of the file

       /QIBM/ProdData/WebAS5/Base/config/templates/system/jdbc-resource-provider-tem


       plates.xml              is             copied              into               the             directory


       /QIBM/UserData/WebAS5/Base/<instance_name>/config/templates/system/ . This is a

       modifiable xml file that sets up the default custom properties values for JDBC connections
       obtained from a datasource. The ProdData version of this file will be copied to the UserData
       directory   so   new   datasources will    use     the   correct   default    values.   The    existing

       jdbc-resource-provider-templates.xml                      in                 the              directory


       /QIBM/UserData/WebAS5/Base/<instance_name>/config/templates/system/                            will   be

       renamed with the following format:


       jdbc-resource-provider-templates_<ISO date>.BAK


       where <ISO date> will be of the format '20030128'.
       Any previous user modifications made to this file will need to be merged into the new version of
       the jdbc-resource-provider-templates.xml file.


  2.   The DB2 Universal JDBC type 4 driver is supported in WebSphere Application Server, Version
       5.0.1. The minimum fix pack level is DB2 V8.1 FP1. The DB2 Universal JDBC type 4 driver does
       not support XA transaction and it is only supported in WebSphere Application Server, Version
       5.0.1 data sources. Although the DB2 Universal JDBC type 4 driver can be used to access
       both iSeries and non-iSeries DB2 databases, it is recommended that users continue using
       the IBM Developer Kit for Java JDBC driver (Native JDBC driver) for accessing the local iSeries
       database, and the IBM Toolbox for Java JDBC driver for accessing remote iSeries databases.
  3.   There is a known problem on mapping StaleConnectionException. When you see the following
       exception stack, it is mapped to StaleConnectionException:


       Error Code = 0
       SQL State = null
       com.ibm.db2.jcc.b.DisconnectException:      A    communication       error    has   been      detected.
       Communication protocol being used: {0}. Communication API being used: {1}. Location where
       the error was detected: {2}. Communication function detecting the error: {3}. Protocol specific
       error codes(s) {4}, {5}, {6}. TCP/IP SOCKETS Agent.sendRequest() OutputStream.flush()
       Connection reset by peer: socket write error * 0
       at com.ibm.db2.jcc.c.a.a(a.java:329)
       at com.ibm.db2.jcc.c.a.u(a.java:302)
4.   The following issue refers to the use of the DB2 Universal JDBC type 4 driver involved in
     non-iSeries DB2 database access.
     Deadlock results from accessing two different rows in a DB2 table when the next key is not
     locked for all INSERT and DELETE statements.


     To eliminate the deadlock, set the DB2_RR_TO_RS environment variable from the DB2
     command line window. Setting this environment variable causes the following:


         o    If RepeatableRead (RR) is your chosen isolation level, it is essentially downgraded to
              Read Stability (RS).
         o    If you chose a different isolation level and the DB2_RR_TO_RS environment variable
              is turned on, scans of the database skip rows that are deleted but not committed. This
              activity occurs even if the row qualified for the scan. The skipping behavior affects the
              RR, RS, and Cursor Stability (CS) isolation levels.
5.   When enterprise beans with container-managed persistent (CMP) types that have any
     VARCHAR FOR BIT DATA columns defined on a DB2 table are deployed in the DB2 universal
     JDBC type 4 driver to persist the data, an SQLException of illegal conversion is thrown at run
     time.


     This exception only occurs when you use the DB2 universal JDBC type 4 driver and with the

     deferPrepares property being set to true. When the deferPrepares property is set to true, the

     DB2 universal JDBC type 4 driver uses the standard JDBC data mapping.


     Currently, the generated deployed code does not follow the standard JDBC specification
     mapping. The failure at execution time is because of a problem in the tool that prepared the
     enterprise beans for execution.


     To avoid receiving this exception, choose one of the following options:



                  o Set the deferPrepares property to false in the data source

                       configuration.
                  o Do not use the DB2 universal JDBC type 4 driver if your table has
                       any VARCHAR FOR BIT DATA or LONG VARCHAR FOR BIT DATA
                       columns. Use the DB2 legacy CLI-based JDBC driver to persist the
                       data.
6.   Changes are made to the Java Database Connectivity providers in WebSphere Application
     Server V5.0.1.
     The following changes are made to the Java Database Connectivity (JDBC) providers in
     WebSphere Application Server V5.0.1:
                      WebSphere Application Server V5.0.1 provides a new JDBC provider for
                       DB2:DB2 Universal JDBC driver provider. Use this JDBC provider to test the
                       new DB2 Universal JDBC type 4 driver. This provider only supports 5.0 data
                       source in WebSphere Application Server, Version 5.0.1. To distinguish
                          between this new jdbc provider and the existing DB2 type 2 jdbc provider,
                          V5.0.1     changes      the     name       of       the   provider    in     the
                          jdbc-resource-provider-templates.xml file to match the provider with the
                          name.




                         It is recommended for performance reasons that users continue using the
                          IBM Developer Kit for Java JDBC driver (Native JDBC driver) for accessing
                          the local iSeries database, and the IBM Toolbox for Java JDBC driver for
                          accessing remote iSeries databases.




Servlets and JavaServer Pages (JSPs)

  1.   Performance changes to the WebSphere HTTP Plugins may result in InterruptedIOTimeout
       exceptions while reading large requests, such as receiving file uploads to a servlet.            To
       circumvent the problem, increase the Connection I/O Timeout value on the Web Container of
       your application server.


            Drill Down to Servers -> Application Servers -> <Server> -> WebContainer ->
                HTTP Transports -> <Transport>
                Click     Customer      Properties      and    add        a    property   named
                ConnectionIOTimeOut and set to the desired value (in seconds). Restart
                the application server for the changes to take effect.



Java Messaging Service

  1.   Limitation on creating more then 100 JMS enabled WAS 5.0 instances per system.


       For each new WAS 5.0, JMS enabled instance, a new queue manager gets created. For each
       queue manager, a corresponding library is created to keep track of the WMQ internals. Because
       the library name is restricted to ten characters on iSeries platform, the first 10 characters of the
       queue manager name is used to create the library. If this name collides with existing library, the
       last two characters are replaced by nn, where nn is 00, 01, 02 and so on. Queue managers
       created for WAS 5.0 instances are named WAS_nodename_servername (for example,
       WAS_MYISERIES_server1) which maps to QMWAS_MYIS for library name. This library
       naming rule limits the number of JMS enabled WebSphere Application Server instances to 100
       per iSeries, assuming the iSeries host name is four or more characters in length.
  2.   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.




Dynamic Caching

  1.   Placing the cachespec.xml file in the /QIBM/UserData/WebAS5/Base/<instance>/properties
       directory does not work at version 5.0.1. Please use the WEB-INF directory of your web
       module           as        outlined       in      the       documentation        found        at
       http://publib.boulder.ibm.com/iseries/v1r1m0/websphere/ic2924/info/rzaiz/50/program/servdync
       xml.htm
  2.   Existing instances (instance created prior to applying the group PTF for V5.0.1) remain
       unchanged. To enable ESI caching in an existing, do the following:


                             Either delete your plugin-cfg.xml file and
                             regenerate, or open the plugin-cfg.xml file in a
                             text editor and add the following element as a
                             child of the <Config> element: <Property
                             Name="ESIEnable" Value="true"/>



Sample Applications

  1.   WebSphere Application Server, Version 5.0.1 contains updates for the Samples. The updates
       contain a number of minor fixes to the original Samples that are shipped with the product. The

       Samples documentation update is located in the samples directory. This directory is located off

       of the root directory of where WebSphere Application Server is installed. The file name is

       readme.pdf. The document contains instructions for uninstalling the Version 5 Samples and

       installing the Version 5.0.1 Samples.
  2.   If your application server name is not server1, you will get an error while running the
       Point-to-Point and Publish and Subscribe Samples. You will need to complete the following step
       in addition to the Configure and Run steps to correct the problem.
       For Publish Subscribe sample:
           a.    Open                           the                       ear                       file
                 /QIBM/UserData/WebAS5/Base/<your-instance>/installableApps/MDBSamples.ear in
                 Application Assembly Tool.
           b.    Click on Application Clients -> PSSampleClient -> Resource Environment
                 Reference

           c.    For each resource (i.e. jms/news, jms/sport, jms/weather), click on Bindings tab.

           d.    Edit the JNDI name so that server1 is changed to to <your-server-name> where
                 <your-server-name> is the name of your server.
           e.    Save your changes
            f.   Start the Administrative console
            g.   Go to Resource -> WebSphere JMS -> Topic Destination
            h.   Select the "Sample.JMS.listen" Topic Destination
            i.   Change the entry for Topic from "Sample/JMS/listen" to "Sample/JMS/#" .
            j.   Save your changes




     For Point-to-Point sample:


            k.   Open                           the                          ear                           file
                 /QIBM/UserData/WebAS5/Base/<your-instance>/installableApps/MDBSamples.ear in
                 Application Assembly Tool.
            l.   Click on Application Clients -> PtoPSampleClient -> Resource Environment
                 Reference

            m. For each resource (i.e jms/Q1, jms/Q2), click on Bindings tab.

            n.   Edit the JNDI name so that server1 is changed to <your-server-name> where
                 <your-server-name> is the name of your server.
            o.   Save your changes
3.   If your instance is not using the default ports for the bootstrap and Soap connector ports,

     additional parameters are required to override the default ports when using the launchclient

     command for the Point-to-Point and Publish and Subscribe Samples.The additional parameters
     are:

     -CCBootstrapPort=<boot strap port>


     -CCsoapConnectorPort=<soap connector port>

4.   The Samples gallery font in languages other than English might appear small, depending on the
     browser you are using. To work around this problem, increase the browser font settings.
5. Known PetStore problems
            a.   Creating new account causes duplicate key exceptions. New accounts can be created
                 several ways in Pet Store. If "Account" is selected from a Pet Store screen, before a
                 user has signed in, they are presented with the option of signing in or creating a new
                 account. If a new account is created in this flow, it will fail with duplicate key exceptions.
                 To create a new account select "Sign in" from a Pet Store screen, new accounts in this
                 scenario can be created.
            b.   Passwords are not compared when creating a new account . When creating a new
                 account, a password must be provided. The first "Password" field is not compared for a
                 match with the second "Password (Repeat)" field.
            c.   Account information is displayed incorrectly. Your account information is displayed
                 when "Account" is selected or during the check out process. First and Last name are
                 switched, the Credit Card Name shows the expiration date, and Expiration Date shows
                 the wrong date.
            d.   The Pet Store Item screen shows a picture of the product to be purchased a long with a
                "List Price" and "Your Price". The list price is greater than your price. Items added to
                the shopping cart are added with the more expensive "List Price".
           e.   When an item is added to the shopping cart it is added with an initial quantity of one.
                That quantity can be adjusted to a higher number in the shopping cart. If that same
                item is re-added to the shopping cart, the adjusted quantity is reset to one.
           f.   The option to forcefully repopulate the Pet Store database fails with an internal server
                error (HTTP 500 - The page cannot be displayed). Refrain from using this option.
           g.   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,
                the URL of Pet Store Catalog DAOSQLURL needs updating 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.



Web Services

       Universal Description, Discovery, and Integration Registry
       component (UDDI)

  1.   Universal Description, Discovery, and Integration 4J (UDDI4J) is a class library that provides an
       API used to interact with a UDDI Registry.



       Two class libraries are provided for UDDI4J in the /QIBM/ProdData/WebAS5/Base/lib

       subdirectory:



           o    uddi4j.jar supports Version 1 of the UDDI API. This is provided for compatibility with

                applications that have been written using UDDI Version 1, and the classes in this class
                library are deprecated.

           o    uddi4jv2.jar supports Version 2 of the UDDI specification. The class in this library

                should be used by any application using UDDI4J to communicate with a Version 2
                UDDI-compliant registry.
  2.   Version 5.0.1 contains updates to the UDDI and Web Services Gateway applications. After
       updating to 5.0.1, you will need to update these applications to the newer level, using the
       following steps:
           a. If you have WebSphere Gateway installed (specifically, the wsgw, wsgwsoap1, or
                wsgwsoap2 applications), back up the following gateway configuration files to a secure
                location, for later restoration. You can find these files on each application server on
                which the gateway has been installed.
                          /QIBM/UserData/WebAS5/<edition>/<instance>/installedApps/node_name/w
                       sgwsoap1.ear/wsgwsoap.war/DeployedServices.ds
                      /QIBM/UserData/WebAS5/<edition>/<instance>/installedApps/node_name/w
                       sgwsoap1.ear/wsgwsoap.war/wsgwsoap.channelname.cfg
                      /QIBM/UserData/WebAS5/<edition>/<instance>/installedApps/node_name/w
                       sgwsoap2.ear/wsgwsoap.war/DeployedServices.ds (if installed)
                      /QIBM/UserData/WebAS5/<edition>/<instance>/installedApps/node_name/w
                       sgwsoap2.ear/wsgwsoap.war/wsgwsoap.channelname.cfg (if installed)
                      /QIBM/UserData/WebAS5/<edition>/<instance>/installedApps/node_name/w
                       sgw.ear/wsgw.war/wsgw.cfg


              where <edition> is Base if you are using WebSphere Application Server or ND if you
              are using Network Deployment, and <instance> is the name of you WebSphere
              instance.


         b. Use the WebSphere Application Server administrative console to stop and remove the
              following enterprise applications, if installed:
         c. wsgw (note that this may be installed with name WSGW G110.L021030.ear)
         d. wsgwsoap1 (note that this may be installed with name WSGW Apache SOAP Channel
              G110.L021030.ear)
         e. wsgwsoap2 (note that this may be installed with name WSGW Apache SOAP Channel
              G110.L021030.ear)


         f.    Reinstall the wsgw, wsgwsoap1, and wsgwsoap2 applications desired using the
              product documentation.
         g.    Restore the gateway configuration files that you backed up in step 1, by copying them
              back to their original locations. Replace any files of the same name that were created
              when the enterprise applications started. If you have not used the RST command to
              back up these files, ensure the authorities are correct.
         h.    Use the WebSphere Application Server administrative console to update the following
              enterprise applications, if installed:
              UDDIRegistry (note that this may be installed with name UDDI Registry.ear)
              wsgwauth (note that this may be installed with name WSGW Authorization Application
              G110.L021030.ear )
              wsgwcorr (note that this may be installed with name WSGW Correlation
              G110.L021030.ear)
         i. Restart the application that were updated or reinstalled.
3.   When the Web Services Technology Preview is installed with the Web Services Security
     options selected, the Web Services invocation fails with the following errors:


     Server side exception when invoking the Web Services:


     [3/13/03 11:30:28:641 CST] 7d090dc5 WebGroup                        E SRVE0026E: [Servlet
     Error]-[com.ibm.ws.security.core.SecurityContext: method
     getCurrent()Lcom/ibm/ISecurityLocalObjectBaseL13Impl/CurrentImpl; not
     found]: java.lang.NoSuchMethodError:
      com.ibm.ws.security.core.SecurityContext: method
      getCurrent()Lcom/ibm/ISecurityLocalObjectBaseL13Impl/CurrentImpl; not
      found


      On the client side, the following default is returned:


      AxisFault
       faultCode: {http://xml.apache.org/axis/}HTTP
       faultString: (500)Internal Server Error
       faultActor: null
       faultDetail:
               null: return code: 500
      Error 500: com.ibm.ws.security.core.SecurityContext: method
      getCurrentt&#40;&#41;Lcom/ibm/ISecurityLocalObjectBaseL13Impl/CurrentI
      mpl&#59; not found


      The reason for these errors is that the WebSphere Application Server security run time in
      WebSphere Application Server Version 5.0.1 is updated but the Web Services Technology
      Preview is not.


      Complete the following action to avoid receiving the errors:


          o    During installation of Web Services Technology Preview, do not select Web Services
               Security options.



HTTP Server

 1.   Communication between the HTTP server plugin and WebSphere application server can be
      done via HTTP or HTTPS. The additional products necessary to run with HTTPS may or may
      not already be installed on the iSeries. If the following message is in the HTTP server job log,
      the WebSphere HTTP server plugin detected it has been configured so it should use HTTPS
      when communicating with the app server, however, the required products for HTTPS
      communication were NOT installed on the iSeries.


      Joblog message:


               Plugin will continue to startup, however, SSL transport did not
               initilize. Secure communication between app server and plugin
               will NOT occur. To run with SSL, additional products may need to
               be installed: 1) OS/400 Digital Certificate Manager (5722-SS1 or
               5769-SS1, option 34) 2) Cryptographic Access Provider
               5769-AC1 (40-bit), 5722-AC2 or 5769-AC2 (56-bit), 5722-AC3 or
               5769-AC3 (128-bit)
Security

  1.   The Domino 6.0 LDAP server is not currently supported as a user registry. Single sign-on
       between a WebSphere application server and a Domino 6.0 server is not currently supported.
       Using a Domino 5.0 LDAP server as a user registry is supported. Single Sign-on with Domino
       5.0 is supported.
  2.   When you specify Domain Qualified User Name from the Security > Global Security

       configuration panel, the runtime call to getCallerPrincipal() from an enterprise bean returns the

       qualified name with the realm prepended twice. For example, the format return is

       realm/realm/user. You can strip the first realm from the returned value when making API calls.


       The servlet API getUserPrincipal() works correctly.

  3.   If   your   application     uses    the    java.net.URLConnection       class    it   may     throw
       java.lang.NullPointerException                                                                  with
       com/ibm/ws/orbimpl/transport/protocol/https/HttpsURLConnection.connect() contained in the
       exception stack. The solution is to remove the URL provider (Samples URL Provider - https)
       from your WebSphere configuration. Use the administrative console to open Resources-> URL
       Providers, then select Server and click the Apply button. Then delete Samples URL Provider
       -https, save the configuration, and restart the application server.
  4.   The IBM Java Secure Socket Extension (JSSE) is currently not supported within applets.
  5.   When Java 2 Security is enabled in the Global Security settings, the installed SecurityManager
       does not currently check modifyThread and modifyThreadGroup permissions for non-system
       threads.


       You can use Web applications and EJB application code to create threads and access to the
       following thread class methods: stop, suspend, resume, setPriority, setName, and setDaemon.


       Allowing Web and EJB application code to create or modify a thread can have a negative impact
       on other components of the container and can affect the capability of the container to manage
       enterprise bean life cycles and transactions.


  6.   The Java Authentication and Authorization Service (JAAS) login configuration entries in the
       Security Center are propagated to the server run time when they are created, not when the
       configuration is saved.


       However, the deleted JAAS login configuration entries are not removed from the server run time.
       To remove the entries, save the new configuration, then stop and restart the server.


  7.   Web client certificate authentication is not currently supported when using the local operating
       system (LocalOS) user registry. However, Java client certificate authentication does work with
       LocalOS. Java client certificate authentication maps the first attribute of the certificate domain
       name to the user ID in the LocalOS user registry.
     Even though Java client certificates work properly, the following error displays in the

     SystemOut.log file:



     SECJ0337E: The mapCertificate method is not supported


     The error is intended for Web client certificates, but also displays for Java client certificates. You
     can ignore this error for Java client certificates.


8.   When specifying identity assertion on the CSIv2 Authentication Outbound panel, you must also
     select basic authentication as supported or required on the CSIv2 Authentication Outbound
     panel. This action allows the server identity to be submitted, along with the identity token, so
     that the receiving server can trust the sending server. Without specifying basic authentication as
     supported or required, trust is not established and the identity assertion fails.
9.   Do not use the forward slash character (/) in the alias name when defining JAAS login
     configuration entries. The JAAS login configuration parser cannot handle the forward slash
     charact
10. 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




11. In WebSphere Application Server, Version 5.0.1, 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 W ebSphere 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 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 deployment manager.
    Another example is that a request fails when a WebSphere Application Server, Version 5.0.1
    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 system does not fail.


    To ensure the interoperability between WebSphere Application Server, Version 5 and Version
    5.0.1, 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.



12. Grant entries specified in the app.policy and was.policy files must have a code base defined. If

    there are grant entries specified without a code base, the policy files are not loaded properly and
    the application can fail.



    If the intent is to grant the permissions to all applications, then use file:${application} as a code

    base in the grant entry.
 13. When specifying identity assertion on the CSIv2 Authentication Outbound panel, you must also
      select basic authentication as supported or required on the CSIv2 Authentication Outbound
      panel. This action allows the server identity to be submitted, along with the identity token, so
      that the receiving server can trust the sending server. Without specifying basic authentication as
      supported or required, trust is not established and the identity assertion fails.
 14. Several release notes follow that relate to how IBM WebSphere Application Server, Version 5
      exposes the JAAS Subject object and WSPrincipal interface.
          o    The Subject object that is generated by the WSLoginModuleImpl instance and
               WSClientLoginModuleImpl instance contains a principal that implements the
               WSPrincipal interface. The getCredential() method of a WSPrincipal object returns an
               object that implements the WSCredential interface. You can also find the
               WSCredential object instance in the PublicCredentials list of the subject instance. It is
               recommended that you retrieve the WSCredential object from the PublicCredentials list
               instead of using the getCredential() method.
          o    The Subject object generated by the J2C DefaultPrincipalMapping module contains a
               resource principal and a PasswordCredentials list. In the present implementation the
               resource principal represents the caller. See the article entitled, "Develop your own
               J2C principal mapping module"



Trace/Debug

 1.   Upon starting the Log Analyzer for the first time or after the Log Analyzer preferences files of the
      users have been deleted, the following message displays in the Log Analyzer's shell window:

      Cannot open input stream for waslogbrsys

      This message is an informational message. You can disregard the message because it does not
      affect the execution of the Log Analyzer.
 2.   For Windows platforms, you can only access the Log Analyzer help files using the operating
      system's default Internet browser. You cannot access the help files using any Internet browser,
      even though there are options allowing you to select either Netscape or Internet Explorer and
      set the location of the browser to display HTML help files.
      For UNIX platforms, you can access the help files using any Internet browser, such as Netscape
      Navigator, by explicitly setting the location of the browser's executable in the tool's Preferences
      dialog. The option that seemingly allows you to select either Netscape or Internet Explorer as
      the browser to display HTML help files is not used.
      To specify the browser on UNIX platforms:
      In the Log Analyzer tool, select File > Preferences. In the Log Analyzer Preferences dialog,
      select Help from the General folder. Set the path to the Internet browser's executable in the
      Browser Location field.
 3.   WebSphere Application Server includes the following Log Analyzer files for use with the
      WebSphere Commerce Suite:
          o    install_root\bin:
                        wcslogbr.bat
                        wcslogbrsys.cfg
                           wcslogbrsys.ini
            o    install_root\properties\logbr:
                           wcsanalyzers.xml
                           wcslogtypes.xml
                           wcsrecdef.xml


       You can ignore these files.




National Language Version Issues/Limitations

  1.   The help search in the administrative console does not return search results for Latin-1 terms
       that contain diacritical markings (for example, German "für", 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").
  2.   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 (CCSI) used by the embedded messaging queue manager.


       To work around this problem, 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.
       Look for a table in the manual with a list of locale and language to CCSI mappings supported by
       the queue manager. Then, 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.


  3.   Known problems or limitations for Workstation Components are the following:
            a.   Readme and PDF install for Traditional Chinese and German languages can not be
                 accessed through the LaunchPad. These files can be viewed through any Web
                 browser.
                 The Readme for Traditional Chinese is located at:

                 <cd drive>\readme\readme_zh_tw.html

                 The install PDF for Traditional Chinese is located at:
     <cd drive>\doc\installguide_zh_tw.pdf


     The Readme for German is located at:

     <cd drive>\readme\readme_de.html

     The install PDF for German is located at:

     <cd drive>\doc\installguide_de.pdf

b.   Help links for Application Assembly Tool, Application Resource Client Tool and Tivoli
     Performance Viewer bring up the English version of the files. To work around this
     problem, change the path to the preferred language version to display the appropriate
     language (include list for languages if possible) list separately if the paths are not the
     same.
c.   The following steps are workarounds to evaluate WebSphere Application Server and
     WebSphere Application Server Network Deployment Version 5 on National Language
     Version operating systems.
             Windows NT:
                   1.   Open Regional Settings from NT Control Panel.
                   2.   Change the setting to English (United States) on Regional
                        Settings, and then select 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 WebSphere Application Server Version 5.


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


             Windows 2000:
                   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 WebSphere Application Server Version 5.


              Note: 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 following command before you install the
            WebSphere Application Server Version 5.



            # export LANG=en_US



   Note: Every time you open a new terminal, you need to invoke the above
    command.
   Solaris Operating Environment 8:
           Open Terminal and run following command before you install the
            WebSphere Application Server Version 5.


            # LANG=en_US
            # export LANG


   Note: Every time you open a new terminal, you need to invoke the above
    command.

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:256
posted:2/4/2010
language:English
pages:26