RTC Launcher Admin Installation

To install the RTC Launcher Admin, follow the steps:

Run the setup file
Click the "Next" button, to proceed to the next setup page
On the opened "Destination Folder" screen, choose the folder to that the RTC Launcher Admin will be installed
Click the "Next" button, to proceed to the next setup page
On the opened "Configuration Settings" screen, fill the settings according to the table below
Click the "Next" button, to proceed to the next setup page
Click the "Install" button
Wait until installation is completed
Click the "Finish" button on the last setup page, to finish the installation

The filled RTC Launcher Admin installation wizard

The configuration settings:

Field Name	Description
Main database SQL Server	The FQDN of the SQL Server for RTC Launcher database. Example: sql.luware.com
Main database SQL Instance	The SQL Instance of the SQL Server for RTC Launcher database. Example: RTC
Main database Database	The RTC Launcher database name. Example: RTC_DB The integrated security is used by default. It is possible to change it in the config file.
Reporting database SQL Server	The FQDN of the SQL Server for RTC Launcher Reporting database. Example: sql.luware.com
Reporting database SQL Instance	The SQL Instance of the SQL Server for RTC Launcher Reporting database. Example: RTC
Reporting database Database	The RTC Launcher Reporting database name. Example: RTC_DB The integrated security is used by default. It is possible to change this in the config file.
Logging database SQL Server	The FQDN of the SQL Server for RTC Launcher Logging database. Example: sql.luware.com
Reporting database SQL Instance	The SQL Instance of the SQL Server for RTC Launcher Logging database. Example: RTC
Reporting database Database	The RTC Launcher database Logging name. Example: RTC_DB The integrated security is used by default. It is possible to change it in the config file.
Admin Host Name	The host name associated with the RTC Launcher Administration Site. If DNS Name was mapped to the current server with default 80 port, then FQDN without Port Number can be set to the field. Example: rtclauncheradmin.luware.com Otherwise, FQDN or IP address of server (where service has been installed) with Port Number is set to the field. Example for http: rtclauncher01.dev.local:90 Example for https: rtclauncher01.dev.local:445 After the installation the setting is stored in IIS
Admin Port Number	The TCP port number for the RTC Launcher Admin Web application in IIS. Example for http: 90 Example for https: 445 After the installation the setting is stored in IIS
Client Host Name with http(s)	URL which is pointing to RTC Launcher Client. Example: http://rtclauncher01.dev.local
Default API Host Name with http(s)	URL(s) which is pointing to RTC Launcher API Service. This URL is needed to synchronize Lync / SfB contact details from provided SIP Addresses and clear cached values. The synchronization is initiated server side from IIS where RTCLauncher Admin is installed to API URL (RTCLauncher API synchronize will over Lync / SfB Server). Please ensure that the API URL(s) is reachable from IIS where RTCLauncher Admin is installed. For Active/Passive scenario multiple API URLs can be specified, devided by comma. Examples: Single API URL: http://rtclauncher01.dev.local:9000 https://rtclauncherapi.luware.com Multiple API URLs: https://rtclauncherapi.luware.com , http://rtclauncher01.dev.local:9000 By default after the installation the setting is stored in <clientSection _BaseApiAddress> of the file: `C:\Program Files\Luware AG\RTCLauncher-Admin\Web.config` CODE
Protocol	Choose between HTTP and HTTPS protocols. After the installation the setting is stored in IIS
Certificate Hash	The hash of server certificate. The field appears only if https protocol is chosen. More details can be found in the Certificate Hash section. After the installation the setting is stored in IIS

By default after the installation the setting is stored in <connectionStrings> of the file:

C:\Program Files\Luware AG\RTCLauncher-Admin\Web.config

CODE