_silentOptions
Installation Directory option
Option | Description of value |
|---|---|
-P installLocation | The installation directory for the product. -P installLocation=C:\Program Files\BMC Software\BladeLogic -P installLocation=/opt/bmc/bladelogic/ |
Database options
Option | Description of value |
|---|---|
-J DATABASE_TYPE | The type of database that you have set up for TrueSight 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. |
-J SCHEMA_PASSWORD | Encrypted version of the password assigned to the user ID. |
-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:
|
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. |
Port option
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. |
Password options
Option | Description of value |
|---|---|
-J BSA_CERTIFICATE_PASSWORD | The initial password of the default security certificate for TrueSight 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
Option | Description of value |
|---|---|
-J FILE_SERVER_AGENT_MAPPING_LOCAL_ADMIN_USERNAME | The name of the local super user for the file server— 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. When the file server and Application Server are on the same host, ensure that you use this option. |
-J APP_SERVER_AGENT_MAPPING_LOCAL_ADMIN_USERNAME | The name of the local super user for the Application Server— 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. When the file server and Application Server are on different hosts, ensure that you use the following options:
|
Console option
Option | Description of value |
|---|---|
-J INSTALL_BLADELOGIC _SERVER_AUTOMATION_CONSOLE | Whether to install the TrueSight Server Automation Console together with the default Application Server, on the same host computer — either false or true. By default, the Console is not installed together with the Application Server (a value of false), as BMC recommends installing the Console on a separate machine, for high performance. |
Alternate temporary directory for Linux option
Option | Description of value |
|---|---|
-J PROP_DEFAULT_STAGING_PATH_UNIX | Sets the value of the alternate temp directory if the default directory /tmp does not have enough free space. The default value of this option is /tmp. |
SRP Account options (for upgrade)
Use the following options to enable access to the Application Server during the upgrade:
Option | Description of value |
|---|---|
-J BSA_APPSERVER_PROFILE | Name of a profile on the Application Server to use during the upgrade for SRP authentication. The profile that you specify must be associated with the same Application Server where you are performing the upgrade. |
-J BSA_APPSERVER_PROFILE_USER | Name of a user for SRP authentication. For example: |
-J BSA_APPSERVER_PROFILE_USER_PASSWORD | A valid password for the specified user. |
Agent options (for upgrade)
Use the following options to authorize the installer to install an RSCD Agent on any remote server where an RSCD Agent is not yet installed (as will be detected by the installer during the upgrade):
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. |
-J PSEXEC_SERVER_HOSTNAME | Host name or IP address of the PSExec host computer. |
-J USE_COMMON_CREDENTIALS_FOR _APPSERVERS_WHERE_RSCD_AGENT _NOT_REACHABLE | Whether to use the same credentials (user name and password) to access all remote servers where the RSCD Agent is not yet installed — either true or false. |
The following options are relevant only when USE_COMMON_CREDENTIALS_FOR_APPSERVERS_WHERE_RSCD_AGENT_NOT_REACHABLE=true | |
-J REMOTE_CONNECTION_COMMON_USERNAME | The name of a user authorized to establish an SSH connection with all remote hosts where the RSCD Agent is not yet installed. |
-J REMOTE_CONNECTION_COMMON_PASSWORD | A valid password for the specified user name. |
-J REMOTE_CONNECTION_COMMON _CONFIRM_PASSWORD | The password once again, for confirmation. |
The following options is relevant only when USE_COMMON_CREDENTIALS_FOR_APPSERVERS_WHERE_RSCD_AGENT_NOT_REACHABLE=false | |
-J LIST_OF_APPSERVER_CREDENTIALS | A list of the remote hosts where an RSCD Agent is not yet installed, along with separate credentials for each of these hosts. To specify the hosts and logon credentials, use the following format: "host1,user1,password1;host2,user2,password2" Use commas within each set of credentials (for each separate host). Use semicolons between sets of credentials. Enclose the full list in quotation marks. |
PXE Server options (for upgrade)
Use the following option to specify a list of remote PXE servers during upgrade of TrueSight Server Automation:
Option | Description of value |
|---|---|
-J LIST_OF_REMOTE_PXE_SERVER | A list of PXE servers that reside on hosts that are separate from the current Application Server. This enables the installer to copy installation files to the remote hosts. To specify the remote PXE servers, use the following format:"host1;host2;host3" Use semicolons between hosts, and enclose the full list in quotation marks. Note the following additional scenarios:
|