Silent installation properties

This topic describes the options that you can specify in a silent installation options file. The silent installation options file is a text file that defines the type of installation, the components to install, the installation location, and the configuration settings for the components. You specify installation properties in the form of a prefix tag followed by a property name and value pair. See the following sample options file for installing the product.

Prefix tags

The following table lists the prefix tags that precede the installation properties.

Prefix tags for silent installation properties

Property flag

Description

-J

Precedes Java properties

-P

Precedes directory properties

-A

Precedes application features

Tip

For a better view of the information in this topic, hide the navigation pane on the left side of your screen by pressing [ or open the page in full screen mode by pressing F. To show the navigation pane, press [ or to exit full-screen mode, press Esc.

Note

You must encrypt the password for each of the password properties. You can use run the BRPMMaintenanceTool.cmd tool packaged with the solution for encrypting passwords. This tool is located in the RLMhome\Disk1\utility directory.

Property nameRequired?Description
New installation
-P installLocationYes

Specifies the full path to the installation directory.

Default value:

  • Windows: C:\Program Files\BMC Software\RLM
  • UNIX: /opt/bmc/RLM
Feature selection

Any combination
of the following lines:

-A featureDeploymentUI
-A featureDeploymentEngine
-A PostgreSQL

Yes,
at least one

Specifies the features that you want to install.

You can install the BMC Release Package and Deployment product.

Installation of the Deployment Engine and the PostgreSQL database are optional.

The -A lines specify any combination of the following features:

  • BMC Release Package and Deployment
  • Deployment Engine (for BMC Release Package and Deployment)
  • PostgreSQL server
Migration information for BMC Release Package and Deployment
(Only supported when migrating from version 4.3.00 to a later version)

-J BMC_MIGRATE_
EXISTING_Q_INSTALLATION

No

Specifies whether to migrate from an earlier version of BMC Release Package and Deployment to the later version.

Default value: false

If you change this value to true, you must also change the values of the following properties as given:

  • -J BMC_Q_DATABASE_MIGRATION=
    • USE_SAME_DATABASE to migrate your earlier version's database to the later version
    • USE_SAME_DATABASE_EMPTY_
      DATABASE_CONTENTS
      to delete the earlier version's database and create a new database
  • -J BMC_Q_MIGRATION_VERSION=BRLM_4_3_00
    Specifies the existing product version.
  • -J BMC_REFERENCE_Q_INSTALLATION_PATH=path
    Provide the directory path where your earlier version of BMC Release Package and Deployment is located.
    Your earlier product version might be installed at RLMhome\4.4.00\RPD.

JRE information

-J USE_BMC_BUNDLED_JRE

Yes

Specifies whether the JRE bundled with the product must be installed or not for BMC Release Process Management.

  • Set to true if the bundled JRE must be installed.
  • Set to false if you want to use JRE version that is already installed on your computer.

Note: If you  want to use JRE that is installed on your computer, specify the USE_BMC_BUNDLED_JRE property.

-J BMC_JAVA_JRE_PATH

No*

Specifies the path for the JRE on your computer BMC Release Process Management.

Note: This property is required only if you want to use JRE installed on your computer (-J USE_BMC_BUNDLED_JRE=false).

Example: -J BMC_JAVA_JRE_PATH=C:\BRPM\lib\jre

Installation type
-J BMC_BRPM_INSTALL_TYPEYes

Specifies whether you perform the installation as a root or as a normal user.

  •  If you make installation as a normal user:
    -J
    BMC_BRPM_INSTALL_TYPE=PARTIAL_PRIVILEGE
  •  If you make installation as a root user:
    -J
    BMC_BRPM_INSTALL_TYPE=FULL_PRIVILEGE
HTTP/HTTPS port information
-J BMC_Q_HTTP_PORTYes

Specifies the HTTP port on which the Apache server for the BMC Release Package and Deployment component product runs.

Example: BMC_Q_HTTP_PORT=80

-J Q_USE_HTTPSNo

Specifies whether to enable SSL settings for the Apache server for BMC Release Package and Deployment.

Note:

If you want to use SSL for your Apache server, the following properties are required:

  • -J BMC_Q_HTTPS_PORT
  • -J BMC_Q_PRIVATE_KEY
  • -J BMC_Q_CERTIFICATE_FILE
  • -J BMC_Q_KEY_PASSWORD

To use SSL, enter USE_HTTPS.

Leave this property blank to use HTTP.

Example: -J Q_USE_HTTPS=USE_SSL

-J BMC_Q_HTTPS_PORTNo*

Specifies the HTTPS port for BMC Release Package and Deployment.

Note: This property is required only if you use SSL for your Apache server (-J Q_USE_HTTPS=USE_SSL).

Example: -J BMC_Q_HTTPS_PORT=443

-J BMC_Q_PRIVATE_KEYNo*

Specifies the path to the private key for the BMC Release Package and Deployment.

Note: This property is required only if you use SSL for your Apache server (-J Q_USE_HTTPS=USE_SSL). 

Example: -J BMC_Q_PRIVATE_KEY=/tmp/key.der

-J BMC_Q_CERTIFICATE_FILENo*

Specifies the path to the certificate file for BMC Release Package and Deployment.

Note: This property is required only if you use SSL for your Apache server (-J Q_USE_HTTPS=USE_SSL). 

Example: -J BMC_Q_CERTIFICATE_FILE=/tmp/cert.der

-J BMC_Q_KEYSTORE_PASSWORDNo*

Specifies the password used to generate the private key for BMC Release Package and Deployment.

Note: This property is required only if you use SSL for your Apache server (-J Q_USE_HTTPS=USE_SSL). 

Example: -J BMC_Q_KEYSTORE_PASSWORD=DES\:c0327a60f9d00b3780258e5f6fe

Superuser information
-J BMC_SUPERUSER_
FIRSTNAME
Yes

Specifies the first name for the superuser.

Example: -J BMC_SUPERUSER_FIRSTNAME=John

-J BMC_SUPERUSER_
LASTNAME
YesSpecifies the last name for the superuser.
Example: -J BMC_SUPERUSER_LASTNAME=Administrator
-J BMC_SUPERUSER_EMAILYes

Specifies the email ID of the superuser.

Example: -J BMC_SUPERUSER_EMAIL=admin@example.com

-J BMC_SUPERUSER_LOGINYes

Specifies the superuser's login ID, used for the first login.

Example: -J BMC_SUPERUSER_LOGIN=admin

-J BMC_SUPERUSER_
PASSWORD

-J BMC_SUPERUSER_
CONFIRM_PASSWORD

Yes

Specifies the encrypted password corresponding to the superuser's login ID.
The password must be encrypted by the utility provided.

Examples:

  • -J BMC_SUPERUSER_PASSWORD= DES\:9c61a83f6c17233a2d6a967aa95bb1ec
  • -J BMC_SUPERUSER_CONFIRM_PASSWORD= DES\:9c61a83f6c17233a2d6a967aa95bb1ec
Database information
-J BMC_DB_TYPEYes

Specifies the database that you want to use.

 You can specify one of the following values:

  • POSTGRESQL
  • ORACLE
  • SQL_SERVER
-J BMC_DB_HOSTYes

Specifies the computer name or the IP address of the server where your database is installed.

Example: -J BMC_DB_HOST=127.0.0.1

-J BMC_DB_PORTYes

Specifies the port of the server that you used for installing your database.

Example:

PostgreSQL: -J BMC_DB_PORT=5432
Oracle:-J BMC_DB_PORT=1521
SQL_Server: -J BMC_DB_PORT=1433

-J BMC_Q_DB_NAMEYes

Specifies the database name or SID for the BMC Release Package and Deployment database.

  • If you use POSTGRESQL or SQL_SERVER, specify the name of the database instance that was used during the database installation.
  • If you use ORACLE, specify the SID details.

Example:-J BMC_Q_DB_NAME=bmc_rpm_db

-J BMC_Q_DB_USER_NAMEYes

Specifies the user name of the database instance that you used while creating it at the time of the database installation.

This property is related to the BMC Release Package and Deployment installation.

Example: -J BMC_Q_DB_USER_NAME=rlmuser

-J BMC_Q_KEYSTORE_PASSWORDYes

Specifies the encrypted password of the database instance that you used while creating it at the time of the database installation.

This property is related to the BMC Release Package and Deployment installation.

Example:-J BMC_Q_KEYSTORE_PASSWORD = DES\:9c61a83f6c17233a2d6a967aa95bb1ec

Email notification information

-J MAIL_NOTIFICATIONS

Yes

Specifies whether you want to use email notification settings for the BMC Release Lifecycle Management or not.

Set the value of this property:

  • Not to receive email notifications:
    -J
    MAIL_NOTIFICATIONS=NO_NOTIFICATIONS
  • To use and configure email notifications:
    -J MAIL_NOTIFICATIONS=USE_SMTP

Note:

If you want to receive email notifications, set values for the following properties:

  • -J BMC_SMTP_HOST
  • -J BMC_SMTP_PORT
  • -J BMC_SMTP_DOMAIN_NAME
  • -J BMC_SMTP_AUTHENTICATION
  • -J BMC_SMTP_USER_NAME
  • -J BMC_SMTP_USER_PASSWORD
  • -J BMC_SMTP_TL

-J BMC_SMTP_HOST

No*

Specifies the fully qualified name or the IP address of the SMTP server used for sending emails.

Note: This property is required if you configure to receive email notifications (-J MAIL_NOTIFICATIONS=USE_SMTP).

Example: -J BMC_SMTP_HOST=smtp.gmail.com

-J BMC_SMTP_PORT

No*

Specifies the SMTP server port.

Note: This property is required if you configure to receive email notifications (-J MAIL_NOTIFICATIONS=USE_SMTP).

Example: -J BMC_SMTP_PORT=25

-J BMC_SMTP_DOMAIN_NAME

No*

Specifies the SMTP domain name in email notification address.
For example, if your username is redmine@example.net, then your domain name is example.net.

Note: This property is required if you configure to receive email notifications (-J MAIL_NOTIFICATIONS=USE_SMTP).

Example: -J BMC_SMTP_DOMAIN_NAME=$SMTP_DOMAIN

-J BMC_SMTP_AUTHENTICATION

No*

Specifies the authentication mechanism used for your SMTP service.

Note: This property is required if you configure to receive email notifications (-J MAIL_NOTIFICATIONS=USE_SMTP).

Set one of the following values:

  • none
  • plain
  • login
  • cram_md5

Example:-J BMC_SMTP_AUTHENTICATION=login

-J BMC_SMTP_USER_NAME

No*

Specifies the user name used to connect to the SMTP server.

Note:

This property is required under following conditions:

  • You configure to receive email notifications (-J MAIL_NOTIFICATIONS=USE_SMTP
  • You do not use SMTP authentication (-J BMC_SMTP_AUTHENTICATION=none)

Example: -J BMC_SMTP_USER_NAME=brpmtest2@gmail.com

-J BMC_SMTP_USER_PASSWORD

No*

Specifies the encrypted password used to connect to the SMTP server.

Note:

This property is required under following conditions:

  • You configure to receive email notifications (-J MAIL_NOTIFICATIONS=USE_SMTP
  • You do use SMTP authentication (-J BMC_SMTP_AUTHENTICATION=plain, -J BMC_SMTP_AUTHENTICATION=login, or -J BMC_SMTP_AUTHENTICATION=cram_md5)

Example: -J BMC_SMTP_USER_PASSWORD= DES\:35582269c6fa5491949a671e3db0c4c5

-J BMC_SMTP_TLS

No*

Specifies whether your SMTP server requires a secure connection and is using TLS or not.

  • If you use secure connection (TLS), set this property to true
  • If you use HTTP, set this property to false

Note: This property is required if you configure to receive email notifications (-J MAIL_NOTIFICATIONS=USE_SMTP).

Example: -J BMC_SMTP_TLS=true

Other properties
-J BMC_DEPLOYMENT_
ACTION_PACKS_LIST
No

Specifies the list of action packs that you plan to manage in BMC Release Package and Deployment.

Example:
-J BMC_DEPLOYMENT_ACTION_PACKS_LIST=Amazon,
CVS,BizTalk_2010,
GlassFish_3,JBoss_6,
Perforce,SharePoint_2010,TIBCO_BW,
WebLogic_10,
Apache_2,Blade,Hyper_V,JetBrains,
Php_5,Sonatype,Tomcat_6,
WebSphere_6,Atlassian,
Citrix,IIS_6,Mercurial,Rational,Subversion,
Tomcat_7,WebSphere_7,BMA,DB2,IIS_7,MySQL_5,
SQLServer_2008,System,
VMware,WebSphere_8,
BizTalk_2006,F5,JBoss_5,Oracle_11g,

SharePoint_2007,TFS,VSS,nsh,BizTalk_2009,Git

Related topic

Silent installation

Was this page helpful? Yes No Submitting... Thank you

Comments