IBM 1.3.3 Operations Analytics - Predictive Insights Installation Guide

IBM Operations Analytics - Predictive Insights 1.3.3

Installation Guide

IBM

Note

Before using this information and the product it supports, read the information in “Notices” on page 55.

© Copyright IBM Corporation 2011, 2015.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . v

Audience .

.

.

.

.

.

.

.

.

.

.

.

.

.

. v

Components .

.

.

.

.

.

.

.

.

.

.

.

.

. v

Chapter 1. Introduction . . . . . . . . 1

Chapter 2. Preparing to install . . . . . 3

Checking the installation prerequisites

.

.

.

.

. 3

Adding the required users .

.

.

.

.

.

.

.

.

. 4

Configuring fully qualified domain names for servers 5

Setting ulimits .

.

.

.

.

.

.

.

.

.

.

.

.

. 6

Installing KSH and required libraries for Operations

Analytics - Predictive Insights .

.

.

.

.

.

.

. 6

Installing the prerequisite software .

.

.

.

.

.

. 7

DB2 .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 8

InfoSphere Streams .

.

.

.

.

.

.

.

.

.

. 15

Jazz for Service Management .

.

.

.

.

.

. 19

Netcool/OMNIbus .

.

.

.

.

.

.

.

.

.

. 21

Chapter 3. Installing Operations

Analytics - Predictive Insights. . . . . 27

Selecting user accounts to install components .

.

. 27

Creating the installation directory .

.

.

.

.

.

. 27

Setting the JAVA_HOME variable .

.

.

.

.

.

. 28

Installing Operations Analytics - Predictive Insights on a single server .

.

.

.

.

.

.

.

.

.

.

. 28

Installing Operations Analytics - Predictive Insights on multiple servers .

.

.

.

.

.

.

.

.

.

.

. 31

Installation order for a distributed installation .

. 31

GUI installation .

.

.

.

.

.

.

.

.

.

.

. 32

Console Installation.

.

.

.

.

.

.

.

.

.

. 40

Post-installation - System status .

.

.

.

.

.

. 46

Installing the Mediation tool on Windows .

.

.

. 47

What to do next .

.

.

.

.

.

.

.

.

.

.

.

. 48

Chapter 4. Uninstalling Operations

Analytics - Predictive Insights. . . . . 49

Uninstalling Operations Analytics - Predictive

Insights.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 49

Chapter 5. Moving from Tivoli

Integrated Portal to Dashboard

Application Services Hub. . . . . . . 51

Chapter 6. Installation log files . . . . 53

Notices . . . . . . . . . . . . . . 55

Trademarks. . . . . . . . . . . . . 59

© Copyright IBM Corp. 2011, 2015

iii

iv

IBM Operations Analytics - Predictive Insights: Installation Guide

Preface

The purpose of this guide is to help you install Operations Analytics - Predictive

Insights.

After completing all steps documented in this guide, you will have a set of running Operations Analytics - Predictive Insights components ready to configure into a fully functional system.

Audience

The audience for this manual is the network administrator or operations specialist responsible for installing Operations Analytics - Predictive Insights.

To install Operations Analytics - Predictive Insights successfully, a basic knowledge of the following is required: v Administration of the Linux operating system.

v Administration of IBM InfoSphere Streams.

v Administration of the DB2 database management system.

v Administration of OMNIbus and OMNIbus WebGUI.

v Operations Analytics - Predictive Insights

Components

IBM

®

Operations Analytics - Predictive Insights consists of four main components.

The IBM Operations Analytics - Predictive Insights components are: v The Database component : is used to store configuration data, metadata and metric data.

v The Analytic component : performs data mediation and processes incoming data to discover any anomalies that are present.

v The UI component : presents any discovered anomalies through the IBM

Dashboard Application Services Hub application or the IBM Tivoli Integrated

Portal application.

v The Mediation tool : is used to configure a data source and the data model that

Operations Analytics - Predictive Insights will monitor.

Operations Analytics - Predictive Insights documentation includes the following guides: v Release notes v Installation Guide v Upgrade Guide v Administration Guide v Error Messages Guide


v

vi


Chapter 1. Introduction

Operations Analytics - Predictive Insights is real-time performance analysis software for business services.

Operations Analytics - Predictive Insights eliminates manual threshold and baseline configuration by providing a self-learning capability.

By analyzing data from various sources and integrating with existing monitoring products, Operations Analytics - Predictive Insights learns the normal behavior of a business service and creates a performance model. When Operations Analytics -

Predictive Insights detects or forecasts anomalous behavior, an alarm is generated.

Operations Analytics - Predictive Insights offers out-of-the-box integration with

Netcool

®

OMNIbus.

The Operations Analytics - Predictive Insights system has four main components: v The Database component : is used to store configuration data, metadata and metric data.

v The Analytic component : performs data mediation and processes incoming data to discover any anomalies that are present.

v The UI component : presents any discovered anomalies through the IBM

Dashboard Application Services Hub application or the IBM Tivoli Integrated

Portal application.

v The Mediation tool : is used to configure a data source and the data model that

Operations Analytics - Predictive Insights will monitor.


1

2


Chapter 2. Preparing to install

Before you begin installing Operations Analytics - Predictive Insights, you must complete a series of tasks to prepare your system.

Checking the installation prerequisites

Run the prereq_scanner.sh script to check various installation prerequisites for

Operations Analytics - Predictive Insights.

Before you begin

If you want to run the prerequisite scanner as a non-root user, enter the following command to add the /usr/sbin directory to the path variable so the Linux mount, swapinfo , and psrinfo commands are available to the script: export PATH=$PATH:/usr/sbin

About this task

The prereq_scanner.sh script completes the following system validation checks: v System: Checks that all system resources such as CPU, memory, free disk space, and operating system flavor and version meet the requirements to run

Operations Analytics - Predictive Insights. The script checks that your system meets the minimum requirements to run Operations Analytics - Predictive

Insights. For information on the additional system requirements to size

Operations Analytics - Predictive Insights for a specific number of KPIs, see

Hardware sizing in the Performance and Sizing wiki v Libraries and packages: Ensures that the required packages for Operations

Analytics - Predictive Insights and its prerequisites are installed in the correct location.

v Software: Checks that the correct version of DB2 is installed.

Procedure

1.

Change to the directory that contains the prereq_scanner.sh script in one of the following locations: v

The predictiveInsightsInstaller1.3.3 directory within the directory where you downloaded and extracted Operations Analytics - Predictive Insights v $PI_HOME after you install Operations Analytics - Predictive Insights

2.

To run the prerequisite scanner, type:

./prereq_scanner.sh

3.

Enter the corresponding number to check the prerequisites for the specific component or components that you wish to install on the server.

2

3

Number

1

Checks prerequisites for:

The database component only

The analytics component only

The UI component running in a Dashboard

Application Services Hub environment.


3

Number

4

5

6

Checks prerequisites for:

The UI component running in a Tivoli

Integrated Portal environment.

The database, analytics, and UI components in a Dashboard Application Services Hub environment.

That database, analytics, and UI components in a Tivoli Integrated Portal environment.

Results

The prerequisite scanner logs the scan activity to a precheck.log file and writes the results of the scan to the result.txt file. Possible results are as follows:

Table 1. Prerequisite scanner results

Result

Pass

Warning

Fail

Explanation

If the target server meets all the prerequisites, the script returns a pass for the prerequisite check.

If the target server does not meet one or more of the prerequisites with a warning severity level, the script returns an overall warning results for the prerequisite check. With a warning result, you can complete the installation of Operations Analytics - Predictive

Insights, but the performance or operation of the system may be affected.

Therefore, it is recommended that you take action to resolve the items with a warning status before you start the installation.

If the target server does not meet the prerequisites, the script returns fail for the prerequisite check. To resolve the failure, take the appropriate actions, for example, install the missing operating system packages, increase disk space, modify the configuration settings and so on.

Adding the required users

Create users for the installation of Operations Analytics - Predictive Insights and its prerequisites.

About this task

When installing Operations Analytics - Predictive Insights on a single server, you can use a single user account to install the system requirements and the Operations

Analytics - Predictive Insights components, or you can use multiple accounts. This section assumes that, at a minimum, you will use the following two accounts: v db2inst1 to install and administer DB2.

4


v scadmin to install the other system requirements and Operations Analytics -

Predictive Insights.

The db2inst1 user must be created on the server on which you install DB2. The scadmin user must be created on all servers on which Operations Analytics -

Predictive Insights components will be installed, and also on the database server.

Procedure

1.

As root user on the database server and on the analytics server, add the user account scadmin.

The following are the commands that are required to create this user: groupadd scadmin useradd -g scadmin -d /home/scadmin -s /bin/bash scadmin passwd scadmin

2.

As user root on the database server, create an OS user within the relevant group.

groupadd db2iadm1 useradd -g db2iadm1 -d /home/db2inst1 -s /bin/bash db2inst1 passwd db2inst1

3.

As root user on the database server, add the existing scadmin user to the same primary group as the DB2

® instance owner, by default this user is db2inst1.

For example, add the user scadmin to the group db2iadm1.

usermod -G scadmin,db2iadm1 scadmin

4.

On the database server, add the following source command into the

~scadmin/.bashrc

file: if [ -f /home/db2inst1/sqllib/db2profile ]; then

. /home/db2inst1/sqllib/db2profile fi

The commands assume two things: v db2inst1 is the DB2 instance owner.

v /home/db2inst1 is the home area of the DB2 instance owner v DB2 is installed in the /home/db2inst1/sqllib directory

Configuring fully qualified domain names for servers

Before you start the installation, ensure that each server that is to host an

Operations Analytics - Predictive Insights component has a fully qualified domain name.

Also, ensure that the host entry in each server's /etc/hosts file is in the following format:

<ip-address> <fully qualified domain name> <short host name>

Note:

Do not install Operations Analytics - Predictive Insights on a server that has an underscore (_) character in its host or domain name. The host name and domain name must conform to the name requirements described in Internet

Official Protocol Standards RFC 952:

A "name" (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.).

Note that periods are only allowed when they serve to delimit components of "domain style names".

Chapter 2. Preparing to install

5

Setting ulimits

Setting the ulimits for your Operations Analytics - Predictive Insights system.

Procedure

1.

As root, create a file named /etc/security/limits.d/90-nproc.conf and add the following lines:

*

* soft hard nproc nproc

100000

100000

2.

As root, create a file named /etc/security/limits.d/91-nofile.conf and add the following lines:

*

* soft hard nofile nofile

100000

100000

3.

Add the following lines to the .bashrc file of the owner of the Analytics component (typically scadmin), so that each new shell that user opens has these updated settings.

ulimit -u 100000 ulimit -n 100000

Installing KSH and required libraries for Operations Analytics -

Predictive Insights

Operations Analytics - Predictive Insights requires the installation of KSH and some libraries.


Note:

This is not a statement of the libraries required by the Operations Analytics -

Predictive Insights pre-requirements, that is, DB2, InfoSphere Streams, and

Netcool/OMNIbus. To find the required libraries for these products, you must run the product-specific dependency checker scripting or check the product-specific documentation.

About this task

The Analytics server requires the following packages: v 64-bit packages:

– atlas

– compat-libgfortran-41

– lapack

– blas

– glibc-devel

The Database server requires the following packages: v 64-bit packages:

– dapl

– sg3_utils

The following packages are required on all servers in the topology: v Packages:

– compat-libstdc++-33

– libstdc++

6


– compat-libstdc++-33.i686

– libstdc++.i686

KSH is also a software requirement.

Procedure

1.

For each required library enter the command, yum install, followed by the name of that library.

2.

If you see this error from yum when installing the 32-bit libstdc++ libraries:

Error: Protected multilib versions: libstdc++

Then run yum update libstdc++ and re-try the install.

3.

If KSH is not on your system, install it as follows: yum install ksh

Installing the prerequisite software

The version numbers of the prerequisite software and the order of installation.

Note:

To ensure that you install the correct versions of the prerequisite software, download and install the following products. For more information, see

Downloading Operations Analytics - Predictive Insights

Table 2. eAssembly numbers for Operations Analytics - Predictive Insights and its prerequisites

Title

IBM Operations Analytics - Predictive Insights V1.3.3 Multiplatform

English eAssembly

IBM Operations Analytics - Predictive Insights OMNIbus Components

V1.3 Linux English eAssembly

eAssembly part number

CRX46EN

CRP12EN

Prerequisite Versions

The following table lists the versions of the prerequisite software required if you want to use Operations Analytics - Predictive Insights with Dashboard Application

Services Hub.

Table 3. Prerequisite Versions for Dashboard Application Services Hub

Prerequisite

IBM DB2 Workgroup Server Edition

IBM InfoSphere Streams

IBM Jazz for Service Management

IBM Netcool/OMNIbus Core

IBM Netcool/OMNIbus WebGUI

IBM Websphere

Version

10.5 FP3

3.2

1.1.0.3 and 1.1.1.0 patch

8.1 FP2 *

8.1 FP2 *

8.5.0.1

* FP2 is optional but is the recommended version.

The following table lists the versions of the prerequisite software required if you want to use Operations Analytics - Predictive Insights with Tivoli Integrated Portal.


7

Table 4. Prerequisite Versions for Tivoli Integrated Portal

Prerequisite

IBM DB2 Workgroup Server Edition

IBM InfoSphere Streams

IBM Netcool/OMNIbus Core

IBM Netcool/OMNIbus WebGUI

Version

10.5 FP3

3.2

7.4

7.4 FP4 *

* FP4 is optional but is the recommended version.

Installation Order

You must install the Operations Analytics - Predictive Insights prerequisite software in the following order:

1.

IBM DB2 Workgroup Server Edition 10.5 FP3

2.

IBM InfoSphere

®

Streams 3.2

3.

IBM Jazz for Service Managment 1.1.0.3. After installation, this must be updated to IBM Jazz for Service Management 1.1.1.0

4.

IBM Netcool/OMNIbus Core 8.1

5.

IBM Netcool/OMNIbus WebGUI 8.1

Note:

If Netcool/OMNIbus is already installed, it is recommended that you create a new instance for Operations Analytics - Predictive Insights.

The order of installation is the same for a single server installation or multi-server installation.

DB2

DB2 is a requirement of Operations Analytics - Predictive Insights.

Document caveat

This installation guide provides a shortened version of the DB2 installation process.

Note:

It must be noted the installation process prescribed in this documentation is not meant to replace the product-specific documentation. The installation process here contained for DB2 has been provided for the convenience of the end-user and should only be used if: v You are performing a basic install of DB2, accepting all the default options.

v You are performing a trial installation of the Operations Analytics - Predictive

Insights product.

You must consult the official DB2 documentation if: v You intend to use extra options or steps that are not the default as described in this document.

v You intend to install multiple instances of the required product

The official and complete IBM DB2 Installation instructions and release notes are available in the DB2 Knowledge Center.

8


Instructions on installing IBM DB2 using a response file are available in the DB2

Knowledge Center section: Installing a DB2 database product using a response file.

Install processes

The following are the two options for DB2 installation covered in this document: v Install DB2 as non-root v Install DB2 as root

Both of these options are covered in the following sections, only one of these options is to be pursued.

Information required for Operations Analytics - Predictive

Insights installation

The installation process for Operations Analytics - Predictive Insights requires that you have your DB2 installation information at the ready.

The following table lists the DB2 information items that the Operations Analytics -

Predictive Insights installer requests as you pursue the installation process. It is a good practice to make note of all listed items as you install the DB2 database.

Table 5. DB2 details required by Operations Analytics - Predictive Insights

Information item

DB2 instance user name

Operations Analytics - Predictive Insights

Database name


Database server port number


Database host


Database user


Database user password

Default

db2inst1

SCAPIDB

50000

Current host scadmin

Installing DB2 as non-root



Verify your operating system user process resource limits (ulimits). If the minimum ulimit values are not met, the DB2 engine can encounter unexpected operating resource shortage errors. These errors can lead to a DB2 database system outage.

See the section Operating system user limit requirements (Linux and UNIX) in the DB2 Knowledge Center for details of the recommended ulimit values.

About this task

The DB2 installer automatically creates and configures a non-root instance during a non-root installation. As a non-root user, you can customize the configuration of the non-root instance during the installation. You can also use and maintain the


9

installed DB2 database product without root privileges. The non-root installation of a DB2 database product has one DB2 instance with most features enabled by default.

A non-root installation can be useful for: v Enterprises that have thousands of workstations and users who want to install a

DB2 database product without consuming a system administrator's time v Application developers who are not typically system administrators but use DB2 database products to develop applications v Independent Software Vendors (ISVs) who develop software that does not require root user authority yet embeds a DB2 database product

After you install DB2 as a non-root user, it has most of the functions that are available when you install it as a root user. However, there are some differences and limitations. You must remove some of the limitations by running the db2rfe command as a root user.

Before you install any DB2 database product as a non-root user, be aware of the differences between root installations and non-root installations, and the limitations of non-root installations. For more information on non-root installation, see

Installing DB2 database servers as a non-root user in the DB2 Knowledge Center.

The following tasks are described in order to allow you install DB2 as a non-root user:

Procedure

1.

Prepare for DB2 installation by installing the required libraries.

2.

Install DB2 using the non-root user account.

3.

Enabling root-based features in non-root installations with db2rfe

4.

If your DB2 installation connection has problems, runs some checks to verify your installation.

Prepare for DB2 installation as non-root:

You must create the non-root user to carry out the installation of DB2 and add the required files.

About this task

DB2 can be installed as a non-root user. The ongoing management of DB2 is done as the DB2 instance owner. Typically the DB2 instance owner is db2inst1.

For more information on DB2 installation prerequisites, see Operating system user

limit requirements (Linux and UNIX) in the DB2 Knowledge Center.

Procedure

1.

As db2inst1, copy the DB2 installation software to the directory in which you want to extract it.

2.

Change the permissions on the folder, if necessary, to be owned by db2inst1.

3.

As db2inst1, extract the DB2 installation software.

For example: tar zxvf DB2_10.5.0.3_limited_Lnx_x86-64.tar.gz

10


Note:

The package filename is correct for DB2 installation version IBM DB2

Workgroup Server Edition 10.5 FP3

4.

As db2inst1, change to the server_r directory and run the DB2 prerequisites checker script.

For example:

./db2prereqcheck -v 10.5.0.3

You can ignore alerts in relation to the following: v /lib/libpam.so* v rdma v InfiniBand v modprobe.conf

v OpenSSH v log_mtts_per_seg

5.

As root, install any packages that are called out as problems by the db2prereqcheck script.

For example: yum install dapl yum install sg3_utils

6.

Check if SELINUX is enabled, and if so disable it.

For example: vi /etc/selinux/config

SELINUX=disabled

7.

Restart the server if the SELINUX setting was changed.

8.

Modify the kernel parameters as described in the section, Modifying kernel

parameters (Linux) of the DB2 Knowledge Center

DB2 installation as non-root:

Install DB2 as the non-root user db2inst1.


Verify your operating system user process resource limits (ulimits). If the minimum ulimit values are not met, the DB2 engine can encounter unexpected operating resource shortage errors. These errors can lead to a DB2 database system outage.

See the section Operating system user limit requirements (Linux and UNIX) in the DB2 Knowledge Center for details of the recommended ulimit values.

Procedure

1.

Log in as the non-root user db2inst1.

2.

Change to the directory containing the installation software.

For example: cd /home/db2inst1/server_r

3.

As db2inst1, run the db2setup script:

./db2setup

4.

Click Install a Product from the menu on the left of the screen.

5.

Click Install New > DB2 Workgroup Server Edition version 10.5 Fix Pack 3.

6.

Follow the installation wizard to complete the installation.


11

What to do next

The DB2 installation script prompts you to set up the DB2 instance environment.

The instructions on how to do this are output by the DB2 installation script. The steps are best pursued in a new command terminal.

Enable root-based features in non-root installations with db2rfe:

There are several features and abilities in non-root installations that are initially unavailable but which can be enabled by running a the db2rfe command.

About this task

There are further limitations on non-root installations that can be overcome by running the db2rfe command. The following features and abilities are initially unavailable in non-root installations: v Operating system-based authentication v The ability to reserve service names in the /etc/services file

To enable them, use the db2rfe_config_file.cfg available in the unpacked

IOA_PI_1.3.3.tgz

Procedure

To enable the features and abilities that are initially unavailable in non-root installations:

1.

Unpack the Operations Analytics - Predictive Insights software,

IOA_PI_1.3.3.tgz

, if you have not already done so.

2.

Navigate to the predictiveInsightsInstaller1.3.3 directory, that is within the directory in which you unpacked IOA_PI_1.3.3.tgz.

3.

(Optional) Update the sample configuration file, db2rfe_config_file.cfg.

The configuration file is used as input to the db2rfe command. Only update the sample configuration file provided if you wish to enable more options than the default file enables.The sample configuration file enables: v Operating system-based authentication v The ability to reserve service names in the /etc/services file

If you wish to enable more options, perform the following steps: a.

Copy the sample configuration file, db2rfe_config_file.cfg, to a different location, for example, /home/db2inst1.

b.

Consult DB2 documentation and update the configuration file as preferred.

c.

Update the file as appropriate.

4.

Stop DB2. As db2inst1, run: db2stop

5.

End the server to client process: As db2inst1, run: db2 terminate

6.

Log in with root user authority.

7.

Navigate to the $HOME/sqllib/instance directory, where $HOME represent's the non-root user's home directory.

8.

Run the db2rfe command referring to the sample or updated configuration file.

For example:

./db2rfe -f /home/db2inst1/db2rfe_config_file.cfg

12


Where: v db2rfe_config_file.cfg

is the configuration file provided in the

IOA_PI_1.3.3.tgz

file.

v /home/db2inst1 is the directory to which you copied db2rfe_config_file.cfg

. If you copied this to another directory, please update the command syntax to refer to your chosen directory.

DB2 post installation tasks:

Configure your DB2 installation so that it is running correctly.

Procedure

1.

Stop DB2. As db2inst1, run: db2stop

2.

End the server to client process: As db2inst1, run: db2 terminate

3.

If the port is closed you may need to disable iptables on the DB2 server.

As root, run the following commands: service iptables stop

/sbin/chkconfig --del iptables

4.

Check DB config to ensure SVCENAME is correct.

Run the following command as db2inst1: db2 get dbm cfg | grep SVCENAME

If SVCENAME does not match "db2c_db2inst1" then update using the following command: db2 update dbm cfg using SVCENAME db2c_db2inst1

5.

Verify SVCENAME, as seen in step 4, exists for correct port in /etc/services file. If not then append it to /etc/services file.

db2c_db2inst1 50000/tcp

6.

Ensure the communication protocols for DB2 instance uses TCPIP.

As db2inst1, run: db2set DB2COMM=tcpip

7.

Start DB2:

As DB2inst1 run command: db2start

What to do next

See the section Verifying the installation using the command line processor (CLP) in the

DB2 Knowledge Center to confirm that DB2 was installed correctly.

Installing DB2 as root


About this task

DB2 can be installed as root. The ongoing management of DB2 is done as the DB2 instance owner. Typically the DB2 instance owner is db2inst1.


13

Procedure

1.

Copy the DB2 installation software to the directory in which you want to extract it.

2.

Extract the DB2 installation software.

For example: tar zxf DB2_10.5.0.3_limited_Lnx_x86-64.tar.gz

Note:

The package filename is correct for DB2 installation version IBM DB2

Workgroup Server Edition 10.5 FP3

3.

Change to the server_r directory and run the DB2 prerequisites checker script.

For example:

./db2prereqcheck -v 10.5.0.3

You can ignore alerts in relation to the following: v /lib/libpam.so* v rdma v InfiniBand v modprobe.conf

4.

Install any packages that are called out as problems by the db2prereqcheck script.

For example: yum install dapl yum install sg3_utils

5.

Check if SELINUX is enabled, and if so disable it.

For example: vi /etc/selinux/config

SELINUX=disabled

6.

Restart if the SELINUX setting was changed.

7.

Modify the kernel parameters as described in the DB2 documentation,

Modifying kernel parameters (Linux)

8.

Change to the directory containing the installation software.

For example: cd /home/db2inst1/server_r

9.

Run the db2setup script:

./db2setup

Note:

This command opens the DB2 installation wizard and therefore must be run from a suitable XTERM or VNC window.

10.

Click Install a product from the set of options displayed.

11.

Click Install New > DB2 Version 10.5 Fix Pack 3 Workgroup, Enterprise and

Advanced Editions

.

12.

Accept the defaults in the installation wizard until you are prompted to set user information for the DB2 instance owner. To set the DB instance owner, click the Existing user radio button and enter db2inst1. Follow the remainder of the wizard to complete the installation.

Make note of any users and passwords that you specified.

14


InfoSphere Streams

InfoSphere Streams is a requirement of Operations Analytics - Predictive Insights.

Infosphere Streams versions

The following versions of Infosphere Streams are supplied with Operations

Analytics - Predictive Insights 1.3.3: v Infosphere Streams 3.2

v Infosphere Streams 4.0.0

When you are deciding which version of Infosphere Streams to install, consider whether you can use SSH in your environment. It is mandatory to use SSH with

Infosphere Streams 3.2, whereas SSH use is optional with Infosphere Streams 4.0.0.

It is recommended that you install Infosphere Streams 3.2 unless you are unable to use SSH in your environment.

Document caveat

This installation guide provides a shortened version of the InfoSphere Streams installation process.

Note:

The installation process that is described in this documentation is not meant to replace the product-specific documentation. You can follow this installation procedure if: v You are completing a basic installation of InfoSphere Streams, accepting all the default options.

v You are completing a trial installation of the Operations Analytics - Predictive

Insights product.

You must consult the official InfoSphere Streams documentation if: v You intend to use extra options or steps that are not the default as described in this document.

v You intend to install multiple instances of the required product

The official and complete installation and administration information for IBM

InfoSphere Streams can be found in the IBM InfoSphere Streams Knowledge

Center.

Console Installation of IBM InfoSphere Stream can be found in the IBM InfoSphere

Streams Knowledge Center section: Installing InfoSphere Streams.



The installation process for Operations Analytics - Predictive Insights requires that you have your InfoSphere Streams install information at the ready.

The following table lists the InfoSphere Streams information items that the

Operations Analytics - Predictive Insights installer requests as you pursue the installation process. It is a good practice to make note of the required InfoSphere

Streams installation information.


15

Table 6. InfoSphere Streams details required by the Operations Analytics - Predictive

Insights installer

Information item Default

InfoSphere Streams user

InfoSphere Streams user password

InfoSphere Streams installation location scadmin

/home/scadmin/InfoSphereStreams

Installing InfoSphere Streams 3.2

Installing InfoSphere Streams 3.2 for Operations Analytics - Predictive Insights.


1.

As root, edit the /etc/selinux/config file to set SELinux to disabled.

A change to this policy requires a restart of the Linux VM/Server

See the section “Security-Enhanced Linux (SELinux) for IBM InfoSphere

Streams” contained in the IBM InfoSphere Streams Knowledge Center.

2.

Ensure the user that is being used to install InfoSphere Streams has executable permissions on the /tmp, /opt, and /home file systems.

3.

Ensure that su from the root user does not require that you enter a password.

4.

Check the /etc/hosts file to make sure that the server name is not on the same line as the loop back address.

For example, if you have an address that looks like:

127.0.0.1 localhost.localdomain localhost <server_name>

Then, remove the server name so that it looks like:

127.0.0.1 localhost.localdomain localhost

You must not remove the loopback address.

5.

Enter the following command to check that the sshd service is running: service sshd status

6.

If the sshd service is not running, enter the following command to start it: service sshd start

7.

Ensure that the user that you will use to complete the installation, for example, scadmin, has full permissions on the InfoSphere Streams installation software.

8.

Change to the scadmin user, for example: su - scadmin

9.

Extract the InfoSphere Streams installation software, for example: tar zxvf Streams-3.2.0.0-x86_64-el6.tar.gz

10.

Change to the directory in which you unpacked the InfoSphere Streams installation software and as scadmin use the InfoSphere Streams dependency checker: cd <streams_unpack_folder>

./dependency_checker.sh

You may receive an alert indicating that the perl-XML-Simple file is missing. If so, you can find the file in the <streams_unpack_folder>/rpm directory.

To install a missing rpm, run the following command: yum install <rpm_name>.rpm

To install any missing packages, run the following command: yum install <package_name>

16


Note:

If root user permissions are required to install missing files, make sure that you switch back to your InfoSphere Streams user, scadmin, after you complete the installation.

Procedure

1.

Run the installer as scadmin: cd <streams_unpack_folder>

./InfoSphereStreamsSetup.bin

Accept all default values presented during setup. When the installation is complete the Postinstallation Tasks dialog is displayed, which lists the set of initial configuration tasks for InfoSphere Streams.

2.

Run the following tasks only from the First Steps: v Configure the SSH environment v Generate public and private keys v Verify the Installation

If the dialog does not open or must be reopened change to the directory

<streams_unpack_folder> and run FirstSteps.sh, for example: cd /home/scadmin/InfoSphereStreams

./FirstSteps.sh

3.

Add the following line to the .bashrc file for scadmin: if [ -f /home/scadmin/InfoSphereStreams/bin/streamsprofile.sh ]; then

. /home/scadmin/InfoSphereStreams/bin/streamsprofile.sh

fi

Note:

If you did not install InfoSphere Streams in the default location,

/home/scadmin/InfoSphereStreams , enter the actual path to your installation in the .bashrc file.

4.

Save and source the file:

. ~/.bashrc

5.

Ensure the version of Java that comes with InfoSphere Streams is the one that is used at run time: a.

Update the JAVA_HOME and PATH to match the new Java.

For example:

PATH=/home/scadmin/InfoSphereStreams/java/bin:$PATH

JAVA_HOME=/home/scadmin/InfoSphereStreams/java export PATH JAVA_HOME

Note:

Substitute the directory path if you installed InfoSphere Streams to a different location.

b.

Add the JAVA_HOME and PATH variables to the ~scadmin/.bashrc and

~scadmin/.bash_profile

files.

6.

Modify LD_LIBRARY_PATH by adding the following line to the ~scadmin/.bashrc

file: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64:/usr/lib

Installing InfoSphere Streams 4.0.0

Installing InfoSphere Streams 4.0.0 for Operations Analytics - Predictive Insights. It is recommended that you install InfoSphere Streams 4.0.0 only if you cannot use

SSH, which is mandatory with InfoSphere Streams 3.2.


17


1.

As root, edit the /etc/selinux/config file to set SELinux to disabled.

A change to this policy requires a restart of the Linux VM/Server

See the section “Security-Enhanced Linux (SELinux) for IBM InfoSphere

Streams” contained in the IBM InfoSphere Streams Knowledge Center.

2.

Ensure the user that is being used to install InfoSphere Streams has executable permissions on the /tmp, /opt, and /home file systems.

3.

Ensure that su from the root user does not require that you enter a password.

4.

Check the /etc/hosts file to make sure that the server name is not on the same line as the loop back address.

For example, if you have an address that looks like:

127.0.0.1 localhost.localdomain localhost <server_name>

Then, remove the server name so that it looks like:

127.0.0.1 localhost.localdomain localhost

You must not remove the loopback address.

5.

Ensure that the user that you will use to complete the installation, for example, scadmin

, has full permissions on the InfoSphere Streams installation software.

6.

Change to the scadmin user, for example: su - scadmin

7.

Extract the InfoSphere Streams installation software, for example: tar zxvf IS_STRM_4.0.0_RHEL6_EN.tar.gz

8.

Change to the directory in which you unpacked the InfoSphere Streams installation software and run the InfoSphere Streams dependency checker: cd <streams_unpack_folder>

./dependency_checker.sh

You may receive an alert indicating that the perl-XML-Simple file is missing. If so, you can find the file in the <streams_unpack_folder>/rpm directory.

To install a missing rpm, run the following command: yum install <rpm_name>.rpm

To install any missing packages, run the following command: yum install <package_name>

Note:

If root user permissions are required to install missing files, make sure that you switch back to your InfoSphere Streams user, scadmin, after you complete the installation.

Procedure

1.

Run the installer as scadmin: cd <streams_unpack_folder>

./InfoSphereStreamsSetup.bin

Accept all default values presented during setup.

2.

When the installation is complete, the installer prompts you to open the

Domain Manager UI. You do not need to open the UI as the Operations

Analytics - Predictive Insights start script, start.sh, creates a domain when it is run.

3.

Add the following lines to the .bashrc file for scadmin: if [ -f /home/scadmin/InfoSphereStreams/bin/streamsprofile.sh ]; then

. /home/scadmin/InfoSphereStreams/bin/streamsprofile.sh

fi

18


Note:

If you did not install InfoSphere Streams in the default location,

/home/scadmin/InfoSphereStreams , enter the actual path to your installation in the .bashrc file.

4.

Save and source the file:

. ~/.bashrc

5.

Ensure the version of Java that comes with InfoSphere Streams is the one that is used at run time: a.


For example:



Note:


b.



files.

6.

To modify the LD_LIBRARY_PATH variable, add the following line to the

~scadmin/.bashrc

file: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64:/usr/lib

Jazz for Service Management

You must install IBM Java

™ for Service Management 1.1.0.3 and patch it to IBM

Jazz for Service Management 1.1.1.0, unless you have already installed Tivoli

Integrated Portal with Omnibus WebGui 7.4.

You will need Dashboard Application Services Hub, which is bundled with Jazz for Service Management, to visualize the events generated by Operations Analytics

- Predictive Insights.

The installation process described in this section is a shortened version of the Jazz for Service Management installation. For information on how to install Jazz for

Service Management with more than just the default options please consult the official installation docs. To see the official installation documentation, navigate to the section entitled Installing Jazz for Service Management within the Jazz for Service

Management Knowledge Center and pursue all steps described.

Installing Jazz for Service Management

Instructions on how to install Jazz for Service Management so that it can be used with Operations Analytics - Predictive Insights.

Procedure

1.

Download and extract the required software The software required for the Jazz for Service Management integration with Operations Analytics - Predictive

Insights is: v JAZZ_FOR_SM_1.1.0.3_FOR_LNX.zip

v WAS_V8.5.0.1_FOR_JAZZSM_LINUX_ML.zip

Extract both files to a directory on the server which you intend to install Jazz for Service Management.

2.

Run the prerequisite scanner.

a.

Navigate to the directory in which you extracted the Jazz for Service

Management zip file.


19

b.

Run the command to start launchpad, for example:

./launchpad.sh

c.

Click Tools > IBM Prerequisite Scanner > Run d.

Resolve any failures in the following sections: v DSH - Dashboard Application Services Hub in JazzSM v ODP - Common prerequisites in JazzSM

Note:

You can ignore failures in other sections of the scanner output. For example: network.availablePorts.db2instance FAIL PortsInUse:631,6001,60001,5901,523... 50000 os.servicesTCPavailablePorts.db2instance FAIL PortsInUse:50000 50000

DBType FAIL DB2 DB2ShdNotBeInstalled

If you run the prerequisite scanner as a non-root user, you can ignore the following failure: user.isAdmin FAIL False True

3.

Run the Jazz for Service Management installation.

a.

Navigate to the directory in which you extracted the Jazz for Service

Management zip file.

b.

Run the command to start launchpad, for example:

./launchpad.sh

c.

Click Tools > Installation Manager.

d.

Enter the location of IBM WebSphere Application Server package repository.

For example, <EXTRACT_LOCATION>/WASRepository/disk1/diskTag.inf

e.

Click Run.

f.

When Installation Manager launches, click Install.

g.

Install the following three packages v IBM WebSphere Application Server v Jazz for Service Management extensions for IBM WebSphere v IBM Dashboard Application Service Hub h.

Continue with the installation using Installation Manager until completion.

Note:

The JazzSM installer creates the required profile so you do not need to create a profile when prompted to do so at the end of the installation.

What to do next

After you have installed Jazz for Service Management, you must download and install the 1.1.1.0 fix pack for Jazz for Service Management.

1.

Download the IBM Jazz for Service Management 1.1.1.0 patch installation files from IBM Support Fix Central.

To locate the fix pack: v Open IBM Support Fix Central.

v Enter Jazz for Service Management.

v Choose All versions and Linux in the remaining fields.

v Browse for fixes and select and download fix pack 1.1.1-TIV-JazzSMmulti.zip

and the readme file, 1.1.1.0-TIV-JazzSM-RME-multi.zip.

2.

Follow the installation instructions in the readme file.

20


Note:

When prompted select Core services in Jazz for Service Management

Package Group Name

and then follow instructions.



The installation process for Operations Analytics - Predictive Insights requires that you have your Jazz for Service Management install information at the ready.

The following table lists the Jazz for Service Management information items that the Operations Analytics - Predictive Insights installer requests as you pursue the installation process. It is a good practice to make note of the required Jazz for

Service Management installation information.

Table 7. Jazz for Service Management details required by the Operations Analytics -

Predictive Insights installer

Information item Default

Jazz for Service Management / Dashboard

Application Services Hub hostname

User name and password of Dashboard

Application Services Hub installer

Dashboard Application Services Hub installation location

Dashboard Application Services Hub profile user name and password

/opt/IBM/jazzSM

Netcool/OMNIbus

Netcool/OMNIbus is a required integration item for Operations Analytics -


Document caveat

This installation guide provides a shortened and more basic version of the

Netcool/OMNIbus installation process.

Note:

The installation process prescribed in this documentation is not meant to replace the product-specific, comprehensive Netcool/OMNIbus installation documentation. The installation process here contained for Netcool/OMNIbus has been provided for the convenience of the end-user and should only be used if: v You are performing a basic install of Netcool/OMNIbus, accepting all the default options.

v You are performing a trial installation of the Operations Analytics - Predictive

Insights product.

You must consult the official Netcool/OMNIbus documentation if: v You intend to use extra options or steps that are not the default as described in this document.

v You intend to install multiple instances of the required product.

v You intend to pursue a silent, console or other installation type that is not the default as described in this document.


21

The official and complete Installation and administration information for

Netcool/OMNIbus can be found in the Tivoli Netcool/OMNIbus Knowledge

Center.

Console installation instructions for Netcool/OMNIbus can be found in the Tivoli

Netcool/OMNIbus Knowledge Center section: Installing in console mode (UNIX and

Linux).



The installation process for Operations Analytics - Predictive Insights requires that you have certain Netcool/OMNIbus and Netcool/OMNIbus WebGUI installation information at the ready.

The following table lists the Netcool/OMNIbus and Netcool/OMNIbus WebGUI information items that the Operations Analytics - Predictive Insights installer will request as you pursue the installation process. It is a good practice to make note of all information items as you install Netcool/OMNIbus and Netcool/OMNIbus

WebGUI.

Table 8. Netcool/OMNIbus and Netcool/OMNIbus WebGUI details required by the

Operations Analytics - Predictive Insights installer


OMNIbus server host name

OMNIbus server port number

OMNIbus Object Server name

OMNIbus admin user name

OMNIbus admin user password

Directory where WAAPI is installed

Default

Current

® host

4100

NCOMS root

Note:

It is possible to leave this password as an empty string. Entering this password incorrectly is not flagged immediately within the Operations Analytics - Predictive

Insights installer, but results in certain components not installing correctly.

/opt/IBM/tivoli/netcool/omnibus_webgui/ waapi

Table 9. Tivoli Integrated Portal details required by the Operations Analytics - Predictive

Insights installer


Directory where Tivoli

® installed

Integrated Portal is

Tivoli Integrated Portal user name

Tivoli Integrated Portal user password

Default

/opt/IBM/tivoli/tipv2 tipadmin

Installing the OMNIbus ObjectServer

The OMNIbus ObjectServer is the standard event management system that

Operations Analytics - Predictive Insights can use.


1.

Download and install the OMNIbus prerequisite scanner to make sure you have all the OMNIbus requirements in place before you begin the installation.

22


The prerequisite scanner can be downloaded from Tivoli Netcool/OMNIbus

Knowledge Center section IBM Prerequisite Scanner.

2.

Run the prerequisite scanner to discover if there are any missing items that must be installed.

3.

Install all packages which are marked as missing.

About this task

OMNIbus ObjectServer can be installed either by root or by a non-root user. If you choose to install as a non-root user, ensure the appropriate permissions on the install software and target location are given to the chosen non-root user. If you install as root, the ongoing management of OMNIbus must be done as root.

Note:

If your OMNIbus and your Operations Analytics - Predictive Insights component are on the same server and owned by the same user, do not set the

NCHOME variable. This is in line with the Tivoli Netcool/OMNIbus Knowledge

Center section Setting Tivoli Netcool/OMNIbus environment variables (UNIX and

Linux). The NCHOME environment variable specifies the home location for Tivoli

Netcool/OMNIbus. Setting NCHOME may cause the probe to point to the wrong location and not run.

Procedure

1.

Copy the OMNIbus ObjectServer installation software, OMNIbus-v8.1-

Core.linux64.zip

, to an empty directory.

2.

Extract the zip file: unzip OMNIbus-v8.1-Core.linux64.zip

Note:

The package filename is correct for IBM Netcool/OMNIbus Core 8.1.

3.

Start the graphical user interface installation wizard:

./install_gui.sh

4.

Follow the installation wizard to complete the installation, selecting the default options.

Note:

When prompted, to choose which program to start, select None.

5.

Copy the OMNIbus ObjectServer fix pack 2 installation software,

OMNIbus-v8.1-FP2-Core.linux64.zip


6.

Extract the zip file: unzip OMNIbus-v8.1-FP2-Core.linux64.zip

7.

To install OMNIbus ObjectServer fix pack 2, first change to the Installation

Manager installation directory.

8.

Use the following command to start the Installation Manager wizard:

./IBMIM

9.

In the main Installation Manager window, click File->Preferences-

>Repositories and add a repository that points to the directory in which you unzipped fix pack 2.

10.

In the main Installation Manager window, click Update.

11.

Follow the installation wizard instructions to complete the installation of fix pack 2.

What to do next

1.

After you have completed the installation, use the following command to test if all prerequisites are met for the OMNIbus ObjectServer:


23

ldd /opt/IBM/tivoli/netcool/omnibus/platform/linux2x86/bin*/nco* | grep "not found"

2.

To make that ldd command resolve all dependent libraries, set

LD_LIBRARY_PATH (both in current shell and in ~/.bashrc).

The following is an example of how this might be done: export LD_LIBRARY_PATH=/usr/lib64:/lib64:/opt/IBM/tivoli/netcool/omnibus/platform/linux2x86/lib64:

/opt/IBM/tivoli/netcool/platform/linux2x86/lib64:/usr/lib:/lib:

/opt/IBM/tivoli/netcool/omnibus/platform/linux2x86/lib:

/opt/IBM/tivoli/netcool/platform/linux2x86/lib:$LD_LIBRARY_PATH

3.

Install any prerequisites that are identified as missing.

Configuring the OMNIbus ObjectServer

When the Omnibus initial installation is complete and before you install OMNIbus

WebGUI, you must configure the ObjectServer.

Procedure

1.

Change to the directory /opt/IBM/tivoli/netcool/etc.

2.

Make a copy of the omni.dat file.

For example, run the commend mv omni.dat omni.dat.ORIG

3.

Run the command: sed s/omnihost/<yourObjServHost>/g omni.dat.ORIG > omni.dat

4.

Change to the directory /opt/IBM/tivoli/netcool/bin.

5.

Run the command:

./nco_igen -out /opt/IBM/tivoli/netcool/etc/interfaces

6.

Change to the directory /opt/IBM/tivoli/netcool/omnibus/bin.

7.

Run the following commands:

./nco_dbinit

Results

Configuration of the OMNIbus ObjectServer is now complete and it is ready to be started

Starting the OMNIbus ObjectServer

When the Omnibus initial installation is complete and before you install OMNIbus

WebGUI, you must start the ObjectServer.

Procedure

1.

Change to the directory /opt/IBM/tivoli/netcool/omnibus/bin.

2.

Run the following commands: nohup ./nco_objserv &

3.

Confirm the ObjectServer is running:

./nco_sql -user root

Note:

If your OMNIbus root user password is blank, press return after entering root .

4.

If the login worked OK, then this is enough to validate the Objectserver is running. Enter 'quit' to exit.

Installing OMNIbus WebGUI

OMNIbus WebGUI is a set of visualization tools for OMNIbus to allow for the monitoring and management of events.

24


About this task

You must use the same user that was used to install Jazz for Service Management.

OMNIbus WebGUI must be installed by root or a non-root user. Ensure the appropriate permissions on the installation software and target location are given to the non-root user if you choose to install as non-root.

Procedure

1.

Ensure the OMNIbus ObjectServer that you installed is started and ensure the

Jazz for Service Management that you installed is started.

2.

Copy the OMNIbus WebGUI installation software, OMNIbus-v8.1-

WebGUI.linux64.zip


3.

Extract the zip file: unzip OMNIbus-v8.1-WebGUI.linux64.zip

Note:

The package file name is correct for IBM Netcool/OMNIbus WebGUI

8.1.

4.

Move to the Image directory: cd im.linux.x86_64

5.

Start the graphical user interface installation wizard: v If you are installing as root, run the following command:

./install v If you are installing as non-root, run the following command:

./userinst

6.

Follow the installation wizard to complete the installation. Select the default options and record any users and passwords that you enter.

7.

Copy the OMNIbus OMNIbus WebGUI fix pack 2 installation software,

OMNIbus-v8.1-FP2-WebGUI.linux64.zip


8.

Extract the zip file: unzip OMNIbus-v8.1-FP2-WebGUI.linux64.zip

9.

To install fix pack 2, first change to the Installation Manager installation directory.

10.

Use the following command to start the Installation Manager wizard:

./IBMIM

11.

In the main Installation Manager window, click File->Preferences-

>Repositories and add a repository that points to the directory in which you unzipped fix pack 2.

12.

In the main Installation Manager window, click Update.

13.

Follow the installation wizard instructions to complete the installation of fix pack 2.

Note:

You must add the WebGUI users that are created in the post installation steps to an Objectserver repository and not a file repository.

What to do next

After you complete the WebGUI installation, a wizard appears that allows you to configure WebGUI to point to your OMNIbus ObjectServer.


25

26


Chapter 3. Installing Operations Analytics - Predictive Insights

How to install Operations Analytics - Predictive Insights

You can install all Operations Analytics - Predictive Insights components on a single server. This section contains the steps required to perform a single server installation.

The installation of Operations Analytics - Predictive Insights components can only be performed on the server on which you are running the IBM Installation

Manager. Remote installation of Operations Analytics - Predictive Insights components is not supported, you must install each component on its host server.

Make sure that you have copied the installation package to the server on which you are installing Operations Analytics - Predictive Insights.

Selecting user accounts to install components

You can use the same user account to install all Operations Analytics - Predictive

Insights components. For example, you can use the scadmin account that you created earlier.

If you wish to use different accounts to install Operations Analytics - Predictive

Insights components, you must observe the following rules when selecting accounts: v The database component must be installed by a user who has permissions to create a database in the DB2 instance that is installed.

v The Analytics component and Mediation Tool component must be installed by the same user that installed InfoSphere Streams.

v If you plan to use Tivoli Integrated Portal to display anomaly events, the UI component must be installed by the same user that installed WebGUI and Tivoli

Integrated Portal.

Creating the installation directory

You must create the directory where you want to install Operations Analytics -

Predictive Insights. For example, to create a directory /opt/IBM/scanalytics:

Procedure

1.

Enter the following command: mkdir /opt/IBM/scanalytics

2.

Ensure that each user account that will be used to install Operations Analytics -

Predictive Insights on the server has read, write and execute permissions on this directory.


27

Setting the JAVA_HOME variable

Set JAVA_HOME for the required users.

About this task

The JAVA_HOME setting is best placed in the user's ~/.bash_profile, or similar profile file.

Note:

If you are aware that non-default locations are used, then you must adjust accordingly the JAVA_HOME variable accordingly.

On the server to which you going to install the Operations Analytics - Predictive

Insights Analytics component, for the IBM InfoSphere Streams administrator, which by default is scadmin, set the JAVA_HOME variable.

Procedure

v Ensure the version of Java that comes with InfoSphere Streams is the one that is used at run time:

1.


For example:



Note:


2.



files.

v If you are installing the Operations Analytics - Predictive Insights Analytics component as root, you must also set the JAVA_HOME variable to InfoSphere

Streams Java, as described in the previous step, for root user.

Installing Operations Analytics - Predictive Insights on a single server

Installing all the Operations Analytics - Predictive Insights components on one server.


Make sure that you have copied the installation package to the server. The installation script can install components only to the server on which it is running.

Also, ensure that you have configured a domain name for your server. During the installation of the UI component, you are required to specify a single sign-on domain.

You can install all Operations Analytics - Predictive Insights components under a single user account through one instance of the IBM Installation Manager, or you can use separate user accounts. If you wish to use separate accounts, see the rules

for using separate accounts in “Selecting user accounts to install components” on page 27.

Note:

The user acount used to install the Database component must have privileges to:

28


v create the Operations Analytics - Predictive Insights database table spaces and tables for the schema.

v perform the following operations on the tables: select, insert, update, merge, and delete.

v create partitions and indexes on the tables.

Procedure

1.

Log in as the appropriate user and do the following: a.

Open an xterm window on the server on which you are installing

Operations Analytics - Predictive Insights.

b.

Navigate to the directory that contains the extracted Operations Analytics -

Predictive Insights installation package.

c.

Change to the predictiveInsightsInstaller1.3.3 directory.

d.

Enter the command ./install.sh.

The IBM Installation Manager is opened.

e.

Click the Install option.

The IBM Installation Manager displays the local installation packages.

f.

Select IBM Operations Analytics - Predictive Insights and click Next.

g.

On the Licenses page, read the license agreements for Operations

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

h.

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. Operations Analytics - 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.

i.

Click Next.

j.

On the Location page, Create a new package group is the only available option for Operations Analytics - 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 Operations Analytics - Predictive

Insights components that can be installed.

2.

If you are installing all components under the same user account, select

Database

, Analytics, Mediation tool, and UI. If you want to use different user accounts to install components, select the component(s) you want to install under the current user account. 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:

Chapter 3. Installing Operations Analytics - Predictive Insights

29

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


7.

If you wish to integrate Operations Analytics - Predictive Insights with

OMNIbus, click Omnibus connection configuration and enter the required information.

8.


9.

Click UI configuration.

You must select the application you wish to use to display anomalies generated by Operations Analytics - Predictive Insights: v Tivoli Integrated Portal (TIP) v

Dashboard Application Services Hub (DASH)

Enter the required information for the application you have selected.

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: v Enter DASH profile user/password : This must be populated by the user profile you created when installing Dashboard Application Services Hub.

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

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

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


11.

Click Mediation tool configuration and enter the required information.

30


12.


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.

Installing Operations Analytics - Predictive Insights on multiple servers

How to install Operations Analytics - Predictive Insights on multiple servers.

You can install the Operations Analytics - Predictive Insights components on multiple servers. In a multi-server installation, you must comply with certain rules when deciding how to distribute components. For more information, see supported topologies.

Note:

You can only install an Operations Analytics - Predictive Insights component on the server on which you are running the IBM Installation Manager. Remote installation of components is not supported.

Installation order for a distributed installation

The order in which you must install components when Operations Analytics -

Predictive Insights is distributed on multiple servers.

If you plan to install the Operations Analytics - Predictive Insights components on separate servers, you must install the components in the following order: v Database v Analytics v UI

If you plan to partially distribute components, you can combine the installation of some components depending on how they are distributed: v Database and Analytics components on same server, UI on separate server.

– If you plan to use the same user account to install both the Database and

Analytics components, you can install both components at the same time. The

Installation Manager automatically installs the Database first. After the

Database and Analytics components are installed, install the UI component.

v Database and UI components on same server, Analytics on separate server.

– Install the Database component first. Next, install the Analytics component.

Finally, install the UI component. If you plan to use the same user account to install both the Database and UI components, you must use the modify option in Installation Manager to install the UI.

v Analytics and UI component on same server, Database on separate server

– Install the Database component first. If you plan to use the same user account to install both the Analytics and UI components, you can install both components at the same time. The Installation Manager automatically completes the Analytics installation first.


31

GUI installation

Installing Operations Analytics - Predictive Insights with the Installation Manager

GUI.

Installing the Database component

You must complete the following steps to install the Database component using the

IBM

®

Installation Manager User Interface (UI).


The Operations Analytics - Predictive Insights Database component can be installed by the database owner or by the root user. The installing user must have privileges to: v create the Operations Analytics - Predictive Insights database table spaces and tables for the schema.



Note:

The installation script can install components only to the server on which it is running. Copy the installation package to the server on which you are installing the Database component.

Procedure

1.

As the database owner, root, or a user that is part of the same group as the database owner, for example, scadmin, open an xterm window on the server.

2.

Go to the directory that contains the extracted Operations Analytics -


3.


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.


7.

On the Licenses page, read the license agreements for Operations Analytics -

Predictive Insights. If you agree to the terms of all the license agreements, click I accept the terms in the license agreements and click Next.

8.

On the Location page, in the Shared Resources Directory field, type the path for the shared directory. The default directory is /opt/IBM/scanalytics/ install_<user>/shared

.

The IBM Installation Manager can share components across products.

Operations Analytics - Predictive Insights does not share components with any other product. It is a requirement of the IBM Installation Manager that a shared directory is 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.


32


11.

In the Installation Directory field, type the path for the installation files and click Next. It is recommended that you use the default directory of

/opt/IBM/scanalytics/install_<user>/installer .

If you choose to change Installation Directory from the default, the

Installation Directory

must be unique for each user who installs the IBM

Installation Manager on the same server.



12.

By default, all components are selected for installation. Clear the check box beside each component other than Database and click Next. The IBM

Installation Manager displays each distinct set of details required under a heading.

13.

Click Database creation configuration and enter the requested information.

The Update to create DB on a specific location is an optional setting that you can use to specify an installation location for the database that is not the default DB2 location. The directory must exist and be owned by the DB2 instance user.

14.

Click Validate to confirm that all settings are correct.

15.


16.

Click Install.

Installing the Analytics component

You must complete the following steps to install the Analytics component using the IBM

®



Ensure that the installation package is on the server on which you are installing the Analytics component.

Ensure that the server has the following prerequisites installed: v IBM InfoSphere Streams 3.2

v IBM Java SDK 7.0 build 2.6 SR5. This prerequisite is installed automatically when you install IBM

®

InfoSphere

®

Streams.

About this task

The Operations Analytics - Predictive Insights Analytics component can be installed by the InfoSphere Streams administrator, which was set to be scadmin during the InfoSphere Streams installation, or by the root user.

Note:

The installation script can install components only to the server on which it is running.

It is recommended that you install the Mediation tool on any server that you install the Analytics component and that you use the same user account to install both.

The Operations Analytics - Predictive Insights Database component must be installed before the Analytics component can be installed. If you install the

Database and Analytics components together, the Installation Manager automatically completes the Database installation first.


33

Procedure

1.

As the scadmin or root user, open an xterm window on the server on which you want to install the Analytics component.

2.

Go to the directory that contains the extracted Operations Analytics - Predictive

Insights installation package.

3.


4.

Enter the following command: ./install.sh

The IBM Installation Manager is launched.

5.

If there is no other Operations Analytics - Predictive Insights component installed on the server or if a component was installed with a different user account to that which you are using to install the Analytics component, click the Install option and complete steps a to o to install the Analytics component: a.

After you click the Install option, the IBM Installation Manager displays the local installation packages. Select IBM Operations Analytics - Predictive

Insights

and click Next.

b.

On the Licenses page, read the license agreements for Operations Analytics

- Predictive Insights. If you agree to the terms of all the license agreements, click I accept the terms in the license agreements and click Next.

c.

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 .



d.

Click Next.

e.


f.


/opt/IBM/scanalytics/install_<user>/installer

. If you want to change the default Installation Directory, 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 Operations Analytics -

Predictive Insights components that can be installed.

g.

By default, all components are selected for installation. Clear the check box beside each component other than Analytics and click Next. The IBM

Installation Manager displays each distinct set of information required under a heading.

h.

Click Database connection configuration and enter the required information.

i.


j.

Click Analytics configuration and enter the required information.

One of the required information items is a new topic name. The topic name must be a single word between 3 and 10 characters long. It can contain alphanumeric characters and the underscore character.

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,

34


application, or geography. The anomalies generated based on your data can then be grouped and displayed by topic.

k.


l.

If you wish to integrate Operations Analytics - Predictive Insights with

OMNIbus, click Omnibus connection configuration and enter the required information.

m.


n.


o.

Click Install.

6.

If another Predictive Insights component was installed on the server with the same user account that you are using to install the Analytics component, click the Modify option and complete steps a to f to install the Analytics component.

a.

After you click the Modify option, the IBM Installation Manager displays the local installation packages.

b.


c.

Select Analytics and click Next.

Note:

The check box beside any component that was previously installed is automatically checked. Do not clear the check box beside any component that was previously installed as this action causes the component to be uninstalled during the modify operation.

d.

Click Next.

e.

Click Modify.

f.

Click Finish when the modify operation is complete.

What to do next

The Operations Analytics - Predictive Insights version 1.3.3 analytics component is designed to handle the significant volume of KPIs that are typically generated by a large enterprise. For more information on the number of KPIs supported, see the

Performance and Sizing wiki.

To add further Analytics instances to your Operations Analytics - Predictive

Insights installation.

1.

Make sure the server that is to host the new Analytics component has the required prerequisites installed, as described in the Before you begin section.

2.

Install the Analytics component as described in the Procedure section.

3.

Install the Mediation tool to the same server as the new Analytics component,

as described in “Installing the Mediation tool” on page 38.

You must create at least one new topic for each Analytics server you install. The new topic or topics are used to select and segment the extra KPI data that you are going to analyze using this Analytics server. The first default topic is created when you install the Analytics component on a new server. For information on how to create supplementary topics, see Creating a Topic in the Configuring and

Administering Guide.

Installing the UI component

You must complete the following steps to install the UI component using the IBM

®



35


Before you begin installing the UI component, ensure that the following are complete: v Both the Operations Analytics - Predictive Insights Database and Analytics components are installed.

v The Analytics component has OMNIbus forwarding configured. You can configure OMNIbus forwarding when installing the Analytics component or after with the configure_omnibus.sh script. For more information, see

Configuring OMNIbus alarm management in the Administering and Configuring

Guide.

v You have configured a domain name for the server. During the installation of the UI component, you need to specify a single sign-on domain.

v

Either Tivoli Integrated Portal with WebGUI 7.4 or Dashboard Application

Services Hub with WebGUI 8.1, depending on which application you are using, is running. The UI installation process restarts Tivoli Integrated Portal or

Dashboard Application Services Hub.

v You have copied the installation package to the server on which you are installing the UI component.

Note:

If you are integrating the UI component with Dashboard Application

Services Hub, you can install the UI on the same server as Dashboard Application

Services Hub or on a different server. If you are installing into an existing Tivoli

Integrated Portal environment, you must be on the Tivoli Integrated Portal server to install the Operations Analytics - Predictive Insights UI component.

Procedure

1.

As the scadmin or root user, open an xterm window on the server on which you want to install the UI component.

2.



3.


4.



5.

If there is no other Operations Analytics - Predictive Insights component installed on the server or if a component was installed with a different user account to that which you are using to install the UI component, click the

Install

option and complete steps a to m to install the Analytics component: a.


Insights

and click Next.

b.


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

c.

On the Location page, in the Shared Resources Directory field, type the path for the shared directory. The recommended default directory is



Operations Analytics - Predictive Insights does not share components with any other product. It is a requirement of the IBM Installation Manager that

36


a shared directory is provided when you install it. The shared directory must be unique for each user who installs the IBM Installation Manager on the same server.

d.

Click Next.

e.

On the Location page, Create a new package group is the only available option for Operations Analytics - Predictive Insights f.

In the Installation Directory field, type the path for the installation files. It is recommended that you use the default directory of /opt/IBM/scanalytics/ install_<user>/installer and then click Next. If you choose to change

Installation Directory from the default, 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 Operations Analytics -

Predictive Insights components that can be installed.

g.

By default, all components are selected for installation. Clear the check box beside each component other than UI and click Next. The IBM Installation

Manager displays each distinct set of information required under a heading.

h.

Click Database connection configuration and enter the required information.

i.


j.

Click UI configuration and enter the required information.

In the UI configuration dialog, you must first select the application that you wish to use to display anomalies that are generated by Operations Analytics

- Predictive Insights: v Tivoli Integrated Portal (TIP) v Dashboard Application Services Hub (DASH)

When you select the Dashboard Application Services Hub (DASH) option you must also enter UI WebGUI configuration details, and UI local configuration details. Most items are populated by default. Note the following: v Enter DASH profile user/password : This must be populated with the user profile you created when installing Dashboard Application Services Hub.

v Enter single sign on key file password : If you configured single sign on

(SSO) for the IBM WebSphere server on which Dashboard Application

Services Hub is installed, enter the keyfile password that was used when

SSO was configured. If SSO was not configured previously, then specify a new password and note for any possible future configuration.

v 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. This password can be left blank.

v 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 user exists in a user repository that is in use in Dashboard Application

Services Hub. Also, ensure that the user has OMNIbus administration access before you proceed with the UI installation.

k.


l.

Click Next. The IBM Installation Manager displays the installation summary information


37

m.

Click Install.

6.

If another Operations Analytics - Predictive Insights component was installed on the server with the same user account that you are using to install the UI component, click the Modify option. The IBM Installation Manager displays the local installation packages. Follow steps a to f to complete the installation using the Modify operation.

a.


b.


c.

Select UI and click Next.

Note:

The check box beside any component that was previously installed is automatically checked. Do not clear the check box beside any component that was previously installed as this action causes the component to be uninstalled during the modify operation.

d.

Click Next.

e.

Click Modify.

f.


Installing the Mediation tool

The Operations Analytics - Predictive Insights Mediation tool is used to configure the data presentation to Operations Analytics - Predictive Insights. The Mediation tool can be installed on Windows or Linux systems.


Note:

The installation script can install components only to the server on which it is running. Copy the installation package to the server on which you are installing the component.

It is recommended that you install the Mediation tool on the same server as the

Analytics component.

Note:

If you can't access a graphical display on the server that hosts the Analytics component, you can install the Mediation tool on a Linux desktop system, or on a

Windows desktop system. For information on how to install the Mediation tool on

a Windows system, see “Installing the Mediation tool on Windows” on page 47.

Installing to a Linux desktop system is performed in the same way as described in the following procedure.

About this task

To install the Mediation tool, complete the following steps:

Procedure

1.

As the scadmin or root user, open an xterm window on the server on which you want to install the Mediation tool.

2.



3.


4.



38


5.

If there is no other Operations Analytics - Predictive Insights component installed on the server or if a component was installed with a different user account to that which you are using to install the Mediation tool, click Install.

Complete steps a to k to install the Mediation tool: a.


Insights

and click Next.

b.


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

c.

On the Location page, in the Shared Resources Directory field, type the path for the shared directory. The recommended default directory is




d.

Click Next.

e.


f.



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



g.

By default, all components are selected for installation. Clear the check box beside each component other than Mediation tool and click Next. The IBM

Installation Manager displays each distinct set of information required under a heading.

h.

Click Mediation tool configuration and enter the required information.

i.


j.


k.

Click Install.

6.

If another Operations Analytics - Predictive Insights component was installed on the server with the same user account that you are using to install the

Mediation tool, click the Modify option. Complete steps a to f to install the

Mediation tool.

a.


b.


c.

Select Mediation tool and click Next.

Note:

The check box beside any component that was previously installed is automatically checked. Do not clear the check box for any component that was previously installed. If you clear the check box for a component that is already installed, it is uninstalled during the modify operation.


39

d.

Click Next.

e.

Modify

f.


Console Installation

You can install Operations Analytics - Predictive Insights in console mode if you cannot access a graphical display.

Installing the Database component

You must complete the following steps to install the Database component using the

IBM

®

Installation Manager command-line interface.


The Operations Analytics - Predictive Insights Database component can be installed by the database owner or by the root user. The installing user must have privileges to: v create the Operations Analytics - Predictive Insights database table spaces and tables for the schema.



Note:

The installation script can install components only to the server on which it is running. Copy the installation package to the server on which you are installing the Database component.

Procedure

1.

As the database owner, root, or a user that is part of the same group as the database owner, for example, scadmin, open a terminal session on the server.

2.

Go to the directory that contains the extracted Operations Analytics -


3.

Run the command:

./install.sh -c

The IBM Installation Manager console installer is launched.

Note:

The console accepts both upper and lower case.

4.

Type 1 to Install and press Enter.

5.

Type 1 to select IBM Operations Analytics - Predictive Insights 1.3.3 and press

Enter.

6.

Type 1 to choose version to install and press Enter.

7.

Type n to select package and press Enter.

8.

Type a to accept license agreement and press enter

9.

Type n and press Enter.

10.

To change Shared Resources location type m, or else type n to accept the default location, and press Enter. The suggested default directory is

/opt/IBM/scanalytics/install_<user>/shared . The IBM Installation Manager can share components across products. Operations Analytics - Predictive

Insights does not share components with any other product. It is a requirement of the IBM Installation Manager that a shared directory is

40


provided when you install it. The shared directory must be unique for each user who installs the IBM Installation Manager on the same server.

11.

To change Packages location type m, or else type n to accept the default location, and press Enter. It is recommended that you use the default directory of /opt/IBM/scanalytics/install_<user>/installer. If you want to change the default Installation Directory, the directory must be unique for each user who installs the IBM Installation Manager on the same server. The IBM

Installation Manager displays all Operations Analytics - Predictive Insights components that can be installed.

12.

By default, all components are selected for installation. Deselect all components other than Database and type n. The IBM Installation Manager displays each distinct set of required details under a heading.

13.

Enter the connection details for the database. The Update to create DB on a

specific location

is an optional setting that you can use to specify an installation location for the database that is not the default DB2 location. The directory must exist and be owned by the DB2 instance user.

14.

If validation fails, type r to re-enter values, or else type n to continue

15.

Type i to install.

16.

Type f to finish.

17.

Type x to exit.

Installing the Analytics component

You must complete the following steps to install the Analytics component using the IBM

®



Make sure that you have copied the installation package to the server on which you are installing the Analytics component.

Make sure the server has the following prerequisites installed: v IBM InfoSphere Streams 3.2

v IBM Java SDK 7.0 build 2.6 SR5. This prerequisite is installed automatically when you install IBM

®

InfoSphere

®

Streams.

About this task

The Operations Analytics - Predictive Insights Analytics component can be installed by the InfoSphere Streams administrator, which was set to be scadmin during the InfoSphere Streams install, or by the root user.

Note:

The installation script can install components only to the server on which it is running. Copy the installation package to the server on which you are installing the component.

It is recommended that you use the same user account to install the Mediation tool and the Analytics component, that is, the InfoSphere Streams administrator.

The Operations Analytics - Predictive Insights Database component must be installed before the Analytics component can be installed. If you install the

Database and Analytics components together, the Installation Manager automatically completes the Database installation first.


41

Procedure

1.

As the scadmin or root user, open a terminal session on the server on which you want to install the Analytics component.

2.



3.

Run the command:

./install.sh -c


Note:


4.

If there is no other Operations Analytics - Predictive Insights component installed on the server or if a component was installed with a different user account to that which you are using to install the Analytics component, type 1 to Install and press Enter. The IBM Installation Manager displays the local installation packages. Complete steps a to m to install the Analytics component.

a.

The IBM Installation Manager displays the local installation packages. Type

1 to select IBM Operations Analytics - Predictive Insights 1.3.3 and press

Enter.

b.


c.


d.

Type a to accept license agreement and press Enter.

e.


f.

To change Shared Resources location type m, or else type n to accept the default location, and press Enter. The recommended default directory is

/opt/IBM/scanalytics/install_<user>/shared . The IBM Installation

Manager can share components across products. Operations Analytics -

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.

g.

To change Packages location type m, or else type n to accept the default location, and press Enter. It is recommended that you use the default directory of /opt/IBM/scanalytics/install_<user>/installer. If you want to change the default Installation Directory, 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

Operations Analytics - Predictive Insights components that can be installed.

h.

By default, all components are selected for installation. Deselect all components other than Analytics and type n. The IBM Installation Manager displays each distinct set of information required under a heading.

i.

Enter the connection details for your database as requested.

j.

If validation fail type r to re-enter values, or else type n to continue.

k.

Type i to install.

l.

Type f to finish.

m.

Type x to exit.

5.

If another IBM Operations Analytics - Predictive Insights component was installed on the server with the same user account that you are using to install the Analytics component, type 3 to Modify and press Enter. The IBM

Installation Manager displays the local installation packages. Complete steps a to f to install the Analytics component:

42


a.

Type 1 to select IBM Operations Analytics - Predictive Insights and press

Enter.

b.


c.

Type 2 to select the Analytics component and press Enter.

Note:

Any component that was previously installed is automatically checked. Do not deselect any component that was previously installed as this action causes the component to be uninstalled during the modify operation.

d.

Type n and press Enter to start the installation.

e.

Type f and press Enter when the modify operation is complete.

f.

Type x to exit.

Installing the UI component

You must complete the following steps to install the UI component using the IBM

®



Before you begin installing the UI component, ensure that the following are complete: v Both the Operations Analytics - Predictive Insights Database and Analytics components are installed.

v The Analytics component has OMNIbus forwarding configured. You can configure OMNIbus forwarding when installing the Analytics component or after with the configure_omnibus.sh script. For more information, see

Configuring OMNIbus alarm management in the Administering and Configuring

Guide.

v You have configured a domain name for the server. During the installation of the UI component, you need to specify a single sign-on domain.

v Either Tivoli Integrated Portal with WebGUI 7.4 or Dashboard Application

Services Hub with WebGUI 8.1, depending on which application you are using, is running. The UI installation process performs a restart of Tivoli Integrated

Portal or Dashboard Application Services Hub.

v You have copied the installation package to the server on which you are installing the UI component.

Note:

If you are integrating the UI component with Dashboard Application

Services Hub, you can install the UI on the same server as Dashboard Application

Services Hub or on a different server. If you are installing into an existing Tivoli

Integrated Portal environment, you must be on the Tivoli Integrated Portal server to install the Operations Analytics - Predictive Insights UI component.

Procedure

1.

Open a terminal session on the server on which you want to install the UI component.

2.



3.

Run the command:

./install.sh -c



43

Note:


4.

If there is no other Operations Analytics - Predictive Insights component installed on the server or if a component was installed with a different user account to that which you are using to install the UI component, type 1 to

Install and press Enter. The IBM Installation Manager displays the local installation packages. Complete steps a to p to install the UI component.

a.

Type 1 to select IBM Operations Analytics - Predictive Insights 1.3.3 and press Enter.

b.


c.


d.


e.


f.

To change Shared Resources location, type m, or else type n to accept the default location, and press Enter. The recommended default directory is




g.

To change Packages location type m, or else type n to accept the default location, and press Enter. It is recommended that you use the default directory of /opt/IBM/scanalytics/install_<user>/installer. If you choose to change default Installation Directory, 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

Operations Analytics - Predictive Insights components that can be installed.

h.

By default, all components are selected for installation. Deselect all components other than UI and type n. The IBM Installation Manager displays each distinct set of details required under a heading.

i.

Enter the connection details for your database as requested.

j.

If validation fails, choose r to re-enter values, or else type n to continue.

k.

Select the application you wish to use to display anomalies generated by

Operations Analytics - Predictive Insights. Type 1 to use Tivoli Integrated

Portal (TIP) or type 2 to use Dashboard Application Services Hub (DASH).

l.

Enter the details for the application you select.

m.

Type i to install.

n.

Type f to finish.

o.

Type x to exit.

5.

If another Operations Analytics - Predictive Insights component was installed on the server with the same user account that you are using to install the UI component, type 3 to Modify and press Enter. The IBM Installation Manager displays the local installation packages. Complete steps a to f to install the UI component.

a.


Enter.

b.


c.

Type 4 to select the UI component and press Enter.

d.


e.


44


f.

Type x to exit.

Installing the Mediation tool

The Operations Analytics - Predictive Insights Mediation tool is used to configure the data presentation to Operations Analytics - Predictive Insights. The Mediation tool can be installed on Windows or Linux systems.


Note:

The installation script can install components only to the server on which it is running.

Make sure that you have copied the installation package to the server on which you are installing the component.

It is recommended that you install the Mediation tool on the same server on which you installed the Analytics component.

Note:

If you are unable to gain access to a graphical display on the server hosting the Analytics component, you can install the Mediation tool on a Linux desktop system, or on a Windows desktop system. For details on installing the Mediation

tool on a Windows system, see “Installing the Mediation tool on Windows” on page 47. Installing to a Linux desktop system is performed in the same way as

described in the following procedure.

About this task

To install the Mediation tool in console mode, complete the following steps:

Procedure

1.

As the InfoSphere Streams administrator or root user, open a terminal session on the server on which you want to install the Mediation tool.

2.



3.

Run the command:

./install.sh -c


Note:


4.

If there is no other IBM Operations Analytics - Predictive Insights component installed on the server or if a component was installed with a different user account to that which you are using to install the Mediation tool, type 1 to

Install and press Enter. The IBM Installation Manager displays the local installation packages. Complete steps a to k to install the Mediation tool.

a.

Type 1 to select IBM Operations Analytics - Predictive Insights 1.3.3 and press Enter.

b.


c.


d.


e.


f.

To change Shared Resources location type m, or else type n to accept the default location, and press Enter. The recommended default directory is


45




g.

To change Packages location type m, or else type n to accept the default location, and press Enter. The recommended default directory is


. If you want to change the default Installation Directory, 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 Operations Analytics

- Predictive Insights components that can be installed.

h.

By default, all components are selected for installation. Deselect all components other than Mediation tool and type n. The IBM Installation

Manager displays each distinct set of information required under a heading.

i.

Type i to install.

j.

Type f to finish.

k.

Type x to exit.

5.

If another Operations Analytics - Predictive Insights component was already installed on this server with the same user account that you are using to install the Mediation tool, type 3 to Modify and press Enter. The IBM Installation

Manager displays the local installation packages. Complete steps a to f to install the Mediation tool.

a.


Enter.

b.


c.

Type 3 to select the Mediation tool and press Enter.

d.


e.


f.

Type x to exit.

Post-installation - System status

After installation, Operations Analytics - Predictive Insights is ready to configure into a working system.

The following elements are in place and ready to use when Operations Analytics -

Predictive Insights installation is complete: v The administration CLI is directly usable by the Linux user account that installed Operations Analytics - Predictive Insights, that is, the Operations

Analytics - Predictive Insights account, which is by default scadmin.

v OMNIbus columns are created in the Object Server.

v An OMNIbus mini-distribution is installed transparently as part of Operations

Analytics - Predictive Insights.

v The probe configuration files are updated to configure the connection to the

Object Server.

v A default set of probe rules file is installed. The rules file stores all relevant attributes in the Object Server database.

v The right-click menu is configured in OMNIbus WebGUI during the UI component installation.

46


v Access rights are granted to view events in Operations Analytics - Predictive

Insights. The way in which rights are granted depends on whether you installed

Operations Analytics - Predictive Insights into Tivoli Integrated Portal or

Dashboard Application Services Hub:

Tivoli Integrated Portal v Two new groups, predictiveInsightsUsers and predictiveInsightsAdmin, are created in Omnibus. By default, both groups have rights to view Operations

Analytics - Predictive Insights events.

v Two new user roles, predictiveInsightsAdmin and predictiveInsightsUser, are created in Tivoli Integrated Portal. By default, both roles have rights to view

Operations Analytics - Predictive Insights events. The Tivoli Integrated Portal administrator, usually tipadmin, is given both roles.

Dashboard Application Services Hub v Two existing Omnibus groups, Netcool_OMNIbus_User and

Netcool_OMNIbus_Admin , are granted rights to view Operations Analytics -

Predictive Insights events.

v The Dashboard Application Services Hub administrative user, ncoadmin, is added to the Netcool_OMNIbus_Admin group.

Note:

The password for the ncoadmin account defaults to the DASH profile user password, typically smadmin. However, if Tivoli Integrated Portal was previously installed on the server, the password for the ncoadmin account defaults to the tipadmin user password.

Installing the Mediation tool on Windows

The Operations Analytics - Predictive Insights Mediation tool can be installed on

Windows as well as Linux.

Procedure

Instructions on how to install the Mediation tool on Windows.

1.

Log on to the Windows environment to which you want to install the

Mediation tool.

2.

Extract the Operations Analytics - Predictive Insights package from the media.

3.

Open the windowsMediationTool folder within the extracted package. This folder contains the file PredictiveInsights-MediationTooling-1.3.3-win32.zip.

4.

Extract the ZIP file to your desired installation location.

5.

Open the folder to which you extracted the ZIP file, and in turn open the contained eclipse folder.

6.

Double click on the eclipse.exe icon. When you open the tool, you will be asked to choose a workspace. Choose a directory unique to the Mediation tool.


47

What to do next

The Operations Analytics - Predictive Insights installation is now complete, so what do you do next?

About this task

The full set of required post-installation configuration tasks are described in the section "Initial configuration of Operations Analytics - Predictive Insights" in the

Operations Analytics - Predictive Insights: Configuring documentation.

48


Chapter 4. Uninstalling Operations Analytics - Predictive

Insights

How to uninstall the Operations Analytics - Predictive Insights system.

Operations Analytics - Predictive Insights offers both an interactive and a silent uninstallation.

Uninstalling Operations Analytics - Predictive Insights

How to uninstall Operations Analytics - Predictive Insights.

About this task

If you distributed the installation of Operations Analytics - Predictive Insights components, that is, installed components on separate servers, you must uninstall components in the following order:

1.

UI

2.

Mediation tool

3.

Analytics

4.

Database

Note:

You must uninstall each component as the user that installed that component. If you distributed the installation of these components, log on to each of the servers and run the following steps.

Procedure

1.

Log on to the server as the appropriate user.

2.



3.


4.

Run ./install.sh

5.

Select Uninstall

6.

Click Next.

7.

Click the check box for Operations Analytics - Predictive Insights.

8.

Click Next.

The next panel displays all the components installed as the current user.

9.

For each component that you uninstall: a.

Enter the requested passwords.

b.

Click Validate.

c.

Click Next when all conditions have been satisfied.

10.

When all component selections have been validated, click Uninstall.


49

50


Chapter 5. Moving from Tivoli Integrated Portal to Dashboard

Application Services Hub

Operations Analytics - Predictive Insights version 1.3.3 supports Tivoli Integrated

Portal and Dashboard Application Services Hub as visualization applications for the UI.

About this task

Operations Analytics - Predictive Insights version 1.3.3 supports both Dashboard

Application Services Hub and Tivoli Integrated Portal for visualization purposes. If you are using Operations Analytics - Predictive Insights with Tivoli Integrated

Portal, you can move to Dashboard Application Services Hub at any time.

There are two ways to complete the move from Tivoli Integrated Portal to

Dashboard Application Services Hub. Follow one of the following scenarios:

Procedure

v Scenario 1 : Install Dashboard Application Services Hub on a separate server so you can run both Tivoli Integrated Portal and Dashboard Application Services

Hub in parallel.

Complete the steps in this scenario if you want to first confirm that your

Dashboard Application Services Hub functions as expected and you are ready to decommission the existing Tivoli Integrated Portal visualization component.

1.

Install IBM Jazz for Service Management 1.1.0.3 on a separate server. For

more information, see Installing Jazz for Service Management.

2.

Install the IBM Jazz for Service Management 1.1.1.0 fix pack.

3.

Install OMNIbus WebGUI on the same server as Jazz for Service

Management. For more information on how to install WebGUI, see

“Installing OMNIbus WebGUI” on page 24.

4.

Install the Operations Analytics - Predictive Insights version 1.3.3 UI component on the same server as Jazz for Service Management and configure it to work with the new Dashboard Application Services Hub. For more

information, see “Installing the UI component” on page 35.

5.

When you are ready to decommission the existing Tivoli Integrated Portal visualization component, uninstall the following:

– Operations Analytics - Predictive Insights UI component, that is configured to work with Tivoli Integrated Portal

– OMNIbus WebGUI 7.4.

– Tivoli Integrated Portal 2.2

v Scenario 2 : Install Dashboard Application Services Hub o the server on which you currently run Tivoli Integrated Portal.

Complete this procedure if you want to install Dashboard Application Services

Hub on the server which currently hosts Tivoli Integrated Portal.

1.

Stop Tivoli Integrated Portal. For more information on how to stop Tivoli

Integrated Portal, see Stopping Tivoli Integrated Portal in the Configuring and

Administering Guide.


51

2.

Install IBM Jazz for Service Management 1.1.0.3 on the Tivoli Integrated

Portal server. For more information, see Installing Jazz for Service Management in the Installation Guide.

3.

Install the IBM Jazz for Service Management 1.1.1.0 fix pack.

4.

Uninstall Operations Analytics - Predictive Insights. For more information,

see Chapter 4, “Uninstalling Operations Analytics - Predictive Insights,” on page 49.

5.

Reinstall Operations Analytics - Predictive Insights. When you are installing the UI component, configure it to work with the Dashboard Application

Services Hub.

What to do next

Follow the post install configuration steps in the Initial configuration of Operations

Analytics - Predictive Insights section of the Configuring and Administering Guide to complete the setup of Dashboard Application Services Hub. In particular, ensure that you update your system so that Dashboard Application Services Hub is prepared for an unplanned shut down.

52


Chapter 6. Installation log files

The log files that are created during the installation of Operations Analytics -


The installation log file: /tmp/tasp_install_<user><date>.log

The command-line interface log file: $PI_HOME/log/cli/cli_trace.log.

Where $PI_HOME is the installation location of the analytics component.


53

54


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM

Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law

IBM Japan, Ltd.

1623-14, Shimotsuruma, Yamato-shi

Kanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.


55

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement,

IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources.

IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.

Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to

IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to

IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM‘s application programming interfaces.

56


If you are viewing this information in softcopy form, the photographs and color illustrations might not be displayed.

Notices

57

58


Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of

International Business Machines Corp., registered in many jurisdictions worldwide.

Other product and service names might be trademarks of IBM or other companies.

A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at http://www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Cell Broadband Engine and Cell/B.E. are trademarks of Sony Computer

Entertainment, Inc., in the United States, other countries, or both and is used under license therefrom.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,

Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

IT Infrastructure Library is a registered trademark of the Central Computer and

Telecommunications Agency which is now part of the Office of Government

Commerce.

ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark

Office.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of

Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

For trademark attribution, visit the IBM Terms of Use Web site

(http://www.ibm.com/legal/us/).


59

60


IBM®

Printed in USA

IBM 1.3.3 Operations Analytics - Predictive Insights Installation Guide

Assistant Bot

IBM Operations Analytics - Predictive Insights 1.3.3

Installation Guide

Contents

Preface

Audience

Components

Chapter 1. Introduction

Chapter 2. Preparing to install

Checking the installation prerequisites

Adding the required users

Configuring fully qualified domain names for servers

Setting ulimits

Installing KSH and required libraries for Operations Analytics -

Predictive Insights

Installing the prerequisite software

DB2

InfoSphere Streams

Jazz for Service Management

Netcool/OMNIbus

Chapter 3. Installing Operations Analytics - Predictive Insights

Selecting user accounts to install components

Creating the installation directory

Setting the JAVA_HOME variable

Installing Operations Analytics - Predictive Insights on a single server

Installing Operations Analytics - Predictive Insights on multiple servers

Installation order for a distributed installation

GUI installation

Console Installation

Post-installation - System status

Installing the Mediation tool on Windows

What to do next

Chapter 4. Uninstalling Operations Analytics - Predictive

Insights

Uninstalling Operations Analytics - Predictive Insights

Chapter 5. Moving from Tivoli Integrated Portal to Dashboard

Application Services Hub

Chapter 6. Installation log files

Notices

Trademarks

IBM®

Key Features

Frequently Answers and Questions

What are the prerequisites for installing Operations Analytics - Predictive Insights?

How do I install Operations Analytics - Predictive Insights?

How do I configure Operations Analytics - Predictive Insights?

Related manuals

IBM

1.3.6 Operations Analytics Predictive Insights

IBM

Predictive Insights

365iD

Portal Scanner Another Location

IBM

1.3.5

IBM

1.3

IBM

1 Release 4.0.3

IBM

V1 Release 4.0.4

IBM

IBM Intelligent Operations Center

IBM

1 Release 4

IBM

IBM Monitoring

IBM

Cloud Application Performance Management

IBM

6.4.2

Table of contents