Preparing to install Remedy SSO with the Remedy installer

This topic provides information that you can use to prepare your environment for installing the Remedy Single Sign-On (Remedy SSO) product by using the Remedy installer. 

Related topics

Planning the Remedy SSO deploymentUpgrading Remedy SSO from an earlier version to 9.1.03.001

Remedy-SSO-system-requirements-for-TrueSight-Operations-Management

Downloading-the-installation-files

Important

If you have installed an earlier version of Remedy SSO, for example, 9.1.00, and want to upgrade it to 9.1.03.001, do the following:

  • Skip this installation section
  • Review the system requirements and perform all preinstall steps mentioned in this section before upgrading Remedy SSO
  • Proceed to upgrading Remedy SSO before upgrading the Presentation Server.

For more information, click the Planning the Remedy SSO deployment and Upgrading Remedy SSO links in the Related topics section.

Preinstallation requirements for Remedy Single Sign-On

Before installing Remedy SSO, you must have:

  • Downloaded the zipped Remedy SSO files through the Electronic Product Download (EPD) or the Remedy SSO DVD.
  • All the required hardware and software are available to install Remedy SSO. For more information on the system requirements, see System requirements.
  • Downloaded latest stable version of Tomcat server 7.x or above installed. Remedy SSO installer does not include bundled Tomcat. 
  • Performed the installation and configuration of the Tomcat server outside Remedy SSO and before the installing Remedy SSO. 
  • Connected to the available database from the server where you install Remedy SSO.
  • Configured the required security level for the installation environment. For more information about security requirements, see Security planning.
  • Configured the sticky session on the load balancer or session replication enabled on the Tomcat instances if you are planning to use the Remedy SSO Admin console in HA mode, else the system displays the login page when the load balancer redirects the requests between different nodes.

Security Planning for Remedy SSO

Review the following sections to understand the security requirements:

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

Database permissions for Remedy SSO

Ensure that you have database user credentials with permissions to create tables and read/write data to them or you have admin credentials to create such a user during installation. You can use the following script examples for creating such permissions:

Note:

Use a new database name for Remedy SSO to prevent the table name conflict for the Configuration table. If you are using Oracle, create a new schema for Remedy SSO before running the Remedy installer. At the time of installation select the new database.

MS SQL

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>

Oracle

CREATE USER <user> IDENTIFIED BY <pwd>
GRANT CONNECT, RESOURCE TO user IDENTIFIED BY <pwd>

If you have Oracle 12c on the system, you must run the following script to provide a quota for a user on the tablespace.

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

PostgreSQL

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>";

Sticky session for Remedy SSO HA load balancer

The referenced document [confluencePage:page:rsso91.Installing Remedy SSO] was not found.

Where to go from here

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*