Ignite-UX Custom Configuration files

}
}
}
...
Forcing software (sw_sel) clauses to be installed
Be careful when marking software automatically for installation using a configuration file. If you
mark it in the following way (set it directly equal to TRUE), the software is marked as required in
the Ignite-UX GUI and you cannot manually deselect the software:
sw_sel "Kernel Config" {
description = "Tunable settings"
sw_source = "site commands"
sw_category = "KernelConfig"
set_kernel = "maxdsiz 0x4000000"
set_kernel += "maxusers 96"
}=TRUE
Compare the previous software clause to the following. Because it starts with init you can
change its state using the Ignite-UX GUI during installation, although by default it is marked for
installation.
init sw_sel "Kernel Config" {
description = "Tunable settings"
sw_source = "site commands"
sw_category = "KernelConfig"
set_kernel = "maxdsiz 0x4000000"
set_kernel += "maxusers 96"
}=TRUE
You can force software installation in other ways, such as with the keywords load_with_any and
load_with_all. However, you should not combine usage of the init keyword with these
methods.
Keep this in mind when defining software because you do not want to force software onto a system
unintentionally.
Automating dependencies in software
This section explains the ways of enforcing dependencies between software with Ignite-UX.
Corequisites are used to enforce dependencies between software that you want to load at the
same time:
corequisite [+]= tag-string
Indicates that the sw_sel referred to by
tag-string should
be loaded along with this sw_sel. Multiple corequisites may
be listed using one corequisite statement per, and by using
the += operator.
In the following example, there are the sw_sel "Product XYZ" and "Product XYZ – 4GL".
The 4GL product requires the other product to be installed as well, so introduced here is a
corequisite for the 4GL to install automatically "Product XYZ" when it is selected for installation.
127