Chatee ahora con Soporte
Chat con el soporte

Quest Knowledge Portal 2.11 - Install Guide

Minimal Rights and Permissions

  1. To install Knowledge Portal, the user account under which the setup is launched must have the following permissions:
    • Must be a member of the local Administrators group on the computer where the setup is run.
    • Must have the System Administrator role for the Microsoft SQL Server Reporting Services.
  2. To install the Report Packs, the user account under which the Report Pack setup is launched must have System Administrator role for the SSRS.
  3. To start the Knowledge Portal, a user must have the Read permission for %WinDir%.

Note: Generally, for the account that will be used to access the Knowledge Portal, Data Source properties are used to assign the required credentials (see the Configuration topic for details). This account must belong to the same domain where SSRS hosting the Knowledge Portal is installed, otherwise membership in the Authenticated Users group (for SSRS domain) is required.

  1. To view reports and data sources, the user account must have:
    • View Folders and View Reports permissions on the Home folder and on the necessary subfolders (where the user’s reports are stored) of the \QKP folder in SQL Reporting Services.
    • View Data Sources permission on the \QKP\SharedDatasources folder in SQL Reporting Services.
    • View Resources permission on \QKP\<Product>\SharedResources folder in SQL Reporting Services. (for the <Product> folder, substitute the folder of the Quest product Report Pack you use; this can be, for example, Reporter, or InTrust), and on the \QKP\SharedResources folder.
  2. To create a report with Report Builder, a user will need the Execute Report Definition permission on the site level. To save a newly created report in the .RDL file on SSRS, Manage Reports permission on target folder with reports is also required.
  3. To modify a report (for example, customize report view, or edit report in Report Builder or Microsoft Visual Studio), a user will need Manage Reports permission on this report (stored in the corresponding folder with reports under \QKP).
  4. To work with models and model-based reports, View Models and View Resources permission on the \QKP\SharedDatasources folder in SQL Reporting Services is required.

Note: If you have no need for such granular rights assignment, the user account can be assigned the following SSRS roles:

  • Content Manager role for the QKP\SharedDatasources folder and for the folder where the report is located (under the \QKP folder) in SQL Reporting Services.
  • Browser role for the Home folder in SQL Reporting Services. However, some additional permissions are required for users who need to work with models and model-based reports (view reports and change their settings) but who have only the Browser role for these reports - Manage Models permission on the \QKP\SharedDatasources folder in SQL Reporting Services.
  • The Publisher and Content Manager roles can provide the Manage Reports permission.

Rights and roles are assigned as explained in the Configuring Access Rights topic.

Checking for Reporting Services on SQL Server

To install Knowledge Portal and the Report Packs, you have to check whether the Reporting Services is installed and configured on your SQL Server, as explained below.

To check whether Reporting Services is running locally

  1. Go to Programs |Microsoft SQL Server | Configuration Tools and launch the Reporting Services Configuration utility.
  2. The utility displays the SSRS service status and checks whether all required configuration data is specified. It also displays SSRS virtual directories (Report Server virtual directory and Report Manager virtual directory).
  3. If these virtual directories are other than the default, you will have to specify them during the Knowledge Portal setup.

To check whether Reporting Services is running remotely

  1. In the Internet Explorer address bar, type:
  2. Check whether the SSRS Report Manager window is displayed. If not, you need to investigate and resolve the problem locally. The cause may be one of the following:
    • SSRS service is not running
    • SSRS Report Manager uses a different virtual directory
    • Your account does not have enough access rights.

If you are already using SQL Server, Reporting Services is a part of your SQL Server deployment. Otherwise, see the New Installation (Reporting Services in Native Mode) MSDN article for details.

Installing Knowledge Portal

Caution: Knowledge Portal can be installed either on the computer where SSRS is running or on a dedicated computer.

To install Knowledge Portal

  1. Run the Knowledge Portal Setup.
  2. Specify your full name and organization.
  3. Specify the installation folder and make sure to select the Knowledge Portal.
  4. Select the country where you are performing installation. This specifies whether or not you are participating in the Quest Software Improvement Program by default. Depending on your choice, you may be asked whether you want to opt in; for some countries, participation will be enabled automatically.

Note: The Quest Software Improvement Program involves Quest automatically receiving anonymous usage statistics from the Quest software you install. No personal identifying data (such as account names) is included in this feedback. The purpose is to determine which features are most popular and find out how their use can be streamlined.

The following information is transmitted:

  • Hardware configuration
  • Which product features are used
  • External IP addresses

Participation in the program is voluntary. For details about opting into and out of the initiative, see the Installing and Configuring InTrust Components topic in the InTrust Deployment Guide.

  1. Specify the site and virtual directory where to install the Knowledge Portal.
  2. Next, select the report server that you want to associate Knowledge Portal with. Setup automatically selects one of the available report servers. If the automatic choice is not suitable for you, select another report server by clicking the button next to the Report Server Web Service URL box.

If setup fails to detect reporting servers that should be available, try editing your Windows Firewall configuration to allow WMI connections. For that, do one of the following:

  • In the Group Policy Object Editor MMC snap-in, set Local Computer Policy | Computer Configuration | Administrative Templates | Network | Network Connections | Windows Firewall | Domain Profile | Windows Firewall:Allow inbound remote administration exception to Allow.
  • In the Windows Firewall Settings dialog box, go to the Exceptions tab, and enable the exception for Windows Management Instrumentation (WMI) in the list of options.
  1. Specify the default user name and password that will be used for:
    • Connecting to the SQL Server hosting the product databases
    • Searching for accounts in Active Directory when granting access rights to report users

Note: This user account should be granted the Log on as a service right on Windows 2003-based computers where Knowledge Portal is installed.

  1. Click Next and wait for the installation to complete.

Installing Report Packs

Report Packs can be installed on the same computer with the Knowledge Portal, or on the different computer.

To install a Report Pack

  1. Run the Report Pack setup.
  2. Next, specify the URL of report server, for example:
  3. To get data for reports provided in the Report Pack, you need to associate the Data Sources (Reporting Services entities) with the corresponding product databases. This should be done on the Configure Data Sources step. Click Configure to provide the settings required for association.

Note: You can skip data source configuration in the setup; then you will have to configure your data sources later, as described in the Configuring Data Sources topic.

  1. In the Data Source Configuration dialog, select the data source to configure and click Modify. The Data Source Configuration Wizard is started to help you with initial configuration of the data source.
  2. On the Specify SQL Server step, enter the name of SQL Server where the product database resides, or click Browse to select server from the list of available SQL Servers. Specify authentication method to use for connection.

    Connection settings will be applied to this data source and used when getting data for the reports and also when removing the temporary tables from the database. (By default, a special Temporary Tables Clean-up job is configured during the setup to periodically clean up the databases from temporary tables that are created during report generation. For details, refer to the Knowledge Portal User Guide.)

Note: To schedule this job, you should select SQL Server Authentication or Windows Authentication. If Integrated Windows Authentication is used, the clean-up job cannot be scheduled.

  1. On the Specify Database step, you can either select a database from the list, or enter a name for a new database to create.
  2. Click Next and wait for connection test to complete. Click OK to finish data source configuration.

Note: For Temporary Tables Clean-up job schedule to be applied, make sure SQL Server Agent is running. If not, start the Agent, then connect to the Knowledge Portal, select the necessary data source and use the Manage Data Source menu command to schedule the clean-up.

To install another Report Pack, follow the same steps. On steps 5–8, select the corresponding data source and associate it with the database you need.

Documentos relacionados