Silent installation allows you to use a file to predefine all the answers that you would normally supply to the setup program interactively. This provides you with the ability to script the installation of your Directory Servers.
This chapter includes the following sections:
Using Silent Installation
Silent Installation Examples
Installation Directives
On Unix machines, log in as root. On Windows NT machines, login with Administrator privileges.
If you have not already done so, download the product binaries file to the installation directory.
On Unix, unpack the product binaries file using the following command: # gzip -dc <filename>.tar.gz | tar -xvof- where <filename> corresponds to the product binaries that you want to unpack. On Windows NT, unzip the product binaries.
# gzip -dc <filename>.tar.gz | tar -xvof-
where <filename> corresponds to the product binaries that you want to unpack.
On Windows NT, unzip the product binaries.
Prepare the file that will contain your installation directives.
Run the setup program with the -s and -f command line options: setup -s -f <filename> where <filename> is the name of the file that contains your installation directives.
setup -s -f <filename>
where <filename> is the name of the file that contains your installation directives.
This section first describes how to create silent installation files. It then provides examples of using silent installation to support the following common installation scenarios:
"A Typical Installation"
"Creating an SIR Consumer Server"
"Creating a CIR Consumer Server"
"Creating an SIR Supplier Server"
"Creating a CIR Supplier Server"
"Using an Existing Configuration Directory"
"Installing the Stand-Alone Netscape Console"
Creating Silent Installation Files
The best way to create a file for use with silent installation is to use the setup program to interactively create a server instance of the type that you want to duplicate around your enterprise. At the end of your installation process, the setup program will ask you if you want to save the install.inf file. This file contains all the directives that you would use with silent installation to create the server instance. You can then use this file to create other server instances of that type.
If you do not delete the file at installation time, you can find it at:
<NSHOME>/setup/install.inf
However, you will have to make some modifications to this file before you use it on other machines. Specifically, make sure you:
Set the FullMachineName directive to a value appropriate for the local machine. In most circumstances, it is best to not use this directive because then FullMachineName will default to the local host name. However, if you use custom install to generate your initial server instance, then this directive will appear in the install.inf file. Either delete the directive from the file, or set it to an appropriate host name for each machine that you use the install.inf file on.
Set the ServerIPAddress directive appropriate for the local machine. The same usage rules apply for ServerIPAddress as for FullMachineName. Specifically, try to not include ServerIPAddress in your install.inf file unless you absolutely have to (as may be necessary for multi-homed systems).
Verify the installation path on the ServerRoot directive. If you are installing on both Windows NT and Unix machines, make sure the appropriate path delimiter is used. Add or remove the Windows NT drive letter designation as is appropriate for the host you are installing on.
If you are installing more than one Directory Server on the same host, make sure the ServerIdentifier directive contains a unique value for each server instance.
If you created your install.inf file on a Windows NT machine, then the SuiteSpotUserID and SuiteSpotGroup directives are both set to nobody. If you subsequently use this file on a Unix machine, make sure the user and group specified by these directives are appropriate for the machine. The SuiteSpotUserID and SuiteSpotGroup directives determine what user and group a server will run under when installed on a Unix system. For information on these directives, see "Installation Directives".
The following is the install.inf file that is generated for a typical installation:
[General] FullMachineName= dir.airius.com SuiteSpotUserID= nobody SuiteSpotGroup= nobody ServerRoot= /usr/netscape/server4 AdminDomain= mcom.com ConfigDirectoryAdminID= admin ConfigDirectoryAdminPwd= admin ConfigDirectoryLdapURL= ldap://dir.airius.com:389/o=NetscapeRoot UserDirectoryAdminID= admin UserDirectoryAdminPwd= admin UserDirectoryLdapURL= ldap://dir.airius.com:389/o=airius.com Components= svrcore,base,slapd,admin
[slapd] SlapdConfigForMC= Yes SecurityOn= No UseExistingMC= No UseExistingUG= No ServerPort= 389 ServerIdentifier= dir Suffix= o=mcom.com RootDN= cn=Directory Manager UseReplication= No SetupSupplier= No SetupConsumer= No AddSampleEntries= No InstallLdifFile= suggest AddOrgEntries= Yes DisableSchemaChecking= No RootDNPwd= admin123 Components= slapd,slapd-client
[admin] SysUser= root Port= 23611 ServerIpAddress= 111.11.11.11 ServerAdminID= admin ServerAdminPwd= admin Components= admin,admin-client,base-jre
[base] Components= base,base-client
Creating an SIR Consumer Server
The following is the install.inf file that is generated when you install a consumer server for supplier-initiated replication:
[General] FullMachineName= dir.airius.com SuiteSpotUserID= nobody SuiteSpotGroup= nobody ServerRoot= /usr/netscape/server4 AdminDomain= airius.com ConfigDirectoryAdminID= admin ConfigDirectoryAdminPwd= admin ConfigDirectoryLdapURL= ldap://dir.airius.com:25389/o=NetscapeRoot UserDirectoryLdapURL= ldap://consumer1.airius.com:32389/o=airius.com UserDirectoryAdminID= cn=Directory Manager UserDirectoryAdminPwd= admin123 Components= svrcore,base,slapd,admin
[slapd] SlapdConfigForMC= No SecurityOn= No UseExistingMC= yes UseExistingUG= No ServerPort= 32389 ServerIdentifier= consumer1 Suffix= o=airius.com RootDN= cn=Directory Manager UseReplication= yes SetupSupplier= No SetupConsumer= 1 AddSampleEntries= No InstallLdifFile= suggest AddOrgEntries= Yes DisableSchemaChecking= No RootDNPwd= admin123 UpdateDN= cn=supplier UpdatePwd= supplier Components= slapd,slapd-client
[admin] SysUser= root Port= 2101 ServerIpAddress= 111.11.11.11 ServerAdminID= admin ServerAdminPwd= admin Components= admin,admin-client,base-jre
Creating a CIR Consumer Server
The following is the install.inf file that is generated when you install a consumer server for consumer-initiated replication:
[General] FullMachineName= dir.airius.com SuiteSpotUserID= nobody SuiteSpotGroup= nobody ServerRoot= /usr/netscape/server4 AdminDomain= airius.com ConfigDirectoryAdminID= admin ConfigDirectoryAdminPwd= admin ConfigDirectoryLdapURL= ldap://dir.airius.com:25389/o=NetscapeRoot UserDirectoryLdapURL= ldap://consumer2.airius.com:24389/o=airius.com UserDirectoryAdminID= cn=Directory Manager UserDirectoryAdminPwd= admin123 Components= svrcore,base,slapd,admin
[slapd] SlapdConfigForMC= No SecurityOn= No UseExistingMC= yes UseExistingUG= No ServerPort= 24389 ServerIdentifier= consumer2 Suffix= o=airius.com RootDN= cn=Directory Manager UseReplication= yes SetupSupplier= No SetupConsumer= 2 AddSampleEntries= No InstallLdifFile= suggest AddOrgEntries= Yes DisableSchemaChecking= No RootDNPwd= admin123 CIRHost= dir.airius.com CIRPort= 25389 CIRBindDN= cn=Replication Consumer, o=airius.com CIRBindDNPwd= replication CIRSuffix= ou=people, o=airius.com CIRInterval= 0 CIRDays= Components= slapd,slapd-client
[admin] SysUser= root Port= 1547 ServerIpAddress= 111.11.11.11 ServerAdminID= admin ServerAdminPwd= admin Components= admin,admin-client,base-jre
Creating an SIR Supplier Server
The following is the install.inf file that is generated when you install a supplier server for supplier-initiated replication:
[General] FullMachineName= dir.airius.com SuiteSpotUserID= nobody SuiteSpotGroup= nobody ServerRoot= /usr/netscape/server4 AdminDomain= airius.com ConfigDirectoryAdminID= admin ConfigDirectoryAdminPwd= admin ConfigDirectoryLdapURL= ldap://dir.airius.com:12683/o=airius.com UserDirectoryAdminID= admin UserDirectoryAdminPwd= admin UserDirectoryLdapURL= ldap://dir.airius.com:12683/o=airius.com Components= svrcore,base,slapd,admin
[slapd] SlapdConfigForMC= Yes SecurityOn= No UseExistingMC= No UseExistingUG= No ServerPort= 12683 ServerIdentifier= supplier1 Suffix= o=airius.com RootDN= cn=Directory Manager UseReplication= yes SetupSupplier= 1 SetupConsumer= No
AddSampleEntries= No InstallLdifFile= suggest AddOrgEntries= Yes DisableSchemaChecking= No RootDNPwd= admin123 ChangeLogSuffix= cn=changelog ChangeLogDir= /usr/netscape/server4/slapd-supplier1/logs/changelogdb SIRHost= dir.airius.com SIRPort= 25389 SIRBindDN= cn=supplier SIRBindDNPwd= supplier SIRSuffix= ou=people,o=airius.com SIRDays= Components= slapd,slapd-client
[admin] SysUser= root Port= 8741 ServerIpAddress= 111.11.11.11 ServerAdminID= admin ServerAdminPwd= admin Components= admin,admin-client,base-jre
Creating a CIR Supplier Server
The following is the install.inf file that is generated when you install a supplier server for consumer-initiated replication:
[General] FullMachineName= dir.airius.com SuiteSpotUserID= nobody SuiteSpotGroup= nobody ServerRoot= /usr/netscape/server4 AdminDomain= airius.com ConfigDirectoryAdminID= admin ConfigDirectoryAdminPwd= admin ConfigDirectoryLdapURL= ldap://dir.airius.com:2346/o=airius.com UserDirectoryAdminID= admin UserDirectoryAdminPwd= admin UserDirectoryLdapURL= ldap://dir.airius.com:2346/o=airius.com Components= svrcore,base,slapd,admin
[slapd] SlapdConfigForMC= Yes SecurityOn= No UseExistingMC= No UseExistingUG= No ServerPort= 2346 ServerIdentifier= supplier2 Suffix= o=airius.com RootDN= cn=Directory Manager UseReplication= yes SetupSupplier= 2 SetupConsumer= No AddSampleEntries= No InstallLdifFile= suggest AddOrgEntries= Yes DisableSchemaChecking= No RootDNPwd= admin123 ChangeLogSuffix= cn=changelog ChangeLogDir= /usr/netscape/server4/slapd-supplier2/logs/changelogdb ConsumerDN= cn=replication, o=airius.com ConsumerPwd= replication Components= slapd,slapd-client
[admin] SysUser= root Port= 3622 ServerIpAddress= 111.11.11.11 ServerAdminID= admin ServerAdminPwd= admin Components= admin,admin-client,base-jre
Using an Existing Configuration Directory
The following is the install.inf file that is generated when you perform a typical install and you choose to use an existing Directory Server as the configuration directory:
[General] FullMachineName= dir.airius.com SuiteSpotUserID= nobody SuiteSpotGroup= nobody ServerRoot= /usr/netscape/server4 AdminDomain= airius.com ConfigDirectoryAdminID= admin ConfigDirectoryAdminPwd= admin ConfigDirectoryLdapURL= ldap://dir.airius.com:25389/o=NetscapeRoot UserDirectoryLdapURL= ldap://dir.airius.com:18257/o=airius.com UserDirectoryAdminID= cn=Directory Manager UserDirectoryAdminPwd= admin123 Components= svrcore,base,slapd,admin
[slapd] SlapdConfigForMC= No SecurityOn= No UseExistingMC= y UseExistingUG= No ServerPort= 18257 ServerIdentifier= directory Suffix= o=airius.com RootDN= cn=Directory Manager UseReplication= No SetupSupplier= No SetupConsumer= No AddSampleEntries= No InstallLdifFile= suggest AddOrgEntries= Yes DisableSchemaChecking= No RootDNPwd= admin123 Components= slapd,slapd-client
[admin] SysUser= root Port= 33646 ServerIpAddress= 111.11.11.11 ServerAdminID= admin ServerAdminPwd= admin Components= admin,admin-client,base-jre
Installing the Stand-Alone Netscape Console
The following is the install.inf file that is generated when you install just Netscape Console:
[General] FullMachineName= dir.airius.com ConfigDirectoryLdapURL= ldap://dir.airius.com:389/o=NetscapeRoot SuiteSpotUserID= nobody SuiteSpotGroup= nobody ConfigDirectoryAdminID= admin ConfigDirectoryAdminPwd= admin ServerRoot= /usr/netscape/server4 Components= svrcore,base,slapd,admin
[base] Components= base-client
[slapd] Components= slapd-client
[admin] Components= admin-client,base-jre
"Silent Installation File Format"
"[General] Installation Directives"
"[Base] Installation Directives"
"[slapd] Installation Directives"
"[admin] Installation Directives"
When you use silent installation, you provide all the installation information in a file. This file is formatted as follows:
[General] directive=value directive=value directive=value ... [Base] directive=value directive=value directive=value ... [slapd] directive=value directive=value directive=value ... [admin] directive=value directive=value directive=value ....
The keywords [General], [slapd], and [admin] are required. They indicate that the directives that follow are meant for a specific aspect of the installation. They must be provided in the file in the order indicated above.
[General] Installation Directives
[General] installation directives specify information of global interest to the Netscape servers installed at your site. That is, the information you provide here will be common to all your Netscape servers.
The [General] installation directives are:
Table 4.1 [General] Installation Directives DirectiveDescription ComponentsSpecifies components to be installed. The list of available components will differ depending on the Netscape servers available on your installation media. For stand-alone directory installation, the list of components is:srvrcore—uninstallation binariesbase—the base installation packageadmin—the Administration Server binariesslapd—the Directory Server binariesThis directive is required. At a minimum, you should always provide:components = srvrcore, base, admin ServerRootSpecifies the full path to the directory where the Netscape server binaries are installed. This directive is required. FullMachineNameSpecifies the fully qualified domain name of the machine on which you are installing the server. The default is the local host name. SuiteSpotUserIDUnix only. Specifies the username that Netscape servers will run as. This parameter does not apply to the user that the Administration Server runs as. See the SysUser directive in Table 4.10 for more information. The default is user nobody. SuiteSpotGroupUnix only. Specifies the group that Netscape servers will run as. The default is group nobody. ConfigDirectoryLdapURLSpecifies the LDAP URL that is used to connect to your configuration directory. LDAP URLs are described in the Netscape Directory Server Administrator's Guide. This directive is required. AdminDomainSpecifies the administration domain under which this server will be registered. See "Determine the Administration Domain" for more information about administration domains. ConfigDirectoryAdminIDSpecifies the user ID of the entry that has administration privileges to the configuration directory. This directive is required. ConfigDirectoryAdminPwdSpecifies the password for the ConfigDirectoryAdminID. This directive is required. UserDirectoryLdapURLSpecifies the LDAP URL that is used to connect to the directory where your user and group data is stored. If this directive is not supplied, the configuration directory is used for this purpose. LDAP URLs are described in the Netscape Directory Server Administrator's Guide. UserDirectoryAdminIDSpecifies the user ID of the entry that has administration privileges to the user directory. UserDirectoryAdminPwdSpecifies the password for the UserDirectoryAdminID. [Base] Installation Directives
Table 4.1 [General] Installation Directives DirectiveDescription ComponentsSpecifies components to be installed. The list of available components will differ depending on the Netscape servers available on your installation media. For stand-alone directory installation, the list of components is:srvrcore—uninstallation binariesbase—the base installation packageadmin—the Administration Server binariesslapd—the Directory Server binariesThis directive is required. At a minimum, you should always provide:components = srvrcore, base, admin ServerRootSpecifies the full path to the directory where the Netscape server binaries are installed. This directive is required. FullMachineNameSpecifies the fully qualified domain name of the machine on which you are installing the server. The default is the local host name. SuiteSpotUserIDUnix only. Specifies the username that Netscape servers will run as. This parameter does not apply to the user that the Administration Server runs as. See the SysUser directive in Table 4.10 for more information. The default is user nobody. SuiteSpotGroupUnix only. Specifies the group that Netscape servers will run as. The default is group nobody. ConfigDirectoryLdapURLSpecifies the LDAP URL that is used to connect to your configuration directory. LDAP URLs are described in the Netscape Directory Server Administrator's Guide. This directive is required. AdminDomainSpecifies the administration domain under which this server will be registered. See "Determine the Administration Domain" for more information about administration domains. ConfigDirectoryAdminIDSpecifies the user ID of the entry that has administration privileges to the configuration directory. This directive is required. ConfigDirectoryAdminPwdSpecifies the password for the ConfigDirectoryAdminID. This directive is required. UserDirectoryLdapURLSpecifies the LDAP URL that is used to connect to the directory where your user and group data is stored. If this directive is not supplied, the configuration directory is used for this purpose. LDAP URLs are described in the Netscape Directory Server Administrator's Guide. UserDirectoryAdminIDSpecifies the user ID of the entry that has administration privileges to the user directory. UserDirectoryAdminPwdSpecifies the password for the UserDirectoryAdminID.
Table 4.1 [General] Installation Directives
There is only one [Base] installation directive and it allows you to determine whether Netscape Console is installed:
Table 4.2 [Base] Installation Directive DirectiveDescription ComponentsSpecifies the base components to be installed. The base components are:base—install the shared libraries used by all server consoles. You must install this package if you are also installing some other Netscape server. base-client—install the Java run time environment used by the server consoles. base-jre—causes the Java run time environment to be installed. Depending on your platform, this component may not be bundled with your software. If it is not, then you must install your own JRE and set the JAVA_HOME environment variable.This directive is required if you are installing a Netscape server (versus, for example, just Netscape Console). You must install both packages when you are installing a Netscape server. [slapd] Installation Directives
Table 4.2 [Base] Installation Directive DirectiveDescription ComponentsSpecifies the base components to be installed. The base components are:base—install the shared libraries used by all server consoles. You must install this package if you are also installing some other Netscape server. base-client—install the Java run time environment used by the server consoles. base-jre—causes the Java run time environment to be installed. Depending on your platform, this component may not be bundled with your software. If it is not, then you must install your own JRE and set the JAVA_HOME environment variable.This directive is required if you are installing a Netscape server (versus, for example, just Netscape Console). You must install both packages when you are installing a Netscape server.
Table 4.2 [Base] Installation Directive
[slapd] installation directives specify information of interest only to the Directory Server instance that you are currently installing. These directives are described in the following sections:
"Required [slapd] Installation Directives"
"Optional [slapd] Installation Directives"
"Consumer Server [slapd] Installation Directives"
"Supplier Server [slapd] Installation Directives"
You must provide the following directives when you use silent installation with Directory Server:
Table 4.3 Required [slapd] Installation Directives DirectiveDescription ComponentsSpecifies the slapd components to be installed. The slapd components are:slapd—install the Directory Server. slapd-client—install the Directory Server Console. This directive is required. It is recommended that you always install both components any time you install the Directory Server. ServerPortSpecifies the port the server will use for LDAP connections. For information on selecting server port numbers, see "Choose Unique Port Numbers" This directive is required. ServerIdentifierSpecifies the server identifier. This directive is required.This value is used as part of the name of the directory in which the Directory Server instance is installed. For example, if your machine's hostname is "phonebook" then this name is the default and selecting it will cause the Directory Server instance to be installed into a directory labeled "slapd-phonebook". SuffixSpecifies the suffix under which you will store your directory data. For information on suffixes, see "Determine your Directory Suffix". This directive is required. RootDNSpecifies the distinguished name used by the directory manager. For information on the directory manager, see "Defining Authentication Entities". This directive is required. RootDNPwdSpecifies the directory manager's password. This directive is required. Optional [slapd] Installation Directives
Table 4.3 Required [slapd] Installation Directives DirectiveDescription ComponentsSpecifies the slapd components to be installed. The slapd components are:slapd—install the Directory Server. slapd-client—install the Directory Server Console. This directive is required. It is recommended that you always install both components any time you install the Directory Server. ServerPortSpecifies the port the server will use for LDAP connections. For information on selecting server port numbers, see "Choose Unique Port Numbers" This directive is required. ServerIdentifierSpecifies the server identifier. This directive is required.This value is used as part of the name of the directory in which the Directory Server instance is installed. For example, if your machine's hostname is "phonebook" then this name is the default and selecting it will cause the Directory Server instance to be installed into a directory labeled "slapd-phonebook". SuffixSpecifies the suffix under which you will store your directory data. For information on suffixes, see "Determine your Directory Suffix". This directive is required. RootDNSpecifies the distinguished name used by the directory manager. For information on the directory manager, see "Defining Authentication Entities". This directive is required. RootDNPwdSpecifies the directory manager's password. This directive is required.
Table 4.3 Required [slapd] Installation Directives
You may provide the following directives when you use silent installation with Directory Server:
Table 4.4 Optional [slapd] Installation Directives DirectiveDescription AddSampleEntriesIf set to Yes, this directive causes the airius.ldif sample directory to be loaded. Use this directive if you are installing the Directory Server for evaluation purposes and you do not already have an LDIF file to populate your directory with. Default is no. AddOrgEntriesIf set to Yes, this directive causes the new Directory Server instance to be created with a suggested directory structure and access control. If this directive is used and InstallLdifFile is also used, then this directive has no effect. Default is no. InstallLdifFileCauses the contents of the LDIF file to be used to populate your directory. UseReplicationIf set to Yes, either SetupConsumer or SetupSupplier must also be specified. Default is no. SetupConsumerCauses this server to be set up as a consumer server. Valid values are:1—set up the consumer for supplier-initiated replication. See Table 4.5 for the list of directives you must use if you specify SetupConsumer=1.2—set up the consumer for consumer-initiated replication. See Table 4.6 for the list of directives you must use if you specify SetupConsumer=2.No—Do not set up the server to be a consumer. This is the default. SetupSupplierCauses this server to be set up as a supplier server. Valid values are:1—set up the supplier for supplier-initiated replication. See Table 4.8 for the list of directives you must use if you specify SetupSupplier=1.2—set up the supplier for consumer-initiated replication. See Table 4.9 for the list of directives you must use if you specify SetupSupplier=2.No—Do not set up the server to be a supplier. This is the default. Consumer Server [slapd] Installation Directives
Table 4.4 Optional [slapd] Installation Directives DirectiveDescription AddSampleEntriesIf set to Yes, this directive causes the airius.ldif sample directory to be loaded. Use this directive if you are installing the Directory Server for evaluation purposes and you do not already have an LDIF file to populate your directory with. Default is no. AddOrgEntriesIf set to Yes, this directive causes the new Directory Server instance to be created with a suggested directory structure and access control. If this directive is used and InstallLdifFile is also used, then this directive has no effect. Default is no. InstallLdifFileCauses the contents of the LDIF file to be used to populate your directory. UseReplicationIf set to Yes, either SetupConsumer or SetupSupplier must also be specified. Default is no. SetupConsumerCauses this server to be set up as a consumer server. Valid values are:1—set up the consumer for supplier-initiated replication. See Table 4.5 for the list of directives you must use if you specify SetupConsumer=1.2—set up the consumer for consumer-initiated replication. See Table 4.6 for the list of directives you must use if you specify SetupConsumer=2.No—Do not set up the server to be a consumer. This is the default. SetupSupplierCauses this server to be set up as a supplier server. Valid values are:1—set up the supplier for supplier-initiated replication. See Table 4.8 for the list of directives you must use if you specify SetupSupplier=1.2—set up the supplier for consumer-initiated replication. See Table 4.9 for the list of directives you must use if you specify SetupSupplier=2.No—Do not set up the server to be a supplier. This is the default.
Table 4.4 Optional [slapd] Installation Directives
The following tables show the directives you use if you specify the SetupConsumer directive.
If you are setting up a consumer server for use with supplier-initiated replication, use the following directives:
Table 4.5 Directives for SIR Consumer Server DirectiveDescription UpdateDNSpecifies the supplier DN for this server. That is, this is the distinguished name of the entry used to update this consumer server. Only entities binding to this server with this DN can write to a tree replicated from some other server. UpdatePwdPassword corresponding to the supplier DN (update DN). If you are setting up a consumer server for use with consumer-initiated replication, use the following directives:
Table 4.5 Directives for SIR Consumer Server DirectiveDescription UpdateDNSpecifies the supplier DN for this server. That is, this is the distinguished name of the entry used to update this consumer server. Only entities binding to this server with this DN can write to a tree replicated from some other server. UpdatePwdPassword corresponding to the supplier DN (update DN).
Table 4.5 Directives for SIR Consumer Server
Table 4.6 Directives for CIR Consumer Server DirectiveDescription CIRHostSpecifies the hostname on which the supplier server resides. This directive is required if you are installing a CIR consumer. CIRPortSpecifies the port number used for LDAP connections to the supplier server. This directive is required if you are installing a CIR consumer. CIRSuffixSpecifies the distinguished name of the tree that is pulled from the supplier server. This directive is required if you are installing a CIR consumer. CIRBindDNSpecifies the distinguished name that this consumer server will use when binding to the supplier server and obtaining updates. This distinguished name must have read, search, and compare privileges for the directory tree that the consumer is obtaining from the supplier, as well as for the supplier's changelog database. This directive is required if you are installing a CIR consumer. CIRBindDNPWPassword for the CIRBindDN. This directive is required if you are installing a CIR consumer. CIRSecurityOnA value of On causes the consumer server to use an SSL connection when obtaining updates from the supplier server. Default is off. CIRIntervalSpecifies the interval between update attempts. Units are in minutes, default is 10 minutes. A value of 0 causes the consumer server to always stay in synch (there is no interval between update attempts). CIRDaysSpecifies the days of the week on which replication can begin. Values are an integer, 0-6, representing a day of the week. That is, 0=Sunday, 1=Monday, 2=Tuesday, and so forth. To specify multiple days of the week, enter each integer with no delimiter between them. Thus, to replicate on Sunday and Wednesday, enter CIRDays=03. To replicate every day of the week, either use CIRDays=0123456, or do not specify this directive. CIRTimesSpecifies the range of time during which replication can begin. Specify times in 24 hour format. For example, CIRTimes = 0100-2300 allows replication to begin anytime between 1 a.m. and 11 p.m. To allow replication to begin at anytime during the day, use CIRTimes=0000-0000, or do not specify this directive. Supplier Server [slapd] Installation Directives
Table 4.6 Directives for CIR Consumer Server DirectiveDescription CIRHostSpecifies the hostname on which the supplier server resides. This directive is required if you are installing a CIR consumer. CIRPortSpecifies the port number used for LDAP connections to the supplier server. This directive is required if you are installing a CIR consumer. CIRSuffixSpecifies the distinguished name of the tree that is pulled from the supplier server. This directive is required if you are installing a CIR consumer. CIRBindDNSpecifies the distinguished name that this consumer server will use when binding to the supplier server and obtaining updates. This distinguished name must have read, search, and compare privileges for the directory tree that the consumer is obtaining from the supplier, as well as for the supplier's changelog database. This directive is required if you are installing a CIR consumer. CIRBindDNPWPassword for the CIRBindDN. This directive is required if you are installing a CIR consumer. CIRSecurityOnA value of On causes the consumer server to use an SSL connection when obtaining updates from the supplier server. Default is off. CIRIntervalSpecifies the interval between update attempts. Units are in minutes, default is 10 minutes. A value of 0 causes the consumer server to always stay in synch (there is no interval between update attempts). CIRDaysSpecifies the days of the week on which replication can begin. Values are an integer, 0-6, representing a day of the week. That is, 0=Sunday, 1=Monday, 2=Tuesday, and so forth. To specify multiple days of the week, enter each integer with no delimiter between them. Thus, to replicate on Sunday and Wednesday, enter CIRDays=03. To replicate every day of the week, either use CIRDays=0123456, or do not specify this directive. CIRTimesSpecifies the range of time during which replication can begin. Specify times in 24 hour format. For example, CIRTimes = 0100-2300 allows replication to begin anytime between 1 a.m. and 11 p.m. To allow replication to begin at anytime during the day, use CIRTimes=0000-0000, or do not specify this directive.
Table 4.6 Directives for CIR Consumer Server
The following tables show the directives you use if you specify the SetupSupplier directive.
Anytime you create a supplier server, you must configure a changelog database. Use the following directives for this purpose:
Table 4.7 Changelog Directives for Supplier Servers DirectiveDescription ChangelogDIRSpecifies the full path to the directory where your changelog database is stored. This parameter is required when you are configuring a supplier server. ChangelogSuffixSpecifies the suffix for the changelog database. This parameter is required when you are configuring a supplier server. Use the following directives to set up a supplier server for use with supplier-initiated replication:
Table 4.7 Changelog Directives for Supplier Servers DirectiveDescription ChangelogDIRSpecifies the full path to the directory where your changelog database is stored. This parameter is required when you are configuring a supplier server. ChangelogSuffixSpecifies the suffix for the changelog database. This parameter is required when you are configuring a supplier server.
Table 4.7 Changelog Directives for Supplier Servers
Table 4.8 Directives for SIR Supplier Servers DirectiveDescription SIRHostSpecifies the hostname of the consumer server to which this server will supply data. SIRPortSpecifies the port number of the consumer server to which this server will supply data. SIRSuffixSpecifies the distinguished name of the root point of the directory tree that you are supplying to the consumer server. SIRBindDNSpecifies the bind DN to use when supplying entries to the consumer server. Correspond's to the consumer's supplier DN. SIRBindDNPWSpecifies the password for the SIRBindDN. SIRSecurityOnA value of On causes the consumer server to use an SSL connection when sending updates to the consumer server. Default is off. SIRDaysSpecifies the days of the week on which replication can begin. Values are an integer, 0-6, representing a day of the week. That is, 0=Sunday, 1=Monday, 2=Tuesday, and so forth. To specify multiple days of the week, enter each integer with no delimiter between them. Thus, to replicate on Sunday and Wednesday, enter SIRDays=03. To replicate every day of the week, either use SIRDays=0123456, or do not specify this directive. SIRTimesSpecifies the range of time during which replication can begin. Specify times in 24 hour format. For example, SIRTimes = 0100-2300 allows replication to begin anytime between 1 a.m. and 11 pm. To allow replication to begin at anytime during the day, use CIRTimes=0000-0000, or do not specify this directive. Use the following directives to set up a supplier server for use with consumer-initiated replication:
Table 4.8 Directives for SIR Supplier Servers DirectiveDescription SIRHostSpecifies the hostname of the consumer server to which this server will supply data. SIRPortSpecifies the port number of the consumer server to which this server will supply data. SIRSuffixSpecifies the distinguished name of the root point of the directory tree that you are supplying to the consumer server. SIRBindDNSpecifies the bind DN to use when supplying entries to the consumer server. Correspond's to the consumer's supplier DN. SIRBindDNPWSpecifies the password for the SIRBindDN. SIRSecurityOnA value of On causes the consumer server to use an SSL connection when sending updates to the consumer server. Default is off. SIRDaysSpecifies the days of the week on which replication can begin. Values are an integer, 0-6, representing a day of the week. That is, 0=Sunday, 1=Monday, 2=Tuesday, and so forth. To specify multiple days of the week, enter each integer with no delimiter between them. Thus, to replicate on Sunday and Wednesday, enter SIRDays=03. To replicate every day of the week, either use SIRDays=0123456, or do not specify this directive. SIRTimesSpecifies the range of time during which replication can begin. Specify times in 24 hour format. For example, SIRTimes = 0100-2300 allows replication to begin anytime between 1 a.m. and 11 pm. To allow replication to begin at anytime during the day, use CIRTimes=0000-0000, or do not specify this directive.
Table 4.8 Directives for SIR Supplier Servers
Table 4.9 Directives for CIR Supplier Servers DirectiveDescription ConsumerDNSpecifies the distinguished name that a consumer server uses to pull data from this supplier server. Used only by CIR consumer servers. This distinguished name must have read, search, and compare privileges for the replicated tree as well as for the changelog database. ConsumerPwdSpecifies the password for the Consumer DN. [admin] Installation Directives
Table 4.9 Directives for CIR Supplier Servers DirectiveDescription ConsumerDNSpecifies the distinguished name that a consumer server uses to pull data from this supplier server. Used only by CIR consumer servers. This distinguished name must have read, search, and compare privileges for the replicated tree as well as for the changelog database. ConsumerPwdSpecifies the password for the Consumer DN.
Table 4.9 Directives for CIR Supplier Servers
[admin] installation directives specify information of interest only to your Directory Server's Administration Server. That is, this is the installation information required for the Administration Server that is used to manage the Directory Server instance that you are currently installing.
The [admin] installation directives are:
Table 4.10 [admin] Installation Directives DirectiveDescription ComponentsSpecifies the admin components to be installed. The base components are:admin—install the Administration Server. You must install the Administration Server if you are also installing some other Netscape server. admin-client—install Netscape Console. Specify just this component if you are installing Netscape Console as stand-alone. Do not install this component if you will remotely manage your servers and the console will be installed somewhere else on your network. SysUserUnix only. Specifies the user that the Administration Server will run as. For default installations that use the default Netscape port numbers, this user must be root. Root is the default. For information on what users your servers should run as, see "Decide Which User and Group to Run Netscape Servers As (Unix only)" PortSpecifies the port that the Administration Server will use. Note that the Administration Server's host name is given by the FullMachineName directive. For more information on FullMachineName, see Table 4.1. ServerAdminIDSpecifies the administration ID that can be used to access this Administration Server if the configuration directory is not responding. The default is to use the value specified by the ConfigDirectoryAdminID directive. See "Defining Authentication Entities" for information on this directive. ServerAdminPwdSpecifies the password for ServerAdminID. ServerIPAddressSpecifies the IP address that the Administration Server will listen to. Use this directive if you are installing on a multi-homed system and you do not want to use the first IP address for your Administration Server.
Table 4.10 [admin] Installation Directives
Previous
