Temporarily disable any screen savers and turn off any virus-detection software.
Default installing directory
Windows
c:\lotus\domino
Unix
/opt/ibm/lotus
You should point the location of notes.ini before running server
(I usually run server on the directory of notes.ini)
Silent install
Windows
Setup command
setup.exe -silent [Silent install with default selections and options]
setup.exe -options-template c:\temp\file.txt [Creating a Response file]
setup.exe -options-record c;\temp\file.txt [Recording a response file]
setup.exe -silent -options c:\temp\file.txt [Silent install using response file]
You can get the sample_response.txt on the installing CD. [You can modify it for meeting your request.
setup.exe -express [You can install Domino very fast]
Unix
You should copy the unix_response.dat/remote_response.dat to a new file unix_response1.dat/remote_response.dat
edit unix_response1.dat/remote_response1.dat
run
./install -script /tmp/unix_response1.dat [on local]
./install -script /tmp/remote1_response1.dat [on remote such as by putty]
concurrent I/O (CIO) and direct I/O (DIO) not support on Domnio servers on AIX
The configure procedure
Note: Domino first server setup creates IDs with a default public key width of 1024 bits. If a different key width is required, run SETUP.EXE to install the Domino files but before starting the server, open the server’s NOTES.INI file, and then set SETUP_FIRST_SERVER_PUBLIC_KEY_WIDTH to the desired key width. For example, for Domino R5-compatible keys, install the files for the Domino server by running SETUP.EXE, but before starting the server, open the NOTES.INI file and then set
SETUP_FIRST_SERVER_PUBLIC_KEY_WIDTH=630. The public key width can be set to either 630 or 1024
when using the NOTES.INI variable.
Setting up the first Domino server does the following:
v Creates a Domino domain.
v Creates the certification log file, names it CERTLOG.NSF, and saves it in the Domino data directory.
Chapter 3. Installing and Setting Up Domino Servers 59
v Uses the PUBNAMES.NTF template to create the Domino Directory for the domain, names the
directory NAMES.NSF, and places it in the Domino data directory.
v Creates an organization certifier ID, names it CERT.ID, and saves it in the Domino data directory.
v Optionally creates an organizational unit certifier ID, names it OUCERT.ID, and stores it in the Domino
Directory.
v Creates a Certifier document, which describes the organization certifier ID, in the Domino Directory.
v Creates a server ID, names it SERVER.ID, and saves it in the Domino data directory.
v Uses the organization certifier ID to certify the server ID.
v Creates a Server document in the Domino Directory and includes in it information that you specified
during the setup program.
v Creates a Person document in the Domino Directory for the Domino Administrator that you specified
during the setup program.
v Creates a user ID and password for the Domino Administrator and attaches it as a file named USER.ID
to the administrator’s Person document in the Domino Directory.
v Uses the organization certifier ID to certify the administrator’s user ID.
v Gives the administrator and the server Manager access in the ACL of the Domino Directory.
v Adds the server name to the LocalDomainServers group in the Domino Directory.
v Creates the log file, names it LOG.NSF, and saves it in the Domino data directory.
v Enables the appropriate network and serial ports.
v Creates a mail directory in the Domino data directory and creates a mail file in that directory for the
Domino Administrator.
v Creates the Reports file, names it REPORTS.NSF, and saves it in the Domino data directory.
v Updates network settings in the Server document of the Domino Directory.
v Configures SMTP, if selected during the setup program.
v If ″DOLS Domino Off Line Services″ was selected during the setup program, creates the Off-Line
Services file, names it DOLADMIN.NSF, and saves it in the Domino data directory,.
v Updates the Access Control List in all databases and templates in the Domino data directory tree toremove Anonymous access and/or add LocalDomainAdmin access, depending on the selections made during the setup program.
v Configures xSP Service Provider information, if selected during the install program.
Setting up an additional Domino server does the following:
v Copies the Domino Directory, if a file location was specified during the setup program, names it
NAMES.NSF, and saves it in the Domino data directory.
v Dials the existing Domino server if the connection is made through a modem (possible only on
Windows systems).
v Copies the server’s ID from the location specified during the setup program, either from a file, a copy
of the directory, or the existing Domino server’s directory; names it SERVER.ID; and saves it in the
Domino data directory.
v Retrieves the Domain name and Administrator name from the Server document in the Domino
Directory.
v Creates the log file, names it LOG.NSF, and saves it in the Domino data directory.
v Copies or replicates the Administration Requests file, names it ADMIN4.NSF, and saves it in the
Domino data directory.
v Copies or replicates the Monitoring Configuration file, names it EVENTS4.NSF, and saves it in the
Domino data directory.
v Replicates the Domino Directory, if it doesn’t already exist, names it NAMES.NSF, and saves it in the
Domino data directory.
v Creates a Connection document to the existing Domino server in the Domino Directory.
60 Lotus Domino Administrator 7 Help
v Creates the Reports file, names it REPORTS.NSF, and saves it in the Domino data directory.
v Updates network settings in the Server document of the Domino Directory.
v Configures SMTP, if selected during the setup program.
v If ″DOLS Domino Off-Line Services″ was selected during the setup program, creates the Off-Line
Services file, names it DOLADMIN.NSF, and saves it in the Domino data directory.
v Updates the Access Control List in all databases and templates in the Domino data directory tree to
remove Anonymous access and/or add LocalDomainAdmin access, depending on the selections made
during the setup program.
v Configures xSP Service Provider information, if selected during the install program.
v Replicates changes made to the Server document with the existing server, if any.
v Removes the SERVER.ID attachment from the Domino Directory, if applicable.
Configure DOLS (Domino off-line services) during Domino server setup.
1.Under "setup internet services for" select "Web Browsers (HTTP Services)," and then click Customize.
2.In the "Domino tasks" list, select "DOLS Domino Off-Line services".
At the end of setup, when you have the option to create an access control list entry, add the group LocalDomainAdmins to all databases and templates.
4.Accept the default option "Prohibit Anonymous access to all database and templates." If you deselect this option, you must open the ACL for each DOLS application and assign No Access to Anonymous.
Configure DOLS manually
open-server document-internet protocols-HTTP
Fill the proper name in the DSAPI filter file name that corresponds to the OS that the server is running.
Restart Domino server.
[ Win32-ndolextn
Linux-libdolextn
AIX-libdolextn
Solaris/Sparc -libdolextn
S390-libdolextn
iSeries-libdolextn
]
Create a DOLADMIN.nsf database from template DOLADMIN.NTF
Restart Domino server.
Open DOLADMIN.nsf.
Configure DOLS use web sit documents
DWA+ Sametime [ I haven't tested sametime. I will create a new topic for samtime later]
Setting up Domino Web Access on a server
Domino Web Access provides Notes users with browser-based access to Notes mail and Notes calendar
and scheduling features. Using Domino Web Access, a user can send and receive mail, view the calendar,
invite people to meetings, create to do lists, keep a notebook, and work off line.
To set up Domino Web Access, choose ″Web Browsers (HTTP Web services)″ during Server Setup. If you
want to give users the ability to work off line, also choose Domino Off-Line Services (DOLS). DOLS is
not required to run Domino Web Access.
Note: When providing a Domino domain name, do not use a period. For example, use AcmeProduction
as a domain name instead of Acme.Production.
In the Domino Administrator, make sure that the Fully Qualified Domain name (FQDN) (such as
acme.lotus.com) is specified on the Basics tab of the Server document.
Setting up Domino Web Access with Sametime
Domino Web Access (DWA) integrates an instant messaging (IM) capability so that users can chat with
their co-workers online and maintain an instant messaging list that shows the online status of other users.
The instant messaging awareness feature also displays online status next to the names of people in mail
messages, views and folders.
There are two versions of Sametime available for Domino 7.0, however these instruction apply to both
version. References to the Sametime server also apply to installing the limited use version. The two
versions are:
v IBM Lotus Instant Messaging Limited Use -- the default instant messaging capability that is included in
Domino 7.0.
v IBM Lotus Sametime® -- the full instant messaging product that includes Web conferencing capabilities.
It is available only if your organization purchased it.
For complete information on installing IBM Lotus Sametime, see the IBM Lotus Sametime 7.0 Installation
Guide for your operating system, and the IBM Lotus Sametime 7.0 Administrator’s Guide. To view or
download the Sametime documentation, go to http://www.lotus.com/LDD/doc.
Configuration Notes:
v For Mozilla, you must have at least Sametime 3.1 to run instant messaging integration. Previous
versions of Lotus Sametime are not supported in Domino Web Access on Mozilla.
v When you install Domino 7.0, the stlinks files that are installed in the stlinks directory (for example,
C:\st\domino\Data\domino\html\sametime\stlinks), are overwritten. If you have modified stlinks
files (for example, if the Sametime server is configured for tunneling) these files will be replaced. When
you are upgrade to 7.0, these files are backed up in a file called stlinks.sav. For additional information,
see the topic Customizing STLinks files for tunneling or reverse proxy servers.
v To access the Sametime server using a protocol that is different from the current Web page’s protocol,
use the NOTES.INI configuration setting iNotes_WA_SametimeProtocol.
v Sametime integration with Domino Web Access is not supported with JRE 1.4.1.
Part 1 - Set up Domino Web Access on a Domino server:
1. Set up Domino Web Access on a server by making the appropriate selections during server setup.
2. Register users with the Domino Web Access (DWA7.NTF) mail template.
Chapter 3. Installing and Setting Up Domino Servers 63
Part 2 - Set up the Sametime server: If possible, the Sametime server should be in the same Domino
domain as the Domino Web Access server. Follow the instructions in the IBM Lotus Sametime 7.0
Installation Guide to install and configure instant messaging on a dedicated Domino server in the same
Domino domain as the Domino Web Access server.
If the Sametime server is in a different domain than your Domino Web Access server, follow the
instructions in Setting up Sametime and Domino Web Access in different domains.
Make sure the Sametime server is functioning properly before proceeding. If you have multiple Sametime
servers in a single community, also make sure that Domino single sign-on (SSO) is functioning properly
between the servers. For complete information on working with multiple Sametime servers, see the IBM
Lotus Sametime 7.0 Administrator’s Guide, available on http:\\www.lotus.com/ldd/doc.
Part 3 - Create Connection documents: You need Connection documents for the Domino Web Access
and the Sametime server if the Sametime server is not in the same domain as the Domino Web Access
server. Also, if the Sametime server is in the same domain as the Domino Web Access server, but is not
clustered with the registration server, you need a Connection document in order to replicate the Domino
Directory.
Create Connection documents using the standard procedure, and include the information below:
On the Domino Web Access server:
v Enter the Sametime server’s name in the ″Destination server″ field. For example: Sametime/Acme.
v Enter the Domino Web Access server’s name in the ″Source domain″ field.
v Enter the Sametime server’s name in the ″Destination domain″ field.
On the Sametime server:
v Enter the Domino Web Access server’s name in the ″Destination server″ field.
v Enter the Sametime server’s name in the ″Source domain″ field.
v Enter the Domino Web Access server’s name in the ″Destination domain″ field.
Part 4 - Specify the Sametime server for Domino Web Access users: There are two ways to specify a
Sametime server for Domino Web Access users. You can edit the Configuration Settings document for the
Domino Web Access server, or you can edit the person document for each user who uses instant
messaging.
Method 1
To enable instant messaging and set the Sametime server for all Domino Web Access users at one time,
use the Instant Messaging settings in the Configuration Settings document, Domino Web Access tab. After
you have done this, individual users can enable or disable instant messaging on their local Domino Web
Access clients by setting a User Preference.
Method 2
If you choose not to enable instant messaging for all users, then you must edit the person document for
each user who will use instant messaging:
1. From the Domino Administrator, click the People & Groups tab.
2. Select the Domino Web Access Domino directory, then click People.
3. Double-click a name to open the user’s Person document.
4. Click Edit.
5. Enter the name of the Sametime server in the ″Sametime server″ field. For example,
Sametime/Sales/Acme/UK.
6. Click ″Save & Close.″
7. Repeat Steps 3 though 6 for each person.
Part 5 - Set up Domino Web SSO authentication between the DWA server and IM server: Domino
single sign-on (SSO) authentication allows Web users to log in once to a Domino or WebSphere server,
and then access any other Domino or WebSphere server in the same DNS domain that is enabled for
single sign-on (SSO) without having to log in again. In a multiple server environment, it is possible that
one or more servers in your Domino domain are already configured for Domino SSO, and the Domino
Directory already contains a Domino Web SSO configuration document. When you install Sametime, it
creates a Web SSO configuration document called LtpaToken unless one already exists in the Domino
directory. If an LtpaToken configuration document already exists, Sametime does not attempt to alter it.
For more information about Domino Web SSO authentication, see the topic Multi-server session-based
name-and-password authentication for Web users (single sign-on).
Configure the Domino Web Access server for Web SSO
Complete the steps in this section if your DWA server is not configured for Web SSO, and you want to
use the Web SSO document that Sametime created to configure it.
1. Ensure that the Domino Directory has replicated throughout the Domino domain since you installed
Sametime.
2. Update the Web SSO Configuration document that was created when you installed Sametime
(LtpaToken):
a. Open the Domino Directory and select the Configurations - Web - Web Configurations view.
b. From within this view, expand the list of Web SSO Configurations.
c. Open the ″Web SSO Configuration for LtpaToken″ document in edit mode. (If you are unable to
edit the document, record the settings in the document, and then delete it and create a new one.)
d. Update these fields if necessary:
Domino Server Names -- make sure this field contains the name of all of the DWA servers and
Sametime servers that should participate in Single Sign-on.
DNS Domain -- make sure this is the fully-qualified domain name of the DWA and Sametime
server.
e. Click Save & Close.
3. Enable single sign-on and basic authentication in the Server document for the DWA server as
described in Enabling single sign-on and basic authentication. When you update the Web SSO
Configuration field, select LtpaToken from the list.
4. Ensure that the updates replicate to all of the servers in the domain.
Update Domino Web Access server Web SSO configuration
Complete the steps in this section if your DWA server is already configured for Domino Web SSO. You
must add the Sametime server to your configuration:
1. Update your existing Domino Web SSO Configuration document.
a. Open the Domino Directory and select the Configurations - Web - Web Configurations view.
b. From within this view, expand the list of Web SSO Configurations.
c. Open the Domino Web SSO document that you are using for your DWA server in edit mode.
d. Update these fields if necessary:
Domino Server Names -- make sure this field contains the name of all of the DWA servers and
Sametime servers that should participate in Single Sign-on.
DNS Domain -- make sure this is the fully-qualified domain name of the Sametime server.
e. Click save & Close.
2. Update the Server document for the Sametime server.
a. Open the server document.
b. Click Internet Protocols - Domino Web Engine, and select the Web SSO Configuration field.
c. From the drop-down list, select the Web SSO Configuration that you are using for the DWA server.
d. Click Save & Close.
3. Ensure that the updates replicate to all of the servers in the domain.
Although Domino SSO is the preferred authentication method, you can continue to use secrets and
tokens authentication databases, if you are already using them. For example, if any of the servers in your
domain is configured for something other than multiple server SSO, (single server SSO for example) you
must use secrets and tokens authentication. For information on setting up Secrets and Tokens
authentication, see the topic Setting up Secrets and Tokens authentication for instant messaging in
Domino Web Access.
Part 6 - (for mixed environments only) Copy the SametimeApplet folder on the Domino Web Access
server to the Sametime server: For a mixed environment, in which the users’ mail files are based on the
INOTES5.NTF mail template, and they are using Domino Web Access Chat, you must copy the
SametimeApplet folder from the Domino Web Access server to the same location on the Sametime server.
On the Domino Web Access server, the applets are located in the \domino\html
directory.
Note: Chat is the Domino Web Access feature that provided awareness and allowed people to chat with
co-workers in Domino Web Access prior to 6.5.2. To use Chat, you must also lower the value of the
instant messaging security setting in the SAMETIME.INI file to allow a connection from an older client.
For iNotes5 and iNotes6 mail templates, use VP_SECURITY_LEVEL=20. For more information on
specifying the minimum security level, see the IBM Lotus Sametime 7.0 Installation Guide (available on
http://www.lotus.com/LDD/doc), which details this setting.
Part 7 - Verify that instant messaging works with Domino Web Access:
1. Make sure that replication is complete, the Person documents exist on the Sametime server, and that
the updated Web SSO document exists on all of the servers that will participate in single sign-on..
2. If you have not already done so, follow the instructions in the IBM Lotus Sametime 7.0 Installation
Guide to verify that instant messaging is working properly before you test whether it is working with
Domino Web Access clients.
3. Launch Domino Web Access in a browser. In any view or document in which online awareness
appears, click the Active status icon of the person you want to chat with to test the instant messaging
connection.
Note: If the instant messaging status does not appear next to the Welcome username text in Domino Web
Access, check the user’s Person document in the Domino directory. If you configured the Sametime server
by populating this document, make sure the ″Sametime server″ field is correct (Basics tab, under
Real-Time Collaboration).
Setting up Secrets and Tokens authentication for instant messaging in Domino
Web Access
If you want to use Secrets and Tokens authentication databases for your instant messaging security
instead of Domino Single Sign-On (SSO) Authentication, you must Create a one-time replica of the
Tokens database on the Domino Web Access server. When you do this, remember that file names are case
sensitive on UNIX, so the Secrets database name must be entered exactly as STAuthS.nsf.
To replicate STAuthS.nsf from the Sametime server to the Domino server directory:
1. Using a Notes client, choose File - Database - Open.
2. Enter the name of the Sametime server (for example, Sametime/Acme).
3. Enter the Secrets database filename: STAuthS.nsf
4. Click Open.
5. Choose File - Replication - New Replica.
6. Enter the name of the Domino Web Access server (for example, iNotes/Acme)
7. Ensure that the database is replicated to the data directory: ...\domino\data\stauths.nsf.
8. Click OK to create the replica.
Note: After you have replicated stauths.nsf from your Sametime server to your Domino server, open the
Replication Settings dialog box for the database, click Other, and check the ″Temporarily disable
replication for this replica″ box. This will prevent another version of the database from a Windows
system from overwriting your name change (using uppercase and lowercase letters) for the UNIX server.
Customizing STLinks files for tunneling or reverse proxy servers
If your Sametime server is configured for tunneling or if you are using reverse proxy servers in your
environment, you may need to customize some files on both your DWA server and your Sametime
server.
Using a custom port for tunneling: If the Sametime server is configured for tunneling on port other
than 8082, you must modify the stlinks.js file on both the Sametime server and the DWA server.
1. Locate the following directory on your Sametime server. This directory contains both the stlinks.js file
and the hostinfo.js file.
2. Copy the following two lines from the Hostinfo.js file to the beginning of the stlinks.js file (by default,
there are only 2 lines in the Hostinfo.js file):
var HTTP_TUNNELING_PORT=xx;
var TUNNELING_ADDRESS="";
The values you see for these variables in the hostinfo.js file should match your Sametime server
tunneling configuration. For releases after 2.5, Sametime normally creates and automatically updates
the content of these files on the Sametime server.
3. Save the updated stlinks.js file on the Sametime server.
Note: When you upgrade your Sametime server to a later release, the stlinks.js file is replaced with
the default version and you must perform steps 1-3 again to update the file. It is also possible that
installing a Sametime fix pack may make it necessary to restore the updates.
4. Copy the updated stlinks.js file from the Sametime server to the DWA server, replacing the existing
stlinks.js file in
Note: If the DWA server is running on i5/OS, make sure that the owner of the stlinks.js file is set to
QNOTES.
Using reverse proxy servers: If your network environment uses reverse proxy servers to protect the
identities of servers behind a firewall, you may need to modify the stlinks.js file on both the DWA server
and the Sametime server.
You must modify the stlinks.js file if you want DWA users to be able to connect to the Sametime
community inside the intranet even if they are outside the firewall. Stlinks.js is located in the following
directory on each server:
Two variables that provide reverse proxy support are included in stlinks.js:
ll_RProxyName - the reverse proxy name
ll_AffinityId - the Sametime server affinity ID
To enable reverse proxy support, the server administrator must replace the defaults with appropriate
values and uncomment the lines. For example:
var ll_RProxyName="https://proxy.ibm.com";
var ll_AffinityId="st1";
Make sure you update the stlinks.js file on both the DWA server and the Sametime server.
For more information about reverse proxy support, see the IBM Lotus Sametime 7.0 Installation Guide
(available on http://www.lotus.com/LDD/doc).
Once you have customized the contents of the stlinks.js files, there are some issues related to future
server upgrades that you need to be aware of:
v When you upgrade Domino to a new release, the customized STLinks files may be replaced, and
DWA-Sametime integration to stop working. This can occur when you upgrade Domino on either the
DWA server or the Sametime server.
In recent Domino releases, the original contents of the STlinks directory are backed up to the following
directory before the files are replaced:
Windows:
AIX and Solaris:
i5/OS:
After you upgrade Domino on either the DWA server or the Sametime server, restore any stlinks.js
customizations from the file in the backup directory to the file in the stlinks directory.
v When you update the level of Sametime by installing a newer release of Sametime or applying a fix
pack, it is possible that you will also need to copy the newer version of the stlinks directory to your
DWA server. Make sure you check the documentation that accompanies the Sametime update to
determine if this is necessary. If this occurs, you will need to reapply your stlinks.js customizations on
each of the servers.
Setting up Sametime and Domino Web Access in different domains
If you prefer to use Web single sign on (SSO) authentication, see the topic Setting up the Web SSO
Configuration document for more than one Domino Domain.
To set up a cross-domain configuration when the Sametime server and the Domino Web Access server are
located in different domains:
1. Cross certify both domains with each other.
2. Configure Directory Assistance on the Sametime server.
3. If you have set up single sign on (SSO), go to Step 4. If you do not have SSO set up, replicate
STAuthS.nsf to the Domino Web Access Server (file name is case sensitive on UNIX servers).
4. Create a server document for the Sametime server in the Domino Directory of the Domino Web
Access server, completing the fields below. Another way to do this is to edit Configuration Settings
document, Domino Web Access tab, and enter the Sametime server name in the in the field ″Set an
instant messaging server hostname for all DWA users.″ If you use this setting, you do not need to
complete Step 5.
v Server name
v Domain name
v Fully qualified Internet host name
v Is this a Sametime server?
5. Enter the Sametime server name in the Sametime Server field of each Domino Web Access user’s
Person document.
Note: If the Sametime server is configured using a port other than the default port, then the ″Fully
Qualified Hostname″ field must contain hostname:port.
For complete information on working with multiple Sametime servers, see the IBM Lotus Sametime 7.0
Administrator’s Guide, available on http://www.lotus.com/LDD/doc.
Troubleshooting Sametime in Domino Web Access
If instant messaging icons do not display in Domino Web Access mail and the Contact List, check the
following:
v The Sametime server is up running. To make sure stlinks is running normally, you can check the
Sametime server directory \trace\stlinks.txt log file.
v All the ST**** services are up running. Check the control panel - services; all ST**** services should be
running when the Sametime server has fully started. If there are ST**** services not running, start
STCommunity server first. If this service cannot be started, check the network connections and the
Sametime server log file.
v Make sure the \stlinks directory and the files are on both the Sametime server and application server
directories.
v When you update the level of Sametime by installing a newer release of Sametime or applying a fix
pack, it is possible that you will also need to update the stlinks files on your DWA server. Make sure
you check the documentation that accompanies the Sametime update.
v If you had previously customized the STLinks files and have recently upgraded either your Sametime
server or your Domino Web Access server to a new version of Domino, the customized files may have
been replaced. See the topic Customizing STLinks files for tunneling or Reverse Proxy servers.
v Make sure the user has enabled Instant Messaging in Preferences.
v Make sure the user’s Person document has been set up with the Sametime server names.
v Use the http:// protocol only for the Sametime server.
To identify the current Sametime server version:
1. Type the following URL: http://
running on a Windows platform. To avoid case sensitive issues on other platforms, search for the file
under
2. At the bottom of the page, click Administer the Server.
3. Login to Instant Messaging, and then click Help - About Sametime.
Browser Address: The instant messaging integration features rely on the ability of the browser to
directly communicate with the Sametime server. This means that the fully-qualified Internet hostname of
the Sametime server must be resolvable from the browser (for example, the fully qualified Internet
hostname for a Domino server named IM/Acme might be im.acme.com).
Therefore, either DNS must be able to resolve this address or it must be resolved to the proper IP address
by some other mechanism (such as editing of the local operating system’s hosts file).
Enabling automatic server setup from the script file
Open your script file
Change the variable: start _server_setup =
(0 To disable automatic server setup
1 To enable automatic launch server setup afer installation or to automatically restart the server after a server upgrade
2 To automatically launch server setup in listen mode after installing a new server. you can then connect to the server using the remote server setup tool. To automatically restart the server after installing a server upgrade.)
Note:
we need add the parameter in the script.dat before instlling Domino by command.
Using the Domino Server setup program remotely
Sratr->all programs->Lotus applications->Remote server setup (Default port is 85850
First you should run
nserver -lsten (Windows)
server -listen (Unix)
Notes:
You should run server on the notesdata directory where the notes.ini locate in.
My profile
You should rut server by a user who doesn't belong root.
Install Domino on Unix and Unix enviroument settings
http://arthur-w.blogspot.com/2008/07/ubuntu-ubuntu-wget-vsftpd-domino-801.html
Use remote server setup from a windows client without Domino administrator, or from a UNIX work station.
Copy cfgdomserver.jar jhall.jar remotesetup.cmd from the Domino server of directory to C:\temp (X:\Program Files\Lotus\Domino) Run remotesetup.cmd (Windows)
Copy cfgdomserver.jar jhall.jar remotesetup from the Domino server of directory to \temp (/opt/ibm/lotus/notes/80010/linux)
run
chmod 755 cfgdomserver.jar
chmod 755 jhall.jar
chmod 755 remotesetup
./ remotesetup
You can run the following command on domino server for remote installing Domino server.
nserver -remote (windows)
server -remote (Unix)
Creating a server setup profile
On server
nserver -record (Windows)
server -record (Unix)
On Domino administrators client
serversetup -record
On without Domino administrator, or from a UNIX work station.
Copy cfgdomserver.jar jhall.jar remotesetup.cmd from the Domino server of directory to C:\temp (X:\Program Files\Lotus\Domino) Run remotesetup.cmd (Windows)
Copy cfgdomserver.jar jhall.jar remotesetup from the Domino server of directory to \temp (/opt/ibm/lotus/notes/80010/linux)
run
chmod 755 cfgdomserver.jar
chmod 755 jhall.jar
chmod 755 remotesetup
remotesetup.cmd -record (Windows)
remotesetup -record (Unix)
Use a setup profile at the server
nserver -playback (Windows)
server -playback (Unix)
Click browser select record file.
To use a setup profile from a windows client with Domino Adminstrator
Run serversetup -playback
on the directory where the Domino Administrator have been installed.
On without Domino administrator, or from a UNIX work station.
Copy cfgdomserver.jar jhall.jar remotesetup.cmd from the Domino server of directory to C:\temp (X:\Program Files\Lotus\Domino) Run remotesetup.cmd (Windows)
Copy cfgdomserver.jar jhall.jar remotesetup from the Domino server of directory to \temp (/opt/ibm/lotus/notes/80010/linux)
run
chmod 755 cfgdomserver.jar
chmod 755 jhall.jar
chmod 755 remotesetup
remotesetup.cmd -playback (windows)
remotesetup -playback (Unix)
Silent setup
You should run the following command on Domino server.
nserver -silent c:\myprofile.pds (Windows)
server -silent /myprofile.pds (unix)
(Myprofile is the name you gave to the profile file)
If the profile uses existing server, certifier, or administrator IDs that require passwords,do the following
a. Create a test file that contains the passwords for existing IDs. The keyword in this are:
Server=
Addserver=
Certifier=
OUCertifier=
Administrator=
b. Add a parameter in the command line for the name of password file.
nserver -silent c:\myprofile.pds c:\passwd.txt (Windows no partitioned server setup)
nserver -silent c:\myprofile.pds c:\passwd.txt =c:\lotus\domino\data2\notes.ini (Windows with partitioned server setup)
You can check errorlog.txt in the domino data directory to confirm that the setup is complete or to view any error messagas that were generated during setup.
To do silent setup server on Domino administrators client
serversetup -silent c:\myprofile.pds -remote serveraddress
If the profile uses existing server, certifier, or administrator IDs that require passwords,do the following
a. Create a test file that contains the passwords for existing IDs. The keyword in this are:
Server=
Addserver=
Certifier=
OUCertifier=
Administrator=
b. Add a parameter in the command line for the name of password file.
serversetup -silent c:\myprofile.pds c:\passwd.txt -remote serveraddress (Windows no partitioned server setup)
serversetup -silent c:\myprofile.pds c:\passwd.txt -remote serveraddress =c:\lotus\domino\data2\notes.ini (Windows with partitioned server setup)
You can check errorlog.txt in the domino data directory to confirm that the setup is complete or to view any error messagas that were generated during setup.
To do a silent setup on without Domino administrator, or from a UNIX work station.
Copy cfgdomserver.jar jhall.jar remotesetup.cmd from the Domino server of directory to C:\temp (X:\Program Files\Lotus\Domino) Run remotesetup.cmd (Windows)
Copy cfgdomserver.jar jhall.jar remotesetup from the Domino server of directory to \temp (/opt/ibm/lotus/notes/80010/linux)
run
chmod 755 cfgdomserver.jar
chmod 755 jhall.jar
chmod 755 remotesetup
remotesetup.cmd c:\myprofile.pds -remote serveraddress (windows)
remotesetup \temp\myprofile.pds -remote serveraddress (Unix)
If the profile uses existing server, certifier, or administrator IDs that require passwords,do the following
a. Create a test file that contains the passwords for existing IDs. The keyword in this are:
Server=
Addserver=
Certifier=
OUCertifier=
Administrator=
b. Add a parameter in the command line for the name of password file.
remotesetup.cmd -silent c:\myprofile.pds c:\passwd.txt -remote serveraddress (Windows no partitioned server setup)
remotesetup.cmd-silent c:\myprofile.pds c:\passwd.txt -remote serveraddress =c:\lotus\domino\data2\notes.ini (Windows with partitioned server setup)
You can check errorlog.txt in the domino data directory to confirm that the setup is complete or to view any error messagas that were generated during setup.
Server registration
When you register a server, Domino does the following
1) Create a server ID for the new server in the Domino Directory
2)Create a Server document for the new server and certifies it with the certifier ID
3)Encrypts and attaches the server ID to the Server Document and saves the ID on a disk or in a file on the server.
4)Adds the server name to the LcoalDomainServers group in the Domino Directory
5)Creates a n entry for the new server in the Certifivation Log (CERTLOG.NSF)
When you register a server by CA, Domino does the following
1)The registration process ccreates a certificate request in the Administration Request database (ADMIN4.nsf) to be processed by the server's internet CA.
2)The registratiron process creates a "create SSL key ring" request ADMIN4.NSF
3)Once you set up and start the new server and the "create SSL keying" request has replicated to it, the "create SSL key ring" request creats the server key ring file and an "enable SSL ports" request for the administration server of the Domino direcrtory.
4)The "enable SSL ports" request enables all the SSL ports on the new server ans creates a "monitor SSL status" request for the new server.
5)The "monitor SSL status" requests restarts all of the internet tasks currentlu running on the new server so that the tasks will accpet SSL connections.
Registering a server
From the Domino Administrator
Configure->tools->Registration Server
Select cert.id -> Enter pasword of cert.id
Fill the proper information. Click continue
In the register New Servers dailog box, complete the proper fields for each server that you want to register.
Creating an addtional organization certifier ID
From Domino Administrator ->Configuration
Toos->Registration-> Organization->Select the proper server->
fill the proper information.
Click OK
Creating an organization unit certifier ID
Configuration -> Registration -> Organization Unit.
Select the server which the OU belongs to.
Internet Site documents
Create an internet Site document
Domino Administrator->configuration->Web->internet Sites->Add internet Site
fill the proper information
Click Save.
Enabling Internet Sites on a server
Configure->basics->enable "Loads internet configuration from server/internet sites documents"
Save
有谁知道 internet Site document 在生产环境中怎么用。
请告知我谢谢。
没有评论:
发表评论