Oracle iPlanet Web Server 7.0.9 Installation and Migration Guide

ProcedureTo Install in Graphical Mode on UNIX and Linux

  1. Download the installer file for your platform to a temporary directory. The file format is:

    Oracle-iPlanet-Web-Server-7.0.9-platform.zip

  2. Unzip the server files. You will see the following:

    • Legal directory

    • README.txt

    • setup

    • WebServer directory

  3. Start the installation with the following command:

    ./setup

    The graphical installation wizard displays. General navigation is as follows:

    • Click Back to return to the previous screen.

    • Click Next to move to the next screen.

    • Click Cancel to cancel the installation.

    • Click Help to display documentation specific to the current screen.

  4. Specify the installation directory.

    The default is /opt/oracle/webserver7 for the root user and user-home/oracle/webserver7 for non-root users.

    Web Server components are installed in the directory specified. If the directory does not exist, you have the option to create it.

  5. Select the installation type, Express (the default) or Custom. For more information about each type, see Installation Types.

  6. Proceed based on installation type:

    • For Express installations, specify the user name (admin by default) and password for the Administration Server user, click Next, and go to Step 13 to finish the installation. Steps 9-13 pertain to Custom installations only. For more information about the default settings used for Express installations, see Express Installation.

    • For Custom installations, go to Step 7.

  7. Select the components to install.


    Note –

    Server Core and Administration Command Line Interface (and Server Core 64–bit Binaries, if applicable for your system) are selected by default. You can install the administration command-line interface without installing server core, but you cannot install server core without installing the administration command-line interface. For more information, see Web Server Components.


    • Server Core. Installs the core binaries needed to set up the Web Server environment.

    • Server Core 64-bit Binaries. (Solaris SPARC, AMD64 and Linux only) Installs the 64–bit binaries required for setting up the 64–bit runtime for the default Web Server instance. This option is selected by default and displays only if the system on which you are installing has 64-bit support. If this option is selected, the 64- and 32-bit binaries are installed. For more information about 64-bit support in Web Server 7.0, see 64-bit Support.

    • Administration Command Line Interface. Installs the command-line administration client used to manage and configure Web Server and its hosted applications from the command line. Specify Java configuration information as described in Step 8, and then go to Step 13 to finish the installation.

    • Sample Applications. Installs the sample applications that demonstrate Web Server features and functionality.

    For more information about each component, see Web Server Components.

  8. Specify Java configuration information.

    Choose to install the JDK bundled with Web Server 7.0 (the default) or specify the absolute path to an existing JDK.

  9. Specify configuration settings.

    Specify whether to configure the administration instance as the Administration Server (the default) or the Administration Node (as described in Server Core). For more information about these choices, see Web Server Components. For Custom installations performed as root, also specify whether the Web Server and its associated Administration Server should be started and stopped automatically on system startup and shutdown. The default is No (the option is not selected).

    • If you select Configure Administration Instance as Administration Server (the default), go to Step 11.

    • Enable SMF. Select this option to enable Service Management Facility in both Administration and default instance server. This flag is valid only for Solaris 10. For more information about Service Management Facility for Java Platform, see Integrating Service Management Facility for the Java Platform with Web Server in Oracle iPlanet Web Server 7.0.9 Administrator’s Guide

    • If you select Configure Administration Instance as Administration Node, specify the Administration Node settings listed below and then go to Step 13 to finish the installation:

      • Host Name. Specify the fully qualified domain name of the computer on which you are installing the Administration Node instance.

      • SSL Port. Specify the SSL port for the Administration Node instance or accept the default. The default is 8989 unless that port is unavailable, in which case this defaults to the next highest available port.

      • Runtime User ID. (UNIX, root) Specify the UNIX user name to use when running the Administration Server. For root installations, the default is root. For non-root installations, the default is the user name that you used at login.

      • Register Node with Remote Administration Server. Specify whether this Administration Node instance should be registered with the Administration Server instance at the time of installation (the default), or later (as described in Registering the Administration Node From the Command-Line). If registration is selected, specify the following settings and then go to Step 13 to finish the installation:


        Note –

        When registering an Administration Node with an Administration Server, ensure that the system date and time of the Administration Node is same as or later than that of the Administration Server.


        • Administration Server Host Name. Specify the fully qualified domain name of the remote host on which the Administration Server is installed.

        • Administration Server SSL Port. Specify the SSL port on which the remote Administration Server is listening. The default is 8989.

        • Administrator User Name. Specify the administrator user name used to log in to the remote Administration Server.

        • Administrator Password. Specify the administrator user password used to log in to the remote Administration Server.

  10. For Custom installations performed as root, specify whether the Web Server and its associated Administration Server should be started and stopped automatically on system startup and shutdown (the default is No). For Custom installations performed as non-root, go to Step 11.

  11. If configuring the administrations instance as the Administration Server, specify Administration Server settings.

    • Host Name. Specify the fully qualified domain name of the computer on which you are installing the Administration Server.

    • SSL Port. Specify the SSL port for the Administration Server or accept the default. The default is 8989 unless that port is unavailable, in which case this defaults to the next highest available port.

    • Non- SSL Port. Specify the non-SSL port for the Administration Server. The default is 8800 unless that port is unavailable, in which case this defaults to the next highest available port.


      Note –

      SSL port is default for Administration Server. However, you can also choose to use the Non-SSL port. When you choose to install through SSL port, use https:// to access the Administration Server.


    • Runtime User ID. (UNIX, root) Specify the UNIX user name to use when running the Administration Server. For root installations, the default is root. For non-root installations, the default is the user you logged in as to perform the installation.

    • Administrator User Name. Specify the Administration Server user name. The default is admin.

    • Administrator Password. Specify the Administration Server user password.

    • Retype Password. Retype the Administration Server user password.

  12. Specify Web Server settings.

    • Server Name. Specify the fully qualified domain name of the computer on which you are installing the default Web Server instance.

    • HTTP Port. Default value depends upon the runtime user ID of the Administration Server instance. If the Administration Server instance's runtime user ID is non-root, the default is 8080. If the Administration Server instance's runtime user ID is root, the default is 80.


      Note –

      root user can bind to any port in Solaris 10 OS. However, on other version of Solaris root only can bind to ports lesser than 1024. Solaris 10 provides an alternative way for non-root users to bind to ports less then 1024. On Solaris 10, you need to provide net_privaddr privileges to a non-root user and start the server. For example, you can start the server as webservd. Log in as root and execute the following command: /usr/sbin/usermod -K defaultpriv=basic,net_privaddr webservd. To start the server as another user, you need to change the user name in the above command. For more information on usermod see, http://docs.sun.com/app/docs/doc/816-5166/6mbb1kqk6?a=view. For more information on privileges see, http://docs.sun.com/app/docs/doc/816-5175/6mbba7f30?a=view.


    • Runtime User ID. (root only) If the Administration Server instance's runtime user ID is non-root, the default is the same as Administration Server instance's runtime user ID. If the Administration Server instance's runtime user ID is root, the default is webservd.

    • Enable a 64–bit runtime. Specify whether the 64–bit runtime should be enabled for the default Web Server instance. The default is No (the option is not selected).

    • Create a document Root. Specify whether the default document root should be created during installation. The default is install-dir/https-server_name/docs. The server's content files reside in this directory.

    • Use the following directory as document Root. Specify a document root other than the default.

  13. On the Ready to Install screen, click Install Now to install the Web Server software.

    A progress bar displays status. Click Stop at any time to stop the installation.

    When the installation process is complete, a screen indicates whether installation succeeded or failed, and provides information about using the Administration Server and reviewing the installation log file. Make note of this information for future reference.