Document revision date: 28 June 1999

This manual contains installation prerequisites and instructions for, along with special information about, the FastTrack Web Server on OpenVMS Alpha systems.

Revision/Update Information: This manual supersedes the Netscape FastTrack Web Server Version 3.01 for OpenVMS Alpha OpenVMS Supplement.

Software Version: Netscape FastTrack Web Server Version 3.01A for OpenVMS Alpha

Compaq Computer Corporation
Houston, Texas

Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.

Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital Equipment Corporation or an authorized sublicensor.

© Digital Equipment Corporation 1999. All rights reserved.

Compaq, the Compaq logo, and the DIGITAL logo are registered in the U.S. Patent and Trademark Office.

Alpha, AlphaServer, AlphaStation, DEC, DIGITAL, OpenVMS, Tru64, VAX, VMS, are trademarks of Compaq Computer Corporation.

The following are third-party trademarks:

Windows is a registered trademark of Microsoft Corporation.

Netscape, Netscape FastTrack Server, and Netscape Navigator are registered trademarks, and Netscape Navigator Gold and Netscape Communicator are trademarks of Netscape Communications Corporation.

Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, used under license for technology invented by Netscape.

UNIX is a registered trademark of The Open Group.

MultiNet and TCPware are registered trademarks of Process Software Corporation.

IEEE is a registered trademark of The Institute of Electrical and Electronics Engineers.

Other product names mentioned herein may be the trademarks of their respective companies.

This document was prepared using VAX DOCUMENT, Version V3.2n.

ZK6560

The OpenVMS documentation set is available on CD-ROM.

Contents

Index

This chapter discusses the tasks you must perform before you begin the installation of the Administration Server and the FastTrack Web Server.

1.1 Locating the Documentation

For a list of new features in this release, see the release notes on the Netscape web site at:

http://home.netscape.com/eng/server/webserver/3.0/

For a list of known problems in this release, see the Release Notes.

For documentation about programming the server, see the DevEdge web site and select Server:

http://developer.netscape.com/library/documentation/index.html

1.2 Reporting Problems

For information about how to report a problem with Netscape FastTrack Version 3.01A for OpenVMS Alpha, click Contact Compaq on the initial FastTrack Administration Server screen, or go to the following URL:

http://www.openvms.digital.com:88/netscape/help/extra/ips_support.html

1.3 Downloading and Unpacking Kits

If you obtain FastTrack for OpenVMS Alpha from the OpenVMS Version 7.2 or later CD-ROM, follow the instructions included in the CD-ROM booklet.

If you obtain the FastTrack kit from the OpenVMS web site, download the backup save set into a temporary directory, and then unpack the file using the command:

$ BACKUP/REPLACE/LOG file-name/SAVE your-tempdir

where file-name is the name you gave to the file you downloaded.

For example:

$ BACKUP/REPLACE/LOG DKA0:[KITS]FASTTRACK.BCK/SAVE - _$ DKA0:[FT_KIT]

This chapter lists installation requirements and prerequisites, and describes how to install the Administration Server and the FastTrack Web Server for OpenVMS Alpha.

2.1 Installation Requirements and Prerequisites

Your system must be running OpenVMS Alpha Version 7.1 or later. OpenVMS VAX is not supported.

2.1.1 Support for MultiNet® and TCPware®

FastTrack Version 3.01A for OpenVMS Alpha supports DIGITAL TCP/IP Services for OpenVMS Version 4.2 or later. We recognize, however, that many customers use other IP stacks. Process Software is testing FastTrack Version 3.01A with MultiNet and TCPware. While we do not anticipate any problems, Process will make a patch kit available for TCPware and/or MultiNet if one is necessary, and notification of patch availability will be posted on the FastTrack download registration page at:

http://www.openvms.digital.com/openvms/products/ips/register_fasttrack.html

2.1.2 Required Disk Space

Your system requires a minimum of 500K blocks of hard disk space; 700K blocks is recommended.

2.1.3 Required Accounts

Two accounts are required:

• An account to run the Administration Server, usually the SYSTEM account
• An account to run the FastTrack server (also known as the Web Server or Personal Server), called the FASTTRACK account

Each account must have a valid default device and directory that is owned by the account.

2.1.4 Software and ECOs

Table 2-1 lists the software and ECOs (patches) that must be installed on your system.

Table 2-1 Required Software and ECOs

Software or ECO	Description	On OpenVMS 7.1	On OpenVMS 7.1-2	On OpenVMS 7.2 or later
ALPACRT07_071	DEC C RTL fixes (fork, exec).	Apply	Do not apply	Do not apply
ALPBASE02_071	Fixes needed to enable ALPACRT07_071.	Apply	Do not apply	Do not apply
ALPDCL01_071	Fixes for multiple kernel threading problem.	Apply	Do not apply	Do not apply
ALPSYSA01_071	Higher-priority thread blocking.	Apply	Do not apply	Do not apply
ALPSYSB02_071	IEEE arithmetic.	Apply	Do not apply	Do not apply
ALPTHREADS_03071	Threads patch.	Apply	Do not apply	Do not apply
VMS712_PTHREADS02	Threads patch.	Do not apply	Apply	Do not apply
DIGITAL TCP/IP Services for OpenVMS	Networking product.	Install V4.2	Install V4.2 or V5.0	Install V4.2 or V5.0

Because the status of ECOs changes frequently as new versions supersede previous versions, query the ECO cited in Table 2-1 and install the latest version resulting in your query. To verify that you have the correct file, refer to the ECO Note found on the page of the ECO you queried. Generally, this Note lists any ECO kits superseded by the most current kit.

You can download OpenVMS Alpha Version 7.1 ECOs from the following URL:

http://ftp1.service.digital.com/patches/public/vms/axp/v7.1/

For issues concerning the service.digital.com gateway only, you must log a call. An online form can be found at:

http://www.service.digital.com/html/gw-feedback.html

2.1.5 SYSGEN Parameters

Set the SYSGEN parameter CHANNELCNT to 512 (unless it is already set at a higher value). This is double the default value of 256. Compaq recommends 512 for servers that are expected to have medium to heavy traffic.

2.1.6 Required Quotas

Table 2-2 lists the recommended quotas for each of the two server accounts, SYSTEM and FASTTRACK.

Table 2-2 Required Quotas

Quota	Default	On SYSTEM	On FASTTRACK
ASTLM (NonPooled) Total number of asynchronous system trap (AST) operations and scheduled wake-up requests that the user can have queued at one time.	250	250	250
BIOLM (NonPooled) Buffered I/O count limit is the maximum number of buffered I/O operations, such as terminal I/O, that can be outstanding at one time.	150	150	150
BYTLM (Pooled) Maximum number of bytes of nonpaged system dynamic memory that a user's job can consume at one time. Nonpaged dynamic memory is used for operations such as I/O buffering, mailboxes, and file-access windows.	64000	100000	400000
CPU (Deductible) Maximum CPU time allowed. Zero means no limit.	0	0	0
DIOLM (NonPooled) Maximum number of direct I/O operations (usually disk) that can be outstanding at one time.	150	150	150
ENQLM (Pooled) Specifies the lock queue limit.	2000	2000	2000
FILLM (Pooled) Open file limit is the maximum number of files that can be open at one time, including active network logical links.	100	100	250
JTQUOTA (Pooled) Byte quota with which the jobwide logical name table is to be created.	4096	4096	4096
MAXACCTJOBS (SystemWide) Maximum number of batch, interactive, and detached processes that can be active at one time for all users of the same account. Zero means no limit.	0	0	0
MAXDETACH (SystemWide) Maximum number of detached processes with the cited user name that can be active at one time. Zero means no limit.	0	0	0
MAXJOBS (SystemWide) Maximum number of processes (interactive, batch, detached, and network) with the cited user name that can be active at one time. The first four network jobs are not counted. Zero means no limit.	0	0	0
PGFLQUO (Pooled) Maximum number of pages that the user's process can use in the system paging file.	50000	200000	200000
PRCLM (Pooled) Maximum number of subprocesses that can exist at one time for the specified user's process.	8	0	0
TQELM (Pooled) Total number of entries in the timer queue plus the number of temporary common event flag clusters that the user can have at one time.	10	20	20
WSDEF (NonPooled) Specifies the default working set limit. This represents the initial limit to the number of physical pages the process can use.	2000	2048	2048
WSEXTENT (NonPooled) Specifies the working set maximum. This is the maximum amount of physical memory allowed to the process. The system provides memory to a process beyond its working set quota only when it has excess free pages.	16384	64000	64000
WSQUO (NonPooled) Specifies the working set quota. This is the maximum amount of physical memory a user process can lock into its working set. It also represents the maximum amount of swap space that the system reserves for this process and the maximum amount of physical memory that the system allows the process to consume if the systemwide memory demand is significant.	4000	32000	32000

2.1.7 Required Privileges

The SYSTEM account must be classified as an OpenVMS system account. Specifically, its UIC group must be not more than the value of the SYSGEN parameter MAXSYSGROUP (usually 10 octal). The SYSTEM account should have all privileges.

The FASTTRACK account must have the following privileges (DEFPRIV and PRIV):

NETMBX OPER TMPMBX SYSGBL PRMGBL

The OPER privilege is required for the FASTTRACK account only if you will be using a port number of 1024 or lower.

The PRMGBL and SYSGBL privileges are required only if you use the Server Status | Monitor Current Activity capability (also known as Site Monitor). To use the Site Monitor, you must also install the ALPACRT07_071 (or higher) patch from the following:

http://ftp1.service.digital.com/patches/public/vms/axp/v7.1/alpacrt07_071

2.1.8 Required File Protection Settings

During the installation of the FastTrack server, the current process must have the standard default file protection settings (SYSTEM:RWED, OWNER:RWED, GROUP:RE, WORLD). To confirm the protections, use the SHOW PROTECTION/DEFAULT command. To change the protections, use the SET PROTECTION/DEFAULT command.

The two accounts that are used by FastTrack (SYSTEM and FASTTRACK) must also have the default file protection setting. If necessary, insert a SET PROTECTION/DEFAULT command into the account's LOGIN.COM to reset the default protection.

2.1.9 Required Global Pages and Global Sections

When the Administration and FastTrack servers are started, they require the following number of global pages and global sections:

Global Pages: 12960 Global Sections: 26

2.1.10 Browser Requirement

Before you can install the server, you must have installed a Web browser that supports frames and JavaScript (for example, Netscape Navigator or Navigator Gold 3.0 or higher, or Netscape Communicator). It can be an OpenVMS browser or any other browser.

2.1.11 JavaScript Requirement

JavaScript must be enabled in your Web browser before you can administer either your Administration Server or your Web server using the Server Manager forms.

2.1.12 DIGITAL TCP/IP Services for OpenVMS (UCX) Configured

Before you install the server, configure DIGITAL TCP/IP Services for OpenVMS. Enter the following commands to see your current settings.

$ UCX SHOW COMMUNICATION $ UCX SHOW CONFIG COMMUNICATION $ UCX SHOW COMM/MEMORY

Table 2-3 lists the TCP/IP parameters you should configure before you install the server. The third column shows the additional value you should add to the default value for each FastTrack server you are running on your system. For example, if you have two FastTrack servers running, you should set LARGE_BUFFERS to 400 (that is, 100 additional for each server).

Table 2-3 TCP/IP Parameter Settings

Parameter	Default	Additional value per server	Value with one server
LARGE_BUFFERS	200	100	300
SMALL_BUFFERS	1000	1000	2000
DEVICE_SOCKETS	60	500	560

The preceding values should be used only as guidelines. On a lightly loaded server, you may be able to use smaller increases, while on a heavily used system, you may need more. The only way to be sure that you are using the right values for these parameters is to monitor your system on a regular basis. Use the UCX SHOW commands shown at the beginning of the section to see the current settings and at what level their usage has peaked since the system was last rebooted.

2.1.13 DNS Configured

If you intend to use host names during the FastTrack server installation, make sure that DNS is configured properly and that your server has an entry in a DNS server.

2.2 Installing the Administration Server

This section describes the installation of the Administration Server. Section 2.3 describes how to use the Administration Server to install the FastTrack server.

After you download the backup save set and unpack the file (described in Section 1.3), enter the following command to start the server installation:

$ SET DEFAULT your-tempdir $ RUN NS-SETUP

For example:

$ SET DEFAULT DKA0:[FT_KIT] $ RUN NS-SETUP

If you do not have sufficient write access, you will receive a message similar to the following:

Can't write to <root> (error: permission denied) Press any key to continue Please choose another server root, of press control-C to exit

2.2.2 Accept Software License Agreement

Enter yes to accept the software license agreement.

2.2.3 Choose Server Root Directory

Enter a server root directory. This is the directory where the server files and directory structure are to be installed. For example:

DKA300:[USERS.MARYS.SUITESPOT]

You can have a maximum of three levels and you must specify an absolute path. This example illustrates both of these requirements.

You will be asked whether you want to configure the server. Press Return to continue.

If you enter no, or you have to restart the installation, enter the following:

$ SET DEFAULT server-root $ RUN [.BIN.ADMIN]NS-CONFIG

2.2.4 Enter Name

Enter the machine's fully qualified IP name or press Return to accept the default value.

2.2.5 Enter Port Number

Enter the Administration Server port number or accept the randomly generated default. This is the port from which the Administration Server runs. The installation program randomly picks a port number as a default. Make sure you take note of the port number, for example, 23703, for the Administration Server.

2.2.6 Enter Administration Server User Name

Enter the Administration Server user name as [SYSTEM].

2.2.7 Enter FastTrack Server User Name

Enter the user name that the FastTrack server will run as [FASTTRACK]. This user should be different from the Administration Server user name.

The user must own its default directory. For example, if the default directory is DKA0:[USERS.FASTTRACK] then DKA0:[USERS]FASTTRACK.DIR must be owned by the FASTTRACK account.

If the user default directory's ownership is wrong, you may see the following error written to the errors log:

failure: startup failure: could not bind to port 80 (VMS specific error)

2.2.8 Enter Path

If you already have a version of the Administration Server installed, you are asked for the path. Press Return to continue.

2.2.9 Answer LDAP Server Question

A prompt appears, asking whether you are using an LDAP server such as the Netscape Directory Server. Type Yes if you are using an LDAP server. If you are not using an LDAP server, type No and then skip the next step.

2.2.10 Enter LDAP Server URL

If you answered Yes to the prompt, type the LDAP server URL with the correct SSL information, server name, server port, and distinguished name (DN).

2.2.11 Enter Administration Server Authentication User Name

Enter the Administration Server authentication user name and password. Type the password again for verification. If you are using an LDAP server, make sure this user name has been added to the LDAP server and has the appropriate access permissions.

Enter the hosts that may access your Administration Server. The following example limits access to a single domain:

*.mcom.com

2.2.13 Enter IP Addresses

Enter IP addresses that may access your Administration Server. Entering an asterisk (*) allows universal access.

The installation program writes the Administration Server configuration files to disk. Your Administration Server is now configured. Press Return to continue.

At this point you can delete your temporary directory.

2.2.14 Start the Administration Server

To start the Administration Server, set default to the root you selected in Section 2.2.3 and enter the following:

$ SET DEFAULT yourroot $ @START-ADMIN

You are now ready to install and configure your new FastTrack web server. Launch the web browser and begin configuring your Netscape FastTrack Server immediately after installation. If you installed on a machine named digvms00, using port 23703, for example, then the URL to go to is:

digvms00:23703

2.3 Installing and Configuring the FastTrack Server

To use the Administration Server to install and configure the FastTrack server, perform the steps described in the following sections.

2.3.1 If You Are Migrating from a Version 1 Server

To migrate from a Version 1 server, do not create a new Netscape Personal Server. Instead, follow the instructions in Chapter 3 for instructions about migrating from Version 1 to Version 2.

2.3.2 If You Are Not Migrating from a Version 1 Server

If you are not migrating from a Version 1 server, your next step is to create a new Netscape Personal Server. From the Server Selector, click Create New Netscape Personal Server.

2.3.3 Enter Server Name

Enter the server name. Users will use this name when they access your server. Include your machine and domain name. If your system administrator has set up a DNS alias for your server, enter the alias here. If not, use the machine's name combined with your domain name as the server's name.

2.3.4 Enter IP Address

Enter the IP address your server should listen to (the bind address). Leave this field blank if you are not planning to have your system answer to different IP addresses.

If you do want your system to answer to multiple addresses, configure your system to listen to multiple IP addresses, then install separate instances of the server, each with a different bind IP address.

2.3.5 Enter Port Number

Enter the port number for your server. This can be any number from 1 to 65535. For example:

80

Keep the following in mind when choosing a port number:

• The standard web server port is 80; the standard SSL-enabled port is 443.
• The FASTTRACK account must have OPER privileges to start a web server with a port number of 1024 or lower.
• Make sure the port you choose is not already in use. Use UCX SHOW DEVICE to make sure you do not assign a port number that is used by another service.
• If you use a port other than the default port (port 80), the URL used to gain access to your home page will change. For example, if your machine is called www.mozilla.com and you choose port 8080, your server's URL will be http://www.mozilla.com:8080/.
• If you activate security on your server, the default HTTPS port is 443. Before security is active, you can access your server by using a URL of http://your_server.domain.com:443/.

Enter the server identification that the Administration Server will use for your server. This will be part of the process name for your web server. The server identification should contain no spaces or slashes.

For example:

port80

2.3.7 Enter User Name

Enter the user name under which you want the web server to run. For example:

FASTTRACK

2.3.8 Resolving IP Addresses to Host Names

Specify when you want the server to resolve IP addresses to host names. When an HTTP client connects to your server, it knows the client's IP address, but does not know its host name (for example, it does not know that the host name for 198.95.251.30 is www.acme.com). For certain operations like access control, CGI, error reporting, and access logging, the server will resolve the IP address to a hostname.

If your server responds to many requests per day, disabling hostname resolution can reduce the load on your DNS or NIS server.

2.3.9 Enter Document Root Directory

Enter the server's document root directory that will contain most of your server documents. If the directory you enter does not exist, the installation software will create the directory.

For example:

DKB200:[DOCS]

By creating a document root for all of your documents, you place all of your documents in one location, and the server handles the URLs. Any request for a document automatically gets redirected to the document root you enter here. Because full file system path names are neither used nor displayed on any browser, your file system is safe, and users are not able to get information about your system.

If you name a nonexistent directory, the software creates it for you (if possible). If it is not possible to create the directory, for example, if you make an error entering a device name, you must use a different server identification or clean up the files left with the previous one.

2.3.10 Configure More About Your Server

When you have completed the previous step, click OK.

If the configuration was successful, you will see a page showing your new server's name, the port it listens to, and the primary document directory. From this page, you can configure your server further, install another server, or return to the Server Administration Page.

Click "Configure more about your new server" to take you to the Server Manager, where you can configure your server.

You may want to consider enabling or activating the following features:

Content Management | User Document Directories

Content Management | Parse HTML

Programs | CGI File Type

The options should appear similar to the following:

On the server httpd-port80: obj.conf: Document root set to '/dkb200/docs/public_html' obj.conf: Activated public information directories obj.conf: URL prefix '/~', subdirectory 'public_html' obj.conf: Server parsed HTML activated for the entire server obj.conf: Without the exec tag obj.conf: Parsing all HTML files obj.conf: Activated CGI: the entire server

If you have Version 1.12 of Netscape Communications or Commerce Server installed, perform the following steps to migrate V1 servers and the user database to V2, and then from V2 to FastTrack Version 3.01A.

3.1 Before you Begin the Migration

Before you begin migrating from V1 to V3, be sure that:

• The FastTrack Server Version 3.01A has been installed.
• The V1 server is installed on a disk that is accessible from the V3 installation tree.
• You have examined the MAGNUS.CONF file of each V1 server, and recorded the user name listed in the 'User' line.

Before you begin the migration, you must create a user account for each user on the system where the V3 server was installed. The accounts created for this step can use a default setting, and can be removed after the V1 to V2 step is completed.

The preceding step is required for the V1 to V2 migration, because the V1 to V2 migration script requires that each listed user in each V1 servers' MAGNUS.CONF file is also an existing user on the system on which the migration is being run.

An alternative method is to manually edit each of the V1 servers' MAGNUS.CONF files and change the user name to one that already exists on the current system where the migration will be peformed. (You can use the FASTTRACK user name if such an account is already set up, but any user account is sufficient.)

If the migration is being performed on the same system on which the V1 server currently runs, these users already exist on the system, and there is no need to create any new user accounts before starting the migration.

3.2 Log In

To make the following steps easier to understand, assume that the V3 server is installed on DUA0:[SUITESPOT] and the V1 server is installed on DUA0:[NETSCAPE.COMMON].

Log in to the system on which V3 is installed, with the user name (usually SYSTEM) used to configure the V1 server.

If you are not sure which user name was used, search the following file in the V1 tree:

DUA0:[NETSCAPE.COMMON.ADMSERV.DATA]NS-ADMIN.CONF

Look for the line that starts with User. The value of user is the user name you should use to log in to the system.

3.3 Use Local Directory LDAP Setting

Be sure to use the local directory LDAP setting when upgrading from V1 to V3. This is the default setting.

If you want to move your users' LDAP files to a remote LDAP server, you can do so after the V1 to V3 migration is complete. Use the export option under the LDAP screen in the Administration Server to move the files.

3.4 Set Default

After you log in to the system, set default to the V3 directory where the migration programs are located, as follows:

$ SET DEFAULT DUA0:[SUITESPOT.INSTALL]

3.5 Start the V1 to V2 Upgrade

To start the V1 to V2 upgrade, enter:

$ @V1UPGRADE

At the prompt, enter the location where the V1 server is installed. Enter the location in a UNIX file format, not in an OpenVMS file format. Note that you must type the leading "/".

For example, assuming that V1 is installed on DUA0:[NETSCAPE.COMMON], enter the following:

/dua0/netscape/common

For another example, if the V1 server root is installed on BILDEM$DKB400:[USERS.NS.COMMON], enter the following:

/bildem$dkb400/users/ns/common

3.6 Choose a Nickname

For each V1 server listed in the SERVERS.LST file under the V1 server tree DUA0:[NETSCAPE], the procedure asks you to choose a nickname for the server. In the V3 tree, each server will have an ID associated with it. Enter the name you want this instance of the server to be known by in the V3 tree. Make sure that a unique ID is given to each server being migrated from V1 to V3, and that each ID does not conflict with another server ID in the V3 tree.

When the V1UPGRADE procedure is completed, a new temporary tree is created for the V2 server. This tree will be created in the V1 tree.

For example, if the V1 server tree was located in DUA0:[NETSCAPE.COMMON], the V2 temporary tree will be created in DUA0:[NETSCAPE.V2TEMP].

This concludes the V1 to V2 upgrade.

3.7 Start the V2 to V3 Upgrade

To start the V2 to V3 upgrade, start the V3 Administration Server. In the initial screen for the Administration Server, click on the following link:

Migrate from previous version

A new screen will appear similar to the following:

Choose 2.x Server Root to Import From

Remember that the 2.x server root resides on the system on which the Administration Server is running.

In the field named Directory, enter the name of the V2 server root. This is the same directory that the V1 to V2 upgrade created earlier. In Section 3.6, it is called DUA0:[NETSCAPE.V2TEMP].

Directory:" " Find Server Return to Server Selector

Enter this directory name in UNIX format. For example:

/dua0/netscape/v2temp

Make sure that there are no leading or trailing spaces in the name.

For another example, if the V2 temporary tree was located in BILDEM$DKB400:[NETSCAPE.V2TEMP], enter the following:

/bildem$dkb400/netscape/v2temp

Next, click Find Servers. A new screen appears that allows you to select the server to migrate. If you receive the following error, the file specification is incorrect or it has leading or trailing spaces:

Can't read server.lst: file specification syntax error

3.8 Choose Servers to Import

The following screen output appears.

Choose Servers to Import

Click the box next to a server to import its configuration:

Netscape Administration Server o Import security files for Administration Server Netscape FastTrack Server o Import httpd-user1

Click the option to the left of "Netscape FastTrack Server" to display the next screen:

Import 2.x Http Server Info Name: httpd-"server_id" User to run server as: " " IMPORT

The server ID will be added by the system. This is the server ID (or the nickname) selected earlier.

In the empty field next to the "User to run server as:" select the OpenVMS user name for the FastTrack server. See Chapter 2 for the requirements for the FastTrack account.

Next, choose the import option.

A new screen will appear showing the progress of the V2 to V3 upgrade, similar to the following output.

Importing Core Server... Core Server Imported. Importing ACL... ACL Imported. Importing Keys and Certificates... System Warning: Certificate database No 2.0 certificate database to convert. System Warning: No 2.0 key file No 2.0 key file to convert. Keys and Certificates Imported. Importing User Databases... Migrating all user/group databases: From old server root: /dkb400/netscape/v2temp/authdb to new server root: /bildem$dkb400/000000/suitespot/authdb Migrated 9 of 9 users from 2.0 database "number three" to local LDAP database Migrated 0 of 0 groups from 2.0 database "number three" to local LDAP database Finished migration of user/group databases.

3.9 After you Complete the Migration

Perform the following tasks to complete the migration process.

After you choose the servers to import, a new directory is created under the V3 server tree for each V1 server migrated. For example, assume that a server ID was given the value "ONE" during the upgrade. A directory called HTTPD-ONE is created under the V3 server root. For example, if the V3 server is installed in DUA0:[SUITESPOT], the following directory is created:

DUA0:[SUITESPOT.HTTPD-ONE]

This directory is used as an example in the following sections.

3.9.1 Review Server Settings

Some of the settings for the migrated V1 servers must be manually adjusted. The adjustments are needed in two configuration files for each migrated server.

These two files are OBJ.CONF and MAGNUS.CONF, located in DUA0:[SUITSPOT.HTTPD-ONE.CONFIG].

These files contain two types of file paths that must be corrected:

• A file path that still references the original V1 installation directory
• A file path that references a directory in the V2 temporary tree. (The V2 temporary tree is created by the V1 to V2 migration step.)

Following are the known entries in MAGNUS.CONF that need manual adjustment:

ErrorLog PidLog ServerRoot

Following are the known entries in OBJ.CONF that need manual adjustment:

flex-init pfx2dir entries that use V2TEMP

You may find that your MAGNUS.CONF or OBJ.CONF files contain additional entries that need to be corrected. Examine OBJ.CONF and MAGNUS.CONF, and search for any path that contains V2TEMP. For each such entry, correct it to make it point to the correct V3 path.

For example, assume that the V1 server was installed on BILDEM$DKA200:[xxx.COMMON], and that the V3 server was installed on DUA0:[SUITESPOT].

In MAGNUS.CONF, you would correct the following line (because it contains V2TEMP):

ErrorLog /bildem$dka200/xxx/v2temp/httpd-u80/logs/errors

Change the preceding line to:

ErrorLog /dua0/suitespot/httpd-u80/logs/errors

Next, adjust two entries in OBJ.CONF that reference a location in the old V1 directory. Modify the lines in OBJ.CONF that contain the following two entries:

'flex-init' 'secure='

Notice that the path in these two entries point to the V1 tree.

Replace the path to point to the new V3 tree. For example, modify the following lines:

Init fn="flex-init" global="/bildem$dka200/xxx/vax/httpd-80/logs/access"

to the following:

Init fn="flex-init" global="/dua0/suitespot/httpd-80/logs/access"

3.9.2 Copy Modified Configuration Files

After completing the manual edits to the files MAGNUS.CONF and OBJ.CONF, move a copy of these files to another directory, as follows:

$ SET DEF DUA0:[SUITESPOT.HTTPD-ONE.CONFIG] $ COPY MAGNUS.CONF [-.CONF_BK] $ COPY OBJ.CONF [-.CONF_BK]

Enter the preceding commands for each migrated server.

3.9.3 Change Ownership of Newly Installed Server Tree

Adjust the protection on the newly migrated server instance tree to allow the FastTrack server access to it. This example assumes that the user under which the FastTrack server will run is called FASTTRACK. Enter the following commands:

$ SET FILE/owner=FASTTRACK DUA0:[SUITESPOT]HTTPD-ONE.DIR/PROT=W $ SET FILE/owner=FASTTRACK DUA0:[SUITESPOT.HTTPD-ONE...]*.*.*

This example assumes that the V3 installation was made on DUA0:[SUITESPOT] and that the V1 to V3 migrated server was assigned an ID of ONE.

3.9.4 Reenter User Passwords

Because of incompatibilities between the way user passwords are stored in V1 and in V3, you should use the V3 Administration Server to reenter user passwords stored in the V1 database.

You can do this by selecting the Users & Groups screen in the Administration Server. Choose the Manage Users option, select and edit each user, choosing the password option, and enter the password again.

3.9.5 Start the Server

The migrated server is now ready to be started. Follow the usual procedures to start the server from the Administration Server initial screen.

This chapter discusses information specific to the FastTrack Web Server for OpenVMS Alpha.

4.1 Features Not Supported on OpenVMS

The following Administration Server features are not supported on OpenVMS:

• Global Settings | SNMP Master Agent Communication
• Global Settings | SNMP Master Agent Trap
• Global Settings | SNMP Master Agent Control

The following FastTrack features are not supported on OpenVMS:

• Server Preferences | Symbolic Links
• Server Preferences | UNIX Chroot
• Server Preferences | Convert 2.0 ACL

Unsupported features do not appear on the server screens.

4.2 Naming Conventions

On OpenVMS, user names and passwords are not case sensitive. However, when using the Netscape software, many entries may be case sensitive; for instance, both user names and passwords are case sensitive.

To avoid problems during the installation process, use uppercase for file names, user names, and passwords.

In most cases, you can input either UNIX style file names or OpenVMS style file names. Output is usually see UNIX style file names.

Occasionally, file names are constructed by the software. In this case, you may be required to use UNIX style syntax (for example, for a root to which additional directories or a file name is appended) because mixed styles are not supported.

4.2.1 Version Numbers in OpenVMS File Specifications

OpenVMS file specifications are permitted in most places where a file name must be provided. However, a version number cannot be specified.

This means that you can use only the highest version of a particular file. If you want to specify an older version of a particular file, rename the higher version of the file so that the version you want to specify becomes the highest version.

4.2.2 When UNIX Style File Names are Required

There are several dialogs in the Administration Server that accept only UNIX style file specifications.

One of these dialogs is the server-side JavaScript Web file path. Others include dialogs for settings in Hardware Virtual Servers & Software Virtual Servers.

4.2.3 Use Fully Qualified Name When Setting ACL on Server Based on Host Name

Setting an ACL on the server based on host name (for example, to allow all access from some host name) works only if the host name specified in the ACL is a fully qualified host name.

For example, setting an ACL to allow access to anyone from host 'host', and then trying to access the server from 'host' will result in an error, and one cannot access the server. But changing the host name to 'host.company.com' will work. Always use a fully qualified host host with ACL setting. Alternatively, use the IP address.

4.3 Running FastTrack on an OpenVMS Cluster

FastTrack Version 3.01A uses the Netscape clustering feature described in Chapter 3, Managing Clusters, of the Administrator's Guide.

Netscape uses the term "cluster" to refer to a collection of servers that can be managed from a single Administration Server. This is very different from an OpenVMS Cluster, which is a group of OpenVMS Alpha and OpenVMS VAX systems that work together as one virtual system.

FastTrack for OpenVMS Alpha is not designed to utilize OpenVMS clustering technology. A separate installation of FastTrack is required on each node of an OpenVMS Cluster that will run FastTrack.

4.4 CGI Information

The following types of CGI files are supported: executable, DCL, and Perl.

A native image CGI file runs immediately. If the image was written in C, then all the standard CGI environment variables will exist. Executables written in other languages will not inherit these environment variables and should use a DCL wrapper.

If the CGI file is not a native image, then DCL will be invoked to run the CGI file. If the file type of the CGI is .PL then the CGI will be considered a Perl script and Perl will be run to execute the script. If the file type is not .PL, then the CGI file is considered to contain valid DCL commands, and the file is passed on to DCL. With both DCL and Perl files, the standard CGI environment variables will exist when the CGI file is invoked.

A CGI file runs from the FastTrack server account. The only privileges the CGI runs with are TMPMBX and NETMBX.

4.4.1 Additional CGI Environment Variables

In addition to the standard set of CGI environment variables, the FastTrack server will define these additional two environment variables:

• VMS_CGIPATH --- the full file path of the CGI. For example:

  /dka200/suitespot/cgi/mycgi.exe

• VMS_CGIPATH_VMS --- same as VMS_CGIPATH but in OpenVMS file format. For example:

  DKA200:[SUITESPOT.CGI]MYCGI.EXE

When you run a CGI under the FastTrack server, the current default directory is undefined. Therefore, you cannot depend on your CGI being run from a certain directory. Any CGI that depends on being run from a certain directory might not function.

To correct this, modify the CGI to chdir to your desired directory. You can use the environment variable, VMS_CGIPATH, to determine where your CGI resides. VMS_CGIPATH is the complete path of your CGI.

For example:

chdir2vms_cgipath() { char *vms_cgipath=NULL, *cgidir=NULL; if ( vms_cgipath = getenv("VMS_CGIPATH") ) if ( cgidir = dirname(vms_cgipath) ) chdir( cgidir ); }

4.5 Perl Information

Perl is not a prerequisite because FastTrack includes its own version of Perl (V5.004_03). If you already have a version of Perl installed on your system, that version will not be affected by the installation of FastTrack.

If you want to have a different version of Perl used within your FastTrack environment, you can update the PERL/PERLSHR images in the FastTrack installation directory. Note that FastTrack has been tested only with Perl Version 5.004_03, and by changing the version, you may lose some functionality in the FastTrack server.

4.6 Running ROTATE.COM to Rotate Server Log Files

On OpenVMS, server log files can not be automatically rotated at predefined times by the Administration Server. If you attempt to configure this, you will receive a message that this feature is not supported.

If you want to have the log files rotated at a specified time, you can submit ROTATE.COM. This command procedure, which resides in the [.HTTPD-<nickname>] directory, renames each log file by appending a date/time string to the file name. For example, ACCESS is renamed to ACCESS.20JUL-06PM, indicating that the rename occurred on July 20, sometime between 6:00 PM and 6:59 PM.

To have ROTATE.COM run at 2:00AM tomorrow morning, enter a command similar to the following:

$ SUBMIT /AFTER="TOMORROW+2::" DKA0:[SUITESPOT.HTTPD-TEST]ROTATE

ROTATE.COM accepts no parameters and rotates all defined log files. Make sure it is run from an account that has access to the log files.

If the server is running, it is restarted after the log files are rotated.

4.7 Using the -z Option for Starting the SSL Server

After you have configured the FastTrack Personal Server to be a secure server (by setting the security option on and installing the security certificate and key-pair files), the server then requires a password every time before it will start. This is the same password you entered into the pop-up window when you configured the server to become an SSL server.

To start the SSL server from the command line, enter the following:

$ @START "-z password"

The lowercase z is followed by one or more spaces, followed by the password exactly as entered when the server was configured as an SSL server.

START.COM is the file used to start the FastTrack Personal Server from the command line. This file is located in the server's own instance directory. For example, if the server ID was called server_one, then the file START.COM is located in the [.HTTPD-server_one] directory.

If the argument "-z password" was omitted from the command line, and the server is an SSL server, then you are prompted to enter the password on the command line.

4.8 Ldapsearch and Ldapmodify

The online help for the FastTrack server refers to ldapsearch and ldapmodify as command line utilities. They are in [<serverroot>.userdb.ldap.tools] and can be run from the DCL prompt.

For example:

$ SET DEFAULT [YOURSERVERROOT.USERDB.LDAP.TOOLS] $ MCR []LDAPSEARCH -b "" "-C" - _$ /yourserverroot/userdb/ldap/config/lcache.conf

Note that if a UNIX style parameter is a capital letter, it must be in quotation marks.

4.9 Logical Names

The following sections discuss logical name considerations.

4.9.1 Shareable Image Name in External Libraries Field

When you install server-side JavaScript applications, you are asked to specify the absolute paths of any libraries to be used with the application in the External Libraries field.

On OpenVMS, the External Libraries field corresponds to the name of a shareable image on your OpenVMS system. A logical name must be used to locate the image if it is not in SYS$SHARE.

For example, if you call registerCFunction(JSFunctionName, libraryPath, externalFunctionName) in your JavaScript code on OpenVMS, libraryPath is not a path, but rather the name of your OpenVMS shareable image.

For example, FOOSHARE is valid, but /sys$share/fooshare.exe and sys$share:fooshare.exe are invalid.

Therefore, in both your JavaScript call to registerCFunction and in the External Libraries field, use FOOSHARE.

4.9.2 File Sharing in Java Virtual Machine

File sharing is available in FastTrack's embedded Java virtual machine (JVM). The JVM has several user-selectable modes of file sharing. To enable JVM file-sharing modes, define the logical JAVA$FILE_OPEN_MODE to any of the following values:

Value	Description
0 or not defined	No sharing.
2	Synchronous writes, every write to a file, the file is synchronized with the disk. Note: A sync for every write gives you file sharing close to what the JVM expects. However, things that normally take seconds to run can take minutes or longer.
3	A table of all open file descriptors is kept by the JVM. The JVM then monitors when an application writes to a file and sets a write_pending flag. Before every read operation, the JVM scans the list of open file descriptors. If a match is found with a write pending, the pending write is flushed to the disk before the read.

Note that, with JVM file sharing, only one process can share the file reliably.

The logical name must be defined in such a way that the server processes can see it. Compaq recommends that you define it in the START.COM command file (in the server root directory), after the line that defines JAVA$FILENAME_CONTROLS.

4.9.3 User Document Directories---Logical Names Needed

To activate User Document Directories (also known as User Public Directories) with your FastTrack server, perform the following steps. Assume a FastTrack installation in DUA0:[SUITESPOT], with a FastTrack Server "httpd-ft301" in DUA0:[SUITESPOT.HTTPD-FT301].

1. Choose "This File" for your Password File from the User Document Directory setup page. Type in an absolute file specification in UNIX format. For example:

   /dua0/suitespot/httpd-ft301/config/user.list

2. Choose "Load entire database on startup."
3. In a logical name table accessible by the account that will execute DUA0:[SUITESPOT.HTTPD-FT301]START.COM, define the logical NETSCAPE$UPD_PWFILE_NAME to point to the OpenVMS specification of the file entered for "This File" in step 1.

For example, before starting the FastTrack server, use the DEFINE command as follows:

$ DEFINE /SYSTEM NETSCAPE$UPD_PWFILE_NAME - _$ DUA0:[SUITESPOT.HTTPD-FT301.CONFIG]USER.LIST

Although this logical does not have to be in the system table, it must be accessible by the account that starts your FastTrack server. If you are starting your server using the Administration Server, then the logical must be accessible by the account in which your Administration Server runs.

To start the FastTrack server, enter the following command from a privileged account:

$ @DUA0:[SUITESPOT.HTTPD-FT301]START.COM

This command will read in directory data from the SYSUAF file, and will write the data to the DUA0:[SUITESPOT.HTTPD-FT301.CONFIG]USER.LIST file in a format that the FastTrack server understands.

You also have an additional option for enhanced security. Before starting your FastTrack server, you can define the logical NETSCAPE$UPD_AUTO_DELETE_PWFILE in a location accessible by the FastTrack server account. For example:

$ DEFINE /SYSTEM NETSCAPE$UPD_AUTO_DELETE_PWFILE 1

When the FastTrack server initializes, it will read in the data from the Password File you chose and then will delete that file. This way the account information is in the memory of only the running FastTrack server.

Also note that any changes made to the SYSUAF data after the FastTrack server has started will not take effect until the next FastTrack server startup.

When you are using the NETSCAPE$UPD_PWFILE_NAME logical to create a data file at FastTrack server startup, certain accounts that share the same UIC may not be picked up by the server.

4.10 Record Format Stream_LF

Most UNIX file-type restrictions have been removed from the FastTrack server software. However, occasionally you may discover that a particular file must have record format Stream_LF.

For example, the certificate database file must be Stream_LF.

To convert a file to record format Stream_LF, use CONVERT with an FDL. For example:

FILE ORGANIZATION sequential RECORD BLOCK_SPAN yes CARRIAGE_CONTROL none FORMAT stream_lf SIZE 32767

If the file containing these lines is called STREAM.FDL, then the form of the CONVERT command is:

$ CONVERT /FDL=[DIRECTORY]STREAM input-file output-file

4.11 Certificate Migration

The Security Certificates in V1.12 of the Netscape Communications and Commerce Servers are not migrated. This includes the Server Security Certificate and the Server's key-pair file (public and private keys).

4.12 Web Server Startup

The web server does not start if you configure the server from Content Management | User Public Directory and then do the following:

• Activate the public information directories with Password File options.
• Use the System file (default).
• Select Loads entire database on startup (not the default).

The message in the web server's log file (SYS$LOGIN:START.LOG) is as follows:

OpenVMS FastTrack unable to load SYSUAF at startup. Please change your User Public Directory settings.

To correct this problem, go back to Content Management | User Public Directory and turn off the "Loads entire database on startup" option.

4.13 Log Analyzer Command 255 Character Limitation

You can run the log analyzer from the FastTrack server or from the OpenVMS command line to analyze multiple logs. However, the OpenVMS command has a 255-character limit.

To analyze more logs in one OpenVMS command, go to the server log directory and run the log analyzer from that directory. For example:

$ SET DEF [<server_root>.HTTPD-XYZ.LOGS] $ MCR [<server_root>.EXTRAS.FLEXANLG]FLEXANLG.EXE - _$ -i LOG1 -i LOG2 -i LOG3 -O OUTPUTFILE ....

	privacy and legal statement
6560PRO.HTML