Prerequisites

  • Determine whether you need a SolutionPack license file by checking the feature names and expiration dates listed in Centralized Management > License Management. If the license is not listed, obtain one by completing a Support Request (SR) form, which you can find on the support website.
  • Ensure the core modules, such as the Module-Manager, are up-to-date on all servers since not all module dependencies are validated during the SolutionPack installation. See the Service Assurance Suite Installation and Configuration Guide for M&R for more information.
  • Ensure you have installed and configured the Presentation Service Assurance Manager (SAM) server with Notification Cache Publishing enabled.
  • Ensure you have enabled security settings to allow interoperability with M&R by setting these flags in the runcmd_env.sh file:
    Table 1. Security settings for the SAM runcmd_env.sh file
    Flag Value
    SM_ALLOW_LEGACY_CRYPTO= TRUE
    SM_TLS_PROTOCOLS= +TLSv1.1
  • Ensure these services associated with the Presentation SAM installation are running:
    Table 2. SAM services when Notification Cache Publishing is enabled
    Service name Description of feature
    ic-broker Broker connected to Presentation SAM server
    ic-sam-server-pres Presentation SAM with Notification Cache Publishing
    smarts-tomcat Smarts EDAA and Notification Cache (hosted by Tomcat server)
    smarts-rabbitmq Notification Exchange (Rabbit MQ)
    smarts-elasticsearch Storage/Search engine used by the Notification Cache
  • Obtain the login credentials and the Fully Qualified Domain Names (FQDN) for the servers where Smarts Broker, Smarts EDAA, and Presentation SAM servers are running.
  • Review the article, How to Set Up SAM, M&R, and the SolutionPack for Smarts, for additional configuration procedures.
  • Review the article, How to Set Up SAM, M&R, and the SolutionPack for Smarts, for additional configuration procedures.

Follow these steps to install the SolutionPack for Smarts.

Procedure

  1. Log in to Administration > Centralized Management.
  2. Select SOLUTIONPACK CENTER.
  3. Select SolutionPack for Smarts in the Browse and Install SolutionPacks window.
  4. Read the summary information and click Install.
  5. Accept the default instance name or type a new name.
    One SolutionPack for Smarts instance may be configured for each Presentation SAM server.
  6. Select which server each component will be installed on.

    The recommended servers are:

    • Data Collection--Collector
    • Events--Primary Backend
    • Reports--Front End
  7. Click Next and complete the field entries for the Data collection, Database, Events, and Reports screens.
    Click the question mark icon to access field-level help. (Actual screens and version numbers will vary from the examples shown in this article.)
  8. Click Install after you complete the last screen.
    The installation process begins.
  9. Select the maximize arrow next to each component to view the installation process.
    When the installation successfully completes, green checkmarks appear.
  10. After installation is complete, select Centralized Management > SolutionPack to verify the installed SolutionPack.
  11. Restart the Presentation SAM services.
    This step is important because the SAM server may have an existing entry in the runcmd_env.sh file that points to a previous CAS configuration. Restarting the Presentation SAM services forces the CAS webapp to run with the latest configuration.

What to do next

Perform these post-installation tasks: