Unattended Installation

Starting Installer in Windows Platform

The Windows version of installer can be started from scripts with arguments. It can be useful for performing silent installations with predefined installation/configuration files or regularly applying patches.

You have to run a first installation manually to be able to enter parameter values for your installation and instance.

The arguments used by installer.cmd from command prompt or script are:

Parameter	Value
<build_home>	Path to your Build Home
<ifs_home>	Path to your IFS Home
silent	[true]
extlog	[true]
APP_OWNER_PWD	[password]

Example:
installer.cmd "D:\Customer\Build_XXXX" "E:\ifs" true true [password]

The location for the installer.cmd can be <ifs_home> or <build_home>\installer\os\<os>

Example of a silent installation from a <build_home> to an empty <ifs_home>

Save the <ifs_home>\installer.xml and <ifs_home>\instance\<instance>\<instance>_configuration.xml from a valid installation.

These files must be carefully modified with an editor for different requirements.

Example of a minimal installer.xml on a <ifs_home> for a Windows installation:

<?xml version="1.0" encoding="UTF-8"?>
<installtool>
  <install>
    <general>
      <os.name>windows</os.name>
      <os.version>6.1</os.version>
      <os.arch>amd64</os.arch>
      <ifs.home><ifs_home></ifs.home>
      <ifs.installer.exist>True</ifs.installer.exist>
      <ifs.installer.silent>True</ifs.installer.silent>
      <installer.version>4.0.0</installer.version>
   </general>
    <components>
      <installer/>
      <client/>
      <server/>
      <webclient/>
      <model/>
    </components>
  </install>
  <configure>
    <mainaction>
      <ifs.action>create</ifs.action>
      <ifs.j2ee.instance>TEST</ifs.j2ee.instance>
    </mainaction>
    <instance.list>TEST</instance.list>
  </configure>
</installtool>

Be careful when editing the <ifs_home>\instance\<instance>\<instance>_configuration.xml not to conflict with existing values for other instances.

Create a <ifs_home> catalog where <ifs_home> is the IFS_HOME argument for the installer.cmd when started.
Apply a modified installer.xml on <ifs_home>
Apply a modified <instance>_configuration.xml on <ifs_home>\instance\<instance>
Start the installer from <build_home> where <build_home> is the BUILD_HOME argument for the installer.cmd when started.

Example: installer.cmd "D:\Customer\Build_XXXX" "E:\ifs\TEST" true true

The configuration files will be saved as installer_silent.xml and <instance>_configuration_silent.xml.

Example of a silent installation from a <ifs_home>

This example runs installer.cmd from an existing <ifs_home>, applying code from a <build_home> defined in the argument for the installer.cmd script. This <build_home> can be a "static" name for a catalog where patches are applied.
If you want that the install.tem should be deployed (if exists in <build_home>) when running in silent mode, add the application owner password [password] as last argument in line.

Start the installer from <ifs_home> and where <build_home> is the BUILD_HOME argument for the installer.cmd when started:

installer.cmd "D:\Customer\Patches" "E:\ifs\TEST" true true [password]

The configuration files will be saved as installer_silent.xml and <instance>_configuration_silent.xml.

Starting Installer in Unix Platforms

To run an unattended installation in unix platforms the installer.sh file on <ifs_home> should be modified as follows.

#
SILENT=true
EXTLOG=false
#

Unlike in the windows platform, the installer startup script does not accept any arguments.

Note: For a successful unattended installation, installer should run in GUI mode at least once.