This document contains the Release Notes for the WebSphere Application Server
Version 3 Release 5 for Windows NT (Windows 2000 tolerated), Sun Solaris, AIX and HP-UX.
These Release Notes cover the Advanced and Standard Editions.
Since the Standard Edition functions are a subset of the Advanced Edition functions,
note that some information in these Release Notes (for example, the mention of enterprise
beans) should not imply that the function is available in the Standard Edition.
Version 3.5 focuses on usability improvements and installation enhancements.
Note: The links below will work if you are viewing the Release Notes
from within the full InfoCenter documentation interface.
The Release Notes contain information about known defects and the workarounds.
This document also includes some supplemental information for topics covered
in the Application Server documentation.
These notes will be updated periodically.
Problem |
Op System |
Workaround |
When you try to install WebSphere Application Server from the CD-ROM,
the operating system may create a directory called ADV_SUN_128#2. This
results in the product not installing, and you receive the error message Exception
in thread "main" java.lang.NoClassDefFoundError: Installer . |
Solaris |
Delete the ADV_SUN_128 directory if it exists. Then, using the
mv command, rename the ADV_SUN_128#2 directory to ADV_SUN_128. |
If you are using DB2 with WebSphere Application Server, you will not be
able to open DB2 connections unless your machine's kernel parameters are set properly. |
Solaris |
Open an editor on your machine's /etc/system file and add the following
parameters:
set semsys:seminfo_semume = 200
set semsys:seminfo_semopm = 200
After you add the parameters, reboot your machine. |
Using Oracle or Sybase as the repository, you will get
an exception when trying to use DB2 as the bean datasource. If you use DB2 as the repository, you can use
all the databases as the bean table, since they all are running on the same machine. This
problem occurs when you are setting up your environment. |
AIX, Solaris |
To alleviate this problem, add the following to your startupServer.sh
LIBPATH and LD_LIBRARY_PATH:
. $DB2_INSTANCE_NAME/sqllib
/db2profile
$DB2_INSTANCE_NAME/sqllib/java12
$DB2_INSTANCE_NAME/sqllib/lib
Note: It is not easy to modify the startupServer.sh file, because all of the settings
are based on DB_TYPE and DB_INSTANCE_HOME, which are specified during installation. You cannot
specify more than one DB type during installation. |
To install JDBC driver for your WebSphere Application Server
node, you must define the file that contains the necessary Java code for your DB2 database. |
Windows NT/2000 |
To enable use of JDBC 2.0, you need to run the
c:\SQLLIB\java12\usejdbc2 program to define DB2 for using jdbc2.0. To verify
which program is in use, look at the "inuse" file in the same directory.
|
Whenever Hotjava Web browser is not properly configured, and
the check box to open the Readme file after installation is checked, but the file does not open. |
Solaris |
Check to make sure you can start the Hotjava browser. If not,
manually start another browser, such as Netscape, and then view the Readme file. |
Because of an AIX limitation, Java applications will not run
reliably where the LIBPATH length exceeds 1548 characters. |
AIX |
Reduce the LIBPATH length to less than 1548 characters. |
The Java Development Kit version installed on your system is not
supported. |
All |
The installation program on the Application Server installation
CD (not the download) will detect the unsupported version and install the correct version of Java
in a private subdirectory. |
IBM HTTP Server fails to install or start. |
All |
Try the installation again. Enter a valid user id and password
(null password will not work) on the Security panel. Also, choose the IBM HTTPServer plugin; this
configures the HTTPServer to work with WebSphere. |
The WebSphere Application Server installation program
installed a Java development kit, but cannot find it. |
AIX, Solaris |
Set the JAVA_HOME environment variable to:
- on AIX:
/usr/jdk_base
- on Solaris:
/usr/java1.1
Then run the installation program again. |
If you are using Apache HTTP Server and install WebSphere Application
Server with the Apache plug-in, you may not be able to start the Apache Web server again.
The plug-in installation added the line ose.mod=out to your Apache configuration
file srm.conf in the /<apache_home>/conf directory. |
All |
Open an editor on the srm.conf file, and remove or comment out the
ose.mode=out line. |
Under stress, some browser connections
may be refused (error 500) when attempting to access servlets and JSPs.
The Web server log may contain the errors:
Aug 30 14:52:53 1999 -
Error -
ws_open_domain_client_socket
connect return 146 error
Mon Aug 30 14:52:53 1999 -
Error -
Ws_open_domain_client_socket
socket return 146 error |
Solaris |
The default communications configuration
between the Web server and the servlet engine is using TCP/IP sockets. Each socket
represents a file descriptor. If the file descriptor limit per process is set too low,
attempts to open socket connections may be refused (error 146). To resolve this
condition, increase the file descriptor limit for the user from which
the Administrative Server is started (normally root). Edit the .profile for
the user, and add the following:
ulimit -n 1024
Depending on the number of connections needed, this number may need to be
increased more. For this change to take effect, you do not have to reboot.
Just logoff and then logon again.
To change the hard upper limit of the number of file descriptors in the
kernel (which defaults to 1024 per CPU), you can, on Solaris, edit the
/etc/system config file to include a couple of entries:
set rlim_fd_max=4096
set rlim_FD_cur=1024
After you change this file, you must reboot for the changes to take effect.
|
Using Oracle, you get a TransactionRolledBackException
message when you try to create a model. |
All |
Increase values of Oracle database initialization parameters
open_cursors to 200. See the WebSphere Application Server InfoCenter configuring
databases section for details. |
You are installing the WebSphere Application Server and the
Administrative Server fails to start if the installation path contains a space (for example,
c:\Program Files\WebSphere\AppServer). |
Windows NT/2000 |
Install the product in a directory that does not contain a space. |
Even though you are logged in as root, the installation of
WebSphere Application Server fails with an error statement that the user does not have root
authority. |
Solaris |
Make sure the "whoami" command or /usr/ucb is in the
path for the root logon. |
When doing a native (silent) installation of WebSphere
Application Server, you cannot select more than one plug-in. |
AIX, Solaris, HP-UX |
Use the Java (GUI) installation program. You can select more
than one plug-in to install. |
A migration tool for a native (silent) installation of WebSphere
Application Server is not provided. |
AIX, Solaris, HP-UX |
Use the Java (GUI) installation program and the migration tool
provided with it. Or, migrate your files independently of a tool. |
Problem |
Op System |
Workaround |
The WebSphere Application Server does not start, and
you receive the following /logs/tracefile error:
FATAL Failed to create a
data source:
{0} COM.ibm.db2
.jdbc.app.DB2Exception:
[IBM][CLI Driver] SQL1031N
The database directory cannot
be found on the indicated
file system. SQLSTATE=58031
|
All |
Create the WAS database. On Solaris and AIX, run the shell file
createdb2.sh.
On Windows NT, the script is started automatically after you reboot. If the script file
fails, start the database, then run the createdb2.bat file. The results are logged in the
wasdb2.log file.
|
If there is not a blank line at the end of the admin.config file,
the Administrative Server fails to start. The tracefile is created, but it contains no message.
On Windows NT/2000, the Services panel reports The IBM WS AdminServer service returned
service specific error 10. |
All |
Add a newline character to the end of the
admin.config file in the \WebSphere\AppServer\bin directory. |
If you choose to use an ID other than root to run the WebSphere
Application Server before starting the AppServer, you need to enter the following from
a command line:
su - root
cd /tmp
rm .asibm*
If you do not do this, you will receive the message Server internal error
from the browser when you run the servlet. You will also get the following message in
your_server-stderr.log:
open_unix_domain_server_socket_listener
- bind/listen: The socket name is
already in use.
com.ibm.servlet.engine.oselistener
.outofproc.ServerQueueException:
Error: create_server 2
|
AIX |
|
When logged in other than as root, you could not run
the administrative server (adminServer). |
Solaris |
Log in as root and try running adminServer again. |
When logged in other than as root, you could not run
the administrative server (adminServer) in the background. |
Solaris, AIX, HP-UX |
Run adminServer again, only in the foreground. For Solaris,
log in as root before running adminServer. |
When logged in other than as root, you could not run
the ServletRedirector. |
Solaris, AIX, HP-UX |
Log in as root and try running the ServletRedirector again. |
You will have trouble starting a secured (that is, security is
enabled) administrative server or an application server on a Windows NT machine, if this
Windows NT machine is configured as a part of a Windows NT domain and is not connected
via the network to the domain server.
|
Windows NT/2000 |
Configure the Windows NT/2000 machine so that it is not part of a
Windows NT/2000 domain. |
If you are using IBM HTTP Server and, with WebSphere Application
Server installed, you use the IHS Module Sequence form to change IHS settings, you may not
be able to stop or restart IHS. The error message displayed is Invalid command 'LoadModule' .
Using the Module Sequnce form added unwanted commands to the IHS httpd.conf file. |
All |
Open an editor on the IHS configuration file httpd.conf and remove
the following commands:
ClearModuleList
LoadModule ibm_app_server_module<path for mod_ibm_app_server.dll> |
Problem |
Op System |
Workaround |
If you do not select the Administrative Console during installation,
you can still run the adminclient.bat file, and an Administrative Console will start. It will
not contain the correct data. The Topology view shows green 'objects' listed, but they are not
valid objects. They appear to be EJB-related methods. |
Windows NT/2000 |
Uninstall WebSphere Application Server and reinstall it, including
the Administrative Console. An alternative is to install the Administrative Console on another
machine and administer it from that machine. |
Screens may not repaint or resize properly when the Administrative
Console is run on a UNIX operating system that uses Exceed as its X window display. The result is
that sometimes the window may appear to be empty or missing panes. When you manually resize the
window, the rest of the text/widgets appear. This problem seems to appear when using the
Administrative Console with Hummingbird Exceed Version 6.0.1. |
Windows NT/2000 |
Do one of the following:
Note: Hummingbird Exceed Version 6.2.0.18 and higher will also work. Follow the
above instructions for configuring the window manager. Exceed requires a patch to work.
Without the patch, windows are incorrectly sized. With the patch, some of the error and
message dialog boxes still have clipped edges, so you need to manually resize these windows.
Contact Robek Corporation for a patch to get to Exceed Version 6.2.0.18 or higher. To
determine the Exceed patch level you need:
- Open the Exceed Xconfig tool.
- Open Troubleshooting.
- In the Troubleshooting window, click the View button. The version is listed at the
top of the Exceed log. For example, after applying the patch Exceed.exe 6.0.2.18, in the
Exceed.log file, the version will be listed as 6.2.0.18.
|
Left frame resizing. Sometimes, when resizing the left
panel, the panel gets squashed (smaller), and then becomes unable to be resized. |
All |
This usually can be alleviated if you click the Topology
view, then resize the left panel. |
The addition to the Administrative Console (GUI) for XML import
did not include some features of the command-line utility. This adversely affects security,
which requires the variable substitution feature of XML import to replace password variables
in the XML file with actual values. Instead, password variables are exported and are
expected to be replaced during import. This would limit password exposure to a single time
while invoking the import command.
Security configuration areas affected by this password limitation include administrator
access, LTPA, LDAP, and enterprise application identities.
|
All |
Use the XMLConfig command line utility for security configurations
that include passwords. |
When you invoke the WebSphere Control Program (wscp) without
specifying the -p option, the property file <home_directory>/.wscprc is loaded (if it exists,
where <home_directory> is the value of the Java property user.home). Note that the value of
can differ depending on the JDK version level. On Windows NT/2000, the JDK 1.2.2 sets the user.home
property based on the value of the USERPROFILE environment variable. |
All |
|
If a resource is deleted and re-created in the WebSphere Application
Server Advanced Edition Administrative Console, the change is not immediately reflected in
the WebSphere Control Program (wscp). You must explicitly refresh all object references in
the repository cache by issuing a "wscp list" operation for the object type of the instance.
Alternatively, exiting and re-invoking the WebSphere Control Program (wscp) also refreshes
the cache. |
All |
To avoid problems due to inconsistent cached information, avoid
issuing concurrent operations on the same object from within the WebSphere Control Program (wscp)
and the console. |
Before working with the WebSphere Administrative Console, wait until the message
Console ready appears and the new status icon changes from its In progress state to
Ready. For example, if you try to start the default server before seeing the Console ready message,
there may be some errors at the WebSphere Administrative Console. |
All |
Do not start servers until the Console ready message appears. |
Problem |
Op System |
Workaround |
Enterprise Bean clients must have access to server-side
exception classes to interpret server-side exceptions in stack traces. |
All |
Examine the server-side trace logs for the complete
error information or make server-side classes available on the client. |
The Jetace tool issues a java.lang.NoClassDefFoundError
message when loading a JAR file. |
All |
When using the Jetace tool, make sure all
dependent classes (and dependencies those classes have) are on the classpath. |
The documentation on writing enterprise beans with bean managed
persistence (BMP) needs correcting.
|
All |
See "Chapter 9: More-advanced programming concepts for enterprise
beans" in the PDF file adswpg00.pdf and in the HTML file atswpgad.htm. In Figure 64, the lines:
getEnvProps();
ds = initContext.lookup("jdbc/sample");
should be in the setEntityContext method (similar to Figure 61) rather than in the constructor.
This is because the getEnvProps method needs the context to be set which is not yet set
in the constructor. Since the container invokes the setEntityContext method to set the context,
the other two methods, getEnvProps and lookup, can be safely done there. |
Because of application programming practices, an application
getting an enumeration of objects from an enterprise bean gets fewer than the expected number
of objects. |
All |
Whenever possible, invoke entity bean finders and
the iteration through a resulting enumeration within a single transaction. Some benefits are:
- Iteration through the enumeration will be 2-4 times faster if done within the
the same transaction in which the find method was invoked.
- Consistency will be maintained; otherwise, iteration through an enumeration obtained
from a finder may return unexpected results if done with no transaction. This is
because concurrent access to the beans may have changed their data between the
time the enumeration was constructed and the time at which it is consumed.
If an entity bean finder is invoked within one transaction (for example,
a transaction which a client started via UserTransaction or from a TX_REQUIRED
session bean method), the resulting enumeration must be consumed within
the same transaction. The result of a finder becomes invalid once the
transaction completes.
The following is an example of finder usage which does not meet the above requirement:
UserTransaction tx = ...;
tx.begin();
Enumeration e = myEntityHome
.findGreaterThan(100);
tx.commit();
while (e.hasMoreElements()) {
....
}
The code should be rewritten as follows:
UserTransaction TX = ...;
tx.begin();
Enumeration e = myEntityHome
.findGreaterThan(100);
while (e.hasMoreElements()) {
...
}
tx.commit();
Though not recommended, the following works, but with no
guarantee of transactional consistency:
UserTransaction TX = ...;
tx.begin();
...
tx.commit();
Enumeration e = myEntityHome
.findGreaterThan(100);
while (e.hasMoreElements()) {
...
}
|
A ClassNotFoundException is thrown during deployment of a bean
that references another bean. |
All |
If a bean in one JAR file references a bean in another JAR file,
the WebSphere Administrative Server needs to know the location of the first bean in order
to deploy the second bean; otherwise, a ClassNotFoundException will occur when you attempt
to deploy the second bean. For example, if bean B in one JAR file references bean A in another
JAR file, deploy bean A first, and add the full path for the deployed JAR file to the node's
Dependent Classpath before deploying bean B. |
Data in non-persisted fields of an entity bean is not maintained
across transactions. |
All |
Entity beans should not rely on data stored in non-persisted fields
(particularly, references to other beans) being maintained across multiple transactions. Entity
bean instances are stored in an object pool between transactions. Each time a new transaction
begins, it retrieves one of the entity bean instances in the pool and loads persisted data for
the requested bean. Non-persisted fields may contain values set by a different bean used previously.
If necessary, you can reinitialize the data in the non-persisted field in the bean's ejbLoad() method. |
There are some isolation level restrictions when working with
enterprise beans. |
All |
- When using UserTransaction to begin a transaction, the isolation level seen by the container
will always be TX_REPEATABLE_READ.
- Since it is illegal to change isolation levels within a transaction, all beans touched by
the transaction must also be marked TX_REPEATABLE_READ.
- The only time at which the programmer has control over the isolation level used on a JDBC
connection is when he writes persistence code himself (BMP). Under all other conditions,
the runtime will use the container's concept of isolation level for the DB connection (meaning
the level declared in the deployment descriptor, or TX_REPEATABLE_READ for transactions
begun via UserTransaction).
- Oracle does not support TX_REPEATABLE_READ. Attempts to set the isolation
level to anything other than TX_READ_COMMITTED or TX_SERIALIZABLE when
running with Oracle will result in the connection manager silently defaulting
the database connection to TX_SERIALIZABLE, regardless of which isolation
level the container may specify. (This means that transactions begun
via UserTransaction will not fail on Oracle, though they will run at
a higher isolation level than the default TX_REPEATABLE_READ.)
|
After deploying an entity enterprise bean, starting the bean or
starting the server that it is installed under results in a failure to create the bean's
persistent table in the relational database.
|
All |
The names used for the persistent data within the enterprise bean
are used as the column names in the relational database. Make sure that the column names are
allowed in your particular relational database. Also, make sure that the Java data types used
by your enterprise beans have a supported mapping to a data type within your relational
database. |
In an inheritence hierarchy involving CMP beans, using the
results of an enumerated finder outside the transaction the finder was run in may lead
to results which violate the inheritence behavior. The behavior may be described by the
following scenario:
Consider an inheritence hierarchy involving the CMP beans Bean P (Parent) and Bean C (child).
Assume that there is one instance of P (P1) and one instance of C (C1). An enumerated finder
on P will return P1 and C1. However, attempts to use C1 outside the transaction in which the
finder was run would result in its behaving like an instance of P (ie, the methods would have
P's behavior, not C's behavior).
|
All |
Clients should start a transaction before running enumerated
finders on CMP hierarchies, and should use the results of the finder within the same
transaction. If this is done, using the scenario on the left, attempts to use C1 will
demonstrate C's behavior, as expected, instead of P's behavior. |
Problem |
Op System |
Workaround |
Using Oracle as a data source for an entity bean can cause clients
that attempt to access the bean to hang. This occurs if you start the bean with the Create
Table option checked in the DataSource tab on the Administrative Console, when an empty table
for the bean already exists in the Oracle database. |
All |
To avoid this, either uncheck the Create Table option for the bean,
or drop the table from the Oracle database before starting the bean. |
You use Oracle as a repository for the Administrative Server
and DB2 as the database access, when you deploy CMP bean to use the DataSource, you get in
the error log:
.java.sql.SQLException:
No suitable driver
|
All |
At the WebSphere Administrative Console:
- Go to the Topology view.
- Select the Application Server on which the bean is created.
- Go to the General tab in the property sheet on the right pane.
- Left click on Environment property.
- In the Property Editor, enter:
- For Variable Name
- PATH
- For Value
- x:\SQLLIB\BIN (x is where DB2 is installed)
- Click Add and then OK.
- Click Apply in the Application Server property sheet.
- Now, start the default server.
|
Sybase JDBC driver with JTA enabled. With JConnect 5.2, you cannot
create a table using the JDBC driver with JTA enabled. |
All |
Create the table with the JTA flag off, and then access the table with
JTA on. A case (number 10636211) is opened on this issue with Sybase. |
If you are using Sybase as a data source for an entity bean, the
table cannot be created, and the bean will not start if the entity bean has Create Table checked
in the DataSource tab on the Administrative Console (but the table already exists in the Sybase
database). The following SQL exception is thrown:
com.sybase.jdbc2.jdbc
.SybSQLException: A table cannot
have more than one primary key,
attempt to define a second primary
key failed on table
'EJB.AccountBeanTbl'.
|
All |
Uncheck the Create Table option to use the existing table, or drop
the table to allow the entity bean to create a new table. |
Under load conditions, AIX and Solaris systems with 512MB may
only support a DB2 connection pool size of 10 connections. If you want to run more than 10
connections, you will need more than 512MB. On average, DB2 connections will use 1-2MB each. |
AIX, Solaris |
When sending a large number (for example, 100
simultaneous users) of requests, use 512MB to run with 10 connections. The 512MB includes
the administrative server, application process, etc. DB2 connections usually run about 1.5MB
to 2MB, so if you want to run more than 10 connections, you will need more than 512MB. |
Problem |
Op System |
Workaround |
The Session Manager's native access support is currently not
in WebSphere Application Server Version 3.0. |
TEXT HERE |
Use the JDBC access until further notification. |
A session persist/cache can lose database connections. A user
creates a cached session. On the next access, attempt to get an object not currently
in the session, then access the database to see if it is there. |
All |
The database connection will be made. On any subsequent
database store, the connection will be made. |
A DB2 blob support should be added for storing persistent
session state. The format of the Sessions tables in the HTTP Sessions persistent to use
a Blob column that can contain 2 megabytes of data. This replaces the "long varchar
for bit data" column that had a 32700 bytes. |
All |
For this to become effective, you must:
- Stop the application server.
- Drop the Sessions table in the database instance your datasource for http session
persistence is pointing to (NOTE: If the database instance is the same as the database
for the WebSphere Administrative Server, be sure and not drop the
SESSION_MGR_TABLE by mistake).
- Restart the WebSphere Application Server, which will automatically create a table
using the Blob column.
If you know your session (in the single row case) or your individual session objects
(in the multirow case), do not exceed 32700 bytes; you can still continue ot use long
varchar for bit data. You do not have to do anything. The table will continue as is.
If you did the above steps to switch to the Blob type and then decide to switch back,
do the following:
- Stop the server.
- Drop the Sessions table.
- Create a new Sessions table.
For other than AS/400, use:
create table sessions
(id varchar (24) not null,
propid varchar (24) not null,
appname varchar (32),
listenercnt smallint,
lastacces bigint,
creationtime bigint,
maxinactivetime integer,
username varchar (256),
small varchar (3595) for bit data,
medium long varchar for bit data)
For AS/400, use:
create table sessions
(id varchar (24) not null,
propid varchar (24) not null,
appname varchar (32),
listenercnt smallint,
lastacces decimal (21),
creationtime decimal (21),
maxinactivetime integer,
username varchar (256),
small varchar (3595) for bit data,
medium long varchar for bit data)
|
Problem |
Op System |
Workaround |
Users of WebSphere Application Server with Domino Versions 5.02,
5.02B, and Domino 5.03 LDAP directories have encountered problems, such as intermittent
server hanging, with security and LTPA as the authentication method. The problems are
due to a defect in these Domino versions. |
All |
This is expected to be fixed in Domino Version 5.05. |
WebSphere Application Server does not currently support
TBSCertificate extensions for client authentication and authorization. |
All |
WebSphere Application Server does support certificate mapping
using Subject DN or Issuer DNs. |
When protecting static HTML files served by the IBM HTTP Server, if
you are using the WebSphere Application Server security infrastructure and client certificates
for authentication, you may experience problems gaining access to the file (for example, you
might get a Document contains no data message). Basic or custom challenges seem to work
fine. Those with client certificates do not. |
All |
Configure the WebSphere Application Server and your system so that
the file is served by WebSphere. Then protect the file to be served on Certificate challenge
using IBM HTTP Server protection. |
When security is enabled, administrators must specify two different
Secure Sockets Layer (SSL) port numbers for use by the administrative server. |
All |
On the server command line, define two port numbers using the -D option:
For the listener port, specify: com.ibm.CORBA.SSLPort
For Location Service Daemon (LSD) port, specify: com.ibm.CORBA.LSDSSLPort
The values of these two properties must be different. |
You might not be able to run IKeyman in the WebSphere environment. |
All |
If you installed both IBM HTTP Server and WebSphere Application
Server Advanced Edition on the same host
- On Windows NT, enter following commands to run the IKeyman keyring management tool:
cd <WebSphere_installation_directory>\bin
setupCmdLine.bat
set PATH=%JAVA_HOME%\bin;%JAVA_HOME%\jre\bin;%JAVA_HOME%\jre\bin\classic;%PATH%
set CLASSPATH=%WAS_HOME%\lib\cfwk.zip;%WAS_HOME%\lib\gsk4cls.jar;%WAS_HOME%\lib\swingall.jar;%CLASSPATH%
java -Dkeyman.javaOnly=true com.ibm.gsk.ikeyman.Ikeyman
- On AIX, Solaris or HP-UX, enter the following commands to run the IKeyman keyring management tool:
cd <WebSphere_installation_directory>/bin
setupCmdLine.sh
set LIBPATH=$JAVA_HOME/jre/bin:$JAVA_HOME/jre/bin/classic:$LIBPATH
set PATH=$JAVA_HOME/bin;$JAVA_HOME/jre/bin;$PATH
set CLASSPATH=$WAS_HOME/lib/cfwk.zip;$WAS_HOME/lib/gsk4cls.jar;%WAS_HOME%/lib/swingall.jar;$CLASSPATH
java -Dkeyman.javaOnly=true com.ibm.gsk.ikeyman.Ikeyman
or, instead of using the java command, run /usr/opt/ibm/gskit/bin/gsk4ikm
If you did not install IBM HTTP Server
- On Windows NT, enter the following commands to run the IKeyman keyring management tool:
cd <WebSphere_installation_directory>\bin
setupCmdLine.bat
set PATH=%JAVA_HOME%\bin;%JAVA_HOME%\jre\bin;%JAVA_HOME%\jre\bin\classic;%PATH%
set CLASSPATH=%WAS_HOME%\lib\cfwk.zip;%WAS_HOME%\lib\gsk4cls.jar;%WAS_HOME%\lib\swingall.jar;%CLASSPATH%
java -Dkeyman.javaOnly=true com.ibm.gsk.ikeyman.Ikeyman
- On AIX, Solaris or HP-UX, enter the following commands to run the IKeyman keyring management tool:
cd <WebSphere_installation_directory>/bin
setupCmdLine.sh
set LIBPATH=$JAVA_HOME/jre/bin:$JAVA_HOME/jre/bin/classic:$LIBPATH
set PATH=$JAVA_HOME/bin;$JAVA_HOME/jre/bin;$PATH
set CLASSPATH=$WAS_HOME/lib/cfwk.zip;$WAS_HOME/lib/gsk4cls.jar;%WAS_HOME%/lib/swingall.jar;$CLASSPATH
java -Dkeyman.javaOnly=true com.ibm.gsk.ikeyman.Ikeyman -
Then, follow the online documentation on using the IKeyman tool. |
If you select the Lotus Domino plug-in during WebSphere
Application Server installation, the Lotus Domino configuration file is updated to use
the old DLL (GWAPI - libgo46.so). The security of the Lotus Domino plug-in will not work. |
TEXT HERE |
Use the new DLL (DSAPI - libdomino5.so). Use the following
steps to obtain the new DLL instead of the old one (these steps assume Solaris is the example
operating system, but can be used on the others):
- Install WebSphere Application Server, and select the Lotus Domino plug-in.
- After installation, comment out the following lines in the httpd.cnf file:
Authorization *
/opt/WebSphere/AppServer/bin/libgo46.so:
authorization_exit
NameTrans *
/opt/WebSphere/AppServer/bin/libgo46.so:
nametrans_exit
Service IBMWebSphere
/opt/WebSphere/AppServer/bin/libgo46.so:
service_exit
ServerInit
/opt/WebSphere/AppServer/bin/libgo46.so:
init_exit
/opt/WebSphere/AppServer/properties/
bootstrap.properties
ServerTerm
/opt/WebSphere/AppServer/bin/libgo46.so:
term_exit
Pass
/IBMWebAS/samples/*
/opt/WebSphere/AppServer/samples/*
Pass /IBMWebAS/*
/opt/WebSphere/AppServer/web/*
- Run the Lotus Domino server.
- Bring up the Lotus Domino Administration display. Go to the Lotus Domino
configuration, and add the following line under DSAPI filter:
/opt/WebSphere/AppServer/bin/libdomino5.so
- Restart the Lotus Domino server. While it is starting, you will see the line:
WebSphere DSAPI filter loaded.
This means the Lotus Domino plug-in will use the new DLL.
- Start WebSphere Application Server.
|
When security is enabled in WebSphere Application Server,
if you specify the ORB property com.ibm.CORBA.listenerPort to define the
listener port for an application, it does not affect the ORB. The ORB continues to
generate a new port dynamically and uses it instead of the one specified. This is
encountered especially in the DMZ and servlet redirector scenarios. |
TEXT HERE |
Specify instead com.ibm.CORBA.SSLPort If you are
are starting an application server as:
java -Dcom.ibm.CORBA.listenerPort=7777
<other parameters>
then, if security is enabled, start the server as:
java -Dcom.ibm.CORBA.SSLPort=7777
<other parameters>
|
As to security in a model/clone environment, if a model
(or one of the clones) is secured, then when WLM is enabled, accessing a bean in the cloned
environment results in a "Authorization failure" on the server side or an "ObjectNotFound"
or an access exception on the client side, where the client is accessing the cloned bean. |
All |
Apply a security configuration to each clone.
In a model/clone environment, security needs to be applied to each clone that needs to be
secured. If the model is secured, then the security configuration will not automatically
apply to all of the model's clones. All clones need to be added to an appropriate
enterprise application and a "Configure Resource Security" task must be applied to all of
those clones. |
When security is enabled and you modelled an application
server and cloned it, starting the model in order to start the clones may cause
exceptions or a system hang, eventually making the server unavailable. |
All |
Start each cloned server individually. That is, do not
start the model in order to start the clones. |
If you changed the password of the userid in the user
registry, you might have problems starting WebSphere Application Server since the
userid and password are invalid. The password of the userid referred to is associated
with WebSphere and configured in the UserRegistry task panel.
|
TEXT HERE |
The only way to change the userid and password that would
not affect other configuration information is to:
- Before changing the userid and password in the registry and while the userid and password
are still valid in the registry, start the WebSphere Administrative Server and the WebSphere
Administrative Console.
- Start the user management utility (LocalOS or LDAP tools), and then change the password.
- Make the corresponding change tothe WebSphere Application Server user registry
configuration:
- Select Global Security Settings, then User registry, then
ServerID and password
- Apply the changes.
- Restart the WebSphere Application Server.
|
REDIRECT using relative path goes to port 80 not port 443.
Consider the following when you perform redirection from within a secure Web resource.
If you are requesting a resource (for example, https://a.b.com/servlet/MyServlet),
and that request redirects you to a relative URL (/servlet/MyServlet2), then
the redirected URL is sent to port 80 and not port 443. In other words, the redirected
URL is for the "http" (not over SSL) URL and not "https" (over SSL).
In this example, the user is redirected to http://a.b.com/servlet/MyServlet2
and not https://a.b.com/servlet/MyServlet2.
|
TEXT HERE |
|
Problem |
Op System |
Workaround |
When debugging a JSP (1.0 OR 0.91) Distributed Debugger
does not step over empty lines. For example, when stepping into a JSP like:
Line 1: Hello<BR>
Line 2:
Line 3: World!
the debugger stops at line 2. |
Windows NT |
|
WebSphere 3.0 provides support for the OLT product.
WebSphere's install includes the OLT server-side runtime. The OLT trace and debug
graphical user interfaces that are part of the OLT product must be installed separately. |
TEXT HERE |
To get the OLT product, go to the Websphere Application
Server Web site, and download the OLT install package. Also get the readme that covers
basic install and usability issues. |
On WebSphere Application Server 3.0 Standard, the OLT Controller
does not get installed when you select Install the initial configuration. |
TEXT HERE |
If you wish to use OLT support with WebSphere Standard
manually create the OLT Controller. Here are the steps:
- In the WebSphere Administrative Console, go to the Types tab:
- Create OLT Controller.
- Fill in values for Home Directory and Driver Path
- Edit the olt.xml file in the properties directory.
- Change Installed to true.
- Put in correct values for Home Directory and Driver Path.
|
The JVM arguments are not being passed to the Java program
if the user invokes idebug using the -qjvmargs option. |
AIX |
Start the OLT Viewer and place it in the Online mode. Then debug
the Java program using idebug with the -qjvmargs option as usual. |
Add irmtdbgj.exe to the nanny.path in the admin.config file for
Object Level Trace. |
TEXT HERE |
Before running OLT/Debugger support in WebSphere Application
Server, you must add the location of the executable irmtdbgj.exe to the nanny.path variable
in the WebSphere Application Server admin.config file. For example, on Windows NT, add the
path
<drive>\IBMDebug\bin\irmtdbgj.exe
to the variable
com.ibm.ejs.sm.util.process.Nanny.path
in the WebSphere\AppServer\bin\admin.config file. |
When running the OLT Viewer, if you try to change the Execution Mode
in the Client Controller for a connected client and then click Apply, the viewer might
freeze. |
Windows 2000 |
Ensure that you have set the Execution Mode properly in the
Client Controller for the Default settings entry before you try tracing. Do not attempt
to change the Execution Mode after you start a trace. |
WebSphere Application Server Version 3.5 supports the locales listed in the table below.
The support is dependent on the availability of the TrueType fonts listed for the
respective languages.
Problem |
Op System |
Workaround |
All Countries |
National language documentation sets in the full
InfoCenter (other than the English set) contain known problems or limitations
that are addressed in the English version of that documentation. Because some
information was translated to languages other than English before the product
was completed, the English version of the documents contain some corrections and
additions which are available with the product but not yet translated. |
All |
These additions and corrections to the documentation
set will be translated and made available in other languages as soon as is
practicable after general availablity of the WebSphere Application Server product.
If you are using a national language version of the documentation other than
English, check the product Web site Library page for information about obtaining
a refreshed version in the language of your choice. Also, consider periodically
referring to the English documentation set in the InfoCenter in addition to the
language set you installed.
|
Samples are missing on NLS versions of Web servers.
Users who have installed WebSphere Application Server Version 3.01 cannot
access the samples, even though the samples are installed.
For example, if you try the samples URL included in the InfoCenter,
which opens the file "index.html," the file cannot be found, even though the file
is installed with WebSphere Application Server.
The problem occurs because the samples are not in your Web server document root.
|
All |
Copy the sample files from your WebSphere Application
Server installation to the document root of your Web server.
For example, for IBM HTTP Server, copy the files to the directory htdocs/xx_XX
(where xx_XX is the locale for your language, such as en_US for English).
The sample files include all of the files under the WebSphereSamples directory,
including index.html. Copy the entire WebSphereSamples directory, its contents,
its subdirectories, and their contents
<AppServer_root>/WebSphereSamples
and
<AppServer_root>/theme
to the document root of your Web server.
|
Because of an NLS bug in the IBM JDK, the word "True" appears
in English on the Default Model Properties page in the Administrative Console. |
All |
Ignore the appearance. |
The web/xml directory in the WebSphere Application
Server Version 3.01 installation root is not installed for some locales. |
TEXT HERE |
The xml directory and its subdirectories contain
document type definition (.dtd) files, which are not translated. A .zip
file containing the xml directory contents will be made available on the
product Web site. If the directory is missing from the Application Server
installation for your locale, retrieve the Zip file and add its contents
to your installation.
If the Zip file is unavailable at the time you need it, you can use the
installation program to install only the documentation. Install the documentation
in English so that you can acquire the xml directory and its contents.
After preserving a copy of the directory, you can delete the rest of the
English documentation.
You only need these materials if you are using the XML functionality of the
product. |
The installation should allow you to install more than
one language and switch between languages. Currently, because all of the languages are named
the same in the same installation path, they overwrite each other. Also, with native install
(using SMIT), when more than one language is installed, an error is issued. |
AIX |
Install only one language of WebSphere Application Server on
AIX. If you need to install a different language, uninstall the previous language before
installing the one desired. |
Just after WebSphere Application Server is installed
on AIX, the fully-qualified domain name (FQDN) is not included in the Alias Host field
of Virtual Host:default_host. Access by httpd://<FQDN>/servlet/snoop fails. |
AIX |
Input FQDN in the Alias Host field and restart the server. |
For non-English locales on AIX, Lotus Domino Go WebServer 4.6.2.x
creates the etc/http/config/<locale>/http.conf file. WebSphere Application Server
installation updates the English file etc/http.conf. |
AIX |
Edit your locale's httpd.conf file and add the WebSphere
Application Server configuration information. |
The Cancel button in Uninstallshield does not work. On AIX, when
you click Cancel in the uninstallshield, the executable loops and the uninstallshield
automatically reloads. |
AIX |
To cancel the uninstall, press Ctrl+C at the command prompt
in the shell from which the uninstall program was initiated. |
IBM Brazilian Portuguese |
The time displayed with events on the Administrative Console
is one hour earlier than the actual system time. This is apparently because of a JDK defect. |
Windows NT, AIX, Solaris |
|
IBM Japan |
Japanese characters are distorted on the following installation panels:
- On the Choose Application Server Components panel, all of the characters in Component Description
are distorted.
- On some panels after the Database Options panel, kana-kan status characters at the bottom left corner are
distorted.
- On the Selected Install Options panel, all of the selected option strings are distorted.
|
AIX |
- Install X11.fnt.ucs.ttf - AIXWindows unicode TrueType fonts.
- Logout and login again.
This must be done to reflect installation of the proper fonts.
- Run xlsfonts | grep 0208 to confirm monotype fonts are installed.
- Install WebSphere Application Server Version 3.5. You will see DBCS characters in TxTArea.
|
When you install WebSphere Application Server
on the Japanese Solaris operating system, the dB_HOME select dialog does not
display the directory entry. startupServer.sh and admin.config are not updated. |
Solaris |
Set locale as LANG=C on the shell, and start
install.sh. |
A warning is displayed when starting Netscape Communicator 4.6
and browsing the index.html (or configuration file) document. The document browses normally. |
All |
The error message is false. Ignore the message |
When using the following procedure, garbage characters and an
error message are displayed:
- Start the WebSphere Administrative Server. From the Start menu, choose:
- Programs
- IBM WebSphere
- Application Server 3.0
- Administrative Console
- Select the Topology tab.
- Expand the WebSphere Admin Domain view.
- Right click the Default server (of your host), and click Start. An information
dialog displays the message Command Default Server.start completed successfully.
- Click OK.
- Browse http://your host/servlet/.
|
Windows NT/2000 |
|
Japanese AIX customers using the eucJP locale need to
change some text files to allow some of the Administrative Console pages to display properly. |
AIX |
If you see pages in the AdminConsole containing lots of
???????????????, install Japanese WebSphere on AIX. If ja_JP locale is used, the following
.txt files in the /web/help directory need to be converted with the command (on one line):
iconv -f IBM-932 -t IBM-eucJP
Originalfile.txt > Originalfile_ja.txt
then, rename the files
mv Originalfile_ja.txt
and
Originalfile.txt
The list of files:
AddJSPEnabFrontPage.txt
AddServletFrontPage.txt
AddWebResFrontPage.txt
AppSecFrontPage.txt
CfgAppSvrFrontPage.txt
CfgEntAppFrontPage.txt
CfgServEngFrontPage.txt
CfgVirtHostFrontPage.txt
CfgWebAppFrontPage.txt
EditEntAppFrontPage.txt
GlobSetFrontPage.txt
MethGroupFrontPage.txt
PermFrontPage.txt
ResAnalyzFrontPage.txt
ResSecFrontPage.txt |
IBM Spain |
When using the Types tab, then selecting Model and create and then
choosing Application Server, the properties window is initially too small. The right side of the
window is cut off by about five characters. |
AIX |
This is a general swing problem which does not occur all the time.
Manually resize the window if this occurs. |
IBM Chinese Simplified |
On AIX V4.3.3:
- PTF U466148 must be applied before installing WebSphere Application Server Version 3.0.
This PTF is available on the 4.3.5 installation media. Note also that it is not necessary
to upgrade the operating system to 4.3.3 to install this PTF.
- WebSphere Application Server Version 3.0 supports only one Simplified Chinese Charset
in AIX, that is BGK.
|
AIX |
|
IBM Chinese Traditional |
Problems with character sets other than
"Big5" on AIX V4.3.3. |
AIX |
WebSphere Application Server supports only one
Traditional Chinese Character Set for AIX V4.3.3. The supported character set
is "Big5". |
While using the product, corrupt panels and code
page conversion errors appear. |
Solaris |
To install and use the WebSphere Application Server
(WAS) with a minimal amount of corrupted panels, follow the procedure below:
- From a command line, type:
export LC_ALL=tchinese
export LANG=tchinese
- Install WAS.
- From a command line, type:
export LC_ALL=zh_TW.BIG5
export LANG=zh_TW.BIG5
- Create the WAS database as instructed in the documentation.
- Repeat step 1.
- Start the administrative server.
- Repeat step 3.
- Start the administrative console.
To uninstall WAS with a minimal amount of corrupted panels:
- From a command line, type:
export LC_ALL=tchinese
export LANG=tchinese
- Uninstall WAS as instructed in the documentation.
|
All IBM Double-Byte Countries |
In the WebSphere Administrative Console, Asian characters show
up as empty boxes because of a limitation in the HP-UX 1.2.2 SDK. The Java swing libraries
require TrueType fonts. HP-UX does not provide these fonts for Asian languages. The SDK release
notes state that HP-UX is working to provide these font in the future.
|
HP-UX |
In the meantime, Japanese, Korean, Chinese Traditional, and
Chinese Simplified customers must purchase their own TrueType fonts from a third party vendor.
They can also force the WebSphere Administrative Console to run in English by running the
following command from the command prompt before starting the WebSphere Administrative Console:
export LANG=en_US.iso88591
Also, for more information on this limitation, refer to the HP-UX SDK Release Notes
(click here).
|
Search documentation does not work. |
All |
The DBCS search function will be removed along with frame
sets for the help and InfoCenter. |
Double-byte server name is corrupt in console messages. If you
name a server with Asian-Pacific characters and start it, the name in the status message
(starting, stopping) on the Administrative Console is garbage (question marks and square
blocks). |
All |
Use only English characters and numbers for your server name. |
An application server will not start if named with more than
three Chinese characters. Any combination of less than three Chinese characters or any
number of English characters works fine. With more than three Chinese characters, the
name in the status message (starting, stopping and others) is made up of meaningless
characters (for examples, question marks and square blocks). |
All |
Use English or fewer than three double-byte characters. |
Problem |
Op System |
Workaround |
The readme.html file incorrectly states that the
WebSphere Application Server Standard Edition installation guides are included
in the product installation. |
All |
Obtain the Standard Edition installation guides as part of the full
InfoCenter download available from the product Web site. Details for this download are in the
readme.html file. |
When opening the InfoCenter or its files using a Netscape browser,
you might receive a file not found message. This message refers to the name and path
of the file you are attempting to open, for example:
'c:\WebSphere\AppServer\web\doc\
begin_here\filename.html' not found
|
Windows NT |
Do the following:
- Start Windows Explorer.
- Click View, then select Options.
- Click the File Types tab.
- Scroll the Registered File Types list to Netscape Hypertext Document and double click.
- Under Actions, double click Open.
- Uncheck the Use DDE option.
- Click OK, then close.
With the Use DDE (Dynamic Data Exchange) option off, the window errors that complain that a
a local file (like the Readme) is not found should not appear. |
Using the Netscape browser, the InfoCenter and Help display
blank pages or give Java/Javascript errors when opening InfoCenter or Help topics. |
Solaris |
To correct this problem you can set up the Netscape browser environment to
allow use of the InfoCenter and Help system (setup consists of putting all Netscape .jar files in the
CLASSPATH, followed by the required WebSphere JDK):
- Configure Netscape:
- Set your CLASSPATH to included (in this order) each Jar file in
the MOZILLA_HOME/Java/classes directory; the Java classes.zip file
found in /usr/java1.1/lib.
- In Netscape, select Preferences, then Appearance, then Fonts and
change the font settings. The recommended setting for variable width font is New Century
Schoolbook; and for fixed width font, it is Courier. Note that many of the font choices
included with the Netscape Navigator product will work. Choose a set you like.
- Access the InfoCenter and Help from a browser on a non-SUN system using the
URLs:
http://<server>/IBMWebAS/doc/begin_here
http://<server>/IBMWebAS/help/helpcon.htm
|
If Netscape Navigator (or Communicator) is the system
default browser and a browser is already open for a purpose other than displaying
WebSphere Application Server help or documentation, the open browser might
ignore a request to display the WebSphere Application Server help or documentation.
The help or documentation is not displayed in the open browser, and no new browser
instance is launched for displaying the requested file. |
Windows NT |
If instances of the default browser are already open
for other purposes, close these browser instances, if possible, before requesting
help or documentation from WebSphere Application Server using the Help menu on the
WebSphere Administrative Console or the Start menu on Windows NT. |
The online help for the Administrative Console may be
disabled for the choices What is it?, How do I?, and Property Help. |
Solaris |
|
In the WebSphere Control Program (wscp) documentation (under the
section titled, "Authenticating to the administrative server"), the following sentence should
be removed:
"If you want to administer WebSphere by using
unattended scripts, you can avoid being prompted
for a user ID and password by changing the value
of the com.ibm.CORBA.loginSource property to
"properties."
|
All |
The value "properties" is the only option for com.ibm.CORBA.loginSource.
The value "login" (prompting for a user ID) is not supported for wscp. |