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.

Upgrading Yellowfin for Live Reporting

This section describes how to upgrade Yellowfin with the latest patch to use the latest Live Reporting dashboards that displays complete live data from your database about the status of your patch, compliance, and job activities in your environment. 

Before you begin

  1. Make sure that your Yellowfin environment is working properly. Review the Live Reporting dashboard and verify that the expected data is currently displayed. 
  2. Back up the Yellowfin database.
  3. On the BladeLogic Application Servers, back up the cacerts file (for example,<Installed_directory>/appserver/NSH/br/java/lib/security for Linux or <Installed_directory>\appserver\NSH\jre\lib\security for Windows) to a separate safe location. You must do this because sometimes the BladeLogic upgrade overwrites the existing cacerts and you won't be able to launch the Live Reporting dashboard from the console. 
  4. Upgrade the BladeLogic Application Server to the latest version. Make sure that you are using the certified and corresponding versions of both BladeLogic and Yellowfin. For more information, see:
  5. Install or upgrade the BMC Server Automation Console to the latest version. For more information, see Installing the BMC Server Automation Console (Linux and UNIX) or Installing the BMC Server Automation Console and Network Shell (Windows).

    Note

    Starting with the 8.9 installer, you don't have to install the BMC Server Automation Console on the same machine as the BladeLogic Application Server. For the Yellowfin upgrade, you simply need the latest version of the Console installed somewhere in your environment. 
  6. Enable HTTPS in Yellowfin if you haven't done so already. You must make sure that you can successfully log on to Yellowfin with the HTTPS protocol before you start postinstallation. The post-installer script does not accept HTTP. 
    For more information, use the Yellowfin instructions to enable Yellowfin access via HTTPS and carefully modify the server.xml andweb.xml files.

Downloading the installation files

Download and extract the Yellowfin components from the Electronic Product Distribution (EPD) website:

  • Yellowfin upgrade installer
  • Post-installer utility

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

For Windows
  • Yellowfin Upgrade Installer for Live Reporting (Yellowfin-71-BSA<version>-WIN-Upgrade.exe)
  • Post Installer Utility for Live Reporting (LiveReportingPostInstaller.zip)
For Linux
  • Yellowfin Upgrade Installer for Live Reporting (Yellowfin-71-BSA<version>-LIN-Upgrade.jar)
  • Post Installer Utility for Live Reporting (LiveReportingPostInstaller.tar)

To upgrade Yellowfin

    1. Run the Yellowfin installation file (for example, Yellowfin-71-BSA89-WIN-Upgrade.exe).
    2. When the opening panel is displayed, click Next.
    3. Select the I accept the terms of this license agreement option and click Next.
    4. When the Yellowfin patch panel is displayed, perform the following pre-upgrade steps:
      1. Stop the Yellowfin service.
      2. Back up the Yellowfin database.
      3. Browse to the directory where you originally installed Yellowfin (by default, C:\Users\Administrator\Yellowfin 7.1 for Windows).
      4. Click Next to immediately start the upgrade process! 
    5. Click Done to close the installer.

    6. Manually start the Yellowfin service. 
    7. Log on to Yellowfin (for example, https://localhost:8443/) with the REPORT_ADMIN login and password.

    8. Verify that you have logged in successfully.
      If so, you have successfully upgraded Yellowfin with the latest 7.1 patch.  
    1. Verify that the Oracle database and listener are started.
    2. Run the Yellowfin installation file (for example, Yellowfin-71-BSA89-LIN-Upgrade.jar).
      For example:

      # java -jar Yellowfin-71-Lin.jar
    3. When the opening panel is displayed, click Next.
    4. Select the I accept the terms of this license agreement option and click Next.
    5. When the Yellowfin patch panel is displayed, perform the following pre-upgrade steps:
      1. Stop the Yellowfin service.
        For example:

        # /usr/local/Yellowfin71/appserver/bin/shutdown.sh
      2. Back up the Yellowfin database.
      3. Browse to the directory where you originally installed Yellowfin (by default, /usr/local/Yellowfin71 for Linux).
      4. Click Next to immediately start the upgrade process! 
    6. Click Done to close the installer.

    7. Manually re-start the Yellowfin service. 

      # /usr/local/Yellowfin71/appserver/bin/startup.sh
    8. Log on to Yellowfin (for example, https://localhost:8443/) with the REPORT_ADMIN login and password.

    9. Verify that you have logged in successfully.
      If so, you have successfully upgraded Yellowfin with the latest 7.1 patch.  

    To generate new keystores before postinstallation

      These steps describe how to generate new keystores to use with the Yellowfin upgrade. You must make sure that you can successfully log on to Yellowfin with the HTTPS protocol before you start postinstallation.

      1. Download LiveReportingPostInstaller.zip to the same host where the Yellowfin server is installed.
      2. Unzip LiveReportingPostInstaller.zip (Window) into a new directory (for example, C:\YellowfinUpgrade\LiveReportingPostInstaller\).
      3. On the Yellowfin host, add JAVA_HOME/bin of the JRE shipped with the new postinstaller to the system PATH variable (for example, C:\postinstaller\LiveReportingPostInstaller\windows_jre\jre1.8.0_71\bin).
        You perform this step to run genkey from the command prompt without having to change directories to the jre\jre1.8.0_71\bin folder.
      4. Create a new folder (for example, yellowfin_cert_upgrade).

      5. Generate a new keystore that you will use to import into the Application Server JRE cacerts, as shown in the following example:
        Use appropriate variables for your environment.

        Note

        In the following example, -keypass password is actually a literal. If you use a different password here, you must use the same password when you modify the server.xml file. Otherwise, enabling HTTPS will not work.

         

        keytool -genkey -alias yellowfin-server -keyalg RSA -validity 365 -keypass password -storepass password -keystore "C:\yellowfin_cert_upgrade\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


         

      6. Go to the ..\Yellowfin 7.1\appserver\conf directory and back up the previous version of tomcat.key.
        For example, rename it to tomcat_old.key
      7. Copy the new version of yellowfin_keystore.jks into ..\Yellowfin 7.1\appserver\conf and rename it to tomcat.key.
      8. 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.

      9. 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).
         

      10. 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 new postinstaller.

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

         

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

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

          C:\YellowfinUpgrade\LiveReportingPostInstaller\windows_jre\jre1.8.0_71\bin>keytool -import -alias yellowfin-server -keystore "C:\YellowfinUpgrade\LiveReportingPostInstaller\windows_jre\jre1.8.0_71\lib\security\cacerts" -trustcacerts -file "C:\yellowfin_cert_upgrade\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

           

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

        Note

        You must re-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 the new 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 upgraded with the BSA Application Server (for example, 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).
        4. At the prompt, enter changeit as the 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

           

      13. After you import the certificate, restart the BSA Application Server service in which the certificate is imported.

      These steps describe how to generate new keystores to use with the Yellowfin upgrade. You must make sure that you can successfully log on to Yellowfin with the HTTPS protocol before you start postinstallation.

      1. Create a new directory for the postinstallation files (for example, /data1/LiveReportingUpgrade).
      2. Download LiveReportingPostInstaller.tar to the same host where the Yellowfin server is installed.
      3. Unzip LiveReportingPostInstaller.tar (Linux) into a new directory.
        For Linux:
        tar -xvf LiveReportingPostInstaller.tar -C /data1/LiveReportingUpgrade
      4. On the Yellowfin host, add JAVA_HOME/bin of the JRE shipped with the postinstaller to the system PATH variable (for example, /../linux_jre/jre1.8.0_71/bin).
        You perform this step to run genkey from the command prompt without having to change directories to the /../linux_jre/jre1.8.0_71/bin folder.
      5. Create a new folder (for example, /data1/yellowfin_cert_upgrade).

      6. Generate a new keystore that you will use to import into the Application Server JRE cacerts, as shown in the following example:
        Use appropriate variables for your environment.

        Note

        In the following example, -keypass password is actually a literal. If you use a different password here, you must use the same password when you modify the server.xml file. Otherwise, enabling HTTPS will not work.

         

        keytool -genkey -alias yellowfin-server -keyalg RSA -validity 365 -keypass password -storepass password -keystore /data1/yellowfin_cert_upgrade/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


      7. Go to the /usr/local/Yellowfin 7.1/appserver/conf directory (the default location) and back up the previous version of tomcat.key.
        For example, rename it to tomcat_old.key
      8. Copy yellowfin_keystore.jks into /usr/local/Yellowfin 7.1/appserver/conf and rename it to tomcat.key.
      9. 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.

      10. 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).
         

      11. 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 new postinstaller.

        keytool -export -alias yellowfin-server -storepass password -file /data1/yellowfin_cert_upgrade/yellowfin_server.cer -keystore data1/yellowfin_cert_upgrade/yellowfin_keystore.jks
        Certificate stored in file </data1/yellowfin_cert_upgrade/yellowfin_server.cer>

         

      12. Import yellowfin_server.cer into your new postinstaller Java cacerts keystore (for example, /data1/LiveReportingPostInstaller/linux_jre/jre1.8.0_71/lib/security). 

        1. Run the keytool command from the jre/bin installed with the postinstaller (/data1/LiveReportingPostInstaller/linux_jre/jre1.8.0_71/bin for Linux). 
        2. At the prompt, enter changeit as the password.
        3. At the prompt to trust the certificate, enter yes.

          keytool -import -alias yellowfin-server -keystore /data1/LiveReportingPostInstaller/linux_jre/jre1.8.0_71/lib/security/cacerts -trustcacerts -file /data1/yellowfin_cert_upgrade\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

           

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

        Note

        You must re-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 the new 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) 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 password.
        5. At the prompt to trust the certificate, enter yes.

          keytool -import -alias yellowfin-server -keystore /opt/bmc/bladelogic/appserver/NSH/br/java/lib/security/cacerts" -trustcacerts -file /tmp/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

           

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


      To run the postinstaller to upgrade the Live Reporting dashboard

       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. Perform the following steps:

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

        2. 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
        3. Execute the Yellowfin postinstaller.bat script (Windows), and provide the following inputs when prompted by the script:
          1. Enter the BSA BLADELOGIC database user password when prompted by the script.

          2. Enter the default password for REPORT_ADMIN, when you are prompted by the script. 
            The script then upgrades the Yellowfin contents and assigns the dashboard to the proper group. 
             

          3. After the post-installer runs successfully, verify that the REPORT_ADMIN user can login successfully. 
          4. (optional) Update any details for the REPORT_ADMIN profile (for example, update and confirm your password) and save your changes. 
          5. After you save your changes, review the default page.

        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. Change directories to the appropriate Yellowfin post-installer package on the same machine where the Yellowfin server is installed. 

        2. 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 the 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 an Oracle database.
          bsa_db_orcl_connection_method(SID/Service)
          Enter SID or Service as defined in the tnsnames.ora file.
          bsa_db_oracle_sid
          Enter the SID or Service that is defined in the tnsnames.ora file, for example, ORA112DB.
          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, for example, /usr/local/Yellowfin71. NOTE: For Linux, add a backslash "\" before the space if a space is present in the installation path. For example: /usr/local/Yellowfin\ 7.1
          Click Expand source to see a sample property file
        3. Execute the Yellowfin postinstaller.sh script (Linux), and provide the following inputs when prompted by the script:
          1. Enter the BSA BLADELOGIC database user password when prompted by the script.

          2. Enter the default password for REPORT_ADMIN, when you are prompted by the script. 
            The script then upgrades the Yellowfin contents and assigns the dashboard to the proper group. 
             

          3. After the post-installer runs successfully, verify that the REPORT_ADMIN user can login successfully.
          4. (optional) Update any details for the REPORT_ADMIN profile (for example, update and confirm your password) and save your changes. 
          5. After you save your changes, review the default page.

        To add dashboards to Live Reporting after you finish upgrading

        After you finish upgrading BladeLogic Server Automation and Yellowfin, the new reports are upgraded but your users might not immediately see the new Compliance or Job Activity dashboards. Use the following steps to add the missing dashboards to Live Reporting.

        Note

        Before you begin, it is recommended that you install the latest version of the BMC Server Automation Console. For more information, see Installing the BMC Server Automation Console (Linux and UNIX).

        If you want to continue using the version 8.8 console, follow the steps described in the "Backward support for earlier client version obviates need for upgrade" section on the 8.9.00 enhancements and updates topic.

        1. Log on to the BladeLogic console as an authorized user (for example, BLAdmin).
        2. Select Configuration > Live Reporting to open Yellowfin. 
        3. Click Browse
           
        4. From the search option, select Dashboards
          The upgraded dashboards are displayed.
           
        5. Click Compliance.
          The Compliance dashboard is then added to Live Reporting. 
           
        6. Click Add so that the Compliance dashboard is permanently embedded in Live Reporting. 
        7. Repeat the steps to add the Job Activity and Patch dashboards. 
          When you finish, all three dashboards are added to Live Reporting.
           

        To authorize users in Yellowfin after upgrading

        After you finish upgrading BladeLogic Server Automation and Yellowfin, your users might not be authorized to see the new dashboards. Use the following steps to update the authorized users and roles.

        1. Log on to Yellowfin with your REPORT_ADMIN credentials.
        2. Select AdministrationAdmin Console.
        3. Select User Groups > LiveReportingGRP, and then click Add.
           
        4. Fill out the Group Details and dashboard tabs.
          1. Create a name and description.
          2. Set Group Status to Active.
          3. (optional) Set Group Security to Secure
          4. Add all three dashboards.
             
        5. In Member Selection, click Search.
        6. Select People Only.
           
        7. Click the user that you want to add to the user group (for example, BLAdmin and REPORT_ADMIN).
           
        8. Review the members and then click Save.
           
        9. Review the updated user groups. 
           

        After you upgrade

        After you upgrade Yellowfin with the latest patch:

        1. Log on to the BladeLogic console as an authorized user (for example, BLAdmin).
        2. Select Configuration > Live Reporting to open Yellowfin. 
        3. Review the Live Reporting dashboards.
        4. Test the database connection to make sure that Yellowfin is properly connected to the BladeLogic database. 
        5. Refresh the filters and save your changes. 

        Where to go from here

        Using the Live Reporting dashboard

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

        Comments