Unattended Installation Packages
The installation scripts for each component are contained in the packages directory below the directory containing the irisinstall_silent script. Each package is in its own directory, and each package directory contains a manifest.isc file defining prerequisite packages for the package in that directory.
The standard_install package is the starting point for a server install in which all packages are installed. To define a custom package, you can use the manifest.isc file for the standard_install package as a template, as follows:
-
Copy the standard_install directory to a new directory.
For example, copy it to a directory named custom_install; initially, the manifest.isc file in the new directory is similar to the following:
#This is the target for a standard (non-client-only) install
package: standard_install
prerequisite: install_mode
prerequisite: database_server
prerequisite: databases
prerequisite: gadget
prerequisite: fop
prerequisite: renderserver
prerequisite: printserver
prerequisite: excelexporter
prerequisite: callin_components
prerequisite: client_components
prerequisite: addenda
prerequisite: install_confirmation
prerequisite: copyright
-
In the new directory, modify the manifest.isc file as follows:
For example, in the following manifest.isc file, the value of the package key has been changed to match the directory name (custom_install).
#This is the target for a custom (non-client-only) install
package: custom_install
prerequisite: install_mode
prerequisite: database_server
prerequisite: gadget
prerequisite: fop
prerequisite: renderserver
prerequisite: printserver
prerequisite: excelexporter
prerequisite: callin_components
prerequisite: client_components
prerequisite: addenda
prerequisite: install_confirmation
prerequisite: copyright
Then you can specify the new custom package when performing unattended installations; for example: sudo ISC_PACKAGE_INSTANCENAME="MyIris" ./irisinstall_silent custom_install.