-------------------------------------------------------------------------- Tarantella Enterprise 3 (version 3.2) -------------------------------------------------------------------------- Read this to find out how to install Tarantella on your system. -------------------------------------------------------------------------- Contents -------------------------------------------------------------------------- - What's on the CD - Before you install - Upgrading and re-installing Tarantella - Upgrading customized webtop themes - Recommended/required operating system modifications Caldera OpenLinux eServer 2.3+ HP-UX 11.00+ IBM AIX 4.3.3+ Linux kernel 2.2+ (all distributions) SPARC Solaris(TM) 2.6+ SuSE Linux 6.3+ TurboLinux 6.0+ UnixWare 7.1.1, Open UNIX 8+ - Additional kernel tuning for the Tarantella Mainframe Connectivity Pack - Installing Tarantella - Configuring a web server for use with Tarantella - Where to look for more information -------------------------------------------------------------------------- What's on the CD -------------------------------------------------------------------------- This CD contains: - For each supported system, one shx archive containing the Tarantella Base Component. - A number of subdirectories containing shx archives for additional Tarantella packs: acp Tarantella AS/400 Connectivity Pack font Additional font packages mcp Tarantella Mainframe Connectivity Pack tsp Tarantella Security Pack - A /modules subdirectory containing Tarantella Enhancement Modules. - A /native subdirectory containing a Native Client archive for each supported system. About shx archives -------------------------------------------------------------------------- Files with the extension "shx" are self-installing archives (SHell eXecutables). Each shx archive contains one or more packages, which are the main self-contained parts of Tarantella. These are UNIX SVR4 packages: the shx file acts as a wrapper around the UNIX pkgadd command. For those versions of UNIX that don't support the SVR4 package mechanism, we've included that too: installed automatically as part of the shx archive. You use the same archives whether you're installing Tarantella for the first time, or upgrading from an earlier version. -------------------------------------------------------------------------- Before you install -------------------------------------------------------------------------- The Tarantella CD insert contains a pre-installation checklist to follow before installing Tarantella. We recommend that you follow this checklist carefully before trying to install Tarantella. This README file contains a list of recommended/required operating system modifications. You must make these modifications BEFORE you install Tarantella. IMPORTANT: If you are upgrading from a previous release of Tarantella Enterprise 3, you don't need to uninstall Tarantella first. Your existing configuration will be preserved when you run Tarantella Setup. -------------------------------------------------------------------------- Upgrading and re-installing Tarantella -------------------------------------------------------------------------- This section describes what happens to your existing configuration when you upgrade or re-install Tarantella. It covers: - The changes Tarantella makes during installation - Preserving customized files, for example webtops - Manually upgrading customized files - Upgrading arrays The changes Tarantella makes during installation -------------------------------------------------------------------------- During the installation, Tarantella makes the following changes which may affect your configuration: - A complete copy of your ENS database (this is the storage area for all the objects in your Tarantella organizational hierarchy) is taken from the var/ens directory and backed up to the var/ens.<> directory. The backup is not changed and the existing ENS database is only changed if new objects essential to the running of Tarantella are needed. - The local/global array configuration (as controlled by Array Manager) stored in the var/serverconfig directory is only changed if there is a need to insert any new properties files and add new attributes to existing properties. This directory is *not* backed up. - All the server resources files in the var/serverresources directory *apart from* var/serverresources/expect are replaced. These files are not normally edited as they control the internal behavior of aspects of the system. The var/serverresources/expect directory is backed up and changes retained. - All add-on packs are uninstalled during the upgrade and you will need to reinstall them. Preserving customized files, for example webtops -------------------------------------------------------------------------- Tarantella aims to be compatible with previous versions so that customized installations should continue to work after an upgrade or re-installation. For various reasons, this is not always possible and the instructions below explain how to avoid potential problems. During the installation, Tarantella backs up the following directories (and the subdirectories within them): - var/docroot (backed up to var/docroot.<>) - var/serverresources/expect (backed up to var/serverresources/expect.<>) - etc/data (backed up to etc/data.<>) - etc/templates (backed up to etc/templates.<>) This creates a backup copy of all customizable files, including login scripts. NOTE: For upgrades from version 3.0 and version 3.01, the etc/templates.<> directory will only contain customized files as the uncustomized versions were not backed up during these installations. Tarantella checks the files in these directories to see if they have been changed or new files added. If a file has not been changed, it is overwritten with the file from the new installation. If a file has been changed or a new file added, it is not overwritten with the new file and remains in its current directory. During the upgrade/re-installation, the following message may display: -- START OF MESSAGE -- Your installation has been upgraded. Please read $<>/var/log/upgraded.files for details of modified files that have been preserved. Setup upgraded a customized installation. This file contains details of how the customizations were preserved. - Number of files that were previously changed or added by hand in the original Tarantella installation: <> See $<>/var/log/customized.list. These customizations are preserved and still active within $<>/var. - Number of these files that would also change for the upgrade to Tarantella <>: <> See $<>/var/log/customizedchanged.list. We recommend that you compare these files against the uncustomized template files used before and after the upgrade. Old templates: $<>/etc/templates.<> New templates: $<>/etc/templates -- END OF MESSAGE -- This message says two log files have been produced: - var/logs/customized.list This is a list of any files that the administrator has edited or added. - var/logs/customizedchanged.list This is a list of any files that the administrator has edited which would also have been changed by the upgrade. This message also indicates that there are customized files that may need to be manually upgraded. Manually upgrading customized files -------------------------------------------------------------------------- The most important of the log files produced is customizedchanged.list as this lists the files that may have to be manually upgraded. For each file listed in this log file, there will be three versions of the file held on your system: - the old, customized version, still in use in the var directory, - the old, uncustomized version, in the etc/templates.<> directory, and - the new, uncustomized version, in the etc/templates directory. To find out whether you need to make any changes to your customized files, use a utility such as diff to compare the file in the etc/templates.<> directory with the file in the etc/templates directory. This will highlight the changes that have been made between Tarantella versions. These changes will need to be applied to the customized file (for example by using a utility such as patch). Upgrading arrays -------------------------------------------------------------------------- Each Tarantella server in array must be upgraded/re-installed independently. We recommend that you upgrade/re-install an array by gradually emptying the array and building a new one. Follow this process: 1 Detach a secondary server from array 1. This will be the new primary in array 2. 2 Upgrade/re-install this new primary server. 3 For each of the remaining secondary servers in array 1: - Detach it from array 1. - Upgrade it. - Join it to array 2. 4 Upgrade the last (primary) member of array 1. 5 Join the last (primary) member of array 1 to array 2 as a secondary server. 6 Re-master array 2 so that the original primary server in array 1 becomes the primary server in array 2. NOTE: In a mixed version array, the primary server must be newer than the secondary servers. In particular, if the primary server is version 3.2, the secondary servers must be *at least* version 3.10. When you make array changes (using Tarantella array detach, join or make_primary) the following directories are copied across the array: - var/docroot/resources - var/ens - var/password - var/preferences - var/serverconfig/global - var/serverresources It is advisable to wait until Tarantella has copied the changes to all array members before running any further Tarantella array commands. This is complete when the Tarantella status command returns the same result for each array member. Changes made to any other files in the var directory are not copied across the array. Administrators have to manually copy these changes to every array member. -------------------------------------------------------------------------- Upgrading customized webtop themes [601228] -------------------------------------------------------------------------- After upgrading to Tarantella Enterprise 3 version 3.2, Netscape 6.x users with customized webtop themes may not be able to use client drive mapping. This is a known issue. In Tarantella Enterprise 3 version 3.2, all four default webtop themes have been adjusted so that the print and client drive mapping applets no longer share the same frame. This fixes the problems with client drive mapping when using Netscape 6.x. If you have customized your webtop themes and Netscape 6.x users experience problems with client drive mapping, you will need to make the same change. -------------------------------------------------------------------------- Recommended/required operating system modifications -------------------------------------------------------------------------- We recommend modifications for the following operating systems: - Caldera OpenLinux eServer 2.3+ - HP-UX 11.00+ - IBM AIX 4.3.3+ - Linux kernel 2.2+ (all distributions) - SPARC Solaris(TM) 2.6+ - SuSE Linux 6.3+ - TurboLinux 6.0+ - UnixWare 7.1.1, Open UNIX 8+ You must make all the modifications BEFORE you install Tarantella. -------------------------------------------------------------------------- Caldera OpenLinux eServer 2.3+ [601770] -------------------------------------------------------------------------- Due to a known problem in Sun's JDK(TM) version 1.3.1 for Linux, updated glibc libraries are required for this platform. Refer to the Java(TM) SDK v1.3.1 Installation Notes (http://java.sun.com/j2se/1.3/install-linux-sdk.html#problems) for information on which version of glibc to use. -------------------------------------------------------------------------- HP-UX 11.00+ [600825] -------------------------------------------------------------------------- Tarantella Enterprise 3 version 3.2 and later uses version JRE 1.3.1_02 of the Java(TM) Runtime Environment (JRE). You should install the appropriate patches for your HP-UX version. See the HP-UX patch information page for details (http://www.hp.com/products1/unix/java/infolibrary/patches.html). Kernel tuning -------------------------------------------------------------------------- If you are seeing "OutOfMemoryException" in the JServer log files (around thread start() or run() methods) you may need to increase the thread tunables. On HP-UX 11.00 the default thread mechanism is kernel threads. Set the kernel tunables (max_thread_proc, nkthread, for example) so that the application can be run with the kernel-threaded virtual machine for the Java(tm) platform ('Java Virtual Machine' and 'JVM'). The tunables of interest are: max_thread_proc The maximum number of threads in a single process. This needs to be large enough to accommodate all of the threads in the Java application plus the handful of additional threads in the virtual machine itself. nkthreads The maximum total number of kernel threads on the system. This needs to be large enough to accommodate all of the applications that will be run simultaneously on the system plus all of the kernel threads needed by the kernel. Typically this parameter is a function of nproc and an expected average number of threads per process. For more information, see the hp frequently asked questions page (http://www.hp.com/products1/unix/java/java1/jdk_jre/faq.html). -------------------------------------------------------------------------- IBM AIX 4.3.3+ [600825] -------------------------------------------------------------------------- Tarantella Enterprise 3 version 3.2 and later uses version 1.3.1 of the Java(TM) Runtime Environment (JRE). This means maintenance packages are required for the AIX 4.3.3 and 5.1 environments. Additional filesets are also required if you are using Chinese, Korean and Japanese (CKJ) locales. These files are available from the IBM Support site (http://techsupport.services.ibm.com/server/fixes). For AIX 4.3.3 the JRE requires the AIX 4330-09 Recommended Maintenance Level. For AIX 5.1 the JRE requires the AIX 5100-01 Recommended Maintenance Level. NOTE: Before updating your AIX 5.1.0 system to the AIX 5100-01 maintenance level, you must first apply and commit APAR IY19375. CKJ locales -------------------------------------------------------------------------- If you are using one of the supported non-UTF8 CKJ locales, one of the following filesets (available on both AIX 4.3.3 and AIX 5.1 base CDs) is required: X11.fnt.ucs.ttf (for ja_JP or Ja_JP) X11.fnt.ucs.ttf_CN (for zh_CN or Zh_CN) X11.fnt.ucs.ttf_KR (for ko_KR) X11.fnt.ucs.ttf_TW (for zh_TW or Zh_TW) For Japanese users, if you are using Japanese Input Method, you may apply the following PTFs to avoid some Input Method related problems: jkit.Wnn6.base 2.2.0.2 (PTF U479697 or APAR IY22917) (Wnn6 user only) X11.motif.lib 5.1.0.15 (PTF U479604 or APAR IY22933) (AIX 5.1 user only) -------------------------------------------------------------------------- Linux kernel 2.2+ (all distributions) [513867] -------------------------------------------------------------------------- On Linux systems, each thread is mapped to a separate process (unlike on UNIX systems). As Tarantella is a multi-threaded server, you'll see a large number of processes in process listings and you may need to increase the number of processes supported by the kernel. The Red Hat Linux 6.2 kernel and kernels compiled with the kernel-source-2.2.14-5.0 RPM support 2560 processes by default. This process limit should support approximately 1000 users per server, if each user runs one application. To increase the number of processes your kernel supports, see your Linux vendor's web site for details. File descriptors and inodes -------------------------------------------------------------------------- You should increase the maximum number of file descriptors and inodes. The inode limit should be three times the file descriptor limit. On some Linux systems (for example Red Hat Linux 6.2) you would append the following lines to /etc/rc.d/rc.local: echo "16384" > /proc/sys/fs/file-max echo "49152" > /proc/sys/fs/inode-max On Caldera OpenLinux eServer 2.3+, edit the /etc/system.cnf file and change the CONF_INIT_MAX_FILES and CONF_INIT_MAX_INODES parameters to 16384 and 49152 respectively. Using Linux as an application server -------------------------------------------------------------------------- If you use Linux as an application server, each emulator session requires one pseudo-tty. For example, 50 users running 10 applications each on one application server requires 500 pseudo-ttys. See http://linuxperf.nl.linux.org/general/common.html for tips on performance tuning. -------------------------------------------------------------------------- SPARC Solaris(TM) 2.6+ [513869] -------------------------------------------------------------------------- You should install the appropriate patches for your Solaris(TM) version (see http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access). NOTE: The patches recommended by Sun for Solaris may not apply to Siemens Solaris-based systems. For information about which patches to install on these systems, refer to your Siemens contact or the Siemens web site. Supporting a large number of users per Tarantella server -------------------------------------------------------------------------- Solaris 7+ only: To support a large number of users on a Tarantella server, increase the hard limit on the number of file descriptors. We recommend you do this to support more than 100 users. Add this line to your /etc/system file (make a backup first): set rlim_fd_max=4096 You need to reboot for the change to take effect. See "man -s 4 system", and http://sunsolve.sun.com/pub-cgi/retrieve.pl?type=0&doc=infodoc/21622 for advice on tunables. This document recommends that you don't increase the hard limit beyond 1024 (the default) on Solaris 2.6 systems. Using Solaris as an application server -------------------------------------------------------------------------- Each emulator session requires one pseudo-tty. For example, 50 users running 10 applications each on one application server requires 500 pseudo-ttys. To set the number of pseudo-ttys, edit your /etc/system file (make a backup first) and add the following line: set pt_cnt= where is the number of pseudo-ttys you require. To create the new devices, reboot with the "-r" option. See http://sunsolve.sun.com/pub-cgi/retrieve.pl?type=0&doc=infodoc/21622 for advice on increasing pseudo-ttys. -------------------------------------------------------------------------- SuSE Linux 6.3+ [600800] -------------------------------------------------------------------------- To increase the number of files that may be open simultaneously, you can make changes to the file descriptors and inodes, and also to the kernel. File descriptors and inodes -------------------------------------------------------------------------- Increase the value of /proc/sys/fs/file-max and /proc/sys/fs/inode-max to something like 256 for every 4MB of RAM you have. For example, for a 64 MB machine, set it to 4096. See http://linuxperf.nl.linux.org/general/kerneltuning.html#filehandles [Linux Performance Tuning] Kernel changes -------------------------------------------------------------------------- Make the following changes to the kernel and re-compile: (see http://www.linuxraid.org/filehandles.patch) Changes to include/linux/fs.h: - increase NR_FILE from 4096 to 65536 - increase NR_RESERVED_FILES from 10 to 128 Changes to fs/inode.c: - increase MAX_INODE from 16384 to 262144 Note: MAX_INODE must be at least three times larger than NR_FILE. -------------------------------------------------------------------------- TurboLinux 6.0+ [511416] -------------------------------------------------------------------------- Tarantella requires that your system is configured to use shadow passwords, storing username and password information in /etc/shadow. Setup warns if your system doesn't use shadow passwords. IMPORTANT: On systems that don't use shadow passwords, users are unable to log in to Tarantella. To convert your system to use shadow passwords, use pwconv. See the pwconv(8) man page and the Linux Shadow Password HOWTO at http://www.linuxdoc.org/HOWTO/Shadow-Password-HOWTO.html, which gives a good overview of the issues you may encounter. -------------------------------------------------------------------------- UnixWare 7.1.1, Open UNIX 8+ [513607], [601770] -------------------------------------------------------------------------- Patches for UnixWare 7.1.1 -------------------------------------------------------------------------- You should install the following patches (available from your support provider or from Caldera Support Services, http://www.caldera.com/support/download.html): set71101j UnixWare 7.1.1 Maintenance Set ftp://ftp.caldera.com/pub/unixware7/ms71101/set71101j.Z ptf7410i libthread Supplement ftp://ftp.caldera.com/pub/unixware7/ptf7410i.Z ptf7715a Networking and MEM supplement (supersedes ptf7666f TCP/IP supplement) ftp://ftp.caldera.com/pub/unixware7/ptf7715a.Z Note: this patch requires ptf7701b ftp://ftp.caldera.com/pub/unixware7/ptf7701b.Z ptf7137a UnixWare 7.1.1 CDE Desktop Supplement (only required if you plan to run CDE Desktop on your Tarantella server) ftp://ftp.caldera.com/pub/unixware7/ptf7137a.Z Newer patches may become available over time, see http://www.caldera.com/support/ftplists/uw7list.html. UnixWare 7.1.1 also needs new/updated UDK FS runtime library packages (libc.so.1, libC.so.1 and libm.so.1) in order to use Java(TM) 2 version 1.3.0. Download the packages from http://www.caldera.com/download. On this site select 'UnixWare and OpenServer Development Kit Feature Supplement 7.1.1b' and then select the 'udkrtfs' package. [601858]. Patches for Open UNIX 8+ -------------------------------------------------------------------------- You should be up to date with your Open UNIX 8 Maintenance Packs, see http://www.caldera.com/support/ftplists/ou8list.html. Kernel tuning for UnixWare 7.1.1 and Open UNIX 8+ -------------------------------------------------------------------------- We recommend you use scoadmin to tune the kernel for optimal performance of Tarantella servers. Raise the following parameters to the specified values if they are currently less than the values shown: Device Drivers NUMREGPT 3072 NUMSCOPT 1024 Virtual Memory DRV_SEGKMEM_BYTES 0x147A000 File System RSTCHOWN 0 Security CONSOLE_SECURITY 0 Process Limits MAXUP 5000 MAXULWP 65000 NPROC 12500 SFNOLIM 2048 HFNOLIM 2048 Virtual Memory SEGKMEM_BYTES 0x2000000 Miscellaneous ARG_MAX 1048576 MAXLINK 32767 File System NBUF 128 NHBUF 32 IPC SEMMNI 10000 Tuning TCP/IP parameters for UnixWare 7.1.1 and Open UNIX 8+ -------------------------------------------------------------------------- You should also tune TCP/IP parameters. Run the following command as root: inconfig tcp_2msl 30 Set the following parameters in the relevant files in the /etc/conf/sdevice.d directory: tcp 4000 ticlts 1000 ticotsor 1000 ticots 8192 -------------------------------------------------------------------------- Additional kernel tuning for the Tarantella Mainframe Connectivity Pack -------------------------------------------------------------------------- The Mainframe Connectivity Pack uses the third-party TN3270E product, which may require additional kernel tuning on your system. The information provided lists the resources that TN3270E requires. To determine the actual values required for your system, you need to know the resource requirements of other applications running on the system. Kernel parameters required for supported operating systems -------------------------------------------------------------------------- Some operating systems only require some of the parameters to be tuned: HP-UX 11.00+ SHMMNI, SEMMNI, SEMMNS, SEMMNU IBM AIX 4.3.3+ No tuning required SPARC Solaris(TM) 2.6+ SHMMNI, SEMMNI, SEMMNS, SEMMAP, SEMMNU UnixWare 7.1.1, Open UNIX 8+ SHMMNI, SEMMNI Definitions -------------------------------------------------------------------------- "TN3270E invocations" is the maximum number of TN3270E programs which will be running concurrently on the system. "HLLAPI sessions" is the total number of TN3270E sessions, for all of the TN3270E programs running with an HLLAPI session ID assigned. HLLAPI session IDs are assigned through the style file or with the -h option. Command line options -------------------------------------------------------------------------- -h allows a hexadecimal HLLAPI session ID to be specified for a TN3270E session. -b starts the TN3270E program as a background process. -e disables the menu interface. Formulas for TN3270E with neither the -b or -e command line options: SHMMNI = 1 + (TN3270E invocations) + (HLLAPI sessions) SEMMNI = (2 x TN3270E invocations) + (HLLAPI sessions) SEMMNS = (2 x TN3270E invocations) + (2 x HLLAPI sessions) SEMMAP = half the value of SEMMNS SEMMNU = (2 x TN3270E invocations) + (HLLAPI sessions) Formulas for TN3270E with the -b or -e command line option specified: SHMMNI = same as above SEMMNI = HLLAPI sessions SEMMNS = 2 x HLLAPI sessions SEMMAP = half the value of SEMMNS SEMMNU = HLLAPI sessions Additional kernel tuning for HLLAPI applications -------------------------------------------------------------------------- SHMSEG must be set on all operating systems except AIX when a single HLLAPI application must access multiple TN3270E sessions. SHMSEG = 1 + the maximum number of HLLAPI sessions to be accessed by a single HLLAPI application process. Shared memory sizes -------------------------------------------------------------------------- In most cases the shared memory sizes configured by default will be sufficient. For the few cases where this is not true, formulas are provided to calculate the approximate shared memory size required by TN3270E: - Without the -b option = (90K * TN3270E invocations) + (14K * HLLAPI sessions) - With the -b option = (19K * TN3270E invocations) + (14K * HLLAPI sessions) Process and socket requirements -------------------------------------------------------------------------- TN3270E uses two processes per invocation when run without either the -b or the -e options. Only one process is used with either the -b or -e option specified. This is true for both the Motif and character TN3270E versions. TN3270E uses one TCP socket per host session. -------------------------------------------------------------------------- Installing Tarantella -------------------------------------------------------------------------- 1 Log in as root on the host on which you want to install Tarantella. 2 Change to the directory where the Tarantella CD is mounted. 3 To install the Tarantella Base Component, type one of the following: sh ttapahp.shx HP-UX 11.00+ sh ttarsai.shx IBM AIX 4.3.3+ sh ttai3li.shx Linux (Caldera OpenLinux eServer 2.3+, Red Hat Linux 6.2+, SuSE Linux 6.3+, TurboLinux 6.0+) sh ttaspso.shx SPARC Solaris 2.6+ sh ttai3un.shx UnixWare 7.1.1, Open UNIX 8+ 4 Follow the instructions on your screen. 5 To install the Tarantella Mainframe Connectivity Pack software, type one of the following: sh mcp/mcppahp.shx HP-UX 11.00+ sh mcp/mcprsai.shx IBM AIX 4.3.3+ sh mcp/mcpspso.shx SPARC Solaris 2.6+ sh mcp/mcpi3un.shx UnixWare 7.1.1, Open UNIX 8+ Note that this pack is not available for all systems. 6 To install the Tarantella AS/400 Connectivity Pack software, type one of the following: sh acp/acppahp.shx HP-UX 11.00+ sh acp/acprsai.shx IBM AIX 4.3.3+ sh acp/acpi3li.shx Linux (Caldera OpenLinux eServer 2.3+, Red Hat Linux 6.2+, SuSE Linux 6.3+, TurboLinux 6.0+) sh acp/acpspso.shx SPARC Solaris 2.6+ sh acp/acpi3un.shx UnixWare 7.1.1, Open UNIX 8+ 7 To install the Tarantella Security Pack software, type one of the following: sh tsp/tsppahp.shx HP-UX 11.00+ sh tsp/tsprsai.shx IBM AIX 4.3.3+ sh tsp/tspi3li.shx Linux (Caldera OpenLinux eServer 2.3+, Red Hat Linux 6.2+, SuSE Linux 6.3+, TurboLinux 6.0+) sh tsp/tspspso.shx SPARC Solaris 2.6+ sh tsp/tspi3un.shx UnixWare 7.1.1, Open UNIX 8+ IMPORTANT: Installing the Tarantella Security Pack does *not* enable SSL. For each host on which the Tarantella Security Pack is installed, a valid X.509 certificate is required before SSL connections are available. 8 To install any of the optional font packages, type the following: sh font/ttafandr.shx Andrew X fonts sh font/ttafhang.shx Hangul X fonts sh font/ttaficl.shx ICL X fonts sh font/ttaforie.shx Oriental X fonts sh font/ttafscot.shx SCO Term X fonts Installation notes -------------------------------------------------------------------------- - In previous versions of Tarantella, you could enter license keys during installation. This no longer happens. After you have installed Tarantella, you must add any license keys by using Array Manager or the the tarantella license add command. [602000] - If you're creating a Tarantella array, we recommend that you install and check each server separately before creating the array. You should install the same set of optional packages on every server in the array. - If you're upgrading from an earlier version of Tarantella, you should restart the web server to ensure it sends the latest files to web browsers. All users of Tarantella should restart their web browsers before connecting to the upgraded server. - In some circumstances the Tarantella installation script on Linux hangs. If this happens, run ps -ef to see if the command lpc reread is running. If it has been running for more than a minute or so, kill it. The installation should then complete successfully. [601586] - If you're installing Tarantella on a UnixWare system, remove unwanted files from /var/tmp before installing Tarantella. If you see an error message informing you that there isn't sufficient space in /var/tmp, type "umount /var/tmp" and try to install Tarantella again. - If you're installing Tarantella Enterprise 3 version 3.2 on UnixWare 7.1.1 the installation will fail because UnixWare 7.1.1 needs new/updated UDK FS runtime library packages (libc.so.1, libC.so.1 and libm.so.1) in order to use Java(TM) 2 version 1.3.0. Download the packages from http://www.caldera.com/download. On this site select 'UnixWare and OpenServer Development Kit Feature Supplement 7.1.1b' and then select the 'udkrtfs' package. [601858] -------------------------------------------------------------------------- Installing the Tarantella Native Client for Microsoft Windows -------------------------------------------------------------------------- 1 Copy the Native Client Setup program (tspwin32.exe) from the native directory on the CD to a temporary directory on your PC. 2 Browse to the temporary directory and double-click tspwin32.exe. -------------------------------------------------------------------------- Installing the Tarantella Native Client for UNIX/Linux -------------------------------------------------------------------------- 1 Copy one of the following Native Client tar files from the native directory on the CD to a temporary directory on your system: tncpahp.tar HP-UX 11.00+ tncrsai.tar IBM AIX 4.3.3+ tnci3li.tar Linux (Caldera OpenLinux eServer 2.3+, Red Hat Linux 6.2+, SuSE Linux 6.3+, TurboLinux 6.0+) tncspso.tar SPARC Solaris 2.6+ 2 At a command prompt, extract the tar file by typing tar xvf . 3 Install the Native Client by typing sh ttwebtop/install. -------------------------------------------------------------------------- Tarantella Enhancement Modules -------------------------------------------------------------------------- Tarantella Enhancement Modules provide support for some Tarantella features and are placed by Setup in the modules directory (var/docroot/modules) of the Tarantella server. To install a Tarantella Enhancement Module locally on an application server, download it from http:///tarantella/cgi-bin/modules.cgi. -------------------------------------------------------------------------- Configuring a web server for use with Tarantella -------------------------------------------------------------------------- Before you can use Tarantella, you must configure your web server in two ways: - Add a Document directory for the Tarantella document root. - Add a Program (CGI) directory for the cgi-bin subdirectory of the document root. How you do this depends on your web server. See your web server's documentation for full instructions, or read one of the following sections. IMPORTANT: If you're upgrading from Tarantella Enterprise II or earlier (version 1.x), you must reconfigure your web server. Apache web servers -------------------------------------------------------------------------- You must add two configuration directives to one of your web server configuration files (for example, httpd.conf): ScriptAlias /tarantella/cgi-bin /var/docroot/cgi-bin Alias /tarantella /var/docroot IMPORTANT: The lines must be in the order shown. Replace with the directory in which you installed Tarantella. Tarantella Setup displays what you must use as part of the "What you must do next" section. You should also ensure the web server follows symbolic links. The Directory directive for / should include "Options FollowSymLinks". These changes assume you are using the default configuration of Apache. See your web server documentation for more information. You must restart the web server for the configuration change to take effect. Netscape web servers -------------------------------------------------------------------------- 1 Start the Netscape Administration Server and connect to it using the Netscape server administrator's username and password. 2 Click the web server you want to use for Tarantella. 3 In the top frame, click Content Management. 4 In the left frame, click Additional Document Directories: - For URL Prefix, type "tarantella". - In Map To Directory, type "/var/docroot", replacing with the directory in which you installed Tarantella. (Tarantella Setup displays what you must use as part of the "What you must do next" section.) 5 Click OK, then click Save. 6 In the top frame, click Programs. 7 In the left frame, click CGI Directory: - For URL Prefix, type "tarantella/cgi-bin". - In Map To Directory, type the name of the cgi-bin subdirectory, "/var/docroot/cgi-bin", replacing with the directory in which you installed Tarantella. (Tarantella Setup displays what you must use as part of the "What you must do next" section.) 8 Click OK. 9, Click Save and Apply. Known web server problems -------------------------------------------------------------------------- Problem: Users can't download the Tarantella Native Client. [125591] Cause: By default, some Netscape web servers treat files with ".exe" extensions as CGI programs to run on the server, rather than files to download to the client. Solution: To allow users to download the Tarantella Native Client, you should ensure your web server is configured correctly. See http://knowledgebase.iplanet.com/ikb/kb/articles/35.html (Setting your server to allow downloading of .EXE files) on Netscape's web site for instructions. You need to edit your web server's mime.types file, to remove "exe" as an extension for the "magnus-internal/cgi" type, and add it as an extension for the "application/octet-stream" type. -------------------------------------------------------------------------- Where to look for more information -------------------------------------------------------------------------- After installing Tarantella, Setup points you to the "Before you begin" section of the online documentation. This includes all the essential information to help you get started with Tarantella. Your Tarantella webtop contains links to detailed Help for users and Tarantella Administrators. You can also check http://www.tarantella.com/knowhow for up-to-date information on this version of Tarantella. For extensive online services (including FAQ, knowledge library and documentation) or to find out details of purchasable Support services, see the Tarantella Support and Services web site at http://www.tarantella.com/support. -------------------------------------------------------------------------- Copyright (C) 1997-2002 Tarantella, Inc. All rights reserved. The names of companies referred to herein, their corporate logos, the names of their hardware and their software may be tradenames, trademarks or registered trademarks of their respective owners and manufacturers. $Id: README,v 1.79 2002/02/15 11:27:52 andrewh Exp $ --------------------------------------------------------------------------