Skip to content

What's the recommended component type to use in a new customization module's deploy.ini (the old 'Cust' type doesn't seem to be documented as valid anymore for IFS Cloud), and how does the IFS Installer decide whether to treat a component as a fresh install versus an existing/upgrade during deployment?

Answer

You can keep using 'Cust' as the component type — it was never actually part of IFS Configuration Builder-specific documentation even historically, and since Configuration Builder itself isn't used in Cloud, that distinction is no longer relevant; the value was informational only even when it existed. For fresh-vs-existing detection: when the installer runs with database credentials, it connects to the database and checks whether the component (and its version) already exists there. If the component doesn't exist yet, it's treated as a fresh install (running the .cre creation scripts); if it exists, its installed version is compared against the [<component>Upgrade] section in deploy.ini to determine which upgrade (.upg) file to run. Without credentials, build-home creation defaults to a fresh install and delivery creation defaults to version-up-to-date.

← Browse Developer Studio, deployment, and upgrades questions