Deployment file properties

The deploy.properties file is used by the silent installation command for a new installation, a file migration, or to upgrade the application data.

You must modify the task value in the deploy.properties file to indicate a new installation, a file migration, or to upgrade the application data. The rest of the properties in the file stay the same for a new installation, a file migration, or to upgrade the application data.

Table 1. Deployment file properties
Property	Values	Description
`task`	`fresh` `upgrade` `file-migration` `upgrade-app-data` `current-deployment` `uninstall` `fix-pack`	`fresh` for a new installation `upgrade` for an in-place upgrade `file-migration` to migrate from an existing installation `upgrade-app-data` to upgrade the application data `current-deployment` to modify an existing environment, such as adding a server `uninstall` to uninstall an environment `fix-pack` to install a fix pack, see Performing a silent installation of a fix pack
`module`	`true` `false`	The `module` value indicates whether to install the IBM OpenPages® solutions. For more information, see Considerations for IBM OpenPages solutions.
`os`	`windows` `linux`	The host computer operating system.
`remote_deploy`	`true` `false`	This value determines whether the installation is on a different host than the computer that runs the installation server.
`auto_roll_back`	`true` `false`	This value determines whether the installation will roll back a failed operation.
`install_db` For more information, see: Configuring the database server (Db2) Configuring the database server (Oracle)	`full` `nondba` `done`	`full` to install the full database. This option requires DBA credentials. `nondba` if the DBA installation actions are already complete. The installer will perform the non-DBA installation steps. `done` if the database installation is already complete. Note: For fix packs, the `nondba` and `done` options are equivalent. The database update must be complete before you use these options for a silent fix pack install.
`db_type`	`Oracle` `DB2`	`Oracle` for an Oracle database `DB2` for an IBM Db2 database.
`java_home_directory`	The absolute path to JAVA_HOME on the server	For application servers, use the path to the IBM SDK. For reporting servers, use the path to the IBM Java™ JRE that is supplied with Cognos® or the Java that you configured for Cognos. For each server, the path that you enter must match the path specified in the JAVA_HOME system environment variable on the server. If the reporting server is deployed on the same server as an application server, do the following: On the server, set `JAVA_HOME` to the JRE of the IBM SDK. For the `java_home_directory` property in the `[report server1]` section, use the same path as you specified for `JAVA_HOME`.