Public properties

Public properties can be used to change the default behavior of the installation, such as changing the default install directory. Public properties can be set at the command line or defined with a transform or in setup.ini.

To set a public property on the command line interface, where PUBLICPROPERTY is one of the public properties listed below, use the following syntax, as appropriate:
  • To set a single property specify: setup /vPUBLICPROPERTY=value
  • To set a single property by instance, specify: setup /vCWBINSTALLTYPE=Custom
  • To set multiple properties specify: setup /v"PUBLICPROPERTY1=value PUBLICPROPERTY2=value"
  • To set multiple properties by instance, specify: setup /v" CWBINSTALLTYPE=Custom CWBPRIMARYLANG=Mri2938 "
When working with properties, you should only change the public properties listed here. Public property names must be entered exactly as shown.
These public properties are described:

CWBINSTALLTYPE

Purpose:
Sets the setup type of a first time installation.
Scope:
Only valid on a first time installation.
Default:
The default setup type is Typical.
Values:
Typical, Custom
Example
For a complete installation setup type, enter setup /vCWBINSTALLTYPE=Typical
Additional Notes:
  1. The values are not case-sensitive.
  2. The CWBINSTALLTYPE property is ignored if upgrading from a previous release of IBM i Access Client Solutions and in maintenance installations.

CWBPRIMARYLANG

Purpose:
Specifies the default primary language to install.
Scope:
This property is valid in first time, upgrade, and silent installs.
Default:
The default language will be the NLV that matches the system's locale, or what the user chooses for the user interface.
Values:
MRI29xx
The language resources for MRI29xx are installed onto the system and MRI29xx is set as the primary language for IBM i Access Client Solutions. xx specifies the language identifier.
Example
setup /vCWBPRIMARYLANG=MRI29xx

CWBUPGSSLFILES

Purpose:
Allows the user to upgrade the SSL files when migrating from a previous release.
Scope:
Valid for a first time install and an upgrade install (full UI and silent)
Default:
If the configuration files for SSL configuration files are found on the target system, update the files with the latest certificates.
Values:
YES (Default)
The files are upgraded and old certificates are merged with new ones.
NO
New certificates are not added to the old certificates.
Example
To not update the certificates when upgrading of fresh installing, enter: setup /vCWBUPGSSLFILES=NO
Additional Note:
This property allows the customer to upgrade SSL certificates with the latest certificates when upgrading to the latest release. Old certificates are kept and new certificates are added.

ADDLOCAL (Windows Installer property)

Purpose:
List of features that are to be installed locally.
Scope:
Valid for a first time installation, a maintenance installation, or an upgrade.
Default:
None. If the public property is not used, then the selections made during the installation wizard or transform (if provided) determine what is installed.
Values:
ALL
Install all features listed in the Feature table locally.
one or more valid feature names
See Using command line parameters to change the installation behavior for a list of feature names.
Example
See Using command line parameters to change the installation behavior for examples.
Additional Notes:
  1. The features must be listed in the Feature table.
  2. Feature names are not case sensitive.
  3. Do not enter ADDLOCAL=ALL into the Property Table, because this generates a locally installed package that cannot be correctly removed.

REMOVE (Windows Installer property)

Purpose:
Specifies features that are to be removed.
Scope:
Valid only when the product is installed.
Default:
None. If this public property is not used, then the selections made in the installation wizard determine any features to remove.
Values:
ALL
Remove all features having an install level greater than 0. Features having an install level of 0 are not removed.
Example
See Using command line parameters to change the installation behavior for examples.
Additional Notes:
  1. The features must be listed in the Feature table. See Using command line parameters to change the installation behavior for a list of feature names.
  2. Feature names are not case sensitive.

INSTALLDIR (InstallShield Property)

Purpose:
Sets the installation directory for IBM i Access Windows Application Package.
Scope:
This is valid only for a first time install.
Default:
If INSTALLDIR is not specified, IBM i Access Windows Application Package will be installed in C:\Program Files\IBM\Client Access.
Values:
Any valid path
Example
To install IBM i Access Client Solutions on the C:\InstallPath directory, enter setup /vINSTALLDIR=X:\Install_Path where X is the destination drive letter and Install_Path is the target directory.

If the directory path contains spaces, use double quotation marks; one pair for the /v parameter and one pair for the INSTALLDIR property, as in the following example. Note that the interior quotation marks need to be escaped with a backslash: setup /v”INSTALLDIR=\”C:\Install Path\””

TARGETDIR

Purpose:
Set the destination directory for an administrative image when performing an administrative installation.
Scope:
This is valid for an administrative installation.
Default:
If this property is not set during an administrative installation, Windows Installer sets it to the first connected network drive it finds.
Values:
A valid path.
Example
To set the destination directory for an administrative image, enter: setup /a v/TARGETDIR=X:\Admin_image where X: is the destination drive letter and Admin_image is the target directory.

If the directory path contains spaces, use double quotation marks; one pair for the /v parameter and one pair for the TARGETDIR property, as in the following example. Note that the interior quotation marks need to be escaped with a backslash: setup /a /v”TARGETDIR=\”C:\Admin Image\””