Using command line parameters to change the installation behavior
A user can install, upgrade or modify the features that are installed by using command line parameters on the setup.exe command.
Note: These examples use the setup.exe command. The
parameters also work in the same way for the cwblaunch.exe command.
Before installing, the user needs to change directories
to the directory that contains the installation image. There should
be a network drive mapped to this image. If not, these are the locations
of the installation images:
Processor type | Installation source | Location of Installation Image |
---|---|---|
32-bit | IBM i Access for Windows DVD | Windows\Image32 |
Licensed Program 5770-XE1 | QIBM\ProdData\Access\Windows\Image32 | |
64-bit AMD | IBM i Access for Windows DVD | Windows\Image64a |
Licensed Program 5770-XE1 | QIBM\ProdData\Access\Windows\Image64a |
- To install, upgrade or add features, enter setup /vADDLOCAL=featurename where featurename is the internal name of the feature. See Table 2 for the list of feature names.
- To include more than one feature, separate the features with a comma as shown in this example: setup /vADDLOCAL=dir,irc,emu
- To install, upgrade or add all features, enter setup /vADDLOCAL=ALL
- To remove features after the install or upgrade, enter setup /vREMOVE=featurename where featurename is the internal name of the feature. See Table 2 for the list of feature names.
- To remove the product, enter setup /vREMOVE=ALL
- To specify transforms to be applied, enter Setup /vTRANSFORMS=transform1.mst,transform2.mst,…
Note: When combining two or more options into the /v parameter or
when the value of an option contains spaces you need to enclose them
in apostrophes as shown in the following example:
setup /v"ADDLOCAL=dir TRANSFORMS=MyTransform.mst"
Feature | Internal name of feature |
---|---|
Required Programs | req |
Directory Update | dir |
Incoming Remote Command | irc |
Data Transfer | dt |
Data Transfer Excel Add-in | dtexcel |
ODBC | odbc |
OLE DB Provider | oledb |
Lotus® 123 File Format Support | lotus123 |
.NET Data Provider | dotnet |
AFP Workbench Viewer | viewer |
5250 Display and Printer Emulator | emu |
Secure Socket Layer (SSL) | ssl |
AFP Printer Driver | afp |
SCS Printer Driver | scs |
Operations Console | oc |
Headers, Libraries, and Documentation | hld |
System i® Navigator (Base Support) | inav |
Basic Operatons | inavbo |
Work Management | inavwm |
Configuration and Services | inavcfg |
Networks | inavnet |
Integrated Server Administration | inavisa |
Security | inavsec |
Users and Groups | inavug |
Databases | inavdb |
File Systems | inavfs |
Backup | inavback |
Commands | inavcmd |
Packages and Products | inavpp |
Monitors | inavmon |
Logical Systems | inavlog |
AFP Manager | inavafp |
Application Administration | inavad |
Toolbox for Java | tbj |
Java™ Programmer's Tools | jpt |
Note: The feature's name
is not case-sensitive.
|
Setting public properties from the command line
To set public properties from the command line, use this command:setup /vPUBLIC_PROPERTIES=value
For
a list of public properties, see the Public properties topic.