Installing Remedy SSO silently
Creating an options.txt file
Before creating an options.txt file, identify the options that you want to include in the installer.
Options for a standalone installation
-A productRemedySSO
-J INSTALL_TYPE=true
-J TOMCAT_HOME=<path to tomcat home> example: D:\tc
-J DB_TYPE=<MSSQL | Oracle>
-J DB_HOST=<FQDN host> example: access.bmc.com
-J DB_PORT=1433
-J DB_MSSQL_INSTANCE=MSSQL
-J DB_MSSQL_DBNAME=rsso_ok21
-J DB_USER=RSSO_USER_OK21
-J DB_USER_PWD=<password>
-J DB_ADMIN=sa
-J DB_ADMIN_PWD=<password>
-J COOKIE_DOMAIN=<cookie domain> example: bmc.com
Options for a high-availability installation
-A productRemedySSO
-J INSTALL_TYPE=true
-J TOMCAT_HOME=<path to tomcat home> example: D:\tc
-J DB_TYPE=<MSSQL | Oracle>
-J DB_HOST=<FQDN host> example: access.bmc.com
-J DB_PORT=1433
-J DB_MSSQL_INSTANCE=MSSQL
-J DB_MSSQL_DBNAME=rsso_ok21
-J DB_IS_USER_EXIST=true
-J DB_USER=RSSO_USER_OK21
-J DB_USER_PWD=<password>
-J COOKIE_DOMAIN=<cookie domain> example: bmc.com
Options to support an installation for the PostgreSQL database
-A productRemedySSO
-J INSTALL_TYPE=true
-J TOMCAT_HOME=<path to tomcat home> example: C:\Program Files\Apache Software Foundation\Tomcat 7.0_sso_server_18081
-J DB_TYPE=Postgres
-J DB_HOST=localhost
-J DB_PORT=5432
-J DB_POSTGRES_DBNAME=rsso_si
-J DB_USER=rsso_user_si
-J DB_USER_PWD=<password>
-J DB_ADMIN=postgres
-J DB_ADMIN_PWD=<password>
-J COOKIE_DOMAIN=<cookie domain> example: bmc.com
Options to support an installation for the Oracle database by using Kerberos
This installation enables the Remedy SSO server to connect to the Oracle database without a password by using Kerberos. In addition to generating the options.txt file, perform the following steps:
- Make sure you have a pre-created Kerberos user.
Check if the Kerberos ticket is obtained by running the klist command.
In the terminal, you should see ticket cache, default principal, validation starting date, expiration date, and service principal.
If not, obtain a new Kerberos ticket by running the kinit command, for example:kinit RSSO_USER@BMC.COMIn the Oracle database, create an Oracle user identified externally as Kerberos user by using the SQL script for the pre-created user in step 1.
See the following example SQL script where Oracle user "RSSO_USER" is created for Kerberos user "RSSO_USER@BMC.COM":CREATE USER "RSSO_USER" IDENTIFIED EXTERNALLY AS 'RSSO_USER@BMC.COM';
ALTER USER "RSSO_USER" QUOTA UNLIMITED ON "USERS";
GRANT CREATE SESSION TO "RSSO_USER";
GRANT ALTER SESSION TO "RSSO_USER";
GRANT CREATE TABLE TO "RSSO_USER";
GRANT CREATE SYNONYM TO "RSSO_USER";
GRANT CREATE VIEW TO "RSSO_USER";
GRANT CREATE SEQUENCE TO "RSSO_USER";
GRANT CREATE PROCEDURE TO "RSSO_USER";
GRANT CREATE TRIGGER TO "RSSO_USER";
GRANT CREATE TYPE TO "RSSO_USER";Configure Kerberos on Tomcat by setting the CATALINA_OPTS environment variable. To do so, run the following command:
export CATALINA_OPTS='-Djava.security.krb5.conf=<path to krb5.conf> -Doracle.net.kerberos5_cc_name=<path to the ticket cache file> -Dsun.security.krb5.debug=true -Doracle.net.kerberos5_mutual_authentication=true -Doracle.net.authentication_services="(KERBEROS5)"'- Add the following parameters to the options.txt file:
-J KERBEROS5_CC_NAME=<path to the ticket cache file>
-J KERBEROS_ENABLED=true
KERBEROS_CONF_FILE and KERBEROS5_CC_NAME depend on the system settings and must be the same as specified in CATALINA_OPTS.
When you prepare the configured options.txt file and set up additional prerequisites (for Oracle database by using Kerberos), you can run the installer in silent mode.
To run the installer silently
- Edit the options.txt file by performing the following actions:
- Remove the comment (#) markers.
- In UNIX environments, make sure that no Ctrl+M characters appear in the options.txt file.
- Run the installer with the -i silent option:
- (Windows) setup.exe -i silent -DOPTIONS_FILE=<path_to_txt_file_with_installation_options>
- (UNIX) sh setup.sh -i silent -DOPTIONS_FILE=<path_to_txt_file_with_installation_options>
You have deployed Remedy SSO in silent mode.