wclient

-c source_dir

Specifies the complete path to the directory containing the installation image. For source_dir, you can specify either the fully qualified path (for example /cdrom) or the source host and the path in the format source_host:path (for example oak:/cdrom).

-d

Sets install_variables to their last set values. Commonly, each installed managed node uses the same set of installation variables. This option provides a shortcut for setting the variables.

-f file_name

Specifies a text file containing a list of machines to be installed. The file contains one line per machine with the format host_name,user,password, whereuser and password are optional. If not specified, the default user is root or Administrator. There can be no spaces between entries. The content of each line determines the default method.

For the default, each entry contains only the machine name.
For account access, each entry contains the machine name followed by a comma (,), the user ID followed by a comma (,), and then the password.
Note

Passwords are not encrypted. Anyone with access to this file can see the passwords.
For trusted host access, each entry contains the machine name followed by a comma (,).

The following is an example of a machine file:

elm,
oak,chris,&rews
liveoak,

-I

Causes the command to prompt for the installation password. If you do not use this option, there is not a password prompt.

-j

Causes the command to use an encrypted secure shell (SSH) connection when the Tivoli server connects to the machine to create the managed node.

Note

You cannot use SSH to perform installations on Windows targets.

-p policy_region

Specifies the name of the policy region in which the managed nodes are installed.

-P

Causes the command to prompt for the root password for the machine. If you specify more than one machine, the command assumes they all have the same root password.

-t

Specifies that the account and password specified with the -U option should be used as the Tivoli remote access account.

-T traa

Specifies the account name to be used for the Tivoli remote access account. When you use this option, you are prompted for the password.

-U user_account

Specifies an account and password other than root for installing each managed node. When you use this option, you are prompted for the password.

-y

Specifies that the installation should proceed without confirmation. By default, the command identifies the actions that must be taken to perform the installation and requests confirmation before continuing. Using this option, the command identifies the actions and performs the installation without requesting confirmation.

install_variables

Indicates the key-value pairs that control the installation. These variables can be set or defaulted on the command line. These variables specify required information or override default information.

Note

Type the names of the installation options exactly as specified in the product documentation. Installation options are case sensitive.

Several of the installation variables specify the directories where the managed node will be installed. If a directory contains files from a previous installation, the command does not install these files again. However, you can force any of these directories to be reinstalled by using an exclamation mark (!) character as the value for the variable.

The following are the installation variables related to the installation directories:

BIN=binaries: Overrides the default installation path (/usr/local/Tivoli/bin) for the binaries.
LIB=libraries: Overrides the default installation path (/usr/local/Tivoli/lib) for the libraries.
DB=client_database: Overrides the default installation path (/var/spool/Tivoli) for the object database.
MAN=manpage: Overrides the default installation path (/usr/local/Tivoli/man) for the manual pages.
APPD=X11_defaults: Overrides the default installation path (/usr/lib/X11/app-defaults) for the X11 application defaults.
CAT=message_catalog: Overrides the default installation path (/usr/local/Tivoli/msg_cat) for the message catalogs.

The following are other useful installation variables:

@AutoStart@=0 | 1: Indicates whether the Tivoli daemon should be started (1) at system boot time. By default, the daemon is not started (0).
@SetPort@=0 | 1: Indicates whether to configure or not configure (0) the remote start capability of the Tivoli daemon. Enabling remote start requires changes to system files; for example, /etc/inetd.conf and /etc/services on Linux and UNIX systems. By default, this capability is configured (1).
@CreatePaths@=0 | 1: Indicates whether to create the specified directories if they do not already exist. By default, directories are created (1). It is an error if a directory you specified with install_variables does not exist.
@ClientAddNoTrans@=yes | no: Indicates whether managed nodes should be added using a transaction. Adding managed nodes without a transaction can save significant time when installing over slow links. If an error occurs, however, you should run the wchkdb command to verify the state of the database.
@ForceBind@=yes | no: Indicates whether communication connections are forced to bind to a single Internet Protocol (IP) address. This option is used in certain high-availability or failover configurations where multiple object dispatchers reside at different IP addresses on a single physical system.

managed_node

Specifies the machines where a managed node is installed. If using the -f option, do not include any machine that is listed in the file specified by this option.

Linux and UNIX Files

/tmp/tivoli.cinstall: This file resides on the Tivoli management region server and contains verbose debugging information from all managed node and product installation attempts.
/tmp/install2.cfg.error /tmp/install2.cfg.output: This transient file is created on a managed node during the initialization of its object database. After a successful initialization, these files are removed.
/tmp/client.cfg.error /tmp/client.cfg.output: This transient file is created on a managed node during the configuration of its object database. After a successful initialization, these files are removed.
/etc/Tivoli/setup_env.sh: This file contains useful Bourne shell environment variables. The file can be sourced in from Bourne shell compatible shells after installation.
/etc/Tivoli/setup_env.csh: This file contains useful C shell environment variables. The file can be sourced in from C shell compatible shells after installation.

Note

When you install Tivoli Management Framework on a UNIX operating system, the /tmp/.tivoli directory is created. This directory contains files that are required by the object dispatcher process. You should not delete this directory or any of its contents unless explicitly directed to by your Tivoli support provider. You should also ensure that regularly scheduled disk clean-up jobs (cron or Tivoli jobs) do not remove this directory or its contents.

To use a different directory, you must set an environment variable in both the object dispatcher and the shell. After installing Tivoli Management Framework, perform the following steps to set the necessary environment variables:

Create a directory. This directory must have at least public read and write permissions. However, define full permissions and set the sticky bit to ensure that users cannot modify files that they do not own.
Set the environment variable in the object dispatcher:
1. Enter the following command:
```
odadmin environ get > envfile
```
2. Add the following line to the envfile file and save it:
```
TIVOLI_COMM_DIR=new_directory_name
```
3. Enter the following command:
```
odadmin environ set < envfile
```
Edit the Tivoli-provided setup_env.csh, setup_env.sh, and oserv.rc files in the /etc/Tivoli directory to set the TIVOLI_COMM_DIR variable.
For HP-UX and Solaris systems, add the following line to the file that starts the object dispatcher:
```
TIVOLI_COMM_DIR=new_directory_name
```
Insert the line near where the other environment variables are set, in a location that runs before the object dispatcher is started. The following list contains the file that needs to be changed on each operating system:
- For HP-UX operating systems: /sbin/init.d/Tivoli
- For Solaris operating environments: /etc/rc3.d/S99Tivoli
Shut down the object dispatcher by entering the following command:
```
odadmin shutdown all
```
Restart the object dispatcher on the Tivoli server by entering the following command:
```
odadmin reexec 1
```
Restart the object dispatcher on the managed nodes by entering the following command:
```
odadmin reexec clients
```

Windows Files

%TMPDIR%\tivoli.cinstall: This file resides on the Tivoli server and contains verbose debugging information from all managed node and product installation attempts.
%TMPDIR%\install2.cfg.error %TMPDIR%\install2.cfg.output: These transient files are created on a managed node during the initialization of its object database. After a successful initialization, these files are removed.
%TMPDIR%\client.cfg.error %TMPDIR%\client.cfg.output: These transient files are created on a managed node during the configuration of its object database. After a successful initialization, these files are removed.

wclient

Syntax

Description

Options

Authorization

Files

Linux and UNIX Files

Windows Files

Examples

See Also