Installing ReportManager

The ReportManager application can be installed on any computer on the network that has network access to the SQL Server. If ReportManager is being installed on a computer that has already had the Common Files installer run on it (such as the SQL Server or Pool Service computer) you can skip the step of installing Common Files application. You need administrator privileges on the computer where ReportManager is installed. If you have write privileges to the Siriusware\Install directory, the installer updates the value of the SiriuswareSQLServer setting in the SiteDefaults.INI file.

• Creates and assigns a value to the LOCATION system environment variable. The value of the LOCATION environment variable must be unique for each computer where it is installed.

Note: On Windows Server 2008 (32- and 64-bit), you need to turn on DEP, and then exclude ReportManager after it is installed. See Installing with an “execution protection” capable processor for how this is done.

1. Ensure that Common Files application is already installed.

2. If you are installing ReportManager on the server computer where Server Files application is already installed, you can run the Install_Siriusware_ReportManagerManager_xxxx.msi installer directly from the \Siriusware\Install directory. If you are accessing the \Siriusware\Install directory over the network, you can either run the installer over the network or copy the installer to the desktop and run it from there. Siriusware Inc. recommends that you run the installer over the network. If you later modify the installation, Windows looks for the installer in the location from which it was originally run. It might inadvertently get deleted from the desktop.

3. You are presented with the following dialog. Click Next.

4. You are presented with the following dialog. You can add the training mode ReportManager, but you are required to install a training database before you can use it (see Installing a training database). You can select either This feature will be installed on local hard drive or This Feature, and all subfeatures will be installed on local hard drive. The two options are equivalent. Click Next.

5. You are presented with the following dialog. Enter the location name for this computer. This dialog causes the LOCATION system environment variable to be created and this value assigned to it. The value of the LOCATION environment variable must be unique for each computer where it is installed. If there is already a LOCATION environment variable on this computer, the value is changed to whatever you type here. In the screen capture below, the value office is pre-populated in the field because it was the value specified during the SysManager installation (the field will only prepopulate with the value specified during SysManager installation if SysManager was installed on the same machine). The value must be one to six characters in length.

6. You are presented with the following dialog. Enter the name or IP address of the SQL Server that contains the Siriusware database. If the computer on which you are installing ReportManager is that computer, choose or type (local) or the actual name of the SQL Server computer (the latter is recommended). This information is used to create the ODBC connection. In this example, the field is already pre-populated with (local) because that value was specified when the Pool Service installer was already run on this computer earlier. If you change this value and you have write privileges to the Siriusware\Install directory, the installer updates the value of the SiriuswareSQLServer setting in the SiteDefaults.INI file.