Workspace Folder Structure

IFS Configuration Builder stores data, such as fetched components, and builds in a working structure referred by the name Workspace. In documentation this catalog is referred as <workspace>.

Before you can fetch any component, you must specify the location of the <workspace>. You specify the path for the  <workspace> in the startup page (Fetch Components) for the IFS Configuration Builder.

All fetch and build operations are usually performed within the <workspace>. This is the main folder (typically named after the project) to which all components are fetched from the release repository and in which all builds are performed. The <workspace> contains the following sub-folders:

• Components
  Into this folder all component releases (including Update, if exist) or language components (including Update, if exist) are fetched from the release repository. Each component will be fetched to a separate folder bearing the component name (e.g., accrul, accruw, invoic). Some folders in the component folders will not be used for building but will be fetched to these folders by the fetch operation anyway.
• LNG_Components
  Into this folder all component language files (including Update, if exist) are fetched from the release repository. Each component will be fetched to a separate folder bearing the component name (e.g., accrul, accruw, invoic).
• UPD_Components
  Into this folder all components changed / new files are fetched for a specific Update set. Each component will be fetched to a separate folder bearing the component name (e.g., accrul, accruw, invoic).
• [Build Destination], e.g. <workspace>\build_home
  Under each <build_home> folder the result of the build can be found. Each<build_home> folder corresponds to either a customer distribution or a build kit to install or upgrade components. Builds destined for different customers or database instances should always be given a new<build_home>. The contents of this folder is described in Folder Structure for Builds