How to Create an Installation Template

You create the installation template to have one single file that will deploy all your components to the database. This file includes settings for each component as well as the installation control, fresh installation or an upgrade scenario.

Prerequisites

An install.ini file should exist. The file is found in <build_home>\database folder e.g. <workspace>\build_home\database.

Note: When you run this step you will also create .tem’s for deployable files in subfolders. E.g. for IALs and IAL.tem will be created.

For details see Page: Create Installation Template for Database Objects

Actions to perform:

  1. Select the page header Create Installation Template for Database Objects.
  2. By default the Build Source Directory will be filled with correct path to where install.ini exists, if Build Destination is set in page Create Build Structure and Compile and database is built into the destination.
  3. If Build Source Directory not filled with correct information, browse to the folder where install.ini is located (<build_destination>\database).
  4. Select Edit Settings to edit the values manually per component listed in install.ini file. Page Create Installation Template for Database Objects, edit settings
  5. Select Refresh to reload files. For example the install.ini file has been manually edited because of unresolved dependencies or merged files has been removed.
  6. Select Get Defaults to revert modified values to standard values.
  7. Select Get values from database to check version of installed components and get correct version set for upgrade, and to get a list of existing tablespaces and the free space available. Dialog: Login
  8. Select Free tablespace to list the found table spaces and the free space. List only available when Get values from database has been executed.
  9. Select Create Installation Template to create the install.tem file with selected values.

Note: Two additional tem files should be created/copied to <build_home>\database folder, biservices.tem and define.tem. The define.tem is copied from the Template sub folder where IFS Configuration Builder is executed, and biservices.tem is created as dummy template if no already exist. These file will be called by the install.tem template.

Verify by