Welcome to IBM(R) eNetworkTM On-Demand Server. This README contains late-breaking information about installing and using On-Demand Server. It also contains troubleshooting information and techniques that you can use to prevent errors from occurring. This information corrects and supplements other documentation in the product package. For the latest information and updates, visit the IBM eNetwork On-Demand Server Web site.
Problem: Users have problems loading an applet and the server receives a "local class not compatible" message.
Explanation: This situation can occur when Internet Explorer users access different versions of an applet from two different servers. If a newer version of an applet is accessed first, the applet is stored in the browser's cache. If the user then accesses an older version of the applet that uses the same namespace but resides on a different server, the applet will not be able to load because of the version conflict. To access the older version, the user must clear the browser's cache and remove all objects. For complete instructions, see Setting up software for users in the On-Demand Server documentation.
Problem: Javascript error "object expected" when trying to access Applet Launcher
Explanation: This problem can occur when a Web server attempts to send frames larger than the network can handle. To fix this, set the maximum send/receive size in your network adapter to be about 4096. This problem occurs only if both the client and the server have the frame size set too large. Otherwise, the TCP protocol negotiates to the smallest size. In small network when everything is on the same subnet and same LAN, this does not occur. It is more likely to occur in larger networks where there are sometimes routers involved in client/server communication.
On OS/2 and Windows NT, removing eNetwork On-Demand Server may leave behind subdirectories and files that contain personal user information, such as log files, configuration files, and HTML files. If you do not want these files, delete them manually. However, when eNetwork On-Demand Server and Host On-Demand coexist on the same drive, they share the same main directory, /onDemand. Do not delete the /onDemand directory unless you are removing both products.
There is a capitalization problem in the index.htm file on the AIX CD that prevents you from accessing the documentation in your browser. You can fix the problem by editing the file and changing the path in the links for each langauge from /help/ondemand/ to /Help/OnDemand/ .
License Use Management (LUM) Runtime 4.3.1.2 must be installed with On-Demand Server.
If you attempt to install On-Demand Server (by selecting OnDemand.base) without
upgrading LUM to 4.3.1.2, you will receive a failure message. From the
software options menu, select
under ifor_ls.base in addition to OnDemand.base.
You should also install the GUI component of LUM if your On-Demand Server
is also going to be used for the license server.
If you are installing License Use Management on AIX in a non-English locale, you need to install the ipfx.msg.locale.rte fileset. This fileset resides on the AIX installation CD. This fileset may not show up when doing a list of filesets on the install media, in which case you must enter it manually. You will need to perform some extra steps if you need the Brazilian translation because the IPFX message fileset (ipfx.msg.pt_BR.rte) does not exist. To get the translation, install the pt_PT fileset, create a /pt_BR directory, and copy the missing CAT file (ipf.cat) into it. For example, if IPFX is installed in the /usr/lpp directory,
WebSphere Application Server 1.1 is recommended in place of WebSphere 1.0 . WebSphere 1.1 is installed when you install On-Demand Server as documented.
If you specify GUESS in the response.res response file, the following will be guessed.
When installing OnDemand.base, warning messages appear indicating that the file names are greater than 128 characters in length and that the file already has an entry that is not owned by any installed fileset. These are Base Operating System (BOS) errors that will be resolved in a future fix level of BOS. It does not indicate a problem with the install and no action is required.
On-Demand Server for AIX and License Use Management for AIX use different Japanese locales. On-Demand Server uses the ja_JP locale. License Use Management uses the Ja_JP locale. Set your LANG variable appropriately before running the respective product.
On-Demand Server authentication fails when running with JDK 1.1.6 Beta for AIX.
To bypass the problem, turn off the JIT compiler by editing the file,
/usr/lpp/IBMWebAS/properties/server/servlet/servletservice/jvm.properties
and change the line
java.compiler=jitc
to:
java.compiler=off
Language | Code page | Locale |
---|---|---|
Brazilian-Portuguese: | ISO8859-1 | pt_BR |
French: | ISO8859-1 | fr_FR |
German: | ISO8859-1 | de_DE |
Italy: | ISO8859-1 | it_IT |
Spanish: | ISO8859-1 | es_ES |
Japanese: | IBM-eucJP | ja_JP |
Korean: | IBM-eucKR | ko_KR |
Simplified Chinese: | IBM-eucCN | zh_CN |
Traditional Chinese: | IBM-eucTW | zh_TW |
On OS/390, the adduser command will not add a user ID unless an OMVS Segment is defined to RACF for the user ID. The instructions for defining an OMVS Segment are contained in OS/390 OpenEdition Planning (SC28-1890) and OS/390 Security Server (RACF) Security Administrator's Guide (SC28-1915).
If Lotus Domino Go Webserver is slow to startup on a second level MVS system, follow these steps:
# OS/390 ServletExpress Only! # # The ncf.jvm.threads.max property is used to increase the number of # threads that the JVM is allowed to create for threaded servlets, # chaining servlets, or filtering servlets. If any of these types of # servlets are being executed, this property will need to be set to # accommodate the threading needs. ncf.jvm.threads.max=80 # # OS/390 ServletExpress Only! # # Define the OS/390 OE native log debug level. The # following define the current debug levels: # # Level 0 # --------------------------------------------------- # - OS/390 OE specific tracing off. # # Level 1 # --------------------------------------------------- # - Trace messages in JNI wrappers. # - Trace messages in the ICS native library for JNI # calls made during servlet processing. # - Trace messages in OE Data Conversion Utility # routines. # # Level 2 (Includes Level 1.) # --------------------------------------------------- # - Trace messages in the ICS native library for JNI # calls made to convertgetBytes_AtoE(). # ncf.native.os390.debug=1
ncf.jvm.classpath=/usr/lpp/java/J1.1/lib/classes.zip :/usr/lpp/ServletExpress/lib/servexp.jar :/usr/lpp/ServletExpress/lib/jsdk.jar :/usr/lpp/ServletExpress/lib/x509v1.jar :/usr/lpp/ServletExpress/lib/jst.jar :/usr/lpp/ServletExpress/lib :/usr/lpp/ServletExpress/web/onDemand/classes
ncf.jvm.classpath=/usr/lpp/ServletExpress/lib/servexp.jar :/usr/lpp/ServletExpress/lib/jsdk.jar :/usr/lpp/ServletExpress/lib/x509v1.jar :/usr/lpp/ServletExpress/lib/jst.jar :/usr/lpp/ServletExpress/lib :/usr/lpp/ServletExpress/web/onDemand/classes :/usr/lpp/java/J1.1/lib/classes.zip
To prevent excessive CPU utilization problems on OS/2 systems that are used as
LUM servers, install the MPTS mini-FixPak.
Note: Systems at FixPak level WRx8423 or higher
do not require a mini-FixPak upgrade.
OS/2 Warp Server Entry/Advanced | FixPak WRx8421 |
OS/2 Warp Server SMP | FixPak WRx8504 |
Any server with TCP/IP 4.1 | FixPak WRx8600 |
Close all programs before you install or uninstall the eNetwork On-Demand Server for OS/2. If any programs are running, the eNetwork On-Demand Server for OS/2 might not install or uninstall properly.
When installing OS/2 Warp Server Advanced for the first time, or to run with the tuning defaults, do the following prior to installing eNetwork On-Demand Server for OS/2:
If the LaunchPad turns gray or the buttons are obscured after installation, move a window over the LaunchPad to force it to repaint. If you continue to have problems returning the LaunchPad to its original color, shutdown and restart your computer.
Do not attempt to update/reinstall a preexisting version of the Java Runtime Environment (JRE) 1.1.6 while programs (such as Lotus Domino Go Webserver and the Navigator browser), are running. Any files that access the JRE during the installation process may not be properly replaced or updated.
When eNetwork On-Demand Server installs Lotus Domino Go Webserver, previous Domino Go configuration information is not retained. As a result, Network Station Manager will not configure properly after you install the eNetwork On-Demand Server. To fix this problem, make the following changes after you install eNetwork On-Demand Server:
Exec /networkstation/admin x:\NSTATION\servbase\cgi-bin\nsmcgain.exe Exec /networkstation/cgi/* x:\NSTATION\servbase\cgi-bin\* Pass /networkstation/* x:\NSTATION\servbase\html\* Authorization /networkstation/* x:\NSTATION\servbase\bin\nsmgauth.dll:nsmGoAuthwhere x represents the drive where Network Station Manager is installed. You can also cut these 4 lines from httpd.$nf (the backup copy of httpd.cnf) and paste them into the post-installation version of httpd.cnf.
The JIT compiler will corrupt the ProfileManagement.registry file when profile management information is updated from the Applet Launcher. For this reason, the JIT compiler is set to OFF. If you or your users are not going to update profile management information from the Applet Launcher, you can turn on the JIT to improve Java performance with Lotus Domino Go Webserver.
If you are installing On-Demand Server over Network Station Manager, you should first remove the IBM DHCP Protocol Driver and replace it with the IBM Intermediate Support Driver from the On-Demand Server CD.
Do not attempt to install Network Station Manager over On-Demand Server. Although the installation completes successfully, the httpd.cnf file used by Lotus Domino Go Webserver is not updated, preventing you from configuring Network Station Manager.
You must install the IBM Intermediate Support Driver from the product CD in order to use the BINL server.
There is an known problem with Windows NT 4.0 (with Service Pack 3) on computers with multiple processors that causes the NT Server to hang after the IBM Intermediate Support Driver is installed and the computer is restarted. To avoid this problem, apply the ndisfixi.exe fix from Microsoft as follows:
If you are using Lotus Domino Go Webserver on Windows NT, it must be installed as a service, not as an application. When you install Lotus Domino Go Webserver, make sure the NT Service option is checked on the Select Components window. It is checked by default.
Problem: Configuration management tree is not sorted properly. Also, a java.lang.ArrayIndexOutOfBoundsException is recorded for the configuration management function in the Tivoli logs.
Explanation: For some of the languages supported by On-Demand Server, this problem can be generated when On-Demand Server is installed on Windows NT and is using the JRE provided by JDK 1.1.6 rather than the JRE that is installed with On-Demand Server. To fix the problem, either disable or upgrade the Just-In-Time (JIT) compiler.
When deleting multiple clients in a single action in the DHCP configuration, it is possible that at least one of the clients will not be removed from the view. Click Refresh to remove all deleted clients from the view. This problem does not occur if you select and delete clients one at a time.
If you manually make configuration changes to any of the TCP/IP servers, the changes you make are not reflected in configuration management until you restart the Web server and then start configuration management. These files are read only during the loading of servlets.
Problem: HTTP Error 404 when trying to access configuration management
If Internet Information Server (IIS) Version 4.0 is the Web server, it is possible to accidentally remove the virtual directory used in the URL (/IBMWebAS) by installing and uninstalling WebSphere Application Server several times. To recover, you must remove and reinstall IIS Version 4.0.
There is a problem in the JRE and JDK for Japanese Windows NT in which the system time zone is always reported to be Japanese Standard Time (JST). Because of this, the date and time used to create the log file names on the server will be off by the difference in hours between JST and the actual system time zone. The actual trace and log records, however, reflect the time zone set by the client where the records are generated.
Two of the supported Web servers, Netscape Enterprise Server 3.5.1 and Microsoft Internet Information Server (IIS) 4.0, allow multiple Web servers operating on the same computer. On-Demand Server handles multiple Web servers as follows:
If you have multiple Web servers on Windows NT that require manual installation of the application server, do the following:
If the Web server used by On-Demand Server is stopped, users' sessions with their applets are lost. Users need to close their browser and log back in to On-Demand Server once the Web server is restarted.
To ensure that Lotus Domino Go Webserver will properly initialize WebSphere, wait several minutes after shutting down Lotus Domino Go Webserver before you attempt to restart it.
If On-Demand Server is configured to use Lotus Domino Go Webserver, several problems can occur if you access configuration management from a client with more than one IP address. In this case, you must change the default Web server DNS Lookup setting to "on" using one of the following methods:
The steps in the installation documentation for distributing and installing On-Demand Server software are incomplete. For complete instructions, see the help for setting up an AIX or Windows NT file package in the On-Demand ServerPlus for Tivoli module.
If you are using a version of the Tivoli TME 10 Framework prior to 3.2, you will not be able to start configuration management using Navigator from the Configuration Management - Applet Launcher task of the On-Demand ServerPlus module. To solve this problem, you need a later version of the wrunui.exe file. To obtain this file, contact your Tivoli service representative. Temporarily, your options are:
If you cannot load or run the Applet Launcher or configuration management,
try to load the diagnostic applet and run it to perform many of the
checks in this section. The diagnostic applet is available from your
On-Demand Server at
If the diagnostic applet is not available, review the following settings:
The Applet Launcher start page is organized into program groups represented by an icon and a group name. A program group can be used to launch an applet or it can be used to group other applets as tasks. Grouping applets saves desktop space. Each program group displays no more than three tasks at a time. If more than three tasks are in a group, users can scroll through the tasks using the up and down arrows (see the example of the Preferences group in Figure 1).
Figure 1. Preferences program group
![]() |
You can create your own program groups and arrange applets and web sites under the groups on the start page. Any software that you do not explicitly organize into a group is displayed in its own group on the Applet Launcher. Before you begin, all software that you want to group should already be defined in profile management. |
Example: To create a group named Sample on the start page with two applets and a URL link to www.yahoo.com :
NCOD|AL|GROUP[Sample]|ID=Sample NCOD|AL|GROUP[Sample]|ICON_URL=http://servername/IBMWebAS/onDemand/icons/sampleIcon.gif NCOD|AL|GROUP[Sample]|APPLET[com.ibm.eNetwork.onDemand.samples.SAMPLEAPP1]=com.ibm.eNetwork.onDemand.samples.SAMPLEAPP1 NCOD|AL|GROUP[Sample]|APPLET[isv.sampleApp2]=isv.sampleApp2 NCOD|AL|GROUP[Sample]|APPLET[HTMLONLYhttpwwwyahoocom]=HTMLONLYhttpwwwyahoocomNCOD.AL.txt contains other statements for the applets shipped with On-Demand Server. Do not change these statements or insert statements for your program groups into the existing statements. Instead, append your statements to the end of NCOD.AL.txt .
Users cannot start more than one Applet Launcher session at a time on the same computer. This is true even when the user tries to load two copies of the Applet Launcher from separate servers into two browser windows.
You should not try to open more than one configuration management session at a time on a client. You can, however, have multiple configuration management sessions at a time on multiple clients. If a conflict in configuration changes exists, the last saved change takes effect.
The Applet Launcher taskbar window is not intended to be resized. The taskbar can be maximized in Internet Explorer, but this consumes the entire Windows desktop area and is not useful.
There is a bug in the JFC (Swing) component of Java that hides the tabs in an applet's panel or window. To display the tabs, click in the tab area where the tab is supposed to appear or press F5.
There is a problem in the Navigator browser that might cause applets to not finish loading when they are first accessed from certain Web servers. To fix this problem, users can right click in the browser (near the edge of the browser window) and select Reload. This forces the applet's HTML to reload from the local cache. This problem does not reoccur as long as the applet remains in the local cache. If this problem occurs when loading the Applet Launcher, you should reload from the edge of the taskbar window.
You must install the Java 1.1.6 upgrade on clients running Netscape Communicator 4.04 for OS/2. The Java 1.1.6 upgrade is available on the eNetwork On-Demand Server CD. After Java 1.1.6 is installed, install the Java 1.1.6 upgrade as follows:
If an OS/2 client user with 32 MBs of memory experiences performance problems with the Applet Launcher in Navigator, follow these you can do the following to improve performance:
To enable your WorkSpace On-Demand clients to run Netscape Communicator
4.04 on the WorkSpace On-Demand Server, copy the files security.jar and
swingall.jar from the eNetwork On-Demand Server subdirectory:
to the client Netscape directories:
(where x represents the WorkSpace On-Demand version and
yy represents the specific geography).
When running certain applets in Internet Explorer on Windows 95 (with Active Desktop) or Windows 98, certain system resources can become exhausted over a period of time. Eventually, Internet Explorer and the desktop are terminated with an Illegal Operation error and restarted. This should not affect active native applications that do not use the Internet Explorer process (iexplorer.exe). However, any applets that you are using, including configuration management, are terminated and you will lose any unsaved data. To fix this problem, do one of the following:
A problem exists when using Internet Explorer's automatic configuration feature (autoproxy) on the same machine on which On-Demand Server is installed (Windows NT). Using the shortcuts in the Start menu will not work and may cause Internet Explorer to crash or hang. This is a bug in Internet Explorer. The problem also appears if Internet Explorer's home page is set to be blank. There are several simple workarounds available, any one of which will eliminate the problem:
There are several problems on DBCS computers (Japanese, Korean, Simplified Chinese and Traditional Chinese) that use the JVM that is shipped with Internet Explorer 4.01 (Service Pack 1). These problems can be fixed by upgrading the JVM to the 5.0.0.2829 level (VM Build 2829, released 7/22/98) from http://www.microsoft.com/java/vm/dl_vm30.htm. There are also versions of the JVM later than 5.0.0.2829 that do not work well with DBCS computers.
If an Internet Explorer user has checked the "Browse in a new process" option, the following occurs with the Applet Launcher:
To view or change this setting:
If you are using a Japanese Windows 95 client and you change the regional settings to English (United States), applets downloaded into Internet Explorer are still displayed in Japanese. This problem does not occur with other language settings, Navigator, or Windows NT.
When Internet Explorer downloads a CAB file from the same namespace as On-Demand Server and the CAB is signed with a different certificate, the user is prompted to overwrite the namespace. This is normal behavior. The user should click Yes to proceed with downloading the applet.
As an administrator, you can launch configuration applets from profile management. The applet loads and runs under the context of the user or group ID that you have selected in the profile management tree in the left pane. This allows you to customize applets for a user or group of users. Settings that you save under the context of a user or group apply only to that user or group. To test this function:
When running applets from profile management:
PMimport and PMbackup are Java command line applications that must be invoked using either the JRE or, if the JDK is installed, the JAVA command. You do not need to set the CLASSPATH before you execute PMimport and PMbackup. Instead, you need to set the CLASSPATH when you invoke the command. The CLASSPATH must be set as follows:
To view changes that you have saved in profile management, click the File menu and select the Refresh option to refresh the view of the configuration.
When adding or changing passwords, only alphabetic (A - Z or a - z) and numeric (0 - 9) characters are allowed. Passwords are case sensitive.
In profile management, the Import button opens the Import Software List window so that you can add software using an import file. The Browse button in this window detects only locations local to On-Demand Server.
If a file system on which the logs are stored gets full, logging from clients will not be saved until room is made available on the file system. The log/trace facility continues logging to the console while the disk is full, but log and trace records are not written to the disk. When space becomes available again, new log and trace records will again be saved, but logging done while the file system was full is lost. In effect, this creates a gap in the log records.
This problem may or may not appear in Internet Explorer depending on the way the host name is listed in profile management for an applet. If the applet is defined to profile management using only the host name (without the domain name), when you open the applet from Applet Launcher, you will be required to log in again. If you attempt to trace the applet, the applet's functions will not be listed by the log/trace facility. This problem does not affect Navigator. To fix the problem, redefine the applet in profile management using the fully-qualified name for the URL parameter. If the applet was defined using an import file, remove the applet from profile management, edit the import file to include the domain name for the URL parameter, and re-import the applet.
The On-Demand Server Toolkit classes do not work in the Java Virtual Machine (JVM) of the Java Plugin. If you write an applet that uses any of the services of On-Demand Server, the applet should not be developed to use the Java Plugin. Instead, your applet should be developed to run in the native browser's JVM using the <APPLET> tag. Setting up software for users explains how to create your applet's HTML file to work with On-Demand Server.
To preserve the default settings with which your applet is shipped to customers,
save them in the following location:
/onDemand/Server/DataStore/defaults/
This location provides a means to migrate the original settings in the case that
a customer migrates their On-Demand Server to a future release.
Applet Launcher performs complex interactions between Java code and Javascript code. This tip describes diagnostic steps to help you correct these errors. While this tip is based on errors that appear in Internet Explorer, the principles outlined apply to any Javascript error, regardless of browser.
When a Javascript problem occurs, this is the dialog box that you will see from Internet Explorer:
Javascript errors associated with web pages
Consistent Javascript errors that are associated with clicking on Web page links displayed in an Applet Launcher window may be due to a clash between Applet Launcher's Javascript and the Javascript code on the link target's Web page. For example, Javascript code at http://www.village.com.au/cybapark/sea/cyba3.htm tried to read Javascript properties on HTML frames owned by Applet Launcher, which is a Javascript security violation.
When Applet Launcher launches an applet, the Applet Launcher Java code
communicates with the Javascript that builds the <APPLET> tag by appending
CGI parameters onto the applet's URL obtained from profile management. As a result,
the URL returned by getDocumentBase() for this applet is cryptic, for example:
To parse this URL string, take into account that it follows the form:
URL | is the applet's URL exactly as entered into profile management, for example: http://server/IBMWebAS/onDemand/applet.html |
? | introduces the CGI parms. Exactly one "?" occurs; it occurs after the .html file name and extension. |
ALPARMS | is a bundle of parameters that will be incorporated as <PARAM> tags nested in the <APPLET> tag. In the example above, the string is alparms=TASK_ID%3dDEFAULT%7c. ALPARMS is optional; it occurs if the administrator entered parameters for this applet into profile management or if the user launches a custom task for this applet (Files On-Demand shortcuts are the best example). Each parameter is a "name=value" pair where the value is URLencode()'ed to allow for arbitrary characters in the value. A logical or ("|") separator appears at the end of each "name=value" pair. |
& | is the standard CGI parms separator character |
ALCODEBASE | is the exact, case-sensitive Applet Launcher codebase which is
necessary for sharing namespaces in Internet Explorer.
ALCODEBASE always is appended to the CGI parms
and returned as
|
The Application Client ID (ACID) is a String with a unique value that identifies the client for "per-seat licensing". The sample code in the toolkit for creating a license client uses the applet name as the ACID value, which does not result in a unique value for each license client. To achieve a unique ACID value, a better option would be to set this value to a combination of the host name where the applet is running and the user ID.