Installation and Upgrade Guides › Policy Server Installation Guide › Installing Reports › Installation Road Map › Gather Information for the Installer › UNIX

UNIX

Follow these steps:

1. Be sure that you have reviewed the installation checklists.
2. Be sure that you have gathered the required information for the installer.
3. Be sure to start the installation using a root user account.
4. Exit all applications that are running.
5. Open a Bourne shell and navigate to the installation media.
6. Enter the following command:

   ./installation_media -i console
   

   installation_media

   Specifies the Report Server installation executable.

   Note: For a list of installation media names, see the Policy Server Release Notes.

   The CA Business Intelligence installer starts and prompts you for a locale.

7. Type the value for English and press Enter.

   The installer introduction appears.

8. Press Enter.

   The CA license agreement appears.

9. Complete the following steps:
   1. Press Enter to advance the license agreement.
   2. Type y to accept the license agreement.
   3. Press Enter.

   The installer prompts you for non–root user credentials.

10. Type the user name and group name and press Enter.

    The installer prompts you to specify the path to the CA Shared Components directory.

11. Leave the default value and press Enter.

    The installer prompts you to install CA sample templates.

12. Type N and press Enter.

    Note: CA sample templates are not related to the SiteMinder reporting templates. The SiteMinder Report Server Configuration wizard installs the required reporting templates. You run the wizard after installing the Report Server.

    The installer prompts you to save a response file for a silent installation.

13. Type Y and press Enter.

    An installation summary appears.

14. Review the summary and press Enter.

    The installer installs the components. The SAP BusinessObjects Enterprise installer prompts you to select an installation language.

15. Select English and press Enter.

    The SAP BusinessObjects Enterprise license agreement appears.

16. Press y to accept the license agreement.

    The installer prompts you enter the Report Server installation directory.

17. Press Tab to auto–complete the default setting and press Enter.

    The installer prompts you to select language packs. English is selected by default.

18. Leave the default and press Enter.

    The installer prompts you for an installation type.

19. Select User – Regular SAP BusinessObjects Enterprise installation and press Enter.

    The installer prompts you for an installation type.

20. Select New and press Enter.

    Note: Do not clear the Enable servers after installation option.

    The installer prompts you for the Content Management Server port and the password for the SAP BusinessObjects Enterprise administrator account.

21. Complete the following steps:
    1. Specify the port to which the Content Management Server must connect and listen for requests.
    2. Specify a password for the default SAP BusinessObjects Enterprise administrator.
    3. Press Enter.

    The installer prompts you to select the type of database that is to function as the report (CMS) database.

22. Complete one of the following steps:
    • (Recommended) To install the embedded version of MySQL, select Install MySQL and press Enter.
    • To configure an existing Oracle database, select Use an existing database server and press Enter.

    Important! The Report Server is a CA common component that CA products can share. As such, the installer lets you configure the report database to database types and versions that other products support, but SiteMinder does not. For a list of supported database types and versions, see the SiteMinder r12.0 SP3 Platform Support Matrix.

    The installer prompts for additional report database information.

23. Complete one of the following steps:
    • (MySQL) Enter the required values for the root user account and the report database administrator credentials.
    • (Oracle) Complete the steps:
      1. Select Oracle and press Enter.

         The installer prompts for database information.

      2. Type the service name and administrator credentials.
24. Press Enter.
    • If you are installing the embedded version of MySQL, the installer prompts you for Auditing Database information.
    • If you are configuring Oracle, the installer prompts you to install the Auditing Database.

      The Auditing Database is not related to SiteMinder audit–based reports. The Content Management Server Auditing Database is used to audit activities specific to the Report Server and is not used for SiteMinder. A SiteMinder audit database is required to run audit–based reports.

25. Complete one of the steps:
    • (MySQL) Accept the defaults and press Enter.
    • (Oracle) Complete the following steps:
      1. Select the Do not install Auditing Database option.
      2. Press Enter.

         The installer prompts you to reinitialize the database.

      3. Select Yes and press Enter.

    The installer prompts you for a Service Intelligence Agent node name and port.

26. Type a node name and port and press Enter.

    The installer prompts you to select a web application server.

27. Select the Install Tomcat deploy web applications option.

    Note: SiteMinder only supports the embedded version of Apache Tomcat.

    The installer prompts you for Apache Tomcat ports.

28. Type the required Apache Tomcat port information and press Enter.

    The installer displays the path of the installation directory.

29. Press Enter to start the installation.

    The installer displays the installation progress and confirms when the installation is complete.

30. Press Enter to exit the installer.

More information:

Installation Media Names

Troubleshoot the Report Server Installation

Use the following files to troubleshoot the Report Server installation:

• CA_Business_Intelligence_InstallLog.log

  We recommend opening this log first to view reported errors.

• ca-install.log

  We recommend scrolling to the bottom of this file to view reported errors. Search for “BIEK_GetExitCode” to verify the returned value of the “BIEK_GetExitCode” function. If the returned value is not 0, then there is an installation error. Search for the following keywords to determine the cause of the error:

  • Error
  • Warning
  • CMS
  • InfoStore

The log files are located in a temporary location during the installation. The TEMP environment property on the system determines the temporary location. If the installation fails, you can locate the log file in this temporary location. After a successful installation, the log files are located at the top level of the Report Server installation directory.

How to Install the Report Templates

Complete the following procedures to install the report templates:

1. Gather information for the installer.
2. Install the report templates.
3. Restart the Report Server.
4. Increase the Job Server service timeout value.

Gather Information for the Installer

The Report Server Configuration Wizard requires the following information:

• BusinessObjects administrator password—Identify the password for the default BusinessObjects administrator account. The Report Server installer creates a default administrative account during installation. A password for this account was required to complete the installation. The Report Server Configuration Wizard requires the password to use the default administrative account to install the report templates.
• SiteMinder audit database type—Identify the type of database that is to function as a SiteMinder audit database. A separate SiteMinder audit database is required to run audit-based reports. The Report Server Configuration Wizard requires the database type to configure the Report Server to use a set of report templates based on the audit database type.

  Note: You do not have to configure a SiteMinder audit database before running the Report Server Configuration Wizard.

A worksheet is provided to help you gather and record required information before installing the report templates.

More information:

Report Server Configuration Worksheet

Install the Report Templates

You install the SiteMinder report templates with the Report Server Configuration Wizard. The following sections detail how to run the Report Server Configuration Wizard on Windows and UNIX.

Before You Install

Consider the following items before you install the report templates:

• You run the Report Server Configuration Wizard using the installation media on the Technical Support site.

  Note: For a list of installation media names, see the Policy Server Release Notes.

  Important! (UNIX) The installation media requires executable permissions. Run the following command to add the permission:

  chmod +x installation_media
  

  installation_media

  Specifies the name of the Report Server Configuration Wizard installation executable.

• (UNIX) If you execute the Report Server Configuration Wizard across different subnets, it can crash. Install the report templates directly on the Report Server host system.

More information:

Locate the Installation Media

Installation Media Names

Windows

To install the report templates on Windows

1. Be sure that you have gathered the required information for the installer.
2. Exit all applications that are running.
3. Double–click installation_media.

   installation_media

   Specifies the name of the Report Server Configuration Wizard installation executable.

   The installer starts.

   Note: For a list of installation media names, see the Policy Server Release Notes.

4. For each prompt, use your completed Report Server configuration worksheet to enter the required values.
5. Review the installation settings and click Install.

   The report templates are installed.

6. Restart the Report Server.

   The Report Server is configured to use the SiteMinder report templates.

More information:

Locate the Installation Media

Installation Media Names

Report Server Configuration Worksheet

Restart the Report Server

UNIX GUI

To install the report templates using a UNIX GUI

1. Be sure that you have gathered the required information for the installer.
2. Exit all applications that are running.
3. Open a shell and navigate the installation media.
4. Enter the following command:

   ./installation_media
   

   installation_media

   Specifies the name of the Report Server Configuration Wizard installation executable.

   The installer starts.

   Note: For a list of installation media names, see the Policy Server Release Notes.

5. For each prompt, use your completed Report Server configuration worksheet to enter the required values.

   Note: Oracle is the only supported audit database for a Solaris Report Server. If you installed the Report Server to Solaris, you are not prompted for an audit database type. The Report Server Configuration Wizard automatically installs Oracle-specific report templates.

6. Review the installation settings and click Install.

   The report templates are installed.

7. Restart the Report Server.

   The Report Server is configured to use the SiteMinder report templates.

More information:

Locate the Installation Media

Installation Media Names

Report Server Configuration Worksheet

Restart the Report Server

UNIX Console

To install the report templates using a UNIX console

1. Be sure that you have gathered the required information for the installer.
2. Exit all applications that are running.
3. Open a shell and navigate to the installation media.
4. Enter the following command:

   ./installation_media -i console
   

   installation_media

   Specifies the name of the Report Server Configuration Wizard installation executable.

   -i console

   Specifies that installation start in a UNIX console.

   The installer starts.

   Note: For a list of installation media names, see the Policy Server Release Notes.

5. For each prompt, use your completed Report Server configuration worksheet to enter the required values.

   Note: Oracle is the only supported audit database for a Solaris Report Server. If you installed the Report Server to Solaris, you are not prompted for an audit database type. The Report Server Configuration Wizard automatically installs Oracle-specific report templates.

6. Review the installation settings and press Enter.

   The report templates are installed.

7. Restart the Report Server.

   The Report Server is configured to use the SiteMinder report templates.

More information:

Locate the Installation Media

Installation Media Names

Report Server Configuration Worksheet

Restart the Report Server

Increase the Job Server Service Timeout Value

Some of the Report Server services have a default timeout of 10 minutes. The Report Server can take longer than 10 minutes to generate large analysis reports.

Increase the timeout value of the Crystal Reports Job Server service to be sure that large analysis reports are successfully generated.

Increase the Timeout Value on Windows

Follow these steps:

1. Click Start, Programs, BusinessObjects XI Release 3.1, BusinessObjects Enterprise, Central Configuration Manager.

   The Central Configuration Manager console appears.

2. Right-click Crystal Reports Job Server and select Stop.

   The Crystal Reports Job Server service stops.

3. Right-click Crystal Reports Job Server and select Properties.

   The Crystal Reports Job Server Properties dialog appears.

4. From the Properties tab, append the following entry to the end of the string in the Command field:

   -requesttimeout 6000000
   

   Note: The timeout value is measured in milliseconds. Specifying 6000000 increases the timeout value to one (1) hour.

5. Click OK.

   The Central Configuration Manager appears.

6. Right-click Crystal Reports Job Server and select Start.

   The Crystal Reports Job Server service starts.

7. Exit the Central Configuration Manager.

   The timeout value for the Crystal Reports Job Server service is set to one (1) hour.

Increase the Timeout Value on UNIX

Follow these steps:

1. Navigate to report_server_home/CommonReporting3/bobje.

   report_server_home

   Specifies the Report Server installation path.

2. Open the ccm.config file, and append the following entry to the end of the value for reportjobserverLAUNCH key:

   -requesttimeout 6000000
   

   Note: The timeout value is measured in milliseconds. Specifying 6000000 increases the timeout value to one (1) hour.

3. Save and close the ccm.config file.

   The timeout value for the Crystal Reports Job Server service is set to one (1) hour.

How to Register the Report Server

Registering the Report Server requires access to the Policy Server host system, the Report Server host system, and the Administrative UI host system. The registration process:

• Establishes a trusted relationship between the Report Server and the Policy Server.
• Establishes a trusted relationship between the Report Server and the Administrative UI.

Complete the following steps to register the Report Server:

1. Create the client name and passphrase.
2. Gather the registration information.
3. Register the Report Server with a Policy Server.
4. Restart the Report Server.
5. Configure the connection to the Administrative UI.

Create a Client Name and Passphrase

You run the XPSRegClient utility to create a client name and passphrase. A client name and passphrase are:

• Values that the Policy Server uses to identify the Report Server you are registering
• Values that you use with the XPSRegClient tool to register the Report Server with the Policy Server

To run the registration tool

1. Open a command–line window from the Policy Server host system.
2. Navigate to siteminder_home/bin.

   siteminder_home

   Specifies the Policy Server installation path.

3. Run the following command:

   XPSRegClient client_name[:passphrase] -report -t timeout -r retries
   -c comment -cp -l log_path -e error_path -vT -vI -vW -vE -vF
   

   client_name

   Identifies the name of Report Server you are registering.

   Limit: The value must be unique. For example, if you have previously used reportserver1, enter reportserver2.

   Note: Record this value. This value is required to complete registration process from the Report Server host system.

   passphrase

   Specifies the password required to complete the Report Server registration.

   Limits: The passphrase

   • Must contain at least six (6) characters.
   • The passphrase cannot include an ampersand (&) or an asterisk (*).
   • If the passphrase contains a space, it must be enclosed in quotation marks.

   If you do not specify the passphrase in this step, XPSRegClient prompts you to enter and confirm it.

   Note: Record this value. This value is required to complete registration process from the Report Server host system.

   -report

   Specifies that a Report Server is being registered.

   -t timeout

   (Optional) Specifies how long you have to complete the registration process from the Report Server host system. The Policy Server denies the registration request when the timeout value is reached.

   Unit of measurement: minutes

   Default: 240 (4 hours)

   Minimum Limit: 1

   Maximum Limit: 1440 (one day)

   -r retries

   (Optional) Specifies how many failed attempts are allowed when you complete the registration process from the Report Server host system. A failed attempt can result from submitting an incorrect passphrase to the Policy Server during the registration.

   Default: 1

   Maximum Limit: 5

   -c comment

   (Optional) Inserts the specified comments into the registration log file for informational purposes.

   Note: Surround comments with quotes.

   -cp

   (Optional) Specifies that registration log file can contain multiple lines of comments. The registration tool prompts for multiple lines of comments and inserts the specified comments into the registration log file for informational purposes.

   Note: Surround comment with quotes.

   -l log path

   (Optional) Specifies where the registration log file must be exported.

   Default: siteminder_home\log, where siteminder_home is where the Policy Server is installed.

   -e error path

   (Optional) Sends exceptions to the specified path.

   Default: stderr

   -vT

   (Optional) Sets the verbosity level to TRACE.

   -vI

   (Optional) Sets the verbosity level to INFO.

   -vW

   (Optional) Sets the verbosity level to WARNING.

   -vE

   (Optional) Sets the verbosity level to ERROR.

   -vF

   (Optional) Sets the verbosity level to FATAL.

   The utility lists the name of the registration log file. If you did not provide a passphrase, the utility prompts for one.

4. Press Enter.

   The registration tool creates the client name and passphrase.

You can now register the Report Server with the Policy Server. You complete the registration process from the Report Server host system.

Gather Registration Information

Completing the registration process between the Report Server and the Policy Server requires specific information. Gather the following information before running the XPSRegClient utility from the Report Server host system.

• Client name—The client name you specified using the XPSRegClient tool.
• Passphrase—The passphrase you specified using the XPSRegClient tool.
• Policy Server host—The IP address or name of the Policy Server host system.

More information:

Report Server Registration Worksheet

Register the Report Server with the Policy Server

You register the Report Server with the Policy Server to create a trusted relationship between both components. You configure the connection from the Report Server host system using the Report Server registration tool.

Follow these steps:

1. From the Report Server host system, open a command–line window and navigate to report_server_home\external\scripts.

   report_server_home

   Specifies the Report Server installation location.

   Default: (Windows) C:\Program Files\CA\SC\CommonReporting3

   Default: (UNIX) /opt/CA/SharedComponents/CommonReporting3

2. Run one of the following commands:
   • (Windows)

     regreportserver.bat -pshost host_name -client client_name -passphrase passphrase -psport portnum -fipsmode 0|1
     

     Important! Before running a SiteMinder utility or executable on Windows Server 2008, open the command line window with administrator permissions. Open the command line window this way, even if your account has administrator privileges.

   • (UNIX)

     regreportserver.sh -pshost host_name -client client_name -passphrase passphrase -psport portnum -fipsmode 0|1
     

   -pshost host name

   Specifies the IP address or name of the Policy Server host system to which you are registering the Report Server.

   -client client name

   Specifies the client name. The client name identifies the Report Server instance that you are registering.

   Note: This value must match the client name that you specified using the XPSRegClient utility when you registered the Report Server on the Policy Server host system.

   Example: If you specified "reportserver1" when using the XPSRegClient utility, enter "reportserver1".

   -passphrase passphrase

   Specifies the passphrase that is paired with the client name. The client name identifies the Report Server instance that you are registering.

   Note: This value must match the passphrase that you specified using the XPSRegClient utility when you registered the Report Server on the Policy Server host system.

   Example: If you specified SiteMinder when using the XPSRegClient utility, enter SiteMinder.

   -psport portnum

   (optional) Specifies the port on which the Policy Server is listening for the registration request.

   fipsmode

   (optional) Specifies how the communication between the Report Server and the Policy Server is encrypted.

   Default: 0

   • Zero (0) specifies FIPS–compatibility mode.
   • One (1) specifies FIPS–only mode.

3. Press Enter.

   You receive a message stating that the registration is successful.

Restart the Report Server

(Windows) Follows these steps:

1. Click Start, Programs, BusinessObjects XI 3.1, BusinessObjects Enterprise, Central Configuration Manager.

   The Central Configuration Manager console appears.

2. Stop the Apache Tomcat and Server Intelligence Agent Services.

   The Report Server stops.

3. Start the Apache Tomcat and Server Intelligence Agent Services.

   The Report Server is restarted.

(UNIX) Follow these steps:

1. Log in to the system as the non–root user that installed the Report Server.
2. Be sure that at least one of the following environment variables is set to a valid utf8/UTF-8 locale:
   • LC_ALL
   • LANG
   • LC_CTYPE
3. Navigate to report_server_home/CommonReporting3/external/scripts and run the following command:

   ../setupenv.sh
   

   report_server_home

   Specifies the Report Server installation path.

4. Be sure that:
   • The IAM_RPTSRV_HOME variable is set to report_server_home/CommonReporting3.

     report_server_home

     Specifies the Report Server installation path.

   • (Oracle report database only) The LD_LIBRARY_PATH variable is set to $ORACLE_HOME/lib32:$ORACLE_HOME/lib:$ETPKIHOME/lib:$LD_LIBRARY_PATH

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

   • The ETPKIHOME variable is set to report_server_home/CommonReporting3.

     report_server_home

     Specifies the Report Server installation path.

5. Navigate to report_server_home/CommonReporting3/bobje and run the following command:

   ./stopservers
   

   report_server_home

   Specifies the Report Server installation path.

6. Run the following command:

   ./tomcatshutdown.sh
   

   The Report Server stops.

7. Run the following command:

   ./startservers
   

8. Run the following command:

   ./tomcatstartup.sh
   

   The Report Server is restarted.

Configure the Connection to the Administrative UI

You configure the Report Server and Administrative UI connection to configure a trusted relationship between both components. You configure the connection from the Administrative UI.

Note: The Administrative UI can have a trusted relationship with one or more Policy Servers. However, each trusted relationship only allows one Report Server connection. If you must connect to a new Report Server, either delete the current Report Server connection or connect to another Policy Server to configure the connection.

To configure the connection to the Administrative UI

1. Log into the Administrative UI.
2. Click Administration, Admin UI.
3. Click Report Connections, Create Report Server Connection.

   The Create Report Server Connection pane appears.

   Note: Click Help for descriptions of settings and controls, including their respective requirements and limits.

4. Type a connection name in the Connection Name field.
5. Type the Report Server host system name or IP address in the Report Server Host field.
6. Enter the Apache Tomcat connection port in the Tomcat Port field.

   Note: This value is the web server port you entered when installing the Report Server.

7. Enter the administrator password in the respective fields.

   Note: This value is the password you entered for the default BusinessObjects administrator account when installing the Report Server.

8. Click Submit.

   The connection between the Report Server and the Administrative UI is configured.

You have completed installing and registering the Report Server. You can now run policy analysis reports.

Note: Creating and managing audit reports requires a separate audit database.

How to Configure an Audit Database

A SiteMinder audit database is required to run SiteMinder audit–based reports.

Note: Although you can write audit information to a text file, you must store your audit information in a supported ODBC database to create and manage audit-based reports. For a list of the supported versions, see the SiteMinder r12.0 SP3 Platform Support Matrix.

Complete the following steps to configure an audit database:

1. (Optional) If you have not already done so, configure a SiteMinder audit database.

   Important! If you are configuring the audit database in Oracle, be sure that the user account you supply does not have the DB role. If the user account has the DB role, audit–based reports do not return correct results.

2. Register the audit database with the Administrative UI.
3. Configure connectivity between the audit database and the Report Server.

More information:

Locate the Platform Support Matrix

How to Store Audit Logs in Oracle

How to Store Audit Logs in SQL Server