Install server in silent mode on UNIX/Linux

This topic provides instructions for installing Deployment Automation in silent mode on UNIX/Linux, and contains examples of configured options for different database types.

Silent mode enables you to automate the installation. You can also install a Deployment Automation server using the interactive installer. For details, see Run the interactive server installer.

Install Deployment Automation in silent mode

Follow these steps for a silent mode installation on UNIX/Linux.

Note: Silent mode installation is available for Linux and AIX systems. For other UNIX platforms, install the server manually. See Install sever manually on UNIX.

To install a server in silent mode on UNIX/Linux:

  1. Download the installation files.

  2. Create an optionsFile.txt and save it in the root directory. For details, see Server silent installation options.

  3. As a user with root privileges, run this command:

    MicroFocusDA-Server.bin -silent -options optionsFile.txt

    where optionsFile.txt is the options file you created in step 2.

After you install your server, continue with the next steps in the Installation checklist.

Back to top

Server silent installation options

The following table describes the server silent installation options in an optionsFile.txt file for UNIX/Linux.

Option Default Description
typical Must be set to typical. Do not enclose in quotation marks.
-P installLocation
  Specify the target directory for installing the DA server. The –P property is used by the silent installation tool as the location to place files on disk. Use this path: /opt/microfocus/da
-V ServerDetailsInstallLoc
  Specify the path to the Deployment Automation profile location. The value depends on the user specified in the -V SctTomcatOwner option. Use this path:
-V ServerDetailsUseExisting

To skip the database installation and administration part of the installation, include this and set it to true.

Note: Use only if there are existing Deployment Automation settings populated in the directory specified by: SRA_USER_INSTALLDIR.

-V ServerDetailsSkipDb
false To skip the database creation, include this and set it to true.
-V ServerDetailsPort
7918 Server port.
-V ServerDetailsMutualAuth
false To use agent mutual authentication, specify this and set it to true. For more information, see Configure SSL mutual authentication.
-V SctFoundLoc
  To reuse an existing installation of Common Tomcat, specify this and set it to true. When this is set to true, you must also include the SctInstallLoc option.
-V SctInstallLoc
  If you specify the SctFoundLoc option to reuse an existing installation of Common Tomcat, you must use this option to specify the location of the existing Common Tomcat.
-V DbDetailsVendor
derby Use this to specify a database vendor other than the default: oracle, sqlserver, or postgresql.
-V DbDetailsUser
da Database user ID.
-V DbDetailsPwd
password Password for database user ID.
-V DbDetailsDatabaseName
  Database name (SQL Server only).
-V DbDetailsSchema
  (Required for Oracle) Database schema.
-V dbDetailsDriverFilename

(Required for a database other than Derby) Specify a database driver file.

Note: The first "d" must be lowercase in this parameter only.

-V DbDetailsDerbyPort
  (Required for Derby) This option specifies the Derby port, 11377.
-V DbDetailsConnection
  Database connection.
  (Required) Installation mode must be set to silent.
-V AdminDetailsName

Required installation owner's administration username.

Caution: Once created, you cannot remove the built-in administrative user through the user interface. Therefore, we recommend using your organization's naming standards.

-V AdminDetailsPwd
  Required user-defined password for the username set by the AdminDetailsName option.
-V SctTomcatOwner
  System user to own the Common Tomcat files, required only for new Common Tomcat installations.
-V SctTomcatPort
8080 Common Tomcat port, required only for new installations. See the SctFoundLoc option.

Back to top

Examples of silent installation settings in an options file

Use the following examples of the optionsFile.txt settings for each database type on UNIX/Linux.

Back to top

See also: