IBM Netcool Operations Insight 1.2 Installation and Upgrade Guide Best Practices

Transcription

1 IBM Netcool Operations Insight 1.2 Installation and Upgrade Guide Best Practices Licensed Materials Property of IBM

2 Note: Before using this information and the product it supports, read the information in Notices at the end of this document. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents About this publication... v Intended audience... v What this publication contains... v Conventions used in this publication... v Typeface conventions... v Operating system-dependent variables and paths... vi Chapter 1 Introduction... 1 Chapter Install and run IBM Prerequisite Scanner for each product... 3 Check maxproc and ulimit settings... 3 maxproc... 4 ulimit... 4 Install IBM Installation Manager... 4 Download the software... 4 Create a IBM Installation Manager data directories... 4 Install the IBM Installation Manager... 5 Perform Netcool/OMNIbus core migration... 5 Use best practice upgrade techniques to minimise disruption... 6 Download the software... 6 Define the target installation directory... 7 Install Netcool/OMNIbus 8.1 via IBM Installation Manager... 7 Set up the software repository... 9 Install Netcool/OMNIbus Updating the ObjectServer schema Updating log file locations Updating the standard multitier architecture configuration Install DB2 and configure REPORTER schema Housekeeping considerations for DB Install the Netcool/Gateway for JDBC Perform Netcool/OMNIbus Web GUI migration Clone existing configuration Download the software Define the target installation directory Install the UI components via IBM Installation Manager Set up the software repository Install WAS, JazzSM and DASH Install Web GUI and IBM Netcool Operations Insight extensions Restore previous configuration to new installation Perform Netcool/Impact 7.1 migration Download the software Define the target installation directory Install Netcool/Impact Migrate the configuration from the incumbent Netcool/Impact system Configure historical event archive database connection in Netcool/Impact Create a new Impact Data Provider in DASH Configure single sign-on (SSO) between Jazz and Netcool/Impact Install and configure Smart Cloud Analytics Logfile Analysis (SCA-LA) Download the software Installation documentation SCA-LA setup notes Housekeeping considerations for SCA-LA Configure Networks for Operations Insight Install IBM Tivoli Common Reporting 3.1 (optional) Perform prerequisite checks Download the software Configure DB2 for Cognos Contents iii

4 Install IBM Tivoli Common Reporting Configure IBM Tivoli Common Reporting Configure right click tools to launch into TCR reports Configure processes to automatically start on machine boot (optional) Configure Jazz to not prompt for credentials when stopping Trademarks Contents iv

5 About this publication The purpose of this document is to provide step-by-step guidance on how to get from an existing Netcool configuration to IBM Netcool Operations Insight - or install IBM Netcool Operations Insight from scratch. IBM Netcool Operations Insight includes Netcool/OMNIbus version 8.1 (includes Web GUI), Netcool/Impact version 7.1 and Smart Cloud Analytics - Logfile Analysis (SCA-LA). Also included in IBM Netcool Operations Insight is the new visualisation UI called the Dashboard Application Services Hub (DASH) which is the replacement for the Tivoli Integrated Portal (TIP). Finally, there is a comprehensive integration of IBM Tivoli Network Manager (ITNM) and Netcool Configuration Manager (NCM) into IBM Netcool Operations Insight called Networks for Operations Insight. An overview of this key networks integration is discussed in this document and the relevant documentation links on IBM Knowledge Center are provided. Intended audience This publication is intended for anyone performing a new installation or an upgrade of an incumbent Netcool system to IBM Netcool Operations Insight and Networks for Operations Insight. It contains details installation steps for how to migrate from previous versions to the new versions provided with IBM Netcool Operations Insight plus an overview and links to the detailed instructions for the Networks for Operations Insight upgrade and integration. What this publication contains This publication contains the following sections: Chapter 1 Introduction on page 2 Provides a summary of the components and steps required to upgrade to IBM Netcool Operations Insight. Chapter 2 on page 3 Provides instructions on how to prepare the target systems for installation and/or upgrade, steps on how to perform the upgrades for each of the components - including part numbers and screen shots, and any recommended post-installation configurations. Conventions used in this publication This publication uses several conventions for special terms and actions and operating systemdependent commands and paths. Typeface conventions This publication uses the following typeface conventions: Bold Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip: and Operating system considerations:) About this publication v

6 Italic Keywords and parameters in text Citations (examples: titles of publications, diskettes, and CDs) Words defined in text (example: a nonswitched line is called a point-to-point line) Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictive clause."; letters as letters example: "The LUN address must start with the letter L.") New terms in text (except in a definition list): a view is a frame in a workspace that contains data Variables and values you must provide:... where myname represents... Monospace Examples and code examples File names, programming keywords, and other elements that are difficult to distinguish from surrounding text Message text and prompts addressed to the user Text that the user must type Values for arguments or command options Operating system-dependent variables and paths This publication uses the UNIX convention for specifying environment variables and for directory notation. When using the Windows command line, replace $variable with %variable% for environment variables, and replace each forward slash (/) with a backslash (\) in directory paths. For example, on UNIX systems, the $NCHOME environment variable specifies the directory where the Network Manager core components are installed. On Windows systems, the same environment variable is %NCHOME%. The names of environment variables are not always the same in the Windows and UNIX environments. For example, %TEMP% in Windows environments is equivalent to $TMPDIR in UNIX environments. If you are using the bash shell on a Windows system, you can use the UNIX conventions. About this publication vi

7 Chapter 1 Introduction With IBM Netcool Operations Insight, the IBM Netcool suite leverages industry leading analytics capabilities to provide both operational agility as well as operational efficiency. IBM Netcool Operations Insight brings Netcool/OMNIbus 8.1 and Netcool/Impact 7.1 together with Smart Cloud Analytics - Logfile Analysis (SCA-LA) into a tightly integrated solution. The Networks for Operations Insight bundle is optional and adds IBM Tivoli Network Manager and Netcool Configuration Manager to the solution to provide additional network management capabilities such as network discovery, visualization, event correlation and root-cause analysis, and configuration and compliance management. The value propositions for upgrading to IBM Netcool Operations Insight are clear. When presented with new versions of products and new technologies however, one of the first considerations an administration team will likely make is how easy or difficult will it be to get from the incumbent versions of the installed products to the new. The IBM Netcool engineering test team have a program whereby they work with key large Netcool customers and work on-site with the upgrade of existing Netcool environments to the latest product versions during the beta phase. The feedback from this exercise is to ensure that any bugs are ironed out and the upgrade process is made as smooth and troublefree as possible prior to releasing the product as generally available. The purpose of this document is to provide a supplementary guide to lead those responsible for upgrading existing Netcool installations to IBM Netcool Operations Insight through the steps highlighting any "gotchas" along the way. A high level list of the steps are as follows: Install IBM Installation Manager on all target machines Perform Netcool/OMNIbus Core migration Perform Netcool/OMNIbus Web GUI migration Perform Netcool/Impact migration Apply Event Analytics configuration and create Seasonality Reports Perform Smart Cloud Analytics Logfile Analysis (SCA-LA) set-up Configure Networks for Operational Insights integration (optional) Install and configure Tivoli Common Reporting and Event List tools (optional) Configure processes to automatically start on machine boot (optional) Note: Having a historical event archive containing the REPORTER schema is a prerequisite for the seasonality functionality. If this is not configured already, it will have to be installed and configured. A license to use DB2 for this purpose is included in the IBM Netcool Operations Insight licensing model. For the TIP-to-DASH, Netcool/OMNIbus and Netcool/Impact upgrades, if the upgrade is being performed on the same box (ie. in situ), the installer will install the new version of the product into a parallel directory and then migrate the configuration. With the exception of Tivoli Common Reporting, all the new versions of the products contained within the IBM Netcool Operations Insight suite use the IBM Install Manager which replaces the Deployment Engine. Prior to installing the new version of each product therefore, an installation of IBM Install Manager is required. Introduction 1

8 Note: The official product documentation for IBM Netcool Operations Insight - including the recommended "Quick Start Guide" - can be found here: /soc/collaterals/soc_netops_kc_welcome.html Finally, note that this document can be used either to upgrade an incumbent Netcool installation to IBM Netcool Operations Insight or for installing IBM Netcool Operations Insight from scratch. Introduction 2

9 Chapter 2 This chapter walks through each of the migration steps for each of the product components. Prior to beginning the process, identify the user you will use to perform the product upgrades with. It is recommended to use the same user as the incumbent product has been installed as to avoid any potential file permission issues during the upgrade process. Install and run IBM Prerequisite Scanner for each product Prior to installing each product listed in this guide, it is recommended to run the IBM Prerequisite Scanner (PRS) to ensure the target system is suitable and no installation problems are foreseeable. IBM Prerequisite Scanner can be downloaded from the following location: Search for: "IBM Prerequisite Scanner" Note: The latest version at the time of publication of this document is: After downloading the latest available version, un-tar the tar archive into the target directory. The IBM Prerequisite Scanner then needs to be run with each of the component codes as follows, where appropriate: prereq_checker.sh NOC detail (for IBM Netcool/OMNIbus) prereq_checker.sh NOW detail (for IBM Netcool/OMNIbus Web GUI) prereq_checker.sh NCI detail (for IBM Netcool/Impact) prereq_checker.sh ODP detail (for IBM Jazz for Service Management) prereq_checker.sh DSH detail (for IBM Dashboard Application Services Hub) prereq_checker.sh TNM detail (for IBM Tivoli Network Manager) prereq_checker.sh NCM detail (for IBM Tivoli Netcool Configuration Manager) prereq_checker.sh TIP detail (for IBM Tivoli Integrated Portal) prereq_checker.sh TCR detail (for IBM Tivoli Common Reporting) Note: Set the environment variable: IMPACT_PREREQ_BOTH=True before running the prerequisite check for Netcool/Impact in order to perform checks for both the Server and GUI Server components. A full list of prerequisite product codes can be found at the following location: Check maxproc and ulimit settings It is recommended to check the maxproc and ulimit settings on the servers you are configuring to ensure they are set to the following minimum values. 3

10 maxproc Open the following file: /etc/security/limits.d/90-nproc.conf Set nproc to: ulimit Open the following file: /etc/security/limits.conf Set nofile to: Install IBM Installation Manager The IBM Installation Manager replaces the IBM Deployment Engine across the new versions of the IBM Netcool Operations Insight product components. Installing the IBM installation Manager is the first step of the migration for each of the target machines therefore. Download the software The compressed file distribution of IBM Netcool/OMNIbus 8.1 is available from IBM Passport Advantage and on DVD and includes IBM Installation Manager. You only need to download Installation Manager separately if you are installing Netcool/OMNIbus 8.1 directly from an IBM repository or from a local repository. If you need to install the IBM Installation Manager first, you can download it from IBM Fix Central from the following location: stallation+manager&platform=linux&function=all Download the relevant version for your platform and unzip the downloaded package into an empty directory. Note: It is recommended to install the latest version of IBM Installation Manager. If multiple versions are available, please select the latest version therefore. Create a IBM Installation Manager data directories In the example given in this document, IBM Installation Manager will be installed in group mode to provide the widest variety of options and flexibility. Prior to running the IBM Installation Manager installer, create the following target directories and set the file permissions for the designated user and group that IBM Installation Manager will be run as and any subsequent product installations: 4

11 Main installation directory: where the product binaries will be installed; Data directory: where IM stores information about installed products; Shared directory: where IM stores downloaded packages used for rollback. It is important to ensure that these directories are separate; particularly for the latest versions of IBM Installation Manager. EXAMPLE # mkdir /opt/ibm/netcoolim # mkdir /opt/ibm/netcoolim/ibmim # mkdir /opt/ibm/netcoolim/ibmimdata # mkdir /opt/ibm/netcoolim/ibmimshared # chown -R netcool:ncoadmin /opt/ibm/netcoolim Note: For an overview of IBM Installation Manager installation modes, please read the following information contained within the IBM Netcool/OMNIbus documentation: us.doc_8.1.0/omnibus/wip/install/reference/omn_ins_im_install_overview.html Install the IBM Installation Manager After decompressing the IBM Installation Manager package, start the installation per the following example command (group mode): groupinst -dl /opt/ibm/netcoolim/ibmimdata Note: The command line option -dl specifies the location of the data directory. Be sure to specify the directory location for the newly created main installation directory (/opt/ibm/netcoolim/ibmim) when you run the installer. Note that the shared directory location will be asked for at a later time during the installation of the first product. At this time you should specify the shared directory created here - ie: /opt/ibm/netcoolim/ibmimshared Perform Netcool/OMNIbus core migration The next step is to upgrade the Netcool/OMNIbus core components. The upgrade steps to upgrading a system running Netcool/OMNIbus 7.x are as follows: Install IBM Installation Manager Download required packaged (or connect directly to Passport Advantage) Install Netcool/OMNIbus 8.1 core via IBM Installation Manager Migrate configuration from old installation to new installation The IBM Installation Manager can connect directly to IBM to download and install products however this requires that the target host has access to the Internet. Alternatively, the 5

12 installation packages can be downloaded first and then copied to the target host for installation. The different installation options are documented at the following location: us.doc_8.1.0/omnibus/wip/install/reference/omn_ins_im_omn_install_overview.html Use best practice upgrade techniques to minimise disruption In order to minimise disruption to production systems, it is recommended to utilise the best practices document entitled: Upgrading Netcool/OMNIbus 7.x in Production Environments - Best Practices. This document is available from the Netcool/OMNIbus wiki best practices page: 20Netcool%20OMNIbus/page/Best%20Practices Note that this document contains instructions for upgrading in situ as well as upgrading an installation including migrating to new hardware. If deploying new hardware is part of the upgrade, Netcool/OMNIbus 8.1 can be installed afresh and the custom configuration SQL and nco_confpack files imported afresh. Data transfer from the incumbent system to the new system will be done via the unidirectional ObjectServer Gateway, per the best practice document referenced above. If the custom configuration has not been implemented in the best practice way, the database files can be copied over manually from the $OMNIHOME/db directory. Note that when any copied ObjectServers are started within the new environment, the update SQL scripts will need to be run against each one to update the internal default components. Note: More details on how to update the ObjectServer internal components can be found in a later section in this document, entitled: Updating the ObjectServer schema. Download the software If the system to be upgraded does not have direct Internet access, you will need to first connect to Passport Advantage and download the necessary installation packages. The Passport Advantage eassembly part number for IBM Tivoli Netcool/OMNIbus v8.1 for Netcool Operations Insight v1.2 eassembly English Multiplatform is: CRSB8EN. Note: Other part numbers for Netcool/OMNIbus 8.1 can be found on this tech note: SSSHTQ&mync=E EXAMPLE The Netcool administrator at Widgetcom needs to upgrade Netcool/OMNIbus to version 8.1 however the server does not have Internet access. After installing the IBM Installation Manager on the target system therefore, the Netcool administrator connects to Passport Advantage from her laptop and downloads the following package: 6

13 IBM Tivoli Netcool OMNIbus 8.1 Core Linux 64bit Multilingual (CN05EML) Once downloaded, the package is copied to the target system and unzipped into a new directory. Note that the destination directory of the unzipped package will become a software repository for IBM Installation Manager. Define the target installation directory Netcool/OMNIbus 8.1 needs to be installed into a separate directory to the incumbent Netcool/OMNIbus installation. You will either need to rename the existing Netcool directory ($NCHOME) to a different name or create a new directory for the new version to be installed into. For example: # mv /opt/ibm/tivoli/netcool /opt/ibm/tivoli/netcool_old # mkdir /opt/ibm/tivoli/netcool # chown -R netcool:ncoadmin /opt/ibm/tivoli/netcool OR # mkdir /opt/ibm/netcool # chown -R netcool:ncoadmin /opt/ibm/netcool Install Netcool/OMNIbus 8.1 via IBM Installation Manager Netcool/OMNIbus is installed via the IBM Installation Manager. Use the following information to start and run the IBM Installation Manager and install the Netcool/OMNIbus package: us.doc_8.1.0/omnibus/wip/install/reference/omn_ins_im_updating_overview.html EXAMPLE The Netcool administrator at Widgetcom has downloaded and copied the Netcool/OMNIbus 8.1 installation package to the target host. The downloaded package file is then copied to a destination directory and unzipped ready for use by the IBM Installation Manager. The Netcool administrator next logs in to the target host as the installation user and runs the IBM Installation Manager as follows: $ cd /opt/ibm/installationmanager/eclipse $./IBMIM -record omnibus_record_file.txt -log omnibus.log 7

14 Note: A record file is created via the -record switch in case the installation needs to be done again in silent mode. The log file option is selected via the -log switch so that the installation progress can be stored for future reference. 8

15 Set up the software repository When the IBM Installation Manager is run for the first time, no software repositories have been defined yet. As a result, the following screen is shown to the user when the Install option is clicked: If the host machine is connected to the Internet, the easiest method is simply to click on the link "Passport Advantage" and enter the credentials needed to access the software. If the host machine has no Internet connection or a local repository is to be used, the user should use the "Repositories" link to define some local repositories for IBM Installation Manager to use. Note: file. A local repository may be a server on the local network or a downloaded package 9

16 EXAMPLE The Netcool administrator starts the IBM Installation Manager and clicks on "Repositories" in order to point the installer at the downloaded installation package. The Netcool administrator is initially presented with an empty list of repositories and so clicks "Add Repository " to add a new one. After navigating to the file named repository.config within the downloaded, unzipped package and clicking "OK", a new repository appears in the repository listing: IBM Tivoli Netcool OMNIbus 8.1 Core Linux 64bit Multilingual: OMNIbusRepository/repository.config 10

17 After clicking on "OK", the software is now ready to be installed: 11

18 Install Netcool/OMNIbus 8.1 Once the repository has been configured, Netcool/OMNIbus 8.1 is ready to be installed. EXAMPLE The Netcool administrator clicks selects Netcool/OMNIbus 8.1 from the options list and clicks "Next" to begin the installation process. 12

19 After accepting the license agreement, the Netcool administrator sets the IBM Installation Manager shared resources directory to be under the IBM Installation Manager installation location and clicks "Next". Note: This is the directory that was set up previously when the IBM Installation Manager was installed (eg: /opt/ibm/netcoolim/ibmimshared/). /opt/ibm/netcoolim/ibmimshared /opt/ibm/netcoolim/ibmim/eclipse/ibm Any subsequent product installations will not ask again for the shared directory location. Note: The default location for the shared directory location is under the current user's home directory hence ensuring this is set correctly is important to ensure the desired location is used for the shared directory resources. 13

20 Next the Netcool administrator needs to select the installation directory for Netcool/OMNIbus 8.1. This should be set to the installation directory set up previously. /opt/ibm/netcoolim/ibmimshared /opt/ibm/netcoolim/ibmim/eclipse/ibm After clicking "Next", the Netcool administrator is presented with the list of installable items. The default is to install all features. The Netcool administrator elects to install all features and clicks on "Next" to continue the installation. 14

21 Next the Netcool administrator is given the option to migrate data from an old Netcool/OMNIbus installation. In this case we will migrate the data from our incumbent Netcool/OMNIbus 7.4 installation located in: /opt/ibm/tivoli/netcool Note: The source directory specified here should be the incumbent installation's $NCHOME location and not the $OMNIHOME location. 15

22 Finally, the Netcool administrator is presented with the following screen indicating that the installation and migration was successful. The Netcool administrator selects "None" and then "Finish" to exit the installer. Note: In a migration scenario, running the initial configuration wizard is not necessary since the ObjectServers are already set up and configured. The initial configuration wizard is useful for a new deployment. Updating the ObjectServer schema If Netcool/OMNIbus has either been upgraded in situ on the same host, or the ObjectServer database files have been copied from the old system to the new, the ObjectServer internal tables and triggers will need to be updated via the update SQL scripts provided with Netcool/OMNIbus 8.1 in the $OMNIHOME/etc directory. This will enable the ObjectServer to take advantage of new features. Instructions for how to do this are included in the product documentation: us.doc_8.1.0/omnibus/wip/install/task/omn_upg_obj_schema.html Note: You will need to apply the update scripts in the correct order from the incumbent system version through to the one labelled: update74fp3to81.sql 16

23 Updating log file locations As part of an in situ upgrade, Netcool/OMNIbus 8.1 is installed to a separate directory. This causes any created log files within the ObjectServer to have the incorrect paths. Consequently when the ObjectServer is started within the new 8.1 environment, the logs will continue to write to the old directory structure. It is very simple to correct this. Simply start up the Configuration Manager (nco_config) and modify the log files to show the correct path. The change can be made on-the-fly and will take effect immediately. Note: This will need to be done once only for each ObjectServer in your environment. Updating the standard multitier architecture configuration Where the standard multitier architecture configuration has been used, some updates are needed with the upgrade to Netcool/OMNIbus 8.1. Notes on how to perform this task including the addition of support for the new Probe Registry are given on the following link: us.doc_8.1.0/omnibus/wip/install/task/omn_upg_multitier_architecture.html 17

24 Install DB2 and configure REPORTER schema The Tivoli Data Warehouse (TDW) component set up with the REPORTER schema for historical event archiving is a prerequisite of the seasonality functionality of IBM Netcool Operations Insight. This should be installed and configured therefore if it has not already been set up. The JDBC Gateway feeds the TDW and the "Configuration Scripts" are used to initialise the schema prior to setting up the Gateway. The part number for the eassembly that contains the DB2 database application used for the TDW is: DB Enterprise Server Edition for Tivoli Netcool/OMNIbus v8.1 eassembly Multilingual Multiplatform (CRS7MML) The part number for the REPORTER schema configuration scripts is: Netcool/OMNIbus 8 Plus JDBC Gateway Configuration Scripts (CIZZ2EN) EXAMPLE The Widgetcom Netcool Administrator connects to Passport Advantage and downloads the following two packages: IBM DB2 Server V10.5 for Linux on AMD64 and Intel EM64T systems (x64) Multilingual (CIXV0ML) Netcool/OMNIbus 8 Plus JDBC Gateway Configuration Scripts (CIZZ2EN) The Netcool administrator decompresses the downloaded package and runs db2setup to install DB on the target machine. Note: DB2 should be installed by the root system user since the setup wizard needs to create a number of users in the process. Next, the Netcool administrator runs IBM Installation Manager on the primary Aggregation Netcool/OMNIbus 8.1 box and installs the Gateway configuration scripts. The SQL file needed to create the REPORTER schema is installed to: $OMNIHOME/gates/reporting/db2/db2.reporting.sql The Netcool administrator then makes some necessary modifications to the SQL file prior to execution against DB2. First, the Netcool administrator uncomments the "CREATE DATABASE" line and sets the default username and password to match the DB2 installation: CREATE DATABASE CONNECT TO reporter USER db2inst1 USING Next, the Netcool administrator uncomments the following lines in the SQL file so that any associated journal and details rows are deleted from the database when the corresponding alerts are deleted. -- Uncomment the line below to enable foreign keys -- This helps pruning by only requiring the alert to be 18

25 -- deleted from the status table, CONSTRAINT eventref FOREIGN KEY (SERVERNAME, SERVERSERIAL) REFERENCES REPORTER_STATUS(SERVERNAME, SERVERSERIAL) ON DELETE CASCADE) Note: The above SQL appears twice in the SQL file - once in the details table definition and once in the journal table definition - and both need to be uncommented. Finally, the Netcool administrator executes the SQL file against the DB2 database by running the following command as system user: db2inst1: $ db2 -td@ -vf db2.reporting.sql Note: The DB2 installer creates a number of users including db2inst1. Housekeeping considerations for DB2 Consideration should be given to the housekeeping of the historical event data in the DB2 instance. Sample SQL is provided to do this in the Netcool/OMNIbus 8.1 Best Practices Guide in the section entitled: Historical event archive sizing guidance. Note: The Netcool/OMNIbus 8.1 Best Practices Guide can be downloaded from the following location: Another option to consider is the use of the DB2 administrative task scheduler. gui.doc/doc/c html Install the Netcool/Gateway for JDBC After the core Netcool/OMNIbus 8.1 components have been installed, the JDBC Gateway needs to be installed via the IBM Installation Manager. The JDBC Gateway will connect the ObjectServer infrastructure to the historical event archive database. Note: The historical event database is a necessary component of the IBM Netcool Operations Insight solution. The seasonality function uses the historical event archive to work off. The historical archive needs to be configured for REPORTER mode. The Passport Advantage eassembly part number for Netcool/OMNIbus 8.1 is: CRS7HML. This eassembly includes the JDBC Gateway as one of the downloadable components. EXAMPLE The Widgetcom Netcool administrator connects to Passport Advantage and downloads the JDBC Gateway for Linux from the Netcool/OMNIbus 8.1 eassembly: Netcool/OMNIbus 8 Plus Gateway for JDBC (nco-g-jdbc 5_0) (CIZZ4EN) 19

26 After decompressing the downloaded package to the software repository directory, the Netcool administrator installs the Gateway packages via the IBM Installation Manager. Since the migration has already been done, the JDBC Gateway properties files will already be present in the $OMNIHOME/etc/ directory, ready for use, since the JDBC Gateway was installed on the incumbent system. Where this is not the case, the files can be copied afresh from: $OMNIHOME/gates/jdbc/ Example JDBC Gateway properties are included below: # Reporting mode properties Gate.Jdbc.Mode: 'REPORTING' # Table properties Gate.Jdbc.StatusTableName: 'REPORTER_STATUS' Gate.Jdbc.JournalTableName: 'REPORTER_JOURNAL' Gate.Jdbc.DetailsTableName: 'REPORTER_DETAILS' # JDBC Connection properties Gate.Jdbc.Driver: 'com.ibm.db2.jcc.db2driver' Gate.Jdbc.Url: 'jdbc:db2://localhost:50000/reporter' Gate.Jdbc.Username: 'db2inst1' Gate.Jdbc.Password: 'db2inst1' Gate.Jdbc.ReconnectTimeout: 30 Gate.Jdbc.InitializationString: '' # ObjectServer Connection properties Gate.RdrWtr.Username: 'root' Gate.RdrWtr.Password: 'netcool' Gate.RdrWtr.Server: 'AGG_V' Perform Netcool/OMNIbus Web GUI migration The next step in the IBM Netcool Operations Insight upgrade is to upgrade the existing installation of the UI server. This document covers the upgrade from the Tivoli Integrated Portal (TIP) running Netcool/OMNIbus Web GUI. Clone existing configuration The first step in upgrading to the new UI is to create a copy of the configuration of the existing system. This is achieved via the Web GUI clone function. Prior to starting the clone process, ensure the product.home parameter is set correctly in the clone properties file. This file is used by the cloning process. The default location for clone properties file is: 20

27 /opt/ibm/tivoli/netcool/omnibus_webgui/integration/plugins/omnibuswe bgui_clone_settings.properties The following lines should be uncommented and the product.home property should be set to the location of the omnibus_webgui directory. For example: TIP.profileName=TIPProfile TIP.cellName=TIPCell product.home=/opt/ibm/tivoli/netcool/omnibus_webgui EXAMPLE The Widgetcom Netcool administrator uses the clone function to export the configuration of the existing TIP/Web GUI server. $ cd /opt/ibm/tivoli/tipv2/profiles/tipprofile/bin $./tipcli.sh Export --username tipadmin --password netcool --settingfile $WEBGUI_HOME/integration/plugins/OMNIbusWebGUI_TIP_clone.properties The Netcool administrator reviews the resulting log file for any errors. /opt/ibm/tivoli/tipv2/profiles/tipprofile/logs/tipcli.log The Netcool administrator copies the exported output data file (data.zip) to a backup location to be used to import into the new system later. $ cd /opt/ibm/tivoli/tipv2/profiles/tipprofile/output $ cp data.zip ~/backup/. Download the software If the system to be upgraded does not have direct Internet access, you will need to first connect to Passport Advantage and download the necessary installation packages. The UI component is installed via the following four packages: IBM WebSphere Application Server V for Jazz for Service Management; IBM Jazz for Service Management V ; IBM Dashboard Application Services Hub ; STEP 1 IBM Netcool/OMNIbus 8.1 Web GUI with the Netcool Operations Insight extensions. Search for the following eassembly part number: 21

28 Jazz for Service Management for Netcool/OMNIbus v8.1 eassembly Multilingual Multiplatform (CRS7LML) Download the following two items from this eassembly for your platform: STEP 2 IBM WebSphere Application Server V for Jazz for Service Management Jazz for Service Management V Search for the following eassembly part number: IBM Tivoli Netcool/OMNIbus v8.1 for Netcool Operations Insight v1.2 eassembly English Multiplatform (CRSB8EN) Download the following item from this eassembly for your platform: STEP 3 IBM Tivoli Netcool OMNIbus 8.1 WebGUI & Extensions for Netcool Operations Insight Unzip each of the downloaded bundles into its own separate directory and unzip them. Now the software is ready for IBM Installation Manager to install. These three directories will be configured as three new repositories for IBM Installation Manager in a later step. EXAMPLE The Netcool administrator at Widgetcom needs to upgrade Netcool/OMNIbus Web GUI to version 8.1 however the server does not have Internet access. After installing the IBM Installation Manager on the target system therefore, the Netcool administrator connects to Passport Advantage from her laptop and downloads the following three packages from the eassembly bundles for Linux: IBM WebSphere Application Server V for Jazz for Service Management for Linux Multilingual (CIES6ML) Jazz for Service Management V for Linux Multilingual (CIXA2ML ) IBM Tivoli Netcool OMNIbus 8.1 WebGUI & Extensions for Netcool Operations Insight Linux 64bit English (CN0K5EN) After downloading the above three packages, the Netcool administrator copies each to its own directory and unzips them, ready for use by IBM Installation Manager. Define the target installation directory The next step is to create new directories to install WebSphere, Jazz for Service Management and Netcool/OMNIbus 8.1 Web GUI into. EXAMPLE The Netcool administrator logs into the target host as the root user and runs the following commands to create two new directories: # mkdir /opt/ibm/jazzsm # chown -R netcool:ncoadmin JazzSM # mkdir /opt/ibm/websphere # chown -R netcool:ncoadmin WebSphere 22

29 # mkdir /opt/ibm/webgui # chown -R netcool:ncoadmin WebGUI Install the UI components via IBM Installation Manager The IBM Netcool Operations Insight UI components are installed via the IBM Installation Manager. Use the following information to start and run the IBM Installation Manager and install the UI packages: us.doc_8.1.0/omnibus/wip/install/reference/omn_ins_im_updating_overview.html EXAMPLE The Netcool administrator at Widgetcom has previously downloaded and copied the IBM Netcool Operations Insight UI installation packages to the target host, and unzipped them ready for use by the IBM Installation Manager. The Netcool administrator next logs in to the target host as the installation user and runs the IBM Installation Manager as follows: $ cd /opt/ibm/installationmanager/eclipse $./IBMIM 23

30 Set up the software repository When the IBM Installation Manager was run for the first time as in a previous example, no software repositories had been defined yet and the initial repository had to be set up. If the IBM Installation Manager is being run subsequently, the new packages have to be added. From the initial screen, select File Preferences from the menus: As in the Netcool/OMNIbus 8.1 installation example, click on "Add Repository " and add four new repositories from the three UI packages by navigating to the following repository definition files: IBM WebSphere Application Server V for Jazz for Service Management: WASRepository/disk1/diskTag.inf Jazz for Service Management V : JazzSMRepository/disk1/diskTag.inf IBM Tivoli Netcool OMNIbus 8.1 WebGUI & Extensions for Netcool Operations Insight: OMNIbusWebGUIRepository/repository.config OMNIbusWebGUI_NOIExtensionsRepository/repository.config 24

31 When finished, there will be four new repositories defined in the IBM Installation Manager: Click on "OK" to apply the changes and close the Preferences dialogue box. The UI is now ready to be installed. Note: The UI is installed in two steps. First WebSphere Application Server (WAS), Jazz for Service Management (JazzSM) and Dashboard Application Services Hub (DASH) are installed. Second, Netcool/OMNIbus 8.1 Web GUI and the IBM Netcool Operations Insight extensions are installed. Install WAS, JazzSM and DASH The first step of installing the UI is to install: WebSphere Application Server (WAS), Jazz for Service Management (JazzSM) and Dashboard Application Services Hub (DASH). The IBM Installation Manager is used to install these components. Start the IBM Installation Manager and select the following packages to install: IBM WebSphere Application Server IBM WebSphere SDK Java Technology Edition (Optional) Jazz for Service Management extension for IBM WebSphere 8.5 IBM Dashboard Application Services Hub 25

32 EXAMPLE The Widgetcom Netcool administrator starts the IBM Installation Manager and selects the following four packages to install and clicks "Next" to continue the installation. After accepting the license agreements, the Netcool administrator is presented with the installation locations for the products. The Netcool administrator sets the paths for both WebSphere and Jazz for Service Management to be the directories created earlier. /opt/ibm/netcoolim/ibmimshared /opt/ibm/netcoolim/ibmim/eclipse/ibm After adjusting the installation directories, the Netcool administrator clicks "Next" to continue the installation. 26

33 English is pre-selected and no other languages are required at this time. The Netcool administrator clicks "Next" to accept the default language settings and to continue the installation. The Netcool administrator accepts the default feature selections and clicks "Next" to continue the installation. 27

34 The Netcool administrator accepts all the default settings and just enters an administrative password for the user to use. The Netcool administrator clicks on "Validate " to validate the settings and then on "Next" to continue the installation. The Netcool administrator is presented with the list of port settings for Jazz for Service Management. She accepts the default ports and clicks "Next" to continue the installation. 28

35 The Netcool administrator is presented with the context root for the Dashboard Application Services Hub. She accepts the default setting and clicks "Next" to continue the installation. The Netcool administrator is presented with the installation summary page. She doublechecks the installation paths and begins the installation by clicking "Install". /opt/ibm/netcoolim/ibmimshared /opt/ibm/netcoolim/ibmim/eclipse/ibm 29

36 The Netcool administrator makes a nice cup of tea while monitoring the installation progress, which takes around 30 minutes to complete. /opt/ibm/netcoolim/ibmimshared /opt/ibm/netcoolim/ibmim/eclipse/ibm When finished, the Netcool administrator is presented with the successful installation screen. The Netcool administrator selects "None" and then clicks "Finish" to complete the installation. 30

37 Install Web GUI and IBM Netcool Operations Insight extensions The second step of installing the UI is to install: IBM Tivoli Netcool/OMNIbus Web GUI and Netcool Operations Insight Extensions for IBM Tivoli Netcool/OMNIbus Web GUI. The IBM Installation Manager is used to install these components. Start the IBM Installation Manager and select the following packages to install: IBM Tivoli Netcool/OMNIbus Web GUI Netcool Operations Insight Extensions for IBM Tivoli Netcool/OMNIbus Web GUI EXAMPLE The Widgetcom Netcool administrator starts the IBM Installation Manager and selects the following two packages to install and clicks "Next" to continue the installation. 31

38 After accepting the license agreements, the Netcool administrator is presented with the installation locations Web GUI. The Netcool administrator sets the path to be the one created earlier: /opt/ibm/webgui /opt/ibm/netcoolim/ibmimshared /opt/ibm/netcoolim/ibmim/eclipse/ibm After adjusting the installation directory, the Netcool administrator clicks "Next" to continue the installation. On the next screen the Netcool administrator is presented with the feature selection. She ensures all features are selected and clicks "Next" to continue the installation. 32

39 The Netcool administrator reviews the WebSphere and Jazz for Service Management installation directory details, then enters the Jazz server administrator password, and then clicks on "Next" to continue the installation. The Netcool administrator reviews the SmartCloud Analytics Log Analysis (SCA-LA) settings, accepts the default settings, and then clicks on "Next" to continue the installation. Note: Since SCA-LA will be installed on the same machine, the default settings are correct. A production environment should use the fully qualified domain name instead of "localhost". 33

40 The Netcool administrator reviews the installation summary screen and clicks on "Install" to begin the installation of the Web GUI and the IBM Netcool Operations Insight extensions. /opt/ibm/netcoolim/ibmimshared /opt/ibm/netcoolim/ibmim/eclipse/ibm The installation takes a few minutes and finally the Netcool administrator is presented with the successful installation screen. The Netcool administrator clicks on "Finish" to complete the installation and enters the configuration options for Netcool/OMNIbus 8.1 Web GUI. 34

41 The installation completes and the Netcool administrator is presented with a new window that will guide her through the initial configuration wizard. The Netcool administrator uses the wizard to set up the authentication provider for Web GUI and set up the initial users and groups. 35

42 The datasources still need to be configured. The Netcool administrator will do this later and clicks "Finish" to complete the installation. Note: See the following documentation link for information on how to add or configure Web GUI datasources: us.doc_8.1.0/webtop/wip/task/web_con_datasourcesgui.html Restore previous configuration to new installation Now that the new UI is installed, the next step is to import the cloned configuration taken from the old system. EXAMPLE The Netcool administrator locates the clone properties file in the following location: /opt/ibm/webgui/omnibus_webgui/integration/plugins/omnibuswebgui_clo ne_settings.properties The Netcool administrator uncomments the following lines in the clone properties file and sets the product.home property to the location of the omnibus_webgui directory. For example: JazzSM.home=/opt/IBM/JazzSM JazzSM.cell.name=JazzSMNode01Cell product.home=/opt/ibm/webgui/omnibus_webgui The Netcool administrator copies the previously exported output data file (data.zip) from the backup location to the import directory in the new system. $ mkdir /opt/ibm/jazzsm/ui/input $ cp ~/backup/data.zip /opt/ibm/jazzsm/ui/input/. The Netcool administrator uses the clone function to import the configuration of the old TIP Web GUI server into the new JazzSM Web GUI server. $ cd /opt/ibm/jazzsm/ui/bin $./consolecli.sh Import --username smadmin --password netcool --settingfile /opt/ibm/webgui/omnibus_webgui/integration/plugins/omnibuswebgui_dash_clone. properties The Netcool administrator reviews the resulting log file for any errors. /opt/ibm/jazzsm/ui/logs/consolecli.log 36

43 Perform Netcool/Impact 7.1 migration Next the Netcool/Impact migration should be done. This will involve installing and configuring Netcool/Impact 7.1 with the IBM Netcool Operations Insight extensions, then migrating the custom configuration from the incumbent system into the new system. Download the software Netcool/Impact 7.1 can be downloaded from Passport Advantage. The Passport Advantage part number for Netcool/Impact 7.1 with the IBM Netcool Operations Insight extensions is: IBM Tivoli Netcool/Impact 7.1 Extensions for NOI Linux 64 bit English (CN0K7EN) EXAMPLE The Netcool administrator at Widgetcom intends to upgrade Netcool/Impact to version 7.1 with the IBM Netcool Operations Insight extensions and so connects to Passport Advantage and downloads the following package: IBM Tivoli Netcool/Impact 7.1 Extensions for NOI Linux 64 bit English (CN0K7EN) Once downloaded, the package is copied to the target system and decompressed, ready for installation. Define the target installation directory Netcool/Impact 7.1 needs to be installed into a separate directory to the incumbent Netcool/Impact installation. You will need to create a new directory for the new version to be installed into. For example: # mkdir /opt/ibm/impact # chown -R netcool:ncoadmin /opt/ibm/impact Install Netcool/Impact 7.1 The Netcool/Impact 7.1 installer automatically installs the IBM Installation Manager as a first step if one of the wrapper scripts are used: install_console.sh install_gui.sh install_silent.sh If Netcool/Impact 7.1 is being installed onto a machine where IBM Installation Manager has not already been installed therefore, this can be a convenient option to install the IBM Installation Manager and Netcool/Impact 7.1 in one go. If the IBM Installation Manager is already installed, the Netcool/Impact 7.1 installation files need to be added as a new repository and Netcool/Impact 7.1 installed via the existing instance. 37

44 Note: The Netcool/Impact 7.1 Installation & Deployment Guide contains full installation instructions and is available at the following location: oc_7.1/admin/imag_install_running_the_installer_gui_t.html EXAMPLE The Netcool administrator at Widgetcom has downloaded and copied the Netcool/Impact 7.1 installation files to the target host. Since the Netcool administrator is setting up a test system for the lab, all components are being installed on the same host. Note: In a production environment, it is recommended to install each Netcool/Impact server instance on its own server for performance reasons. Note that this does not necessarily apply to the Netcool/Impact GUI server component however which may coexist on the same host as a DASH server in a production environment. See later in this section for information on how to avoid port conflict in this case. Since the Netcool administrator is installing the Netcool/Impact 7.1 components onto the same host where WebSphere/JazzSM/DASH/WebGUI is installed, the IBM Installation Manager is already present. The Netcool/Impact 7.1 with Netcool Operations Insight extensions package is added as a new repository therefore to the IBM Installation Manager setup: IBM Tivoli Netcool OMNIbus 8.1 WebGUI & Extensions for Netcool Operations Insight: noi/impactextrepository/disk1/disktag.inf 38

45 Next, the Netcool administrator selects the packages to install and clicks "Next" to continue the installation. In this case, the Impact server, the Impact GUI server and the Impact IBM Netcool Operations Insight Extensions will be selected. After accepting the licensing agreement, the Netcool administrator sets the installation directory to the one configured earlier and then clicks "Next" to continue the installation. /opt/ibm/netcoolim/ibmimshared /opt/ibm/netcoolim/ibmim/eclipse/ibm 39

46 The Netcool administrator is then presented with the feature selection page. By default both the Impact server and the GUI server are preselected. The Netcool administrator accepts this default and clicks "Next" to continue the installation. 40

47 The Netcool administrator is then prompted to choose a user registry for user management and authentication. In this case, the Aggregation ObjectServer pair will be used. The Netcool administrator enters the primary and backup ObjectServer details and then clicks "Next" to continue the installation. Note: Since this is a lab environment and all components are being installed onto the same host, "localhost" is acceptable for the hostname. In a production environment however, the fully qualified domain name should be used. 41

48 The Netcool administrator is prompted to set an administrative password for the Netcool/Impact administrator user. The Netcool administrator accepts the default username of impactadmin, sets a password and clicks on "Next" to continue the installation. Note: The user needs to be created in the ObjectServer first before clicking "Next". The Netcool administrator is prompted to set the starting port for the range of ports used by both the Impact server and the Impact GUI server. Since Netcool/OMNIbus Web GUI is already using the default port of 16310, the Netcool administrator sets the starting port for the Impact GUI server to be (ie ) and then clicks "Next" to continue installation. Note: If the Netcool/Impact GUI server is not being installed onto the same box as a DASH instance, it is not necessary to change the "Starting port number" from the default. 42

49 The Netcool administrator is prompted to enter the location of the Impact Nameserver that the current instance should use. Since this is the only instance to be installed, the Netcool administrator accepts the default settings of the local host and clicks "Next" to continue. Note: Since this is a lab environment and all components are being installed onto the same host, "localhost" is acceptable for the hostname. In a production environment however, the fully qualified domain name should be used. 43

50 The Netcool administrator is prompted for the name of the Impact server instance, its cluster name and the command line port number it should use. The Netcool administrator accepts the default values and clicks "Next" to continue the installation. The Netcool administrator is prompted for the configuration details for the embedded Derby database used by Netcool/Impact for solutions and reporting. Since this is a standalone instance, the Netcool administrator accepts the default setting and clicks "Next" to continue. 44

51 Netcool/Impact is now ready to be installed. The Netcool administrator is presented with an installation summary. After checking the details, she clicks "Install" to begin the installation process. /opt/ibm/netcoolim/ibmimshared /opt/ibm/netcoolim/ibmim/eclipse/ibm Once installation is complete, the Netcool administrator is presented with the following page and clicks on "Finish" to complete the installation. 45

52 Migrate the configuration from the incumbent Netcool/Impact system After installation, the next step is to migrate the configuration from the incumbent system to the new system. Netcool/Impact 7.1 provides tools to migrate configuration from an older version of Netcool/Impact to the new version. Full step-by-step instructions are provided here and cover scenarios for migrating from different versions of Netcool/Impact and whether or not the old and new systems are installed on different machines or the same machine. oc_7.1/admin/migrating_intro_c.html Configure historical event archive database connection in Netcool/Impact The seasonality functionality in IBM Netcool Operations Insight is provided via Netcool/Impact. Netcool/Impact connects to the historical event archive database ondemand and processes the data therein to provide the Seasonality reports. From the Netcool/Impact configuration side, the first configuration task is to ensure it can connect to the historical event archive database therefore. EXAMPLE The Netcool administrator connects to the Netcool/Impact GUI and logs in as the administrative user: impactadmin; then selects "Seasonality" from the projects menu and then selects the "Data Model" tab. The Netcool administrator then right-clicks on the Data Source labelled: "ObjectServerHistoryDB2ForSeasonality" and selects "Test Connection" from the pop-up menu. Initially, the connection is not properly configured and so the Netcool administrator is presented with a "Connection could not be made" dialogue box. 46

53 After editing the datasource and entering the password of the database user as well as checking the host, port and schema name ("REPORTER"), the test is re-done and the result successful. The Netcool administrator then clicks on "OK" and the Save icon to save the changes. 47

54 Create a new Impact Data Provider in DASH Before using the seasonality functions, Netcool/Impact needs to be added as a Data Provider for Netcool/OMNIbus Web GUI. This is done via the Connections interface. EXAMPLE The Netcool administrator selects "Connections" from the "Console Settings" menu and then selects "Create new remote provider" from the "Connections" menu. The Netcool administrator next enters the protocol as "HTTPS-TLS", the host name, the port and user credentials for the Impact server into the new connection dialogue and clicks 48

55 "Search" to locate the Impact server. The data provider: "Impact_NCICLUSTER" is selected from the search results and the Netcool administrator enters a "Description" for the Data Provider and then clicks "OK" to save. Note: The "Name" and "Provider ID" fields are automatically populated when the "Impact_NCICLUSTER" Data Provider is selected. The new Data Provider is now available for use. 49

56 The Seasonality reporting capability is now available for use and can be accessed via the "Incidents" menu in Netcool/OMNIbus Web GUI. Note: For more information on configuring the fields the Seasonality reports return and how to create a new report, see the product documentation at the following link: /soc/event_analytics/concept/soc_ea_seasonaleventreportlet.html Configure single sign-on (SSO) between Jazz and Netcool/Impact This is an optional step. In order to configure single sign-on between Jazz and Netcool/Impact, please use the following steps: oc_7.1/admin/imag_configure_single_signon.html Install and configure Smart Cloud Analytics Logfile Analysis (SCA-LA) The final steps are to install and configure: Smart Cloud Analytics - Logfile Analysis (SCA-LA); Netcool/OMNIbus Insight Pack for SCA-LA; Netcool/OMNIbus Gateway for XML (Message Bus). Download the software Smart Cloud Analytics - Logfile Analysis (SCA-LA) can be downloaded from IBM Passport Advantage using the following part numbers: eassembly: IBM SmartCloud Analytics 1.2 Log Analysis eassembly Multilingual Multiplatform (CRSC0EN) 50

57 Component part numbers: IBM SmartCloud Analytics 1.2 Enablement Key English Linux (CITC0EN) IBM SmartCloud Analytics - Log Analysis 1.2 English Linux 64 bit (CITC1EN) IBM SmartCloud Analytics - Log Analysis 1.2 Big Insights Tooling English Linux (CIUB6EN) IBM Tivoli Netcool/OMNIbus Insight Pack V for SmartCloud Analytics - Log Analysis Linux English (CN0K8EN) Download all four of the above part numbers. The Netcool/OMNIbus Gateway for XML is the conduit used to forward Netcool/OMNIbus event data to SCA-LA and can be downloaded from IBM Passport Advantage using the following part numbers: eassembly: IBM Tivoli Netcool OMNIbus Event Forwarding V8.1 English Multiplatform eassembly (CRS7QML) Gateway part number: Netcool/OMNIbus 8 Plus Gateway for Message Bus (nco-g-xml 5_0) Multiplatform English (CN066EN) Installation documentation Installation instructions for the three Smart Cloud Analytics - Logfile Analysis (SCA-LA) parts can be found here: Installation instructions for the Netcool/OMNIbus Insight Pack can be found here: Installation instructions for the Netcool/OMNIbus Gateway for XML can be found here: tion/wip/concept/xmlgw_intro.html SCA-LA setup notes Once SCA-LA is installed with the latest fix packs and interim fixes and running, use the following notes to guide you in the configuration of SCA-LA and the Netcool/OMNIbus Gateway for XML. Note: The SCA-LA installer does not utilize IBM Install Manager configured in "Group Mode". Run install.sh from the install image therefore. 1. Install Netcool/OMNIbus Insight Pack using the following utility: 51

58 $UNITY_HOME/utilities/pkg_mgmt.sh 2. The Netcool/OMNIbus Gateway for XML must connect to SCA-LA visa SSL. Configure the Netcool/OMNIbus Gateway for XML properties file, SSL connections and SCA- LATransformers.xml per the official documentation: doc_1.2.0/soc/event_search/task/soc_es_config_sca-la_omnibus.html egration/sc /concept/xmlgw_intro.html ways/xmlintegration/sc /concept/xmlgw_config.html 3. To set up the SSL certificates for the Gateway to connect to SCA-LA, the first step is to generate both the client and server keys. CLIENT KEY $ cd $NCHOME/platform/linux2x86/32bit jre_directory/jre/bin $./keytool -genkey -alias youralias -keystore \ $OMNIHOME/java/security/client.jks SCA-LA SERVER KEY Open the following URL in your web browser where SCA-LA-host is the hostname of the host where SCA-LA is installed: Left mouse click the lock icon in the URL bar of the firefox GUI. Navigate to the certificate and export it to file on the computer where XML gate runs then import the certificate into your newly created key store: $ cd $NCHOME/platform/arch/32bit jre_directory/jre/bin $./ keytool -importcert -keystore \ $OMNIHOME/java/security/cacerts.jks -file SCA-LA-host.crt \ -alias SCA-LA-host 52

59 Next, run the following to verify your steps and show certificates in your trust store: $./keytool -list -keystore \ $OMNIHOME/java/security/client_passwd_is_netcool.jks Enter keystore password: Keystore type: jks Keystore provider: IBMJCE Your keystore contains 2 entries SCA-LA-host, Aug 8, 2014, keyentry, Certificate fingerprint (SHA1): 1D:90:5C:B3:42:EC:CF:F9:F3:44:B1:82:6F:96:38:05:31:9E:7F:8A SCA-LA-host, Aug 8, 2014, trustedcertentry, Certificate fingerprint (SHA1): 47:20:F8:1B:B5:B9:D6:66:FF:C9:E9:3B:7A:8E:76:E7:3B:6D:69:1F Finally, edit the SCA-LA transport file ($OMNIHOME/java/conf/SCA- LATransport.properties) and set up the following properties per the following example: SCA-LAURL= keystore=/opt/ibm/netcool/omnibus/java/security/client.jks keystorepassword=netcool truststore=/opt/ibm/netcool/omnibus/java/security/cacerts.jks truststorepassword=netcool username = unityadmin password = unityadmin jsonmsghostname = localhost jsonmsgpath = omnibus Note: The properties username and password are the credentials to log in to SCA-LA. 4. Next log into SCA-LA as user unityadmin and create data source: Use the Add Data Source wizard to configure a data source for Tivoli Netcool/OMNIbus events; Choose a custom type and enter the hostname where Netcool/OMNIbus Gateway for Message Bus Gateway is running; The value for "Name" must match the property "JsonMsgHostname" from the SCA-LATransport.properties file - for example: localhost 53

60 The value for "File Path" must match the property "JsonMsgPath" from the SCA- LATransport.properties file - for example: omnibus (see note below) Set the value for "Type" to: OMNIbus1100 Set the value for "Collection" to: OMNIbust1100-Collection Note: The value for "File Path" must also match the data source name specified during the installation of Netcool/OMNIbus. See page 33 for a screenshot of where this is configured. It is recommended to run the Netcool/OMNIbus Gateway for XML (nco_g_xml) in debug mode initially to verify that it is successfully sending events from Netcool/OMNIbus into SCA-LA by tailing the Gateway log: $OMNIHOME/log/G_SCA-LA.log If the Netcool/OMNIbus Gateway for XML is successfully sending events to SCA-LA, you will see messages like the following in the Gateway log file: $ tail -f $OMNIHOME/log/G_SCA-LA.log* grep -i success T13:37:01: Debug: D-GJA : [ngjava]: XMLGateway: [THREAD=40]: Successfully sent '2' log records from a batch of '2' events to data collector T13:38:01: Debug: D-GJA : [ngjava]: XMLGateway: [THREAD=44]: Successfully sent '1' log records from a batch of '1' events to data collector T13:42:02: Debug: D-GJA : [ngjava]: XMLGateway: [THREAD=48]: Successfully sent '1' log records from a batch of '1' events to data collector. Housekeeping considerations for SCA-LA Modify the delete.properties file and configure as appropriate to set up data housekeeping configuration for SCA-LA. Once configured, set up a UNIX cron job to run the cleaning script on a regular basis to remove old data. The deletion properties file is located here: $UNITY_HOME/utilities/deleteUtility/delete.properties The housekeeping script is located here: $UNITY_HOME/utilities/deleteUtility/deleteUtility.py Note: Per the installation prerequisites for SCA-LA, Python 2.x is required. The typical use case for housekeeping old SCA-LA data would be option 4: usecase_4 Use this use case to delete data for a time period and window that you specify 54

61 Configure Networks for Operations Insight Networks for Operations Insight is an optional feature of the IBM Netcool Operations Insight solution that integrates the products of the base Netcool Operations Insight solution with further network management products. IBM Networks for Operations Insight adds network management capabilities to the Netcool Operations Insight solution. These capabilities provide network discovery, visualization, event correlation and root-cause analysis, and configuration and compliance management that provide service assurance in dynamic network infrastructures. It contributes to overall operational insight into application and network performance management. The products of the Networks for Operations Insight feature are Network Manager V4.1.1, which includes Tivoli Integrated Portal and the Tivoli Netcool/OMNIbus V7.4 Web GUI, and Netcool Configuration Manager V Extra configurations are provided that you must install to set up the integration between the base products and the Networks for Operations Insight feature products. Detailed upgrade, migration and integration instructions are provided in the IBM Knowledge Centre at the following location: /omn_nmip/task/nnm_noi_ins_extendtonetcooloperationsinsight.html Install IBM Tivoli Common Reporting 3.1 (optional) In order to use IBM Tivoli Common Reporting (TCR), it needs to be installed and configured. Note: Before beginning the installation of IBM Tivoli Common Reporting, ensure Jazz is running. IBM Tivoli Common Reporting will install such that the Jazz stop/start script also stops/starts the Cognos-10 processes of TCR. Perform prerequisite checks Before you begin installing IBM Tivoli Common Reporting, run the IBM Prerequisite Scanner as outlined on page 3 of this document to ensure the target system is suitable. For UNIX platforms, verify that the following RPMs are installed: openmotif.i686 compat-glibc compat-libstdc openmotif openmotif-2.3+ Download the software The latest version of IBM Tivoli Common Reporting at the time of writing is version The Passport Advantage part numbers for IBM Tivoli Common Reporting version are as follows: IBM Tivoli Common Reporting V for AIX Multilingual (CIN3HML) 55

62 IBM Tivoli Common Reporting V for Linux Multilingual (CIN3IML) IBM Tivoli Common Reporting V for Linux on System z Multilingual (CIN3JML) IBM Tivoli Common Reporting V for Windows Multilingual (CIN3KML) Configure DB2 for Cognos Ahead of installing IBM Tivoli Common Reporting, DB2 needs to be configured to store the Cognos report artefacts. Use the following steps to do this: 1. Generate the DB2 SQL script to create the schema: $ cd <tcr-3.1_install_image_directory>/tcrinstaller $./TCR_generate_content_store_db2_definition.sh CogDB netcool The tcr_create_db2_cs.sql script was created 2. Copy the generated SQL script to a temporary directory and execute it against your DB2 instance as the DB2 user: db2inst1 $ cp tcr_create_db2_cs.sql /tmp/tcr_create_db2_cs.sql $ su db2inst1 c "db2 -vtf /tmp/tcr_create_db2_cs.sql" Note: Look for the following message in the output: "DB20000I The SQL command completed successfully." Install IBM Tivoli Common Reporting As the same user that the prior products have been installed (eg: netcool), run the IBM Tivoli Common Reporter installer script. Note: If installing IBM Tivoli Common Reporting on the same host as your DB2 instance, source the DB2 profile before running the installer so that all the DB2 environment variables are set up correctly - for example: $. /opt/ibm/db2/sqllib/db2profile Use the following command to install IBM Tivoli Common Reporting: $ cd <tcr-3.1_install_image_directory>/tcrinstaller $./install.sh 56

63 Use the following sequence of screenshots to guide you through the installation. The IBM Autonomic Deployment Engine will be installed if it is not already present: 57

64 Tell the TCR installer where JazzSM is installed: The installer displays a summary of the JazzSM server configuration: 58

65 Next the installer prompts for the JazzSM administrative user credentials: The DB2 instance administrative user credentials are also prompted for: 59

66 The installer next displays a pre-installation summary: Finally, the installation is complete: Note: The Jazz server stop/start script will now also stop/start TCR 3.1/Cognos

67 Configure IBM Tivoli Common Reporting To show the reports in IBM Tivoli Common Reporting, you need to create a connection between IBM Tivoli Common Reporting and the DB2 relational database. Then, you import the reports package, which is supplied with IBM Netcool/OMNIbus into IBM Tivoli Common Reporting and verify that the import was successful. The steps illustrated in this section are documented here: Note: Before you begin, copy the TCR reports that ship with Netcool/OMNIbus to the Cognos deployment directory - for example: cp $OMNIHOME/extensions/tcr_event_reports/Netcool_OMNIbus.zip /opt/ibm/jazzsm/reporting/cognos/deployment/. Use the steps illustrated below to help guide you through the configuration process. 61

68 ASSIGN REPORTING ROLE TO USERS The first step is to log in to the DASH console as the administrative user (ie. smadmin) and assign the relevant users the role: tcrportaloperator 62

69 Click on "Save" to save the user update and log out as user smadmin. 63

70 SET UP THE DB2 CONNECTION Next, log in to the DASH console as one of the users you have just assigned the tcrportaloperator role. This next step will import the reports into IBM Tivoli Common Reporting. Select: Administration from the pull-down menu: Select the "Configuration" tab, select "Data Source Connections" and then click on the create a new data source button: 64

71 Select the existing DB2 entry as source of the new datasource: Choose "DB2" for the connection type and uncheck the "Configure JDBC connection" box: Click on "Next" to continue. 65

72 Give the new datasource a label (ie. "reporter") and enter the user credentials for the db2inst1 user: Click on "Finish" to complete the setup of the new datasource. 66

73 IMPORT THE NEW REPORTS Next, click on "Content Administration" to import the new reports: Click on the "New Import wizard button: Select "Netcool_OMNIbus" as the deployment archive and click "Next": 67

74 Select the target name of the the packages to deploy: Note: The imported package will overwrite any existing one with the same name. Select to "Save and run once" to perform the import once only and click "Finish": The Netcool/OMNIbus reports will now be available for use under "Common Reporting": 68

75 Configure right click tools to launch into TCR reports It may be desirable to provide some right-click tools for your Event List users such that they can run historical event queries against the historical event archive. For example: To do this, create new tools within Netcool/OMNIbus Web GUI that will launch a new page with the given URL. The following provides examples of such tools. Note: Use the fully qualified domain name in these tools to ensure no password is asked for by Jazz when they are executed. Last30Days This tool passes the Node of the selected event(s) to the tool and returns event data for that Node for the last 30 days: wer&ui.action=run&ui.object=%2fcontent%2fpackage%5b%40name%3d%27netcool_omnib us%27%5d%2freport%5b%40name%3d%27event%20selection%27%5d&ui.name=event%20s election&run.outputformat=&run.prompt=true&p_criteriacolumn=node&p_criteriavalue ={@Node}&p_TCRDateFilter=Last 30 days Last90Days This tool passes the Node of the selected event(s) to the tool and returns event data for that Node for the last 90 days: wer&ui.action=run&ui.object=%2fcontent%2fpackage%5b%40name%3d%27netcool_omnib us%27%5d%2freport%5b%40name%3d%27event%20selection%27%5d&ui.name=event%20s election&run.outputformat=&run.prompt=true&p_criteriacolumn=node&p_criteriavalue ={@Node}&p_TCRDateFilter=Last 90 days 69