Installing the default Application Server node silently

As an alternative to performing an interactive installation, you can perform an unattended (silent) installation of the default Application Server node. In a silent installation, you run the unified product installer through a command line.

Before you begin

Ensure that your environment meets the requirements discussed in Requirements for installing on Microsoft Windows and Requirements for installing on UNIX and Linux.

To encrypt your database password in preparation for specifying it in the options file (see step 4 below), use the BSAOneClickInstallMaintenanceTool utility provided in the installation package. After extracting the package (step 1 below), you can find this utility in the temporary directory: \Disk1\utility\BSAOneClickInstallMaintenanceTool.cmd (for Windows) or /Disk1/utility/BSAOneClickInstallMaintenanceTool.sh (for Linux).
You can run this utility in the following ways:

• Interactively - Run the utility, enter your password on the Encrypt tab, and click Encrypt
• Silently - Run the following command from the directory where the utility is located:
  
  • (Windows) BSAOneClickInstallMaintenanceTool.cmd -silent -encrypt -encrypt -password=<password> -confirm_password=<password>
  • (Linux) ./BSAOneClickInstallMaintenanceTool.sh -silent -encrypt -encrypt -password=<password> -confirm_password=<password>

To install the default Application Server node in silent mode

1. Download and extract the installation package appropriate for the operating system level and hardware platform in a temporary directory. The package follows the naming convention BBSA<version>-<platform>.zip, and contains the unified product installation program files.

2. Extract the RSCDAgent.zip file and copy the rscd folder to one of the following locations before running the unified product installer (The unified product installer uses the RSCD installers while installing or upgrading BMC Server Automation in your environment):

   • (Windows) <temporary location>/files/installer/

   • (Linux):  

     • For version 8.6.00 or 8.6.00.001:  <temporary location>/files/installers

     • For version 8.6.01 and later:  <temporary location>/Disk1/files

3. If you are on a Linux machine, assign executable permission to the temporary directory by entering the following command:

   chmod +x -R <temporary directory> 

   In addition, if the temporary directory is at the end of a path (that is, has at least one parent directory), assign read permission to the others class for all directories in the path. To do this, execute the following command on the top-level directory in the path:

   chmod o+r -R <top-level directory>

4. In a text editor, create an options file and define values for the relevant installation options. Define each option on a separate line.
   The following list of available installation options is divided according to the categories that are displayed in the installation wizard during an interactive wizard:

   Installation directory
   

   

   Database options

   Option	Description of value
   -J DATABASE_TYPE	The type of database that you have set up for BMC Server Automation, either SQL_SERVER or ORACLE.
   -J SCHEMA_HOST	Host name (or, for an IPv4 system, IP address) of the server that runs the database.
   -J SCHEMA_INSTANCE	Name of the database instance.
   -J SCHEMA_LOGIN	User name that the database needs to authenticate your connection.
   -J SCHEMA_PORT	Port that the database listens on. The default port is 1521 for Oracle Database and 1433 for SQL Database.
   -J SCHEMA_PASSWORD	Encrypted version of the password assigned to the user ID. For example: -J SCHEMA_PASSWORD=DES\:84bcbe1dc68f845808829e457d4e2030
   -J CONFIRM_SCHEMA_PASSWORD	Repeated specification of the password, for confirmation.
   -J NLS_CHAR_SET	The character data type for string data stored in the database — one of the following values: CHAR — CHARACTER data type, which uses the ASCII character set. This is the default value. NCHAR — NATIONAL CHARACTER data type, which uses the Unicode character set and stores data using UTF8 encoding.

   File Server options

   Option	Description of value
   -J USE_SEPARATE_FILE_SERVER	Whether you want the file server installed separately from the first Application Server node, on a different host computer. Values are either true or false. The default is false.
   -J MANUALLY_INSTALL_SEPARATE_FILE_SERVER	Whether you have already manually installed the separate file server, and do not want the unified product installer to install it for you. Values are either true or false. The default is false. This option is useful if you want the file server hosted on a platform that is not supported by the unified product installer, such as a 32-bit or Solaris computer.
   The following file server options are relevant only when USE_SEPARATE_FILE_SERVER=true.
   -J FILESERVER_HOSTNAME	Host name or IPv4 address of the separate file server. Note that if your server is on an IPv6 address system, you enter only the host name of the server.
   -J FILESERVER_REPOSITORY_PATH	The path to the directory on the separate file server where data is stored. The default path is /opt/bmc/bladelogic/storage on Linux and C:\Program Files\BMC Software\BladeLogic\storage on Windows.
   -J FILE_SERVER_OS_TYPE	The operating system that is running on the host computer of the specified separate file server, either Windows or Linux. If you do not specify an OS type, the UPI assumes that the separate file server runs on the same operating system as the first Application Server node. Note: If you manually installed the separate file server on a Solaris computer (and set MANUALLY_INSTALL_SEPARATE_FILE_SERVER=true), this option is not relevant.
   The following file server options are relevant only when USE_SEPARATE_FILE_SERVER=true and MANUALLY_INSTALL_SEPARATE_FILE_SERVER=false.
   -J PSEXEC_USER	A local Administrator or Administrator-equivalent local user to run PSExec on a Windows file server host during installation. The default is Administrator.
   -J PSEXEC_USERPASSWORD	The password of a local Administrator or Administrator-equivalent local user who will run PSExec on a Windows file server host.
   -J PSEXEC_CONFIRM_USERPASSWORD	The PSExec user password once again, for confirmation.
   -J FILE_SERVER_SSH_USER	A local super user (root or a root-equivalent user) for establishing an SSH connection to a Linux file server host during installation.
   -J FILE_SERVER_SSH_USER_PASSWORD	The password of a local super user (root or a root-equivalent user) for establishing an SSH connection to a Linux file server host.
   -J FILE_SERVER_SSH_USER_CONFIRM_PASSWORD	The SSH user password once again, for confirmation.

   
   

   Ports
   

   Option	Description of value
   -J BSA_APPSERVER_BASE_PORT	The Application server base port, relative to which all other Application Server ports are configured. The default base port is 9800, and the allowed range is 1024-65000. For more information, see Application Server ports.

   Passwords
   

   Option	Description of value
   -J BSA_CERTIFICATE_PASSWORD	The initial password of the default security certificate for BMC Server Automation. This password is used to generate a self-signed X.509 certificate for the Application Server.   The password must be at least 6 characters. For more information about certificates and the TLS protocol, see Authentication.
   -J CONFIRM_BSA_CERTIFICATE_PASSWORD	The certificate password once again, for confirmation.
   -J BSA_BLADMIN_PASSWORD	The initial password for the BLAdmin (BladeLogic Administrator) user. This built-in user is created during the installation process. The BLAdmin user is only assigned the BLAdmins role. For more information, see RBACAdmin and BLAdmin users.
   -J CONFIRM_BSA_BLADMIN_PASSWORD	The BLAdmin password once again, for confirmation.
   -J BSA_RBACADMIN_PASSWORD	The initial password for the RBACAdmin (BladeLogic Role-Based Access Control Administrator) user. This built-in user is created during the installation process. The RBACAdmin user is only assigned the RBACAdmins role. For more information, see RBACAdmin and BLAdmin users.
   -J CONFIRM_BSA_RBACADMIN_PASSWORD	The RBACAdmin password once again, for confirmation.

    

   Agent mapping
   

   Option	Description of value
   -J AGENT_MAPPING_LOCAL_ADMIN_USERNAME	The name of the local super user — root or root-equivalent user on Linux, local Administrator or Administrator-equivalent local user on Windows — to which the RSCD Agent should map incoming connections during the installation. The default on the first node is root on Linux and Administrator on Windows.

5. Change directory (cd) to the location where the installation file (setup.exe for Windows or setup.bin for Linux) resides in the temporary directory.

6. Run the installation program with the -i silent option, using the following command. Use an absolute path to the options file. Enclose the path in double quotation marks (" ").
   setup.exe|setup.bin -i silent -DOPTIONS_FILE="<OptionsFilePath>"

   Example

   (Windows) setup.exe -i silent -DOPTIONS_FILE="C:\Program Files\BMC Software\BladeLogic\silentinstall_win_options.txt"

   (Linux) setup.bin -i silent -DOPTIONS_FILE="/opt/bmc/bladelogic/silentinstall_linux_options.txt"

   Note

   The installation log file, bsainstallupgrade.log, is stored in %TEMP% (on Windows) or in /tmp (on Linux). For more information about the log files created by the unified product installer, see the Troubleshooting section.