When you build the application, the fetched components are assembled into a "build-structure" in which the source code for the client and middle tier can be compiled (C# and Java files) and database files can be generated. This page describes a basic / typical scenario. For a more detailed description of each step, including additional options, please refer to the IFS Configuration Builder documentation - How to Build in General and How to Prepare Database Objects and Generate.
To build a fresh installation you first fetch the selected components. The
components were originally selected in GCDB and is transferred into the
configuration file, so you probably want to fetch all the components.
If
languages were defined for the installation, the configuration file will include
these language codes, Limit Fetch to Selected Languages will be enabled
and you will be able to decide if you want to limit the fetch of translation
files only to selected languages.
If the components include updates, the specified update version will be fetched first and then files from core release (except already fetched files from the update) for the component.
When fetching is done you create and set the build destination.
You select the build options (normally all) and languages to be included, decide
if compilation of Java and/or C# should be automatically started when build is
completed, and start the build operation.
Once the build is completed you decide if database files should be generated,
including generation of installation template files. At this time you also
choose to do the fresh installation.
The IFS Configuration Builder tool must have been set up according to How to Configure IFS Configuration Builder.
When the steps in IFS Configuration Builder are successfully completed you have a build ready for deployment using the IFS Applications Installer. Log files are created during the build process and these can be useful in order to find out the root cause in case the build process doesn't complete as expected.