Important

   

Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

Installing and configuring Yellowfin to enable Live reporting (for versions 8.9.01 and later)

This topic describes the process to install and configure Live Reporting with BMC Server Automation, and includes the following sections:

The Live reporting dashboard displays complete information about patch management, compliance, and job activity in one consolidated view. The dashboard contains multiple reports, many of which you can run live while you are in a patching window, to review up-to-the-minute compliance. 

For more information about the dashboard, see Using the Live Reporting dashboard.


Notes

  • Use of Yellowfin technology is provided in conjunction with the Live reporting dashboard capability of BMC Server Automation. Use of Yellowfin for capabilities other than the Live reporting dashboard or independently of the integrated BMC Product is prohibited.
  • If you are BMC Server Automation 8.9.00, you must use the installer shipped with that versions and follow instructions provided in Installing and configuring Yellowfin to enable Live reporting.

System requirements for Live Reporting

This section describes the requirements for installing and using Live Reporting in your environment.

Application server requirements

Requirement

Recommended minimum specifications

Processor

2 x Dual Core 3GHz or faster

RAM

4 GB minimum

Hard Disk

1 GB free space

Operating System

  • Windows 2000 or later
  • Red Hat Enterprise Linux

Database server requirements

Requirement

Recommended minimum specifications

Processor

2 x Dual Core 3Ghz or faster

RAM

4 GB minimum

Hard Disk

10 GB (preferably with RAID disk mirroring)

Database

For Live Reporting, BMC supports only the following databases as
an application configuration database:

  • Oracle Database 11g R2 and 12c
  • SQL Server 2008 R2 and 2012 R2

Client requirements

Requirement

Recommended minimum specifications

Web Browser

Supported browsers include:

  • Internet Explorer 8+
  • Firefox 2+
  • Opera 8+
  • Safari 2+
PDF

PDF reader such as Adobe Acrobat Reader for viewing PDF files. This reader is required only if users export Live Reporting reports to PDF.

Requirements for concurrent users

Number of users

CPU requirements

RAM requirements

Developer / Demonstration

Single 2 GHz Xeon or equivalent

2 Gb

25 or Less Concurrent Users

2 x 2 GHz Xeon or equivalent

4 Gb

50 Concurrent Users

4 x 2 GHz Xeon or equivalent

8 Gb

150 Concurrent Users

8 x 2 GHz Xeon or equivalent

16 Gb

Downloading the installation files

Download and extract the Live Reporting installer from the Electronic Product Distribution (EPD) website:

Use the appropriate Live Reporting components, depending on which operating system you are installing on.

For Windows

Installer for Live Reporting (BladeLogic_LiveReportingInstaller.exe)
 

For Linux

Installer for Live Reporting (BladeLogic_LiveReportingInstaller.bin)

Before you begin

Tip

To prevent erroneous WS.Reputation.1 alert messages from being generated, disable the Symantec anti-virus software in your environment before you start installation. The Live Reporting installer is not malicious. You can re-enable Symantec when the installation is finished. For more information, see How to bypass Symantec’s WS.Reputation.1 System.

  • Live Reporting upgrade to 8.9.02 from Live Reporting 8.9.00 or 8.8.xx is not supported. BMC recommends you to first manually uninstall the existing version, that is, Live Reporting 8.9.00 or 8.8.xx, and only then install Live Reporting 8.9.02.  For steps on uninstalling the existing version of yellowfin, see Uninstalling yellowfin
  • As no new features have been added to Live Reporting 8.9.02 after the 8.9.01 release, BMC recommends you not to re-install 8.9.02 if you are already running Live Reporting 8.9.01.
  • When BMC customers use Live Reporting in their production environment, the type of Yellowfin database must match the BMC Server Automation database. For example, if your BladeLogic Server Automation environment is running MS SQL Server, then your Yellowfin environment must also be running MS SQL Server. You cannot mismatch databases.
  • The database server does not have to reside on the same system as the Live Reporting application. However, BMC recommends that you install Live Reporting on a dedicated host.
  • Install Oracle 64-bit JRE 1.6 or later. BMC tested both JRE 1.7 and JRE 1.8 in its lab environments. Do not install the JRE Server version of the product.

  • For Windows, you must use a pre-created MS SQL Server database and database user. Keep the following information handy while installing the Live Reporting feature. For more information about pre-creating a Microsoft SQL database, see Walkthrough: Setting up a SQL Server database.

    Tip

    You can refer to the steps for creating a Microsoft SQL database for BMC Server Automation. Note that you will have to use yellowfin-specific values provided below while creating the database, instead of the BSA-specific values provided in Walkthrough: Setting up a SQL Server database.

    The information you need is:

    • Host name or IP address of the Windows server running the database
    • Port number that the database listens on. The default port is 1433 for MS SQL Server
    • Credentials of a database user. Do not use the default sa user for the Yellowfin database user; use a more restricted user for the Yellowfin database. Choose one of the following:
      • Database and database user credentials supplied to you by your DBA 
      • If you are using Windows Authentication, pre-create a user account in Computer Management and add it to the Administrator group, and then pre-create a database and a database user.
    • Credentials of the database administrator (for example, sa).
    • For SQL database user, no specific permissions are required.
  • For Linux, you must use a pre-created Oracle database and database user. Keep the following information handy while installing the Live Reporting feature.

    Tip

    You can refer to the steps for creating an Oracle database for BMC Server Automation. Note that you will have to use yellowfin-specific values provided below while creating the database, instead of the BSA-specific values provided in Walkthrough: Creating the BladeLogic Database for Oracle.


    The information you need is:

    • Host name or IP address of the Linux server running the database
    • Port number that the database listens on. The default port is 1521 for Oracle.
    • Oracle SID (for example, ORA112DB) or the Oracle Service Name used to connect with Oracle, as defined in tnsnames.ora.
    • Credential of a database user (do not use system) which is specifically created to configure the Yellowfin metadata.  The schema of database user must be empty.

 Click here to expand detailed instructions on manually creating a tablespace and Yellowfin database user for Oracle database
  1. Create a yellowfin directory with the correct permissions to store the table space. For example:

    mkdir /data1/oracle/product/database/yellowfin
    chown oracle:dba /data1/oracle/product/databases/yellowfin
  2. Log on to SQL *Plus and connect to the Oracle database. For example:

    su - oracle
    sqlplus /nolog
    connect sys/password@ORA112DB as SYSDBA
  3. Create a Yellowfin table space, which can be used by the Yellowfin installer. For example:

    CREATE TABLESPACE YELLOWFIN LOGGING
    DATAFILE '/data1/oracle/product/databases/yellowfin/YELLOWFIN.dbf'
    SIZE 200M DEFAULT STORAGE (INITIAL 500M NEXT 100M MAXEXTENTS UNLIMITED PCTINCREASE 0);
  4. Create a Yellowfin table space index. For example:

    CREATE TABLESPACE YELLOWFIN_INDEX LOGGING
    DATAFILE '/data1/oracle/product/databases/yellowfin/YELLOWFIN_INDEX.dbf'
    SIZE 50M DEFAULT STORAGE ( INITIAL 500M NEXT 100M MAXEXTENTS UNLIMITED PCTINCREASE 0);
  5. Create a Yellowfin database user and grant required permissions to the user. For example:

    CREATE USER YELLOWFIN
    PROFILE DEFAULT IDENTIFIED BY password
    DEFAULT TABLESPACE YELLOWFIN
    TEMPORARY TABLESPACE TEMP ACCOUNT UNLOCK;
    GRANT CONNECT TO YELLOWFIN;
    GRANT RESOURCE TO YELLOWFIN;
    GRANT CREATE VIEW TO YELLOWFIN;
    GRANT SELECT ANY DICTIONARY TO YELLOWFIN;
    GRANT EXECUTE ON dbms_lock TO YELLOWFIN;
    GRANT UNLIMITED TABLESPACE TO YELLOWFIN;
    GRANT EXECUTE ON DBMS_LOB TO YELLOWFIN;
    GRANT EXECUTE ON DBMS_SQL TO YELLOWFIN;
    GRANT CREATE TABLE TO YELLOWFIN;
    GRANT CREATE SEQUENCE TO YELLOWFIN;
    GRANT CREATE TRIGGER TO YELLOWFIN;
    GRANT CREATE PROCEDURE TO YELLOWFIN;
  6. Alter the data files of the BSA schema table space and the Index table space to auto extend. For example:

    ALTER DATABASE
    DATAFILE '/data1/oracle/product/databases/yellowfin/YELLOWFIN.dbf'
    AUTOEXTEND ON NEXT 250M;
    ALTER DATABASE
    DATAFILE '/data1/oracle/product/databases/yellowfin/YELLOWFIN_INDEX.dbf'
    AUTOEXTEND ON NEXT 50M;

Step 1: Installing Live Reporting

Depending on which operating system you are installing Live Reporting on, follow one of the following procedures.

    Perform the following steps to install Live Reporting on your Windows host.

    1. Run the Live Reporting installation file (for example, BladeLogic_LiveReportingInstaller.exe) as an administrator.
    2. The first screen of the Live Reporting installation wizard appears. Click Next.
    3. Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement.
      Click Next.

    4. Enter the HTTPS port number of the Yellowfin server that you want to connect to. The default port number is 8443.

      Tip

      Enable the Install Windows Service option, if you want to install Yellowfin as a windows service. This enables Yellowfin to automatically start whenever the server is started.

    5. Select the type of database that you are using with Yellowfin, which is Microsoft SQL for this procedure.

    6. Enter the Yellowfin SQL server database details (which you created in in this step) as displayed in the following screenshot and table:

      Field Description
      Host Name or IP Address Enter the Host name or IP address of the server that runs the Yellowfin SQL server database.
      Port Enter the port that the Yellowfin database listens on. The default port is1433 for an SQL Database.
      Instance Name
      (only visible if the Named Instance option is selected)
      Enter the name of the database instance that you created.
      Database Name Enter the name of the database that you created.
      User Name Enter the user name that you created for the database.
      User Password Enter the user name password that you created for the database.
      Confirm User Password Confirm the user name password that you created for the database.
      Windows Authentication or SQL Server Authentication Select whether the user must log on to the Yellowfin database server using Windows credentials or SQL server credentials.
    7. Enter and confirm the password that you want to assign to the Yellowfin REPORT_ADMIN user. The REPORT_ADMIN user is the default administrator user for Yellowfin.

    8. Enter the Tomcat Web server certificate information as displayed in the below screenshot and table. This information is used to enable an HTTPS connection to Yellowfin.

      Field Description
      Common Name (CN) Enter a name to identify the CA certificate
      Organizational Unit (OU) Enter your organization unit, for example: IDD
      Organization Name (O) Enter your organization name, for example: BMC Software
      Locality Name (L) Enter the name of your locality, for example: San Jose 
      State Name (S) Enter the name of your state, for example: California
      Country (C) Enter the name of your country, for example: USA
      Create Keystore Password Enter the keystore password.
      Important: Enter the password that is set for JRE cacerts keystore in BMC Server Automation. The default password set for cacerts is typically changeit.
      Create Keystore Password Confirm the keystore password.
      Important: Enter the password that is set for JRE cacerts keystore in BMC Server Automation. The default password set for cacerts is typically changeit.
    9. Enter BMC Server Automation database server details as displayed in the following screenshot and table:

      Field Description
      Host Name or IP Address Enter the Host name or IP address of the server that runs the BMC Server Automation (BSA) database.
      Port Enter the port that the BSA database listens on. The default port is1433 for an SQL Database.
      Instance Name
      (only visible if the Named Instance option is selected)
      Enter the name of the BSA database instance.
      Database Name Enter the name of the BSA database.
      User Name Enter the user name of the BSA database.
      User Password Enter the user name password of the BSA database.
      Confirm User Password Confirm the user name password of the BSA database.
      Windows Authentication or SQL Server Authentication Select whether the user must log on to the BSA database server using Windows credentials or SQL server credentials.
    10. Enter the path to the directory in which you want to install Live Reporting. The default path is C:\Program Files\BMC Software\Live_Reporting. Click Next.

      Tip

      Enter a path without extra spaces or punctuation to avoid errors during installation.

        If you need to install Live Reporting on a system that does not have internet access, click here for more information.

      If you need to install Live Reporting on a system that does not have internet access, perform the following steps:

      1. Install Live Reporting on a supported Microsoft Windows or Linux operating system.
      2. Stop the Yellowfin service.
      3. Locate the following section in the <yellowfin_installation_directory>/appserver/webapps/root/web-inf/web.xml file:
        <!DOCTYPE web-app
        PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
        "http://java.sun.com/dtd/web-app_2_3.dtd" [
        <!ENTITY jsps SYSTEM "file:/opt/bmc/Yellowfin/appserver/webapps/ROOT/WEB-INF/web-jsps.xml">
        ]>
      4. Replace the above with the following: 
        <!DOCTYPE web-app
        SYSTEM "web-app_2_3.dtd" [
        <!ENTITY jsps SYSTEM "file:/opt/bmc/Yellowfin/appserver/webapps/ROOT/WEB-INF/web-jsps.xml">
        ]>
      5. Start the Yellowfin service.
      6. Run the post-installation script:
        • postinstaller.bat (Windows)
        • postinstaller.sh (Linux)

      Note

      A sample path for Microsoft Windows in the ENTITY jsps SYSTEM tag is

      <!ENTITY jsps SYSTEM "file:C:\Program Files\BMC Software\Live_Reporting\Yellowfin\appserver\webapps\ROOT\WEB-INF\web-jsps.xml">

    11. Review the information on the Preview screen and click install to start the installation.

      Tip

      The installation should take 20-25 minutes to complete successfully.

    12. After the installation is successful, you must not close the Tomcat window.

    Perform the following steps to install Live Reporting on your Linux host.

    1. Run the Live Reporting installation file (for example, BladeLogic_LiveReportingInstaller.bin) as a root user.
    2. The first screen of the Live Reporting installation wizard appears. Click Next.
    3. Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement.
      Click Next.

    4. Enter the HTTPS port number of the Yellowfin server that you want to connect to. The default port number is 8443.

    5. Select the type of database that you are using with Yellowfin, which is Oracle for this procedure.
    6. Enter the Yellowfin Oracle database details (which you created in in this step) as displayed in the following screenshot and table:

      Field Description
      Host Name or IP Address Enter the Host name or IP address of the server that runs the Yellowfin Oracle database.
      Port Enter the port that the Yellowfin database listens on. The default port is 1521 for an Oracle Database.
      Service or SID
      (depending on the option you have selected)
      Enter the database SID or the Service name, depending on which option you have selected.
      User Name Enter the user name of a database user (do not use system) which is specifically created to configure the Yellowfin metadata.

      User Password Enter the password of the user name that you created for the database.
      Confirm User Password Confirm the password of the user name that you created for the database.
    7. Enter and confirm the password that you want to assign to the Yellowfin REPORT_ADMIN user. The REPORT_ADMIN user is the default administrator user for Yellowfin.
    8. Enter the Tomcat Web server certificate information as displayed in the below screenshot and table. This information is used to enable an HTTPS connection to Yellowfin.

      Field Description
      Common Name (CN) Enter a name to identify the CA certificate
      Organizational Unit (OU) Enter your organization unit, for example: IDD
      Organization Name (O) Enter your organization name, for example: BMC Software
      Locality Name (L) Enter the name of your locality, for example: San Jose 
      State Name (S) Enter the name of your state, for example: California
      Country (C) Enter the name of your country, for example: USA
      Create Keystore Password Enter the keystore password.
      Important: Enter the password that is set for JRE cacerts keystore in BMC Server Automation. The default password set for cacerts is typically changeit.
      Confirm Keystore Password Confirm the keystore password.
      Important: Enter the password that is set for JRE cacerts keystore in BMC Server Automation. The default password set for cacerts is typically changeit.
    9.  Enter BMC Server Automation database server details as displayed in the following screenshot and table:

      Field Description
      Host Name or IP Address Enter the Host name or IP address of the server that runs the BMC Server Automation Oracle database.
      Port Enter the port that the BMC Server Automation database listens on. The default port is 1521 for an Oracle Database.
      Service or SID
      (depending on the option you have selected)
      Enter the database SID or the Service name, depending on which option you have selected.
      User Name Enter the user name of the BSA database.
      User Password Enter the password of the user name of the BSA database.
      Confirm User Password Confirm the password of the user name of the BSA database.
    10. Enter the path to the directory in which you want to install the Live Reporting feature. The default installation path is /opt/bmc/live_reporting. Click Next.

      Tip

      Enter a path without extra spaces or punctuation to avoid errors during installation.

        If you need to install Yellowfin on a system that does not have internet access, click here for more information.

      If you need to install Live Reporting on a system that does not have internet access, perform the following steps:

      1. Install Live Reporting on a supported Microsoft Windows or Linux operating system.
      2. Stop the Yellowfin service.
      3. Locate the following section in the <yellowfin_installation_directory>/appserver/webapps/root/web-inf/web.xml file:
        <!DOCTYPE web-app
        PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
        "http://java.sun.com/dtd/web-app_2_3.dtd" [
        <!ENTITY jsps SYSTEM "file:/opt/bmc/Yellowfin/appserver/webapps/ROOT/WEB-INF/web-jsps.xml">
        ]>
      4. Replace the above with the following: 
        <!DOCTYPE web-app
        SYSTEM "web-app_2_3.dtd" [
        <!ENTITY jsps SYSTEM "file:/opt/bmc/Yellowfin/appserver/webapps/ROOT/WEB-INF/web-jsps.xml">
        ]>
      5. Start the Yellowfin service.
      6. Run the post-installation script:
        • postinstaller.bat (Windows)
        • postinstaller.sh (Linux)

      Note

      A sample path for Microsoft Windows in the ENTITY jsps SYSTEM tag is

      <!ENTITY jsps SYSTEM "file:C:\Program Files\BMC Software\Live_Reporting\Yellowfin\appserver\webapps\ROOT\WEB-INF\web-jsps.xml">

      For Windows, use the postinstaller.bat script and the property file (LiveReportingConfig.properties) shipped with BMC Server Automation to configure Yellowfin with BMC Server Automation. The postinstaller.bat file can be found in the following location:

      Path Example
      <Yellowfin Installation Location>\Live_Reporting\liveReportingPostInstaller/postinstaller.bat C:\Program Files\BMC Software\Live_Reporting\liveReportingPostInstaller\postinstaller.bat

      The following video shows how to configure YellowFin for the BMC Server Automation Live Reporting dashboard in a Windows/SQL Server environment.

      https://www.youtube.com/watch?v=tQ19rHAWJtE

      Perform the following steps:

      1. Go to the LiveReportingPostInstaller.zip directory that you previously extracted.

      2. Change directories to the appropriate Yellowfin post-installer package on the same machine where the Yellowfin server is installed. 

      3. Update the properties in the LiveReportingConfig.properties file, using any text editor.

        Properties Description
        bsa_db_username
        Enter the name of the BSA database user you created. For more information, see Walkthrough: Setting up a SQL Server database.
        bsa_db_hostname
        Host name of the server running the BMC Server Automation database
        bsa_db_port
        Port that the database listens on. The default port is 1433 for SQL Database
        bsa_db_type(Oracle/MSSQL)
        Enter MSSQL for the Microsoft SQL database
        bsa_db_mssql_dbname
        Name of the database instance.
        bsa_db_orcl_connection_method(SID/Service)
        Leave this property empty if you are using a Microsoft SQL database.
        bsa_db_oracle_sid
        Leave this property empty if you are using a Microsoft SQL database.
        yellowfin_server_hostname
        Host name of the server hosting the Yellowfin server
        yellowfin_server_portnumber
        Port number that the Yellowfin server listens on. The default port number is now 8443 since you previously configured the HTTPS protocol.
        yellowfin_server_installPath
        Path at which the Yellowfin business intelligence tool is installed. NOTE: For Windows, the path must use forward slashes (/) rather than the normal Windows-format backslashes (\)

        A sample, valid path on windows is C:/Users/Administrator/Yellowfin71. The postinstall configuration fails if you use backslashes.

        Click Expand source to see a sample property file
      4. Verify that the Yellowfin service is running.

      5. Execute the Yellowfin postInstaller.bat script (Windows) in a command window, and provide the following inputs when prompted by the script:

        Tip

        If you make a mistake and the script throws an error, troubleshoot the problem and re-run the script. The script is surprisingly forgiving.

        1. Enter the BMC Server Automation database user password when prompted by the script.

        2. Create a temporary password for the new REPORT_ADMIN user when you are prompted by the script. This password must contain at least four characters.

          Note

          The postinstaller script deletes the default Yellowfin admin user.
        3. Enter the password for Yellowfin database user when you are prompted by the script.
          The script finishes in a few minutes.  

          PS C:\Yellowfin\LiveReportingPostInstaller> .\postInstaller.bat
          C:\Yellowfin\LiveReportingPostInstaller>.\windows_jre\jre1.8.0_71\bin\java -jar PostInstaller.jar
          [main] INFO  com.bmc.postinstaller.livereporting.LiveReportingPostInstaller  
             - Loading data from property file
          ...
          Enter BSA bladelogic Database user Password
          Enter password for yellowfin admin@yellowfin.com.au user
          Enter password for yellowfin REPORT_ADMIN user
          Re-Enter password for yellowfin REPORT_ADMIN user
          Enter Password of  yellowfin Database
          [main] INFO  com.bmc.postinstaller.livereporting.LiveReportingPostInstaller  
             - Completed fetching the details
          ...
          [main] INFO  com.bmc.postinstaller.livereporting.LiveReportingPostInstaller  
             - Adding user REPORT_ADMIN

      Tip

      See the yellowfinpostinstaller.log file of the postinstaller script in the

      <path-to-postinstaller>\log folder for troubleshooting purposes.

      For Linux, use the postinstaller.sh script and the property file (LiveReportingConfig.properties) shipped with BMC Server Automation to configure Yellowfin with BMC Server Automation.

      The postinstaller.sh file can be found in the following location:

      Path Example
      <Yellowfin Installation Location>/Live_Reporting/liveReportingPostInstaller/postinstaller.sh

      /opt/bmc/bladelogic/Live_Reporting/liveReportingPostInstaller/postinstaller.sh

      Perform the following steps:

      1. Go to the LiveReportingPostInstaller folder that you previously extracted.

      2. Change directories to the appropriate Yellowfin post-installer package on the same machine where the Yellowfin server is installed. 

      3. Update the properties in the LiveReportingConfig.properties file, using any text editor.

        Properties Description
        bsa_db_username
        Enter the name of the BSA database user you created. For more information, see Walkthrough: Creating the BladeLogic Database for Oracle.
        bsa_db_hostname
        Host name of the server running the BMC Server Automation database
        bsa_db_port
        Port that the database listens on. The default port is 1521 for Oracle Database
        bsa_db_type(Oracle/MSSQL)
        Enter Oracle for the Oracle database
        bsa_db_mssql_dbname
        Leave this property empty if you are using a Oracle database
        bsa_db_orcl_connection_method(SID/Service)
        Connection method to access the Oracle database, defined in tnsnames.ora file.
        bsa_db_oracle_sid
        SID of the database.
        yellowfin_server_hostname
        Host name of the server hosting the Yellowfin server
        yellowfin_server_portnumber
        Port number that the Yellowfin server listens on. The default port number is now 8443 since you previously configured the HTTPS protocol.
        yellowfin_server_installPath
        Path at which the Yellowfin business intelligence tool is installed
        Click Expand source to see a sample property file
      4. Execute the Yellowfin postinstaller.sh (Linux) script, and provide the following inputs when prompted by the script:

        Tip

        If you make a mistake and the script throws an error, troubleshoot the problem and re-run the script. The script is surprisingly forgiving.

         

        1. Enter the BMC Server Automation database user password when prompted by the script.

        2. Create a temporary password for the new REPORT_ADMIN user when you are prompted by the script. This password must contain at least four characters.

          Note

          The postinstaller script deletes the default admin user.
        3. Enter the password for Yellowfin database when you are prompted by the script.

          [root@clm-aus-011043 LinuxLiveReportingPostInstaller]# ./postInstaller.sh 
          [main] INFO  com.bmc.postinstaller.livereporting.LiveReportingPostInstaller  
             - Loading data from property file
          ...
          Enter BSA bladelogic Database user Password
          Enter password for yellowfin admin@yellowfin.com.au user
          Enter password for yellowfin REPORT_ADMIN userfire
          Re-Enter password for yellowfin REPORT_ADMIN user
          Enter Password of  yellowfin Database
          [main] INFO  com.bmc.postinstaller.livereporting.LiveReportingPostInstaller  
             - Completed fetching the details
          [main] INFO  com.bmc.postinstaller.livereporting.LiveReportingPostInstaller  
             - Adding user REPORT_ADMIN

      Tip

      See the yellowfinpostinstaller.log file of the postinstaller script in the <path-to-postinstaller>\log folder for troubleshooting purposes.

    11. Review the information on the Preview screen and click install to start the installation.

      Tip

      The installation should take 35-40 minutes to complete successfully.

    Step 2: Importing certificate to BMC Server Automation application server

    You must import the certificate on every Application Server and Configuration Server in your environment. Otherwise, you will see an error when you try to access the Live Reporting data from the Application Servers.

    1. Copy <installed_directory>\Yellowfin\appserver\conf\yellowfin_server.cer and paste it into a temp folder on the BSA Application Server host.  
    2. Open a administrative command prompt.
    3. Run the keytool command from the jre\bin installed with the BSA Application Server. The default path for bin directory are as follows:
      For Linux : <installed_directory>/appserver/NSH/br/java/bin
      For Windows : <installed_directory>\appserver\NSH\jre\bin

    4. Import <temp_folder>\yellowfin_server.cer into your BSA Application Server Java cacerts keystore. The default path for cacerts keystore are as follows:
      For Windows : <installed_directory>\appserver\NSH\jre\lib\security\cacerts
      For Linux: <installed_directory>/appserver/NSH/br/java/lib/security).
      For example, in a Windows environment:
      keytool -import -alias yellowfin-server -keystore "C:\Program Files\BMC Software\BladeLogic\appserver\NSH\jre\lib\security\cacerts" -trustcacerts -file "C:\temp\yellowfin_server.cer"
       

      For example, in a Linux environment:
      keytool -import -alias yellowfin-server -keystore "/opt/bmc/bladelogic/appserver/NSH/br/java/lib/security/cacerts" -trustcacerts -file "/tmp/yellowfin_server.cer"



    5. At the prompt, enter changeit as the default cacerts password.
    6. At the prompt to trust the certificate, enter yes.

      keytool -import -alias yellowfin-server 
        -keystore "<installed_directory>\appserver\NSH\jre\lib\security\cacerts" 
        -trustcacerts -file "<temp_directory>\yellowfin_server.cer"
      Enter keystore password:
      Owner: CN=clm-aus-013663.bmc.com, OU=IDD, O=BMC Software, 
        L=San Jose, ST=California, C=US
      Issuer: CN=clm-aus-013663.bmc.com, OU=IDD, O=BMC Software, 
        L=San Jose, ST=California, C=US
      Serial number: 744eb125
      
      Valid from: Thu Apr 07 07:59:15 GMT-12:00 2016 until: Fri Apr 07 07:59:15 GMT-12
      :00 2017
      Certificate fingerprints:
               MD5:  4D:EE:5D:7A:F1:FF:1F:6B:78:10:89:02:E0:86:D0:C4
               SHA1: 84:7A:C7:D9:18:FF:C8:4B:7D:60:9F:5B:08:A2:81:26:A7:6C:6A:D7
               SHA256: 75:A7:4E:DE:8E:04:D5:2D:6C:09:69:1B:FA:7B:5D:E8:DB:39:5B:
                  68:76:BC:EF:DC:31:BD:04:A5:60:95:66:0E
               Signature algorithm name: SHA256withRSA
               Version: 3
      Trust this certificate? [no]:  yes
      Certificate was added to keystore

       

    7. After you import the certificate, restart the BSA Application Server in which the certificate is imported.
      For example:

      /etc/init.d/blappserv stop
      /etc/init.d/blappserv start

    Step 3: Verifying the Live Reporting installation

    Follow this procedures to verify the Live Reporting installation.

    1. Verify that whether the Live Reporting is installed successfully by logging on to Yellowfin (https://<yellowfinServerName>:<portNumber>) with the new REPORT_ADMIN user. Update the details for the REPORT_ADMIN profile (for example, enter the temporary password, create and confirm the new password for REPORT_ADMIN, and so on) and save your changes. 

       

    2. After you save your changes, review the default page.

      Tip

      For troubleshooting purposes, see the live_reporting_install_log.txt file of the Live Reporting installer in the /tmp folder in Linux and C:\Users\ADMINI~1\AppData\Local\Temp in Windows.

    Step 4: Configuring the BLAS Admin

    Before you launch the live reporting dashboard, run the following command in the BLAS Admin console. For information about starting the BLAS admin console, see Starting the Application Server Administration console.

    set livereporting livereportingurl https://<hostname>:<portNumber>


    Replace the variables with values, as described in the following table:
    VariableDescription
    <hostname>Host name of the server hosting the Yellowfin server
    <portNumber>

    Port number that the Yellowfin server listens on.

    The default port number is 8443 since you are using the HTTPS protocol.

    Note

    If you are running multiple BladeLogic Application Servers in your environment, you only need to set the Live Reporting URL one time. However, you must import the yellowfin_server.cer into each Application Server in order to cross-launch the Live Reporting Dashboard with HTTPS.

     Examples:
    set livereporting livereportingurl https://<yellowfinServerName>:8443


    Step 5: Creating an automation principal for REPORT_ADMIN

    You need an automation principal to create an BladeLogic Application Server session to communicate with Yellowfin.

     Perform the following steps to create the automation principal for the REPORT_ADMIN user:

    1. Log on to BMC Server Automation Console using your RBAC Admin (RBACAdmin) credentials. For more information, see RBACAdmin and BLAdmin users.
    2. In the RBAC Manager folder, select Automation Principals.
    3. Create a new automation principal by right-clicking and selecting New > Automation Principal from the pop-up menu. The Automation Principal Creation wizard appears.
    4. Enter the following details to create your Automation principal for the REPORT ADMIN:

      FieldDescription
      NameEnter REPORT_ADMIN
      Description(Optional) Enter descriptive text
      Principal IDEnter REPORT_ADMIN
      DomainLeave empty
      PassphraseEnter the modified password of the REPORT_ADMIN user (not the temporary password that you created while running the post installer script)
      ConfirmRe-enter the modified password of the REPORT_ADMIN user
    5. Click Finish.

    Step 6: Assigning authorization to your role

    Perform the following steps:
    1. Remain logged on to BMC Server Automation Console using your RBAC Admin credentials. For more information, see RBACAdmin and BLAdmin users.
    2. In the RBAC Manager folder, select Roles.
    3. Right-click on the role that you will assign to the user, who launches the Live reporting dashboard (for example, BLAdmins), and select Open from the pop-up menu. Alternatively, create a new role for this by right-clicking and selecting New > Role from the pop-up menu.

    4. Click the System tab at the bottom of the Available Authorizations list.
    5. Assign the Report.Writer authorization to the role, by clicking and moving the Report.Writer authorization from the Available Authorizations box to the Selected Authorizations box.

      Tip

      Enter Report in the Type to filter field to shrink the number of roles that are displayed.


    6. Make sure the role now has the Report.Writer authorization.
    7. Assign the AutomationPrincipal.Read authorization to the role, by clicking and moving the AutomationPrincipal.Read authorization from the Available Authorizations box to the Selected Authorizations box. Note that you can skip this step if you are using the BLAdmin role to access Live Reporting.

      Tip

      Enter AutomationPrincipal in the Type to filter field to shrink the number of roles that are displayed.


    8. Click the Users tab to ensure that the role is assigned to the user with which you plan to launch the Live reporting dashboard. For more information about assigning roles to users from the Users tab, see Role - Users.

      Warning

      Ensure that the name of the user to whom the role is assigned to is not more than 20 characters.

    9. Save your changes to the role.
      For detailed information about creating a role and its authorizations, see Creating roles. For information about modifying a role and its authorizations, see Modifying Roles.

    You are now ready to use the Live reporting dashboard. For more information, see Where to go from here.

    Step 7: Populating the reports

    The first time you launch the Live Reporting dashboard from the console, no data is shown in any of reports. To populate the reports, do the following:

    Important

    You need to refresh the cached filter list to ensure that the latest values are reflected in the dashboards. Ensure that you perform this procedure at regular intervals so that latest information is disaplyed in your Live Reporting dashboard.


    1. Log on to Live Reporting using the REPORT_ADMIN user.
    2. Select Administration > Admin Console
    3. Click Schedule Management on the right of the screen.
    4. Click Select All to ensure that all filters are selected, and then click Run now.
    5. Ensure that all filters have been refreshed in the current date and time. If any filter still shows an earlier date and time in the Last Run column, select that filter and click Run Now again.
    6. The latest values of server groups, patch catalogs, and so on are now reflected in your dashboard. 

    Uninstalling Live Reporting

    If you need to uninstall the Live Reporting feature perform the following steps:

    1. Run the Live Reporting uninstallation file as an administrator.

      Microsoft Windows<yellowfin_installation_directory>\live_reporting\UninstallBMCLive_Reporting\uninstall.exe 
      Linux<yellowfin_installation_directory>/live_reporting/UninstallBMCLive_Reporting/uninstall.bin

      The first screen of the Live Reporting installation wizard appears. Click Next.

    2. Enter the BMC Server Automation database user name and password that is configured with Live Reporting.

    3. Review the information on the preview screen and click Uninstall to begin the uninstallation process.

    Where to go from here

    Using the Live Reporting dashboard
    Was this page helpful? Yes No Submitting... Thank you

    Comments

    1. Steven Green

      In the "Database server requirements" section, please include "Oracle 11g R2 RAC" and "Oracle 12c RAC". These are shown as supported for Live Reporting on the Product Availability and Compatibility (SPAC) page.

      Feb 28, 2019 12:14