Sun ONE logo     Previous      Contents      Index      Next     
Sun ONE Web Proxy Server 3.6 SP2 Installation Guide - NT Version



Chapter 2   Installing iPlanet Web Proxy Server

This chapter tells you how to install your iPlanet Web Proxy Server. It also explains how to migrate from a previous version of the proxy server and to install multiple proxy servers.

Installing iPlanet Web Proxy Server

After you've installed the required software, you can install iPlanet Web Proxy Server. You can install a new proxy, replace an existing proxy server, or install more than one proxy.



Note

While it is possible to install your proxy server on the same machine as another Sun ONE server, it is not recommended that you do so. Running two or more Sun ONE servers on the same machine will cause a significant impact on the servers' performance.



If you're already running a proxy server, you must install the new proxy server to a different port. For example, if you are replacing a proxy that listens to port 8080, you might first install the new proxy server on port 8081, assuming that port is available. After the new proxy server is properly configured, shut down the old proxy server and then change the new proxy to use port 8080.

  1. Download the Sun ONE Web Proxy Server 3.6 SP2 software from the following location and save it in a temporary directory:
  2. http://wwws.sun.com/software/products/web_proxy/home_web_proxy.html

  3. Change to the directory where you downloaded the file.
  4. Double-click the p36diu.exe file
  5. or

    Choose Start | Run, and type the full path to the p36diu.exe  file, and press Enter.

    The Installation Wizard takes you through the installation process. During this process you need to specify the following items:



    Note

    If you already have a SuiteSpot 3.x server installed on your machine, the installation wizard will not prompt you for the destination directory, directory service, administrator's username and password, or administration server port.



    • Destination Directory—This is the directory into which the proxy server will be installed. You can either choose the default directory, C:\Netscape\SuiteSpot, or browse for another directory.
    • Directory Service—This is the service you will use to store user and group information. You can use either an LDAP-based service, such as iPlanet Directory Server, or you can use the local directory service. If you choose an LDAP-based service, you need to enter the directory server's name, its port, and its Base Distinguished Name. (The Base Distinguished Name is the directory under which all relevant user and group information is stored. It has the form o=organization, c=country. For instance, o=iPlanet, c=US.)
    • Administrator's Username and Password—These are the username and password you will need to access the administration server.
    • Administration Server Port—This is the port address that the administration server will use.
    • Cache Partition Root—This is the location of your proxy server's cache. You can choose either the default directory, C:\Netscape\SuiteSpot\Proxy, or browse for another directory.
    • Proxy Server Port—This is the port address that the proxy server will use. The standard proxy port is 8080.

Reinstalling on Windows

To install the binary, proceed as follows:

  1. Backup all files under <server-root>(normally c:\WINNT\Netscape\SuitSpot).
  2. Under this directory you should see the following:

    • adminacl -> directory
    • admin-serv -> directory
    • alias -> directory
    • bin -> directory
    • extras -> directory
    • httpacl -> directory
    • include -> directory
    • install -> directory
    • lib -> directory
    • manual -> directory
    • nsapi -> directory
    • ns-icons -> directory
    • plugins -> directory
    • proxy -> directory
    • userdb -> directory
    • proxy- <machine-name> ->directory
    • admserv -> file
    • license.txt -> file
    • Nyr -> file
    • Proxy.txt -> file
    • uninst.exe -> uninstall binary

    This will create a copy of all configuration files, proxy instances, etc.

  3. Stop the Proxy and Admin Server. Uninstall the Proxy, using the binary <server-root>\uninst.exe. Uninstall the Admin Server.
  4. Remove everything under <server root> manually. Take care to remove only the directories and files concerning the Proxy (in case the customer is running additional Netscape applications). Refer to step (1) for more information.
  5. Reinstall the Proxy in the same directory as the old Proxy, using the binary provided. Enter the same information as in the previous installation (the same admin password, admin port, proxy port, and binding information to the LDAP directory server, if applicable).
  6. After installation from a DOS prompt, stop the Proxy and Admin Server. Copy all the configuration files from the back-up Proxy copy into the correct location (admin config files, proxy config files, and .acl  files). This process can be cumbersome, depending on the customer configuration. Not all the files shown below must be copied (files to be copied depend on the customer configuration):
  7. adminacl

    ->

    Admin acl files

    admin-serv \config

    ->

    Admin config files

    httpacl

    ->

    Proxy acls

    proxy-"name machine"\config\

    ->

    Proxy config files (if there is more instances process must be repeated with each of them)

    proxy\cache

    ->

    Cache of proxy

    userdb

    ->

    If using local database instead of LDAP directory server

  8. Start the Admin Server, then start the Proxy Server.

Migrating from a Previous Version of the Proxy Server

To migrate the proxy server data files from Netscape Proxy Server 3.5x to iPlanet Web Proxy Server 3.6 or higher, complete the following steps:

  • Stop the current version of proxy server. To do so:
    • stop all instances of Netscape Proxy Server 3.5x and SOCKS servers
    • stop the Administration Server

  • Copy the proxy directory to a backup directory of your choice.


  • Note

    If you have configured the proxy server so that the data files aren't stored in their default location, you should save the data files separately.



  • Uninstall the current version of proxy server.
  • Install iPlanet Web Proxy Server 3.6 in a directory with the same name as the previous version of the proxy server.
  • Create the same number of proxy instances that you used before, with exactly the same `Server Identifier' (in the Server Installation window) for each. If necessary, remove the default proxy instance that is automatically created during the installation process.
  • Stop all proxy servers instances and the Administration Server.
  • Restore all configuration files from backup directories to the new proxy directories either by manually copying them or by using the perl script \extras\cpProxyData.pl (this recursively restores your directories).


  • Note

    If the configuration files are not in their default location, you will have to update the list of files given below and the list of copy commands in the \extras\cpProxyData.pl script.



The following directories need to be restored:

  • Directories common to all proxy instances:
    • <backup-directory>\adminacl
    • <backup-directory>\admin-serv\config
    • <backup-directory>\admin-serv\logs
    • <backup-directory>\alias
    • <backup-directory>\httpacl
    • <backup-directory>\plugins
    • <backup-directory>\userdb
    • <backup-directory>\proxy\cache
    • <backup-directory>\cache (if it exists)

  • For each instance of proxy server, the directory containing the configuration files specific to that instance:
  • <backup-directory>\<proxy_name>

    For example, if the configuration files are in the default location, you can restore the files using the \netscape\suitespot\extras\cpProxyData.pl script, as follows :

    1. cd <proxy_dir>
    2. Copy all common configuration files as follows:
    3. .\install\perl.exe .\extras\cpProxyData.pl -s <backup-directory> -d <proxy_dir> -c

    4. For each proxy server instance, copy all specific configuration files as follows:
    5. .\install\perl.exe .\extras\cpProxyData.pl -s <backup-directory> -d <proxy_dir> -i <proxy_name>

  • Restart the Administration Server and the Proxy Servers instances.
  • The Administration Server will warn you that configuration files have been updated manually and that you should load the last updates. To load the updates, do the following:
    1. Click Apply in the Administration Server window.
    2. If the "Save and Apply" dialog box is displayed, click Undo.
    3. Click Apply again.
    4. Click "Load Configuration Files" in the "Apply changes" dialog box.

    Although the backup directory is not needed any more, you are recommended to retain it in case you require the configuration information in future.

Installing Multiple Proxy Servers

Once you have one proxy server running on your computer, you can install another proxy server without going through the installation program.

Each proxy server you have installed can run on any TCP/IP port on your system, but you cannot run two servers on the same port at the same time. Your proxy server software license allows you to have as many proxy servers as you want on one computer. With multiple servers on your computer, you will see several subdirectories in your server root directory; each of these servers can be managed from the Server Administration page.

To install another proxy server,

  1. On the Server Administration page, click the "Create New iPlanet Web Proxy Server 3.6" link. The iPlanet Web Proxy Server Installation form appears.
  2. Enter values for the following:
    • Server name—Type the fully qualified domain name for your server. If you are installing a second server for a different domain, enter the domain here.
    • Server port—Type the port number to which you want this server to listen.
    • Server identifier—Type the server identification the administration server will use for your server. This is the name that appears in the Server Selector and becomes part of the name for the main directory for this new server. All server instances on the same machine must have a unique server identifier.


    • Note

      The name you specify for the Server Identifier can contain only letters, digits, hyphens and underscores, and must begin with a letter.



    • DNS behavior—Select whether you want the proxy server always to resolve host names, to resolve them for access control, or never to resolve them.
    • Log format—Select whether you want to use common, extended, or extended-2 log format. For more information on these formats, see the Administrator's Guide.
    • Proxied protocols—Select which protocols (HTTP, FTP, Gopher) your proxy will service.
    • SSL tunneled protocols—Select which secure protocols (HTTPS, NNTP) your proxy server will tunnel.
    • Caching behavior—Specify whether caching is enabled for your proxy server. If you do enable caching, specify the directory where cached files will be stored. For more information on caching, see the Administrator's Guide.
    • Cache size—Select the size of your cache. For more information on cache size, see the Administrator's Guide.
    • Cache sections—Select the number of sections that will be in your cache. Fore more information on cache sections, see the Administrator's Guide.
    • Cache directories per section—Select the number of subdirectories that will be within each section in your cache. For more information on cache directories, see the Administrator's Guide.
    • HTTP caching behavior—Select whether you want your proxy server to cache HTTP documents. If so, specify the refresh and expiration policies. For more information on caching HTTP, see the Administrator's Guide.
    • FTP caching behavior—Select whether you want your proxy server to cache FTP documents. If so, specify the FTP refresh policy. For more information on caching FTP, see the Administrator's Guide.
    • Gopher caching behavior—Select whether you want your proxy server to cache Gopher documents. If so, specify the Gopher refresh policy. For more information on caching Gopher, see the Administrator's Guide.

  3. Click OK.


Previous      Contents      Index      Next     
Copyright 2003 Sun Microsystems, Inc. All rights reserved.