Release Notes for IBM WebSphere Application Server Version 3.5 with Fix Pack 3 applied

Last updated 3/07/01

This document contains the Release Notes for IBM WebSphere Application Server Version 3.5 with Fix Pack 3 (also known as Version 3.5.3) for Linux, Windows NT (Windows 2000 supported), Sun Solaris, AIX and HP-UX.

These Release Notes cover both the Advanced and Standard Editions. Because 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) applies only to the Advanced Edition.

Note: This file is best printed in a landscape format. Also, if you find that all text does not fit on a printed page, a suggestion is to decrease the scaling before printing. To change the scaling, access the print properties. Setting the scaling to 80 has proven successful.

What is new in WebSphere Application Server 3.5.3

JDK Fix Pack 9 (Windows NT/AIX/Linux)
Additional features of Fix Pack 3

See InfoCenter article 0.0.7 to learn more about these additions to Fix Pack 3.

Release Notes

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.

Installation and Configuration
Starting Application Server Components
Administrative Console (GUI) and Command Line Tools
Enterprise Beans
Object Request Brokers (ORBs)
Servlets
Java Server Pages Files (JSP files)
XML and XSL
Connection Pooling
HttpSession
Workload Management
Networking
Security
Performance and Stability
OLT and Debugging
Tracing
National Language Version Issues/Limitations
Samples
InfoCenter


Installation and Configuration

Problem Op System Workaround
If you named your Microsoft SQL Server instead of using the default name (hostname), you will need to configure Sequelink. Windows NT/2000 Follow these steps to configure Sequelink:

Note:The non-default Microsoft SQL Server name is STLAB20\SQLEJS in this example.
  1. Access SL Admin Mgr Snapin from the Start menu.
  2. Choose SLSQLServer51.
  3. Choose Configuration.
  4. Choose Data Source Settings.
  5. Choose Default.
  6. Right click and choose New and then Attribute.
  7. From the dropdown menu choose DataSourceMSSODBCConnStr.
  8. If you are using SQL Server 2000 ODBC Driver type in this value:
    Driver={SQL Server};Server=STLAB20\SQLEJS (Note: Everything after Server= is the name of the Microsoft SQL Server name).

    If you are using SQL Server 7.0 ODBC Driver (Default) type in this value:
    Driver={MERANT MSSS Driver for SequeLink 5.0};Server=STLAB20\SQLEJS.
  9. Stop the Sequel Server agent and restart it.
The following error messages appear in the browser window when trying to access static HTML pages served by the File Serving Enabler in WebSphere Application Server Version 3.5.3, Advanced Edition:

A recursive error was detected.
The server cannot use specified error page. Please check the application error-path.

Original Error:
Error Message: File not found: null
Error Code: 403
Target Servlet: File Serving Enabler
All Apply efix pq46735.jar by doing the following:
  1. Create a directory to store the jar file (e.g. c:\WebSphere\AppServer\efix)
  2. Copy pq46735.jar to the directory.
  3. Add the directory/jar file to the begining of the admin server's classpath in admin.config:
    com.ibm.ejs.sm.adminserver.classpath=C:/WebSphere/AppServer/efix/pq46735.jar...
  4. Stop and restart the administrative server.
The URL for the efix is http://www-4.ibm.com/software/webservers/appserv/efix.html

Note:If you applied efix pq46735, make sure you remove this efix. If you leave this efix in place, you may not see an error but the server code you are running may be back-leveled. You can remove this by taking pq46735.jar out of your com.ibm.ejs.sm.adminserver.classpath.
On Unix, permissions of DBConfig.sh need to be changed to make it executable after unzipping the DBConfig.zip. When a radio button for a particular database is selected, the tool does not automatically fill in the correct database driver and database prefix. AIX, Solaris Choose the right database driver from the pull down menu and change the database prefix to the appropriate value.
On Unix, DBConfig tool changes the permissions of $WAS_HOME/bin/startupServer.sh to nonexecutable. AIX, Solaris Change the permissions of startupServer.sh to make it executable before starting the administrative server.
The IIS filter/extension mechanism requires that the dll be on the virtual directory. Therefore install sets the virtual directory to point to WebSphere bin directory. When setting the virtual directory to point to WebSphere's bin directory, there are files that should not be accessed. For example: If a user types "http:///SEPlugins/admin.config" they can view that file and the content contains the password. Another file in the bin directory that shouldn't be accessed is NTRegistry.dll. All To fix this problem:
  1. Create a plugins sub-directory under the bin directory.
  2. Copy the iis20.dll into that directory.
  3. Make the virtual directory(sePlugins) in the IIS configuration point to the bin\plugins directory and not bin.
The Cancel button in the uninstall screen doesn't work. AIX If you need to cancel the install, press Ctrl+X.
Upgrading from WebSphere Application Server Version 3.5 to Version 3.5.3 on Microsoft Windows NT, Enterprise Edition, SP6a fails. When running the FixPak 3 install.bat the following error displays:

Upgrading IBM JDK 1.2.2
The syntax of the command is incorrect.
Invalid number of parameters
Error in POProcessor:
The directory specification, -targetdir D:\WebSphere\AppServer\java_ptf_3, seems not to be a directory.
Windows NT Press any key to continue.
Distributed transaction which uses two datasources defined on separate WebSphere Application Server nodes is failing.
Both the data sources use JTA enabled DB2 7.1/FixPak 2 JDBC drivers.
The following exceptions were thrown by the client:

Failed to debit card: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: debitCard failed: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL30090N Operation invalid for application execution environment. Reason code = "06". SQLSTATE=25000


Note: "Debit card" in the above error message is the application used for testing.
All  
For SQL Server 2000 on Windows NT, there is a problem with Microsoft Data Access Componentry(MDAC) Version 2.6. The ODBC driver for SQL Server, embedded with SequeLink 5.x, requires dlls that are no longer shipped in MDAC Version 2.6. Therefore, if you install SQL Server 2000 on a clean Windows machine, the following error displays:

Specified driver could not be loaded due to system error 126 (MERANT MSSS Driver for SequeLink 5.0)
Windows NT The SQL Server 7 driver requires dlls that are not required by the SQL Server 2000 driver and no longer ship with MDAC Version 2.6 or higher.

To fix this problem, install the MDAC version that is shipped on the DataDirect SequeLink CD(or version 2.1 from the Microsoft website). Here is a link to the Microsoft website for MDAC Version 2.1:

http://www.microsoft.com/data/download_21242023.htm
If WebSphere or its Web servers are running during the time of installing the Fix Pack, you will get errors. All To avoid errors, follow these steps:
  1. Stop all Web servers.
  2. Stop WebSphere.
  3. Uninstall the Fix Pack.
  4. Delete the backup files.
  5. Reinstall the Fix Pack.
When installing the Fix Pack on a machine with only the administrative console, it will not update. Windows NT Copy the admin.config file from a WebSphere machine and put it under /bin.
WebSphere does not recognize multiple instances of IIS. It only recognizes the default instance. Windows 2000 Create two virtual directories in the second instance of IIS (IBMWebAS, sePlugins). Make these virtual directories identical to the first instance of IIS. Both virtual directories in both instances should be identical. You can do this for as many IIS instances you have.
If you select the Lotus Domino plug-in during WebSphere Application Server installation, the new DSAPI filter is not enabled by default. All The new DSAPI filter file names, depending on the platform, are as follows:
  • Windows: libdomino5.dll
  • AIX: libdomino5.a
  • Solaris: libdomino5.so
  • HP_UX: libdomino5.sl
These files are located under the WAS_HOME/bin directory.

Use the following steps to enable the new DSAPI filter. (These steps assume Solaris is the example operating system, but you can use the same steps on other operating systems).
  1. Install WebSphere Application Server, and select the Lotus Domino plug-in.
  2. Run the Lotus Domino server.
  3. Open the server document either in the Lotus Notes client or in a browser.
  4. Go to the Internet Protocols tab. In the DSAPI filter file names (under DSAPI heading ) field, add the full path to DSAPI filter file name.
    • Example(for Solaris): /opt/WebSphere/AppServer/bin/libdomino5.so
  5. Restart the Lotus Domino server. When the HTTP task starts, you will see the line:

    WebSphere DSAPI filter loaded

    This means the new filter is loaded and WebSphere is ready to use the Domino HTTP server.
  6. Start WebSphere Application Server.
In article 1.2.3.2.3 the section entitled "Setting up the administrative database in DB2/390" mentions that sample JCL can be found in the installation directory but does not specify where. All The db22390.sql JCL file is located in the bin directory.
Unable to start the WebSphere Administrative Server with the following message (Sybase):
com.sybase.jdbc2.jdbc.SybSQLException: User name EJSADMIN does not exist in sysusers
All When using a schema other than EJSADMIN with Oracle and Sybase, you need to specify the following in admin.config:
com.ibm.ejs.sm.adminServer.dbSchema=

There are two important points to remember:

  1. The schema owner must be CAPITALIZED
  2. The schema owner must be terminated with a period
    Example: com.ibm.ejs.sm.adminServer.dbSchema=WASADMIN.
After uninstalling the Fix Pack, and trying to reinstall the same Fix Pack, your machine detects that the Fix Pack is still installed. When trying to exit, you are not able to, and the JDK is automatically updated. All After uninstalling the Fix Pack, delete the backup jar files and the uninstaller of the Fix Pack.
During the WebSphere Application Server installation, the following error displays:
ERROR-FUNCTION-entry not found on string table
because you are missing a file "lodctr.exe" in the WINNT/SYSTEM32 directory.
Windows NT WebSphere automatically installs IHS and, when this error occurs, the silent install will stop and the WebSphere install will continue. IHS does not copy all of its needed files to the hard drive of the machine, therefore it won't run at all. This may happen if you don't have IHS on your machine and you install Full, Quick or Custom install with IHS.

To fix this:
Before installing WebSphere with IHS, ensure you have the file "lodctr.exe" in the WINNT/SYSTEM32 directory. If you don't have it, copy it from another Windows NT machine and put it in the WINNT/SYSTEM directory. The installation of WebSphere and IHS will now work.

When installing WebSphere, if you are using a Web server or database that exceeds WebSphere's current required version of Web server or database, the pre-req checker runs and displays a message that you can't install with versions other than the required versions. All On Windows NT, click OK and continue.

On Solaris and AIX, you must cancel the install or choose the default version of the Web server or database.

To avoid the problem, disable the pre-req checker. This is done by going to the pre-req.properties in the install files and changing prereq_checker=1 to prereq_checker=0 (line is in [WAS] block at top of the file).

A new property was introduced in Fixpack 3. All There is a new property that can be added in the admin.config file located in the bin directory of the WebSphere Installation directory.

Example file location: c:\WebSphere\AppServer\bin\admin.config
The property name is: com.ibm.ejs.sm.adminServer.dbInitialized=true

If the admin.config file has the new "com.ibm.ejs.sm.adminServer.dbInitialized=true" entry the WebSphere Repository database tables will not be created. On subsequent stop and start of the administrative server, the AdminServer.java will verify whether this parameter is present in the admin.config file, and if the parameter is not present, the database tables are created if necessary.

Note: If the WebSphere Administrator Server database is dropped after this property is added to the admin.config file, database exceptions will occur.
To rebuild the database follow the steps below:
  1. Stop WebSphere Application Server's administrative server if it is running.
  2. Modify the admin.config file and remove the com.ibm.ejs.sm.adminServer.dbInitialized=true property.
  3. Start WebSphere Application Server's administrative server.
Once this property has been added to the admin.config file, uninstalling a FixPak will not remove it. The property MUST be manually deleted. You may wish to make a copy of this file in the /tmp directory and invoke the installer using the modified copy in the following manner: /install.sh /prereqfile /tmp/prereq.properties

Note 2: Development and service frequently drop the WebSphere administrator database. It is obvious that the above entry has to be removed from the admin.config file in order to recreate the repository tables. Setting com.ibm.ejs.sm.adminServer.dbInitialized=false in the admin. confile file will not recreate the tables. Before recreating, the whole entry (com.ibm.ejs. sm.adminServer.dbInitialized=true) should be removed from the file.
The admin.config entry com.ibm.ejs.sm.adminServer.dbInitialized=true (or false) is not present in the admin.config file after installing the base GM code and Fix Pack 3, and starting the server and adminclient. All If the admin.config file has the "com.ibm.ejs.sm.adminServer.dbInitialized=true" entry (after initializing the database), the database tables will not be recreated.

On subsequent stop and start of the administrative server, the AdminServer.java will verify whether this parameter is present in the admin.config file. If the parameter is not present, the database tables are created. Thus, make sure this parameter is set in the admin.config file.

Note: Development and service frequently drop the WebSphere Application database. It is obvious that the above entry has to be removed from the admin.config file in order to recreate the tables. Setting com.ibm.ejs.sm.adminServer.dbInitialized=false in the admin.config file will not recreate the tables. Before recreating, the whole entry (com.ibm.ejs.sm.adminServer.dbInitialized=true) should be removed from the file.

When migrating from Version 3.02 to Version 3.5, Version 3.02 configurations are lost. All Before migrating from Version 3.02 to Version 3.5, you must migrate any application files first.

See InfoCenter article 3 for more information.

Step 2 of the instructions tells you to migrate or upgrade to IBM WebSphere Application Server 3.5. You need to migrate, then upgrade.

Follow steps 3-5 for migration, then go ahead with your upgrade.

Using the "Programs" to uninstall WebSphere Application Server causes problems. All To uninstall WebSphere Application Server, use the Uninstall option.

For Windows NT, select Start->Programs->IBM WebSphere->Application Server Version 3.5->Unistall WebSphere Application Server.

On Unix, execute the uninstall.sh script which is located in the WebSphere root installation directory (e.g./opt/WebSphere/AppServer).

Other uninstall tips:

  • If you installed the IBM HTTP Server as part of the WebSphere Application Server, you may need to separately uninstall IBM HTTP Server.
  • Delete the WebSphere directories from the file system after you have completed uninstalling the product. The method for doing so varies by Operating System.

    On Unix, use of rm -r WebSphere will accomplish this, although be cautious with this approach to avoid inadvertent removal of other portions of the file system.

    On Windows NT, navigate through the WebSphere directory with Windows Explorer and delete the directories. Deleting the directories will avoid conflicts if you choose to reinstall the product.

The exception NoSuitableDriver is displayed when you install WebSphere Application Server using Oracle, Sybase or IDB as the WebSphere Application Repository.

The exception occurs when you use DataSource to access the DB2 database for application data by choosing the DataSource for Connection Pooling function or enterprise bean.

AIX, Solaris Set up the DB2 environment properly in the WebSphere Application Server startupServer.sh if you plan to refer to Oracle, Sybase or IDB databases as administrative databases.

To modify startupServer.sh, find the following line in startupServer.sh in a then clause:
export LD_LIBRARY_PATH

Next, add the following lines BEFORE the export LD_LIBRARY_PATH line:

DB2_INSTANCE_HOME=/export/home/db2inst1
export DB2_INSTANCE_HOME
.$DB2_INSTANCE_HOME/sqllib/db2profile
LD_LIBRARY_PATH=$DB2_INSTANCE_HOME/sqllib/java12:$DB2_INSTANCE_HOME/sqllib/lib:$LD_LIBRARY_PATH
LIBPATH=$LD_LIBRARY_PATH
export LD_LIBRARY_PATH LIBPATH


For $DB2_INSTANCE_HOME, specify your DB2 instance home directory.
The README file at the end of the installation is not displayed, and Hotjava is the default web browser. Solaris Make sure that the Hotjava browser can be started. If not, use another browser to view the README file.
Java applications will not run reliably where the LIBPATH length exceeds 1548 characters. AIX Reduce the LIBPATH length to less than 1548 characters.
The Apache server will not start after installing the WebSphere Application Server plug-in for Apache server. All The plug-in installation added the line ose.mode=out to your Apache configuration file srm.conf in the /<apache_home>/conf directory. Open an editor on the srm.conf file, and remove or comment out the ose.mode=out line.
Connection is refused (error 500) when attempting to access servlets and JSP files. The Web server and application server are under stress and the Web server log contains the following 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 might be refused (error 146).

To resolve this condition, increase the file descriptor limit for the user from which the administrative server is started (ususally 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, log off and then log on.

To change the hard upper limit of the number of file descriptors in the kernel (which defaults to 1024 per CPU), you can edit the /etc/system config file to include a couple of entries:

set rlim_fd_max=4096
set rlim_FD_cur=1024


After you save the file, restart the machine for the changes to take effect.
Using Oracle, the following message displays, TransactionRolledBackException, when attempting 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.
WebSphere Application Server installation fails even though you are logged in as root. An error is displayed that states the user does not have root authority. Solaris Ensure the "whoami" command or /usr/ucb is in the path for the root logon.
The IBM HTTP Server will not install.

There are bad entries in the system file table: /etc/fstab. The swinstall fails in the analysis phase because the mount_all_file_systems option is true by default.

HP-UX Remove the bad entries from the /etc/fstab file and reinstall. If you cannot do so, edit the install_ihs_128.sh (or install_ihs_56.sh), adding the -x mount_all_file_systems=false option to the swinstall command.
The install directory for DB2 7.1 has changed (x:\Program Files\SQLLIB) and WebSphere Application Server Version 3.5 defaults to the old DB2 directory (x:/sqllib). The following error displays when WebSphere Application Server is started:

2140:An internal Windows NT error occurred
All Check to make sure that the admin.config file is pointing to the new DB2 directory (x:\Program Files\SQLLIB). Otherwise the default will point to the old directory (x:/sqllib). Modify the admin.config pointer to the DB2 driver if you have already installed and tried to start WebSphere Application Server and are getting the error.

Starting Application Server Components

Problem Op System Workaround
The WebSphere Application Server, when using DB2, does not start and the following error displays:
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 WebSphere Application Server 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.
The administrative server fails to start.

The failure is related to the lack of a new line character at the end of the wasdb2.log file.
The tracefile is created, but contains no message.
On Windows NT/2000, the Services panel reports:
The IBM WebSphere AdminServer service returned service specific error 10.

All Add a newline character to the end of the admin.config file located in the bin directory under the product installation root ( such as C:\WebSphere\AppServer\bin\admin.config or Windows NT).
The administrative server/application server runtime is running as non-root.

When running a servlet, the following message displays from the browser:
Server internal error
Then the following message displays in your_server-stderr.log:
open_unix_domain_server_socket_listener - bind/listen: The socket name isalready in use.
com.ibm.servlet.engine.oselistener.outofproc.ServerQueueException:EError: create_server 2

AIX See InfoCenter article 1.2.2.6 for the correct way to run as non-root.
The administrative server is running as non-root on Solaris and the following error message displays:
$ ./startupServer.sh operation failed,Not owner
Solaris Install Websphere as root user with the following steps:
  1. Move into the directory where WebSphere is installed (/opt/WebSphere).
  2. Type the command: chown -R nonRootUser AppServer(where nonRootUser is a valid user on the machine).
  3. Switch user to a non-root user: su - aUser.
  4. Go the WebSphere Home directory /vi /opt/WebSphere/AppServer/bin/admin.config and add the line com.ibm.ejs.sm.adminServer.bootstrapPort=2222.
  5. Run startupServer.sh.
  6. Start adminclient.sh serverHostName 2222.
  7. Start DefaultServer.
The thin servlet redirector configuration cannot be run when you are logged in other than as root. Solaris, AIX, HP-UX Thin Servlet redirector configuration runs only when you log in as a root..
You have trouble starting a secured (that is, security is enabled) administrative server or an application server on a Windows machine configured as a part of a Windows domain and 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.
The IBM HTTP Server will not start when you attempt to add a module using the Module Sequence form.

The following error message Invalid command 'LoadModule' displays and the server may not restart.

All Using the Module Sequence form added unwanted commands to the IHS httpd.conf file.

Edit the file and remove the following commands:
ClearModuleList LoadModule ibm_app_server_module<mod_ibm_app_server.dll path>

Administrative Console (GUI) and Command Line Tools

Problem Op System Workaround
The administration of an WebSphere Application Server administrative domain will not properly work if all nodes within the domain are at different FixPak levels of a release. All WebSphere Application Server administrative domain requires that all nodes be at the same FixPak level for the administration of the domain to properly work.
In a configuration with one node run as an administrative agent and another node as the administrative server, if the installation directory on the agent node is not the same as the installation directory on the administrative server node, starting an application server fails. All In the admininistrative console, edit the properties for the RemoteSRP bean under the Default Container of the administrative agent node so that the "Jar File" property specifies the correct path to the ibmwebas.jar (e.g. C:\WebSphere\AppServer\lib\ibmwebas.jar)
When starting the Administrative Console, the following error stating that the maximum number of open cursors is exceeded displays:

5803af6d DBMgr W Exception on database query: "select * from ejsadmin.REL_DEFN_TABLE where SOURCE_TYPE = ? or TARGET_TYPE = ?"
com.ibm.ejs.cm.portability.ResourceAllocationException: ORA-01000: maximum open cursors exceeded
at java.sql.SQLException.(SQLException.java:45)
at com.ibm.ejs.cm.portability.PortableSQLException.(PortableSQLException.java:22)
at com.ibm.ejs.cm.portability.ResourceAllocationException.(ResourceAllocationException.java:14)
at java.lang.reflect.Constructor.newInstance(Native Method)
at com.ibm.ejs.cm.portability.PortabilityLayerImpl.translateException(PortabilityLayerImpl.java:139)
at com.ibm.ejs.cm.pool.ConnectO.translateException(ConnectO.java:861)
at com.ibm.ejs.cm.proxy.ConnectionProxy.translateException(ConnectionProxy.java:84)
at com.ibm.ejs.cm.proxy.OracleConnectionProxy.prepareStatement(OracleConnectionProxy.java(Compiled Code))
at com.ibm.ejs.sm.util.db.DBMgr.executePreparedQuery(DBMgr.java(Compiled Code))
at com.ibm.ejs.sm.beans.RelationBean.ejbFindByEndpoint(RelationBean.java:1033)
at com.ibm.ejs.sm.beans.EJSRelationHomeBean.findByEndpoint(EJSRelationHomeBean.java:161)
at com.ibm.ejs.sm.beans.EJSRemoteRelationHome.findByEndpoint(EJSRemoteRelationHome.java:170)
at com.ibm.ejs.sm.beans._RelationHome_BaseStub.findByEndpoint(_RelationHome_BaseStub.java:371)
at com.ibm.ejs.sm.beans._RelationHome_Stub.findByEndpoint(_RelationHome_Stub.java:374)
at com.ibm.ejs.sm.beans.RepositoryObjectImpl.getRelationships(RepositoryObjectImpl.java:1079)
at com.ibm.ejs.sm.beans.RepositoryObjectImpl.getModelRelation(RepositoryObjectImpl.java:1119)
at com.ibm.ejs.sm.beans.RepositoryObjectImpl.isAClone(RepositoryObjectImpl.java:1318)
at com.ibm.ejs.sm.beans.RepositoryObjectImpl.getModelName(RepositoryObjectImpl.java:1342)
at com.ibm.ejs.sm.beans.ServerBean.initializeConfig(ServerBean.java:564)
at com.ibm.ejs.sm.beans.EJBServerBean.getConfig(EJBServerBean.java:183)
at com.ibm.ejs.sm.beans.ServerBean.getActiveAttributes(ServerBean.java:1038)
at com.ibm.ejs.sm.beans.ServerBean.readInstanceVariables(ServerBean.java:1004)
at com.ibm.ejs.sm.beans.ServerBean.getAttributes(ServerBean.java:81)
at com.ibm.ejs.sm.beans.EJBServerBean.getAttributes(EJBServerBean.java:122)
at com.ibm.ejs.sm.beans.EJSRemoteEJBServer.getAttributes(EJSRemoteEJBServer.java:245)
at com.ibm.ejs.sm.beans._EJSRemoteEJBServer_Tie._invoke(_EJSRemoteEJBServer_Tie.java:452)
at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(ExtendedServerDelegate.java:505)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:2261)
at com.ibm.CORBA.iiop.WorkerThread.run(WorkerThread.java:195)
at com.ibm.ejs.oa.pool.ThreadPool$PooledThread.run(ThreadPool.java(Compiled Code))
All To fix this problem:

  1. Update the initorcl.ora and increase 'open_cursors=200' to open_cursors=220.
  2. Stop and restart Oracle.
  3. Restart the Administrative Console
When the administrative console is downloaded from the Internet it doesn't run. All A JDK has to be present on the machine using the remote console.
And/Or set the JAVA_HOME.
And/Or put the JDK location in the PATH.
Issuing a command such as % ./wscp.sh -c "ApplicationServer list" results in the following error being displayed: An action to perform on ApplicationServer must be specified. AIX, Solaris, HP-UX The argument quoting is being lost by one of the shell scripts involved in executing the command -- wscp.sh and/or the script referenced by the JAVA_EXE environment variable.

Check these scripts to ensure they use "$@" (i.e. the quotes are required) in order to preserve the argument quoting.

In the HTTP Administrative Console, the Web application property sheet does not show up with the Netscape browser. Windows Use Microsoft Internet Explorer as your browser.
The WebSphere Control Program (WSCP) command line uses Tcl.

The Tcl variable is "errorCode" when command line commands are executed.The Tcl variable "errorCode" is used to store the result of a Tcl command that fails. The translation of a non-zero error message is no longer displayed.

All Previously, if a nonzero error occurred (and the Tcl interpreter's result string was not set), the translation of the error message was displayed. Now, both interactive users and script writers must check the errorCode variable to determine whether a command succeeded or failed.
The Java administrative console is not displaying correctly after installing the product. You did not install the Java administrative console while installing the product and used adminclient.bat to view the Java administrative console. 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, including the Java administrative console. An alternative is to install the administrative console on a remote machine, which can be used to administer the remote administrative server.
The Web-based browser administrative console is unavailable if the default server is stopped. All The Web administrative console runs under the default server. Stopping the default server makes the HTTP administrative console unavailable. Start the default server and then try restarting the HTTP administrative console.
Screens are not repainting or resizing properly when running the Java administrative console changes on a UNIX operating system with the Display exported to a Windows NT/2000 system running a Hummingbird Exceed 6.0.1 X Windows server.

The window appears to be empty or missing panes.

When you manually resize the window, the rest of the text and widgets are displayed.

Windows NT/2000 Do one of the following:
  • Install the Administrative Console on a machine that is remote from the Unix system running WebSphere Application Server. Then run the following command to connect to the remote UNIX machine:

    $WAS_HOME/bin /adminclient.bat <remoteHostName>

  • Use an alternative X Window manager on Windows NT.
  • Use Hummingbird Exceed Version 6.1 instead. Be sure to use the X configuration tool to modify the Screen Definition.
  • Use the following options for the Window Manager settings that appear under the Screen X tab in the Screen Definition configuration tool:

    Window Manager: Window Manager = Native Use Native WM for embedded clients = No First Window to display = No

  • 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:

    1. Open the Exceed Xconfig tool.
    2. Open Troubleshooting.
    3. 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.

    See InfoCenter article 1.2.2.4.1.1 for many more tips and instructions.

    Resizing the left panel of the Java administrative console causes the panel to become squashed and then cannot be resized. All Click the Topology view, then resize the left panel.
    The XML import feature of the Java administrative console does not completely handle security configurations. All Instead of the Java administrative console import, use the XMLConfig command line utility for security configurations that include passwords.

    The background for this recommendation is as follows:


    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.
    The .wscprc file does not load when the WebSphere Control Program (WSCP)is invoked. All The Java property user.home is used to locate the .wsprc file. Check the value for user.home and ensure that the .wscprc file is located in the directory designated by user.home.

    Optionally, when you invoke WSCP, use the -p option to specify the user.home directory and, thus, the location of the .wscprc file:
    -p <user.home_directory>/.wscprc

    Note: The user.home directory may differ among JDK version levels and platforms. On Windows NT/2000, the JDK 1.2.2 sets the user.home property based on the value of the USERPROFILE environment variable.

    After using the Java administrative console to delete a resource and create the resource again, the change is not immediately reflected in the WSCP. All To avoid problems due to inconsistent cached information, avoid issuing concurrent operations on the same object from within the WSCP and the console.

    If you encounter the described problem, 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 WSCP also refreshes the cache.

    After installing WebSphere Application Server, you elected to install the default configuration, and the fully-qualified domain name (FQDN) is not included in the Alias Host list of the default_host Virtual Host. Access by http://<FQDN>/servlet/snoop may fail. All Add a virtual host alias for the fully-qualified domain name (FQDN) of your machine running the Web Server. The short name is automatically defined, but some systems do not automatically define the FQDN:
    1. Go to the Topology view of the Administrative Console.
    2. Select default_host.
    3. Edit the Advanced properties panel and add a fully qualified virtual host alias, including domain name.
    4. Restart the Default Server Application Server.

    Enterprise Beans

    Problem Op System Workaround
    When a database does not support FOR UPDATE clause and the following access pattern is frequent, deadlocks could occur in the database.

    All Transaction 1:
    Select * from tb1 where id=1
    Select * from tbl2 where id=2
    ---------------------------- x
    Update tbl2 .. where id = 2
    Update tbl1 ... where id=1

    Transaction 2:
    Select * from tb1 where id=1
    Select * from tbl2 where id=2
    ----------------------------- x
    Update tbl2 .. where id = 2
    Update tbl1 ... where id=1

    If both transactions are at point x, then both have obtained read locks on data item represented by id=2. Now neither transaction can upgrade to write locks necessary to execute the next update statements. Usually, the database detects the deadlock and aborts one transaction. FOR UPDATE clause on select statements allows us to obtain a write lock while executing the select statement before point x and prevents the deadlock.
    While configuring the Resource Security to an existing Enterprise application a HotSpot Virtual Machine Error might occur while adding a clone of an Enterprise Java Bean. This will cause your administrative server to restart. HP-UX 11.0 (Advanced Custom Configuration) Disabling the HotSpot compiler will resolve the issue.
    This can be done by removing the HotSpot compiler from the runtime path.
    For example: mv /opt/WebSphere/AppServer/java/jre/lib/PA_RISC/hotspot
    /opt/WebSphere/AppServer/java/jre/lib/PA_RISC/hotspot.bak
    mv /opt/WebSphere/AppServer/java/jre/lib/PA_RISC2.0/hotspot
    /opt/WebSphere/AppServer/java/jre/lib/PA_RISC2.0/hotspot.bak
    The following error displays when trying to deploy specific beans within a jar file:
    Drive, com.transarc.systest.ejs.webpennies. EJBCount does not exist. Please verify the appropriate drive was given.
    Note: "Webpennies" and "EJBCount" in the above error message is the application used for testing.
    Solaris, AIX, Linux The error occurs when you try to deploy only one entity bean stored within a .jar file.

    Select the entire *.jar file for deployment. You are then given the option to click Yes to deploying all the entity beans within the file.

    JNDI lookup EJBHome fails to return org.omg.CORBA.Object instance.
    Try:
    {
    tmpObj = ic.lookup ("V3Phone");
    }
    catch (NamingException ne)
    {
    System.out.println("MyPhoneBookServlet FAILED to lookup \"EmployeeBean\":");
    ne.printStackTrace();
    }
    if (tmpObj instanceof org.omg.CORBA.Object)
    phoneHome = (V3PhoneHome)javax.rmi.PortableRemoteObject.narrow(tmpObj,V3PhoneHome.class);
    System.out.println("after phoneHome narrow" + phoneHome):


    Above println prints null for phoneHome because tmpObj is not an instance of a rg.omg.CORBA.Object.
    All Comment out the condition //if (tmpObj instanceof org.omg.CORBA.Object)
    The required attributes of an enterprise bean include the DeploymentDescriptor and JarFile attributes. The DeploymentDescriptor has a new format. All The attribute value must be a string that includes the remote interface name, a JAR file, and the node name, each separated by the @ symbol. The syntax is as follows:
    bean_remote_interface [ @jar_file ] @node_name ] ]

    Where bean_remote_interface is the name of the bean's remote home interface, jar_file is the full path name of the JAR file on the node for which the enterprise bean is being defined, and node is the name of the node where the enterprise bean is being created. The JAR file and the node name are optional, and are automatically supplied if they are not specified. The value for jar_file is taken from the value of the JarFile attribute. The value for node name is extracted from the fully-qualified name of the enterprise bean.
    There is no BLOB or CLOB support for WebSphere Application Server Version 3.5 on HP using DB2 with Container Managed Persistence (CMP). HP-UX Any CMP bean which is to be run on the HP platform with DB2 as its persistent store CANNOT designate a Serializable object type as a CMP field.
    Some enterprise beans request more database connections on DB2 than are configured for the database, resulting in trap errors on 8-way Windows NT systems. All  
    Enterprise bean clients are unable to interpret server-side exceptions in stack traces. All Enterprise bean clients must have access to server-side exception classes to interpret server-side exceptions in stack traces. Examine the server-side trace logs for the complete error information or make server-side classes available on the client.
    When trying to view a distributed transaction, the transaction monitor will not display and, if you persist in trying to access the transaction monitor, the Java administrative console hangs.

    All To stop the console from hanging, restart the administrative console. However, you still will not be able to access the transaction monitor.
    The Jetace tool displays this message when loading a JAR file:
    java.lang.NoClassDefFoundError
    All When using the Jetace tool, make sure all dependent classes (and dependencies those classes have) are on the classpath.

    See InfoCenter article 6.3 for guidance.
    The documentation regarding writing enterprise beans with bean managed persistence (BMP), located in "Chapter 9: More-advanced programming concepts for enterprise beans" in the PDF file adswpg00.pdf and in the HTML file atswpgad.htm, is incorrect. All 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 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()) {
    ...
    }

    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.
    In an inheritance 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 inheritance behavior. The behavior may be described by the following scenario:

    Consider an inheritance 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.

    Object Request Brokers (ORBs)

    Problem Op System Workaround
    Where to find documentation on the Request Interceptor Interface of the IBM Java ORB. All The documentation for the Request Interceptor Interface is located at:

    http://www-4.ibm.com/software/webservers/appserv/request_interceptors.html

    The Object Request Broker lacks interoperability between Version 3.5 and Version 3.0.2.1, Advanced Editions only. All To enable full interoperability for the Java ORB between Version 3.5 and Version 3.0.2.1, obtain the Fix Pack (Version 3.0.2.2) and apply it to your 3.0.2.1 installation. Interoperability is not supported between Version 3.5 and versions prior to 3.0.2.2.

    Servlets

    Problem Op System Workaround
    When a client prematurely ends a connection to the servlet engine the following error displays:
    nativeWrite operation: Status Code: -1
    All This error message is not indicative of a problem and occurs during normal operation as users close their browser or other network outages occur.
    If the clone is created on the same node and the option "Make XXX a clone" is not selected when creating the Model, the clone can not be created successfully. All This happens because two servlets can't use the same URI unless they are both clones or they are on different nodes. Otherwise the URI duplication error will occur.

    To fix this problem:
    If the clone is created on the same node, the option "Make XXX a clone" must be selected when creating the Model. If the clone is created on a different node, the option "Make XXX a clone" doesn't need to be selected.

    Any web application using the InvokerServlet installed prior to Fix Pack 3 will not work. After installing WebSphere Application Server Fix Pack 3, the following error displays:
    404 Not found error
    All The problem is due to a Fix Pack 2 change in the way URIs are handled.

    To fix this problem:

    1. Go to the Topology view of the administrative console.
    2. Under the web application, choose Auto-Invoker or InvokerServlet servlet.
    3. On the General Properties panel, select the Servlet Web Path List and click Edit.
    4. Modify the Servlet Path to end in "/*".
    5. Click OK.
    6. Click Apply.
    7. Stop and Restart the Application Server.
    When you choose the 'Add a servlet' option from the Wizard tab, the following error displays:
    RepositoryOpException: Unexpected naming exception and other exceptions.
    AIX Ignore the error. The servlets will be created.

    Java Server Pages Files (JSP files)

    Problem Op System Workaround
    The location of JSP files that reside in subdirectories of the Web application's document root are reflected in the names of the servlets generated by the JSP Enabler. For JSPs that are in deeply nested subdirectories or in subdirectories with long names, the file name of resulting servlet name may exceed the length allowed by the operating system. When this occurs the following message displays:

    Can't write: &gnt;
    All To fix this, try one of the following or a combination of all three workarounds:
    1. Reduce the subdirectory level that the JSP is nested.
    2. Shorten the length of the names of the directories.
    3. Shorten the names of the JSPs.
    Using JSP 1.1 to trace and debug JSPs is not available. All  
    The flastmod NCSA tag returns a false date and time. All If the target file for an flastmod query does not exist or cannot be found, the query response will be a false date and time (always "Wed Dec 31 19:00 1969").

    Ensure that the target of an flastmod query exists and can be found in the specified path.

    XML and XSL

    Problem Op System Workaround
    An XSL user needs to specify an XML Liaison. The version of XSL included with WebSphere Application Server Version 3.5 works with the Xerces XML parser, which is not included with the product. All Create a Liaison class for XML4J and pass it into the XSLTProcessor constructor. For example:
    XSLTProcessor processor = XSLTProcessorFactory
    .getProcessor(new com.lotus.xml.xml4j2dom
    .XML4JLiaison4dom());

    Connection Pooling

    Problem Op System Workaround
    When using Oracle as the administrative database and DB2 for application data, and deploying a CMP bean to use the DB2, the following error displays:
    .java.sql.SQLException:
    No suitable driver
    All In the Java administrative console:
    1. Go to the Topology view.
    2. Select the Application Server on which the bean is created.
    3. Go to the General tab in the property sheet on the right pane.
    4. Left click on Environment property.
    5. In the Property Editor, enter:
      For Variable Name
      PATH

      For Value
      x:\SQLLIB\BIN (x is where DB2 is installed)

    6. Click Add and then OK.
    7. Click Apply in the Application Server property sheet.
    8. Start the default server.
    JTA support doesn't work correctly with Sybase JDBC driver. All Create the table with the JTA flag off, and then access the table with JTA on.
    Under load conditions, 512 MB systems only support a DB2 connection pool size of 10 connections. AIX, Solaris To run more than 10 connections, you will need more than 512 MB. On average, DB2 connections will use 1-2 MB each.

    When sending a large number (for example, 100 simultaneous users) of requests, use 512 MB to run with 10 connections. The 512 MB includes the administrative server, application process, and so on. DB2 connections usually run about 1.5 MB to 2 MB, so if you want to run more than 10 connections, you will need more than 512 MB.

    HttpSession

    Problem Op System Workaround
    In article 1.2.3.2.3 of the InfoCenter, under "Setting up the HttpSession database on DB2/390," step 1, bullet 2 is incorrect. All Use the following SQL script instead:

    CREATE TABLE DATABASE.SESSIONS
    (ID VARCHAR(64) NOT NULL,
    PROPID VARCHAR(64) NOT NULL,
    APPNAME VARCHAR(64),
    LISTENERCNT SMALLINT,
    LASTACCESS DECIMAL(21),
    CREATIONTIME DECIMAL(21),
    MAXINACTIVETIME INTEGER,
    USERNAME VARCHAR(256),
    SMALL VARCHAR(3313) FOR BIT DATA,
    MEDIUM LONG VARCHAR FOR BIT DATA,
    LARGE BLOB(2M),
    TROW ROWID GENERATED ALWAYS )
    IN WAS.CMPTB001;

    CREATE TYPE 2 UNIQUE INDEX CMP.CMPND001 ON DATABASE.SESSIONS (ID, PROPID) USING VCAT DSN610; COMMIT;

    CREATE LOB TABLESPACE CMPLS001 IN WAS
    BUFFERPOOL BP32K
    LOCKSIZE LOB
    USING VCAT DSN610
    CLOSE NO;

    CREATE AUX TABLE CMP.CMPLT001
    IN WAS.CMPLS001
    STORES DATABASE.SESSIONS
    COLUMN LARGE;COMMIT;

    CREATE INDEX CMP.CMPLI001 ON CMP.CMPLT001 USING VCAT DSN610;COMMIT;
    When you specify a value other than zero for the Session Timeout on a web application, the value specified for the Invalidate Time on the Session Manager is overridden. All Specify "0"(zero is the default) for Session Timeout on a web application if you want session timeout to be the value designated for Invalidate Time on the Session Manager.

    Specify "-1" for the Session Timeout on a web application (as prescribed in the Servlet 2.2 API) if you never want the session to time out.

    Important Note: The value for the Timeout is the value specified when the session is originally created. Thus, if you create a session and then change the value for Session Timeout/Invalidate Time, and the session has not timed out, characteristics for the session will not change until it expires. You need to manually delete session records from the underlying database if you had sessions created with a "-1" Session Timeout parameter.

    The Session Manager's native access support is currently not available. All Use the JDBC access until further notification.
    The Session Manager's EJB mode of persistence on advance edition is no longer supported. All Use the JDBC access (direct to database)

    Workload Management

    Problem Op System Workaround
    The WebSphere version of Remote Invocation Method compiler (RMIC) is not properly installed. WLMJAR does not operate correctly with the JDK version of RMIC. AIX The correct version of RMIC should be in the path. Usually there is a link in /usr/bin for RMIC, and the problem can be corrected by executing:
    ln -sf
    /usr/WebSphere/AppServer/hosts/default_host/
    admin/install/aix/rmic
    /usr/bin/rmic
    The WLMJAR program might choose the JDK version of the WebSphere Application Server version. Windows NT/2000 Ensure that your JDK \bin directory does not appear before the WebSphere Application Server \bin directory in your PATH environment variable.

    Networking

    Problem Op System Workaround
    WebSphere Standard and Advanced tolerate the presence of more than one network on a single platform as long as the environment used to run WebSphere is configured such that the following conditions are met:
    • The primary hostname refers to the default - primary - network interface.
    • The Domain Name Server's response to a query of the platform's hostname returns the address of the primary network interface.
    • The IP for the platform resolves to the hostname and vice versa for both formats of hostname: fully qualified and not fully qualified.
    All Here is a good example of a multi-network interface card Windows NT platform that conforms to the above:

    d:\work>ipconfig
    Windows NT IP Configuration
    Ethernet adapter ND53004:
    IP Address. . . . . . . . . : 208.180.235.122 (Primary IP)
    Subnet Mask . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . : 208.180.235.1
    Ethernet adapter NdisWan3:
    IP Address. . . . . . . . . : 129.17.33.12
    Subnet Mask . . . . . . . . : 255.255.254.0
    Default Gateway . . . . . . : 129.17.32.1

    d:\work>nslookup 208.180.235.122
    Server: rose.tyler.net
    Address: 205.218.118.1 Name: cdm-235-122-pflu.cox-internet.com (Resolves to hostname)
    Address: 208.180.235.122

    d:\work>hostname
    cdm-235-122-pflu (hostname is set correctly)

    d:\work>nslookup cdm-235-122-pflu (and resolves to the same)
    Server: rose.tyler.net
    Address: 205.218.118.1
    Name: cdm-235-122-pflu.cox-internet.com
    Address: 208.180.235.122 (IP when NOT fully qualified)

    d:\work>nslookup cdm-235-122-pflu.cox-internet.com (also resolves to the same)
    Server: rose.tyler.net
    Address: 205.218.118.1
    Name: cdm-235-122-pflu.cox-internet.com
    Address: 208.180.235.122 (IP when fully qualified)

    Security

    Problem Op System Workaround
    Customers want to protect individual JSP files based on the Webpaths (URIs) and do not want to protect all the JSP files (*.jsp) in the system. The documentation for adding JSP URI to a Web application suggest using "Add JSP or Web resource" task. This task adds the JSP URI but does not add the JSP to the web application.

    When you configure steps to protect the JSP Webpaths (URIs), the Webpaths (URIs) are treated as Web server resources because they are not part of a Web application. Therefore, security doesn't work as intended.

    All Do not use the "Add a JSP or web resource task" to introduce new JSP Webpaths (URIs) and to associate with web applications. If you have already done so, first remove all the Webpaths (URIs) and then follow these steps:

    1. Select the Topology View.
    2. Expand Node->App Server->Servlet Engine to view the web application.
    3. Select the JSP file processor servlet in that application.
    4. In the configuration panel for that JSP file, there is a list of Web paths; it should contain /default_host/<:webapp-path>/*.jsp
    5. Click Add (to add to the web path list).
    6. Enter the Webpaths (URIs) you want to protect (e.g., /default_host/<:webap-path>/toBeProtected.jsp)
    7. Repeat (6) for all the JSP files you want to protect.
    8. Apply and complete this task.
    9. Follow security configuration steps to protect these newly added JSP files.
    10. Restart the Application server.

    You encounter the following error when starting the WebSphere Administrative Server:

    com.ibm.ejs.security.registry.RegistryErrorException:
    Windows NT: Access is denied

    Windows NT/2000 The user ID that will be used to start the WebSphere server in Windows NT or Windows 2000 platforms needs Administrator rights. Add the user ID under which the server is running to the group.
    When using WebSphere Application Server with Domino Versions 5.02, 5.02B, and Domino 5.03 LDAP directories, you encounter problems, such as intermittent server hanging. The problems occur when WebSphere is enabled, with LTPA as the authentication mechanism.

    Also, Domino Version 5.05 is required for Windows 2000 support.

    All  
    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 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 cannot 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/2000, 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

      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/2000, 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.
    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 situation occurs especially when using a DMZ configuration, particularly the servlet redirector scenarios. All Specify instead com.ibm.CORBA.SSLPort.

    If you 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>
    If a model (or one of the clones) is secured, and WLM is enabled, accessing a bean in the cloned environment results in an 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.
    After changing the password of the user ID in the user registry, you have problems starting WebSphere Application Server because the user ID and password are invalid. The password of the user ID referred to is associated with WebSphere and configured in the UserRegistry task panel.

    Windows NT/2000 The only way to change the user ID and password that would not affect other configuration information is to:
    1. Before changing the user ID and password in the registry and while the user ID and password are still valid in the registry, start the WebSphere Administrative Server and the WebSphere Administrative Console.
    2. Start the user management utility (LocalOS or LDAP tools), and then change the password.
    3. Make the corresponding change to the WebSphere Application Server user registry configuration:
      1. Select Global Security Settings, then User registry, then ServerID and password.
      2. Apply the changes.
    4. Restart the WebSphere Application Server.

    Performance and Stability

    Problem Op System Workaround
    Applications running with several large objects cause poor performance and eventually the Application Server will fail. All A performance and stability enhancement provided in the Util Delegate class can be used by application servers to improve performance.

    Set the command line options for the application server with this property:
    -Djavax.rmi.CORBA.UtilClass=com.ibm.CORBA.iiop.Util
    -Dcom.ibm.CORBA.iiop.noLocalCopies=true
    DB2 databases are local and multiple connections cannot be established successfully. Solaris, AIX Catalog the DB2 databases using a TCP/IP loopback.
    To implement TCP/IP loopback without having the need to change the application to connect to the new alias and the USER and USING parameters, step 5 below does the trick.
    1. Set up a TCP/IP port in /etc/services if a port for remote DB2 clients has not been setup yet.
    2. Ensure that the TCP/IP communication protocol has been specified by the DB2COMM registry parameter. To check the current setting of the DB2COMM parameter, enter 'db2set DB2COMM'. To update the DB2COMM registry variable to include TCP/IP, use the db2set command.
      Example: db2set DB2COMM=,tcpip
    3. Update the SVCENAME database manager configuration parameter to the connection service name as defined in /etc/services (step 1).
      Example: db2 update dbm cfg using svcename
    4. Catalog the loopback node.
      Example: db2 catalog tcpip node remote 127.0.0.1 server
    5. Catalog the database as follows:
      • db2 catalog db as
      • db2 uncatalog db
      • db2 catalog db as at node
      • Restart DB2 to refresh to directory cache.
    Note:For background information of the problem, please see the technote:http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/document.d2w/report?&fn=DWEB-4MKHBD.

    OLT and Debugging

    For this release, Standard/Advanced provides remote and distributed Java debugging support or tracing capabilities on Windows NT/2000, AIX, HP/UX, Linux, Linux/390 and Solaris, as described below:

    Problem Op System Workaround
    In order to install the debugger on Solaris, the customer should run the "dbgsetup" script. But, as shipped, this script does not have the execute bit set. All In order to run the script, the customer should run the following command:
    chmod 755 dbgsetup
    Context sensitive help inside OLT/DD is not available. Windows NT  
    The Distributed Debugger does not start when executing trace and debug. HP-UX  
    Because of JDK problems, the IBM Distributed Debugger is not currently supported. Solaris,HP-UX  
    When running the OLT Viewer, you attempt to change the Execution Mode in the Client Controller for a connected client. When you click Apply, the view freezes. Windows NT/2000 3.5, 3.5.1, 3.5.2 only. This problem has been fixed in 3.5.3. Set the Execution Mode properly in the Client Controller for the Default settings before you begin tracing. Do not attempt to change the Execution Mode after starting the trace.

    Tracing

    Problem Op System Workaround
    Dynamic tracing from the Java administrative console (Console->Trace->Enabled) on a Windows NT workstation does start properly with javaw. Windows NT Edit the adminclient.bat file and make the following modification:

    Change javaw to java in the following line:

    @start %JAVA_HOME%\bin\javaw -Xminf0.15 -Xmaxf0.25 -classpath %WAS_CP%
    %CLIENTSAS% -Dcom.ibm.CORBA.principalName=%COMPUTERNAME%/AdminClient
    -Dserver.root=%WAS_HOME% com.ibm.ejs.sm.client.ui.EJSConsole %DEST%
    %DESTPORT% %DEBUGOPTS% %QUALIFYNAMES%

    National Language Version Issues/Limitations

    Supported locales

    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.

    Language Windows NT/2000 Solaris AIX HP-UX
    Brazilian Portuguese IBM-850 pt_BR pt_BR.ISO8859-1 No Brazilian Portuguese locale
    French IBM-850
    IBM-858
    fr
    fr.ISO8859-15
    fr_FR.ISO8859-1
    fr_FR.ISO8859-1@euro
    fr_FR.ISO8859-1
    fr_FR.ISO8859-15@euro
    German IBM-850
    IBM-858
    de
    de.ISO8859-15
    de_DE.ISO8859-1
    de_DE.ISO8859-1@euro
    de_DE.ISO8859-1
    de_DE.ISO8859-15@euro
    Italian IBM-850
    IBM-858
    it
    it @ISO8859-15
    it_IT.ISO8859-1
    it_IT.ISO8859-1@euro
    it_IT.ISO8859-1
    it_IT.ISO8859-15@euro
    Japanese IBM-943 ja
    ja_PC.PCK
    ja_JP.IBM.eucJP
    Ja_JP.IBM-942
    ja_JP.SJIS *
    Korean IBM-1363 ko ko_KR.IBM.eucKR ko_KR.eucKR *
    Simplified Chinese IBM-1386 zh zh_CN.IBM.eucCN zh_CN.hp15CN *
    Spanish IBM-850
    IBM-858
    es
    es @ISO8859-15
    es_ES.ISO8859-1
    es_ES.ISO8859-1@euro
    es_ES.ISO8859-1
    es_ES.ISO8859-15@euro
    Traditional Chinese IBM-950 zh_TW
    zh_TW.big5
    zh_TW.big5 zh_TW.big5 *

    Issues and limitations

    Problem Op System Workaround
    All Languages
    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 after general availability 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.

    See InfoCenter article 0.0.7 for a full account of the differences between English and translator versions.

    The word "True" is displayed in English on the Default Model Properties page in the Administrative Console. All Ignore the appearance.
    Installing WebSphere Application Server in more than one causes the different language versions to overwrite each other. Also, with native install (using SMIT), when more than one language is installed, an error displays. AIX 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.

    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.

    The Cancel button in uninstallshield does not work.

    When you click Cancel in 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.
    Brazilian Portuguese
    The time displayed with events on the administrative console is one hour earlier than the actual system time. Windows NT/2000, AIX, Solaris  
    Japanese
    Japanese characters are distorted on the following installation panels:
    • Choose Application Server Components panel, all of the characters in Component Description.
    • On some panels after the Database Options panel, kana-kan status characters at the bottom left corner.
    • Selected Install Options panel, all of the selected option strings.
    AIX
    1. Install X11.fnt.ucs.ttf - AIXWindows unicode TrueType fonts.
    2. Logout and login again.

      This must be done to reflect installation of the proper fonts.

    3. Run xlsfonts | grep 0208 to confirm monotype fonts are installed.
    4. 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 dialog on which you select the database home directory (DB_HOME) does not display the directory entry. startupServer.sh and admin.config are not updated. Solaris
    1. Set the following value for the locale on the shell: LANG=C
    2. Start install.sh.
    Java administrative console pages do not display properly for Japanese AIX customers using the eucJP locale. AIX You will need to change some text files:

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

    Spanish
    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 Manually resize the window.
    Chinese Simplified
    On AIX V4.3.3:
    • Fix Pack U466148 must be applied before installing WebSphere Application Server.
    • WebSphere Application Server only supports one Simplified Chinese Charset, BGK.
    AIX Fix Pack U466148 is available on the 4.3.5 installation media. It is not necessary to upgrade the operating system to 4.3.3 to install this Fix Pack.
    Chinese Traditional
    Problems with character sets other than BIG5 on AIX V4.3.3. AIX WebSphere Application Server only supports the BIG5 Traditional Chinese Character Set for AIX V4.3.3.
    While using the product, corrupt panels and code page conversion errors appear. Solaris To install and use the WebSphere Application Server with a minimal amount of corrupted panels, follow the procedure below:
    1. From a command line, type: export LC_ALL=tchinese export LANG=tchinese
    2. Install WebSphere Application Server.
    3. From a command line, type: export LC_ALL=zh_TW.BIG5 export LANG=zh_TW.BIG5
    4. Create the WebSphere Application Server database as instructed in the documentation.
    5. Repeat step 1.
    6. Start the administrative server.
    7. Repeat step 3.
    8. Start the administrative console.

    To uninstall WebSphere Application Server with a minimal amount of corrupted panels:

    1. From a command line, type: export LC_ALL=tchinese export LANG=tchinese
    2. Uninstall WebSphere Application Server as instructed in the documentation.
    All Double-Byte Languages
    In the WebSphere Administrative Console, Asian characters show up as empty boxes. HP-UX 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 fonts in the future. 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).

    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.

    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 Any combination of less than three Chinese characters or any number of English characters works fine. Use English or fewer than three double-byte characters.

    Samples

    Problem Op System Workaround
    After installing the GM code, applying Fix Pack 3 and restarting the application, the samples do not work and 500-type errors with SQL references are displayed. All Drop sample database and follow the instructions in the Sample Gallery to recreate the sample database. Windows NT users may need to reboot after installing the Fix Pack.
    When you use DB2 and overlap the WebSphere Application Server samples installation with the installation of WebSphere Studio samples, the Studio servlet does not work because it tries to use the table name (WSDEMO) as the alias (WSDEMO). All The WebSphere Studio samples configuration expects to have a DB2 database called sample created by a user other than WSDEMO. The Studio version of the CreateDatabase servlet will create and populate the tables that the Studio samples need, and give them a WSDEMO alias.

    The Application Server samples can have a DB2 or other relational database (Oracle, Sybase, etc.) designated with any name. The Application Server samples version of the CreateDatabase servlet creates tables using the WSDEMO userid which becomes part of the table name.

    Therefore, if the Application Server samples are installed first and a DB2 database is created with the name sample, the sample configuration instructions use sample as an example database name. Although the name sample isn't required, most users use it because it is the example.

    Because dataSources are used in a certain way, it is necessary to change the name of the database and the database name that it points to. The samples code also needs to be changed because it uses the names in the .servlet files.

    Follow these steps:

    1. When creating the DB2 database during "DB2 Database Configuration", name the database something other than "sample."
    2. When creating the dataSource during "DB2 Database Configuration", name the dataSource something other than "sample."
    3. Edit the samples' .servlet files and change the dataSourceName and database name to the names used during creation. These files are located in /AppServer/hosts/default_host/WSsamples_app/servlets/WebSphereSamples/[Sample].

      The lines in the servlet file look like this:
      Database Name: --> change "sample" to [whatever]
      DataSource Name: --> change "sample" to [whatever]
    WebSphere Samples installed prior to Fix Pack 3 will not work after running in Servlet 2.2/JSP 1.1 Full Compliance mode. After installing WebSphere Application Server Fix Pack 3, the samples display the following error:
    404 Not Found
    All The problem is due to a Fix Pack 2 change in the way URIs are handled.
    To fix this problem:
    1. Go to the Topology view of the administrative console.
    2. Under the Node, expand Default Server, and then Default Servlet Engine.
    3. Under Default Servlet Engine expand the WSamples_app or the WSsamplesIDB_app or the WSsamplesDB2_app web application.
    4. Under this web application, choose the Auto-Invoker servlet.
    5. On the General Properties panel, select the Servlet Web Path List and click Edit.
      The value will be either default_host/WebSphereSamplesIDB/servlet for the WSsamplesIDB_app web application or default_host/WebSphereSamples/servlet for the WSsamples_app and WSsamplesDB2_app web applications.
    6. Modify the Servlet Path to end in "/*" .
    7. Click OK.
    8. Click Apply.
    9. Stop and restart the Default Server Application.
    Bean Scripting Framework(BSF) has been disabled because of a memory leak.

    Note:The Bean Scripting sample will not work as a result of BSF being disabled.

    All BSF is not supported at this time.
    WebSphereSamples fails with /servlet/xxx not found when using fully-qualified hostname. All If the WebSphereSamples fail when using the fully-qualified hostname, but run successfully when using the IP Address or localhost, add a virtual host alias for the fully-qualified domain name (FQDN) of your Web server. The short name is automatically defined, but some systems do not automatically define the FQDN:
    1. Go to the Topology view of the Administrative Console.
    2. Choose default_host.
    3. Edit the Advanced properties panel and add a fully qualified virtual host alias, including domain name.
    4. Restart the Default Server Application Server.

    InfoCenter

    Problem Op System Workaround
    The Search function for the InfoCenter does not work with Netscape browsers. All Use a browser other than Netscape.
    When installing WebSphere Application Server Version 3.5, and trying to access the InfoCenter, a browser appears prompting you to get the full InfoCenter. After clicking the link, Topic 0.0.2 loads in the left frame of the same window and displays that this version of the documentation is not complete and that you need the full InfoCenter. When you click the link to the full InfoCenter, the WebSphere Application Server: Library Page is loaded in the left frame of the browser and can not be sized to display the whole site. All
    1. Click the browser's Back button.
    2. Right click the link for the full InfoCenter.
    3. Click Open in the new window.
    4. This forces the link to open in a new browser and you can navigate the page.

    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. The installation guides are also available from the online InfoCenter.
    When opening the InfoCenter or its files using a Netscape browser, you might receive this message:
    file not found

    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/2000 Do the following:
    1. Start Windows Explorer.
    2. Click View, then select Options.
    3. Click the File Types tab.
    4. Scroll the Registered File Types list to Netscape Hypertext Document and double click.
    5. Under Actions, double click Open.
    6. Uncheck the Use DDE option.
    7. Click OK, then close.

    With the Use DDE (Dynamic Data Exchange) option off, the window errors that complain that 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 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):
    1. Configure Netscape:
      1. Set your CLASSPATH to include (in this order) each Jar file in the MOZILLA_HOME/Java/classes directory; the Java classes.zip file found in /usr/java1.1/lib.
      2. 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.
    2. 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/2000 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, HP-UX  
    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.