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

To enable Live reporting, you must install and configure Yellowfin with BMC Server Automation. This topic describes that process, and includes the following sections:

Important

If you are on BMC Server Automation 8.9.01 or later, follow the instructions provided in Installing and configuring Yellowfin to enable Live reporting (for versions 8.9.01 and later). The new installer shipped with versions 8.9.01 and later, provides an integrated UI that takes you through the complete installation of Live reporting, which includes installing Yellowfin and performing post installation configuration.

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.


Note

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.

Yellowfin system requirements for Live Reporting

This section describes the requirements for installing and using Yellowfin 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

Java

Oracle JRE 1.6 or later

Web Application Server

Yellowfin installs standalone Apache Tomcat

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 Yellowfin 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 Yellowfin components from the Electronic Product Distribution (EPD) website:

  • Yellowfin installer
  • Post-installer utility

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

For Windows
  • Yellowfin Installer for Live Reporting (Yellowfin-71-BSA89-WIN.exe)
  • Post Installer Utility for Live Reporting (LiveReportingPostInstaller.zip)
For Linux
  • Yellowfin Installer for Live Reporting (Yellowfin-71-BSA89-LIN.jar)
  • Post Installer Utility for Live Reporting (LiveReportingPostInstaller.tar)

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 Yellowfin 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.

  • BMC recommends that you install Yellowfin 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.

Step 1: Preparing the Yellowfin database for installation

When BMC customers use Yellowfin 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.

Note

Do not use the embedded HSQL database shipped with the base Yellowfin product. This database is suitable for testing purposes only.

The database server does not have to reside on the same system as the Yellowfin application. Database preparation is fairly straightforward.

  • For Windows, you must use a MS SQL Server database. If the database and database user were manually pre-created, then provide the details in the installation steps. Otherwise, use the Yellowfin installation program to automatically create the database and database user, as shown here:

    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 Yellowfind 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
      • Select the Create new database and Create new user options to create them automatically using the Yellowfin installer. 
      • 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 Linux, you must use an Oracle database. You must manually pre-create the database user credential for the Oracle database. Unlike Windows/SQL Server, Yellowfin does not provide the option to create the default database user for the Oracle database.

    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 an Oracle database...
  1. Create a yellowfin directory with the correct permissions to store the table space. For example:

    mkdir /data1/oracle/product/databases/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 2: Installing Yellowfin

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

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

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

    Perform the following steps to install Yellowfin on your Windows host.

    1. Run the Yellowfin installation file (for example, Yellowfin-71-BSA89-WIN.exe) as administrator.
    2. Select the language with which you want to run the installer.
    3. Review the platforms, databases, and Java information and click Next.
    4. Select the I accept the terms of this license agreement option and click Next.
    5. Ensure that you have selected the Core package snapshot option, unselect Tutorial Content, and then click Next.

      Warning

      If you do not deselect Tutorial Content when installing Yellowfin, Live Reporting will not work properly.


    6. In the General Options panel, do the following:

      1. Enter the port number that you want the Yellowfin business intelligence tool to communicate. The default port number is 8080.

      2. Select the option to run Yellowfin as a Window service. The default startup type of the Yellowfin service is Manual; later you will change it to Automatic.
      3. Click Next.
         
    7. Select the appropriate option from the Type of Database field and click Next. The type of Yellowfin database must be the same as the BMC Server Automation database. For Windows, select Microsoft SQL Server. Enter the Yellowfin database details, as follows:
      1. Enter the Host name or IP address of the server running the database.
      2. Enter the port number that the database listens on. The default port is 1433 for SQL Server.
      3. Select either Default instance (shown below) or Named Instance in the instance Type field.

        If you select Named Instance, the details you must enter are slightly different. Do not enter the entire instance name, for example, <hostname>\<instancename>.
      4. Enter the name of the database instance (for example, Yellowfin) and ensure that the Create new database option is selected.
      5. For Windows, select SQL Server Authentication or Windows Authentication in the Authentication field.
        If you select Windows Authentication, specify the pre-created database, the logon domain (enter only the domain of the user account you want to log on with), and the pre-created database user, as shown in the following example:
      6. For the Database User, specify the credentials of a database user (not sa) supplied by your DBA to access the Yellowfin database. Optionally, you can select the Create new user option to create a new Yellowfin database user by the installer. 
      7. For the Administrator User, specify the credentials of an administrator user (for example, sa) who has administrator-level access to the database server in order to create the Yellowfin database, .
      8. Click Next.
    8. When you are prompted to validation the database connection, click Yes. If the connection was successful, click OK to continue.
    9. Browse and select the path (by default, C:\Users\Administrator\Yellowfin 7.1 for Windows) at which you want to install Yellowfin. Click Next.
      Selecting a path location in C:\Program Files\ requires that you always run Yellowfin as an administrator. You can also create a common path, for example, C:\Yellowfin71.

      Tip

      Enter a path without extra spaces or punctuation to avoid using an escape character to avoid errors during installation..

    10. After Yellowfin is installed on your machine, review the start and login instructions, and then click Done to close the installer.

    11. Open the Services windows and perform the following steps:

      1. Set the Startup type to Automatic.

      2. Start the Yellowfin service.
         

    12. Log on to Yellowfin (for example, http://localhost:8080/) with the required username (admin@yellowfin.com.au) and default password (test).
       

    13. Verify that you have logged in successfully.
       

    Perform the following steps to install Yellowfin on your Linux host:

    1. Verify that the Oracle database and listener are started.

    2. Run the Yellowfin installation file (for example, Yellowfin-71-BSA89-LIN.jar).
      For example:

      # java -jar Yellowfin-71-BSA89-LIN.jar
    3. Select the language with which you want to run the installer.

    4. Review the platforms, databases, and Java information and click Next.
    5. Select the I accept the terms of this license agreement option and click Next.
    6. Ensure that you have selected the Core package snapshot option, unselect Tutorial Content, and then click Next.

      Warning

      If you do not unselect Tutorial Content when installing Yellowfin, Live Reporting will not work properly.

    7. Enter the port number that you want the Yellowfin business intelligence tool to communicate on and click Next. The default port number is 8080.

    8. Select the appropriate option from the Type of Database field (for example, Oracle) and click Next. The type of Yellowfin database must be the same as the BMC Server Automation database.
    9. Enter the Yellowfin database details, as follows:
      1. Enter the Host name or IP address of the server running the database.
      2. Enter the port number that the database listens on. The default port is 1521 for Oracle Database.
      3. Enter the Oracle SID (the default) or the Oracle Service Name. This example entered ORA112DB as the Oracle SID, as defined in tnsnames.ora.
      4. Enter the database user (not system) credentials specifically created to store the Yellowfin metadata.
      5. Select Next.
    10. When you are prompted to validate the database connection, click Yes. If the connection was successful, click OK to continue.
    11. Browse and select the path (by default, /usr/local/Yellowfin 7.1 for Linux) at which you want to install Yellowfin. Click Next.

      Tip

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

    12. After Yellowfin is installed on your machine, start the Yellowfin service, before running the post installer script.

      /usr/local/Yellowfin71/appserver/bin/startup.sh

      For more information, see the Yellowfin documentation.  

    13. Log on to Yellowfin (for example, http://localhost:8080) with the required username (admin@yellowfin.com.au) and password (test).

    14. Verify that you have logged in successfully.
       

    Step 3: Enabling HTTPS in Yellowfin before post-installation

    Depending whether you are using self-signed certificates or third-party certificates, follow one of the following procedures. Because the Live Reporting integration with Yellowfin now supports only HTTPS, you must make sure that you can successfully log on to Yellowfin with the HTTPS protocol before you start post-installation.

       The following video (7:20) shows how to how to enable SSL with Yellowfin with a self-signed certificate.

        https://youtu.be/56OQbfz44ZU


      Perform the following steps to enable SSL with Yellowfin with self-signed certificates.

      Note

      • Back up your VM or your file system before you start. If you make a mistake, you can revert to a saved snapshot and try again.
      • Copy and paste the SSL commands into a text editor like Notepad, Notepad++, or TextPad, strip out the line breaks, and modify the syntax for your environment. 
      • All keystores and certificates will be stored in C:\temp.
      • The keystore password used throughout this procedure is changeit.
      • Executing a keytool command can take several minutes to complete the key generation. The key generation may delay the prompting for user input, perhaps by as long as 4-5 minutes. The delay does not indicate an issue with the tool.
      1. Unzip LiveReportingPostInstaller.zip (Window) or LiveReportingPostInstaller.tar (Linux).
        For Linux:
        tar xvf LiveReportingPostInstaller.tar 
      2. On the Yellowfin host, add JAVA_HOME/bin of the JRE shipped with the postinstaller to the beginning of the system PATH variable (for example, C:\LiveReportingPostInstaller\windows_jre\jre1.8.0_102\bin or /../linux_jre/jre1.8.0_102/bin).
        Adding JAVA_HOME/bin to the beginning of the PATH variable ensures it is used first and not some other utility on the host in the pre-existing PATH. You must perform this step to run keytool from the command prompt without having to change directories to the jre\jre1.8.0_102\bin folder.

        Important

        Ensure that you only use the JRE bundled with the post installer to avoid encountering errors later in the installation procedure.

      3. Generate a new keystore that you will use to import into the Application Server JRE cacerts.
        For example:

        keytool -genkey -alias yellowfin-server -keyalg RSA  
        -validity 365 -keypass changeit -storepass changeit
        -keystore "C:\temp\yellowfin_keystore.jks"

        Use appropriate variables for your environment.

        Note

        Whatever password you use in this step, you must use the same password when you later modify the server.xml file, for example, changeit. Otherwise, enabling HTTPS will not work.

         

        keytool -genkey -alias yellowfin-server -keyalg RSA 
           -validity 365 -keypass changeit -storepass changeit 
           -keystore "C:\temp\yellowfin_keystore.jks"
        What is your first and last name?
          [Unknown]:  clm-aus-013663.bmc.com
        What is the name of your organizational unit?
          [Unknown]:  IDD
        What is the name of your organization?
          [Unknown]:  BMC Software
        What is the name of your City or Locality?
          [Unknown]:  San Jose
        What is the name of your State or Province?
          [Unknown]:  California
        What is the two-letter country code for this unit?
          [Unknown]:  US
        Is CN=clm-aus-013663.bmc.com, OU=IDD, O=BMC Software, L=San Jose, ST=California,
         C=US correct?
          [no]:  yes

         

      4. Copy yellowfin_keystore.jks into ..\Yellowfin71\appserver\conf and rename it to tomcat.key.
        Ignore the warning that the key might now be unusable because you changed the extension.  

      5. In ..\Yellowfin71\appserver\conf, modify the server.xml and web.xml files with a good text editor.

        1. In server.xml, uncomment the SSL connector section that handles HTTPS requests.
          When you uncomment this section, Yellowfin then responds to both HTTP and HTTPS requests.

          <!-- Uncomment this for an SSL connector running on port 8443 (change
          the port as required). You will need to generate a certificate
          and save it in this directory as "tomcat.key" (change the
          keystoreFile and keystorePass values as required).
          See: http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html -->
          <!--
          <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" URIEncoding="UTF-8"
          keystoreFile="${catalina.home}/conf/tomcat.key"
          keystorePass="password"
          />
          -->
        2. Change the keystore password setting. For example:
          From:
          keystorePass="password"
          To:
          keystorePass="changeit"

        3. Save your changes in server.xml.

        4. In web.xml, add the following <security-constraint> section to the end of the file – but before the final <web-app> braces – and then save the file.
          The <security-constraint> section forces all connections to the HTTP 8080 port to the 8443 HTTPS port.

            <security-constraint>
              <web-resource-collection>
                <web-resource-name>Automatic SLL Forwarding</web-resource-name>
                <url-pattern>/*</url-pattern>
              </web-resource-collection>
              <user-data-constraint>
                <transport-guarantee>
                  CONFIDENTIAL
                </transport-guarantee>
              </user-data-constraint>
            </security-constraint>
          </web-app>

          For more information, see the Yellowfin instructions to enable Yellowfin access via HTTPS in the Yellowfin documentation.

      6. Restart the Yellowfin service to apply these changes. You might have to restart your host before Yellowfin works as expected. Make sure that the database services have started as well.

      7. Verify that you can log on to Yellowfin with an HTTPS address. 

        Tip

        Try the old HTTP URL, for example:
        http:localhost:8080

        If you correctly reconfigured Yellowfin, you are automatically redirected to the HTTPS port.


        Upon initial access, a warning about an non-trusted certificate appears (because this is a self-signed certificate, not generated by a trusted CA).

         

      8. From a command prompt, export the certificate and create a new yellowfin_server.cer file.
        For example:

        keytool -export -alias yellowfin-server -storepass changeit 
        -file "C:\temp\yellowfin_server.cer"
        -keystore "C:\temp\yellowfin_keystore.jks"


        Make sure that keytool uses the jre\bin folder that is shipped with the postinstaller.

        keytool -export -alias yellowfin-server -storepass changeit 
          -file "C:\temp\yellowfin_server.cer" 
          -keystore "C:\temp\yellowfin_keystore.jks"
        Certificate stored in file <C:\temp\yellowfin_server.cer>
      9. Import yellowfin_server.cer into your postinstaller Java cacerts keystore (for example, C:\LiveReportingPostInstaller\windows_jre\jre1.8.0_71\lib\security).

        1. Run the keytool command to import the certificate. For example:
          keytool -import -alias yellowfin-server 
          -keystore "C:\LiveReportingPostInstaller\windows_jre\jre1.8.0_102\lib\security\cacerts"
          -trustcacerts -file "C:\temp\yellowfin_server.cer"
           
        2. At the prompt, enter changeit as the default cacerts password.
        3. At the prompt to trust the certificate, enter yes.

          C:\Yellowfin\LiveReportingPostInstaller\windows_jre\jre1.8.0_102\bin>keytool  
             -import -alias yellowfin-server 
             -keystore "C:\Yellowfin\LiveReportingPostInstaller
             \windows_jre\jre1.8.0_71\lib\security\cacerts" 
             -trustcacerts -file "C:\temp\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: 21bb24d8
          Valid from: Mon May 16 12:35:58 PDT 2016 until: Tue May 16 12:35:58 PDT 2017
          Certificate fingerprints:
                   MD5:  87:0A:33:81:EC:63:A2:5F:3F:59:1C:3C:84:1D:AC:21
                   SHA1: 8C:AD:30:0A:D7:7A:6E:F2:AF:D9:C3:BF:2D:CA:83:71:DC:51:80:07
                   SHA256: C4:55:22:5D:AD:71:9A:1B:5B:07:00:1B:2A:BE:0E:B1:3C:57
                     :09:22:D0:8D:2E:F4:D3:81:29:36:13:C9:5F:7F
                   Signature algorithm name: SHA256withRSA
                   Version: 3
          Trust this certificate? [no]:  yes
          Certificate was added to keystore

           

      10.  Change over to the BSA Application Server host or hosts.

        Note

        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 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 (/opt/bmc/bladelogic/appserver/NSH/br/java/bin for Linux or C:\Program FIles\BMC Software\BladeLogic\appserver\NSH\jre\bin for Windows) and import yellowfin_server.cer into your BSA Application Server Java cacerts keystore (the default Windows path is C:\Program Files\BMC Software\BladeLogic\appserver\NSH\jre\lib\security\cacerts and the default Linux path is /opt/bmc/bladelogic/appserver/NSH/br/java/lib/security).
          For example:
          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"
           
        4. At the prompt, enter changeit as the default cacerts password.
        5. At the prompt to trust the certificate, enter yes.

          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"
          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

           

        6. After you import the certificate, restart the BSA Application Server in which the certificate is imported by performing the following steps, for example:

          On Linux:

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

          On Windows:

          Restart the BladeApp Server windows service.


      This section creates a trial third-party certificate authority (CA) – specifically, Symantec to enable HTTPS with Yellowfin. You can also use these same steps if you have already configured a self-signed certificate in your environment but now want to apply a CA to Yellowfin.

      Note

      • Back up your VM or your file system before you start. If you make a mistake, you can revert to a saved snapshot and try again.
      • Copy and paste the SSL commands into a text editor like Notepad, Notepad++, or TextPad, strip out the line breaks, and modify the syntax for your environment. 
      • The steps show the configuration steps with the Google Chrome browser. The instructions for Firefox or Internet Explorer might be different.
      • Executing a keytool command can take several minutes to complete the key generation. The key generation may delay the prompting for user input, perhaps by as long as 4-5 minutes. The delay does not indicate an issue with the tool.

       

      1. Unzip LiveReportingPostInstaller.zip (Window) or LiveReportingPostInstaller.tar (Linux).
        For Linux:
        tar xvf LiveReportingPostInstaller.tar 
      2. From the command prompt, navigate to the directory where keytool is located, for example, C:\LiveReportingPostInstaller\windows_jre\jre1.8.0_102\bin.
      3. Create the keystore and the private key (yellowfin_keystore.jks).
        A keystore holds your private and public keys. When creating a Java keystore, you create the yellowfin_keystore.jks file that at first contains only the private key This example used password as the password.

        keytool -genkey -alias yellowfin-server -keyalg RSA 
          -keystore C:\Keys\yellowfin_keystore.jks -keysize 2048
        Enter keystore password:
        Re-enter new password:
        What is your first and last name?
          [Unknown]:  vw-aus-clmidd09.bmc.com
        What is the name of your organizational unit?
          [Unknown]:  IDD
        What is the name of your organization?
          [Unknown]:  BMC Software
        What is the name of your City or Locality?
          [Unknown]:  San Jose
        What is the name of your State or Province?
          [Unknown]:  California
        What is the two-letter country code for this unit?
          [Unknown]:  US
        Is CN=vw-aus-clmidd09.bmc.com, OU=BMC Software, 
        O=IDD, L=San Jose, ST=California
        , C=US correct?
          [no]:  yes
        Enter key password for <clmui>
                (RETURN if same as keystore password):
        Re-enter new password:
      4. Create the certificate sign-in request (CSR).
        This example used password as the password.

        keytool -certreq -alias yellowfin-server 
          -file C:\Keys\yellowfin_server.csr 
          -keystore C:\Keys\yellowfin_keystore.jks -sigalg SHA1withRSA
        Enter keystore password:
      5. Send the CSR file to a CA for signing using Symantec, for example. CA returns a signed SSL certificate, for example, ssl_cert.cer.
         
      6. (optional) Download and import the Root CA certificate (for example, RootCA.cer) into the browser's trusted root store certification authorities.
        Trial versions of the Root CA certificate must be installed on each browser where you will test it. This step is not necessary with production certificates. For more information, see the Symantec documentation on using root certificates.   

        Tip

        To work as expected, you must explicitly import the Root CA certificate into the Trusted Root Certificate Authorities on the Google Chrome browser.


      7. Download and import the Root CA certificate (for example, RootCA.cer) on the product host.
        Do not mismatch the Root and intermediate CA certificates –  select the appropriate Intermediate CA certificate for your SSL Certificate type.

        keytool -import -trustcacerts -alias root 
          -keystore "C:\Keys\yellowfin_keystore.jks" 
          -file "C:\Keys\RootCA.cer"
        Enter keystore password:
        Owner: CN=VeriSign Trial Secure Server Root CA - G2, OU="For Test Purposes Only.
          No assurances.", O="VeriSign, Inc.", C=US
        Issuer: CN=VeriSign Trial Secure Server Root CA - G2, OU="For Test Purposes Only.
          No assurances.", O="VeriSign, Inc.", C=US
        Serial number: 168164a428ca12dfab12f19fb1b93554
        Valid from: Tue Mar 31 19:00:00 CDT 2009 until: Sat Mar 31 18:59:59 CDT 2029
        Certificate fingerprints:
                 MD5:  E0:19:F5:FC:C0:9A:13:0E:38:B7:BF:0D:02:40:D3:C2
                 SHA1: 51:51:B8:63:8A:4C:1F:15:54:56:ED:37:C9:10:35:CA:D3:01:B9:36
                 SHA256: 89:DD:5C:3D:FE:28:13:87:45:1F:A3:A0:F7:8C:1A:B6:77:DB
                   :18:63:9E:71:72:AD:B2:52:91:CF:BE:F7:8D:19
                 Signature algorithm name: SHA1withRSA
                 Version: 3
        Trust this certificate? [no]:  yes
        Certificate was added to keystore
        PS C:\LiveReportingPostInstaller\windows_jre\jre1.8.0_102\bin> 
      8. Download and import the intermediate certificate (for example, intermediate.cer) on the product host.
        Do not mismatch the Root and intermediate CA certificates –  select the appropriate Intermediate CA certificate for your SSL Certificate type.

        keytool -import -trustcacerts -alias Intermediate 
          -keystore C:\Keys\yellowfin_keystore.jks 
          -file C:\Keys\intermediate.cer 
        Enter keystore password:
        Certificate was added to keystore
        PS C:\LiveReportingPostInstaller\windows_jre\jre1.8.0_102\bin>
      9. Install the SSL certificate (for example, ssl_cert.cer) on the product host.
        The alias name in this command must be the same as the alias name used during the generation of the private key and CSR, for example, yellowfin-server.

        keytool -import -trustcacerts -alias yellowfin-server 
          -keystore "C:\Keys\yellowfin_keystore.jks" 
          -file "C:\Keys\ssl_cert.cer"
        Enter keystore password:
        Certificate reply was installed in keystore
        PS C:\Yellowfin\LiveReportingPostInstaller\windows_jre\jre1.8.0_71\bin>

         

      10. Verify the contents of the keystore that the SSL certificate is imported into the alias with the "Entry Type" of PrivateKeyEntry or KeyEntry.  
        For example:

        keytool -list -v -keystore "C:\Keys\yellowfin_keystore.jks"
          > C:\Keys\output_filename.txt
        Enter keystore password:

         

      11. Copy yellowfin_keystore.jks into ..\Yellowfin 7.1\appserver\conf and rename it to tomcat.key.
      12. In ..\Yellowfin71\appserver\conf, modify the server.xml and web.xml files with a good text editor.

        1. In server.xml, uncomment the SSL connector section that handles HTTPS requests.
          When you uncomment this section, Yellowfin then responds to both HTTP and HTTPS requests.

          <!-- Uncomment this for an SSL connector running on port 8443 (change
          the port as required). You will need to generate a certificate
          and save it in this directory as "tomcat.key" (change the
          keystoreFile and keystorePass values as required).
          See: http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html -->
          <!--
          <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" URIEncoding="UTF-8"
          keystoreFile="${catalina.home}/conf/tomcat.key"
          keystorePass="password"
          />
          -->
        2. Change the keystore password setting. For example:
          From:
          keystorePass="password" 
          To:
          keystorePass="changeit"

        3. Save your changes in server.xml.

        4. In web.xml, add the following <security-constraint> section to the end of the file – but before the final <web-app> braces and then save the file.
          The <security-constraint> section forces all connections to the HTTP 8080 port to the 8443 HTTPS port.

            <security-constraint>
              <web-resource-collection>
                <web-resource-name>Automatic SLL Forwarding</web-resource-name>
                <url-pattern>/*</url-pattern>
              </web-resource-collection>
              <user-data-constraint>
                <transport-guarantee>
                  CONFIDENTIAL
                </transport-guarantee>
              </user-data-constraint>
            </security-constraint>
          </web-app> 

          For more information, see the Yellowfin instructions to enable Yellowfin access via HTTPS in the Yellowfin documentation. 

      13. Restart the Yellowfin service to apply these changes. You might have to restart your host before Yellowfin works as expected. Make sure that the database services have started as well.

      14. Verify that you can log on to Yellowfin with the fully-qualified HTTPS address.
        If you correctly installed the third-party certificate, you are automatically redirected to the HTTPS port. You should not see a warning about using a non-trusted certificate (because you are using a trusted CA). 

        Note

        The default localhost URL no longer works with a third-party certificate, for example:
        http:localhost:8080

         

         

         

      15. (optional) Click the green lock in the URL to review the certificate chain in the browser.
         

      16. From a command prompt, export the certificate and create a new yellowfin_server.cer file.
        Make sure that you use the jre\bin folder that is shipped with the postinstaller.

        keytool -export -alias yellowfin-server -storepass password 
          -file "C:\Keys\yellowfin_server.cer" 
          -keystore "C:\Keys\yellowfin_keystore.jks"
        Certificate stored in file <C:\temp\yellowfin_server.cer>

         

      17. Import yellowfin_server.cer into your postinstaller Java cacerts keystore (for example, C:\Yellowfin\LiveReportingPostInstaller\windows_jre\jre1.8.0_71\lib\security).

        1. Run the keytool command from the jre\bin installed with the postinstaller (C:\Yellowfin\LiveReportingPostInstaller\windows_jre\jre1.8.0_71\bin for Windows). 
        2. At the prompt, enter changeit as the default cacerts password.
        3. At the prompt to trust the certificate, enter yes.

          keytool -import -alias yellowfin-server 
            -keystore "C:\Yellowfin\LiveReportingPostInstaller
            \windows_jre\jre1.8.0_71\lib\security\cacerts" 
            -trustcacerts -file "C:\Keys\yellowfin_server.cer"
          Enter keystore password:
          Owner: CN=clm-aus-016971.bmc.com, OU=IDD, 
            O=BMC Software, L=San Jose, ST=California, C=US
          Issuer: CN=Symantec Trial Secure Server CA - G3, 
            OU="For Test Purposes Only.  No assurances.", 
            O=Symantec Corporation, C=US
          Serial number: 65196973a41fdee79ae1ceb48c5b398d
          Valid from: Mon Sep 12 12:00:00 GMT-12:00 2016 
            until: Thu Oct 13 11:59:59 GMT-12:00 2016
          Certificate fingerprints:
                   MD5c:  6E:E7:08:88:49:87:FE:FC:AC:2F:8A:BD:55:C1:E8:DB
                   SHA1: 3E:99:65:AD:E6:DF:63:BD:65:0D:B5:64:99:9B:97:DB:F9:C0:66:62
                   SHA256: 79:D4:A8:7E:E9:21:CF:22:4D:3A:FF:89:74:6D:43:2E:30:60
                     :C1:69:DB:F0:CF:51:F4:2F:88:13:56:05:F1:26
                   Signature algorithm name: SHA256withRSA
                   Version: 3
          Trust this certificate? [no]:  yes
          Certificate was added to keystore

           

      18. Change over to the BMC Server Automation Application Server host or hosts.

        Note

        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 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 (/opt/bmc/bladelogic/appserver/NSH/br/java/bin for Linux or C:\Program FIles\BMC Software\BladeLogic\appserver\NSH\jre\bin for Windows) and import yellowfin_server.cer into your BSA Application Server Java cacerts keystore (the default Windows path is C:\Program Files\BMC Software\BladeLogic\appserver\NSH\jre\lib\security\cacerts and the default Linux path is /opt/bmc/bladelogic/appserver/NSH/br/java/lib/security).
        4. At the prompt, enter changeit as the default cacerts password.
        5. At the prompt to trust the certificate, enter yes.

          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"
          Enter keystore password:
          Owner: CN=clm-aus-016971.bmc.com, OU=IDD, O=BMC Software, 
            L=San Jose, ST=California, C=US
          Issuer: CN=Symantec Trial Secure Server CA - G3, 
            OU="For Test Purposes Only.  No assurances.", 
            O=Symantec Corporation, C=US
          Serial number: 65196973a41fdee79ae1ceb48c5b398d
          Valid from: Mon Sep 12 12:00:00 GMT-12:00 2016 
            until: Thu Oct 13 11:59:59 GMT-12:00 2016
          Certificate fingerprints:
                   MD5:  6E:E7:08:88:49:87:FE:FC:AC:2F:8A:BD:55:C1:E8:DB
                   SHA1: 3E:99:65:AD:E6:DF:63:BD:65:0D:B5:64:99:9B:97:DB:F9:C0:66:62
                   SHA256: 79:D4:A8:7E:E9:21:CF:22:4D:3A:FF:89:74:6D:43:2E:30:60
                     :C1:69:DB:F0:CF:51:F4:2F:88:13:56:05:F1:26
                   Signature algorithm name: SHA256withRSA
                   Version: 3
          Trust this certificate? [no]:  yes
          Certificate was added to keystore

           

        6. After you import the certificate, restart the BSA Application Server host.

        7. When the app server restarts, make sure that the BSA Application Server is started.

       

      Step 4: Configuring Yellowfin to use BMC Server Automation

      Depending on which operating system you installed Yellowfin on, follow either of the following procedures to configure Yellowfin with BMC Server Automation.

      Note

       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 following video shows how to configure YellowFin 7.1 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
          4. Verify that the postinstaller script works by logging on to Yellowfin 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. 

             

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

        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. 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
          4. Verify that the postinstaller script works by logging on to Yellowfin 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. 
          5. After you save your changes, review the default page.

        Tip

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

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


         

        Step 5: 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 6: 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 7: 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 8: 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:

        1. Log on to Yellowfin using the REPORT_ADMIN user.
        2. Select Administration > Admin Console
        3. Select Data Sources.
           
        4. Edit the BSA data source.
        5. Click the first tab:
          1. Update the region and time zone as needed.
          2. Test the database connection and make sure that it succeeds. 
             
          3. Click Save
        6. Click the second tab.
        7. For each filter, do the following:
          1. Click the filter link, for example, ROLE FOR DEPLOY.
          2. Select Refresh filter when new users are created.

          3. Select Refresh this filter now
          4. Save the changes, and repeat for each filter.
        8. To update the server group list (static groups or smart groups) to ensure that the Cohort Analysis views will work properly, perform the following steps:
          1. Run the following BLCLI command:
            blcli -v defaultProfile Utility populateServerGrpforLiveReporting 
          2. When you launch the Live Reporting dashboard, check the Server Group drop-down list in the Filters section, and ensure that the list reflects the appropriate server groups.

        Uninstalling Yellowfin

        You might need to uninstall Yellowfin and start over if you made a mistake, for example, you didn't unselect Tutorial Content during installation. 

          This is a three-step process – remove the Yellowfin/Tomcat service, run the Yellowfin uninstaller, and then delete the Yellowfin instance from the database. 

          1. Navigate to the directory in which Yellowfin is installed. By default, this directory is C:\Users\Administrator\Yellowfin 7.1 for Windows.
          2. Delete the Tomcat service.
            1. Open a command prompt.
            2. Navigate to the \<Yellowfin_install_directory>\appserver\bin folder where the Tomcat files are located. 
            3. Run the following command:
              service remove Yellowfin 
              This command deletes the Yellowfin service and the associated Tomcat files. 
          3. Change directories to the <Yellowfin_install_directory>\Uninstallerfolder. 
          4. Double-click uninstaller.jar
          5. When the Uninstaller starts:
            1. Choose the option to force delete the installed directory, as shown below. 

              Note

              The uninstaller does not remove the database artifacts. 
            2. Click Uninstall
          6. When the uninstallation is finished, click Quit to close the uninstaller. 
          7. Manually delete the Yellowfin folder. This action is safe because there are no remaining artifacts left, only some empty folders. 
          8. Manually delete the Yellowfin database instance when you are finished. Do not leave any remaining artifacts in your environment, especially if you plan to re-install Yellowfin. 

          This is a three-step process – stop the Yellowfin server, run the Yellowfin uninstaller, and then delete the Yellowfin instance from the database. 

          1. Navigate to the directory in which Yellowfin is installed. By default, this directory is /usr/local/Yellowfin 7.1 for Linux.
          2. Stop the Yellowfin server so that you don't leave Tomcat processes lingering after the uninstallation is finished.
            1. Open a command prompt.
            2. Check if there are any running Tomcat processes:
              ps -ef | grep tomcat 
            3. Navigate to the /<Yellowfin_install_directory>/appserver/bin folder where the Tomcat files are located. 
            4. Stop Yellowfin.
              ./shutdown.sh
            5. Verify that the Tomcat processes are stopped.
              ps -ef | grep tomcat 
          3. Change directories to the <Yellowfin_install_directory>/Uninstaller folder. 
          4. Run the Java uninstaller:
            java -jar uninstaller.jar 
          5. When the Uninstaller starts:
            1. Choose the option to force delete the installed directory, as shown below. 

              Note

              The uninstaller does not remove the database artifacts. 
            2. Click Uninstall
          6. When the uninstallation is finished, click Quit to close the uninstaller. The uninstaller deletes the /usr/local/Yellowfin_install_directory folder. 
          7. Manually delete the Yellowfin database instance when you are finished. Do not leave any remaining artifacts in your environment, especially if you plan to re-install Yellowfin. 

          Where to go from here


          Using the Live Reporting dashboard


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

          Comments