This documentation supports the 22.1 version of BMC Helix Single Sign-On, which is available only to BMC Helix customers (SaaS). To view an earlier version, select the version from the Product version menu.
Installation worksheets
Before you start installing BMC Helix Single Sign-On, you must gather information about the parameters that the installer requires. The planning spreadsheet provided in this section helps you gather these parameter values. To avoid installation errors, refer to this spreadsheet when you run the installation.
Before you install BMC Helix SSO, download the Installation Excel worksheet (which includes the four worksheets below) and gather information about the installation parameter values you will need to enter.
"Install Remedy SSO server" worksheet
Overview
Install Remedy SSO server
Integrate with AR System
Integrate with Mid Tier
Integrate with BMC Analytics
Sheet 1: Install Remedy SSO server
| Field in installer | Example value for Windows | Example value for Linux | Your value | Description | Notes |
| Remedy Single Sign-On server information | |||||
| Destination directory | C:\Program Files\BMC Software\Remedy SSO | /<root>/opt/bmc/Remedy SSO | Accept the default destination directory or browse to select a different directory. | ||
| Tomcat directory path | C:\Program Files\Apache Software Foundation\Tomcat 7.0 | /opt/bmc/tomcat7 | Browse to select the Apache Tomcat directory path where Remedy SSO will be deployed. | (Linux) Run Tomcat and the Remedy SSO installer from the same user group. For example, if Tomcat is running under root privileges, then you must run the Remedy SSO installer under the same privileges. | |
| Remedy Single Sign-On feature selection | |||||
| BMC Remedy Single Sign-On installation | Install BMC Remedy Single Sign-On installation | Install BMC Remedy Single Sign-On installation | Select BMC Remedy Single Sign-On installation. | To integrate RSSO with other products, you need to run this installer separately on the servers where the integrated products are installed. | |
| Remedy Single Sign-On database information | |||||
| Type | Microsoft SQL | Oracle | Select one of the following types: - Microsoft SQL - Oracle - PostgresSQL - Embedded | The Embedded type is an in-memory database, and it does not need separate installation. The Remedy SSO installer installs and sets up this database at the time of installation. BMC recommends using the embedded database for testing and demo purposes only and not using it in the production environment. (HA environment) Do not select embedded database if you plan to create an HA enviriment. | |
| Host | clm-tex-090897.bmc.com | clm-tex-090897.bmc.com | Fully qualified domain name of the database server. | ||
| Port | 1433 | 1521 | Port of the database server. | ||
| Instance | MSSQL | Oracle | Name of the database instance. | ||
| Database name | rsso | rsso | Name of the database. | You must not use the AR System database name for Remedy SSO if you plan to integrate Remedy SSO with BMC Remedy AR System. Use a new database name for Remedy SSO to prevent the table name conflict. | |
| Remedy Single Sign-On database user information | |||||
| Assign database user(s) | Create New User | Select one of the following options: -Create New User -Use Existing User | (HA environment) On a secondary node in an HA environment, select the Use Existing User option. | ||
| Database admin name | sa | sa | You need to provide these details if you selected to create a new database user. | ||
| Database admin password | bmcAdm!n | bmcAdm!n | |||
| Database user name | rsso_user | rsso_user | This user can access the details of application configuration and user sessions. You can provide the credentials of an existing database user that has permissions to create tables, or you can create a new user. | (HA environment) On a secondary node in an HA environment, use the credentials that you provided for the primary node. | |
| Database user password | userPa$1 | userPa$1 | |||
| Cookie domain | bmc.com | bmc.com | The domain value of the cookie must be the network domain of Remedy SSO or one of its parent domains. | ||
Sheet 2: Integrate with AR System
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Remedy AR System | Select to integrate with BMC Remedy AR System. | |
| Remedy Single Sign-On server information | |||
| Path to BMC Remedy AR System Home | C:\Program Files\BMC Software\ARSystem | Enter the directory path where BMC Remedy AR System application is installed. | |
| Remedy Single Sign-On server information | |||
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | It is used for internal back end communication between AR System agent and BMC Remedy Single Sign-On instance. Generally that communication happens behind firewall, so you ca use HTTP or HTTPS. The format of the URL must be the following: <Protocol>://<FQDN host name>:<Port>/<context path>. (High availability) In the HA mode, this URL must be the URL of a load balancer. | |
Sheet 3: Integrate with Mid Tier
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Remedy Mid Tier | Select to integrate with BMC Remedy Mid Tier. | |
| Remedy Mid Tier server information | |||
| Path to BMC Remedy Mid Tier Home | C:\Program Files\BMC Software\ARSystem\midtier | Enter the directory path where BMC Remedy Mid Tier application is deployed. | |
| Path to BMC Remedy Mid Tier Web server | C:\Program Files\Apache Software Foundation\Tomcat 7.0 | Enter the home directory of the Tomcat server on which Remedy AR System Server and Mid Tier is deployed. It is the Tomcat server that uses port 8080 for connection to AR System. | |
| Remedy Single Sign-On server information | |||
| Public BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | This URL is used to redirect unaothorized user request to BMC SSO instance for authentication. For the sake of security, the user facing URL should be HTTPS. The format of the URL must be the following: <Protocol>://<FQDN host name>:<Port>/<context path> (High availability) In the HA mode, it is the URL of the load balancer. | |
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-0103645.bmc.com:9080/rsso | This URL is used for internal back end communication between Mid Tier agent and BMC Remedy Single Sign-On instance. Generally that communication happens behind firewall, so you ca use HTTP or HTTPS. For the sake of performance, in a secured area you can use HTTP. The format of the URL must ne the following: <Protocol>://<FQDN host name>:<Port>/<context path> (High availability) In the HA mode, it is the URL of the load balancer. | |
Sheet 4: Integrate with BMC Analytics
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Analytics | Select to integrate with BMC Analytics | |
| BMC Analytics for Business Service Management information | |||
| Analytics webserver path | Specify the directory path to BMC Analytics home. | ||
| Analytics home | C:\Program Files\BMC Software\ | Specify the directory where BMC Analytics is installed. | |
| Remedy Single Sign-On server information | |||
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | Enter the URL for communication between Remedy SSO and agent. The URL must be a Fully Qualified Domain Name (FQDN). | |
| Public BMC Remedy Single Sign-On instance URL | https://clm-aus-010365.bmc.com:9080/rsso | Enter the URL to redirect unauthenticated user requests to Remedy SSO for authentication. | |
"Integrate with AR System" worksheet
Overview
Install Remedy SSO server
Integrate with AR System
Integrate with Mid Tier
Integrate with BMC Analytics
Sheet 1: Install Remedy SSO server
| Field in installer | Example value for Windows | Example value for Linux | Your value | Description | Notes |
| Remedy Single Sign-On server information | |||||
| Destination directory | C:\Program Files\BMC Software\Remedy SSO | /<root>/opt/bmc/Remedy SSO | Accept the default destination directory or browse to select a different directory. | ||
| Tomcat directory path | C:\Program Files\Apache Software Foundation\Tomcat 7.0 | /opt/bmc/tomcat7 | Browse to select the Apache Tomcat directory path where Remedy SSO will be deployed. | (Linux) Run Tomcat and the Remedy SSO installer from the same user group. For example, if Tomcat is running under root privileges, then you must run the Remedy SSO installer under the same privileges. | |
| Remedy Single Sign-On feature selection | |||||
| BMC Remedy Single Sign-On installation | Install BMC Remedy Single Sign-On installation | Install BMC Remedy Single Sign-On installation | Select BMC Remedy Single Sign-On installation. | To integrate RSSO with other products, you need to run this installer separately on the servers where the integrated products are installed. | |
| Remedy Single Sign-On database information | |||||
| Type | Microsoft SQL | Oracle | Select one of the following types: - Microsoft SQL - Oracle - PostgresSQL - Embedded | The Embedded type is an in-memory database, and it does not need separate installation. The Remedy SSO installer installs and sets up this database at the time of installation. BMC recommends using the embedded database for testing and demo purposes only and not using it in the production environment. (HA environment) Do not select embedded database if you plan to create an HA enviriment. | |
| Host | clm-tex-090897.bmc.com | clm-tex-090897.bmc.com | Fully qualified domain name of the database server. | ||
| Port | 1433 | 1521 | Port of the database server. | ||
| Instance | MSSQL | Oracle | Name of the database instance. | ||
| Database name | rsso | rsso | Name of the database. | You must not use the AR System database name for Remedy SSO if you plan to integrate Remedy SSO with BMC Remedy AR System. Use a new database name for Remedy SSO to prevent the table name conflict. | |
| Remedy Single Sign-On database user information | |||||
| Assign database user(s) | Create New User | Select one of the following options: -Create New User -Use Existing User | (HA environment) On a secondary node in an HA environment, select the Use Existing User option. | ||
| Database admin name | sa | sa | You need to provide these details if you selected to create a new database user. | ||
| Database admin password | bmcAdm!n | bmcAdm!n | |||
| Database user name | rsso_user | rsso_user | This user can access the details of application configuration and user sessions. You can provide the credentials of an existing database user that has permissions to create tables, or you can create a new user. | (HA environment) On a secondary node in an HA environment, use the credentials that you provided for the primary node. | |
| Database user password | userPa$1 | userPa$1 | |||
| Cookie domain | bmc.com | bmc.com | The domain value of the cookie must be the network domain of Remedy SSO or one of its parent domains. | ||
Sheet 2: Integrate with AR System
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Remedy AR System | Select to integrate with BMC Remedy AR System. | |
| Remedy Single Sign-On server information | |||
| Path to BMC Remedy AR System Home | C:\Program Files\BMC Software\ARSystem | Enter the directory path where BMC Remedy AR System application is installed. | |
| Remedy Single Sign-On server information | |||
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | It is used for internal back end communication between AR System agent and BMC Remedy Single Sign-On instance. Generally that communication happens behind firewall, so you ca use HTTP or HTTPS. The format of the URL must be the following: <Protocol>://<FQDN host name>:<Port>/<context path>. (High availability) In the HA mode, this URL must be the URL of a load balancer. | |
Sheet 3: Integrate with Mid Tier
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Remedy Mid Tier | Select to integrate with BMC Remedy Mid Tier. | |
| Remedy Mid Tier server information | |||
| Path to BMC Remedy Mid Tier Home | C:\Program Files\BMC Software\ARSystem\midtier | Enter the directory path where BMC Remedy Mid Tier application is deployed. | |
| Path to BMC Remedy Mid Tier Web server | C:\Program Files\Apache Software Foundation\Tomcat 7.0 | Enter the home directory of the Tomcat server on which Remedy AR System Server and Mid Tier is deployed. It is the Tomcat server that uses port 8080 for connection to AR System. | |
| Remedy Single Sign-On server information | |||
| Public BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | This URL is used to redirect unaothorized user request to BMC SSO instance for authentication. For the sake of security, the user facing URL should be HTTPS. The format of the URL must be the following: <Protocol>://<FQDN host name>:<Port>/<context path> (High availability) In the HA mode, it is the URL of the load balancer. | |
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-0103645.bmc.com:9080/rsso | This URL is used for internal back end communication between Mid Tier agent and BMC Remedy Single Sign-On instance. Generally that communication happens behind firewall, so you ca use HTTP or HTTPS. For the sake of performance, in a secured area you can use HTTP. The format of the URL must ne the following: <Protocol>://<FQDN host name>:<Port>/<context path> (High availability) In the HA mode, it is the URL of the load balancer. | |
Sheet 4: Integrate with BMC Analytics
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Analytics | Select to integrate with BMC Analytics | |
| BMC Analytics for Business Service Management information | |||
| Analytics webserver path | Specify the directory path to BMC Analytics home. | ||
| Analytics home | C:\Program Files\BMC Software\ | Specify the directory where BMC Analytics is installed. | |
| Remedy Single Sign-On server information | |||
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | Enter the URL for communication between Remedy SSO and agent. The URL must be a Fully Qualified Domain Name (FQDN). | |
| Public BMC Remedy Single Sign-On instance URL | https://clm-aus-010365.bmc.com:9080/rsso | Enter the URL to redirect unauthenticated user requests to Remedy SSO for authentication. | |
"Integrate with Mid Tier" worksheet
Overview
Install Remedy SSO server
Integrate with AR System
Integrate with Mid Tier
Integrate with BMC Analytics
Sheet 1: Install Remedy SSO server
| Field in installer | Example value for Windows | Example value for Linux | Your value | Description | Notes |
| Remedy Single Sign-On server information | |||||
| Destination directory | C:\Program Files\BMC Software\Remedy SSO | /<root>/opt/bmc/Remedy SSO | Accept the default destination directory or browse to select a different directory. | ||
| Tomcat directory path | C:\Program Files\Apache Software Foundation\Tomcat 7.0 | /opt/bmc/tomcat7 | Browse to select the Apache Tomcat directory path where Remedy SSO will be deployed. | (Linux) Run Tomcat and the Remedy SSO installer from the same user group. For example, if Tomcat is running under root privileges, then you must run the Remedy SSO installer under the same privileges. | |
| Remedy Single Sign-On feature selection | |||||
| BMC Remedy Single Sign-On installation | Install BMC Remedy Single Sign-On installation | Install BMC Remedy Single Sign-On installation | Select BMC Remedy Single Sign-On installation. | To integrate RSSO with other products, you need to run this installer separately on the servers where the integrated products are installed. | |
| Remedy Single Sign-On database information | |||||
| Type | Microsoft SQL | Oracle | Select one of the following types: - Microsoft SQL - Oracle - PostgresSQL - Embedded | The Embedded type is an in-memory database, and it does not need separate installation. The Remedy SSO installer installs and sets up this database at the time of installation. BMC recommends using the embedded database for testing and demo purposes only and not using it in the production environment. (HA environment) Do not select embedded database if you plan to create an HA enviriment. | |
| Host | clm-tex-090897.bmc.com | clm-tex-090897.bmc.com | Fully qualified domain name of the database server. | ||
| Port | 1433 | 1521 | Port of the database server. | ||
| Instance | MSSQL | Oracle | Name of the database instance. | ||
| Database name | rsso | rsso | Name of the database. | You must not use the AR System database name for Remedy SSO if you plan to integrate Remedy SSO with BMC Remedy AR System. Use a new database name for Remedy SSO to prevent the table name conflict. | |
| Remedy Single Sign-On database user information | |||||
| Assign database user(s) | Create New User | Select one of the following options: -Create New User -Use Existing User | (HA environment) On a secondary node in an HA environment, select the Use Existing User option. | ||
| Database admin name | sa | sa | You need to provide these details if you selected to create a new database user. | ||
| Database admin password | bmcAdm!n | bmcAdm!n | |||
| Database user name | rsso_user | rsso_user | This user can access the details of application configuration and user sessions. You can provide the credentials of an existing database user that has permissions to create tables, or you can create a new user. | (HA environment) On a secondary node in an HA environment, use the credentials that you provided for the primary node. | |
| Database user password | userPa$1 | userPa$1 | |||
| Cookie domain | bmc.com | bmc.com | The domain value of the cookie must be the network domain of Remedy SSO or one of its parent domains. | ||
Sheet 2: Integrate with AR System
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Remedy AR System | Select to integrate with BMC Remedy AR System. | |
| Remedy Single Sign-On server information | |||
| Path to BMC Remedy AR System Home | C:\Program Files\BMC Software\ARSystem | Enter the directory path where BMC Remedy AR System application is installed. | |
| Remedy Single Sign-On server information | |||
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | It is used for internal back end communication between AR System agent and BMC Remedy Single Sign-On instance. Generally that communication happens behind firewall, so you ca use HTTP or HTTPS. The format of the URL must be the following: <Protocol>://<FQDN host name>:<Port>/<context path>. (High availability) In the HA mode, this URL must be the URL of a load balancer. | |
Sheet 3: Integrate with Mid Tier
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Remedy Mid Tier | Select to integrate with BMC Remedy Mid Tier. | |
| Remedy Mid Tier server information | |||
| Path to BMC Remedy Mid Tier Home | C:\Program Files\BMC Software\ARSystem\midtier | Enter the directory path where BMC Remedy Mid Tier application is deployed. | |
| Path to BMC Remedy Mid Tier Web server | C:\Program Files\Apache Software Foundation\Tomcat 7.0 | Enter the home directory of the Tomcat server on which Remedy AR System Server and Mid Tier is deployed. It is the Tomcat server that uses port 8080 for connection to AR System. | |
| Remedy Single Sign-On server information | |||
| Public BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | This URL is used to redirect unaothorized user request to BMC SSO instance for authentication. For the sake of security, the user facing URL should be HTTPS. The format of the URL must be the following: <Protocol>://<FQDN host name>:<Port>/<context path> (High availability) In the HA mode, it is the URL of the load balancer. | |
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-0103645.bmc.com:9080/rsso | This URL is used for internal back end communication between Mid Tier agent and BMC Remedy Single Sign-On instance. Generally that communication happens behind firewall, so you ca use HTTP or HTTPS. For the sake of performance, in a secured area you can use HTTP. The format of the URL must ne the following: <Protocol>://<FQDN host name>:<Port>/<context path> (High availability) In the HA mode, it is the URL of the load balancer. | |
Sheet 4: Integrate with BMC Analytics
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Analytics | Select to integrate with BMC Analytics | |
| BMC Analytics for Business Service Management information | |||
| Analytics webserver path | Specify the directory path to BMC Analytics home. | ||
| Analytics home | C:\Program Files\BMC Software\ | Specify the directory where BMC Analytics is installed. | |
| Remedy Single Sign-On server information | |||
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | Enter the URL for communication between Remedy SSO and agent. The URL must be a Fully Qualified Domain Name (FQDN). | |
| Public BMC Remedy Single Sign-On instance URL | https://clm-aus-010365.bmc.com:9080/rsso | Enter the URL to redirect unauthenticated user requests to Remedy SSO for authentication. | |
"Integrate with BMC Analytics" worksheet
Overview
Install Remedy SSO server
Integrate with AR System
Integrate with Mid Tier
Integrate with BMC Analytics
Sheet 1: Install Remedy SSO server
| Field in installer | Example value for Windows | Example value for Linux | Your value | Description | Notes |
| Remedy Single Sign-On server information | |||||
| Destination directory | C:\Program Files\BMC Software\Remedy SSO | /<root>/opt/bmc/Remedy SSO | Accept the default destination directory or browse to select a different directory. | ||
| Tomcat directory path | C:\Program Files\Apache Software Foundation\Tomcat 7.0 | /opt/bmc/tomcat7 | Browse to select the Apache Tomcat directory path where Remedy SSO will be deployed. | (Linux) Run Tomcat and the Remedy SSO installer from the same user group. For example, if Tomcat is running under root privileges, then you must run the Remedy SSO installer under the same privileges. | |
| Remedy Single Sign-On feature selection | |||||
| BMC Remedy Single Sign-On installation | Install BMC Remedy Single Sign-On installation | Install BMC Remedy Single Sign-On installation | Select BMC Remedy Single Sign-On installation. | To integrate RSSO with other products, you need to run this installer separately on the servers where the integrated products are installed. | |
| Remedy Single Sign-On database information | |||||
| Type | Microsoft SQL | Oracle | Select one of the following types: - Microsoft SQL - Oracle - PostgresSQL - Embedded | The Embedded type is an in-memory database, and it does not need separate installation. The Remedy SSO installer installs and sets up this database at the time of installation. BMC recommends using the embedded database for testing and demo purposes only and not using it in the production environment. (HA environment) Do not select embedded database if you plan to create an HA enviriment. | |
| Host | clm-tex-090897.bmc.com | clm-tex-090897.bmc.com | Fully qualified domain name of the database server. | ||
| Port | 1433 | 1521 | Port of the database server. | ||
| Instance | MSSQL | Oracle | Name of the database instance. | ||
| Database name | rsso | rsso | Name of the database. | You must not use the AR System database name for Remedy SSO if you plan to integrate Remedy SSO with BMC Remedy AR System. Use a new database name for Remedy SSO to prevent the table name conflict. | |
| Remedy Single Sign-On database user information | |||||
| Assign database user(s) | Create New User | Select one of the following options: -Create New User -Use Existing User | (HA environment) On a secondary node in an HA environment, select the Use Existing User option. | ||
| Database admin name | sa | sa | You need to provide these details if you selected to create a new database user. | ||
| Database admin password | bmcAdm!n | bmcAdm!n | |||
| Database user name | rsso_user | rsso_user | This user can access the details of application configuration and user sessions. You can provide the credentials of an existing database user that has permissions to create tables, or you can create a new user. | (HA environment) On a secondary node in an HA environment, use the credentials that you provided for the primary node. | |
| Database user password | userPa$1 | userPa$1 | |||
| Cookie domain | bmc.com | bmc.com | The domain value of the cookie must be the network domain of Remedy SSO or one of its parent domains. | ||
Sheet 2: Integrate with AR System
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Remedy AR System | Select to integrate with BMC Remedy AR System. | |
| Remedy Single Sign-On server information | |||
| Path to BMC Remedy AR System Home | C:\Program Files\BMC Software\ARSystem | Enter the directory path where BMC Remedy AR System application is installed. | |
| Remedy Single Sign-On server information | |||
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | It is used for internal back end communication between AR System agent and BMC Remedy Single Sign-On instance. Generally that communication happens behind firewall, so you ca use HTTP or HTTPS. The format of the URL must be the following: <Protocol>://<FQDN host name>:<Port>/<context path>. (High availability) In the HA mode, this URL must be the URL of a load balancer. | |
Sheet 3: Integrate with Mid Tier
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Remedy Mid Tier | Select to integrate with BMC Remedy Mid Tier. | |
| Remedy Mid Tier server information | |||
| Path to BMC Remedy Mid Tier Home | C:\Program Files\BMC Software\ARSystem\midtier | Enter the directory path where BMC Remedy Mid Tier application is deployed. | |
| Path to BMC Remedy Mid Tier Web server | C:\Program Files\Apache Software Foundation\Tomcat 7.0 | Enter the home directory of the Tomcat server on which Remedy AR System Server and Mid Tier is deployed. It is the Tomcat server that uses port 8080 for connection to AR System. | |
| Remedy Single Sign-On server information | |||
| Public BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | This URL is used to redirect unaothorized user request to BMC SSO instance for authentication. For the sake of security, the user facing URL should be HTTPS. The format of the URL must be the following: <Protocol>://<FQDN host name>:<Port>/<context path> (High availability) In the HA mode, it is the URL of the load balancer. | |
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-0103645.bmc.com:9080/rsso | This URL is used for internal back end communication between Mid Tier agent and BMC Remedy Single Sign-On instance. Generally that communication happens behind firewall, so you ca use HTTP or HTTPS. For the sake of performance, in a secured area you can use HTTP. The format of the URL must ne the following: <Protocol>://<FQDN host name>:<Port>/<context path> (High availability) In the HA mode, it is the URL of the load balancer. | |
Sheet 4: Integrate with BMC Analytics
| Field in installer | Example value for Windows | Your value | Description |
| Remedy Single Sign-On feature selection | |||
| BMC Remedy Single Sign-On installation | Integrate with BMC Analytics | Select to integrate with BMC Analytics | |
| BMC Analytics for Business Service Management information | |||
| Analytics webserver path | Specify the directory path to BMC Analytics home. | ||
| Analytics home | C:\Program Files\BMC Software\ | Specify the directory where BMC Analytics is installed. | |
| Remedy Single Sign-On server information | |||
| Service BMC Remedy Single Sign-On instance URL | https://clm-aus-010364.bmc.com:9080/rsso | Enter the URL for communication between Remedy SSO and agent. The URL must be a Fully Qualified Domain Name (FQDN). | |
| Public BMC Remedy Single Sign-On instance URL | https://clm-aus-010365.bmc.com:9080/rsso | Enter the URL to redirect unauthenticated user requests to Remedy SSO for authentication. | |
Related topics