IBM Netcool Operations Insight Version 1.4 Deployment Guide
IBM Netcool Operations Insight Version 1.4 Deployment Guide
IBM Netcool Operations Insight Version 1.4 Deployment Guide
Shaker Al-Muaber
Fernando de Andrade Cavalcanti
Vasfi Gucer
Mario Schuerewegen
Steven Shuman
Redbooks
International Technical Support Organization
July 2016
SG24-8365-00
Note: Before using this information and the product it supports, read the information in Notices on page v.
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Now you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Stay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
This information was developed for products and services offered in the US. This material might be available
from IBM in other languages. However, you may be required to own a copy of the product or product version in
that language in order to access it.
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 users 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 grant you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, MD-NC119, Armonk, NY 10504-1785, US
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 websites are provided for convenience only and do not in any
manner serve as an endorsement of those websites. The materials at those websites are not part of the
materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you provide in any way it believes appropriate without
incurring any obligation to you.
The performance data and client examples cited are presented for illustrative purposes only. Actual
performance results may vary depending on specific configurations and operating conditions.
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.
Statements regarding the IBM future direction or intent are subject to change or withdrawal without notice, and
represent goals and objectives only.
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 actual people or business enterprises 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. The sample programs are
provided AS IS, without warranty of any kind. IBM shall not be liable for any damages arising out of your use
of the sample programs.
The following terms are trademarks or registered trademarks of International Business Machines Corporation,
and might also be trademarks or registered trademarks in other countries.
DB2 Netcool Redbooks (logo)
IBM Passport Advantage Tivoli
Jazz Redbooks WebSphere
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.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency
which is now part of the Office of Government Commerce.
Java, and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its
affiliates.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, or service names may be trademarks or service marks of others.
Download
Android
iOS
Now
IBM Netcool Operations Insight integrates infrastructure and operations management into
a single coherent structure across business applications, virtualized servers, network devices
and protocols, internet protocols, and security and storage devices. This IBM Redbooks
publication will help you install, tailor, and configure Netcool Operations Insight Version 1.4.
Netcool Operations Insight consists of several products and components that can be installed
on many servers in many combinations. You must make many decisions, both critical and
personal preference. The purpose of this document is to accelerate the initial deployment of
Netcool Operations Insight by making preferred practice choices.
The target audience of this book is Netcool Operations Insight deployment specialists.
Authors
This book was produced by a global team of specialists working with the International
Technical Support Organization (ITSO) in Austin, Texas.
Bill Cain, Rob Clark, Jim Carey, Brian Fabec, Mark Simpson
IBM US
Zane Bray
IBM UK
Find out more about the residency program, browse the residency index, and apply online at:
ibm.com/redbooks/residencies.html
Comments welcome
Your comments are important to us!
We want our books to be as helpful as possible. Send us your comments about this book or
other IBM Redbooks publications in one of the following ways:
Use the online Contact us review Redbooks form found at:
ibm.com/redbooks
Send your comments in an email to:
[email protected]
Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400
Preface xi
xii IBM Netcool Operations Insight Version 1.4: Deployment Guide
1
Netcool Operations Insight consists of a base solution for managing and analyzing
application monitoring environments and also an optional extension that is called Networks
for Operations Insight. This optional extension widens the scope to include network
discovery, visualization, event correlation, topology-based root-cause analysis, and
configuration and compliance management. The Networks for Operations Insight capability is
provided through the Network Manager and Netcool Configuration Manager products.
In addition, you can also set up IBM Network Performance Insight as part of your Netcool
Operations Insight solution to monitor network traffic performance, and you can integrate with
further solutions, such as IBM Alert Notification and IBM Runbook Automation.
Netcool Operations Insight integrates infrastructure and operations management into a single
coherent structure across business applications, virtualized servers, network devices and
protocols, internet protocols, and security and storage devices.
The Tivoli Netcool/OMNIbus Insight Pack is installed in Operations Analytics - Log Analysis
and provides custom apps that search the events based on various criteria. The custom apps
can generate dashboards that present event information to show how your monitoring
environment is performing over time. With keyword searches and dynamic drill-down
functions, you can go deeper into the event data for detailed information. The apps can be run
from the Operations Analytics - Log Analysis.
Tooling can be installed into the Web GUI that launches the apps from the right-click menus of
the Event Viewer and the Active Event List. An event reduction wizard is also supplied that
includes information and apps that can help you analyze and reduce volumes of events and
minimize the noise in your monitored environment.
This integrated, security-rich platform helps people engage with networks of experts in the
context of critical business processes. Now, everyone can act with confidence and anticipate
and respond to emerging opportunities.
IBM Dashboard Application Services Hub (DASH) service is a common web portal for IBM
Netcool suite. When you log in to the DASH, you will get access to the Content Page,
OMNIbus Web GUI, Network Manager topology views, discovery configuration, and other
integrations.
4. Click the Discovery folder, as shown in Figure 1-6, to open the Network Discovery
Configuration page and the Network Discovery Status page. The pages are the same
pages that were in Tivoli Integrated Portal.
5. Click the Incident folder, as shown in Figure 1-8, to open OMNIbus Web GUI views and
Network views. You can navigate through the Event Dashboard, Event List, and Active
Event List (AEL), and work with OMNIbus events. You can navigate through the Network
views, Hop view, Health view, Fault-Finding view, Simple Network Management Protocol
(SNMP) Management Information Base (MIB) Browser view, and real-time graphing.
9. Click the Insights folder (Figure 1-12) to open the analytics pages:
Seasonal Events
Related Events
Both pages are empty after installation and require configuration. Statistical analysis of
Tivoli Netcool/OMNIbus historical event data is shown here. Insights can identify seasonal
patterns, such as when and how frequently events occur.
10.Click the Reporting folder icon (Figure 1-14) to navigate through tens of predefined
reports that are installed and ship with the Netcool Operations Insight components.
Reports are built on top of the IBM Tivoli Common Reporting engine. You get OMNIbus
historical reports as part of the OMNIbus installation, which is used by the analytics
engine. Approximately 55 reports for Tivoli Network Manager are available if you install the
product. For Tivoli Netcool Configuration Manager, approximately 15 reports about
compliance and security are available. Moreover, a customized report is available by using
the Report Studio tool.
12.Click the Configurations folder icon to open the IBM Tivoli Netcool Configuration
Manager (ITNCM) base and compliance GUI. See Figure 1-16. You still get the JNLP
application when you click one of the applications.
14.Click Impact to open the Netcool Impact GUI. See Figure 1-18. Impact is a core
component for Netcool Operations Insight. All enhancements and event analytics depend
on it.
For more information about Netcool Operations Insight, see the following Redbooks
publications, which include actual product scenarios and use cases:
Improving Operations Effectiveness and Efficiency with IBM Netcool Operations
Insight: A Scenarios Guide, SG24-8352
Delivering Consistency and Automation with Operational Runbooks, REDP-5347
1.4 Architecture
This section shows the high-level architecture of the environment that was used in this book.
It also includes other details, such as the necessary IBM DB2 instances and the
relationships and connections among the Netcool Operations Insight components.
GUI
NCM-A (LIC)
DBServ-A
172.16.61.202 GUI 172.16.61.137
GUI
TO
DB2 FROM
(CONF) Omni-A Omni-B NCM
GUI 172.16.61.131 172.16.61.132
NCM_B DBServ-B
172.16.61.203 172.16.61.138
DIS_1 DIS_2
ITNM-A
172.16.61.140
Impact-A
172.16.61.135
COL_P_1 COL_B_1
In Figure 1-19, JazzSM is deployed for HA. It collects data from the following sources:
Network Manager servers
Netcool Configuration Manager
Netcool Impact
DB2
IBM Operations Analytics - Log Analysis
Netcool/OMNIbus
Table 1-1 Main ports that are used for Netcool Operations Insight
Netcool Operations Insight component Port used
Impact 16311
Note: The Network Configuration Manager ports are not included in Table 1-1 because
Network Configuration Manager was not part of the basic deployment that we performed in
this book. The ports for Network Configuration Manager will be mentioned in 2.8, IBM
Netcool Configuration Manager on page 175.
AGG 4100
Https 9987
OQL 7968
Http / https 16310 -16
Https 16311
IOALA-A
9987
AGG
ITNM-A ITNM-B 4100
DIS
Omni-A 4102 DIS
7968 7968 Omni-B
4102
AGG
4100
COL
4101 COL
4101
Impact-A Impact-B 16311
16311
Event
Sources
Figure 1-21 Ports that are used to connect the Netcool Operations Insight components
In addition to these environment-specific ports, each product also uses other ports. A full list
of ports that are used for each product is available in the IBM Knowledge Center
documentation for each product:
https://ibm.biz/BdrFcE
Figure 1-23 Full list of ports that are used for Network Manager deployment
1.4.4 Usernames and passwords that are used for each component
The usernames and passwords that are used in our deployment for each component of
Netcool Operations Insights are listed.
Important: Do not create smadmin in the LDAP server because Jazz requires that the
username variables are unique across all repositories. The smadmin username is a fixed
internal FileBased variable.
Netcool Omnibus
Table 1-6 lists the Netcool Omnibus users.
2.1.1 Introduction
This section covers the basic installation of Installation Manager only. Installation Manager is
required to be installed in all servers that are used in the environment of this book. As a
preferred practice, follow the standard settings in Table 2-1 for the remainder of this book
when you install Installation Manager in each server.
Note: Installation Manager replaces the Deployment Engine (DE) that was used to install
the previous versions of the Netcool products.
We will install the Installation Manager by using the groupinst command. Other options are
described in the following link if you need further information:
https://ibm.biz/Bdrr5e
Example 2-1 Preparing the environment for the Installation Manager installation
# As root user:
#-------------
# Assuming netcool user has not been created yet:
groupadd ncoadmin
useradd -c "Netcool User" -g ncoadmin netcool
mkdir -p /opt/IBM/netcool
cd /opt
chown -R netcool:ncoadmin IBM
# As netcool user:
# ----------------
cd /opt/IBM/netcool
mkdir IM
cd IM
mkdir -p InstallationManager/eclipse
mkdir IBMIMData
mkdir IBMIMShared
cd /opt/IBM/netcool
mkdir core NcKL
When you run Installation Manager in group mode as we did in Example 2-2, you might see
the following error when you start Installation Manager, Locking is not possible in the
directory when running in group mode. This error is a known error, and it is described in
the following technote:
https://ibm.biz/BdrD7R
Example 2-3 shows the commands that must be executed to avoid the issue that is described
in the previous URL.
Note: The issue that is described in the URL was seen in Installation Manager 1.8.4. It is
possible that you will not experience the same issue in recent versions of Installation
Manager.
Example 2-3 Changing file permissions after the Installation Manager installation
# As root:
# --------
chmod 777
/opt/IBM/netcool/IM/InstallationManager/eclipse/configuration/org.eclipse.core.run
time/.manager/.fileTableLock
chmod 777
/opt/IBM/netcool/IM/InstallationManager/eclipse/configuration/org.eclipse.equinox.
app/.manager/.fileTableLock
2.1.4 Verification
To verify the Installation Manager installation, you can try to register repositories in Installation
Manager.
Tip: If the top-level directory contains both the repository.config file and the
groupinst command, this directory is the Installation Manager installation media. Look
for a subdirectory that contains the actual repository.
Important: The script must be run as the root user. The DB2 prerequisites tool is in the
DB2 installation image.
Tip: In the last line of Example 2-5 on page 28, the db2prereqcheck output states Then,
run db2_install. However, we install DB2 by using db2setup, not db2_install.
A few required files are missing. DB2 requires the dapl sg3_utils, sg_persist libstdc++,
rdma.noarch pam.i686, and glibc-utils.x86 files. You can install these files by using the yum
install command in Linux.
You need to set the ulimit on the operating system as shown in Example 2-6 and in
Example 2-7.
Configuring Linux
You need to disable SELINUX in the /etc/selinux/config file, as shown in Example 2-7.
Note: Depending on the type of Linux that you use, the nproc configuration can also be in
/etc/security/limits.conf.
2. As shown in Figure 2-2, click I accept the terms in the license agreement. Click Next.
2.2.4 Verification
To verify the DB2 installation, as the db2inst1 user, try to start and stop DB2 with the
db2start and db2stop commands. The path for these commands is
/home/db2inst1/sqllib/adm/.
2.3.1 Introduction
Netcool/OMNIbus comes with a set of predefined requirements for the operating system. To
verify the requirements that are needed for the installation of each Netcool Operations Insight
component, we use the IBM Prerequisite Scanner, which is documented at the following
website:
https://ibm.biz/Bdrr5b
Follow the instructions at the website to download the IBM Prerequisite Scanner. You must
download it and extract the files in the package before you can use it.
$NCHOME /opt/IBM/tivoli/netcool/
$OMNIHOME /opt/IBM/tivoli/netcool/omnibus
Machine Information
Machine name: Omni-A
Serial number: VMware-42 16 c7 bb 11 31 ef 63-35 bc 57 c1 01 c6 cd fb
2. Install each of the missing packages until you get the overall result of PASS. Example 2-12
shows how to fix this problem in a Linux environment.
3. After you install the missing packages and fix any other errors, rerun the prerequisite
checker script.
4. After all of the prerequisites are fulfilled, the following message is shown at the end of the
scripts execution:
Overall result: PASS (NOC 08010000: PASS)
3. As shown in Table 2-4, add multiple repositories that are included in the following source
files:
OMNIbus-v8.1.0.5-Core.linux64.zip, which is the core package for OMNIbus,
including Fix Pack 5 (FP5)
8.1.0-TIV-OMNIbusCore-linux-x86_64-FP0007.zip, which is Fix Pack 7 (FP7)
OMNIbus-v8.1.0.5-Core.linux64.zip <EXTRACTED_DIR>/Base/OMNIbusRepository
8.1.0-TIV-OMNIbusCore-linux-x86_64-FP0007.zip <EXTRACTED_DIR>/OMNIbusRepository/composite
Note: For the next few steps, until step 8 of this procedure, OMNIbus Core plus FP5 was
installed in advance. Therefore, the window captures show only the steps to upgrade to
FP7 because they are similar to the clean installation.
6. In the main Installation Manager window, because OMNIbus Core plus FP5 was installed
in advance, click Update (Figure 2-14 on page 44). For the initial installation of OMNIbus
Core plus FP5, we selected Install on this step.
Note: For more information about the multitiered environment, see the following link:
https://ibm.biz/BdrRn4
6. Enter the settings for the Aggregation layer and click Next (Figure 2-26).
10.Review the Apply the configuration window and click Next (Figure 2-30).
Follow these steps to install and configure the Backup OMNIbus server, Omni-B:
1. After you complete the steps in the Primary OMNIbus server, you must install and
configure the Backup OMNIbus server, Omni-B. Repeat the steps of the Installing
OMNIbus on page 44. When you are ready to perform the basic configuration (Initial
configuration on page 50), instead of selecting Create a new configuration, select Apply
an existing configuration in this computer.
2. Ensure that the deployment_descriptor.xml file is copied from the Primary OMNIbus
server to the Backup OMNIbus server. Click Next (Figure 2-31), and browse to locate the
XML file in the Backup OMNIbus server.
3. Complete the steps of the wizard to finish the configuration of the Backup OMNIbus
server, Omni-B.
After you start the ObjectServer, you can run the following command to confirm that the
nco_objserv process is running:
The properties file, default database tables, default data, default users, default groups, and
default roles are created for the ObjectServer. The SQL customization is also applied. If the
ObjectServer name ends in _B (based on the naming conventions), the backup ObjectServer
property is automatically set to TRUE and the corresponding automations that are required by
the backup ObjectServer are enabled.
2. Start the gateway. Example 2-19 shows how to start the gateway AGG_GATE.
The properties file, and the default database tables, data, users, groups, and roles are
created for the ObjectServer. The SQL customization is also applied.
cp $NCHOME/omnibus/extensions/multitier/gateway/C_TO_A_GATE_P_1.* \
$NCHOME/omnibus/etc/.
Initialize the ObjectServer COL_B_1 and apply the SQL import file to apply to this
ObjectServer (Example 2-24).
The properties file, and the default database tables, data, users, groups, and roles are
created for the ObjectServer. The SQL customization is also applied.
Copy the multitiered property files for the gateway to the default location where configuration
and properties files are held (Example 2-26).
cp $NCHOME/omnibus/extensions/multitier/gateway/C_TO_A_GATE_B_1.* \
$NCHOME/omnibus/etc/.
Note: The -dsdprimary command-line option is set to the name of the virtual ObjectServer
pair in the aggregation layer. See Example 2-28.
The properties file, and the default database tables, data, users, groups, and roles are
created for the ObjectServer. The ObjectServer is created as a desktop ObjectServer with
dual-write mode enabled. The SQL customization is also applied.
cp $NCHOME/omnibus/extensions/multitier/gateway/A_TO_D_GATE.tblrep.def \
$NCHOME/omnibus/etc/.
cp $NCHOME/omnibus/extensions/multitier/gateway/A_TO_D_GATE_1.props \
$NCHOME/omnibus/etc/.
2. Start the gateway. Example 2-31 shows how to start the gateway A_TO_D_GATE_1.
The properties file, and the default database tables, data, users, groups, and roles are
created for the ObjectServer. The ObjectServer is created as a desktop ObjectServer with
dual-write mode enabled. The SQL customization is also applied.
cp $NCHOME/omnibus/extensions/multitier/gateway/A_TO_D_GATE.tblrep.def \
$NCHOME/omnibus/etc/.
cp $NCHOME/omnibus/extensions/multitier/gateway/A_TO_D_GATE_2.props \
$NCHOME/omnibus/etc/.
2. Start the gateway. Example 2-35 shows how to start the gateway A_TO_D_GATE_2.
For more information about this configuration, see the following link:
https://ibm.biz/Bdrr5p
Use the following steps to configure the historical event database in the environment.
Note: In our scenario, we deploy the JDBC gateway in Omni-A where the Primary
ObjectServer, AGG_P, is running. Another option is to install the JDBC gateway in the DB2
server where the REPORTER database will be located.
Tip: One of the features of Installation Manager is that all platforms can be shipped in a
single compressed file, which means that you do not need to select the platform that you
require. Installation Manager selects the platform for you.
4. Figure 2-32 shows the JDBC gateway repositories that are imported to Installation
Manager.
6. Review the installation summary and complete the installation (Figure 2-34).
If DB2 is installed in the DB_A server, proceed with the following steps:
1. Copy the file $OMNIHOME/gates/reporting/db2/db2.reporting.old.sql from Omni-A to
the DB_A server.
Note: The file name is db2.reporting.old.sql. This script has additional code that is
needed to create the REPORTER database.
2. Create the gateway user in the AGG_P server with password netcool. If you need more
information about how to create a user in OMNIbus, see the following link:
https://ibm.biz/Bdrr58
# Table properties
Gate.Jdbc.StatusTableName: 'REPORTER_STATUS' # STRING (Target table for alerts.status)
Gate.Jdbc.JournalTableName: 'REPORTER_JOURNAL' # STRING (Target table for alerts.journal)
The Tivoli Netcool/OMNIbus process control system: The process control system
performs two primary tasks. It manages local and remote processes, and it runs external
procedures that are specified in automations. You can use process control to simplify the
management of Tivoli Netcool/OMNIbus components, such as ObjectServers, probes, and
gateways. You can install process agents (PA) on each host and configure them to
manage processes.
The configured process agents cooperate automatically and understand their own
configuration. They start processes, and they can keep those processes running. You can
define processes that are dependent on other processes, and processes that have timed
threshold dependencies. If a managed host is restarted, the process agent can be
configured to restart local components automatically.
In this deployment scenario, the PA needs to be configured on all servers that carry an
Omnibus component, which are Omni-A and Omni-B in our environment.
3. Create the configuration files for Tivoli Netcool/OMNIbus services by running the following
commands (Example 2-41).
4. As the netcool user, copy the configuration files by running the following commands
(Example 2-42).
5. Configure the props file by appending the following lines (Example 2-43).
6. Configure the OMNI_A_PA.conf file. Example 2-44 shows how you need to configure the
.conf file.
Note: The SCALAGateway configuration is included in Example 2-44 for later usage.
nco_process 'ColObjectServer_P_1'
{
Command '$OMNIHOME/bin/nco_objserv -name COL_P_1 -pa OMNI_A_PA' run as
1001
Host = 'Omni-A'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'
RetryCount = 0
ProcessType = PaPA_AWARE
}
nco_process 'DispObjectServer_1'
{
Command '$OMNIHOME/bin/nco_objserv -name DIS_1 -pa OMNI_A_PA' run as 1001
Host = 'Omni-A'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'
RetryCount = 0
ProcessType = PaPA_AWARE
}
nco_process 'ColToAggP_1'
{
Command '$OMNIHOME/bin/nco_g_objserv_uni -propsfile
$OMNIHOME/etc/C_TO_A_GATE_P_1.props' run as 1001
Host = 'Omni-A'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'
RetryCount = 0
ProcessType = PaPA_AWARE
}
nco_process 'AggToDisp_1'
{
nco_process 'JDBCGateway'
{
Command '$OMNIHOME/bin/nco_g_jdbc -propsfile $OMNIHOME/etc/G_JDBC.props'
run as 1001
Host = 'Omni-A'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'
RetryCount = 0
ProcessType = PaPA_AWARE
}
nco_process 'SCALAGateway'
{
Command '$OMNIHOME/bin/nco_g_xml -propsfile
$OMNIHOME/gates/xml/scala/G_SCALA.props' run as 1001
Host = 'Omni-A'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'
RetryCount = 0
ProcessType = PaPA_AWARE
}
#
# List of Services.
#
nco_service 'Core'
{
ServiceType = Master
ServiceStart = Auto
process 'AggObjectServer_P' NONE
process 'ColObjectServer_P_1' NONE
process 'DispObjectServer_1' NONE
process 'ColToAggP_1' 'AggObjectServer_P'
process 'AggToDisp_1' 'AggObjectServer_P'
process 'JDBCGateway' 'AggObjectServer_P'
process 'SCALAGateway' 'AggObjectServer_P'
}
nco_service 'InactiveProcesses'
{
#
# Routing Table Entries.
#
# 'user' - (optional) only required for secure mode PAD on target host
# 'user' must be member of UNIX group 'ncoadmin'
# 'password' - (optional) only required for secure mode PAD on target host
# use nco_pa_crypt to encrypt.
nco_routing
{
host 'Omni-B.swg.be.ibm.com' 'OMNI_B_PA'
host 'Omni-A' 'OMNI_A_PA'
}
Note: Ensure that you stop any Netcool processes that are running before you restart the
PA.
Note: Due to a current known issue in RedHat 7 where the nco.service is not configured
correctly, this method does not start the PA. If you use RedHat 7, until this issue is
resolved, use the second method to start PA.
Call the nco_pad with all of the arguments as the root user. See Example 2-46.
Tip: You can also install the history gateway on the Tivoli Data Warehouse server.
Start a process:
nco_pa_start -server OMNI_A_PA -user netcool -password object00 -process
AggObjectServer_P
Stop a process:
nco_pa_stop -server OMNI_A_PA -user netcool -password object00 -process
AggObjectServer_P
Stop PA:
nco_pa_shutdown -server OMNI_A_PA -user netcool -password object00
9. Repeat steps 1 - 7 for the backup ObjectServer, Omni-B. When you run the steps, replace
OMNI_A_PA with OMNI_B_PA.
10.Also, you neeed to make a few changes in the OMNI_B_PA.conf file in your environment.
Example 2-48 shows the differences in OMNI_B_PA in our environment in bold.
#
# List of Processes.
#
nco_process 'AggObjectServer_B'
{
Command '$OMNIHOME/bin/nco_objserv -name AGG_B -pa OMNI_B_PA' run as 1001
Host = 'Omni-B'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'
RetryCount = 0
ProcessType = PaPA_AWARE
}
nco_process 'ColObjectServer_B_1'
{
Command '$OMNIHOME/bin/nco_objserv -name COL_B_1 -pa OMNI_B_PA' run as
1001
Host = 'Omni-B'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
nco_process 'DispObjectServer_2'
{
Command '$OMNIHOME/bin/nco_objserv -name DIS_2 -pa OMNI_B_PA' run as 1001
Host = 'Omni-B'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'
RetryCount = 0
ProcessType = PaPA_AWARE
}
nco_process 'ColToAggB_1'
{
Command '$OMNIHOME/bin/nco_g_objserv_uni -propsfile
$OMNIHOME/etc/C_TO_A_GATE_B_1.props' run as 1001
Host = 'Omni-B'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'
RetryCount = 0
ProcessType = PaPA_AWARE
}
nco_process 'AggToDisp_2'
{
Command '$OMNIHOME/bin/nco_g_objserv_uni -propsfile
$OMNIHOME/etc/A_TO_D_GATE_2.props' run as 1001
Host = 'Omni-B'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'
RetryCount = 0
ProcessType = PaPA_AWARE
}
nco_process 'AggregationGateway'
{
Command '$OMNIHOME/bin/nco_g_objserv_bi -propsfile
$OMNIHOME/etc/AGG_GATE.props' run as 1001
Host = 'Omni-B'
Managed = True
RestartMsg = '${NAME} running as ${EUID} has been restored on
${HOST}.'
AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'
RetryCount = 0
ProcessType = PaPA_AWARE
}
nco_service 'InactiveProcesses'
{
ServiceType = Non-Master
ServiceStart = Non-Auto
}
#
# Routing Table Entries.
#
# 'user' - (optional) only required for secure mode PAD on target host
# 'user' must be member of UNIX group 'ncoadmin'
# 'password' - (optional) only required for secure mode PAD on target host
# use nco_pa_crypt to encrypt.
nco_routing
{
host 'Omni-B.swg.be.ibm.com' 'OMNI_B_PA'
host 'Omni-A' 'OMNI_A_PA'
}
2.3.4 Verification
Perform the following steps to verify the installation:
1. Example 2-49 shows the complete $OMNIHOME/etc/omni.dat for this environment
(including the G_SCALA configuration that will be performed later in this book). Review
the omni.dat file in Omni-A and Omni-B to confirm that they are correct.
2. If any event sources point to your Netcool Operations Insight environment, configure them
to the COL_P OMNIbus server. If you need to perform initial tests, use the Simnet Probe
to send sample alerts:
a. Append the following line to the $OMNIHOME/probes/linux2x86/simnet.props file:
Server : 'COL_P_1'
b. Start the probe (Example 2-50).
3. To view the events, you can start an Event List. For more information about monitoring
events, see the following link:
https://ibm.biz/Bdrr5g
2.4.1 Introduction
Netcool Impact offers a set of predefined requirements for the operating system. These
requirements are documented on the IBM documentation server:
https://ibm.biz/Bdrr5b
The IBM Prerequisite Scanner (version 1.2.0.17 in this book) checks these requirements
against the installed operating system. For this deployment, the settings that are shown in
Table 2-6 were used.
$IMPACT_HOME /opt/IBM/tivoli/netcool/impact/
Important: The Prerequisite Scanner must be run by the same user that installs the
products.
Tip: In the export IMPACT_PREREQ_BOTH parameter, TRUE means check for both Netcool
Impact and Impact GUI and FALSE means check for Netcool Impact only.
Machine Information
Machine name: Impact-a
Serial number:
sudo su -
yum install libgcc.i686 glibc.i686
Tip: If you see unexpected results, check the following logs to help in troubleshooting:
$IMPACT_HOME/logs/impactserver.log
$IMPACT_HOME/logs/guiserver.log
As shown in Table 2-7, multiple repositories are included in the following source files:
Impact-v7.1.0.4.linux64.zip is the core package for Impact.
Impact-v7.1.0.4-NOI.linux64.zip is the Netcool Operations Insight extensions
package.
7.1.0-TIV-NCI-LINUX-FP0005.zip is Fix Pack 5.
Impact-v7.1.0.4.linux64.zip <EXTRACTED_DIR>/ImpactRepository/disk1
Impact-v7.1.0.4-NOI.linux64.zip <EXTRACTED_DIR>/ImpactRepository/disk1
Impact-v7.1.0.4-NOI.linux64.zip <EXTRACTED_DIR>/ImpactExtRepository/disk1
7.1.0-TIV-NCI-LINUX-FP0005.zip <EXTRACTED_DIR>/ImpactRepository/disk1
7.1.0-TIV-NCI-LINUX-FP0005.zip <EXTRACTED_DIR>/ImpactExtRepository/disk1
Note: The ObjectServer repository is used for the initial configuration of Impact only. Later,
we configure the Lightweight Directory Access Protocol (LDAP) repository and use it
instead. Then, we remove the ObjectServer repository.
Click Next.
Note: Ignore the error about the nameserver that cannot be found.
Tip: The instance name is different, but both configurations use the same cluster name.
Note: You can ignore the error to connect to the backup ObjectServer in Figure 2-51 if you
know that the backup ObjectServer is not running.
Impact NameServer
You can check the running nameserver cluster through this URL:
http://impact-a.swg.be.ibm.com:9080/nameserver/services
2.5.1 Introduction
Network Manager comes with a set of predefined requirements for the operating system.
These requirements are documented on the IBM documentation server:
https://ibm.biz/BdrrNb
The IBM Prerequisite Scanner (version 1.2.0.17 in this book) will check these requirements
against the installed operating system.
Note: The prerequisite configuration file for Tivoli Network Manager 4.2 is included in IBM
Prerequisite Scanner 1.2.0.18. You can refer to the following Quick Start Guide for
Prerequisite Scanner 1.2.0.18:
https://ibm.biz/BdrrNg
$NCHOME /opt/IBM/netcool/core
$ITNMHOME $NCHOME/precision
Machine Information
Machine name: itnm-a
Serial number: VMware-42 16 f2 60 a4 6d 2c da-e2 e8 2f f4 d0 d9 b0 51
2.5.3 Installation
Follow these steps:
1. Before you install the Network Manager core, extract the db2_creation_scripts.tar.gz
DB2 creation scripts into a temporary folder on the DB2 database server
DBServ-a.swg.be.ibm.com, as shown in Example 2-54. You can find this file in the top
directory of the ITNM repository.
You can issue database manager commands and SQL statements from the command
prompt. For example:
db2 => connect to sample
db2 => bind sample.bnd
To exit db2 interactive mode, type QUIT at the command prompt. Outside
interactive mode, all commands must be prefixed with 'db2'.
To list the current command option settings, type LIST COMMAND OPTIONS.
db2 =>
Database Connection Information
db2 => db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => DB20000I The SQL command completed successfully.
db2 => db2 => DB20000I The SQL command completed successfully.
db2 => db2 => DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully.
SQL1362W One or more of the parameters submitted for immediate modification
were not changed dynamically. Client changes will not be effective until the
next time the application is started or the TERMINATE command has been issued.
Server changes will not be effective until the next DB2START command.
db2 => DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully.
db2 => db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
SQL1363W One or more of the parameters submitted for immediate modification
were not changed dynamically. For these configuration parameters, the database
must be shut down and reactivated before the configuration parameter changes
become effective.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
SQL1363W One or more of the parameters submitted for immediate modification
were not changed dynamically. For these configuration parameters, the database
must be shut down and reactivated before the configuration parameter changes
become effective.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
SQL1363W One or more of the parameters submitted for immediate modification
were not changed dynamically. For these configuration parameters, the database
must be shut down and reactivated before the configuration parameter changes
become effective.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
SQL1363W One or more of the parameters submitted for immediate modification
were not changed dynamically. For these configuration parameters, the database
must be shut down and reactivated before the configuration parameter changes
become effective.
db2 => DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 => db2 => DB20000I The SQL command completed successfully.
2. Start the core installation on the itnm-a.swg.be.ibm.com core server. Start the previously
installed Installation Manager as shown in Example 2-55.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 101
6. Select Next to accept the license agreement, as shown in Figure 2-56.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 103
8. Figure 2-58 shows the installation directory selection. Leave it as it is. Click Next.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 105
10.Figure 2-60 shows the ObjectServer configuration panel. You cannot configure the failover
capability yet. Therefore, we use the Primary Aggregation ObjectServer (AGG_P). We
change this name later. Click Next.
Tip: If you do not select the check box, you also choose to skip the configuration of the
ObjectServer for Network Manager. We configure the Network Manager, triggers, and user
accounts later in Configuration on page 113 when we finish the failover changes.
Note: The user itnmconnect needs to be configured in ObjectServer before you execute
the step in Figure 2-60.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 107
12.Figure 2-62 shows the configuration of the network domain name.
Important: This name is not the name of the ObjectServer. This name is used inside
Network Manager to label the network partition that will be discovered and monitored.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 109
14.Do not change the Python path, as shown in Figure 2-64. Click Next.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 111
16.Figure 2-66 shows the completed installation.
After a successful installation, post-installation steps for non-root users are required, as
described in the following document:
https://ibm.biz/BdrrNV
Note that only two lines ar in the file. All other lines are the header comments:
$NCHOME/precision/install/scripts/nco_create_control_scripts.sh $1
$NCHOME/precision/install/scripts/ncp_create_control_scripts.sh $1
The GUI is installed during the installation of IBM Jazz for Service Management (JazzSM).
Configuration
You need to configure the Network Manager core server for failover, as described in the
following document:
https://ibm.biz/BdrrNA
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 113
values
(
1,
"NCOMS",
"NCOMS_B",
"NCOMS_V"
);
3. Add the Network Manager triggers and GUI user accounts to the ObjectServer:
a. Move this file to the ObjectServer server:
$NCHOME/precision/install/data/create_itnm_triggers.sql
create_itnm_triggers.sql
b. Add the Network Manager triggers by running this command:
nco_sql -server AGG_P -user root -password '' < create_itnm_triggers.sql
c. Create the accounts in the ObjectServer by using the nco_config administration GUI:
itnmadmin in the System group
itnmuser in the Normal and ISQLWrite groups
IBM Tivoli Network Manager Version 4.2 (Build 11) 64 bit created by ncpbuild at
08:57:51 Sat Jan 23 GMT 2016
3. Restart the itnm core service on the primary server as the user netcool. See
Example 2-61.
5. Restart the backup itnm instance (Example 2-63). It now restarts as domain NCOMS_B.
2.5.4 Verification
Verify the installation. Review the log file for the ncp_virtualdomain that is in
/opt/IBM/netcool/core/log/precision, as shown in Example 2-64. Look for the
Connection messages and determine whether any errors exist.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 115
2016-05-05T19:29:51: Information: I-MOM-001-001: [990959424t] ncp_virtualdomain[15295] Version
4.2 (Build 11) 64 bit on linux2x86 becoming Primary
2016-05-05T19:29:53: Information: I-VIR-001-028: [930039552t] Requesting initial topology from
Primary domain
2016-05-05T19:29:53: Information: I-VIR-001-020: [930039552t] Connection made to primary domain
NCOMS
2016-05-05T19:29:53: Information: I-VIR-001-022: [923735808t] Updating topology in backup domain
2.6.1 Introduction
JazzSM combines data from integrated services to provide access to users to all data within a
single page, including reporting, security, and administration. Users can use JazzSM to
connect to DB2, IBM WebSphere, Dashboard Application Services Hub (DASH), registry
services, security services, and reporting services.
JazzSM has a set of predefined requirements for operating systems. These requirements are
documented on the IBM documentation server:
https://ibm.biz/Bdrr7d
Note: In Example 2-65, we show the prerequisite checking for Tivoli Common Reporting
(TCR) because the checking is the most complete checking for JazzSM. Depending on
your deployment needs, additional scripts exist in JazzSMScripts that you might need to
run. For our scenario, the checking for Tivoli Common Reporting was enough.
Machine Information
Machine name: jazz-a
Serial number: VMware-42 16 ce f3 3b b3 c8 27-be 2b ed 20 9b 19 a5 58
You need to fix any of the FAIL messages before you proceed, which we did in the other
products that are already installed in this book.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 117
Configuring Linux
You need to disable SELinux in /etc/selinux/config, as shown in Example 2-66.
Note: Depending on the type of Linux distribution, the nproc configuration can also be in
/etc/security/limits.conf.
2.6.3 Installation
Because of the distributed installation of our scenario (DB2 and JazzSM are installed on
different servers), you need to create the Tivoli Common Reporting database (TCRDB)
before you install JazzSM. The following URL has more details about these steps:
https://ibm.biz/Bdrr57
Note: Because DB2 is on a remote server in this example, you must copy the file to the
DB2 server to run the following example. For more information, see the IBM Knowledge
Center:
https://ibm.biz/BdrrN3
4. On the JazzSM servers, install the DB2 client. The following URLs explain how to install
the DB2 client:
https://ibm.biz/BdrrNk
https://ibm.biz/BdrrNt
5. Catalog the remote server (Example 2-72).
After you configure the TCRDB, perform the following steps to install JazzSM:
1. Install JazzSM as the user netcool. From /mnt/ITSO_SHARE/Jazz/JazzSM, start the
Installation Manager (Example 2-73).
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 119
2. After you issue the command, launch the GUI. Select File Preferences. See
Figure 2-67.
Table 2-9 shows all of the repositories that we used in this book for the JazzSM
installation. Several packages need more than one repository.
JAZZ_FOR_SM_1.1.2.0_FOR_LNX.zip /mnt/ITSO_SHARE/Jazz/JazzSM/JazzSMRepository/disk1
1.1.2-TIV-JazzSM-multi-FP001.zip /mnt/ITSO_SHARE/Jazz/JazzSM_FP1.1.2.1/JazzSMFPRepository/disk1
ITCR_3.1.2.1_FOR_LINUX.tar.gz /mnt/ITSO_SHARE/Jazz/JazzSM/TCRCognos
OMNIbus-v8.1.0.4-WebGUI.Linux64.zip /mnt/ITSO_SHARE/OMNI/core/OMNIbusWebGUI_NOIExtensionsRepository
/mnt/ITSO_SHARE/OMNI/core/OMNIbusWebGUIRepository
OMNIbus-v8.1.0-WebGUI-FP5-IM-Extensions-linux64-UpdatePack /mnt/ITSO_SHARE/OMNI/webGUI_NOI_FP5/OMNIbusWebGUI_NOIExtensionsRepository
.zip
/mnt/ITSO_SHARE/OMNI/webGUI_NOI_FP5/OMNIbusWebGUIRepository
OMNIbus-v8.1.0-WebGUI-FP5-IM-linux64-UpdatePack.zip /mnt/ITSO_SHARE/OMNI/webGUI_FP5/OMNIbusWebGUIRepository
ITNP_IP_LIN.zip /mnt/ITSO_SHARE/ITNM/Base/repositories/disk1
NTWRK_HLTH_DSHBRD_V4.2_LNX.zip /mnt/ITSO_SHARE/ITNM/NTWRK_HLTH_DSHBRD_V4.2_LNX/repositories/disk1
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 121
4. The following screen captures show the repositories for the products that we will install.
5. Add a repository for WebSphere Application Server (WAS). Click Browse. Drill down to
Jazz/JazzSM/WASRepository/disk1/. Choose diskTag.inf. See Figure 2-69. Click OK.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 123
9. Add a repository for the JazzSM fix pack. Click Browse. Under
/Jazz/JazzSM_FP1.1.2.1/JazzSMFPRepository/disk1/, choose diskTag.inf. See
Figure 2-73. Click OK.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 125
12.Click Install to start the installation, as shown in Figure 2-76.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 127
14.Accept the terms of the license agreements. See Figure 2-78. Click Next.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 129
16.Figure 2-80 shows the packages to install. Click Next.
Figure 2-81 Review the summary information and start the installation
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 131
18.Figure 2-82 shows the progress of the package installation.
19.Ensure that you select None in Figure 2-83 and click Finish.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 133
22.Accept the terms of the license agreements. See Figure 2-85. Click Next.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 135
24.Accept the WebSphere default user ID, as shown in Figure 2-87.
Tip: After you enter the password in Figure 2-87, click Validate to verify the connections.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 137
26.The installation of the JazzSM (DASH) packages starts. See Figure 2-89.
Tip: To avoid the message, Unable to connect to the Cognos content store, ensure
that you create the tcruser first by using the command useradd tcruser on the DB2
server and initialize and start the TCRDB. See 2.6.3, Installation on page 118.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 139
28.As shown in Figure 2-91, install the database client for Tivoli Common Reporting and click
Test connection.
Figure 2-91 Install the database client for Tivoli Common Reporting
Note: These files are the same files that you unpacked from
ITCR_3.1.2.1_FOR_LINUX.tar.gz.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 141
30.As shown in Figure 2-93, verify the packages that you need to install and click Next.
Note: As shown in Figure 2-93, we did not check the option Install event search with IBM
Operations Analytics - Log Analysis on purpose because event search needs the Log
Analysis server to be installed and running.
Note: As shown in Figure 2-94, due to a limitation of the configuration wizard, for now, we
set up the connection to the primary ObjectServer, AGG_P, but we will modify the data
source later for high availability.
Important: Whether you check Create/overwrite WebGUI data source or not, ensure that
the $NCHOME/etc/precision/ModelNcimDb.<domain>.cfg file on the Network Manager core
server contains the correct data source name that you want to use to calculate the status in
the topology maps. Here, we checked the box because we are installing Web GUI and
Network Manager GUI at the same time, which will create a data source with the name of
the ObjectServer (AGG_P).
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 143
32.Enter the password, as shown in Figure 2-95, and click Next.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 145
34.Verify the installation packages and click Install as shown in Figure 2-97.
2.6.4 Verification
You can perform the following verification of the installation.
Open the DASH login page. For instance, to verify the jazz-a installation in our scenario, we
opened the following URL in the browser:
https://jazz-a.swg.be.ibm.com:16311/ibm/console/
Ensure that you use the correct host name for your scenario and open the URL in your
browser. You see the DASH login page. Log in with the smadmin user to verify that DASH
works.
2.7.1 Introduction
Log Analysis comes with set of predefined requirements for the operating system. These
requirements are documented on the IBM documentation server:
https://ibm.biz/BdrrNc
Table 2-10 Settings for installing the IBM Operations Analytics - Log Analysis
Setting Value
$SCALA_HOME /opt/IBM/netcool/LogAnalysis/
$UNITY_HOME /opt/IBM/netcool/LogAnalysis/
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 147
2.7.4 Installation and basic configuration
Due to a known limitation, Log Analysis cannot reuse an existing group-mode Installation
Manager. You need to install a new one by using the install.sh script:
1. As the netcool user, launch the Installation Manager, as shown in Example 2-75.
mkdir LA
cd LA
tar xvzf OALA_1.3.2_ENTRY_LINUX_64_BIT.tar.gz
./install.sh
2. Select all packages to install and click Next. See Figure 2-98.
Figure 2-99 Accept the licensing agreement terms for both licenses
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 149
4. As shown in Figure 2-100, change the shared resources directory to
/opt/IBM/netcool/IM/IBMIMShared and the installation manager directory to
/opt/IBM/netcool/IM/InstallationManager/eclipse. Click Next.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 151
6. Select the packages that are shown as selected in Figure 2-102 and click Next.
Tip: The Apache Solr package can be distributed on another server, if necessary. For
more information, see this website:
https://ibm.biz/BdrrNE
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 153
8. Click Install as shown in Figure 2-104.
Configuration
The configuration of Log Analysis is documented in the following document:
https://ibm.biz/BdrrNX
./pkg_mgmt.sh -install
/opt/IBM/netcool/LogAnalysis/unity_content/NetworkManager/NetworkManagerInsightPack_v1.3.0.0.zip
BUILD SUCCESSFUL
Total time: 4 seconds
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 155
Figure 2-105 shows the initial window.
c. Click Start Now under the Create Data Source wizard. Figure 2-106 shows the Create
Data Source wizard.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 157
e. As shown in Figure 2-108, for the file path, enter AGG_V. For the type, enter
OMNIbus1100. For Collection, enter OMNIbus1100-Collection. Click Next.
Note: The name omnibus is mandatory because it was configured in the Insight Pack as
the default data source name.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 159
g. With the data source in place, you can configure the nco-g-xml gateway (or SCALA
gateway) for OMNIbus. For more information, see this website:
https://ibm.biz/BdrrN4
The configuration of the nco-g-xml gateway (or SCALA gateway) for OMNIbus involves
the following steps:
i. Add the nco-g-xml gateway on the IBM Operations Analytics - Log Analysis server.
(You will need to install the gateways support on this server, too.) Use IBMIM to add
the repository from the Im-nco-g-xml-7_0.zip to the Installation Manager, as
shown in Figure 2-110.
This gateway will be installed near the destination (ioala-a server) because the
gateway and IBM Operations Analytics - Log Analysis cannot fail over.
iii. Click Next and wait until the installation is finished. Then, continue with the
configuration.
5. Create a gateway server in the Netcool/OMNIbus interfaces file by using the following
commands (Example 2-78).
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 161
6. Configure the G_SCALA.props properties file, including the specification of the .map
mapping file, as shown in Example 2-79.
Gate.XMLGateway.TransformerFile : '$OMNIHOME/java/conf/scalaTransformers.xml'
Gate.XMLGateway.TransportFile : '$OMNIHOME/java/conf/scalaTransport.properties'
Gate.XMLGateway.TransportType : 'SCALA'
Gate.XMLGateway.DateFormat : 'yyyy-MM-dd\'T\'HH:mm:ssZ'
#################
# Omnibus settings
Gate.Reader.Server : 'AGG_V'
Gate.Reader.Username : 'root'
Gate.Reader.Password : '' # nco_g_crypt output
Gate.Reader.Description : 'SCALA Gateway Reader'
Important: The host name that is used in the configuration needs to be identical to the
certificate that is imported in Example 2-81 on page 163.
8. If, due to network security reasons, a Secure Sockets Layer (SSL) connection is required
from the Log Analysis server to the Object Servers, perform the following steps to
configure the SSL connection. See the following document for details:
https://ibm.biz/BdrrNr
Important: In our environment, the server did not send a fully qualified domain name
(FQDN) certificate. (See the response under Certificate Subject Alternative Name(s) in
Example 2-81.) Confirm from the certificate response whether you received an FQDN
certificate, and change the name in the scalaURL property correctly (in Example 2-82).
Otherwise, the SSL connection fails.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 163
#
# keyStore - the keyStore that contains the private keys for any https ports (see
JVM property javax.net.ssl.keyStore)
# keyStore=/the/path/to/the/keystore
keyStore=$OMNIHOME/java/security/client.jks
#
# keyStorePassword - the password to the keyStore that contains the private keys
for any https ports (see JVM property javax.net.ssl.keyStorePassword)
keyStorePassword=netcool
#
# trustStore - the trustStore that contains the server's public key for any https
clients (see JVM property javax.net.ssl.trustStore)
# trustStore=/the/path/to/the/truststore
trustStore=$OMNIHOME/java/security/cacerts.jks
#
# trustStorePassword - the password to the trustStore that contains the server's
public key for any https clients (see JVM property
javax.net.ssl.trustStorePassword)
trustStorePassword=netcool
#
# threadPoolSize - the number of threads that the http servers share to process
incoming requests
# threadPoolSize = 16
#
# username - the username to use for authentication with the data collector.
username = unityadmin
#
# password - the password to use for authentication with the data collector.
password = unityadmin
#
# eventBufferSize - the maximum number of events to contain in each batch of log
record data sent to the SCA-LA data collector.
# eventBufferSize = 200
#eventBufferSize = 3
#
## eventBufferFlushTime - the amount of time to wait for new events in seconds
before flushing the buffer. Flush timer is reset on each event added to the batch.
# eventBufferFlushTime = 30
#
# enableTrace - enable diagnostic tracing of communications between the SCA-LA
transport and the data collector.
# enableTrace = true
#
# readTimeout - socket timeout for reading responses from SCA-LA, in seconds
# readTimeout = 30
#
# jsonMsgHostname - The hostname that corresponds to the data source for ingested
data.
jsonMsgHostname = IOALA-A.swg.be.ibm.com
#
# jsonMsgPath - The path that corresponds to the data source for ingested data.
jsonMsgPath = AGG_V
3. Verify the installed Insight Packs with the following command (Example 2-85).
cd /opt/IBM/netcool/LogAnalysis/utilities/
./pkg_mgmt.sh -list
.Buildfile: /opt/IBM/netcool/LogAnalysis/utilities/pkg_mgmt.xml
initializeCustomTasks:
main:
[packagemanager] 04/30/16 17:23:24:363 CEST [main] INFO - PrerequisitesManager :
CTGLC0044I : Running prerequisite checks...
[packagemanager] 04/30/16 17:23:24:368 CEST [main] INFO - PrerequisitesManager :
CTGLC0045I : Prerequisite checks passed
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 165
[packagemanager] 04/30/16 17:23:24:369 CEST [main] INFO - ContentPackManager :
CTGLC0030I : Listing installed insight packs started...
[packagemanager] 04/30/16 17:23:24:440 CEST [main] INFO - ContentPackManager :
[packagemanager] GAInsightPack_v1.1.1.3 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] NetworkManagerInsightPack_v1.3.0.0 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] DB2InsightPack_v1.1.0.2 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] DB2AppInsightPack_v1.1.0.3 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] OMNIbusInsightPack_v1.3.0.2 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] WASInsightPack_v1.1.0.3 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] WindowsOSEventsInsightPack_v1.1.0.4 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] SyslogInsightPack_v1.1.0.3 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] JavacoreInsightPack_v1.1.0.3 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] WASAppInsightPack_v1.1.0.3 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] WebAccessLogInsightPack_v1.1.0.2 -
/opt/IBM/netcool/LogAnalysis/unity_content
[packagemanager] 04/30/16 17:23:24:442 CEST [main] INFO - ContentPackManager :
CTGLC0031I : Listing completed successfully
BUILD SUCCESSFUL
Total time: 1 second
Add Log Analysis integration to the OMNIbus Web GUI part of JazzSM
Perform the following steps to add the Log Analysiss integration to the OMNIbus Web GUI
part of JazzSM.
2. Click Modify. Select IBM Netcool GUI Components, as shown in Figure 2-112. Click
Next.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 167
3. Select all features under IBM Tivoli Netcool/OMNIbus Web GUI to install. Ensure that you
check Install event search with IBM Operations Analytics - Log Analysis
(Figure 2-113) and click Next.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 169
5. As shown in Figure 2-115, type the smadmin password again and click Next.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 171
7. Click Modify, as shown in Figure 2-117.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 173
2.7.5 Verification
Perform the following steps to verify the successful installation:
1. Log in to https://ioala-a.swg.be.ibm.com:9987/Unity as shown on Figure 2-119.
2. You can also see the ingestion of data from the nco-g-xml gateway by using the
Administrative Settings option, as shown in Figure 2-120.
The Server Statistics window shows you the daily intake of events. You can also drill down to
a more detailed view.
2.8.1 Introduction
Netcool Configuration Manager comes with a set of predefined requirements for the operating
systems, databases, and hardware.
Note: The current Prerequisite Scanner does not support Netcool Configuration Manager
Version 6.4.1.0/1. This support will be available for version 6.4.2.1, which was not
available at the time of writing this book.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 175
2.8.2 Installation and basic configuration
Perform the following steps:
1. Download and extract the necessary files that correspond to your server operating
system. You can obtain the correct part numbers at this website:
https://ibm.biz/BdrFAn
2. Create a set of repository directories, as shown in Table 2-11.
/opt/IBM/noi_repo/jazz JazzSM
/opt/IBM/noi_repo/websphere WebSphere
3. Start the previously installed Installation Manager by using the following command
(Example 2-87).
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 177
7. Modify the Shared Resources Directory with the correct path
(/opt/IBM/netcool/IM/IBMIMShared) as shown in Figure 2-124. Click Next.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 179
14.Accept the default context root by selecting Next, as shown in Figure 2-128.
15.Review the packages to install and select Install. See Figure 2-129.
Tip: Remember to scroll down in the Packages window to review all packages and expand
the Repository Information to verify.
16.After the installation of WebSphere and JazzSM completes, choose None on the final
window and click Finish.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 181
19.On the next window, click I accept the terms in the license agreement. Click Next. See
Figure 2-131.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 183
21.Choose the type of installation that is required. In this example, we chose a combined
Presentation Server and Worker Server type of installation, as shown in Figure 2-133.
Click Next.
After you enter the database details, click Next, as shown in Figure 2-134.
23.The database connection details are verified. When the Warning pop-up window opens,
you must confirm that this process will load the database at the conclusion of the Netcool
Configuration Manager installation. Click OK. See Figure 2-135.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 185
24.Complete the Netcool Configuration Manager Server configuration. Enter the ftpuser
password, SMTP server (localhost), and Network Manager integration details. These
settings are shown in Figure 2-136 and Figure 2-137 on page 187. (Scroll down to see the
second window.)
Tips: Use an IP address for the FTP server because the Domain Name System (DNS) is
not configured for many network devices, especially in a lab setting.
Provide a more meaningful name for the Netcool Configuration Manager unique name,
such as NCMLab1, or a name that describes the specific installation.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 187
25.On the next window, provide the JazzSM password that was used in the previous
installation step. Click Next and a password verification pop-up window opens. After
successful validation, the next window opens. See Figure 2-138.
27.After the installation completes, the installed packages window opens. Click Finish to
proceed, as shown in Figure 2-140.
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 189
Verification
You can perform the following steps to verify the installation.
Components
----------
Worker Server = NOT RUNNING
Compliance Core = NOT RUNNING
GUI Server = NOT RUNNING
Logging level
-------------
Log status unavailable
Load version
------------
6.4.2.1-0-32
Database
--------
Hostname/IP Address = localhost
Database Name = ncm6421
For a complete listing of the driver assemblies, their individual installers, and the installation
instructions, see the Netcool Configuration Manager Drivers 20 release notes:
https://ibm.biz/BdrrNm
Chapter 2. IBM Netcool Operations Insight installation and basic configuration 191
192 IBM Netcool Operations Insight Version 1.4: Deployment Guide
3
In addition to the basic configuration, you can configure several other features in Netcool
Operations Insight. In this chapter, we describe how to configure these additional capabilities
of Netcool Operations Insight.
Tip: The central LDAP server will be required for the SSO (single sign-on) configuration.
For a seamless integration among all of the Netcool Operations Insight components and
consoles, it is a preferred practice to configure SSO in your environment.
For more information about these configurations, see the following resources:
https://ibm.biz/BdE79r
https://ibm.biz/BdrEju
Important: For the SSO to work, your Impact server must be on the same domain as your
DASH server.
Important: If the repository was configured for the ObjectServer, you must remove the
repository now.
4. Figure 3-3 shows how the federated repositories appear at the end of this step.
5. Configure the LDAP users in the console as described in the following document:
https://ibm.biz/Bdrr7E
Tip: When the steps refer to Users and Groups Manage Users, these steps are
performed in the WebSphere Administrative Console.
Also, to log in to the WebSphere Administrative Console, you must log in as smadmin.
Tip: Netcool/Impact and DASH must use the same domain name.
Perform the following steps to configure Netcool/Impact in the same central user repository
as DASH:
1. Configure LDAP for Netcool/Impact as described in the following document:
https://ibm.biz/Bdrr7r
Example 3-1 shows how the $IMPACT_HOME/install/security/impactdap.properties file
was configured in our environment.
# Custom LDAP Search Filtering (Default values for IBM Tivoli Directory Server)
#LDAPUserFilter="(&(uid=%v)(objectclass=ePerson))"
#LDAPGroupFilter="(&(cn=%v)(|(objectclass=groupOfNames)(objectclass=groupOfUniqueN
ames)(objectclass=groupOfURLs)))"
#LDAPUserIdMap="*:uid"
#LDAPGroupIdMap="*:cn"
#LDAPGroupMemberIdMap="ibm-allGroups:member;ibm-allGroups:uniqueMember;groupOfName
s:member;groupOfUniqueNames:uniqueMember"
2. After you configure the impactdap.properties file, run the confAuth4LDAP.sh script.
Example 3-2 shows the confAuth4LDAP.sh script while it executes.
The expected result for the command is the BUILD SUCCESSFUL message:
BUILD SUCCESSFUL
Total time: 2 minutes 9 seconds
3. To grant additional permissions to the users in Impact, you need to use the mapRoles.sh
script. Example 3-3 shows how to grant permissions to a user.
Example 3-3 Use the mapRoles.sh script to grant permissions to users in Impact
[netcool@Impact-B ~]$ cd $IMPACT_HOME/install/security
[netcool@Impact-B security]$ ./mapRoles.sh -add -user johndoe -roles
"ConsoleUser|impactMWMUser|impactOSLCDataProviderUser|impactOpViewUser|impactRBAUs
er|impactSelectedOpViewUser|impactUIDataProviderUser|impactWebServiceUser"
Adding user johndoe to role ConsoleUser
Adding user johndoe to role impactMWMUser
Adding user johndoe to role impactOSLCDataProviderUser
Adding user johndoe to role impactOpViewUser
Adding user johndoe to role impactRBAUser
Adding user johndoe to role impactSelectedOpViewUser
Adding user johndoe to role impactUIDataProviderUser
Adding user johndoe to role impactwebserviceuser
Important: Impact does not verify the existence of the user/group that is used in the
command in Example 3-3. So, check the syntax exactly and be aware of case sensitivity if
the LDAP requires it.
For more information about each of the Impact roles, see the following website:
https://ibm.biz/Bdrr7s
l. On the same window, you can configure the signer certificates for all servers that will
integrate with DASH. Figure 3-6 shows all of the certificates that are needed in our
environment.
Tip: It is a preferred practice to copy this file to a shared directory where all other servers in
the environment can access this file.
For the GUI Server, the ltpa.keys are stored in the following directory:
$IMPACT_HOME/wlp/usr/servers/ImpactUI/resources/security/
cp /mnt/ITSO_SHARE/Keys/ltpa.keys
$IMPACT_HOME/wlp/usr/servers/ImpactUI/resources/security/ltpa.keys
7. Run the SSO configuration script configImpactSSO.sh. Specify the same parameter
values that are referenced in step 1 in Configuring single sign-on in Netcool/Impact on
page 199. Example 3-5 shows the execution of the configImpactSSO.sh script.
The expected result for the command is the BUILD SUCCESSFUL message:
BUILD SUCCESSFUL
Total time: 1 minute 5 seconds
Restart both the Dashboard Application Services Hub and Impact servers
Restart both the DASH and Impact servers for the changes to take effect.
Perform the steps for Console Integration as described in the following document:
https://ibm.biz/Bdrr7Y
4. Figure 3-12 shows the result of the search. Ensure that the Name field is
Impact_NCICLUSTER. Click OK.
Important: You need to execute the steps that relate to DASH in this section for both
Jazz-A and Jazz-B.
Also, you need to execute the steps that relate to Impact for both Impact-A and Impact-B.
3.1.2 Importing the LTPA keys for the SSO in the JAZZ secondary server
To configure SSO in the secondary JazzSM server, follow the steps in this document:
https://ibm.biz/Bdrr7z
3.1.3 Configuring IBM Operations Analytics - Log Analysis for SSO with Jazz
for Service Management
To configure IBM Operations Analytics - Log Analysis for SSO with JazzSM, follow the steps
in this document:
https://ibm.biz/Bdrr7q
Important: When you enable LDAP in Operations Analytics - Log Analysis, ensure that the
props file for the G_SCALA gateway is updated with the LDAP user/password that can
access Operations Analytics - Log Analysis.
Example 3-6 Configure LDAP for IBM Operations Analytics - Log Analysis
ldap_hostname_property=itso-ad.swg.be.ibm.com
ldap_port_property=389
ldap_baseDN_property=DC=ITSO,DC=IBM,DC=COM
ldap_bindDN_property=CN=Administrator,CN=Users,DC=ITSO,DC=IBM,DC=COM
ldap_bindPassword_property=Object00
ldap_realm_property=LDAPRealm
ldap_id_property=LdapRegistryId
ldap_ignoreCase_property=true
<activedLdapFilterProperties id="unityactivedfilters"
userFilter="(&(sAMAccountName=%v)(objectcategory=user))"
groupFilter="(&(cn=%v)(objectcategory=group))"
userIdMap="user:sAMAccountName"
groupIdMap="*:cn"
groupMemberIdMap="memberOf:member"/>
</server>
2. As part of step 4 of the procedure that was described in the URL in the beginning of this
section, add the lines that are shown in Example 3-7 to the file
/opt/IBM/netcool/LogAnalysis/wlp/usr/servers/Unity/server.xml.
3. Add the LDAP admin group to the Log Analysis Admin users as described in the following
document:
https://ibm.biz/Bdrr7P
Example 3-8 show how we performed this step in our environment.
Example 3-8 Adding the LDAP admin group to the Log Analysis Admin users
vi /opt/IBM//LogAnalysis/wlp/usr/servers/Unity/unityConfig.xml
<oauth-roles>
<authenticated>
<group name="UnityUsers"/>
<group name="Jazz_Admins/>"
</authenticated>
</oauth-roles>
4. Restart the Log Analysis server. To verify that the SSO connection is set up correctly, log
in to the JazzSM server. Open a new tab page in the browser and log in to Operations
Analytics - Log Analysis.
5. To test the Operations Analytics - Log Analysis integration with DASH, open an Event
Viewer in DASH. Figure 3-14 shows an Event Viewer with a selected event.
Note: You need to configure Event Analytics to see the options, as shown in Figure 3-16.
For more information, see 3.2.3, Event Analytics on page 211.
The status of the service shows a check mark in a green square, as shown in Figure 3-18.
The service depends on the status of the current run of the configuration.
This file was created by the event integration component of Web GUI. For more information,
see 3.2.1, Seasonality on page 210.
This action adds a set of new fields, triggers, and tables to the ObjectServers.
3. Reconfigure the gateways to support the new fields:
IBMExtractedType
IBMProcessingStage
ParentIdentifier
This task is partially documented at this website:
https://ibm.biz/Bdrr7v
4. Reconfigure the gateways to support the new fields by logging in to Omni-A as the user
netcool and by running the command that is shown in Example 3-12.
5. You must make the same changes to the AGG_GATE.map file and the A_TO_D_GATE.map file
on Omni-B as shown in Example 3-13.
cd $OMNIHOME/etc
vi AGG_GATE.map
##############################################################################
#
# CUSTOM alerts.status FIELD MAPPINGS GO HERE
#
##############################################################################
'IBMExtractedType' = '@IBMExtractedType',
'IBMProcessingStage' = '@IBMProcessingStage',
'ParentIdentifier' = '@ParentIdentifier',
##############################################################################
6. At the end of the AGG_GATE.map file, add the configuration for the extra failover capabilities
as shown in Example 3-14. For more information, see this website:
https://ibm.biz/Bdrr7v
cd $OMNIHOME/etc
vi AGG_GATE.map
CREATE MAPPING RE_CACHEMAP
(
'name' = '@name' ON INSERT ONLY,
7. Edit the AGG_GATE.tblrep.def file to add the commands to the end of the file as shown in
Example 3-15.
8. On the Impact server, configure the data sources and services that are used by Netcool
Operations Insight. Configure the ObjectServer data source as shown in Figure 3-19.
9. In this data source, enter the Primary ObjectServer, Secondary ObjectServer, and their
ports. Point the Primary ObjectServer, Secondary ObjectServer, and their ports to the
Aggregation Layer ObjectServers and use the previously created ObjectServers user
name: impactconnect.
cd /opt/IBM/tivoli/netcool/impact/add-ons/Seasonality/db
cp seasonality_db2.sql /mnt/ITSO_SHARE/tmp
b. Run the database creation script on the DB2 Server as user db2inst1, as shown in
Example 3-17.
Note: You can change the Seasonality Database to the DB2 instance. For more
information, see this website:
https://ibm.biz/Bdrr7K
20.Confirm that all services are started, except StartSeasonalityProcessing, which is only
used to start the Seasonality whenever the server starts. If the services are marked with
an X in a red circle, start them.
Example 3-18 Apply the SQL files on the Aggregation and Display Server
cd /opt/IBM/tivoli/netcool/omnibus/bin
./nco_sql -user root -server AGG_P
</opt/IBM/tivoli/netcool/omnibus/extensions/scala/scala_itnm_configuration.sql
./nco_sql -user root -server AGG_B
</opt/IBM/tivoli/netcool/omnibus/extensions/scala/scala_itnm_configuration.sql
./nco_sql -user root -server DIS_1
</opt/IBM/tivoli/netcool/omnibus/extensions/scala/scala_itnm_configuration.sql
./nco_sql -user root -server DIS_2
</opt/IBM/tivoli/netcool/omnibus/extensions/scala/scala_itnm_configuration.sql
2. For the menus, apply the changes to the JazzSM servers. On both JazzSM servers, set
the username/password in the waapi.init file. See Example 3-19.
Important: If LDAP is activated, you must use an LDAP user name. Otherwise, use the
smadmin user name.
5. Add the menu item to the Network view by adding <menu id="Event Search"/> to the
ncp_topoviz_device_menu.xml as shown in Example 3-22.
Note: Before you join nodes to a cluster, ensure that each node uses the same file-based
repository user ID, which is assigned the role of iscadmins.
/opt/IBM/netcool/JazzSM/lib/db2/db2jcc.jar
/opt/IBM/netcool/JazzSM/lib/db2/db2jcc_license_cu.jar
14.Select the JDBC provider that you created, for example, DB2 Universal JDBC Driver
Provider, and click Next (Figure 3-37).
Important: Click Use this data source in container managed persistence (CMP).
19.Click Save.
20.Click Previous and Next to refresh the window and show the DB2 username.
25.If the connection test is successful, close the web page and restart the server. See
Example 3-24.
Tip: To stop and start Jazz without typing the user name and password, change the
following file:
/opt/IBM/netcool/JazzSM/profile/properties/soap.client.props
Edit the following lines to include the smadmin user ID and password:
com.ibm.SOAP.loginUserid=smadmin
com.ibm.SOAP.loginPassword=netcool
26.Enable server-to-server trust on both servers. Edit the ssl.client.props file and
uncomment the section that starts with com.ibm.ssl.trustStoreName=AnotherTrustStore
so that it looks like Example 3-25.
Here is the signer information (verify the digest value matches what is displayed at the server):
29.Verify the load balancing implementation. You can verify the status of the cluster by using
the following command (Example 3-28).
You can set up a load-balanced cluster of console nodes with identical configurations to
evenly distribute user sessions.
If you want to add a node to a cluster and the node contains custom data, you must export the
data before you join the node to the cluster. The exported data is later imported to one of the
nodes in the cluster so that it is replicated across the other nodes in the cluster.
Important: Be careful when you add new nodes to an existing cluster. The custom content
of the new nodes will be replaced with the content that is stored in DB2.
Implementation steps
First, you must prepare the HTTP server for load balancing:
1. On the load balancer server, you need to install the IBM HTTP server and the IBM HTTP
Server Plug-in for IBM WebSphere Application Server as the user netcool. Perform the
following steps:
a. Extract the WAS_V8.5.5_SUPPL_1_OF_3.zip file, the WAS_V8.5.5_SUPPL_2_OF_3.zip file,
and the WAS_V8.5.5_SUPPL_3_OF_3.zip file into the same directory by using the
following commands. See Example 3-29.
b. The included Java code (iKeyman) needs 32-bit libraries that are added to the operating
system. As the root user, run these commands (Example 3-30).
Tip: Ignore the error about an unsupported operating system. In this environment, the
error was caused by the use of Red Hat Enterprise Linux 7.1.
b. Click Next. Accept the terms of the license agreement and click Next.
4. Save this certificate on the load balancer server. For instance, for Jazz-A, we saved the
certificate in the shared directory /mnt/ITSO_SHARE/Jazz/Jazz-A.crt.
5. Create the keystore by using the commands that are shown in Example 3-32.
7. Select the Create a new key database file icon. Change the file name and path as shown
in Figure 3-56. Ensure that you select key database type CMS. Click OK.
Tip: The file is called plugin-key.kdb in several places in the product documentation. The
name does not matter, but you must always use the same file name in the following
configuration.
12.Click Add and browse all of the Jazz certificates. See Figure 3-61.
13.Type an alias for each certificate, for example, Jazz-A, as shown in Figure 3-62. Click OK.
Look for the remarked (#) code below and change accordingly
cd ../bin
./apachectl
start
Important: The red _ prefixed number must match the number from the above container,
as shown in Example 3-34. The value=''12345'' needs to be unique on each JazzSM server.
18.Generate the plug-in cfg files. Run the following commands, as shown in Example 3-35.
cp /opt/IBM/netcool/JazzSM/profile/config/cells/plugin-cfg.xml
/mnt/ITSO_SHARE/Jazz/JazzA_plugin-cfg.xml
or
cp /opt/IBM/netcool/JazzSM/profile/config/cells/plugin-cfg.xml
/mnt/ITSO_SHARE/Jazz/JazzB_plugin-cfg.xml
19.On the load balancer server, merge the plug-in cfg files manually. Look for the
<ServerCluster start and add the <Server entry from the other .xml file. See
Example 3-36.
<PrimaryServers>
<Server Name="JazzSMNode01_server1"/>
<Server Name="JazzSMNode01_server2"/>
</PrimaryServers>
</ServerCluster>
Note: Type the correct CloneID and server name. In our example, the generated
plugin-cfg.xml file contained host names only, not the fully qualified domain name
(FQDN) host name, so the file was changed to the FQDN.
20.Add this plugin-cfg.xml file in the HTTP Server http.conf file. See Example 3-37.
Example 3-37 Add the plugin-cfg.xml file in the HTTP Server http.conf file
cd /opt/IBM/netcool/IBM/HTTPServer/conf
vi http.conf
LoadModule was_ap22_module
"/opt/IBM/netcool/IBM/WebSphere/Plugins/bin/64bits/mod_was_ap22_http.so"
WebSpherePluginConfig "/opt/IBM/netcool/IBM/HTTPServer/conf/plugin-cfg.xml"
cd ../bin
./apachectl restart
Note: For more detailed configuration options, see the following URLs:
Understanding IBM HTTP Server plug-in Load Balancing in a clustered environment:
https://ibm.biz/BdrHji
The plugin-cfg.xml options:
https://ibm.biz/BdrHjb
Recommended values for web server plug-in config:
https://ibm.biz/BdrHje
Important: Due to the technical limitations of the IBM HTTP Server, you must deploy this
solution on a separate instance.
For more information about this configuration, see the How to load balance and provide
high availability with JazzSM Dashboard Connections white paper, which is authored by
Brian R. Fabec. The paper is available at the following link:
https://ibm.biz/BdrHjV
To provide load balancing for the connections from JazzSM dashboards to the Netcool/Impact
GUI servers, you must install and configure an IBM HTTP Server.
The IBM HTTP Server is installed between the Netcool/Impact GUI servers and the JazzSM
dashboard server.
JazzSM bundles the WebSphere Application Server Version 8.5 Supplements installation
media, which contains the installation packages for the IBM HTTP Server.
Example 3-38 Log in as the netcool user and launch the IBMIM
su - netcool
cd /opt/IBM/netcool/IM/InstallationManager/eclipse
./IBMIM
Important: The keystore that is used by the Web Server Plug-in must be a configuration
management system (CMS) keystore. The Java KeyStore (JKS) that is created by the
Liberty profile and used by Netcool/Impact cannot be used.
11.The CMS keystore must be created by using the iKeyman utility and the certificates that
are exchanged between the Web Server Plug-in CMS keystore and the Netcool/Impact
JKS keystore.
12.For each Impact GUI server in the environment, export the SSL certificate from the
Netcool/Impact JKS keystore by using the keytool command (Example 3-39).
2. Copy all of the exported certificates to the IBM HTTP Web Server.
3. Start the iKeyman utility, which is under the WebSphere Customization Toolkit directory
(Example 3-40).
14.Select the CMS key database type. Provide a location and file name to store the key
database file for the WebSphere Customization Toolbox and select OK. See Figure 3-72.
Note: This location will be used for the rest of the configuration. In this scenario, we used
the location /opt/IBM/HTTPServer/conf/plugin.kdb to store the database key file.
16.Enter a keystore password and ensure that Stash password to a file is selected. Select
OK. See Figure 3-74.
18.Select Signer Certificates from the Key database content drop-down list box. See
Figure 3-76.
What is a web server plug-in? A web server plug-in is used to forward HTTP requests
from the IBM HTTP Server to one or more application servers, including WebSphere
Liberty, which is the application server platform on top of which Netcool/Impact servers
run. The plug-in takes the request and based on the configuration in the plugincfg.xml file
maps the URI for the HTTP request to the host name and port number of an application
server and forwards the request to the specified application server.
22.Log in to any server in the environment that is a host for an Impact GUI server.
23.Add the following pluginConfiguration element in the
$IMPACT_HOME/wlp/usr/servers/ImpactUI/server.xml file between the <server>
</server> sections (Example 3-41).
30.Repeat the steps for each Impact GUI server in the environment. The plugin-cfg.xml is
generated under the $IMPACT_HOME/wlp/usr/servers/ImpactUI directory.
31.Copy all of the generated plugin-cfg.xml files to the JazzSM Dashboard Component
server.
32.In the $JAZZSM/profile/bin directory, use the pluginCfgMerge utility to merge all of the
generated plugin-cfg.xml files that were copied. Use the following command to generate
the plugin-cfg.xml file that will be used in the IBM HTTP Server by merging the
plug-cfg1.xml and plugin-cfg2.xml files. See Example 3-42.
Example 3-43 Add these lines to the end of the IBM HTTP Server configuration file
LoadModule was_ap22_module
"/opt/IBM/WebSphere/Plugins/bin/64bits/mod_was_ap22_http.so"
WebSpherePluginConfig "/opt/IBM/HTTPServer/conf/plugin-cfg.xml"
36.To enable SSL on the IBM HTTP Web Server, add the following section to the end of the
httpd.conf file, as shown in Example 3-44.
Example 3-44 Add this section to the end of the httpd.conf file
LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
Listen 443
<VirtualHost *:443>
SSLEnable
</VirtualHost>
KeyFile /opt/IBM/HTTPServer/conf/plugin.kdb
SSLDisable
37.Start the IBM HTTP Web Server by using the /apachectl start command.
Note: You will not be able to log in to the Netcool/Impact GUI successfully by using the
load balancer. However, HTTP and HTTPS UI data provider connections from the
Dashboard will connect successfully.
40.Select the previously created Impact_NCICLUSTER and click the Edit existing provider
icon (or add an Impact_NCICLUSTER if it does not exist yet). See Figure 3-83.
Now, Dashboard pages can be created by using the IBM HTTP Server, providing load
balancing and high availability connections to the Netcool/Impact UI data provider GUI
servers.
Troubleshooting
To enable additional logging for the web server plug-in, edit the plugin-cfg.xml file in the
configuration directory of the IBM HTTP Server and update the Log element with the correct
location and log level for the plug-in logs, for example:
<Log LogLevel="Trace" Name="/opt/IBM/HTTPServer/logs/http-plugin.log"/>
References
For more information, see the following resources:
Netcool/Impact Clustering overview:
https://ibm.biz/Bdrr7p
Load balancing for DASH:
https://ibm.biz/Bdrr7h
The publications listed in this section are considered particularly suitable for a more detailed
discussion of the topics covered in this book.
IBM Redbooks
The following IBM Redbooks publications provide additional information about the topic in this
document. Note that some publications referenced in this list might be available in softcopy
only.
Improving Operations Effectiveness and Efficiency with IBM Netcool Operations Insight: A
Scenarios Guide, SG24-8352
Delivering Consistency and Automation with Operational Runbooks, REDP-5347
You can search for, view, download or order these documents and other Redbooks,
Redpapers, Web Docs, draft and additional materials, at the following website:
ibm.com/redbooks
Online resources
These websites are also relevant as further information sources:
IBM Netcool Operations Insight Version 1.4.0.1 Knowledge Center documentation:
https://www.ibm.com/support/knowledgecenter/SSTPTP_1.4.0.1/soc/collaterals/soc_
netops_kc_welcome.html?lang=en
SG24-8365-00
ISBN 0738441848
Printed in U.S.A.
ibm.com/redbooks