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
The topics in this section describe the installation of iPlanet Web Server on Unix platforms.
|
Caution
|
You must install your version 6.0 servers in a server root directory separate from the server root directory that contains previous versions of the web server.
|
Logging In as the Correct User
Before you install iPlanet Web Server, you must log in as root, unless you meet the following conditions:
You plan to install the iPlanet Web Server on a port higher than 1024.
The location where you plan to install the server (the server root directory) is writable with your non-root login.
You are not planning to use Express installation.
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
Put the iPlanet Web Server, Enterprise Edition CD in the drive.
Change to the CD-ROM directory. For example:
- cd /cdrom
Change to the directory on the CD labeled with your Unix operating system. For example:
- cd solaris
Change to the installation directory. For example:
- cd entprise
Copy the tar file from the CD to your home directory or a temporary directory. For example:
- cp ee60sol.tar /tmp/iwsinstall
|
Note
|
Untarring the file will cause the permissions of the destination directory to be modified so that applications can no longer write files to it. To avoid this problem, untar the file in a directory where you can modify the permissions. For example, instead of /tmp, use a subdirectory under /tmp, for example, /tmp/iwsinstall.
|
- Copying the file may take a little time.
Change to the directory on your Unix machine where you copied the file. For example:
- cd /tmp/iwsinstall
Untar the file by typing tar -xvf filename.tar. For example:
- tar -xvf ee60sol.tar
- 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
Download the file from http://www.iplanet.com/downloads/download and save it in a temporary directory.
Change to the directory on your Unix machine where you copied the file. For example:
- cd /tmp/iwsinstall
Unpack the .gz file by typing gunzip filename.tar.gz. The file name is in the format:
- ee60platform.tar.gz
- For example:
- ee60sol.tar.gz.
Untar the unzipped file by typing tar -xvf filename.tar.
- 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 three files: LICENSE.txt, README.txt, setup, setup.inf, installWrapper, and template.inf.
|
Note
|
Untarring the file will cause the permissions of the destination directory to be modified so that applications can no longer write files to it. To avoid this problem, untar the file in a directory where you can modify the permissions. For example, instead of /tmp, use a subdirectory under /tmp, for example, /tmp/iwsinstall.
|
Running Setup
You run the setup program to install iPlanet Web Server.
During the installation process, you have the choice of three kinds of installation: Express, Typical, or Custom. Most users should choose Typical or Custom (they are identical). Typical or Custom gives you more flexibility in the components you can install and the settings you can configure.
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).
Press CTRL+C to cancel the installation program.
Enter comma-separated lists of numbers when you want to select multiple items (for example, 1, 2, 3).
|
Note
|
For Express installation, you must be logged in as root when running setup.
|
Typical or Custom Installation
Most users should install the Typical or Custom installation.
To run setup, follow these steps:
If you are not in the directory already, change to the directory where you unpacked the file.
Type ./setup to start the server installation.
- If you aren't logged in as the root user (superuser), or if you don't have sufficient write permissions, you'll get one or more error messages.
- A welcome screen appears.
Press Enter to continue with the installation.
Choose whether you accept the software license agreement by typing 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.txt that is in the same directory as the setup program.
Choose Typical or Custom.
- Press Enter.
Type a server root directory or accept the default (/usr/iplanet/servers).
- This directory is where the server files and directory structure will be installed.
- You need to run the server as a user that has write access to this directory, for example, the directory owner.
Choose all components.
- Press Enter.
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.
- By default, all subcomponents are installed.
- If you are migrating from iPlanet Web Server 4.x, when you install subcomponents, you must install all the subcomponents you installed for 4.x, otherwise they are not migrated properly and may not work. You can install additional subcomponents as well.
- The subcomponents you can choose to install are described in the following numbered sections.
|
Caution
|
You must install the Server Core and Java Support subcomponents the first time you install iPlanet Web Server. If you install additional subcomponents later, you are not required to reinstall the Core subcomponent.
|
- Server Core. Installs 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 Java Runtime Environment (JRE) or a Java Developer's Kit (JDK), also known as Java 2 Software Development Kit (SDK). You can install the provided JRE, or supply your own JDK. For more information, see Installing a Java Developer's Kit.
|
Caution
|
If you are using HP-UX, even if you are not installing Java you must install the JRE or supply a JRE or JDK. Without one or the other, the HP-UX iPlanet Web Server won't run.
|
- 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. As the server administrator, you can create a customized text search interface tailored to your user community.
- SNMP Support. Install this subcomponent if you are planning to use SNMP to monitor your servers.
Enter the machine name or accept the default.
Enter the Unix user and group names to use when running the default instance of iPlanet Web Server.
- The default user and group is nobody. If you're planning to use SNMP, the user name must be root.
|
Note
|
HP-UX has a UID of -2 for nobody. If you have to run the server as nobody on this platform, change the UID of nobody to a positive unique number less than the UID max.
|
Enter the Unix user name to use when running the Administration Server.
- In most cases this user is root.
Enter the Administration Server user name and password to use for authentication. You are asked to enter your password twice.
Type the Administration Server port number or accept the default of 8888.
- Make sure you remember the port number for the Administration Server.
- For the most flexibility, choose a port number above 1024. If you want to use a port number lower than 1024 for your Administration Server, you must be logged on as root to start the server. Do not use a port that is already in use.
- This iPlanet Web Server Administration Server is not the same as the Netscape Console, or the Administration Server shipped with other iPlanet/Netscape servers.
- For more information on ports, see Choosing Unique Port Numbers.
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.com and you choose port 9753, your server's URL will be
http://www.iplanet.com:9753/
- For more information on ports, see Choosing Unique Port Numbers.
Type the root directory where your server's content files (the images, HTML documents and data you want to present to users accessing the server) will reside. The default is server_root/docs.
If you want to use your own JDK, enter Yes.
- If you are installing Java 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. For more information, see Installing a Java Developer's Kit.
If you are installing Java support, and you either did not choose to install the provided JRE, or you chose to use your own JDK, enter the absolute path to the directory where you installed the JDK on your system.
- The JDK must already exist in the specified directory.
- If the JDK libraries and CLASSPATH are stored in the default directories below the JDK directory (/jre/lib and /lib, respectively), press Enter at the JDK LIBPATH and JDK CLASSPATH prompts. If the libraries and CLASSPATH are stored in a different place on your system, enter the pathnames. On most systems you will not have to enter pathnames at these prompts.
After the installation program extracts and installs the iPlanet Web Server components, press Enter.
Go to the https-admserv directory under your server root directory (for example /usr/iplanet/servers) and start the 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.
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. It makes assumptions about such things as port number and which components to install.
The following table lists the assumptions made by the Express installation. If you would like to use different installation settings, use Typical or Custom installation.
Table 2-1 Express installation settings
|
Installation Setting
|
Value
|
|
administration port
|
8888
|
|
administration URL
|
http://machine name:administration port
|
|
HTTP port number
|
80
|
|
document root
|
server_root/doc
|
|
Unix user to run server
|
root
|
|
LDAP users and groups
|
not using
|
|
JDK
|
none
|
|
JRE
|
default JRE shipped with iPlanet Web Server
|
|
subcomponents
|
All default subcomponents installed
|
After installing, you can configure the server to use LDAP users and groups, and to use a JDK. For more information on how to make these changes, see the iPlanet Web Server Administrator's Guide.
|
Caution
|
You must log in as root to use Express installation.
|
To run setup, follow these steps:
If you are not in the directory already, change to the directory where you unpacked the file.
Type ./setup to start the server installation.
- A welcome screen appears.
Press Enter to continue with the installation.
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.txt that is in the same directory as the setup program
Choose Express and press Enter.
Type a server root directory or accept the default (/usr/iplanet/servers).
- This directory is where the server files and directory structure will be installed. root must have write access to this directory.
Choose all components.
- Press Enter.
Enter the Unix user and group names to use when running the default instance of iPlanet Web Server.
- For Express installation, this user must be root. The group must be the group to which root belongs.
Enter the Unix user name to use when running the Administration Server.
- In most cases, this user is root.
Enter the Administration Server user name and password to use for authentication. You are asked to enter your password twice.
- If you are using a iPlanet Directory Server, you must make sure that the Administration Server user exists in the Directory Server, and that it has access permissions to the Directory Server to perform user and group management tasks.
After the installation program extracts and installs the iPlanet Web Server components, press Enter.
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.
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.
Installing Across Multiple Machines
You can install iPlanet Web Server, Enterprise Edition on multiple machines using two different methods: templatized installation and silent installation.
Templatized installation is executed from your local machine, where you run the installation program silently across multiple remote machines at once.
Silent installation requires that you first install the web server on a local machine, then edit the resulting log file, install.inf, to correspond to the remote machines. With silent installation, you must install the remote instances one by one.
Both methods are described in this section.
Using Templatized Installation
To use templatized installation, enter the installation settings for each remote machine in a template file called template.inf. You can then use the template to install the web server on multiple machines from a single session on your local machine.
The template.inf file is found in the same directory as the setup program.
To run templatized installation, perform the following steps:
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
In the /etc/hosts.equiv 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
- For example, if the remote machine name is host1 on the domain dogs, enter the following information:
- host1.dogs.com
In the /.rhosts directory of each remote machine where you will install the web server, create an entry for your local machine using the format
- local_machine_name username
- For example, if the local machine name is chewbacca on the domain dogs and you are logged in as root, enter the following information:
- chewbacca.dogs.com root
In the /etc/hosts.equiv directory of each remote machine where you will install the web server, create an entry for your local machine using the format
- local_machine_name
- For example, if the local machine name is chewbacca on the domain dogs, enter the following information:
- chewbacca.dogs.com
Create a setup directory on your local machine with a link to server root
- ln -s server_root/ setup-directory
Change to the directory where setup resides.
Open the template.inf file.
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.
SetUpLocation: the location of the setup program used by the template file.
- For each host, enter the following:
[hostname]: the name of the machine where the web server will be installed by the template. .
InstallType: the type of installation to run: express [1], typical [2], or custom [3].
SuiteSpotUserID: The user ID used when running the default instance of the iPlanet Web Server.
SuiteSpotGroup: The group the user running the default instance of the iPlanet Web Server belongs to.
ServerRoot: the directory where your server will be installed. For example:
- /usr/iplanet/servers
JRE_DIR: If you are installing the JRE shipped with the iPlanet Web Server, the directory where it is installed. For example:
- /usr/iplanet/servers/bin/https/jre
HttpDocRoot: The document root of the iPlanet Web Server instance. For example:
- /usr/iplanet/servers/docs
- For the core server, enter the following:
Reinstall: enter True if you are reinstalling this version of iPlanet Web Server. Otherwise, enter False.
AdminPort: enter the port number for the Administration Server.
HttpPort: The port of the default iPlanet Web Server instance.
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. For example: admin.
Run the installation wrapper by typing the following command at the command prompt:
- ./installWrapper -f template.inf
The following is an example of the template.inf file:
|
[ MachineName]
HostNames =host1,host2
Components=Nescore,jre,java,snmp,search
SetUpLocation=/usr/iplanet/downloads
[host1]
InstallType= 2
SuiteSpotUserID=
SuitespotGroup=
SecurityCheck= False
RequireDomain= False
InstallWhich= 1
ServerRoot=/usr/iplanet/servers
HttpDocRoot=
JRE_DIR=
[host2]
InstallType= 2
SuiteSpotUserID=
SuitespotGroup=
SecurityCheck= False
RequireDomain= False
InstallWhich= 1
ServerRoot=/usr/iplanet/servers
JRE_DIR=
HttpDocRoot=/usr/iplanet/servers/docs
[core]
Reinstall= False
AdminPort=8888
HttpPort=80
AdminSysUser=
AdminName=
AdminPassword=
CompVersions= 2:2:1:2:2:1:1:2:
[cleanup]
Archive= cleanup.zip
|
|
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. With silent installation, you must first install iPlanet Web Server on your local machine, then edit install.inf to correspond to the remote machines where you'll install additional instances of the server. If you are installing iPlanet Web Server on a number of remote machines, it is recommended that you use templatized installation instead.
Silent installation works best when you use the Typical installation and your installations are all similar.
|
Caution
|
The install.inf file contains the password used to log on to the Administration Server. The password is not encrypted; it is in plain text. If you use silent installation, be sure and delete the install.inf file once you are through with it.
|
To use silent installation, follow these steps:
Run setup with the -k option, which creates a file called install.inf that contains all your responses to the installer's prompts. At the command prompt, type:
- ./setup -k
Answer the installer prompts and install iPlanet Web Server.
When the server is installed, go to the server_root/setup directory, where you'll find the install.inf file.
Copy the install.inf file to the directory where you will run setup to install your next iPlanet Web Serve.
Edit the values in the install.inf file to match the values of the next server you want to install.
- For example, change the machine name, port number, installation directory, etc.
Run setup using the install.inf file for input. For example:
- ./setup -s -f install.inf
The server is installed.
The following is an example of an install.inf file.
|
[General]
FullMachineName= host1.iplanet.com
SuiteSpotUserID= root
SuitespotGroup= root
SecurityCheck= False
RequireDomain= False
ServerRoot= /usr/iplanet/servers
Components= WebServer
[WebServer]
Reinstall= False
AdminPort= 8888
HttpPort= 80
HttpDocRoot= /usr/iplanet/servers/docs
AdminSysUser= root
AdminName= admin
AdminPassword= password
JRE_DIR= /usr/iplanet/servers/bin/https/jre
USE_JDK= No
CompVersions= 2:2:1:2:0:0:0:0:0:
Components= Nescore,jre,java,cleanup
[cleanup]
Archive= cleanup.zip
|
|
The following table shows some useful install.inf parameters to edit. For best results, do not edit any parameters except those listed in the table.
Table 2-2 Silent Installation Parameters
|
Parameter Name
|
Use
|
|
FullMachineName
|
The machine name.
|
|
SuiteSpotUserID
|
The user ID used when running the default instance of the iPlanet Web Server.
|
|
SuiteSpotGroup
|
The group the user running the default instance of the iPlanet Web Server belongs to.
|
|
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.
|
|
AdminPassword
|
The password used to access to the Administration Server's administration screens.
|
|
JRE_Dir
|
If you are installing the JRE shipped with the iPlanet Web Server, the directory where it is installed.
|
|
USE_JDK
|
Yes and No indicate whether you are using a JDK.
|
|
JDK_DIR
|
The directory where your JDK is installed.
|
Using Uninstall on Unix
You can remove iPlanet Web Server from your computer by using the uninstall application.
|
Caution
|
Though you can select individual subcomponents to uninstall, it is not recommended. The uninstaller only removes the parts of the code pertaining to the selected subcomponent, but does not update configuration files. Your server may not run if you uninstall individual subcomponents.
|
To remove your iPlanet Web Server:
Go to your server root and type ./uninstall.
- A list of iPlanet servers currently installed in this location appears.
Find iPlanet Web Server in the list and type the number next to it at the prompt.
- Note that uninstalling iPlanet Web Server automatically uninstalls the Administration Server, since it is an instance of iPlanet Web Server.
- A list of installed iPlanet Web Server subcomponents appears.
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:
Copy the uninstall script (uninstall) to another file, for example, uninstslapd.
Use uninstall to uninstall iPlanet Web Server.
Rename uninstslapd to uninstall.
Use uninstall to uninstall Directory Server.
If you migrated from iPlanet Web Server 4.x to iPlanet Web Server 6.0, when you uninstall 4.x, the uninstaller does not delete the files that were used in 4.x but not in 6.0. You have to delete these files manually.