Installing Predictive Insights on a single server

Installing all the Predictive Insights components on one server.

1. Log in as the appropriate user and do the following:
   1. Open an xterm window on the server on which you are installing Predictive Insights.
   2. Navigate to the directory that contains the extracted Predictive Insights installation package.
   3. Change to the predictiveInsightsInstaller1.3.6 directory.
   4. Enter the command ./install.sh.

      The IBM Installation Manager is opened.

   5. Click the Install option.

      The IBM Installation Manager displays the local installation packages.

   6. Select IBM Predictive Insights and click Next.
   7. On the Licenses page, read the license agreements for Predictive Insights. If you agree to the terms of all the license agreements, click I accept the terms in the license agreements and then click Next.
   8. On the Location page, in the shared Resources Directory field, type the path for the shared directory. The suggested default directory is /opt/IBM/scanalytics/install_<user>/shared.

      The IBM Installation Manager provides the ability to share components across products. Predictive Insights does not share components with any other product. It is a requirement of the IBM Installation Manager that a shared directory be provided when you install it. The shared directory must be unique for each user who installs the IBM Installation Manager on the same server.

   9. Click Next.
   10. On the Location page, Create a new package group is the only available option for Predictive Insights.

       In the Installation Directory field, type the path for the installation files. We suggest using default directory of /opt/IBM/scanalytics/install_<user>/installer and then click Next.

       If you choose to change Installation Directory from the default, note that the Installation Directory must be unique for each user who installs the IBM Installation Manager on the same server.

       The IBM Installation Manager displays all Predictive Insights components that can be installed.

2. If you are installing all components under the same user account, on the same server, you need to:
   1. Use the Install option in Installation Manager to install only the Database component.
   2. Perform the steps to get the SYSTOOLSPACE tablespace created. Click Installing the Database component and see step 17 for more information.
   3. Use the Modify option in Installation Manager to add the Analytics, Mediation tool, and UI components to the installation.
   If you want to use different user accounts to install components, select the component(s) you want to install under the current user account, note that the Database component must be selected on it's own and it must be followed by the steps to get the SYSTOOLSPACE tablespace created. Click Next. The IBM Installation Manager displays each distinct set of required information under a heading.
3. At Database configuration, enter the required information.

   Note the following points:

   • Update to create DB on a specific location: Optional setting by which you can specify an install location for the database that is not the default Db2 location. The directory must exist and be owned by the Db2 instance user.
4. Click Validate to confirm all settings are correct.
5. Click Analytics configuration and enter the required information.

   One of the required information items is a new topic name. The topic name must be one word consisting of alphanumeric characters, the underscore character can also be used, that is, '_', and the name must be between 3 and 10 characters long.#

   You must deploy each model that you create to a topic. Topics allow you to segment your data in ways that are relevant to your business. For example, you can use a topic to group data that originates from a specific service, application, or geography. The anomalies generated based on your data can then be grouped and displayed by topic.

6. Click Validate to confirm all settings are correct.
7. If you want to integrate Predictive Insights with OMNIbus, click Omnibus connection configuration and enter the required information.
   Note: If you have a multi-tiered OMNIbus environment, for example, a collection ObjectServer, an aggregation ObjectServer, and a display ObjectServers, you can configure alarm forwarding to any one of these ObjectServers during the installation. After you complete the installation, and before extracting any data, you must run the configure_omnibus command against each ObjectServer in the environment.

   For more information, see Configuring alarm forwarding from the Analytics server to an OMNIbus ObjectServer.

   If the OMNIbus ObjectServer requires a Secure Sockets Layer (SSL) connection, you must specify the directory path to ObjectServer's SSL certificate.
8. Click Validate to confirm all settings are correct.
9. Click UI configuration.

   You must select the IBM Dashboard Application Services Hub (DASH) application to display anomalies generated by Predictive Insights:

   When you select the Dashboard Application Services Hub (DASH) option you must also enter UI WebGUI configuration details, and UI local configuration details. The majority of items are populated by default, but you should note the following:

   • Enter DASH profile user/password: This must be populated by the user profile you created when installing Dashboard Application Services Hub.
   • Enter single sign on key file password: If you have configured single sign on (SSO) for the IBM WebSphere server on which Dashboard Application Services Hub is installed, enter the keyfile password used when SSO was configured. If SSO has never been configured previously, then specify a new password and note for any possible future configuration.
   • Enter single sign-in domain: This entry allows the installer to validate that both the UI component (for Dashboard Application Services Hub) and the Dashboard Application Services Hub itself are on servers that are in the same domain.
   • UI WebGUI Config: Populate Enter WebGUI user with the user details of the user that installed WebGUI, this is a user that has administrative access to WebGUI. Populate Enter OMNIbus user with the user details of the user that installed OMNIbus.
     Note: If you specify a WebGUI user other than ncoadmin, ensure that the particular user exists in Omnibus and has appropriate access before you proceed with the UI installation. If the WebGUI user does not exist in Omnibus, the installation of Dashboard Application Services Hub fails.
10. Click Validate to confirm all settings are correct.
11. Click Mediation tool configuration and enter the required information.
12. Click Validate to confirm all settings are correct.
13. Click Next.
    The IBM Installation Manager displays the installation summary information.
14. Click Install.
    Note: If you chose not to install all components under the current logged in user account, in step 2, you must repeat this procedure to install each remaining component under the desired user account.