Installation and Migration Guide iPlanet Web Server, Enterprise Edition Version 6.
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corporation. All rights reserved. Sun, Sun Microsystems, and the Sun logo, iPlanet, and the iPlanet logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Netscape and the Netscape N logo are registered trademarks of Netscape Communications Corporation in the U.S. and other countries.
Contents About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 What You Need to Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 What’s in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Document Conventions . . . . . . . .
Chapter 2 Installing iPlanet Web Server, Enterprise Edition on Unix . . . . . . . . . . . . . . . . . . Installing on Unix Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging In as the Correct User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unpacking the Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrating ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating Search Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating Search Pattern Files . . . . . . . . . . . . . . . . . . .
iPlanet Web Server, Enterprise Edition Installation and Migration Guide • May 2001
About This Guide This guide explains how to install iPlanet™ Web Server, Enterprise Edition 6.0 and how to migrate from a previous version of the iPlanet Web Server to this version.
What’s in This Guide What’s in This Guide The iPlanet Web Server Installation and Migration Guide covers the information you need to install iPlanet Web Server on your system. If you have a previous version of iPlanet Web Server installed, this guide also explains how to migrate your data.
Where to Find This Guide Online Where to Find This Guide Online You can find the iPlanet Web Server Installation Guide online in PDF and HTML formats. To find these files, use this URL: http://docs.iplanet.com/docs/manuals/enterprise.html The information in this guide is also part of the help system for iPlanet Web Server. See “How to Use Online Help.
Where to Find Related Information 10 iPlanet Web Server, Enterprise Edition Installation and Migration Guide • May 2001
Chapter 1 Before You Install iPlanet Web Server, Enterprise Edition The following sections provide the information you need to know before you install iPlanet Web Server, Enterprise Edition.
Supported Platforms Supported Platforms iPlanet Web Server, Enterprise Edition runs on these platforms: Table 1-1 Supported Platforms Operating System Architecture Required Memory Required Disk Space Hewlett-Packard HP-UX 11.0; 11.0 64 supported through binary compatibility PA-RISC 64 MB minimum 110 MB minimum IBM AIX 4.3.3 Power PC 64 MB minimum 110 MB minimum Sun Solaris 2.6; Solaris 8 Ultra SPARC 64 MB minimum 110 MB minimum Microsoft Windows NT version 4.0 with Service Pack 6a.
Hardware and Software Requirements Unix/Linux • Swap space at least as large as the amount of RAM on your system (twice the amount of RAM is recommended). Linux requires 256 MB swap space. • Netscape Communicator 4.72 or higher, or Microsoft Internet Explorer 5.0 or higher. • Java and cookies enabled in your browser. • If you are using Internet Explorer, you need to set your browser to check for a new version of a page every time you access it.
Other Technical Requirements • If you are using Internet Explorer, you need to set your browser to check for a new version of a page every time you access it. To configure this setting, from the View menu, choose Internet Options. On the General tab, in the Temporary Internet Files section, click Settings. Click the radio button to check for newer versions of stored pages every visit to the page. • Java and cookies enabled in your browser.
Other Technical Requirements For example, you might call the server my_server.my_company.com and then use an alias like www.my_company.com. So the URLs to documents on your server would always use the www alias instead of my_server. NOTE DNS names should start with a letter, not a number. Unix and Linux User Accounts for the Server When the iPlanet Web Server starts, it runs with a Unix or Linux user account that you specify during installation.
Other Technical Requirements Windows NT User Accounts for the Server You should create a Windows NT user account for your iPlanet Web Server. It should have restricted access to your system resources and run under a nonprivileged system user account (one that has a limited set of system permissions to your system). When the server starts, it runs with this user account. Any server extension modules the server uses are created with this user account as the owner.
Installation Overview Make sure the port you choose isn’t already in use. On Unix and Linux systems, you can check the file /etc/services on the server machine to make sure you don’t assign a port number that is reserved for another service. If you choose a port that is currently being used by another service, the installation program prompts you for another port. NOTE If you use Unix or Linux, and you choose a server port number lower than 1024, you must be logged in as root to start the server.
Installing Netscape Communicator CAUTION 4. iPlanet Web Server 6.0 and iPlanet Directory Server 5.0 cannot exist in the same directory. If you plan to install iPlanet Directory Server 5.0 on the same machine as your web server, you must install it in a different directory than iPlanet Web Server 6.0. Install and configure iPlanet Web Server.
Installing iPlanet Directory Server Installing Communicator on Windows NT To install Netscape Communicator you can download the software from http://home.netscape.com, or follow these steps to install from the CD: 1. Put the iPlanet Web Server CD-ROM in the drive and double-click the ntx86 folder. 2. Double-click to the comm472 folder. 3. Double-click setup.exe. 4. Follow the onscreen instructions.
Installing Netscape Console NOTE NOTE You can install iPlanet Directory Server and iPlanet Web Server on the same Windows NT machine if you do the following: • If during installation you are asked which version of libraries to install, always select those which have the most recent release dates. • If you need to uninstall either product, you must first make a copy of the uninstall program (uninst.exe) since it will be removed during the uninstall process.
Installing a Java Developer’s Kit Installing a Java Developer’s Kit If you are planning to use JSPs that have not been compiled, you must install a Java Developer’s Kit (JDK), also referred to as a Java 2 Software Development Kit (SDK). Servlets and precompiled JSPs require only the JRE that comes with iPlanet Web Server. CAUTION If you are using HP-UX, you must install the JRE included with iPlanet Web Server or supply a JDK. Without one or the other, the HP-UX iPlanet Web Server won’t run.
Accessing iPlanet Web Server from the Netscape Console Accessing iPlanet Web Server from the Netscape Console If you want to be able to access the iPlanet Web Server from the Netscape Console, run the installMCC script after you install iPlanet Web Server and the Netscape Console. installMCC is a perl script found in server_root/bin/https/bin. To run the script, follow these steps: 1.
Chapter 2 Installing iPlanet Web Server, Enterprise Edition on Unix This chapter tells you how to install iPlanet Web Server on Unix systems. It contains the following sections: • Installing on Unix Platforms • Installing Across Multiple Machines • Using Uninstall on Unix Installing on Unix Platforms The topics in this section describe the installation of iPlanet Web Server on Unix platforms. CAUTION You must install your version 6.
Installing on Unix Platforms If you meet these conditions, you do not need to log in as root to install the server; instead log in as the user account that the Administration Server will use. However, you may still prefer to log in as root, even though you meet the conditions. Unpacking the Files To get the iPlanet Web Server files and unpack them, follow these steps: Installing from an iPlanet Web Server, Enterprise Edition CD 1. Put the iPlanet Web Server, Enterprise Edition CD in the drive. 2.
Installing on Unix Platforms This command unpacks the server files and creates a temporary directory structure under the current directory. Unpacking the file may take a little time. When the files are unpacked, you see a WebServer directory, and the following files: LICENSE.txt, README.txt, setup, setup.inf, installWrapper, and template.inf. Installing a Downloaded Server 1. Download the file from http://www.iplanet.com/download/download and save it in a temporary directory. 2.
Installing on Unix Platforms Express installation is for users who have little experience or are evaluating the product. It makes assumptions about such things as port number and which components to install. When running the installer, you can use the following commands: • Press the Enter key to accept defaults specified in brackets (for example [All]). • Press CTRL+B to return to a previous screen (note that this sequence does not work on all screens).
Installing on Unix Platforms You need to run the server as a user that has write access to this directory, for example, the directory owner. 7. Choose all components. Press Enter. 8. Choose the iPlanet Web Server subcomponents to install If you do not install a subcomponent and later decide you want to use it, you can run the installer again to install just the missing subcomponent. However, you cannot uninstall individual subcomponents once they are installed.
Installing on Unix Platforms Java Support. Install this subcomponent if you are planning to use the Administration Server and/or Java servlets. You also need a JRE or JDK/SDK to use iPlanet Web Server’s Java support. Install the JRE provided with iPlanet Web Server (see the previous subcomponent) or install a JDK/SDK. Search and Indexing Support. Install this subcomponent to search the contents and attributes of documents on the server.
Installing on Unix Platforms 14. Type the port number of iPlanet Web Server. The default is 80. This port should be different than the Administration Server port. Unless you are installing as root, the port must be within the stated range (1024 to 65535). If you are installing as root you can use port numbers below 1024. 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 computer is called www.iplanet.
Installing on Unix Platforms 20. To configure your iPlanet Web Server, use the URL: http://server_name:administration_port For example: http://www.iplanet.com:8888 Enter your administration user name and password. You can now configure your iPlanet Web Server. For more information, see the iPlanet Web Server Administrator’s Guide. Express Installation Express installation is for users who have little experience or are evaluating the product.
Installing on Unix Platforms To run setup, follow these steps: 1. If you are not in the directory already, change to the directory where you unpacked the file. 2. Type ./setup to start the server installation. A welcome screen appears. 3. Press Enter to continue with the installation. 4. Choose whether you accept the software license agreement by entering Yes to accept, or No to decline. If you have not yet read the license agreement, cancel out of the installation and read the file LICENSE.
Installing Across Multiple Machines 12. Go to the https-adminserv directory under your server root directory (for example /usr/iplanet/servers) and start Administration Server by typing ./start. You can also type ./startconsole in the server root directory. startconsole starts the Administration Server and launches a browser to the Administration Server administration pages. 13. To configure your iPlanet Web Server, use the URL: http://server_name:administration_port For example: http://www.iplanet.
Installing Across Multiple Machines To run templatized installation, perform the following steps: 1. In the /.rhosts directory of your local machine, create an entry for each remote machine where you will install the web server using the format remote_machine_name username For example, if the remote machine is host1 on the domain dogs, and you are logged in as root, enter the following information: host1.dogs.com root 2. In the /etc/hosts.
Installing Across Multiple Machines 8. Enter the installation settings: ❍ HostNames: the name of the host where the web server will be installed, separated by commas. For example: host1,host2,host3 ❍ Components: the components to install, separated by commas. For example: Nescore,jre,snmp For a list of components, see “Choose the iPlanet Web Server subcomponents to install,” on page 27.
Installing Across Multiple Machines ❍ ❍ ❍ 9. AdminSysUser: The user ID used when running the Administration Server. The user should exist in the Directory Server and have access permissions to use the Directory Server to perform user and group management tasks. For example, root. AdminName: The user name used to access to the Administration Server’s administration screens. For example: admin. AdminPassword: The password used to access to the Administration Server’s administration screens.
Installing Across Multiple Machines The following is an example of the template.
Installing Across Multiple Machines Using Silent Installation Silent installation is a less efficient way than templatized installation to install multiple instances of iPlanet Web Server because remote instances of the server are installed one by one rather than several at a time. You use silent installation to create a file of responses to the setup program’s prompts, then edit the file (install.inf) and use it to install future iPlanet Web Server installations.
Installing Across Multiple Machines The following is an example of an install.inf file. [General] FullMachineName= host1.iplanet.
Using Uninstall on Unix Table 2-2 Silent Installation Parameters Parameter Name Use ServerRoot The directory where you install the server. AdminPort The Administration Server port. HttpPort The port of the default iPlanet Web Server instance. HttpDocRoot The document root of the iPlanet Web Server instance. AdminSysUser The user ID used when running the Administration Server. AdminName The user name used to access to the Administration Server’s administration screens.
Using Uninstall on Unix 3. Select all subcomponents and press Return. The subcomponents are uninstalled and you return to the command prompt. NOTE The uninstall program does not remove every server file. For example, it does not remove keys and certificates, configuration files, logs, ACL files or the document root. If you installed another 4.x server (for example, iPlanet Directory Server or Messaging Server) in the same directory as iPlanet Web Server, follow these steps when uninstalling: 1.
Chapter 3 Installing iPlanet Web Server, Enterprise Edition on Windows NT This chapter tells you how to install iPlanet Web Server on Windows NT. It contains the following sections: • Installing on Windows NT • Using Silent Installation • Using Uninstall on Windows NT Installing on Windows NT The following sections describe the installation of the iPlanet Web Server. Any errors that occur when the server starts are logged in the Event Viewer.
Installing on Windows NT • If you have previous versions of Netscape or iPlanet web servers installed, shut down the Administration Server and Enterprise Server instances before installing iPlanet Web Server 6.0. • If you install both iPlanet Directory or Messaging Server and iPlanet Web Server on the same machine, during the web server installation when you are asked which version of libraries to install, always select those which have the most recent release dates, except for system32\libplc.dll.
Installing on Windows NT 4. The Select Installation Type screen appears. Choose the kind of installation you want: Express, Typical or Custom. Express installation is for users who have little experience or are evaluating the product. It makes assumptions about such things as port number and which components to install. This option is not recommended if you are using your server in a production environment. Typical and Custom installation give you more options, and for this release, do the same thing.
Installing on Windows NT 5. The Location of Installation dialog box appears. The default location for the server files is C:\iplanet\servers, where C: is the letter of the drive on which you are installing the server. If you want to install iPlanet Web Server in a non-default location, use Browse to navigate to the folder you want, or type the name in the field. If you choose a folder that does not exist, the installation program asks if you want to create the folder. Click Next. 6.
Installing on Windows NT Server Core. Install this subcomponent to install the Administration Server and the first instance of iPlanet Web Server. Java Runtime Environment. If you are planning to use the Administration Server and/or Java and servlets support, you must have a JRE or a JDK. You can install the supplied JRE subcomponent or use a JDK already installed on your system. If you want to use your own JDK, you’ll need to supply the path to it later in the installation.
Installing on Windows NT 10. The Default Web Server dialog box appears. A default instance of iPlanet Web Server is installed automatically. Type a port number for the default instance of your iPlanet Web Server. This port should be different than the Administration Server port. 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 computer is called www.iplanet.
Using Silent Installation NOTE You should not cancel the installation process while the files are being copied. If you do, you will have a partial installation you need to clean up. If an uninstaller for iPlanet Web Server exists, use it to uninstall the portion of iPlanet Web Server you installed. If the uninstaller does not exist, manually delete all the files that are in the server root. 13. Click Finish. 14. Restart your machine or use the Services Control Panel to start the iPlanet Web Server. 15.
Using Silent Installation Because iPlanet Web Server, Enterprise Edition is downloaded as a self-extracting .exe file, you must first extract the files before running setup.exe. To extract the files, follow these steps: 1. Double-click the self-extracting .exe file to start the installer. 2. When you launch the installer, it unpacks the files to your TEMP directory. Without exiting the installer, go to the TEMP directory and copy the installation files to another location. 3.
Using Silent Installation The following is an example of an install.inf file. [General] Components=svrcore,WebServer ServerRoot=D:\iplanet\Servers [WebServer] Components=NESCore,JRE,Java,Cleanup AdminPort=8888 HttpPort=80 HttpDocRoot=D:\iplanet\Servers\docs AdminName=admin AdminPassword=admin [Java] JRE_DIR=D:/iplanet/servers/bin/https/jre [Cleanup] Archive=cleanup.zip The following table shows some useful install.inf parameters to edit.
Using Uninstall on Windows NT Using Uninstall on Windows NT You can remove the iPlanet Web Server from your computer by using the uninstall application. The uninstall application determines which servers are installed on your machine and allows you to choose which of those servers you want to delete. CAUTION Though you can select individual subcomponents to uninstall, it is not recommended.
Using Uninstall on Windows NT NOTE The uninstall program does not remove every server file. For example, it does not remove keys and certificates, configuration files, logs, ACL files or the document root. If you install a 4.x server (for example, iPlanet Directory Server or Messaging Server) on the same machine as iPlanet Web Server, you should have no problems uninstalling any server if you install the servers in the same directory.
Using Uninstall on Windows NT 52 iPlanet Web Server, Enterprise Edition Installation and Migration Guide • May 2001
Chapter 4 Migrating Your Web Server You can migrate the following iPlanet Web Server 4.x information to work with iPlanet Web Server 6.
iPlanet Web Server 6.0 Changes When you migrate information from iPlanet Web Server 4.x to iPlanet Web Server 6.0, the changes are made in the following areas: • Configuration Files • Java Server Pages • Java Servlets • Java Configuration Files • Simple Session Manager • Virtual Servers Configuration Files Certain directives found in the iPlanet Web Server 4.x magnus.conf file are now located in the iPlanet Web Server 6.0 server.xml file.
Any JSPs you have written in 0.92 will still work on iPlanet Web Server 6.0 as long as they are in a designated legacy directory. To designate a directory as a legacy directory, access the Class Manager, click the Services tab, and click Legacy JSP Directory. Use this page to designate your legacy directories. JSPs written in JSP 1.1 that are part of a web application can reside in any directory that the server can serve from. JSP 1.1 samples are in server_root/plugins/samples/servlets/jsp.10.
The settings for virtual servers are stored in the server.xml file, found in the server_root/server_ID/config directory. See the iPlanet Web Server Administration Guide for more information about virtual servers. Obsolete Features The following iPlanet Web Server 4.x features are not supported in iPlanet Web Server 6.0: • WAI • Web Publishing • Server Side JavaScript (SSJS)/LiveWire Data and settings are not migrated for these features.
Symbolic Links in Configuration Files (Unix and Linux) Symbolic or relative links in server configuration files may cause problems when upgrading. Make sure that server configuration files that contain absolute references to files under the server root always reference the path to the server root in the same way. Preferably, these links should not transverse any symbolic links. Migrating Settings and Data CAUTION Shut down all server instances before migrating. To migrate settings and data from a 4.
❍ Search Collections ❍ Search Pattern Files ❍ Keys and Certificates For more information, see The Migration Parameters Page in the online help 6. Click Migrate. The Migrate Server_name page appears. It shows the results of the migration, including the parameters successfully migrated and the parameters that you need to migrate manually. It also shows any features of your 4.x server that are not supported in 6.0. 7.
Migrating Virtual Servers iPlanet Web Server 4.x provided two methods for creating hardware virtual servers: the object method and the virtual method. How hardware virtual server information is migrated depends upon which method you used: • If your iPlanet Web Server 4.x hardware virtual servers were created using the object method, these hardware virtual server settings are migrated from the 4.x obj.conf file to the 6.0 server.xml file. • If your iPlanet Web Server 4.
If you choose to use your old document root, the search collections you migrated work automatically. If you choose to use a new document root instead of your old one, you may need to recreate some of your collections before they will work. Migrating Search Pattern Files You have the option of migrating the search pattern files. You should only do this if you have customized the default pattern files.
NOTE When you install the Java subcomponent, the configuration files that are installed include a set of files that end in .default (for example, rules.properties.default). These files contain the default values for the Java configuration files. During migration, the Java configuration files are not changed from the previous version. If you want to update the old files to the new settings, refer to the .default files. You can also refer to the .
iPlanet Web Server, Enterprise Edition Installation and Migration Guide • May 2001
Index SYMBOLS D .default files, 54, 61 .
preparation for, 11 subcomponents, 44 Unix, 23 express, 30 typical or custom, 26 uninstall, 39 user account needed for, 23 Windows NT, 41 uninstall, 50 IWSSessionManager, 55 applications, 60 certificates, 59 overview, 53 search, 59, 60 settings and data, 57 users and groups, 58 virtual servers, 55, 59 web server changes, 54 MMapSessionManager, 55 N J Java applets, migrating, 61 Java configuration files, 54 Java Server Pages, migrating from 4.
S search, migrating, 59, 60 server name aliases, 14 changing, 14 CNAME and, 14 server user account, 15 servers, removing, 39, 50 servlets, migrating, 55, 60 silent installation, 32, 37, 47 Simple Session Manager, 55 software requirements, 12 start script, and migrating, 56 stop script, and migrating, 56 subcomponents, 27, 44 Sun Solaris, version, 12 supported platforms, 12 symbolic links, 57 users and groups, migrating, 58 V virtual servers, migrating, 55, 59 W web.xml, 54 web-apps.
iPlanet Web Server, Enterprise Edition Installation and Migration Guide • May 2001
