Previous     Contents     Index     DocHome     Next     
iPlanet Application Server Installation Guide



Chapter 4   Advanced Installations for Solaris


This chapter describes the advanced installation options to install and configure iPlanetTM Application Server for the SolarisTM platform. It contains the following information:

Check the Release Notes for any updates to these instructions at:

http://docs.iplanet.com/docs/manuals/ias.html


Note Before you start iPlanet Application Server installation, make sure that you are running a Solaris 2.6 or Solaris 8 system.




What You're Installing


The software you're installing for iPlanet Application Server, actually consists of a group or stack of components, including:

  • iPlanet Directory Server, Enterprise Edition 5.0 SP1

  • iPlanet Administration Console, which has its own Administration Server

  • iPlanet Application Server and its subcomponents:

    • iPlanet Application Server Web Connector Plug-in Component

    • iPlanet Application Server Core Server Component

    • iPlanet Application Server Administration Tool

    • iPlanet Application Server Deployment Tool

    • PointBase Database Server.

      Installs the required PointBase packages when you select the Application Server core components.

See Chapter 1 "Getting Started," for an overview of iPlanet Application Server features and components.


Note In addition to these components, Custom Installation allows you to install database clients, proprietary Type 2 iPlanet Application Server Database Drivers, and Type 3 JDBC drivers.




Using the Solaris Custom Installer


This section explains how to install iPlanet Application Server on the Solaris platform using the custom set up procedure. It includes the following topics:


Starting Solaris Installation

Before you begin installing iPlanet Application Server, meet the Minimum System Requirements and Prerequisites for Installation, as given in "Chapter 2 "Preparing to Install".


Note A Web server and Web browser must be installed and running before you begin iPlanet Application Server installation. You can download iPlanet Web Server, Enterprise Edition 4.1 SP7 from: http://www.iplanet.com/downloads/download/


When installing iPlanet Application Server on the Solaris platform, use the following keystroke commands:

  • Enter key; accepts that screen's default setting and goes to next screen.

  • CTL-B; goes back to the previous screen within an installation section, as defined by the title at the top of the screen. You cannot use CTL+B to go back to a screen in a different section.

  • CTL-C; exits the installation. Once exited, the installer starts over at the beginning.

  • Comma (,) delimited list; specifies more than one item.


To Begin the Custom Installation

  1. Login as root.

  2. Insert the product CD in the CD-ROM drive.

  3. Mount the CD-ROM on, for example, /cdrom/cdrom0

  4. At the shell prompt, run the following command:

    /cdrom/cdrom0/solaris/iAS

    If you have downloaded the tar file, untar the file and type:

    ./setup

    The Tips screen appears.

  5. Press Enter.

    The License Agreement screen appears.

  6. You must enter Y to continue.

  7. Press enter to accept the default; install the iPlanet Servers group unless you select the iPlanet Console instead.

    If you select iPlanet Console (formerly Netscape Console), the iPlanet Administration Console is installed as a standalone application, which can be used from any machine to administer your iPlanet Application Server configuration.

  8. Enter 3 to select the Custom Installation type.

  9. Enter the installation directory. The default iPlanet Application Server installation directory location is: /usr/iplanet/ias6

    If you enter a different location, do not include spaces in the path name. All components are installed in this base directory


    Note You must have at least 400 MB free space available on this drive to install iPlanet Application Server.


  10. On the iPlanet Server Products Components panel, the default choice of [All] indicates which components are installed during a full installation of iPlanet Application Server. You may choose to:

    • Keep the default selection (All).

      If you choose [All], the sub-components of the selected components are listed in subsequent screens, so that you can further refine your choices.

    • Enter 1,3,4 to not install the Directory Suite component if you already have a directory service available.


      Note The Directory Suite Component should not be selected if you intend to install multiple instances of iPlanet Application Server. See "Installing Multiple Instances on Solaris" for more information.


    • Enter 1,2,4 to not install the Administration Services component if you don't want to install iPlanet Administration Console.

    • Enter 4 to install only the iPlanet Application Server.

      The components selected here have multiple sub-components. Press Enter in each screen to accept the default sub-components.

  11. Press Enter in each subsequent screen to accept the default sub-components.

  12. Press Enter to accept the default name of the computer you are installing on.

  13. Enter the system user and system group names.



    You should have already set up this user and group prior to running the installation program. Typically, this user and group should be the same as that which installed the web server.

    Specify a user that has no privileges elsewhere on the system to avoid access to restricted servers, such as the configuration Directory Server.

Within the iPlanet Application Server installation there are several panels having to do with installing and configuring the Directory Suite.


Note
  • The Directory Server Component should not be selected if you intend to install multiple instances of iPlanet Application Server. For more information, see "Installing Multiple Instances on Solaris".

  • If you don't install Directory Server with iPlanet Application Server, you must designate an existing Directory Server as the configuration directory. The Directory Server you designate as the configuration directory must contain the data tree: o=NetscapeRoot.



To Configure the Directory Server

The Custom Installation Wizard panels set up the following:

  • Directory Server

  • Registers the Directory Server's data tree by indicating what the Directory Server stores:

    • Configuration data

    • Directory data

  • Sets up following administrators:

    • Configuration Data Administrator

    • Directory Data Administrator, known as Directory Manager

  • Records general settings for the Directory server's

    • LDAP communication port

    • Local host machine

    • Data Tree Root Suffix for the iPlanet Application Server you're installing

  • Sets Administrative Domain boundaries for the Directory Server
    Note For information about installing the Directory Server, see the iPlanet Directory Server Installation Guide at:

    http://docs.iplanet.com/


  • Press Enter to accept the default and register this Directory Server as the configuration Directory Server.


    If you are not installing the configuration Directory Server included in this installation, specify an existing Directory Server and provide its fully qualified domain name (hostname.domain.com), and port number.


    Tip The Configuration Directory Server is the part of the Directory Server used to store configuration information. The Directory Server also stores directory data.


  • Press Enter to accept this Directory Server instance as the general directory data storage server.

    If you have an existing Directory Server already installed on your system for this purpose, specify it. You will have to provide the fully qualified domain name, port number, the data information tree suffix, and the user directory admin (typically cn=Directory Manager) and password.

  • Press Enter to accept the default directory server port number of 389.

    If you are not logged in as root, the default value is a random number generated by the installer, which is greater than 1024.

  • Press Enter to set the unique identifier for the Directory Server by default to the name of the computer it's being installed on.

    To enter a different name, type in the name and press Enter.

  • Assign the Administrator ID and password for the Configuration Directory Server.



    • Press Enter to accept default username as admin, or type in a username and press Enter.

    • Enter a password; it can contain letters and numbers.


      Note Record and keep the Configuration Directory Administrator ID and password for future reference. They are required to login to the iPlanet Administration Console and to uninstall the iPlanet Application Server and the Directory Server.


  • Enter the data information tree suffix for your organization.



    For example, if an organization uses the distinguished name service (DNS) of sales.sun.com, then a reasonable suffix for identifying that organizations' data is: dc=sales, dc=sun, dc=com.

  • Enter a distinguished name (DN) for the directory server's administrator. The default value is Directory Manager (cn=Directory Manager).

    Enter a password for the Directory Manager that is at least 8 characters long.



    The Directory Manager's Distinguished Name is the special directory entry for the administrator of the Directory Server. Access control does not apply to the Directory Manager.

  • Enter the directory server's Administration Domain.

    If your installation has multiple domains setup for this Directory Server, enter a unique domain name here, otherwise keep the default entry. The default is set to the installation computer's domain. If you need to change this value, you should use a name that corresponds to the organizations that control the servers in each domain.

    Since a Directory Server may store Configuration information for multiple domains, the Administration Domain is used to keep these separate. Enter an administration domain to use for keeping software configuration information stored in the Configuration Directory Server distinct from other such information.

  • Enter Y to configure this Directory Server installation for replication; otherwise accept the default choice.

    Replication is used to duplicate all or part of a directory server to another directory server to provide a fail-safe setup.

    A server that holds a replica that is copied to a replica on a different server is called a supplier. A server that holds a replica that is copied from a different server is called a consumer. For more information on replication concepts, see iPlanet Directory Server Deployment Guide.

    http://docs.iplanet.com/docs/manuals/directory.html#dirserver

  • Enter Y to enter sample directory data or accept the default.

  • Enter the full path and filename of a file in LDIF format to populate the directory with your custom database, or Enter suggest at the prompt to add sample entries to the Directory Server.

  • Press Enter to enable schema checking for an imported database.

    Disable schema checking if you are going to import an old database immediately after or during installation, and you think you may have problems with it. If you choose to do this, schema checking will remain off
    until you manually turn it back on.

    We recommend that you turn it back on as soon as possible.

The Directory Server is now configured for installation. Next, you will configure the port numbers and the number of Java and C++ servers.


To Configure iPlanet Application Servers

  1. Press Enter to accept the default port number for the administration server, or type in a different port number.


    The Administration Server is separate from any of your application servers since it listens to a different port and access to it is restricted.

  2. Enter the IP address of the machine you want the Administration Server to bind to.

    By default, the IP address is that of the current host.

  3. Press Enter to enable "root" user access to the Administration Server.

  4. Enter Y if you want the locally installed Directory Server to be the instance which connects to the iPlanet Application Server.

    Depending on the configuration you are currently installing you may or may not want the locally installed Directory Server to be the instance which connects to iPlanet Application Server.

  5. Press Enter to accept the default global configuration name or type a unique name for this installation of iPlanet Application Server.



    This name is stored on the configuration Directory Server, under the o=NetscapeRoot tree, along with global configuration names of any other iPlanet Application Server installations.

  6. Enter the product key.

    The Product Key is in the welcome letter you received with iPlanet Application Server. You must enter this number correctly for installation to continue.

  7. Enter the full path of your Web Server instance.

    No default is provided.

  8. Press Enter to accept the default listener port numbers.



    Listener ports must be within the acceptable range (1025 to 32768), and must be unique (not used by any other services on your system).

  9. Press Enter to install one Java Server (KJS).

    If you intend to use more than one, enter the number and their default port number(s), or type different port numbers.

    All Java Server port numbers are listener ports and must be within the acceptable range of 1025 to 32768. Port numbers must be unique (not used by any other services on your system).

  10. Press Enter to install one C++ Server (KCS).

    If you intend to use more than one C++ server, enter the number and their default port number(s).

    All C++ port numbers are listener ports and must be within the acceptable range of 1025 to 32768. Port numbers must be unique (not used by any other services on your system).

  11. Enter the username and password to use for the iPlanet Application Server Administration Tool.




    Note Record the username and password. After installation, you'll need them to register iPlanet Application Server with the iPlanet Application Server Administration Tool.


Next up are configuration options to setup third party JDBC database drivers. You can also configure them after installation by running the db_setup.sh utility.

iPlanet Application Server supports iPlanet Type 2 JDBC drivers and third party JDBC database drivers.


To Configure Database Connectivity

This section includes procedures on setting up the database clients, Third party JDBC drivers, the Transaction Manager, and the Resource Manager.


Choose To Set Up JDBC Drivers

  • Press Enter to install iPlanet Type 2 JDBC drivers by default, or 2 to install Third Party JDBC drivers, or enter 3 for none.



    We recommend that you use the third party JDBC drivers, since the proprietary iPlanet Type 2 JDBC drivers are to be deprecated in the next major release.


To Set Up Third Party JDBC Drivers

  1. Enter the number of Third Party JDBC drivers you need.

  2. For each Third Party JDBC driver, enter the driver name, driver class name, and driver CLASSPATH. Follow the formats in the wizard examples. For more details, see "Preparing to Configure Third Party JDBC Drivers".

    The Third Party Native Driver Directory is required for Type 2 drivers only.


    Note
    • PointBase database server and its third party JDBC driver is automatically registered with the Administration Server. It also populates the sample databases of e-Store, J2EEGuide, Database, and Bank sample applications.

    • After installation you must register the datasource for the third party JDBC drivers. For more information, see "Configuring JDBC Datasources for Your Applications".

      Additional information is available in the iPlanet Application Server Administrator's Guide and the online help of the Deployment Tool.



To Configure Type 2 Database Connectivity

The installation program lists the database clients supported by iPlanet Application Server. These clients are required for Type 2 connectivity.

  1. Indicate if you want to configure this instance of iPlanet Application Server to connect with each of the supported database clients. For each client that you specify "Yes," provide the specified information for that client:

    • Oracle

      • Oracle home directory

      • Class library

    • Sybase:

      • Sybase home directory

      • Sybase server name

      • Class library

    • Informix:

      • Informix home directory

      • Informix server name

      • Class library

    • DB2:

      • DB2 home directory

      • DB2 server name

      • Class library

  2. Type Y (Yes) or N (No) to indicate whether or not to configure iPlanet Application Server for communication with Oracle, Sybase, Informix, and IBM DB2.

  3. Rank each database according to its priority for your application's data lookup needs.

    This enables you to write applications without specifying what database to use.


To Configure the Transaction Manager

The restart backup file for managing transactions, in case of engine failure, should be stored in a directory on a separate drive from the iPlanet Application Server installation directory. This needs to be setup prior to installing the application server.

  1. Enter the mirror directory path where the transaction manager restart.bak file of each KJS process is to be stored.

    The default directory is installDir/CCS0/TXNMGR_MIRROR/. This is the same path that is used to store the restart file. It is recommended that you store restart.bak in a different location than the default one. Consider using a pointer to the different physical disk drive.

  2. Set a location for the transaction manager log file.

    The log volume disk name is where the transaction manager log file is stored. The engine specified by /ENGx/represents the KJS engine process number. Create a directory on a separate disk drive and specify if it is a raw partition.

  3. Press Enter to configure iPlanet Application Server to use the Resource Manager with the Transaction Manager.

    If you have not yet configured a database, you are prompted to do it here.

  4. Coordinate the first resource manager instance with a database driver. You must specify the database server name, administrative user name and password.

    To configure others, type a unique resource identifier, the database type to associate it with, as well as, the database server name, administrative user name and password.

  5. Enter Y to enable standard Java Internationalization support, otherwise accept the default setting (N).


To Install iPlanet Application Server Clusters

Follow instructions for installing and verifying the simple cluster on the Solaris platform at: http://developer.iplanet.com/appserver/samples/cluster/docs/unix-cluster.html

Additional information on configuring and deploying iPlanet Application Servers is available under "Configuring Clusters and Data Synchronization", and in the iPlanet Application Server Administrator's Guide.


To Configure Clusters for Data Synchronization

  1. Enter y and press Enter to set this iPlanet Application Server instance to participate in data synchronization. The default is no (n).


    Note During installation, you cannot configure multiple instances on a single machine as a cluster. Use the Administration Tool to set up a clustering environment.

    For more information, see the iPlanet Application Server Administrator's Guide.




    This sets up the synchronization of session and state information across multiple servers for failover and fault tolerance.

  2. If you answered yes in the previous screen, you are asked to:

    1. Enter the name of the cluster to which this instance of iPlanet Application Server belongs. The cluster may already exist, or this may be the first server assigned to the cluster.



    2. Indicate if this iPlanet Application Server instance is to be a Sync Local or Sync Server instance.

      A Sync Local server uses data synchronization services, but is not eligible to become a Sync Primary or the Sync Backup Server. For more information on Sync Servers and Sync Local, see "Configuring Clusters and Data Synchronization"

    3. Enter the IP addresses and port numbers for each installation of iPlanet Application Server in the cluster. The IP address of the machine you are installing on is added by default (if it's a Sync Server).

      These IP addresses and port numbers must match across installations for the cluster to function properly.



    4. Enter the priority for each Sync Server. Start with the highest priority Sync Server in the cluster. This is the first server to take over if Sync Primary fails. Enter each Sync Server's priority until all are ranked.



    5. Specify the number of Sync Backup servers that should be active while the cluster is running.



This completes the configuration of your iPlanet Application Server installation. Continue with the next few steps to extract the packages and complete the installation.


To Complete the Installation

  1. Enter Y to enable this iPlanet Application Server instance to automatically start at system startups.

    The default is No.


    Note You can only run iPlanet Application Server automatically at startup if you have logged on as root.


  2. The installation program now extracts the iPlanet Application Server files and installs them in your system.

    Here, you may be prompted to change the ownership of iAS files if the owner and group are different.

    Type y and press Enter if you want to change the group permission of iAS files to that of the user you are installing as. You must be the superuser or logged in as that user to change permissions.

    After all the files have been extracted, the installer generates a report of the port numbers assigned.


    Note
    • Record or print the port number report as the port numbers are required to administer the iPlanet Application Server.

    • After installation is complete, the PointBase database package's administration dialog will be displayed. If you get an error message, and you are unable to view the dialog box, set the DISPLAY terminal variable to X.


    The PointBase database engine automatically starts after installation (if you had opted to install it). Use this bundled database application to test your sample database applications. If you don't want to use it right away, you can shut down the PointBase database engine and use it later.

    To start PointBase, go to the <iASInstallDir>/pointbase/network/bin and type:

    pointbaseServer start

    To stop, type:

    pointbaseServer stop

  3. To start iPlanet Administration Console, go to the installation directory and execute the command (printed at the end of the port number report):

    startconsole -a http://<servername.domain.com>:<port_number> .



Verifying Installation of the Application Server

The iPlanet Web site provides an application that verifies connectivity of your iPlanet Application Server installation. Since this basic application, which uses servlets and JSPs, does not rely on a database, it runs without any extra setup.


To Verify Installation

  1. Open your browser and enter the following URL:

    http://<yourwebserver>:<portnumber>/ias-samples/index.html

  2. Press Enter.

  3. Click the Quick Test link, under Sample Applications.

  4. Press the shift key and click on the browser's Reload button to ensure the application repeatedly returns a new HTML stream.



Using the Sample Applications

To better understand specific technology features provided by iPlanet Application Server, run the iPlanet Application Server Technology Samples.


To Use the Sample Applications

  1. Start iPlanet Application Server.

  2. Open your browser, enter the following URL, and press Enter:

    http://<yourwebserver>:<portnumber>/ias-samples/index.html

  3. Select the iPlanet Application Server J2EE Application Samples link and select a specific sample application. Follow the application-specific setup instructions to establish the necessary database settings and to run the application.

After you become familiar with the iPlanet Application Server sample applications, run the Sun Samples, which are applications based on those found at http://www.java.sun.com. The Java Pet Store example in particular demonstrates how a popular J2EE application is deployed to iPlanet Application Server.

You can review the source code of the sample applications and associated J2EE XML Deployment Descriptors by browsing in the following location:

installDir/ias/ias-samples/

You can also find compile scripts at this site for experimenting with the sample code.



Installing Multiple Instances on Solaris


Multiple instances benefit both the development and production environments. In the development environment, having multiple iPlanet Application Server instances enables you to isolate code. In a production environment, multiple iPlanet Application Server instances will improve scalability.

For more information on the benefits of installing multiple instances, see "Reasons for Installing Multiple Instances"


Note This option is available only on Solaris.



To Install for Developer Deployment

  1. Create logins for each iPlanet Application Server instance.

  2. Install the initial instance of the iPlanet Application Server on each system.

    • Set up a home directory, such as: /usr/iplanet/ias6/instance0.

    • Store configuration data under the global configuration name, iasconfig0, on the Directory Server.

    • Configure the number of executive server (KJS) processes so there is one KJS per iPlanet Application Server instance.

  3. Install additional iPlanet Application Server instances.

    • Use Custom Installation to assign different port numbers.

    • Set up different home directories for each instance, like:
      /usr/iplanet/ias6/instance1, /usr/iplanet/ias6/instance2

    • Do not install the iPlanet Directory Suite or Administration Services.

    • Do not install iPlanet Core Java classes or Java Runtime Environment.

  4. Store configuration data on the primary directory server in "iasconfig1", "iasconfig2", and so forth.

  5. Install the Web Connector on all Web Server instances. Each Web Server instance is associated with one iPlanet Application Server instance.


To Install for Production Deployment

  1. Install two Directory Servers; one to serve as a primary and the other a secondary server. Configure these servers so that the primary Directory Server replicates to the secondary.

  2. Create logins for each Directory Server instance. The best performance comes from using 1 instance per processor, but up to eight (8) processors can be used per Directory Server instance.

  3. Install the initial instance of the iPlanet Application Server on each system.

    • Setup an installation directory, like: /usr/iplanet/ias6/instance0.

    • Store configuration data in iasconfig_global on the primary Directory Server.

    • Configure for the secondary Directory Server.

    • Configure at least two KJS processes per iPlanet Application Server instance.

    • Optional: Configure the application server so that it starts up automatically

  4. Install additional instances.

    • Use the Custom Installation to change port numbers.

    • Input different home directories for each instance, like: /usr/iplanet/ias6/instance1, /usr/iplanet/ias6/instance2

    • Do not install the iPlanet Directory Suite or Administration Services.

    • Do not install iPlanet Core Java classes or Java Runtime Environment.

    • Do not install iPlanet Application Server Web Connector Component or Deployment Tool.

  5. Store configuration data on the primary Directory Server in:

    • iasconfig_global for most instances

    • iasconfig_aol for Web servers and iPlanet Application Servers in a cluster configuration dedicated to handling AOL customers

    • iasconfig_isp1 for Web servers and iPlanet Application Servers in a cluster configuration dedicated to handling isp1 customers

    • iasconfig_ispN for Web servers and iPlanet Application Servers in cluster configuration dedicated to handling ispN customers

  6. Configure a secondary Directory Server.

  7. Configure the number of KXS and KJS processes so that there are at least two KJS processes per instance. Configure for a maximum of 8 processors per instance, but definitely consider starting with 1 processor per instance.

  8. Configure each instance so that it does not start up automatically.

  9. Create a script to bind processes to individual processors. Consider binding the KXS and two KJS processes of an instance to the same processor if a processor per instance has been allocated. Otherwise, bind the KXS to one processor and each of the KJS processes to separate processors for each instance. Consider 2 processor sets for KXS processes on Primary instances.

  10. Create a crontab script to periodically check process bindings. A restart of a KJS process should cause this script to run the process binding script.

  11. Configure cluster pairs so that:

    • A ring topology is achieved as much as possible

    • Each instance is on a separate server

    Example 1:

    Server A runs Instance 0 and Instance 1

    Server B runs Instance 2 and Instance 3

    Server C runs Instance 4 and Instance 5

Create Cluster 0 with Instance 1 and Instance 2

Create Cluster 1 with Instance 3 and Instance 4

Create Cluster 2 with Instance 5 and Instance 0

Example 2:

Server A runs Instance 0, 1, 2, and 3

Server B runs Instance 4, 5, 6, and 7

Server C runs Instance 8 and 9

Create Cluster 0 with Instance 0 and 4

Create Cluster 1 with Instance 1 and 5

Create Cluster 2 with Instance 2 and 6

Create Cluster 3 with Instance 3 and 9

Create Cluster 4 with Instance 7 and 8

  1. Configure all iPlanet Application Server clusters for Per Component load balancing. Per Server load balancing will be confused by the sharing of servers between instances.

    On each server, modify the rc2 startup scripts so that all Sync Primary instances are started as soon as possible. Delay the startup of all Sync Backup Instances. Determine which instances are to be Sync Primary or Sync Backup by evenly dividing the load between the physical servers. The reason for making these changes is that Sync Primary servers do more work, so it is desirable to evenly divide the work. Sync Primary instances are determined based on the startup order.

    Example 1:

    Continuing from Example 1 in the previous section. Primary instances could be 1, 3, and 5.

    Example 2:

    Continuing from Example 2 in the previous section. Primary instances could be 0, 1, 6, 7, and 8.

  2. Install Web Connector on all web server instances. Allocate appropriate numbers of web server instances for each cluster that is allocated to ISP proxies. All other web server instances can be shared by the remaining cluster pairs.

    • Configure the web tier load balancer so that sessions return to their original web servers.

    • Configure the web tier load balancer so that known ISP proxies are associated with the web servers which have been allocated for that purpose.

    • Configure the web tier load balancer so that application partitioning between clusters is supported (in cases where applications do not exist on all clusters).
      Note Not all load balancing solutions can support all of these features. Resonate Central Dispatch is an example of a load balancer with these features.




Installing on Multiple Solaris Machines

The Silent Installation feature allows you to install the Application Server on multiple Solaris machines without running the installation program more than once.


To run Silent Install

  1. Run the setup -k command on the first machine.

    Proceed with the installation program. An install.inf file is generated in the installDir/setup directory. In addition, a log file,userinput.log, is generated in the installDir/ias directory. This file contains all input entered during the installation procedure.

  2. Once you have completed the installation process, copy install.inf and userinput.log and add them to the /tmp directory of a second system.

  3. Modify the copies of install.inf and userinput.log, as described in the following steps.

  4. You may have to change some or all of the following values in install.inf, depending on your configuration requirements, such as, port numbers, domain name, etc.


    Table 4-1    Settings in install.inf

    Value

    Description

    FullMachineName  

    Name of the machine on which iPlanet Application Server is being installed  

    ServerRoot  

    Installation root directory  

    AdminDomain  

    Directory server's administration domain  

    ConfigDirectoryLdapURL  

    URL for the configuration information in the directory server.  

    UserDirectoryLdapURL  

    URL for the user information in the directory server  

    ServerPort  

    Local directory server port  

    ServerIdentifier  

    Local directory server identifier  

    Port  

    Local Administration port  

  5. Change the following keys in the userinput.log file. You may need to change some or all of the following values, depending on your configuration requirements:


    Table 4-2    Settings in userinput.log file

    Value

    Description

    NAS_backup_dir  

    Directory used to back up files, usually <ServerRoot>/backup  

    LDAP_ServerRoot  

    Same as ServerRoot in install.inf  

    LDAP_Hostname  

    Same as FullMachineName in install.inf  

    LDAP_ServerIdentifier  

    Same as ServerIdentifier in install.inf  

    LDAP_ServerPort  

    Same as ServerPort in install.inf  

    AdminServer_Port  

    Same as Port in install.inf  

    LDAP_AdminDomain  

    Same as AdminDomain in install.inf  

    LDAP_UserDirectoryLdapURL  

    Same as UserDirectoryLdapURL in install.inf  

    NAS_home  

    Root of iPlanet Application Server installation. Usually <ServerRoot>/ias  

    NAS_userinputlog  

    Path for storing userinput.log file  

    BASEDIR  

    Same as NAS_home  

    LocalHostName  

    Name of the machine on which silent install is being done  

    LocalIPAddress  

    IP address of the machine on which silent install is being done  

    KIVAKey  

    Product Key  

    LDAP_nasconfig  

    Global configuration name under which iPlanet Application Server configuration information is stored in the directory server.  

    NSRootDir  

    Path of the Web Server instance  

    nsinst  

    Same as NSRootDir  

    webserver_version  

    If you are running iPlanet Web Server 4.1, then this value id 4.1. If you are running 6.0, then use the value 6.0  

  6. Enter the port numbers for KAS, KXS, KJS, KCS, etc.

  7. Enter the logvol root's sizes for each of the kjs engines, such as, TXN_DirectoryRoot_logVol_1

  8. Enter passwords in the following fields. You need not modify these values if you want to use the same passwords for all the multiple installations.

    • Password settings in the install.inf file:

      • ConfigDirectoryAdminPwd

      • UserDirectiryAdminPwd

      • RootDNPwd

      • ServerAdminPwd

    • Password settings in the userinput.log file

      • LDAP_RootDNPwd

      • LDAP_UserDirectoryAdminPwd

      • PASSWORD

  9. Run the following command on the second system to begin silent installation: setup -s -f fullpath/install.inf

This performs an installation with exactly the same setup as the first system.


Previous     Contents     Index     DocHome     Next     
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.

Last Updated November 22, 2001