Setting up the reporting server

The reporting server is the server on which you install the BusinessObjects Business Intelligence (BI) platform. You can review the deployment options on Deployment use cases.

Reporting server requirements

Note

The recommended database is Sybase SQL Anywhere. This is the default database for fresh installation of BusinessObjects BI 4.1 SP6, 4.1 SP9 and 4.2.

Ensure that your reporting server has enough space and meets the following requirements:

  • BusinessObjects BI must be installed before installing BMC Decision Support – Network Automation.
    • The BusinessObjects BI installation requires a 64-bit computer.
    • You can use an existing BusinessObjects BI installation or perform a new installation.
    • You must use the same instance of BusinessObjects BI for all BMC Decision Support – BladeLogic Automation Suite products installed in your environment.
    • Download and install BusinessObjects BI depending upon the BMC Decision Support – Network Automation version you are using as follows:

      BMC Decision Support – Network Automation versionBusinessObjects BI installation overview 
      8.9.02.005
      8.9.02.004

      You need to install or upgrade to version 4.2 SP5 and then you can upgrade to 4.2 SP5 Patch 5.

      (Fresh installation of version 4.2 SP5) To start fresh installation of version 4.2 SP5, open the BO_42_SP5_64_bit_Server_WIN.zip file using Windows Explorer and double-click the setup.exe file located in the BusinessObjectsServer_win folder. 

      (Upgrade to version 4.2 SP5) To start upgrading to version 4.2 SP5 from 4.1 SP9, double-click BO_42_SP5_64_bit_Server_Update_WIN.zip.

      To start upgrading to version 4.2 SP5 Patch 5, double click BO_42_SP5_P5_64_bit_Server_Update_WIN.zip.

      For detailed upgrade instructions, refer to the Business Intelligence Platform Upgrade Guide at PDFs.


      8.9.02.003
      8.9.02.002
      8.9.02.001
      • (Fresh installation) To start fresh installation of version 4.2 SP5, open the BO_42_SP5_64_bit_Server_WIN.zip file using Windows Explorer and double-click the setup.exe file located in the BusinessObjectsServer_win folder. 
        For detailed installation instructions, refer to the Business Intelligence Platform Installation Guide (Windows) at PDFs
      • (Upgrade) To start upgrading to version 4.2 SP5 from 4.1 SP9, double-click BO_42_SP5_64_bit_Server_Update_WIN.zip.
        For detailed upgrade instructions, refer to the Business Intelligence Platform Upgrade Guide at PDFs.

      8.9.02
      8.9.01
      • (Fresh installation) To start fresh installation of version 4.1 SP9, open the BO_41_SP9_64_bit_Server_WIN.zip file using Windows Explorer and double-click the setup.exe file located in the BusinessObjectsServer_win folder. 
        For detailed installation instructions, refer to the Business Intelligence Platform Installation Guide (Windows) at PDFs
      • (Upgrade) To start upgrading to version 4.1 SP9 from 4.1 SP6, double-click BO_41_SP9_64_bit_Server_Update_WIN.exe.
        For detailed upgrade instructions, refer to the Business Intelligence Platform Upgrade Guide at PDFs.
       
      8.9.00
      • (Fresh installation) To start fresh installation of version 4.1 SP6, open the BO_41_SP6_64_bit_Server_WIN.zip file using Windows Explorer and double-click the setup.exe file located in the BusinessObjectsServer_win folder. 
        For detailed installation instructions, refer to the Business Intelligence Platform Installation Guide (Windows) at PDFs
      • (Upgrade) To start upgrading to version 4.1 SP6 from 4.0 SP2, double-click BO_41_SP6_64_bit_Server_Update_WIN.exe.
        For detailed upgrade instructions, refer to the Business Intelligence Platform Upgrade Guide at PDFs.
       
    • For information about supported versions of BusinessObjects BI, see System requirements.
    • For information about licensing requirements, see Applying passwords or licensing requirements.
  • The BusinessObjects BI server must be configured to use Enterprise Authentication. See the "Authentication" section in the Business Intelligence Platform Administrator Guide at PDFs for more information.
  • The BusinessObjects BI server must be configured to automatically resolve its host name. For instructions, see Configuring the application server.
  • Configure the JDBC drivers.
  • Ensure that all services are running. For more information, see Restarting the BusinessObjects services.
  • Optionally, download and install SAP BusinessObjects BI Platform Client Tools on the BusinessObjects BI server. Client Tools are required to perform miscellaneous tasks, such as creating custom reports or editing existing reports.

    Note

    Download the same version of Client Tools as of BusinessObjects BI server. BMC recommends that you install Client Tools on a different computer than the BusinessObjects BI server.


    To start the installation, open one of the zip files using Windows Explorer, and double-click the setup.exe file: 

    BMC Decision Support – Network
    Automation version
    BusinessObjects BI Client tools fileFile location
    8.9.02.005
    8.9.02.004
    8.9.02.003
    8.9.02.002
    8.9.02.001
    BO_42_SP5_Client_Tools_WIN.zipSBOP_BI_PLAT_4.2_SP5_CLNT_WIN_32_64B_\DATA_UNITS\BusinessObjectsClient
    8.9.02
    8.9.01
    BO_41_SP9_Client_Tools_WIN.zipSBOP_BI_PLAT_4.1_SP9_CLNT_WIN_32_64B_\DATA_UNITS\BusinessObjectsClient
    8.9.00BO_41_SP6_Client_Tools_WIN.zipSBOP_BI_PLAT_4.1_SP6_CLNT_WIN_32_64B_\DATA_UNITS\BusinessObjectsClient

Configuring the application server

The application server must be able to automatically resolve the host name for the BusinessObjects BI server (the reporting server). If the application server is unable to automatically resolve the reporting server's host name, you can manually configure access to the reporting server.

This section describes how to manually configure access to the reporting server for servers with a static IP address or a dynamic IP address by using the Central Management Console. BMC recommends that you use a static IP address, if possible.

For complete information about using the Central Management Console, see the Business Intelligence Platform Administrator Guide at PDFs.

To configure access to a reporting server with a static IP address

  1. On the application server, navigate to the Windows\System32\drivers\etc directory.
  2. Edit the hosts file in a text editor and add an entry mapping the reporting server IP address to the host name, using a fully-qualified host name as shown in the following example:
    10.128.35.39 vw-pun-bna-pt03.pune-labs.bmc.com
  3. Save the file.

To configure access to a reporting server with a dynamic IP address

  1. Log on to the Central Management Console as an Administrator.
  2. Navigate to Servers List.
  3. In the right pane, right-click CentralManagementServer and select Properties
  4. Under Common Settings, in the Host Identifiers section, select the Hostname option (if not selected already) and provide the BusinessObjects BI server host name.
  5. Restart the Central Management Server.

To redirect http port to https

  1. Navigate to the C:\Program Files (x86)\SAP BusinessObjects\tomcat\webapps\BOE\WEB-INF directory and open the web.xml file with a text editor.
  2. Add the <security-constraint> tag before the closing tag of <web-app>, as follows:

    <web-app xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/j2ee" version="2.4" id="BOE">
    .....
    	<security-constraint>	
    		<web-resource-collection>
    			<web-resource-name>http://<BusinessObjectsBIServerHostName>:8080</web-resource-name>
    			<url-pattern>/*</url-pattern>
    		</web-resource-collection>
    	<!-- auth-constraint goes here if you require authentication -->
    		<user-data-constraint>
    			<transport-guarantee>https://<BusinessObjectsBIServerHostName>:8443</transport-guarantee>
    		</user-data-constraint>
    	</security-constraint>
    </web-app>

    Replace BusinessObjectsBIServerHostName with the host name of the BusinessObjects BI server. 8080 is the http port number and 8443 is the https port number.

  3. Restart Tomcat.

Configuring the JDBC drivers

This section provides instructions for ensuring that the reporting server has access to the BMC Decision Support – Network Automation data warehouse.

Important

You do not need to perform this task for 8.9.02 and later versions of BMC Decision Support – Network Automation. The Content Deployment utility configures the JDBC drivers.

To configure the BusinessObjects server JDBC drivers 

  1. Download or copy one of the following JAR files from the internet, by using the appropriate file for your database type:
  2. Copy the JAR file to the BusinessObjects Business Intelligence (BI) server (for example, you might copy it under D:\program files\Business Objects).
  3. Locate the following database file for your database type.
    The file is usually located in the BusinessObjects BI installation directory. For example, C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\dataAccess\connectionServer\jdbc.
    • Oracle: oracle.sbo
    • SQL Server: sqlsrv.sbo
    • Postgres: Locate the file as follows:
      • greenplum.sbo: If you are using version 4.0 of BusinessObjects BI platform or you are upgrading from version 4.0 to 4.1.
      • postgresql.sbo: If you are doing a fresh installation of version 4.1 of BusinessObjects BI platform. 
  4. Edit the database file for your database type and modify the settings for each database type as follows:
    • For all versions of Oracle: 
      1. Find Oracle 11 and locate the <JDBCDriver> tag. If the tag already exists, change the path to the one where you have copied the ojdbc6.jar file. 
        If the <classpath> tag does not exist in the <JDBCDriver> tag, go to step b. A sample file without the <classpath> tag looks like the following. 

        <DataBase Active="Yes" Name="Oracle 11">
        	<JDBCDriver>
            	<!-- Uncomment and edit the following lines
            		 to define java classes required by JDBC driver
        	         &lt;ClassPath&gt;
             		 &lt;Path&gt;your jar or class files directory&lt;/Path&gt;
                	 &lt;/ClassPath&gt;
                -->
                ...
            </JDBCDriver>
                    ...
        </DataBase>
      2. Replace the content in the <JDBCDriver> tag with the following content, as follows:

        <DataBase Active="Yes" Name="Oracle 11">
        	<JDBCDriver>
            	<ClassPath>
                	<Path>
                		D:\program files\Business Objects\ojdbc6.jar
        	        </Path>
                </ClassPath>
            </JDBCDriver>
            ...
        </DataBase>
        


        D:\program files\Business Objects indicates the path where you have copied the ojdbc6.jar file.

    • For all versions of SQL Server:
      1. Find MS SQL Server 2008 and locate the <JDBCDriver> tag. If the tag already exists, change the path to the one where you have copied the sqljdbc4.jar file. 
        If the <classpath> tag does not exist in the <JDBCDriver> tag, go to step b. A sample file without the <classpath> tag looks like the following: 

        <DataBase Active="Yes" Name="MS SQL Server 2008">
        	<JDBCDriver>
            	<!--  Uncomment and edit the following lines
                	  to define java classes required by JDBC driver
                      &lt;ClassPath&gt;
                      &lt;Path&gt;your jar or class files directory&lt;/Path&gt;
                      &lt;/ClassPath&gt;
                -->
                ...
            </JDBCDriver>
            ...
        </DataBase>
      2. Replace the content in the <JDBCDriver> tag with the following content, as follows:

        <DataBase Active="Yes" Name="MS SQL Server 2008">
        	<JDBCDriver>
            	<ClassPath>
                	<Path>
                    	D:\program files\Business Objects\sqljdbc42.jar
                    </Path>
                </ClassPath>
            </JDBCDriver>
            ...
        </DataBase>
        

        D:\program files\Business Objects indicates the path where you have copied the sqljdbc42.jar file.

    • For Postgres:
      • If you have upgraded from version 4.0 to 4.1 of BusinessObjects BI platform, follow these steps:
        1. Rename the existing greenplum.sbo file. 
        2. Copy the attached sample greenplum.sbo file to the BusinessObjects BI installation directory. For example, C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\dataAccess\connectionServer\jdbc.
        3. Perform steps i and ii in the copied greenplum.sbo file.
      • In case of fresh installation of version 4.1 of BusinessObjects BI platform, perform steps i and ii in the postgresql.sbo file:
        1. For all versions of Postgres, find Postgres 8 and locate the <JDBCDriver> tag. If the tag already exists, change the path to the one where you have copied the postgresql-9.4.1207.jre6.jar or postgresql-9.4-1206-jdbc4.jar file.
          If the <classpath> tag does not exist in the <JDBCDriver> tag, go to step b. A sample file without the <classpath> tag looks like the following:

          <DataBase Active="Yes" Name="Postgres 8">
          	<JDBCDriver>
              	<!--  Uncomment and edit the following lines
                        to define java classes required by JDBC driver
                        &lt;ClassPath&gt;
                        &lt;Path&gt;your jar or class files directory&lt;/Path&gt;
                   	  &lt;/ClassPath&gt;
                  -->
                  ...
              </JDBCDriver>
              ...
          </DataBase>
        2. Replace the content in the <JDBCDriver> tag with the following content, as follows:

          <DataBase Active="Yes" Name="Postgres 8">
          	<JDBCDriver>
              	<ClassPath>
                  	<Path>
                      	D:\program files\Business Objects\postgresql-9.4.1207.jre6.jar
                      </Path>
                  </ClassPath>
              </JDBCDriver>
              ...
          </DataBase>
          

          D:\program files\Business Objects indicates the path where you have copied the postgresql-9.4.1207.jre6.jar or postgresql-9.4-1206-jdbc4.jar file.

  5. Save and close the file.
  6. Restart the BusinessObjects services.

Securing the SAP BusinessObjects BI launch pad

Use the following guidelines to make the SAP BusinessObjects BI launch pad web application secure:

  • Do not use the browser auto-complete feature to store the password for SAP BusinessObjects BI launch pad. 
  • Do not use IBM WebSphere Application Server 7.x for hosting the SAP BusinessObjects BI launch pad.

BMC recommends to follow these steps to make the SAP BusinessObjects BI launch pad web application secure:

  1. Use SSL certificates for the SAP BusinessObjects Tomcat. Perform the following steps to apply SSL certificates to the BusinessObjects Tomcat:
    1. Stop Tomcat.
    2. Enable SSL for Tomcat by uncommenting the entry for the SSL connector in the server.xml file, which is located at %TOMCAT_HOME%\conf\server.xml by default.
    3. In the server.xml file, add the correct file path of the keystore and truststore and use TLSv1.2 version for the sslEnabledProtocols property. The following example shows a sample file with the keystore and truststore path:

      <Connector port='8443' maxHttpHeaderSize='8192' maxThreads='150' minSpareThreads='25'
      maxSpareThreads='75' enableLookups='false' disableUploadTimeout='true' acceptCount='100' scheme='https'
      secure='true' clientAuth='false' sslProtocol='TLS' sslEnabledProtocols='TLSv1.2' keystoreFile='C:\https\server.ks'
      truststoreFile='C:\https\server.ts'/>
    4. Start Tomcat.

  2. Configure the crossdomain.xml located at %TOMCAT_HOME%\webapps\ROOT to allow access only to domains that are authorized to access the web application. For information refer to the Tomcat documentation.
  3. Configure the BusinessObjects web application located at %TOMCAT_HOME%\webapps\BOE by following these steps:
    1. Stop Tomcat.
    2. Create a directory called custom in the following directory: %TOMCAT_HOME%\webapps\BOE\WEB-INF\config.
    3. Copy the global.properties and BIlaunchpad.properties files from %TOMCAT_HOME%\webapps\BOE\WEB-INF\config\default to %TOMCAT_HOME%\webapps\BOE\WEB-INF\config\custom.
    4. Open the global.properties file located at %TOMCAT_HOME%\webapps\BOE\WEB-INF\config\custom using notepad, and set properties as follows:

      logon.embed.secret=<secret>
      logon.embed.timeout=1
      persistentcookies.enabled=false
    5. Open the BIlaunchpad.properties file located at %TOMCAT_HOME%\webapps\BOE\WEB-INF\config\custom using notepad and set properties as follows. Add a property if it does not exist.

      enforceTopLevelFrame.enabled=true
      logontoken.enabled=false
      logon.allowInsecureEmbedding=false
    6. Start Tomcat.

Where to go from here

Setting up the application server

Was this page helpful? Yes No Submitting... Thank you

Comments