Restricting the set of features that users can install

You can use Transforms and the Feature table to restrict the set of features that your users can install.

Before customizing the Feature table, you should be familiar with the feature tree structure and what dependencies exist between features.

All required dependencies for a feature will be installed if that feature is selected. The following table shows which features depend on other features:

Table 1. Feature dependencies
Feature	Dependent on following features
5250 Display and Printer Emulator	none
.NET Data Provider	none
AFP Printer Driver	none
AFP Workbench Viewer	none
Data Transfer	none
Data Transfer Excel Add-in	Data Transfer
Directory Update	none
Headers, Libraries, and Documentation	none
Incoming Remote Command	none
System i® Navigator	OCI, JRE, Toolbox for Java™, ODBC
Basic Operations Work Management Configuration and Services Network Integrated Server Administration Security Users and Groups Databases File Systems Backup Commands Packages and Products Monitors Logical Systems AFP Manager Application Administration	System i Navigator
Java Programmer's Tools	JRE, Toolbox for Java, ODBC
JRE	none
Lotus Notes® 123	none
ODBC	none
OLE DB Provider	none
Operations Console	OCI, 5250 Display and Printer Emulator (if no PCOMM)
Required Programs	none
SCS Printer Driver	none
Secure Sockets Layer (SSL)	none
Toolbox for Java	JRE

Notes:

Do not delete or modify rows from the MSI database in ways not described here.
JRE does not appear in the feature tree as an installable component. JRE resources are installed as part of System i Navigator and Java Programmers Tools.
Do not change the Level column for the req feature.
Features emus, emuk, emup and emut are not visible by design. Do not change the Display or the Level values for these features.
If you set public property CWBINSTALLTYPE to Complete, all features are installed except for those with a Level value of 0.
If you set public property CWBINSTALLTYPE to PC5250User, all features with a level equal or lower to 50 are installed except for those with a Level value of 0.

To restrict the set of features that your users can install, follow these steps:

Change the Level and Attributes values as necessary:

To preselect a feature to be installed, change its Level value to 1.
- For a basic, reduced, or silent install, the feature is installed.
- For a full user interface install, the feature is preselected in the Custom dialog, but a user can deselect it. If you want make sure the feature cannot be deselected, change the Attributes value to 24 to mark it as Required.
To deselect a feature without disallowing it, change its Level value to 125.
- For a basic, reduced and silent install, the feature is not installed.
- For a full user interface install, the feature is not preselected in the Custom dialog, but a user can select it to be installed.
To hide a feature during a full user interface install, change its Display value to 0.
- This does not disallow the feature from being installed, but it is not shown in the Feature selection tree in a Custom install. Whether the feature is installed or not depends on the Level value for the feature, or whether the feature name was passed in the ADDLOCAL property.
- For basic, reduced, and silent installs, changing the Display column has no effect.
To completely disallow a feature, change its Level value to 0.
- For a full user interface install, the feature is not shown and it is not installed.
- For basic, reduced, and silent installs, the feature is not installed.
- Passing the feature name in ADDLOCAL does not install the feature.