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 fresh installations with predefined installation/configuration files (based on template files), or regularly applying deliveries.

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]
SYS_PWD [password]

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

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> including database objects

Use the templates installer_xml.tem and instance_configuration_xml.tem from <build_home>\template\fndbas.

If you want that the install.tem to be deployed (if existing in <build_home>) when running in silent mode, add the application owner password APP_OWNER_PWD as fifth argument in line.
If you want that the prepare.sql to be deployed (if existing in <build_home>) when running in silent mode, also add the sys password SYS_PWD as sixth argument in line.

Save installer_xml.tem as <ifs_home>\installer.xml and instance_configuration_xml.tem as <ifs_home>\instance\<instance>\<instance>_configuration.xml

These files must be carefully modified with an editor or script replacing the tokens and values with appropiate values for the installation.

The templates are for a simple fresh installation with default values, using a self-signed certificate.
Passwords for internal users are "internal".
User Middleware Admin User is "ifs" with password "internal123"
User Middleware Monitoring User is "ifsmon" with password "internal123"


Example <ifs_home>\installer.xml
#IFS_HOME#  -> C:\ifs
#SERVICE# -> C_ifs_TEST
#IFS_J2EE_INSTANCE# -> TEST

Example <ifs_home>\instance\<instance>\<instance>_configuration.xml
#IFS_J2EE_INSTANCE# -> TEST
#IFS_HOST# -> MY_HOST
#IFS_DB_HOST# -> MY_DB_HOST
#IFS_DB_SID# -> MY_DB_SID
#IFS_APPLICATION_OWNER# -> MY_APPLICATION_OWNER
#IFS_HOST_FQDN# -> MY_HOST_FQDN


Other "fixed" values can be replaced if needed, like Oracle Listener port "1521", the port prefix "58" or Docman temp path "c:\temp\".

More advanced configurations can be achieved by modifying other values, by comparing with existing advanced configuration files.

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 APP_OWNER_PWD SYS_PWD

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


Example of a silent delivery from <dist_home> to <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.

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

Example:
installer.cmd "D:\Customer\Patches" "E:\ifs\TEST" true true APP_OWNER_PWD SYS_PWD

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

Starting Installer in Unix Platforms


The template files should be modified to Unix path's.

Example:
installer.sh "/home/ifs/build_XXXX" "/opt/ifs" true true APP_OWNER_PWD SYS_PWD