Part 2. Planning for and installing your server

Chapter 3. Planning for installation

Use this chapter to prepare for installing your server.

Check READ.ME

Prior to installing your server, look at the READ.ME file for any late changes to the planning information, installation procedure, or other information in this book.

Hardware requirements

For Windows NT, you need:

• Any PS/2 or personal computer that can support Windows NT 3.51 or 4.0

• A mouse or compatible pointing device

• Any communication hardware adapter supported by Windows NT

• A minimum of 12 MB of RAM; recommended RAM is 24 MB

  12-24 MB of memory can be divided between RAM and a swap file on a hard disk.

• Approximately 11 MB of free disk space for installation:
  • Approximately 4 MB to install the server.
  • Approximately .5 MB to install the security files.
  • Approximately .1 MB to install the NT service files.
  • Approximately 6.3 MB to install the Nodelock Administration Tool (NAT) files.

• A CD-ROM drive, if you are installing your server from a CD

Software requirements

For Windows NT, you need:

• Microsoft Windows NT or NT-J Server or Client (Workstation) 3.51 or 4.0, with TCP/IP configured

• A partition formatted using the NT File System (NTFS), the High Performance File System (HPFS), or the File Allocation Table (FAT). We recommend that you use NTFS for better file protection.

• For SNMP support, install the SystemView Agent Developers toolkit which can be downloaded from the http://www.software.ibm.com/download/ URL.

• To compile and run Java servlets, you will need the Java Developers' Kit (JDK), Version 1.0.2.

  You can download JDK from the IBM software download library at URL http://www.software.ibm.com/download.

  We will provide our own version of the Java servlet classes in the icsclass.zip file.

  Note: To use Java servlet support, the CLASSPATH environment variable must be set as follows before you install the Internet Connection Secure Server:

  CLASSPATH=C:\java_home_directory\lib\classes.zip
  

  When you install the Internet Connection Secure Server, the installation program will automatically add the icsclass.zip file to your CLASSPATH environment variable.

To prevent the entire screen going black and flashing a few times before a pop-up window is displayed, set the default MS-DOS mode for the Display Options for Console Windows to "Window" rather than "Full Screen". For Windows NT, use the "Console" control panel to set the Display Options for Console Windows to "Window".

Compatibility

IBM's Web clients and servers use industry standard protocols and are compatible with other Web clients and servers that are compliant with these protocols.

Migration considerations

This section describes issues that you should consider when migrating from a previous release.

Imbeds directive

In Version 4 Release 2, the imbeds directive is required for server-side includes. In previous releases, you could specify that documents with a specific extension or suffix be processed for server-side includes. If you specified an extension or suffix of .html or .htm, you do not need to make any changes to your configuration file. If you specified any other extension or suffix, you need to check the AddType directives and make sure you have an AddType defined for that suffix that has a content type of text/x-ssi-html. See the Webmaster's Guide for information about this directive.

Proxy server and caching proxy server

The Configuration and Administration forms for defining proxy and caching proxy settings have been rearranged and changed slightly. Two forms have been deleted and the information from them has been added to the other proxy forms.

These forms have been deleted:

• Time Limit for Cached Files
• Cache File Expiration

In addition, the CacheTimeMargin directive has been deleted. See the Webmaster's Guide for information about configuring your server as a proxy server or caching proxy server.

Proxy authentication

Server IP Address

Beginning with Version 4 Release 2, a wildcard character can no longer be specified for a server's IP address. This applies to the following directives:

• imbeds
• Welcome
• DefProt
• Protect
• Exec
• Fail
• Map
• Pass
• Redirect
• Enable
• NameTrans
• Service

CHECKIN and CHECKOUT methods for the Enable directive

Beginning with Version 4 Release 2, the CHECKIN and CHECKOUT methods are no longer supported. You can use the PUT method for CHECKIN and the GET method for CHECKOUT; however, the Internet Connection Secure Server does not perform locking or versioning.

Accessory script directives

The accessory script directives, DELETE-Script, POST-Script, PUT-Script, and Search, are no longer supported. You need to port your scripts to ICAPI applications. See the Web Programming Guide for more information.