Customizing the setup fileset
The main configuration file Setup.xml, located in the x64 folder, lists all features included in the setup.
When you create a server image, a copy of the Setup.xml file is included. If you want to customize the setup fileset on the server image, you must edit the Setup.xml file to reflect your desired changes.
The Setup.xml file contains four main types of nodes. With an understanding of these four nodes, you can modify the Setup.xml file to create a customized server image.
Each <Msi/> node specifies a main setup file, such as an executable (EXE) file, a self-extracting ZIP file, or an MSI file that bundles (or "chains") other MSI files.
For example, you can exclude Ghostscript from the installation by making the following modification.
Each <Dbm/> node specifies a component of a <Msi/> node — typically, an MSI file. A <Dbm/> node has the following structure, where GUID is the associated product code, and MSI is the path and filename of the MSI file:
Some <Dbm/> nodes also require a condition.
If you want to apply an MST file to the specified MSI file, you can use the following syntax (in cases where the MST and MSI files are in the same folder, MST is the filename of the MST file; in cases where the MST and MSI files are in separate folders, MST is the path and filename of the MST file):
Each <Feature/> node specifies a feature that is associated with an MSI file. A <Feature/> node has the following format, where name is the name of the MSI file and feature is the name of the associated feature:
Some <Feature/> nodes have subnodes.
For a list of the available features, see Deploying a custom set of features.
Each <Property/> node specifies a property. A <Property/> node has the following structure, where property is the name of the public property and value is its value:
For a list of available public properties, see Using public properties.