The dominstall command

Edit online

When you run dominstall, certain files and links are created. The profile file that is created contains the environmental variables and the alias for running Data Protection for HCL Domino.

Files and links created

For each Domino partition that you configure, the dominstall program creates the following files in the Data Protection for HCL Domino installation directory:

domdsmc_
domdsmc_/domdsmc
domdsmc_/.profile
domdsmc_/domdsm.cfg
domdsmc_/dsm.sys.additions
domdsmc_/dsm.sys.changes

Note: A dsm.opt file is not generated automatically with dominstall, you must create this file. The DSMI_CONFIG environment specified the full name of the dsm.opt file.

The following links are created in the Domino /bin and executable directories:

/opt/lotus/bin/domdsmc_ -> tools/startup
/opt/lotus/notes/latest/ibmpow/domdsmc_ ->
/opt/tivoli/tsm/client/domino/bin/domdsmc_/domdsmc
/opt/lotus/bin/domdsmc -> tools/startup
/opt/lotus/notes/latest/ibmpow/domdsmc ->
/opt/tivoli/tsm/client/domino/bin/domdsmc
/opt/lotus/bin/dsmdomp -> tools/startup ->
/opt/tivoli/tsm/client/domino/bin/dsmdomp

Data Protection for HCL Domino is set up to start with the Domino startup script, tools/startup.

The dsmdomp file is the Data Protection for HCL Domino plug-in executable file for the web client GUI

Environment variables

After you run the dominstall program, the Notes user ID that runs Data Protection for HCL Domino includes the environment variables that are shown in the profile file. The profile file sets the environment so that for each partition the command domdsmc resolves to /opt/lotus/bin/domdsmc_. The profile file also sets the environment so that each partition uses its own Data Protection for HCL Domino preferences files.

When the alias is defined in the profile file, you can run Data Protection for HCL Domino by issuing the domdsmc command. When the alias is not set in the profile file, run the following command:

/opt/lotus/bin/domdsmc_

Running dominstall on an existing version

If Data Protection for HCL Domino is installed over a previous version, the dominstall program creates links so that changes to the existing environment are not required. The following links are created:

/opt/lotus/bin/domdsmc -> /opt/lotus/notes/latest/ibmpow/domdsmc

/opt/lotus/notes/latest/ibmpow/domdsmc -> /usr/tivoli/tsm/client/domino/bin64/domdsmc

You can remove these symbolic links if Data Protection for HCL Domino is not installed over a previous version.

Notes user IDs

The dominstall program sets the ownership of all the files in the Data Protection for HCL Domino installation directory to the Notes user. If multiple partitions with unique UNIX and Linux user IDs are configured, verify that each Notes user has appropriate access to the configuration files. To ensure appropriate access, specify the passworddir option for each Notes user. Make sure the directory that is specified by the passworddir option is different for each Notes user. Do not specify the installation directory for the passworddir option because that would prevent other users from having write access to the password file, TSM.PWD. If a Notes user does not have read/write permission to the password file, the passwordaccess=generate setting fails for that partition. For the web client to be able to access its partitions, the password must be generated for all of the partitions. Carry out these actions to address this issue:

Define a separate server stanza in dsm.sys for each partition. For example, specify the following path on the server stanza in dsm.sys for the Notes user ID notes:
```
passworddir /opt/tivoli/tsm/client/domino/bin/domdsmc_notes/
```
On the server stanza in dsm.sys for the Notes user ID notes1, specify
```
passworddir /opt/tivoli/tsm/client/domino/bin/domdsmc_notes1/
```

The values for DSMI_LOG, DOMI_LOG, and DOMI_CONFIG can specify the same directory for a Notes user. However, the directory that is specified by these environment variables cannot be specified for a separate Notes user. For example, set the environment for a Domino server with two partitions that are identified with Notes user IDs notes and notes1, as follows:

notes

DSMI_LOG=/opt/tivoli/tsm/client/domino/bin64/domdsmc_notes
DOMI_LOG=/opt/tivoli/tsm/client/domino/bin64/domdsmc_notes
DOMI_CONFIG=/opt/tivoli/tsm/client/domino/bin64/domdsmc_notes/domdsm.cfg

notes1

DSMI_LOG=/opt/tivoli/tsm/client/domino/bin64/domdsmc_notes1
DOMI_LOG=/opt/tivoli/tsm/client/domino/bin64/domdsmc_notes1
DOMI_CONFIG=/opt/tivoli/tsm/client/domino/bin64/domdsmc_notes1/domdsm.cfg

The key objective of these requirements is that these values must specify a location where the Notes user has read/write permission.

See Using multiple Domino server partitions for more information about using Data Protection for IBM Domino in multiple Domino server partitions.