Upgrading to WebTen 2.0 from WebTen 1.x

The WebTen 2.0 Installer is designed to be installed as a clean, or fresh installation. It is not packaged as an update to any previous release of WebTen. Upgrading an existing WebTen system to WebTen 2.0 requires some care to prevent corruption of the WebTen Libraries folder and to preserve your site specific customizations. After WebTen 2.0 is installed, the preserved customizations may be re-entered.

This document is intended to assist in installing WebTen 2.0 GM on a system that is already running a previous version of WebTen.

While your existing WebTen system is still running:

• Export and save your users database (use the Admin Server).
• Export and save any SSL key and certificate files. This step is only necessary if you have been running a secure server. For more information about exporting SSL key and certificate files, see the section "SSL Key and Certificate Files" below.
• Quit WebTen.
• Check the memory size allocated to the WebTen application. If you have modified this memory size or you have modified any resources within the WebTen application, make notes of these changes.

Before installing WebTen 2.0:

• Save your existing WebTen folder. This folder contains all of your Web content as well as some configuration files containing information about your site customizations.
• Move your existing WebTen Libraries folder out of the active extensions folder. The WebTen 2.0 installer will create a new WebTen Libraries folder. Creating this folder on top of an existing WebTen Libraries folder may cause corruption to these libraries. After the installer creates the new folder, the old folder can be used as a reference for re-organizing these libraries according to whether you are using Open Transport, are replacing Open Transport, or are using the dual stack mode.
• Leave the WebTen Preferences file in place. New preferences are not installed by the WebTen 2.0 Installer. Leaving this file in place will preserve your WebTen preference settings.
• Most of the WebTen customizations are stored in the file '/tenon/apache/conf/httpd.conf'. The format of this file changed in WebTen 2.0, so it is not possible to preserve this file from a previous WebTen system and install it in WebTen 2.0. However, you can use this file as a reference for the customizations that have been made at your site, easing the process of reconfigurating the same settings.

To aid in this process each WebTen release (including Beta releases) contains a copy of the httpd.conf file as it was delivered in that release. If you compare this file against your current httpd.conf file, the customizations or site specific changes to that file can be identified. Now, if you understand Apache's httpd.conf file format and directives, you can use these differences as a reference for re-entering your sites customizations.

The released httpd.conf file is saved in: '/tenon/apache/conf/Release/httpd.conf'. Use BBEdit to generate a list of differences between this file and your current httpd.conf file (above).

Install WebTen 2.0

• Reorganize the WebTen Libraries to match the organization of your previous WebTen Libraries folder. Specifically, note the locations of MacTCPdLib, OTSocketLib and SocketLib. These files may reside in the WebTen Libraries folder or within the Disabled folder inside the WebTen Libraries folder. Arrange these files to match the organization in your old WebTen Libraries folder.
• Move (or copy) your Plug-Ins and CGIs from their respective folders into the Plug-Ins and cgi-bin folders. If a plug-in is to serve more than one virtual host, see the section "Plug-In Installation under WebTen 2.0 " below.
• Move (or copy) the WebTen Settings file from the old WebTen folder into the WebTen 2.0 folder. This file holds the settings for the plug-ins. Thus any custom configurations made to a plug-in do not need to be re-entered.
• Set WebTen's memory size. This step is necessary only if this size was changed in your previous WebTen installation. Likewise, re-enter any resource changes made to your previous WebTen installation.

Launch WebTen 2.0

• Open or double-click on the WebTen icon.
• Set your serial number and administrator's password.
• Import the saved users database. Passwords with more than 8 characters are supported in WebTen 2.0 GM. If you are updating from any version prior to WebTen 2.0 GM to any version later than WebTen 2.0 GM (inclusive) you must re-enter passwords with more than 8 characters. Passwords with 8 or less characters do not need to be re-entered.
• Re-enter all of your virtual host names using the WebTen Admin Server.
• Import any saved SSL key and certificate files. For more information, see the section "SSL Key and Certificate Files" below. Once the key and certificate files are imported, enable SSL for any virtual hosts that require secure operation (use the Admin Server).
• Move (or copy) the Web content from each of the virtual hosts folders in the old WebTen folder into the corresponding folders in WebTen 2.0's 'WebSites' folder.
• Re-enter all access controls, realm protections, MIME types, Action Handlers and any other custom settings using the WebTen Admin Server.

Explore WebTen 2.0's new features

• Read the online documentation. All of WebTen 2.0's capabilities and each of its new features are discussed in detail.
• SSL (Secure Sockets Layer 3.0)
• FTP (Anonymous and password based file transfer)
• DNS (Domain Name Service)
• NFS (Network File Systems)

Plug-In Installation under WebTen 2.0

W*API plug-ins are sometimes distributed with Web content folders and instructions to place the content folder in the server's document root folder.

Under WebTen, multiple document root folders are possible depending on the number of virtual hosts configured. All Web document root folders, including the default virtual host root folder are contained in the WebSites folder.

If the plug-in's content is to serve one or more virtual hosts, follow these steps:

• Place the plug-in Web content folder in the WebTen "WebSites" folder.
• Create a Macintosh Alias of the plug-in Web content folder.
• Move the Alias to the document root folder of the virtual host to be served by the plug-in.
• Rename the Alias to match the actual name of the Web content folder.
• Place the plug-in itself in the "Plug-Ins" folder inside the WebTen folder.

SSL Key and Certificate Files

SSL key and certificate files are required for operation of a secure Web server. If your WebTen server is not serving any secure Web sites, you do not need to perform the steps in this section when upgrading your WebTen system.

SSL key and certificate files may be exported from a WebTen system using a special CGI named sslcerts.cgi. For security reasons, this CGI is not installed by default in a WebTen system. It must be installed and executed using the export option on the existing WebTen system prior to upgrading to the new version of WebTen. It then must be installed and executed using the import option on the new WebTen system after that system has been installed. Once the SSL key and certificate files have been imported into the upgraded system, sslcerts.cgi should be uninstalled from that system.

Exporting SSL Files

To export the SSL key and certificate files from an existing WebTen system:

• Copy sslcerts.cgi (from the Utilities folder on the WebTen 2.0 CD or from the support folder in the WebTen 2.0 distribution) into the cgi-bin folder. If your existing version of WebTen has a support folder, copy sslcerts.cgi into the cgi- bin within the support folder. Otherwise, copy sslcerts.cgi into the active cgi-bin.
• Execute sslcerts.cgi. If you put sslcerts.cgi in the /support/cgi-bin folder, use a URL like the following to execute this cgi. You must substitute your own host and domain names and replace the IP address 10.0.0.1 with your own IP address. When executing this cgi in this way you will be required to provide your WebTen administrator's password. Note that the protocol is https as the server is operating with SSL security on.

  <https://host.domain/webten_support/cgi-bin/sslcerts.cgi?10.0.0.1+export>

• If you put the sslcerts.cgi in the /cgi-bin folder, use a URL like the following to execute this cgi. You must substitute you own host and domain names and replace the IP address 10.0.0.1 with your own IP address. When executing this cgi in this way you will not be required to provide your WebTen administrator's password.

  <https://host.domain/cgi-bin/sslcerts.cgi?10.0.0.1+export>

• The exported SSL key and certificate files will be placed in a folder within the /tenon folder. This folder will be named after the IP address that you provided in the URL above. For example, if the IP address was 10.0.0.1, the folder will be named 10.0.0.1.ssl. Save this folder for subsequent importing into the newer version of WebTen.
• Remove the sslcerts.cgi from the cgi-bin folder.

Importing SSL Files

To import the SSL key and certificate files from a previous version of WebTen:

• Copy the folder containing the SSL key and certificate files exported from the previous version of WebTen to the /tenon folder on the new WebTen installation. Be sure to copy the entire folder, for example the 10.0.0.1.ssl folder, not just the contents of this folder.
• Copy sslcerts.cgi (from the Utilities folder on the WebTen 2.0 CD or from the support folder in the WebTen 2.0 distribution) into the cgi-bin folder within the support folder.
• Execute sslcerts.cgi using a URL like the following. You must substitute your own host and domain names and replace the IP address 10.0.0.1 with your own IP address. When executing this cgi in this way you will be required to provide your WebTen administrator's password.

  <http://host.domain/webten_support/cgi-bin/sslcerts.cgi?10.0.0.1+import>

• The imported SSL key and certificate files will be placed into their respective places within the WebTen distribution.
• Remove sslcerts.cgi from the /support/cgi-bin folder.
• Remove the folder containing the SSL key and certificate files (for example the 10.0.0.1.ssl folder) from the WebTen system. You may choose to save these files in a safe place (preferably not on the WebTen system) for subsequent upgrading or for backups of your SSL key and certificates.

Page last updated 12/27/1999