This documentation supports the 19.05 version of Remedy Single Sign-On.

To view an earlier version, select the version from the Product version menu.

Manually installing Remedy SSO

This topic describes how to install Remedy Single Sign-On by manually running the installation scripts. 

Before you begin

Before you install Remedy SSO, ensure that your environment meets the hardware and software requirements described in System requirements

Manual installation overview

Manual installation of the Remedy SSO comprises of the following stages:

  1. Deploy Remedy SSO on Tomcat web server
  2. Manually create a database for Remedy SSO
  3. Set up a database for Remedy SSO
  4. Encrypt the database password
  5. Configure the Remedy SSO web server

Task 1: To deploy Remedy SSO on the Tomcat web server 

  1. Install Tomcat.

  2. Deploy rsso.war to the <Tomcat>/webapps/rsso folder.

Task 2: Manually create a database for Remedy SSO 

The database is usually configured through the installer. However, when you install Remedy SSO by running scripts or automation tools, you must configure the database manually.

Perform one of the following tasks to create a database:

To manually create a Microsoft SQL Server database

  1. Make sure that SQL Server is configured for SQL Server authentication and not integrated for Windows authentication.
  2. Run the following script:

    CREATE DATABASE <database>
    CREATE LOGIN user WITH PASSWORD = <pwd>, DEFAULT_DATABASE = <database>
    USE <database>
    CREATE USER <user> FOR LOGIN <user> WITH DEFAULT_SCHEMA = dbo
    EXEC SP_ADDROLEMEMBER DB_OWNER, <user>
    

To manually create an Oracle database

  1. Create a new schema for Remedy SSO. At the time of installation, select a new database.
  2. Run the following script:

    CREATE USER <user> IDENTIFIED BY <pwd>
    GRANT CONNECT, RESOURCE TO user IDENTIFIED BY <pwd>
  3. (Oracle 12c) For Oracle 12c, you must additionally grant a quota on tablespaces for the user. To do this, run the following script:

    ALTER USER <user> quota unlimited on <tablespace name>

To manually create a PostgreSQL database 

Run the following script:

CREATE DATABASE "<database>";
CREATE ROLE "<user>" WITH LOGIN PASSWORD '<pwd>';
GRANT ALL PRIVILEGES ON DATABASE "<database>" TO "<user>";
GRANT ALL ON ALL TABLES IN SCHEMA public TO "<user>";

Task 3: To set up a database for Remedy SSO 

After you create the database, perform the following steps to set up your database:

  1. Copy rsso-database-all.jar and database.properties from the rsso-database to some place on your system,  for example, copy to C:\ directory.

  2. Edit the database.properties and update the values for the following parameters:

    database-type=<database_type>
    db-url=<database_jdbc_url>
    db-user-id=<db_user_name>
    db-password=<db_user_password>
    #db-password must be plain text value

    The database-type value and db-url format are specific to a database type. The following examples show how to properly set values for these parameters: 

    Example: SQL Server database
    database-type=MsSql
    #db-url=jdbc:sqlserver:// <DB_server_hostname>:<Port> ;instanceName= <instance_name> ;databaseName=<database_name> 
    db-url=jdbc:sqlserver://AMS3-SQ-DEV01:1433;instanceName=DEV01;databaseName=whthat_dev_ar
    Example: Oracle database
    database-type=Oracle
    #db-url=jdbc:oracle:thin:@[host][:port]:SID
    db-url=jdbc:oracle:thin:@localhost:1521:XE
    Example: PostgreSQL database
    database-type=Postgres
    #db-url=jdbc:postgresql://[host]:[port]/[database]
    db-url=jdbc:postgresql://localhost:5432/rsso
  3. Ensure that the correct version of Java (Java 8, 11, or higher) is in the system path.

  4. Navigate to the directory where the rsso-database-all.jar and database.propeties files are located, and run the following command: 

    java -jar rsso-database-all.jar database.properties

    The output displayed in the console with no errors encountered  indicates that the Remedy SSO database tables are successfully created or upgraded. You can log in to the database management tool to verify that the tables exist.

Task 4: To encrypt the database password 

To configure Remedy SSO with the database settings, it is recommended to encrypt the database password. To generate an encrypted password, perform the following steps:

  1. Open the command line window, and navigate to the <TOMCAT_HOME>/rsso/WEB-INF/lib.
  2. Run the following command:

    java -jar rsso-ds.jar -cp <TOMCAT>/rsso/WEB-INF/classes <message-to-encrypt> <initialkey>

Task 5: To configure the Remedy SSO web server 

  1. Go to the Remedy SSO Tomcat folder and stop the Tomcat server.

  2. Edit the <Tomcat>/webapps/rsso/META-INF/context.xml and configure the following parameters:

    ParameterDescription

    url

    Set to the value of the db-url parameter that you used to set up your database.
    usernameSet to the value of the db-user-id parameter that you used to create your database.
    passwordSet to the value of the db-password parameter that you used to set up your database. Best practice: BMC recommends that use the encrypted password value. The format of the encrypted password value is the following: AES:<encrypted password>.
    driverClassThis value depends on your database.
    • (Microsoft SQL Server) Set the value to com.microsoft.sqlserver.jdbc.SQLServerDriver

    • (Oracle) Set the value to oracle.jdbc.driver.OracleDriver 
    • (PostgreSQL) Set the value to org.postgresql.Driver
  3. Copy the following jdbc driver libraries to the <tomcat>/lib folder:

    • sqljdbc4-4.0.jar

    • ojdbc6-11.2.0.2.0.jar

    • postgresql-9.4.1207.jre7.jar

  4. Restart the Tomcat server.

Where to go from here

Verifying the installation

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

Comments

  1. Abhijeet Anand

    In the section "To manually create an Oracle database" #3. The SQL given is:

    ALTER USER quota unlimited on

    Which tablespace you are referring here?

    Jul 17, 2019 08:10
    1. Abhijeet Anand

      Do we need to create a separate tablespace for RSSO?

      Jul 17, 2019 08:13
      1. Olga Kutetska

        Hello!

        Thank for the questions.

        If a db admin does not create an own tablespace, the default table space "USERS" is used. If an admin has created a tablespace, then he should specify in the Oracle script the name of the space he created. A separately created tablespace is not required. It can be used only if there is some special need for this.


        Jul 18, 2019 07:05