Chapter 4 Performing Silent Installation

Sun ONE Meta-Directory 5.1.1 Installation Guide

Chapter 4
Performing Silent Installation

This chapter describes installing Meta-Directory using the ‘Silent Installation’ method. ‘Silent Installation’ involves defining the configuration information in a file, and then using it to install Meta-Directory from remote systems. You can also use this file to perform installations on multiple systems - simultaneously.

This chapter contains these sections:

Install.inf File Description

Creating an Install.inf File

Using the Install.inf File

Installing Meta-Directory Using the Install.inf File

Install.inf File Examples

Install.inf File Description

The install.inf file is used to perform the silent installation of Meta-Directory. It is created during the initial installation of Meta-Directory and can be modified for use during unattended installations. The basic format of the file is this:

[General]
directive= value
directive= value
directive= value
...
[base]
directive= value
directive= value
directive= value
...
[admin]
directive= value
directive= value
directive= value
....

The keywords [General], [base], and [admin] are required. These keywords identify a specific aspect of the installation process. Directives are detailed specifications of each keyword.

Defining the Directives

The directives used in install.inf are of four types: [General], [Base], [admin], and [component].

General Directives

General installation directives specify information that will be common to all installations performed.

Table 4-1  [General] Installation Directives

Directive

Description

Components

Specifies one or all of following components that will be installed (mandatory):

srvrcore—uninstallation binaries

base—the base installation package

admin—the Administration Server binaries

ServerRoot

Specifies the complete path where the selected Meta-Directory components are installed (mandatory).

FullMachineName

Specifies the fully qualified domain name of the machine on which you are performing the silent installation. If is not present, the Common Install Shell will query the machine for its name.

SuiteSpotUserID

For Solaris^® only: Specifies the name of the user under which Meta-Directory will run.

SuiteSpotGroup

For Solaris^® only: Specifies the name of the group to which the SuiteSpotUserID belongs.

ConfigDirectoryLdapURL

Specifies the URL of the directory server used to manage the information and data. The URL is specified in the following format: ldap://<machinename>:<port>/<base DN> (mandatory)

AdminDomain

Specifies the administration domain under which this server will be registered.

ConfigDirectoryAdminID

Specifies the user ID that has permission to access the configuration directory and the specified administration domain (mandatory).

ConfigDirectoryAdminPwd

Specifies the password for the user that has permission to access the configuration directory and the specified administration domain (mandatory).

UserDirectoryLdapURL

Specifies the URL of the directory server in this installation which requires write access to the user directory.

UserDirectoryAdminID

Specifies the user ID of the user that has administration privileges to the user directory.

UserDirectoryAdminPwd

Specifies the password for the user that has administration privileges to the user directory.

Base Directives

The [base] installation directive determines which of the components needed for the Sun ONE Console will be installed.

Table 4-2  [base] Installation Directive

Directive

Description

Components

The values for this directive are one, two, or all three of:

base — the shared libraries used by the Sun ONE Console

base-client — the Java Runtime Environment used by server consoles

base-jre — the Java Runtime Environment used by all other consoles

Admin Directives

The [admin] installation directives specify information needed by the administration server to manage the instance that is being installed.

Table 4-3  [admin] Installation Directives

Directive

Description

Components

Specifies which of the following admin components will be installed:

admin — installs the Administration Server. You must install the Administration Server to install and use other Sun ONE servers.

admin-client — installs Sun ONE Console. Do not install if you will remotely manage your servers from an instance of Sun ONE Console elsewhere on the network.

SysUser

For Solaris only: Specifies the user for which the Administration Server will run. For default installations, this user must be root.

Port

Specifies the port that the Administration Server will use. Note that the Administration Server’s host name is given by FullMachineName, one of the general directives.

ServerAdminID

Specifies the administration ID that is used to access the Administration Server when the configuration directory is not responding.

ServerAdminPwd

Specifies the password for ServerAdminID.

ServerIPAddress

Specifies the IP address that the Administration Server will listen to. Use this directive if you are installing on a system with more than one IP address and you do not want to use the first IP address for your Administration Server.

Component Directives

The [component] installation directives determine which, if any, of the Meta-Directory’s components will be installed. Each component is its own directive. They can include all or some of the components in Table 4-1. (To understand how component directives are formed, see "Install.inf File Examples".)

Table 4-4  [component] Installation Directives

Directive

Description

Components

Specifies the Meta-Directory component to be installed and have a value equal to themselves:

[nsperl]nsPerl (value includes a version number)

[join]Join engine

[utc]Universal connector

[metaconsole]Meta-Directory console

[ntdc]Windows NT domain connector

[adc]Active Directory connector

[dbc]Database connector

[exc]Exchange Connector

[nov] Novell Connector

[notes] Lotus Notes Connector

InstallType

Specifies the type of installation. The options are New, Upgrade, Migrate, Extraction, or Remove.

InstallUnitAction

Specifies the type of installation. The options are None, Create, Migrate, Repair, or Remove.

HaveReached

By the fault the value is ‘True’.

Note

Disregard the sf. prefix in front of all component directives.

Creating an Install.inf File

    To create the Install.inf file

On Solaris

Execute the setup script using the -k command-line option:

<Netsite_Root>/setup.sh -k

This creates the install.inf file, which is located here:

<Netsite_Root>/setup/install.inf

On Windows

Download the zipped file of Meta-Directory to temporary directory. Create a temporary directory if it does not exist.

From the temporary directory, decompress the zipped file using a decompression program such as WinZip.

Go to Start > Programs > Run to display the Command Prompt window.

Go the directory where you decompressed the binaries, and then type setup.bat -k to execute the setup batch file.

Using the Install.inf File

The install.inf file must be modified to perform installations on several machines. This section describes the modifications that are required.

    Modify the following in the install.inf file

Change the FullMachineName directive to the fully-qualified domain name of the new machine on which Meta-Directory will be installed.

Note

Ensure that FullMachineName defaults to the local host name.

Enter the path to the local machine in the ServerIPAddress directive.

Note

It is recommended to use the ServerIPAddress directive only if you are installing Meta-Directory on a machine with multiple IP addresses.

Ensure that the installation path used in the ServerRoot directive is system-appropriate.

Note

If you are installing on both Windows and Solaris machines, make sure the correct path delimiter is used. You may need to add or remove the Windows drive letter designation appropriately.

Solaris only: If you are installing more than one instance of Meta-Directory on the same host, ensure that the ServerRoot directive contains a unique value for each instance.

If you create the install.inf file on a Windows system, then the SuiteSpotUserID and SuiteSpotGroup directives should be set to user nobody. If you subsequently use this file on a Solaris machine, ensure the user and group names are appropriate for the machine. The SuiteSpotUserID and SuiteSpotGroup directives determine the user and group that Meta-Directory will run under when installed on a Solaris machine.

Caution

Be aware that the install.inf files contain server passwords and should be protected.

Installing Meta-Directory Using the Install.inf File

    To install Meta-Directory using the install.inf file, run the setup script with the -s and -f command options

On Solaris

<Netsite_Root>/setup.sh -sf install.inf

On Windows

<Netsite_Root>/setup.bat -sf install.inf

Install.inf File Examples

This section provides examples of the install.inf files for Solaris and Windows systems.

Solaris Install.inf File Example

This is an example of an install.inf file generated on a Solaris-based system.

[General]

FullMachineName=restaurants.madisonparc.com

SuiteSpotUserID=root

SuitespotGroup=other

ConfigDirectoryAdminID=admin

ConfigDirectoryAdminPwd=netscape

ServerRoot=/usr/sunone/servers

AdminDomain=madisonparc.com

MachineName=restaurants

InstallTimeStamp=20030116102730Z

Components=

svrcore,base,admin,nsperl,metaconsole,join,utc,dbc,ndc,notes,perldap

ConfigDirectoryLdapURL=ldap://restaurants.madisonparc.com:3030/

LDAPPort=3030

LDAPHost=restaurants.madisonparc.com

AdminGroupDN=cn=Server Group (2),cn=restaurants.madisonparc.com, ou=madisonparc.com, o=NetscapeRoot

[admin]

SysUser=root

Port=3032

ServerIpAddress=

ServerAdminID=admin

ServerAdminPwd=netscape

Components=admin,admin-client

[nsperl]

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

Components=nsperl582

[metaconsole]

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

Components=metaconsole

[join]

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

Components=join

[utc]

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

Components=utc

[dbc]

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

Components=dbc

[ndc]

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

Components=ndc

[notes]

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

Components=notes

[base]

Components=base,base-client,base-jre

[perldap]

Components=perldap

Windows Install.inf File Example

This is an example of an install.inf file generated on a Windows-based system.

[General]

AdminDomain=example.madisionparc.com

Components=base,admin,nsperl,metaconsole,join,utc,ntdc,adc,exc,dbc,ndc,not es,perldap

ServerRoot=C:\SunONE\Servers

ConfigDirectoryLdapURL=ldap://example.madisionparc.com:5000/o=NetscapeRoot

ConfigDirectoryAdminID=uid=admin,ou=Administrators,ou=TopologyManagement, o=NetscapeRoot

ConfigDirectoryAdminPwd=netscape

FullMachineName=example.madisionparc.com

SuiteSpotUserID=None

SuitespotGroup=None

SelectedComponents=base,base-client,base-jre,admin,admin-client,nsperl582, metaconsole,join,utc,ntdc,adc,exc,dbc,ndc,notes,perldap

MachineName=talio

InstallTimeStamp=20030116103500Z

[base]

Components=base,base-client,base-jre

Reinstall=TRUE

[admin]

Components=admin,admin-client

Reinstall=TRUE

Port=5001

SysUser=root

ServerAdminID=uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot

ServerAdminPwd=netscape

[nsperl]

Components=nsperl582

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

[metaconsole]

Components=metaconsole

Reinstall=TRUE

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

[join]

Components=join

Reinstall=TRUE

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

[utc]

Components=utc

Reinstall=TRUE

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

[ntdc]

Components=ntdc

Reinstall=TRUE

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

[adc]

Components=adc

Reinstall=TRUE

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

[exc]

Components=exc

Reinstall=TRUE

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

[dbc]

Components=dbc

Reinstall=TRUE

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

[ndc]

Components=ndc

Reinstall=TRUE

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

[notes]

Components=notes

Reinstall=TRUE

sf.InstallUnitAction=Create

sf.HaveReached=True

sf.InstallType=New

[perldap]

Components=perldap

Reinstall=TRUE

[base-client]

Reinstall=TRUE

[base-jre]

Reinstall=TRUE

[admin-client]

Reinstall=TRUE

[nsperl582]

Reinstall=TRUE

Previous      Contents      Index      Next

Copyright 2004 Sun Microsystems, Inc. All rights reserved.

Directive	Description
Components	Specifies one or all of following components that will be installed (mandatory): srvrcore—uninstallation binaries base—the base installation package admin—the Administration Server binaries
ServerRoot	Specifies the complete path where the selected Meta-Directory components are installed (mandatory).
FullMachineName	Specifies the fully qualified domain name of the machine on which you are performing the silent installation. If is not present, the Common Install Shell will query the machine for its name.
SuiteSpotUserID	For Solaris^® only: Specifies the name of the user under which Meta-Directory will run.
SuiteSpotGroup	For Solaris^® only: Specifies the name of the group to which the SuiteSpotUserID belongs.
ConfigDirectoryLdapURL	Specifies the URL of the directory server used to manage the information and data. The URL is specified in the following format: ldap://<machinename>:<port>/<base DN> (mandatory)
AdminDomain	Specifies the administration domain under which this server will be registered.
ConfigDirectoryAdminID	Specifies the user ID that has permission to access the configuration directory and the specified administration domain (mandatory).
ConfigDirectoryAdminPwd	Specifies the password for the user that has permission to access the configuration directory and the specified administration domain (mandatory).
UserDirectoryLdapURL	Specifies the URL of the directory server in this installation which requires write access to the user directory.
UserDirectoryAdminID	Specifies the user ID of the user that has administration privileges to the user directory.
UserDirectoryAdminPwd	Specifies the password for the user that has administration privileges to the user directory.

Directive	Description
Components	Specifies which of the following admin components will be installed: admin — installs the Administration Server. You must install the Administration Server to install and use other Sun ONE servers. admin-client — installs Sun ONE Console. Do not install if you will remotely manage your servers from an instance of Sun ONE Console elsewhere on the network.
SysUser	For Solaris only: Specifies the user for which the Administration Server will run. For default installations, this user must be root.
Port	Specifies the port that the Administration Server will use. Note that the Administration Server’s host name is given by FullMachineName, one of the general directives.
ServerAdminID	Specifies the administration ID that is used to access the Administration Server when the configuration directory is not responding.
ServerAdminPwd	Specifies the password for ServerAdminID.
ServerIPAddress	Specifies the IP address that the Administration Server will listen to. Use this directive if you are installing on a system with more than one IP address and you do not want to use the first IP address for your Administration Server.

Directive	Description
Components	Specifies the Meta-Directory component to be installed and have a value equal to themselves: [nsperl]nsPerl (value includes a version number) [join]Join engine [utc]Universal connector [metaconsole]Meta-Directory console [ntdc]Windows NT domain connector [adc]Active Directory connector [dbc]Database connector [exc]Exchange Connector [nov] Novell Connector [notes] Lotus Notes Connector
InstallType	Specifies the type of installation. The options are New, Upgrade, Migrate, Extraction, or Remove.
InstallUnitAction	Specifies the type of installation. The options are None, Create, Migrate, Repair, or Remove.
HaveReached	By the fault the value is ‘True’.


Note	Disregard the sf. prefix in front of all component directives.


Note	Ensure that FullMachineName defaults to the local host name.


Note	It is recommended to use the ServerIPAddress directive only if you are installing Meta-Directory on a machine with multiple IP addresses.


Note	If you are installing on both Windows and Solaris machines, make sure the correct path delimiter is used. You may need to add or remove the Windows drive letter designation appropriately.


Caution	Be aware that the install.inf files contain server passwords and should be protected.