Installation and Upgrade Guides › Policy Server Installation Guide › Installing Reports › Reporting Installation Checklists

Reporting Installation Checklists

Review the Report Server and report database checklists to help ensure the following:

• Your environment meets the minimum operating system and database requirements
• You complete the required prerequisite configuration

Report Server

• Be sure that the Report Server host system meets the minimum operating system requirements:
  • Windows
  • UNIX
• (Solaris) Install the required operating system patches to the Report Server host system.

  Note: For more information, see the Policy Server Release Notes.

• Be sure that the Report Server host meets the connectivity requirements.
• Be sure that the Report Server host name does not include any of the following characters:
  • An underscore (_)
  • A period (.)
  • A slash (/) (\)
• If you are reinstalling the Report Server, uninstall the current instance. The installation fails if you attempt to install over an existing instance.
• Windows installations:
  • Be sure that you have access to a user account that is a member of the local Administrators group. The user account that runs the installer must be a member of the local Administrators group.

    Important! Installing to a system where the default Windows security settings have been modified for the local Administrator group is not supported.

  • Be sure that the system to which you are installing is not a domain controller. Installing to a domain controller is not supported.
• UNIX installations:
  • Be sure that the Report Server host IP is configured properly in the /etc/hosts file to avoid an IP resolution problem.
  • Be sure that you have access to a root user account and a non–root user account. You require a root-user account to start the installation and a non–root user account to complete the installation. Be sure that the non–root user account:
    • Is the owner of a valid home directory.
    • Has write permissions to the home directory.
  • Be sure that the following commands and utilities are installed on the operating system and available on the PATH environment variable for the root user account:
    • /bin/sh
    • uname
    • awk
    • tar
    • stty
    • pwd
    • expr
    • chown
    • id
    • ulimt
    • read
    • hostname
    • grep
    • dirname
    • which
    • touch
    • sed
    • tail
    • gzip
  • Be sure that the PATH environment variable of the root–user account does not inlcude GNU or third–party replacements for core system command–line tools or an individually downloaded and compiled version of the tool.
  • Set at least one of the following variables to a valid utf8/UTF-8 locale:
    • LC_ALL

      Example: export LC_ALL=en_US.UTF-8

    • LANG

      Example: export LANG=en_US.UTF-8

    • LC_CTYPE

      Example: export LC_CTYPE=en_US.UTF-8

Report Database and Audit Database

• If you are not using the embedded version of MySQL:
  • Be sure that the database server host system has a fixed host name.
  • Be sure that you are using a supported database to function as the report database.
  • Be sure that a new, empty database is available.
  • Be sure that the database client and server are configured to use UTF8 character encoding. For more information about the required settings for a Unicode configuration, see your vendor-specific documentation.
• (SQL Server) If you are using SQL Server as a report database, an audit database, or both, complete the following items on the Report Server host system:
  • Be sure that a CA SiteMinder® supported SQL Server driver is installed on the Report Server host system.
  • Create a data source name (DSN) that identifies each database. The Report Server uses the DSN to communicate with each database.
• (Oracle) If you are using Oracle as a report database, an audit database, or both:
  • Do the following items on the Report Server host system:
    • Be sure that a supported Oracle Net client is installed.
    • Use an Oracle Net Service Name to identify each database in the tnsnames.ora file. The Report Sever uses the service name to communicate with each database.
    • Set the NLS_LANG variable to one of the following UTF–8 settings:

      – AMERICAN_AMERICA.WE8MSWIN1252

      – AMERICAN_AMERICA.AL32UTF8

    • Set the ORACLE_HOME variable to Oracle_Net_client.

      Oracle_Net_client

      Specifies the Oracle Net client installation path.

      Windows Example: C:\oracle\product\10.2.0\client

      UNIX Example: export ORACLE_HOME=/opt/oracle/product/10.2.0/client1

    • (Windows) Add the ORACLE_HOME variable to the system environment variables.

      Example: %Oracle_Home%\bin

    • (UNIX) Set the LD_LIBRARY_PATH variable to $ORACLE_HOME/lib32:$ORACLE_HOME/lib.

      Example: LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$ORACLE_HOME/lib:$LD_LIBRARY_PATH

    • (UNIX) Set the PATH variable to $ORACLE_HOME/bin:$PATH.

      Example: export PATH=$ORACLE_HOME/bin:$PATH

  • Do the following items on the database server host system: Set the NLS_LANG variable to one of the following UTF–8 settings:
    • AMERICAN_AMERICA.WE8MSWIN1252
    • AMERICAN_AMERICA.AL32UTF8

Report Database and Audit Database

• If you are not using the embedded version of MySQL:
  • Verify that the database server host system has a fixed host name.
  • Verify that you are using a supported database to function as the report database.
  • Verify that a new, empty database is available.
  • Verify that the database client and server are configured to use UTF-8 character encoding. For more information about the required settings for a Unicode configuration, see your vendor-specific documentation.
• (SQL Server) If you are using SQL Server as a report database, an audit database, or both, complete the following items on the Report Server host system:
  • Verify that a CA SiteMinder® supported SQL Server driver is installed on the Report Server host system.
  • Create a data source name (DSN) that identifies each database. The Report Server uses the DSN to communicate with each database.
  • Verify that the database is enabled for UTF-8 character encoding. For more information about the required settings for a Unicode configuration, see your SQL Server documentation.
• (Oracle) If you are using Oracle as a report database, an audit database, or both:
  • Do the following items on the Report Server host system:
    • Verify that a supported Oracle Net client is installed.
    • Verify that the database client and server are configured to use UTF-8 character encoding. For more information about the required settings for a Unicode configuration, see your vendor-specific documentation.
    • Use an Oracle Net Service Name to identify each database in the tnsnames.ora file. The Report Server uses the service name to communicate with each database.
    • Set the NLS_LANG variable to one of the following UTF–8 settings:

      – AMERICAN_AMERICA.WE8MSWIN1252

      – AMERICAN_AMERICA.AL32UTF8

    • Set the ORACLE_HOME variable to Oracle_Net_client.

      Oracle_Net_client

      Specifies the Oracle Net client installation path.

      Windows Example: C:\oracle\product\10.2.0\client

      UNIX Example: export ORACLE_HOME=/opt/oracle/product/10.2.0/client1

    • (Windows) Add the ORACLE_HOME variable to the system environment variables.

      Example: %Oracle_Home%\bin

    • (UNIX) Set the LD_LIBRARY_PATH variable to $ORACLE_HOME/lib32:$ORACLE_HOME/lib.

      Example: LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$ORACLE_HOME/lib:$LD_LIBRARY_PATH

    • (UNIX) Set the PATH variable to $ORACLE_HOME/bin:$PATH.

      Example: export PATH=$ORACLE_HOME/bin:$PATH

  • Do the following items on the database server host system: Set the NLS_LANG variable to one of the following UTF–8 settings:
    • AMERICAN_AMERICA.WE8MSWIN1252
    • AMERICAN_AMERICA.AL32UTF8