IBMTivoli Netcool Performance Manager 1.4.1 Wireless Component Document ... · Wireless Component Document Revision R2E1 Installation Guide. Note Before using this information and

IBM Tivoli Netcool Performance Manager 1.4.1Wireless ComponentDocument Revision R2E1

Installation Guide

��

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

© Copyright IBM Corporation 2006, 2015.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Introduction . . . . . . . . . . . . . vIntended audience . . . . . . . . . . . . vRequired skills and knowledge . . . . . . . . viThe Tivoli Netcool Performance Manager - Wirelesscomponent user publications. . . . . . . . . viService Management Connect . . . . . . . . viiTivoli Netcool Performance Manager technicaltraining . . . . . . . . . . . . . . . viiSupport information . . . . . . . . . . . viiConventions used in this publication . . . . . . vii

Typeface conventions . . . . . . . . . . vii

Chapter 1. Installation process . . . . . 1Preinstallation roadmap . . . . . . . . . . 1Installation roadmap. . . . . . . . . . . . 2

Chapter 2. Planning your installation . . 3Tivoli Netcool Performance Manager distribution . . 3Components of Tivoli Netcool Performance Manager 3

Supported configurations . . . . . . . . . 4

Chapter 3. Preparing for the Installation 5Server hardware and software requirements . . . . 5

Server hardware requirements . . . . . . . 5Server software requirements . . . . . . . . 5

Client computer hardware and softwarerequirements on Microsoft Windows . . . . . . 12

Client hardware requirements . . . . . . . 12Client software requirements . . . . . . . 12

Chapter 4. Preinstallation tasks . . . . 13Prerequisites . . . . . . . . . . . . . . 13

Required server information . . . . . . . . 13Required file systems . . . . . . . . . . . 13Ports and firewall configurations . . . . . . . 15

Distributed installations with Application,Loader, or Directory Servers on RHEL . . . . 16

Installing the platform package . . . . . . . . 17Creating user and group accounts . . . . . . . 18Setting directory ownership . . . . . . . . . 18Configuring the kernel . . . . . . . . . . 19Setting up the domain name. . . . . . . . . 19Setting up the host name . . . . . . . . . . 21Building Perl on Gateway servers . . . . . . . 21Setting memory for Java client processes . . . . 21

Chapter 5. Installing Jazz for ServiceManagement . . . . . . . . . . . . 23Common directory locations for Jazz for ServiceManagement . . . . . . . . . . . . . . 23Preparing your environment for a full installation ofJazz for Service Management . . . . . . . . 27Location of Jazz for Service Management software 27

Overview of Jazz for Service Managementinstallation . . . . . . . . . . . . . . 28

Performing an upgrade installation . . . . . 28Performing a fresh installation . . . . . . . 30Changing the default DB2 port . . . . . . . 32

Verifying the installation . . . . . . . . . . 33Verifying the Tivoli Common Reportinginstallation . . . . . . . . . . . . . 34Stopping Jazz for Service Managementapplication servers . . . . . . . . . . . 36Starting Jazz for Service Management applicationservers . . . . . . . . . . . . . . . 37

Uninstalling Jazz for Service Management . . . . 37

Chapter 6. Running the DependencyChecker tool . . . . . . . . . . . . 39

Chapter 7. Installing Oracle RDBMSand the Oracle client. . . . . . . . . 43Configuring Oracle environment variables . . . . 43Installing Oracle 11g . . . . . . . . . . . 44

Installing Oracle RDBMS (stand-alone system ordatabase server) . . . . . . . . . . . . 44Installing Oracle database 11g Client (ApplicationServer or Tivoli Common Reporting server inDistributed Systems only) . . . . . . . . 45Installing Oracle 11.2.0.4 Instant Client(stand-alone Server or database Server combinedwith Tivoli Common Reporting server) . . . . 47

Checking Oracle configuration . . . . . . . . 48Stopping the listener process . . . . . . . . 49

Chapter 8. Installing the SecurityDirectory Server and IBM DB2 . . . . 51Required packages . . . . . . . . . . . . 51Running the Security Directory Server installationscripts . . . . . . . . . . . . . . . . 52Installing the Security Directory Server client . . . 54

Chapter 9. Installing the Tivoli NetcoolPerformance Manager software . . . . 55Prerequisites . . . . . . . . . . . . . . 55Installing a stand-alone system unattended . . . . 56Installation of a stand-alone system . . . . . . 57

Running an interactive installation. . . . . . 57Installing the JBoss application server . . . . 58Installing the directory server schema . . . . 58Installing the database . . . . . . . . . . 59Installing the database schema . . . . . . . 59Database schema post-installation tasks . . . . 60Installing the cronjobs . . . . . . . . . . 61Installing the Gateways . . . . . . . . . 62Installing the technology packs . . . . . . . 62Encrypting passwords . . . . . . . . . . 64

© Copyright IBM Corp. 2006, 2015 iii

Installing a distributed system . . . . . . . . 65Running an interactive installation. . . . . . 65Installing a database server . . . . . . . . 65Installing a separate directory server . . . . . 70Installing the Application Server . . . . . . 73Installing a Loader Server . . . . . . . . 79Installing the Gateways separately. . . . . . 81

Applying Tivoli Netcool Performance Manager 1.4.1patch . . . . . . . . . . . . . . . . 82

Installing Tivoli Netcool Performance Manager1.4.1 patch . . . . . . . . . . . . . . 82

Uninstalling Tivoli Netcool Performance Manager1.4.1 patch . . . . . . . . . . . . . . . 83

Chapter 10. Installing the technologypacks separately . . . . . . . . . . 85Starting the system . . . . . . . . . . . . 85Setting up users and data sources . . . . . . . 86Checking database space . . . . . . . . . . 86Installing the technology pack: step 1. . . . . . 87Installing the technology pack: step 2. . . . . . 88Performing postinstallation checks for thetechnology packs . . . . . . . . . . . . 88Starting the SAP process monitor tool . . . . . 90Starting the Application Server . . . . . . . . 91Starting the Loaders . . . . . . . . . . . 91Configuring multiple identical Loaders . . . . . 92Loading data . . . . . . . . . . . . . . 93

Verifying data loading . . . . . . . . . . 93Removing Loadmaps and Loader configuration . . 94Creating a Loader on a distributed server . . . . 95

Chapter 11. Postinstallation tasks . . . 97Provisioning stored Busy Hours, Summaries, andData Availability. . . . . . . . . . . . . 97

Stored Busy Hours definitions . . . . . . . 97Summary definitions . . . . . . . . . . 98Data Availability definitions . . . . . . . . 98

Configuration of the Application Server memory(Optional) . . . . . . . . . . . . . . . 99

The jvm.args property . . . . . . . . . . 99Recommended jvm.args Property settings forApplication Servers . . . . . . . . . . 100

Configuration of Loader Server memory(Recommended) . . . . . . . . . . . . 100

The SAP configuration params property . . . 101Recommended JVM memory size settings forLoader Servers . . . . . . . . . . . . 102

Checking the Time Zone settings for the ReportScheduler. . . . . . . . . . . . . . . 102

Setting the Time Zone . . . . . . . . . 102Changing the default client ports . . . . . . . 103Integrating IBM Tivoli Monitoring . . . . . . 103Integrating IBM Tivoli Netcool/OMINbus WebGUI . . . . . . . . . . . . . . . . 103

Chapter 12. Starting Tivoli NetcoolPerformance Manager. . . . . . . . 105Rebooting the server . . . . . . . . . . . 105Process checks for Solaris . . . . . . . . . 106Process checks for AIX . . . . . . . . . . 106Process checks for Linux . . . . . . . . . 107Completing startup of Tivoli Netcool PerformanceManager - Wireless component . . . . . . . 108

Chapter 13. Enable CommonReporting on Tivoli NetcoolPerformance Manager . . . . . . . . 111Tivoli Netcool Performance Manager - ApplicationStudio . . . . . . . . . . . . . . . . 111

Appendix A. Installation output . . . . 113Installation output for patch . . . . . . . . 120

Appendix B. Log file errors . . . . . 123Creating OEM repository and console accessible bya specific port . . . . . . . . . . . . . 123

Appendix C. Dependency Checkererrors. . . . . . . . . . . . . . . 125

Notices . . . . . . . . . . . . . . 129Terms and conditions for product documentation 131Trademarks . . . . . . . . . . . . . . 132

Index . . . . . . . . . . . . . . . 133

iv IBM Tivoli Netcool Performance Manager: Installation Guide

Introduction

Explains how to install and configure Tivoli Netcool Performance Manager, 1.4.1.

Note: If you are upgrading Tivoli Netcool Performance Manager, see theUpgrading Tivoli Netcool Performance Manager - Wireless Component.

Important: Before you install Tivoli Netcool Performance Manager, you areadvised to read the Release Summary for Tivoli Netcool Performance Manager.Release summary contains information specific to your installation that is not apart of this guide. Failure to consult the release notes might result in a corrupted,incomplete, or failed installation.

Intended audienceRead this information if you want to install Tivoli Netcool Performance Manager,1.4.1- Wireless Component. This information is intended for:v Experienced system administratorsv Database administratorsv Product installers

Required skills and knowledge

Readers must be familiar with the following topics:v Hardware:

– IBM® PowerPC®

– Oracle– x86-64

v Operating System:

– AIX®

– Oracle Solaris

– Red Hat Enterprise Linux

– Microsoft Windowsv Database:

– Oracle databasev Other software

– Jazz™ for Service Management and its components

© Copyright IBM Corp. 2006, 2015 v

Required skills and knowledgeTo install Tivoli Netcool Performance Manager, you must be familiar with thefollowing technologies:v Hardware:

– Oracle Sun Microsystems– x86-64– IBM PowerPC

v Operating System:

– AIX

– Oracle Solaris

– Red Hat Enterprise Linux

– Microsoft Windowsv Database:

– Oracle

The Tivoli Netcool Performance Manager - Wireless component userpublications

Tivoli Netcool Performance Manager - Wireless component consists of thefollowing publications:

Table 1. Tivoli Netcool Performance Manager - Wireless component user documentation

Document Description

Release Summary for Tivoli Netcool PerformanceManager

Additional release-specific information not in theguides.

Installing Tivoli Netcool Performance Manager -Wireless Component

Instructions for installing and configuring theTivoli Netcool Performance Manager software.

Upgrading Tivoli Netcool Performance Manager -Wireless Component

Instructions for upgrading Tivoli NetcoolPerformance Manager software.

Administering Tivoli Netcool Performance Manager -Wireless Component

Instructions and general information about how tomaintain and support Tivoli Netcool PerformanceManager

Using Tivoli Netcool Performance Manager - WirelessComponent

Conceptual information and procedures for usingTivoli Netcool Performance Manager software forperformance, trending analysis and performancealarms.

Installing and Using Tivoli Netcool PerformanceManager - Application Studio - Wireless Component

Provides instructions for installation and usage ofthe Tivoli Netcool Performance Manager -Application Studio.

Tivoli Monitoring Integration - Wireless Component Provides instructions for integrating IBM TivoliMonitoring with Tivoli Netcool PerformanceManager.

Tivoli Netcool/OMNIbus Web GUI Integration -Wireless Component

Provides instructions for integrating IBM TivoliNetcool/OMNIbus Web GUI with Tivoli NetcoolPerformance Manager.

The documentation is available on the knowledge center at http://www-01.ibm.com/support/knowledgecenter/SSBNJ7/welcome.

vi IBM Tivoli Netcool Performance Manager: Installation Guide

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7/welcome

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7/welcome

Service Management ConnectConnect, learn, and share with Service Management professionals: product supporttechnical experts who provide their perspectives and expertise.

Access Network and Service Assurance community at https://www.ibm.com/developerworks/servicemanagement/nsa/index.html. Use Service ManagementConnect in the following ways:v Become involved with transparent development, an ongoing, open engagement

between other users and IBM developers of Tivoli products. You can access earlydesigns, sprint demonstrations, product roadmaps, and prerelease code.

v Connect one-on-one with the experts to collaborate and network about Tivoliand the Network and Service Assurance community.

v Read blogs to benefit from the expertise and experience of others.v Use wikis and forums to collaborate with the broader user community.Related information:

Tivoli Netcool Performance Manager 1.4 community on developerWorks

Tivoli Netcool Performance Manager technical trainingFor Tivoli Netcool Performance Manager technical training information, see thefollowing Tivoli Netcool Performance Manager Training website at:https://tnpmsupport.persistentsys.com/training.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineAccess the IBM Software Support site at http://www.ibm.com/software/support/probsub.html .

IBM Support AssistantThe IBM Support Assistant is a free local software serviceability workbenchthat helps you resolve questions and problems with IBM softwareproducts. The Support Assistant provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe Support Assistant software, go to http://www.ibm.com/software/support/isa.

Troubleshooting GuideFor more information about resolving problems, see the problemdetermination information for this product.

Conventions used in this publicationSeveral conventions are used in this publication for special terms, actions,commands, and paths that are dependent on your operating system.

Typeface conventionsThis publication uses the following typeface conventions:

Bold

Introduction vii

https://www.ibm.com/developerworks/servicemanagement/nsa/index.html

https://www.ibm.com/developerworks/servicemanagement/nsa/index.html

https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=d4b565fd-04e5-47c2-965a-943ccdfabdb9

https://tnpmsupport.persistentsys.com/training

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/isa

http://www.ibm.com/software/support/isa

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), labels (such as Tip:, and Operating system considerations:)

v Keywords and parameters in text

Italic

v Citations (examples: titles of publications, diskettes, and CDs)v Words defined in text (example: a nonswitched line is called a

point-to-point line)v Emphasis of words and letters (words as words example: "Use the word

that to introduce a restrictive clause."; letters as letters example: "TheLUN address must start with the letter L.")

v New terms in text (except in a definition list): a view is a frame in aworkspace that contains data.

v Variables and values you must provide: ... where myname represents....

Monospace

v Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Bold monospace

v Command names, and names of macros and utilities that you can typeas commands

v Environment variable names in textv Keywordsv Parameter names in text: API structure parameters, command

parameters and arguments, and configuration parametersv Process namesv Registry variable names in textv Script names

viii IBM Tivoli Netcool Performance Manager: Installation Guide

Chapter 1. Installation process

The preinstallation and installation roadmaps describe how to install Tivoli NetcoolPerformance Manager.

Before installation, ensure that you have all the hardware you need, and have theappropriate software ready to install.

Preinstallation roadmapBefore you install Tivoli Netcool Performance Manager, you must complete each ofthe steps in this preinstallation roadmap.

© Copyright IBM Corp. 2006, 2015 1

Installation roadmapTo install Tivoli Netcool Performance Manager, you must complete each of thetasks in the following installation roadmap.

2 IBM Tivoli Netcool Performance Manager: Installation Guide

Chapter 2. Planning your installation

You must install Tivoli Netcool Performance Manager on ahigh-performance and scalable platform.

Choose between the various installation options and ensure that you follow theinstructions that apply to your installation.

Tivoli Netcool Performance Manager distributionHow to get the product distribution.

The Tivoli Netcool Performance Manager distribution is available as an electronicimage. These instructions assume that you are installing from an electronic image.

If you install the product from an electronic image, be sure to keep a copy of thedistribution image in a well-known directory because you will need this image inthe future to make changes to the environment, including uninstalling TivoliNetcool Performance Manager.

The Tivoli Netcool Performance Manager distribution contains the softwarerequired to install Tivoli Netcool Performance Manager 1.4.1.

Components of Tivoli Netcool Performance ManagerDescribes the components that made up of a Tivoli Netcool Performance Managerinstallation.

A typical Tivoli Netcool Performance Manager installation consists of the followingcomponents:v Application server component - Runs a core application framework.v Gateway component - Processes data that is downloaded from the adapter data

sources.v Loader components - Parse and load data into a database.v Database component - Stores data in an Oracle database.v Directory server - Provides directory services by using Lightweight Directory

Access Protocol that is based on Security Directory Server.v Tivoli Common Reporting server- Provides the new Common Reporting GUI

that is accessed by using a browser. Tivoli Common Reporting is installed fromJazz for Service Management. To use Common Reporting, you must also installTivoli Netcool Performance Manager - Application Studio on a Windowscomputer. Tivoli Netcool Performance Manager - Application Studio is anadministrative and modeler tool for Common Reporting on Tivoli NetcoolPerformance Manager.

Note: You can use Model Maker if you have earlier Cognos models.


v Client software provides graphical user interface (GUI) access from clientcomputers.

Supported configurationsSupported system configurations for the installation of the Tivoli NetcoolPerformance Manager components.

Install Tivoli Netcool Performance Manager components in one of the two mainconfigurations as follows:v A stand-alone system, where you install all components on a single stand-alone

server.v A distributed system, where you can install components over several servers in

different combinations.

For example, you can install the database, application, gateway, and loadercomponents, plus the directory server, on one server, or install each component onseparate servers.

Servers can also be defined by using Solaris Containers. SolarisContainers is a virtualization technology in Solaris 10 that provides isolated andsecure runtime environments for applications. It uses zones, which are separateenvironments that can be viewed as individual OS instances that are running onthe same server. A container can be defined as a zone with resources (processor,memory) allocated by using the resource management features available in Solaris10. A distributed system can consist of components that are installed on separatezones that can span one or more Solaris 10 servers.

Installation on VMware ESX is also supported by using RHEL as theguest operating system. For more information about VMware, see:http://www.vmware.com/index.html

In this information, a server refers to the individual OS instance on which theTivoli Netcool Performance Manager - Wireless component software is installed.This can be a non-global Solaris 10 zone or an RHEL instance that is running onVMWare ESX. If the servers are defined as non-global Solaris 10 zones, perform allinstallation tasks on these zones rather than on the global zone, unless otherwisespecified.


http://www.vmware.com/index.html

Chapter 3. Preparing for the Installation

Ensure that you have the hardware and software required for a Tivoli NetcoolPerformance Manager installation.

Server hardware and software requirements

Ensure that you have the necessary server hardware and softwarerequirements.

Server hardware requirementsThe minimum hardware requirements for a Tivoli Netcool Performance Managerinstallation.

The minimum hardware requirements for a Tivoli Netcool Performance Managerserver are as follows:

v 4 x UltraSPARC IV, IV+

v 4 x x86-64 dual-core processors

v 4 x PowerPC Power5 processorsv 32 GB core memoryv 4 x 146 GB and 6 x 300 GB hard disksv Optical drive (DVD ROM/R/RW)

If you are deploying in a distributed environment, each server, or the virtualmachine requires the following configuration:v 1 x Intel Xeon 5500/5600 series processor (quad-core) 2.4 GHzv 4 GB RAMv 300 GB disk space

Server software requirementsThe minimum software requirements for a Tivoli Netcool Performance Managerinstallation.

To install a Tivoli Netcool Performance Manager system, you need the appropriatenumber of AIX, Solaris, or Linux servers, extra IBM, and third-party software foreach server. Depending on the server type, you need some or all of the followingextra software.


Prerequisite softwareThe prerequisite software for a Tivoli Netcool Performance Manager installation.

Product Version

Operating system 64-bit onlyv Red Hat Enterprise Linux

(RHEL) 5.9 and 6.x

v IBM AIX 6.1 or later

v Oracle Solaris 10 Update 8

v Oracle Enterprise Edition withpartitioning option

v Oracle Client

v Oracle Instant Client

v Oracle Instant Client SQL*PlusExtension package

v Oracle 32-bit libraries

v Oracle database Enterprise 11.2.0.4, 64-bit withpartitioning option.Note: Oracle 11.2.0.4 is a full installation.

v You must install The Oracle 32-bit librariesthat are contained in the Oracle 32-bit instantclient package.

Important: You must give vtdb as the databaseSID.

Jazz for Service Management 1.1.1.0

Tivoli Common Reporting 3.1.0.2

For more information about the availability ofthis version, see http://www-01.ibm.com/support/docview.wss?uid=swg24036990

JBoss Application Server 4.0.3 Service Pack 1

Perl 5.6.1 for Gateway servers on Solaris and RHEL

Bundled softwareThe software that is bundled with Tivoli Netcool Performance Manager.

Product Version

IBM Security Directory Server (required) 6.3.1

IBM DB2 (required) 9.7 Fix pack 6 (version 9.7.0.6)

IBM Tivoli Monitoring agent script(optional)

6.3

IBM Java 1.7.0 SR8 FP10 64-bit

Location of the Tivoli Netcool Performance Manager softwareNote the location of the Tivoli Netcool Performance Manager software before youstart the installation.

In addition to the Tivoli Netcool Performance Manager software, the followingIBM products are included.v IBM Security Directory Serverv Jazz for Service Managementv WebSphere Application Serverv Tivoli Common Reportingv IBM DB2v IBM Tivoli Monitoring


http://www-01.ibm.com/support/docview.wss?uid=swg24036990


You can install Tivoli Netcool Performance Manager either by using the productmedia, or by downloading it from the IBM Passport Advantage website:http://www.ibm.com/software/howtobuy/passportadvantage/

The following is a list of the core package files:v vallent-vt-ant-<version>.tar.gz

v vallent-vt-as-core-<version>.tar.gz

v vallent-vt-common-<version>.tar.gz

v vallent-vt-core-<version>.tar.gz

v vallent-vt-db-conf-<version>.tar.gz

v vallent-vt-db-install-<version>.tar.gz

v vallent-vt-ds-conf-<version>.tar.gz

v vallent-vt-java-libs-<version>.tar.gz

v vallent-vt-jre-<version>.tar.gz

v vallent-vt-njloader-<version>.tar.gz

v vallent-vt-sap-<version>.tar.gz

v vallent-vt-tcr-<version>.tar.gz

v vallent-vt-test-framework-<version>.tar.gz

v pmw_install

v default.rsp

v dependency_checker

v wireless_db_post_install.ksh

v vallent-vt-patch-P1410110-TNPM1.4.1.0.110.tar.gz

Location of Oracle Solaris software

For each server that runs on Oracle Solaris, a full installation (all components) ofSolaris 10 must be available on the server.

Note the location of the Solaris software before you start the installation.

To check whether a package is installed, run the following command:pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibC SUNWlibm SUNWlibms SUNWsprot

SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt SUNWcsl

Extra Solaris packages required for installing Oracle 11g:

The following packages (or later versions) are required for Oracle database 11gRelease 2 (11.2) for Oracle Solaris.SUNWarcSUNWbtoolSUNWheaSUNWlibCSUNWlibmSUNWlibmsSUNWsprotSUNWtooSUNWi1ofSUNWi1cs (ISO8859-1)SUNWi15cs (ISO8859-15)SUNWxwfntSUNWcsl

Chapter 3. Preparing for the Installation 7

http://www.ibm.com/software/howtobuy/passportadvantage/

Location of Red Hat Enterprise Linux software

For each server that runs on Red Hat Enterprise Linux (RHEL), you need a basicRHEL installation. In addition, depending on the server type, install all of thespecified extra RHEL packages.

To check whether a package is installed, run the following command:rpm -qa | grep <package_name>

The dependency_checker tool also reports any missing packages. See Chapter 6,“Running the Dependency Checker tool,” on page 39 for details of the tool.

Any additional required packages must be in the Server directory of the RHELinstallation media.

If any packages are missing, install them by running the following command asuser root:rpm -i <RPM package file>

All the extra packages that are listed in the following sections are x86_64 versionsunless otherwise stated.

You must have all the packages that are installed, regardless of whether they are 32bit or 64 bit.

For example, the libXp package has two packages that are listed, the i386 and thex86_64 version; you must install both.

The architecture is displayed in bold for each package listed.

Extra RHEL packages required for installing Oracle 11g:

Before you install Oracle 11g on an RHEL server, install each of the followingpackages (specified versions or higher) on the server.

RHEL 5.9binutils,2.17.50.0.6,0.el5,x86_64compat-db,4.1.25,9,x86_64compat-libstdc++-33,3.2.3,61,x86_64compat-libstdc++-33,3.2.3,61,i386compat-libstdc++-296,2.96,138,i386control-center,2.16.0,14.el5,x86_64elfutils-libelf-devel,0.125,0,x86_64gcc,4.1.2,0.el5,x86_64gcc-c++,4.1.2,0.el5,x86_64glibc,2.5,24,x86_64glibc,2.3.4,2,i686glibc-common,2.5,12,x86_64glibc-devel,2.5,12,x86_64glibc-devel,2.5,12,i386glibc-headers,2.5,12,x86_64libgcc,4.1.2,0.el5,x86_64libgcc,4.1.1,52.el5,i386libaio,0.3.106,0,x86_64libaio,0.3.106,0,i386libaio-devel,0.3.106,0,x86_64libaio-devel,0.3.106,0,i386libstdc++,3.4.3,9.EL4,x86_64


libstdc++-devel,3.4.3,22.1,x86_64libgomp,4.1.2,0.EL5,x86_64libXp,1.0.0,8.el5,i386libXp,1.0.0,8.el5,x86_64make,3.81,1.1,x86_64sysstat,7.0.2,0.el5,x86_64

RHEL 6.xbinutils,2.17.50.0.6,0.el5,x86_64compat-db,4.1.25,9,x86_64compat-libstdc++-33,3.2.3,69.el6,x86_64compat-libstdc++-33,3.2.3,69.el6,i686compat-libstdc++-296,2.96,144.el6,i686control-center,2.16.0,14.el5,x86_64elfutils-libelf-devel,0.125,0,x86_64gcc,4.1.2,0.el5,x86_64gcc-c++,4.1.2,0.el5,x86_64glibc,2.5,24,x86_64glibc,2.3.4,2,i686glibc-common,2.5,12,x86_64glibc-devel,2.12,1.47.el6,x86_64glibc-devel,2.12,1.47.el6,i686glibc-headers,2.5,12,x86_64libgcc,4.4.6,3.el6,x86_64libgcc,4.4.6,3.el6,i686libaio,0.3.106,0,x86_64libaio,0.3.106,0,i686libaio-devel,0.3.106,0,x86_64libaio-devel,0.3.106,0,i686libstdc++,3.4.3,9.EL4,x86_64libstdc++-devel,3.4.3,22.1,x86_64libgomp,4.1.2,0.EL5,x86_64libXp,1.0.0,15.1.el6,i686libXp,1.0.0,15.1.el6,x86_64make,3.81,1.1,x86_64sysstat,7.0.2,0.el5,x86_64

Extra RHEL packages required for installing IBM Security Directory Server andIBM DB2:

Before you install IBM Security Directory Server and IBM DB2 on an RHEL server,you must install each of the following packages (specified versions or higher) onthe server.

RHEL 5.9compat-libstdc++-296,2.96,138,i386compat-libstdc++-33,3.2.3,61,x86_64compat-libstdc++-33,3.2.3,61,i386compat-gcc-34,3.4.6,4,x86_64compat-gcc-34-c++,3.4.6,4,x86_64compat-libf2c-34,3.4.6,4,x86_64compat-libf2c-34,3.4.6,4,i386kernel-headers,2.6.18,53.el5,x86_64glibc-headers,2.5,18,x86_64glibc-devel,2.5,18,x86_64glibc-devel,2.5,18,i386libgomp,4.1.2,14.el5,x86_64

RHEL 6.xcompat-libstdc++-296,2.96,144.el6,i686libstdc++,4.4.6,3.el6,i686compat-libstdc++-33,3.2.3,69.el6,x86_64compat-libstdc++-33,3.2.3,69.el6,i686compat-gcc-34,3.4.6,4,x86_64compat-gcc-34-c++,3.4.6,4,x86_64compat-libf2c-34,3.4.6,19.el6,x86_64


compat-libf2c-34,3.4.6,19.el6,i686kernel-headers,2.6.18,53.el5,x86_64glibc-headers,2.5,18,x86_64glibc-devel,2.12,1.47.el6,x86_64glibc-devel,2.12,1.47.el6,i686libgomp,4.1.2,14.el5,x86_64

Extra RHEL packages required for installing Tivoli Common Reporting:

Before you install IBM Tivoli Common Reporting on an RHEL server, you mustinstall each of the following packages (specified versions or higher) on the server:

RHEL 5.9compat-libstdc++-33,3.2.3,61,x86_64compat-libstdc++-33,3.2.3,61,i386glibc,2.5,24,x86_64glibc,2.3.4,2,i686openmotif22,2.2.3,18,x86_64openmotif22,2.2.3,18,i386

RHEL 6.xcompat-libstdc++-33,3.2.3,69.el6,x86_64compat-libstdc++-33,3.2.3,69.el6,i686glibc,2.5,24,x86_64glibc,2.3.4,2,i686openmotif22,2.2.3,19.el6,x86_64openmotif22,2.2.3,19.el6,i686

Related information:

Jazz for Service Management Detailed System Requirements

Tivoli Common Reporting requirements

Extra RHEL packages required for installing JBoss Application Server:

Before you install JBoss Application Server on an RHEL server, install each of thefollowing packages (specified versions or higher) on the server.

RHEL 5.9eclipse-ecj,3.2.1,18.el5,x86_64zlib-devel,1.2.3,3,x86_64libgcj-devel,4.1.2,14.el5,x86_64gcc-java,4.1.2,14.el5,x86_64java-1.4.2-gcj-compat-devel,1.4.2.0,40jpp.112,x86_64

RHEL 6.xecj,3.4.2,6.el6,x86_64zlib-devel,1.2.3,3,x86_64libgcj-devel,4.1.2,14.el5,x86_64gcc-java,4.1.2,14.el5,x86_64java-1.5.0-gcj-devel,1.5.0.0,29.1.el6,x86_64

Location of AIX software

For each server that runs on AIX, a full installation (all components) of AIX 6.1 orgreater, must be available on the server. Ensure that you have the required AIXsoftware before you start with the installation.



http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/tcr_c_install_prereqs.html

Extra AIX packages required for installing Oracle 11g:

Before you install Oracle 11g on an AIX server, install each of the followingpackages (specified versions or higher) on the server.bos.adt.basebos.adt.libbos.adt.libmbos.perf.libperfstatbos.perf.perfstatbos.perf.proctoolsxlC.aix61.rte:9.0.0.1 or later (AIX 6.1)xlC.rte:9.0.0.1 or later (AIX 6.1)

Extra AIX packages required for installing Security Directory Server and IBMDB2:

Before you install Security Directory Server and IBM DB2 on an AIX server, installeach of the following packages (specified versions or higher) on the server.rsct.basic.rtersct.opt.storagerm

Location of Oracle RDBMS and Oracle Client softwareNote the location of the Oracle RDBMS and Client software before you start theinstallation.

Location of JBoss Application Server softwareDescribes the location of the JBoss Application Server software.

Note the location of the JBoss Application Server software before starting theinstallation. Ensure that the JBoss archive is in the /appl directory and is in .zip,.tar.gz or .tar.bz2 format.

Installation scripts automatically install JBoss during the Tivoli NetcoolPerformance Manager software installation.

If necessary, download the JBoss Application Server software from the followinglocation:http://www.jboss.org/jbossas/downloads/

Note: The version that is required is 4.0.3 Service Pack 1. For example:jboss-4.0.3SP1.tar.gz.

Location of Perl softwareThe following section describes the location of the Perl software.

Note: The location of the Perl software before you start the installation.

If necessary, download the required Perl software source code fromhttp://www.perl.com/CPAN/src.


http://www.jboss.org/jbossas/downloads/

http://www.perl.com/CPAN/src

Client computer hardware and software requirements on MicrosoftWindows

Ensure that the client computer has the necessary hardwareand software requirements.

Client hardware requirementsThe minimum hardware requirements for a Tivoli Netcool Performance Managerclient installation.

The minimum client hardware requirements for a Tivoli Netcool PerformanceManager client are as follows:v 1.4 GHz Pentium III (or above) processorv 4 GB memory

Client software requirementsThe minimum software requirements for a Tivoli Netcool Performance Managerclient installation.

Table 2 lists the software products that you need on a client computer to access theTivoli Netcool Performance Manager system. The required software must beinstalled on the client computer before you start the installation.

Table 2. Client software requirements

Product Version

Operating system Windows 7

Web browser v Internet Explorer 9, 10, and 11

v Mozilla Firefox ESR 17, 24, 31

Java Runtime Environment (JRE) JRE 1.7 Update 51 or above

Flash Player Adobe Flash Player 10.0.22 or later

Downloading the Java Runtime Environment Software

Download the Java Runtime Environment from http://www.oracle.com/technetwork/java/index.html.


http://www.oracle.com/technetwork/java/index.html


Chapter 4. Preinstallation tasks

You must prepare and configure each server individually.

Prerequisites

Prerequisites before you start the installation.

Before you start the installation, ensure that you have installed the appropriateoperating system on each of the servers. Also, depending on the components thatyou want to install on a particular server, ensure that you install any additionaloperating system packages required.

Required server informationImportant server information for installation.

Before you start the installation, you need the following information for each of theservers in your configuration.v Server IP addressv Server hostnamev Server domain namev Router IP address

Required file systems

Ensure that you set up the required file systems for the TivoliNetcool Performance Manager installation.

Using Table 3 on page 14 as a guide, create the required file systems on eachserver. Ensure that the file system sizes meet your specific requirements; theminimum file system sizes in this table are only sufficient for a base applicationsetup. Refer to the sizing document provided for your system for accurate sizings.All external file systems must reside on storage area networks (SAN) file systemonly.


Note: In a default installation, the Oracle database is configured in NOARCHIVELOGmode and archived redo log files are not created. Online redo log files are placedin both the /oralogs1/vtdb and /oralogs2/vtdb directories. You must keeparchived Oracle redo log files and online redo log files on separate devices/LUNs. Ifyou want to use ARCHIVELOG mode, update the Oracle database configurationparameter log_archive_dest to point to a directory on a separate device/LUN thanthe online redo log files, such as the /oradump mount point.

Note: If you are installing the database server on a Solaris non-global zone,configure the zone with access to the raw disk devices to implement RAID 1+0 forthe Oracle DB file systems.

Table 3. Required file systems

File system Description

Minimum

Size Partition Type Server Type

/ OperatingSystem

8 GB System diskpartition or LVMdevice

All

swap OperatingSystem


All

/var OperatingSystem


All

/appl Oracle andTivoli NetcoolPerformanceManagerapplicationsoftware

24 GB Non-system diskpartition or LVMdevice

All

/export/home Users HomeAccounts


All

/oradata01 Oracle databasefiles StorageLocation 1


Database



Database



Database



Database

/oralogs1 Oracle Redo Loglocation 1


Database

/oralogs2 Oracle Redo Loglocation 2


Database


Table 3. Required file systems (continued)

File system Description

Minimum

Size Partition Type Server Type

/oratemp OracleTemporary tablespace storagelocation


Database

/oradump Oracle memorydump Locationfor archive logsand for databasebackups


Database

/data/trace_log1

Trace LogLocation forapplication logs


Application,Loader

/data/trace_archive1

Trace ArchiveLocation forarchivedapplication logs


Application,Loader

Note: IBM recommends RAID 1+0 (implemented in hardware if possible) for thenon-system file systems. RAID 10 is the supported RAID configuration for allOracle file systems such as /oradata*, /oralogs*, and /oradump.

Ports and firewall configurations

You must configure a number of ports and firewalls for a TivoliNetcool Performance Manager system.

Table 4. Ports needed for Tivoli Netcool Performance Manager

Port Description

LDAPPORT=1389 LDAP authentication interface

ORACLEPORT=1521 Oracle database port

SAPMONPORT=9009 Port for Service Application Processor (SAP)

OMPORT=9008 Framework RMI communication

ASHTTPPORT=8080 Application server HTTP port

ASREDIRPORT=8443 Application server Redirect port

ASAJPPORT=8086 Apache Integration

ASWEBSRVPORT=8083 Application server Web port

ASBRIDGEPORT=10091 Application server Bridge port

ASNSPORT=1099 JNDI Communications

ASJRMPINVOKPORT=4444 EJB Communications

ASPOOLINVOKPORT=4445 EJB Communications

ASRMIPORT=1098 EJB Communications

ASUIL2PORT=8093 JMS Communications

ASHSQLPORT=1701 Internal DB

Chapter 4. Preinstallation tasks 15

Table 4. Ports needed for Tivoli Netcool Performance Manager (continued)

Port Description

ORBPORT=3528 CORBA Alarm notification

ORBSSLPORT=3529 Secure CORBA alarm notification

SMTP_PORT=25 Mail relay port

MSTRCACHE_RMI=9876 Java Remote Method Invocation port forMaster Cache

ALRMCACHE_RMI=9877 Java Remote Method Invocation port forAlarm Cache

4000 -> 4010 SNMP Gateway Admin port range (Port4444 must be open to enable the use of theAlarm tools.)

IBM DB2 port=50000 Default port for IBM DB2

Dashboard Application Services Hubport=16310 and 16311

Default ports for Dashboard ApplicationServices Hub

All ports that are listed are required for communication between the applicationcomponents. If these components are distributed between different servers, thenthe servers must be able to connect via these ports through any firewall.

The ports that are identified by ASHTTPPORT, ASJRMPINVOKPORT and ORACLEPORT arerequired for communication between the client workstations and the server. Allowthese ports through any firewalls present between the client and the servers.

Distributed installations with Application, Loader, or DirectoryServers on RHEL

When you deploy the Application, Directory or Loader servers on RHEL as part ofa distributed installation, configure the firewall on each RHEL server to allowcommunication to and from each of the other servers, regardless of the operatingsystem.

About this task

To allow distributed installations with Application, Loader or Directory Servers onRHEL, configure the IPTables service on the RHEL system by using the IPaddresses of the other servers as follows:

Procedure1. Determine if the firewall is enabled.

# service iptables status

Note: If the firewall is not enabled, you do not need to complete the followinginstructions. Ignore the remainder of this section.

2. Allow a server through the RHEL firewall by editing the /etc/sysconfig/iptables file as user root and specifying the server IP address. For each server,place an entry similar to the following after the first -A RH-Firewall entry inthe file:A RH-Firewall-1-INPUT -p all -s <IP address> -j ACCEPT


This entry allows access from the specified server through the firewall on allports.

3. Ensure that you add the following ports to allow clients to access theapplication server and alarms component. Enter each entry on a single line.-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp -dport<ASHTTPPORT> -j ACCEPT-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp -dport<ASJRMPINVOKPORT> -j ACCEPT-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp -dport<ORACLEPORT> -j ACCEPT

4. Substitute the correct port numbers for <ASHTTPPORT>, <ASJRMPINVOKPORT>, and<ORACLEPORT>. Here is an example of how the /etc/sysconfig/iptables filelooks afterward:*filter:INPUT ACCEPT [0:0]:FORWARD ACCEPT [0:0]:OUTPUT ACCEPT [0:0]:RH-Firewall-1-INPUT - [0:0]-A INPUT -j RH-Firewall-1-INPUT-A FORWARD -j RH-Firewall-1-INPUT-A RH-Firewall-1-INPUT -i lo -j ACCEPT-A RH-Firewall-1-INPUT -p all -s <IP address> -j ACCEPT-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 8080 -j ACCEPT-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 4444 -j ACCEPT-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 1521 -j ACCEPT-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibitedCOMMIT

5. Run the command as user root:# service iptables restart

Installing the platform package

Install the platform package provided with your softwaredistribution. The platform package provides some system administration functionsand installation scripts to help you correctly install the Oracle database and thedirectory server.

About this task

The name of the package is ibm-tn-plat-install-PLAT<version>.tar.gz. Installthis package on all Tivoli Netcool Performance Manager servers even in thedistributed environment. The package consists of the following files:v ibm-tn-plat-install.install

v ibm-tn-plat-install.remove

v ibm-tn-plat-install.sw

v ibm-tn-plat-install.license

To install the platform package, complete the following steps as user root:

Note: If the installation is using Solaris containers, the platformpackage must be installed on the global zone as well as the non-global zones.


Procedure1. Place the platform package in the /appl directory or the directory where Tivoli

Netcool Performance Manager is to be installed.2. Enter the following command to extract the package:

# gzip -dc ibm-tn-plat-install-PLAT<version>.tar.gz | tar xf -

3. Run the installation script.# ./ibm-tn-plat-install.install now

The platform package is installed under the /var/install directory.

Creating user and group accounts

Describes how to create user and group accounts.

Before you begin

Ensure that no Tivoli Netcool Performance Manager users, such as oracle orvirtuo, are logged in while you run the following commands.

About this task

To create the required users and groups, complete the following on all servers:

Procedure1. On the server on which you want to install the Security Directory Server

software, run the following command as user root:# /var/install/sbin/setup_users -product virtuo -sds

2. On all other servers, run the following command as user root:# /var/install/sbin/setup_users -product virtuo

3. At the prompts, create a password for each new user created.

Important: You need the password for the idsinst user when you install IBMSecurity Directory Server and IBM DB2 (see Chapter 8, “Installing the SecurityDirectory Server and IBM DB2,” on page 51).

Setting directory ownership

Describes how to set directory ownership.

About this task

Perform the following task to set the owner of the Oracle database directories tooracle:


Procedure

Run the following command as user root on the database server:# chown oracle:dba /ora*

Configuring the kernel

Describes how to configure the kernel.

About this task

Correctly configure the OS kernel so that you can install Oracle and the SecurityDirectory Server.

Procedure1. To configure the kernel, run the following command as user root on the

database and application servers:# /var/install/sbin/system_configure

On Solaris, the system_configure command must be run on the global zone.2. Reboot the server by using the appropriate commands:

# /usr/sbin/shutdown -i6 -g0 -y

This updates the /etc/system file and backs up the original file as/etc/system.backup.IBM.<datestamp>

# shutdown -r now

This updates the /etc/sysctl.conf file and backs up the original file as/etc/original_sysctl.conf.

# shutdown -Fr

Setting up the domain name

Describes how to set up the domain name.

About this task

You must set up each of the servers on a common domain, typically, a DNSdomain. If you do not set up the DNS domain name, you might not be able toview the Alarm UI from the Tivoli Netcool Performance Manager Wireless webclient after the installation is complete. For more information about this issue, seehttp://www-01.ibm.com/support/docview.wss?uid=swg21613283.

To set up the servers on a common domain, follow these steps:



Procedure1. Run the following command as user root:

# grep domain /etc/resolv.conf

If a DNS domain is configured, you see output like as follows:domain this.domain.com

If a DNS domain is not being used, set up the domain name by completing asfollows:a. As user root on the servers, check to see if the domain name is set by

running the following command:# domainname

If nothing is returned, the domain is not set.b. To set the domain, run the following command:

# domainname <domain>

<domain> is the selected domain name for the system, for example, ibm.com.2. Do one of the following based on your system:

v On Solaris systems, edit the /etc/hosts file and change the<hostname>.domainname entry to the local host name appended with thedomainname. The entry in /etc/hosts must be as follows:<IP address> <hostname>.<domainname> <hostname> loghost

v On systems with Linux application servers that are usingDNS, edit the /etc/hosts file:a. If the entry for localhost in /etc/hosts as follows:

127.0.0.1 <hostname>.<domainname> <hostname>localhost.localdomain localhost

Change the localhost entry so that it looks as follows:127.0.0.1 localhost.localdomain localhost

b. If the system is not using DNS, add the following line to /etc/hosts file.<IP address> <hostname>.<domainname> <hostname>

v On Solaris systems, add the domain name to the/etc/defaultdomain file:<domainname>

v On AIX systems, the entry in /etc/hosts must be:<IP address> <hostname> <hostname>.<domainname>

If the entry does not conform to this format, edit the file.


Setting up the host name

Describes how to set up the host name.

About this task

You must set up the host name. If you are installing a distributed system and arenot using DNS, ensure that the host name of each server is present in the/etc/hosts file of each server.

Procedure1. Modify the /etc/hosts file as user root on each server.2. Ensure the host name and IP addresses of the application server, database

server, and loader servers and, if separate, the directory server is present in the/etc/hosts file.

Note: The host name must not contain an underscore (_), when it is set up ona Linux system. It results in installation failure. There is a limitation on parsingthe host name that contains underscore on Linux systems.

Building Perl on Gateway servers

Perl installation information.

By default, Perl has threading enabled in a Solaris or Linux distribution. However,for correct functioning of the Gateways, reinstall Perl without threading enabledand without 64int. For guidance on correctly installing Perl without 64int, refer tothe Gateway Framework Distribution Note in your distribution.

Install Perl in the $WMCROOT/gways/ directory of the server on which you areinstalling the gateway components. For the instructions on the Perl build, see:




Setting memory for Java client processes

Describes how to increase the memory available to Java clientprocesses.





If a Java client process requires an extensive use of memory and the default Javaheap size is insufficient, then the process can fail with an OutOfMemoryError Javaexception:java.lang.OutOfMemoryError: Java heap space

This error can occur in the following scenarios:v When you install or upgrading large technology packs.v When you run the secondary key removal tool sbh_sk_remover to remove

secondary key fields before the provisioning of SBH definitions.

This problem is resolved by increasing the memory available to Java clientprocesses. Available memory is increased by amending the ANT_OPTS variable.

Important: If you are installing large technology packs, it is recommended thatyou set the ANT_OPTS variable to a value of 1 G before installation. Do not allow theinstallation to fail before you increase the ANT_OPTS value.

For information about increasing the memory available to Java client processes, seeJava client processes topic of the Administering Tivoli Netcool Performance Manager- Wireless Component


Chapter 5. Installing Jazz for Service Management

The Jazz for Service Management installation supports different installationscenarios, user types, installation modes, and server topologies depending on yourorganization needs and target server environments. You can use either a launchpador IBM Installation Manager to install and configure Jazz for Service Management.You can install and configure one or more integration services on a one, two, orthree servers. You can optionally install IBM DB2® and IBM WebSphere®

Application Server.

About this task

To plan the Jazz™ for Service Management installation, you must choose yourinstallation scenario. This choice is dependent on different factors, for example,number of integration services to install, by using existing database andapplication server middleware, installation mode, or user type.

These factors determine your installation scenario that you use to install Jazz forService Management. You can also use the decision maps. See Installation decisionmaps.

Important: Do not install Jazz for Service Management 1.1.1.0 on a Solaris machinein a distributed or a stand-alone environment.Related information:

Installing Jazz for Service Management

Common directory locations for Jazz for Service ManagementJazz for Service Management topics use path name variables for paths to commondirectories, for example, home directories.

Jazz for Service Management home directory

The JazzSM_HOME variable describes the location where Jazz for ServiceManagement is installed. This location can be specified during installation. If notspecified, the following default locations are used:

v Root user installations: /opt/IBM/JazzSMv Non-root user installations: <user_home_dorectory>IBM/JazzSM

Jazz for Service Management profile directory

The JazzSM_WAS_Profile variable describes the location of the application serverprofile that is used for Jazz for Service Management. This location is in the/profile/ subdirectory of the Jazz for Service Management home directory.

v Root user installations: /opt/IBM/JazzSM/profilev Non-root user installations: <user_home_dorectory>IBM/JazzSM/profile


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_c_install_plan_maps.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_c_install_plan_maps.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_c_install.html

Jazz for Service Management profile name

The JazzSM_Profile_Name variable refers to the name assigned to the WebSphereApplication Server profile for Jazz for Service Management. The default name isJazzSMProfile.

Installation images home directory

The Install_Imgs_Home variable describes the common root directory that containsthe extracted contents of the installation images depending on the installationscenario.

Full installationIBM DB2, IBM WebSphere Application Server, and IBM Tivoli® CommonReporting if you want to install Tivoli Common Reporting during the fullinstallation flow.

Attention: You must extract the contents of the installation media for thissoftware to the same common root directory, otherwise the full installationdisplays error messages for missing software.

Custom installationIBM WebSphere Application Server, if you do not want to use an existinginstallation; Tivoli Common Reporting if you want to install it after acustom installation of the other integration services.

Note: It is not necessary to extract the contents of the installation mediafor this software to the same common root directory, but it is preferable tomaintain all extracted installation media in a central location.

Jazz for Service Management installation images home directory

The JazzSM_Image_Home variable describes the common root directory in which theJazz for Service Management is extracted. It contains the launchpad, IBMInstallation Manager, IBM Prerequisite Scanner, the Installation Manager repositorywith the software packages for the integration services except Tivoli CommonReporting.

Tip: Ensure that the path to the JazzSM_Image_Home directory does not contain anyspaces or special characters, otherwise the launchpad does not start.

IBM DB2 home

The DB2_HOME variable describes the location where IBM DB2 is installed. Thislocation was specified during installation. If not specified, the following defaultlocations are used:

v Root user installations: /opt/ibm/db2v Non-root user installations: $HOME/sqllib

$HOME represents the non-root user's home directory.


WebSphere Application Server home directory

The WAS_HOME variable describes the location where WebSphere Application Serveris installed. This location was specified during installation. If not specified, thefollowing default locations are used:

v Root user installations: /opt/IBM/WebSphere/AppServerv Non-root user installations: <user_home_dorectory>IBM/WebSphere/AppServer

Administration Services home directory

The ADMIN_HOME variable describes the location where Administration Servicesis installed. This location can be specified during installation. If not specified, the

following default locations are used:v Root user installations: /opt/IBM/JazzSM/adminv Non-root user installations: /home/nonrootuser_name/IBM/JazzSM/admin

Administration Services UI home directory

The ADMINUI_HOME variable describes the location where Administration Services UIis installed. This location can be specified during installation. If not specified, the

following default locations are used:v Root user installations: /opt/IBM/JazzSM/adminuiv Non-root user installations: /home/nonrootuser_name/IBM/JazzSM/adminui

Registry Services home directory

The REGISTRY_HOME variable describes the location where Registry Services isinstalled. This location can be specified during installation. If not specified, the

following default locations are used:v Root user installations: /opt/IBM/JazzSM/registryv Non-root user installations: /home/nonrootuser_name/IBM/JazzSM/registry

Security Services home directory

The SECURITY_HOME variable describes the location where Security Services isinstalled. This location can be specified during installation. If not specified, the

following default locations are used:v Root user installations: /opt/IBM/JazzSM/securityv Non-root user installations: /home/nonrootuser_name/IBM/JazzSM/security

Dashboard Application Services Hub home directory

The DASH_HOME variable describes the location where Dashboard ApplicationServices Hub is installed. This location can be specified during installation. If notspecified, the following default locations are used:

v Root user installations: /opt/IBM/JazzSM/uiv Non-root user installations: <user_home_dorectory>IBM/JazzSM/ui

Chapter 5. Installing Jazz for Service Management 25

Dashboard Application Services Hub profile directory

The DASH_Profile variable describes the location of the application server profilethat is used for Dashboard Application Services Hub. This location is inthe/profiles/ subdirectory of the Jazz for Service Management home directory.

v Root user installations: /opt/IBM/JazzSM/profilev Non-root user installations: <user_home_dorectory>IBM/JazzSM/profile

Tivoli Common Reporting home directory

The REPORTING_HOME directory that contains the uninstallation program, theinstallation log files, and Tivoli Common Reporting component files. If notspecified, the following default locations are used:

v Root user installations: /opt/IBM/JazzSM/reportingv Non-root user installations: <user_home_dorectory>IBM/JazzSM/reporting

IBM Cognos® installation directory

The c10_location directory that contains the Cognos® installation. If not specified,

the following default locations are used:v Root user installations: /opt/IBM/JazzSM/reporting/cognosv Non-root user installations: /home/nonrootuser_name/IBM/JazzSM/reporting/

cognos

Full installation log directory

The Simple_install_log_dir directory into which general and offering specific logsare created during full installation:

v On UNIX systems: $HOME/jazzsm_launchpad/logs/

IBM Prerequisite Scanner installation directory

The ips_root directory that contains the contents of the extracted PrerequisiteScanner platform package. If not specified, the default locations are used:

v On UNIX systems: Install_Imgs_Home/PrereqScanner/UNIX_LinuxRelated information:

Common directory locations


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/ref/psc_r_pathnames.html

Preparing your environment for a full installation of Jazz for ServiceManagement

Perform tasks to ensure that your environment is ready for the full installation ofJazz for Service Management, such as checking prerequisites.

Before you begin

Before you install Jazz for Service Management, refer to the technical notes for Jazzfor Service Management. The technical notes provide information aboutlate-breaking issues, limitations, and workarounds.v Tech notes documenting issues in Jazz for Service Management Version 1.1.1.0v Tech notes documenting issues in Jazz for Service Management Version 1.1.0.3v Tech notes documenting issues in Jazz for Service Management Version 1.1.0.2

Procedure1. Ensure that your target environment meets the hardware and software

requirements for Jazz for Service Management and its integration services. SeeHardware and software requirements.

2. Set up a local file system. See Setting up a local file system for a fullinstallation.

3. If you want to use an alternative temporary directory while installing theintegrations services, see Specifying an alternative temporary directory forinstallation.

4. If you do not intend to install Jazz for Service Management to the defaultinstallation directory or use the default temporary directory, you must modifythe Prerequisite Scanner configuration files to check whether these non-defaultdirectories have the required available disk space. See Editing defaultconfiguration files for non-default installation locations.

5. Select the installation path as needed. See “Overview of Jazz for ServiceManagement installation” on page 28.


Jazz for Service Management on IBM Knowledge Center

IBM DB2 on IBM Knowledge Center

IBM Installation Manager on IBM Knowledge Center

IBM WebSphere Application Server on IBM Knowledge Center

Location of Jazz for Service Management softwareDescribes the location of the Jazz for Service Management 1.1.1.0 software. Jazz forService Management has a number of integration services: Administration,Registry, IBM Tivoli Common Reporting, Security, and IBM Dashboard ApplicationServices Hub.

Jazz for Service Management includes installation media for Jazz for ServiceManagement, IBM DB2, IBM WebSphere Application Server, and the Quick StartGuide. Download the Jazz for Service Management from the IBM PassportAdvantage website: http://www.ibm.com/software/howtobuy/passportadvantage/


http://www.ibm.com/support/search.wss?q=jazzsm1110relnotes



http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_c_install_prereqs.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_t_install_typical_local_sys.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_t_install_typical_local_sys.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_c_install_alt_dir.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_c_install_alt_dir.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/ips_edit_jazzsm_cfg_files.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/ips_edit_jazzsm_cfg_files.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/psc_ic-homepage.html

http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.kc.doc/welcome.html

http://www-01.ibm.com/support/knowledgecenter/SSDV2W_1.6.0/com.ibm.cic.agent.ui.doc/helpindex_imic.html?cp=SSDV2W_1.6.0%2F0&lang=en

http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/as_ditamaps/was855_welcome_ndmp.html




Download Jazz for Service Management Version 1.1.0.3

Jazz for Service Management Version 1.1.1.0 readme file

Overview of Jazz for Service Management installationJazz for Service Management Version 1.1.1.0 can be installed or updated, when youinstall it along with earlier Jazz for Service Management versions. For example,1.1.0.3.

Before you begin

Attention: Ensure that the package that you have downloaded is the latestrefresh of Jazz for Service Management Version 1.1.1.0.1. Run the prerequisite scanner. See

Running Prerequisite Scanner by using convenience scriptsRunning Prerequisite Scanner manually

2. Before you update Jazz for Service Management, see the late-breaking issues,limitations, and workarounds from here:http://www-01.ibm.com/support/search.wss?q=jazzsm1110relnotes

3. If you intend to update your existing Tivoli Common Reporting environment toVersion 3.1.0.2, ensure that you back up your jazzSM_Home/reporting/cognosdirectory before you begin the update.

Note: 4 GB of free disk space is required for an upgrade installation.

About this task

Typically, there are two scenarios for installing Jazz for Service Management:v If you have an earlier version of Jazz for Service Management on your system.

Then, upgrade to V1.1.1.0. See “Performing an upgrade installation.”v If you must install Jazz for Service Management from scratch. Then, install an

older version of Jazz for Service Management and upgrade to V1.1.1.0. See“Performing a fresh installation” on page 30.

Performing an upgrade installationUse IBM Installation Manager in GUI or silent modes to first update the Jazz forService Management extension for IBM WebSphere. Use this installation procedureif you already have an earlier version of Jazz for Service Management on yoursystem. For example, 1.1.0.3.

About this task

Install Version 1.1.1.0 for the following installed integration services:v Administration Servicesv Administrative Services UIv IBM Dashboard Application Services Hubv Registry Servicesv Security Services




http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_t_install_prs_prereqs.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_t_install_run_prs_cli.html

http://www-01.ibm.com/support/search.wss?q=jazzsm1110relnotes

Note: Jazz for Service Management Version 1.1.1.0 contains Tivoli CommonReporting Version 3.1.0.2, which is the latest available fix pack for Tivoli CommonReporting. Use the Tivoli Common Reporting update program to update yourexisting Tivoli Common Reporting environment.

You must update the installed integration services in the same application serverprofile to the same fix pack level.

Procedure1. Download and extract 1.1.1-TIV-JazzSM-multi.zip file to a local directory

from Fix Central page.For example, 1.1.1-TIV-JazzSM-multi

2. In a command window, open the /<user_home_directory>/IBM/InstallationManager/eclipse directory and run the following command:./IBMIM

3. Set up the fix pack repository preference.a. Select File > Preferences.b. In the Preferences > Repositories pane, click Add Repository.c. Click Browse and browse to the following location of the file:

JazzSM_111_Home/1.1.1-TIV-JazzSM-multi/JazzSMFPRepository/disk1/diskTag.inf

d. Click Apply.e. Click OK to close the Repositories pane.

4. On the Installation Manager home page, click Update. The Update Packageswindow opens.

5. Select Update all check box and click Next.The Licenses pane opens.

6. Review the license agreement for the software packages, and accept the terms,and click Next. The Features pane opens.

7. In the Common Configurations tab, enter password for smadmin user.8. Click Validate.9. After the validation completes successfully, click Next.

10. In the Registry Services 1.1.1.0 tab, enter password for smadmin user.11. Click Validate.12. After the validation completes successfully, click Next.13. In the Summary pane, review the software packages that you want to install

and click Update. After Installation Manager updates the fix pack, it displaysa message.

14. Click Finish.Related information:

Applying fix packs

Jazz for Service Management Version 1.1.1.0 Readme


http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=all

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_t_update_fp_oview_fp3.html


Performing a fresh installationAssuming that you do not have earlier version of Jazz for Service Management onyour system, install Jazz for Service Management 1.1.0.3 first, and then apply thefix pack 1.1.1.0.

About this task

Install Version 1.1.1.0 for the following installed integration services:v Administration Servicesv Administrative Services UIv IBM Dashboard Application Services Hubv Registry Servicesv Security Services

Note: Jazz for Service Management Version 1.1.1.0 contains Tivoli CommonReporting Version 3.1.0.2, which is the latest available fix pack for Tivoli CommonReporting. Use the Tivoli Common Reporting update program to update yourexisting Tivoli Common Reporting environment.

You must update the installed integration services in the same application serverprofile to the same fix pack level.

Procedure1. Download and extract Jazz for Service Management 1.1.0.3 from Fix central

page. For example, JazzSM_Image_Home2. Download and extract 1.1.1-TIV-JazzSM-multi.zip file to a different local

directory from Fix Central page.For example, 1.1.1-TIV-JazzSM-multi

Note: Note: 6 GB of free disk space is needed for a fresh installation.3. Start the launchpad by using the following command:

<JazzSM_Image_Home>/launchpad.sh.

Restriction: Ensure that the path to the JazzSM_Image_Home/ directory doesnot contain any spaces or special characters, otherwise the launchpad does notstart.

Important:

v It is recommended that you have only one instance of the launchpad openat a time.

v If DB2, Tivoli Common Reporting, or WebSphere Application Serverrepository is available on a shared network drive, ensure that you run thelaunchpad from the local file system to access the repository on the shareddrive, and install Jazz for Service Management.

4. Click Full. The Full Installation window opens.5. Review the instructions in the Full Installation window, and click Next. The

Full Installation > Software License Agreement window opens.

Important: If your environment already contains DB2, WebSphere ApplicationServer, or any of the Jazz for Service Management services that are installed,you cannot proceed with Full Installation. To proceed with Full Installation,you must uninstall them or you must use Custom workflow instead.


http://www-933.ibm.com/support/fixcentral/swg/selectFixes?product=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=fixId&fixids=1.1.0-TIV-JazzSM-multi-FP003&includeSupersedes=0

http://www-933.ibm.com/support/fixcentral/swg/selectFixes?product=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=fixId&fixids=1.1.0-TIV-JazzSM-multi-FP003&includeSupersedes=0

http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=all

6. Review the license agreements and accept the terms, and click Next. The FullInstallation > Installation Images Location window opens.

7. If you do not want to install Tivoli Common Reporting in the same flow, clearthe Install Tivoli Common Reporting check box. In the Installation imageshome field, specify the installation images root directory Install_Imgs_Home/,into which you copied and extracted all installation images. Click Next. TheFull Installation > Prerequisite Scan window opens.

8. Click Scan to run Prerequisite Scanner and scan your environment for the Jazzfor Service Management requirements. The launchpad runs the conveniencescript for a full installation and displays the overall result in the PrerequisiteScan window. To view the details, click Detailed Scan Results. The results canbe as follows:

Fail

If the target environment does not meet any of the prerequisite checks,Prerequisite Scanner returns an overall FAIL result for theenvironment. The tool displays the scan results for the individualprerequisite properties in the command window.

If Prerequisite Scanner returns this result, take the appropriate actions;for example, install the missing operating system packages, increasedisk space for the file systems, or modify the configuration settings ofthe target environment to match the expected values in the scanresults.

CAUTION:You can continue with the full installation without takingappropriate action, but it might fail or install with issues.

Pass

If the target environment meets all prerequisite checks, PrerequisiteScanner returns an overall PASS result for the environment.

If Prerequisite Scanner returns this result, you can install Jazz forService Management.

9. Click Next. The Full Installation > Basic Settings window opens.10. Verify, use, or enter the default values as needed:

Option Description

User name The administration user ID for the database,application servers, and Jazz for ServiceManagement integration services. Thedefault value is smadmin.Restriction: On Linux systems only: Thelength of the user ID must be a maximum of8 characters; otherwise, the installationprogram cannot create the DB2 instance.

Password and Confirm password The password that is associated with anyusers created by the full installation. Thepassword must have a minimum of 8alphanumeric characters and must notcontain special characters or space.


Option Description

Local host name The fully qualified name or IP address of thelocal server on which you install thesoftware. The default value is the fullyqualified host name that the launchpadretrieves from the local server. If it is not avalid value, you can change the value.

WebSphere Home The installation location for IBM WebSphereApplication Server (WAS_HOME). Thedefault location if not specified is/opt/IBM/WebSphere/AppServer on Linuxand AIX systems.

DB2 Home The installation location for IBM DB2(DB2_HOME). The default location if notspecified is /opt/ibm/db2 on Linux and AIXsystems.

Jazz for Service Management Home The installation location for Jazz for ServiceManagement (JazzSM_HOME). The defaultlocation if not specified is /opt/IBM/JazzSMon Linux and AIX systems.

11. Click Next. The Full Installation > Installation Summary window opens.12. Click Install. After the installation is complete, the launchpad displays the

overall result of the installation in the Full Installation > Installation Resultswindow.

13. Apply the Fix Pack 1.1.1.0 by using the steps from “Performing an upgradeinstallation” on page 28

Results

The generic and offering specific log files that are generated during the fullinstallation are saved in the following locations:

On UNIX systems: $HOME/jazzsm_launchpad/logs/.

Changing the default DB2 portIf you cannot use 50000 as the default port number for TCP/IP communicationwith the DB2 instance, you must modify the DB2 sample response file.

Before you begin

By default, the full installation uses the 50000 port to configure the DB2 instancefor TCP/IP communication. The full installation fails, if this port is already in use.You must change the value for the DB2_INST.PORT_NUMBER to an available port inthe DB2 sample response file.

Procedure1. Browse to the following directory and open the db2ese.rsp file:

Table 5. Location of the db2ese.rsp file

Option Description

On AIX systems Install_Imgs_Home/ese/db2/aix/samples


Table 5. Location of the db2ese.rsp file (continued)

Option Description

On Linux systems Install_Imgs_Home/ese/db2/linuxamd64/samples

On Windows systems Install_Imgs_Home/ESE/image/db2/Windows/samples

2. Change the value for the DB2_INST.PORT_NUMBER to an available port numberand save the file.

Note: After you change value for the port number, do not uncomment the line.

Verifying the installationYou can verify the installation of IBM WebSphere Application Server Version 8.5.0.1and the Jazz for Service Management integration services.

About this task

For more information about this task, see http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_t_install_adv_verification.html?lang=en

Procedure

Verify the Dashboard Application Services Hub installation:1. Log in to the Dashboard Application Services Hub console. See Logging in.2. If required, start the Jazz for Service Management application server.Verify the Registry Services installation3. Open a browser window and send an HTTP GET request to the provider URL

that represents the server and port to which you deployed Registry Services.For example:https://<myserver.mycompanydomain.com>:16311/oslc/pr If this request issuccessful, it returns 200 (OK) with a response body that contains the providerregistry description.

Verify the Administration Services installation:4. If required, log in to the Dashboard Application Services Hub, and verify that

the Administration Services icon in the navigation bar.5. If the Administration Services icon is not visible, you must assign an

Administration Services role to your user ID as follows:a. Click Console Settings > User Roles. The User Roles page opens.b. In the User ID field, enter your user ID and click Search.c. In the table, select your User ID. The User Roles > Available Roles page

opens.d. In the table, select the Platform Administrator role and click Save.e. Log out and then log on again.

6. In the navigation bar, click Administration > Administration. TheAdministration window opens. Verify if the Applications view displays themanaged systems, and that the Application Details view displays the tasksthat are associated with the selected managed system.


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_t_install_adv_verification.html?lang=en



http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/tip_original/ttip_start_logon.html?lang=en

What to do next

If you cannot access the web page in step 3, restart Jazz for Service Managementapplication server.

Some configuration or administration tasks for an integration service require thatyou restart the IBM WebSphere Application Server. Stopping a Jazz for ServiceManagement application server impacts all integration services installed in theassociated WebSphere Application Server profile.Related tasks:Stopping Jazz for Service Management application serversYou can stop any Jazz for Service Management application server by using the IBMWebSphere stopServer command. You might need to restart the application serverafter you complete a configuration task for an integration service, or stop theapplication server for maintenance. To start the server again, use the startServercommand.Starting Jazz for Service Management application serversYou can start any Jazz for Service Management virtualization and reporting serversby using the IBM WebSphere startServer command. You might need to restart theapplication server after you complete a configuration task for an integrationservice, or after you take down the application server for maintenance.Related information:

Jazz for Service Management post installation tasks

Verifying the Tivoli Common Reporting installationTo verify the installation, you can use different URLs to log in and access thereporting interface.

About this task

You can verify the installation by accessing the reporting interface as follows:

Dashboard Application Services Hub

Log in to the reporting interface from the Dashboard Application ServicesHub login page.

Both Dashboard Application Services Hub and Tivoli Common Reportingare installed in the same application server environment, and the reportinginterface is integrated with Dashboard Application Services Hub.

Direct accessLog in to the reporting interface from its own login page.

Tivoli Netcool Performance Manager’s user interfaceLog in to the reporting interface from a Tivoli product’s login page.

Procedurev Access the reporting interface from Dashboard Application Services Hub as

follows:1. Open a web browser and enter the following URL for the Jazz for Service

Management UI and reporting server:https://host.domain:port/<DASH_context_root>For example: https://<myJazzSMserver.ibm.com>:16311/ibm/console


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_ctr_install_post_install.html?lang=en

– host.domain is the fully qualified host name or IP address of the Jazz forService Management UI and reporting server.

Note: When single sign-on (SSO) is enabled, ensure that you use the fullyqualified host name in the URL of the Jazz for Service Managementreporting and UI server. SSO requires that the browser pass LTPA cookiesto the Jazz for Service Management application server, and these cookiescontain the fully qualified host name.

– port is the secure HTTPs port number that was specified duringinstallation. The default value is 16311.

– /DASH_context_root is the context root for the console that was specifiedduring installation. The default value is /ibm/console.

2. On the Dashboard Application Services Hub login page, enter the WebSphereadministrator user ID and password that were specified during installation.Click Log in. The Dashboard Application Services Hub Welcome page opens.

3. In the navigation bar, verify that Reporting icon > Common Reportingexists. If Reporting icon does not exist in the navigation bar, complete thefollowing steps:a. Click Console Settings > User Roles. The User Roles page opens.b. In the User ID field, enter your user ID and click Search.c. In the table, select your user ID. The User Roles > Available Roles page

opens.d. In the table, select the tcrPortalOperator role and click Save.e. Log out and then log in again.

v In the navigation bar, click Reporting icon > Common Reporting. The CommonReporting portal is displayed within a Dashboard Application Services Hubportlet page.

v Verify that you can run and view the sample report. See Running the sampleoverview report.

v Access the reporting interface directly as follows:1. Open a web browser and enter the following URL for the reporting interface:

http://<host.domain:port>/tarf/servlet/dispatchFor example: http://<myJazzSMserver.ibm.com>:16310/tarf/servlet/dispatch

– host.domain is the fully qualified host name or IP address of the Jazz forService Management reporting server.

Note: When single sign-on (SSO) is enabled, ensure that you use the fullyqualified host name in the URL of the Jazz for Service Managementreporting server.

– port is the non-secure HTTP port number that was specified duringinstallation. The default value is 16310.

2. On the Log on to IBM Cognos Software page, enter the WebSphereadministrator user ID and password that were specified during installation.Click OK. The Common Reporting portal opens.

3. Verify that you can run and view the sample report.


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/tcr_original/ttcr_run_moswos.html?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/tcr_original/ttcr_run_moswos.html?lang=en

What to do next

You can check the installation log for any error messages that are generated by theinstallation. Locate the TCR3101InstallMessage00.log ,TCR3101InstallTrace00.log,TCR3102InstallMessage00.log, and TCR3102InstallTrace00.log files in the userhome directory on UNIX systems.

In a Dashboard Application Services Hub environment, you must assigntcrPortalOperator role to new users and user groups, otherwise they cannotaccess the reporting interface from the console.

In any of the supported environments, you can also change permissions in thereporting interface to restrict access to various reporting resources and functionsafter you configure the security permissions. See Configuring security permissions.Related information:

Verifying the Tivoli Common Reporting installation

Stopping Jazz for Service Management application serversYou can stop any Jazz for Service Management application server by using the IBMWebSphere stopServer command. You might need to restart the application serverafter you complete a configuration task for an integration service, or stop theapplication server for maintenance. To start the server again, use the startServercommand.

Procedure1. On the relevant Jazz for Service Management server, open a command window.2. Change to the JazzSM_WAS_Profile/bin directory. The default location for

<JazzSM_WAS_Profile> is /opt/IBM/JazzSM/profile.3. Run the following command:

./stopServer.sh <server_name> -username <WAS_admin_user_name> -password <WAS_admin_password>

Where

server_nameEnter the name of the application server that was specified when theapplication server profile was created. For example, server1.

WAS_admin_user_nameThe default user name is smadmin.

WAS_admin_passwordThis is the password that is specified at the time of installation.

Example

stopServer.sh server1 -username smadmin -password jazzsmpwd


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/tcr_original/ttcr_config_sec.html?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_t_install_adv_verification_tcr.html?lang=en

Starting Jazz for Service Management application serversYou can start any Jazz for Service Management virtualization and reporting serversby using the IBM WebSphere startServer command. You might need to restart theapplication server after you complete a configuration task for an integrationservice, or after you take down the application server for maintenance.

About this task

The same procedure applies to any Jazz for Service Management applicationserver.

Procedure1. On the relevantJazz for Service Management server, open a command window.2. Change to the JazzSM_WAS_Profile/bin directory. The default location for

<JazzSM_WAS_Profile> is /opt/IBM/JazzSM/profile.3. Run the following command:

./startServer.sh server_name

Where

server_nameEnter the name of the application server that was specified when theapplication server profile was created. For example, server1.

Uninstalling Jazz for Service ManagementYou can uninstall or roll back the modification for the following integrationservices: Administration Services, IBM Dashboard Application Services Hub,Registry Services, and Security Services. Use the Rollback function of InstallationManager to remove the fix pack and return your environment to its state beforethe fix pack installation. You can also roll back to the previous version of the Jazzfor Service Management extension for IBM WebSphere.

About this task

Attention: You cannot roll back to the original Tivoli Common Reporting Version3.1 or 3.1.0.1 environment, that is, you cannot uninstall the Tivoli CommonReporting Version 3.1 Fix Pack 2 delta. You can perform a full uninstallation ofTivoli Common Reporting.

Procedure

Use IBM Installation Manager in GUI or silent modes to uninstall Version 1.1.1.0.

Note: When you revert to the previous version of Jazz for Service Management,Installation Manager does not automatically install interim fixes. You mustmanually install interim fixes after you roll back.Related information:

Uninstalling Jazz for Service Management


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_c_install_uninstall_oview.html?lang=en


Chapter 6. Running the Dependency Checker tool

The dependency_checker tool helps you to validate the configuration of a serverbefore you begin an installation or upgrade. It detects any problems with theplatform configuration.

Before you begin

Before you run the dependency_checker, ensure that Korn Shell (ksh) is present inthe /usr/bin path. If ksh is not available, then create a softlink by using thefollowing command:ln -s /bin/ksh /usr/bin/ksh

Note: Dependency Checker tool must be run only after you install the Jazz forService Management.

About this task

The dependency_checker checks the following aspects:v Operating system type and versionv Existing file systems and available disk spacev Installation of prerequisite packagesv Location of Tivoli Netcool Performance Manager packagesv Oracle configuration, if Oracle is already installed

For installation, on distributed servers, use the -t option to specify the type ofserver you are checking.

Procedure1. Copy all of the Tivoli Netcool Performance Manager package files to a

designated target directory on the server. The recommended location for thepackage files is /appl.

2. Set the permissions on dependency_checker before you run by giving thefollowing command:chmod u+x dependency_checker

3. Run the following commands as user root:cd <package location>./dependency_checker [ -t app|db|ds|ldr|standalone ] [ -upgrade ] [ -pkgs <packages_list>][ -nopkgcheck ]

For upgrade, run the dependency checker with the -upgrade option on eachserver before you upgrade the server.v -t app (Application server)v -t db (Database server)v -t ds (Directory server)v -t ldr (Loader server)v -t standalone (Stand-alone Server)v -upgrade (All servers)


Results

The script performs a number of checks on the system. The following exampleoutput shows a successful check with no reported problems:./dependency_checker

======================================================================Tivoli Netcool Performance Manager pre-installation check======================================================================

Checking PATH.../usr/sbin: OK/usr/bin: OK

Performing checks for server type: all

-------------------------------------------------------------Perform Operating System configuration checks-------------------------------------------------------------

Hostname: <myserver.ibm.com>Processor type x86_64 is supported.Operating system version Red Hat Enterprise Linux Server release 5.9(Tikanga) is at supported level.

-------------------------------------------------------------Perform Host Setup configuration checks-------------------------------------------------------------

Fully Qualified Domain name: <myserver.ibm.com>Checking IP address... OKChecking root user umask...OK

-------------------------------------------------------------Checking installed Linux packages for sds-------------------------------------------------------------

Checking package: byacc x86_64... Status: OKChecking package: nscd x86_64... Status: OKChecking package: compat-libstdc++-296 i386... Status: OKChecking package: compat-libstdc++-33 x86_64... Status: OKChecking package: compat-libstdc++-33 i386... Status: OKChecking package: compat-gcc-34 x86_64... Status: OKChecking package: compat-gcc-34-c++ x86_64... Status: OKChecking package: compat-libf2c-34 x86_64... Status: OKChecking package: compat-libf2c-34 i386... Status: OKChecking package: kernel-headers x86_64... Status: OKChecking package: glibc-headers x86_64... Status: OKChecking package: glibc-devel x86_64... Status: OKChecking package: glibc-devel i386... Status: OKChecking package: libgomp x86_64... Status: OK

-------------------------------------------------------------Checking installed Linux packages for oracle-------------------------------------------------------------

Checking package: byacc x86_64... Status: OKChecking package: nscd x86_64... Status: OKChecking package: binutils x86_64... Status: OKChecking package: compat-db x86_64... Status: OKChecking package: compat-libstdc++-33 x86_64... Status: OKChecking package: compat-libstdc++-33 i386... Status: OKChecking package: compat-libstdc++-296 i386... Status: OKChecking package: control-center x86_64... Status: OKChecking package: elfutils-libelf-devel x86_64... Status: OKChecking package: gcc x86_64... Status: OKChecking package: gcc-c++ x86_64... Status: OK


Checking package: glibc x86_64... Status: OKChecking package: glibc i686... Status: OKChecking package: glibc-common x86_64... Status: OKChecking package: glibc-devel x86_64... Status: OKChecking package: glibc-devel i386... Status: OKChecking package: glibc-headers x86_64... Status: OKChecking package: libgcc x86_64... Status: OKChecking package: libgcc i386... Status: OKChecking package: libaio x86_64... Status: OKChecking package: libaio i386... Status: OKChecking package: libaio-devel x86_64... Status: OKChecking package: libaio-devel i386... Status: OKChecking package: libstdc++ x86_64... Status: OKChecking package: libstdc++-devel x86_64... Status: OKChecking package: libgomp x86_64... Status: OKChecking package: libXp i386... Status: OKChecking package: libXp x86_64... Status: OKChecking package: make x86_64... Status: OKChecking package: sysstat x86_64... Status: OK

-------------------------------------------------------------Checking installed Linux packages for jboss-------------------------------------------------------------

Checking package: byacc x86_64... Status: OKChecking package: nscd x86_64... Status: OKChecking package: eclipse-ecj x86_64... Status: OKChecking package: zlib-devel x86_64... Status: OKChecking package: libgcj-devel x86_64... Status: OKChecking package: gcc-java x86_64... Status: OKChecking package: java-1.4.2-gcj-compat-devel x86_64... Status: OK

-------------------------------------------------------------Perform Filesystem configuration checks-------------------------------------------------------------

Checking space on / partition...OK

-------------------------------------------------------------Perform Oracle configuration checks-------------------------------------------------------------

Checking if Oracle User exists... OKChecking oracle user shell... OKChecking oracle user umask... OKChecking oracle group... OKOracle inventory directory /appl/oracle/product/oraInventory does not exist

-------------------------------------------------------------Perform TNPM core package checks-------------------------------------------------------------

Checking for core packages in /applChecking for package jre... OKChecking for package ant... OKChecking for package java-libs... OKChecking for package as-core... OKChecking for package core... OKChecking for package sap... OKChecking for package njloader... OKChecking for package ds-conf... OKChecking for package db-install... OKChecking for package db-conf... OKChecking for pmw_install... OKChecking for Platform package... OK

-------------------------------------------------------------

Chapter 6. Running the Dependency Checker tool 41

Checking for JBoss package-------------------------------------------------------------

-------------------------------------------------------------Perform SDS / DB2 package checks-------------------------------------------------------------

Checking for SDS packages in /appl/depends/sds631Checking for SDS package base... OKChecking for SDS package db2... OKChecking for SDS package gskit... OK

-------------------------------------------------------------Perform JAZZ SM/ TCR installation checks-------------------------------------------------------------

Checking default ports (16310 / 16311) for TCR... Not ConfiguredChecking default installation directories for Jazz SM & TCR:/opt/IBM/JazzSM/profile/bin/ ... Missing/opt/IBM/JazzSM/reporting/bin ... Missing

Jazz SM and TCR are not installed on the system.

GYMWI0069E FAIL: Missing Jazz SM & TCR Installation

-------------------------------------------------------------Perform files checks-------------------------------------------------------------

Checking required files.../usr/bin/ksh: OK

-------------------------------------------------------------The following tests failed -- you must investigate and fixthese failures before beginning the installation-------------------------------------------------------------

FAILURE: 1GYMWI0069E Missing Jazz SM & TCR InstallationYou must install Jazz SM along with TCR before installing TNPM Wireless Component.-------------------------------------------------------------

The script reports a FAIL message for any checks that return an invalid result. Asummary of these errors displays when the script completes. The followingexample output shows a number of FAIL messages:-------------------------------------------------------------The following tests failed -- you must investigate and fixthese failures before beginning the installation-------------------------------------------------------------FAILURE: 1GYMWI0020E oracle Linux packages are missingcompat-db:x86_64 libaio-devel:x86_64 libXp:x86_64 sysstat:x86_64-------------------------------------------------------------FAILURE: 2GYMWI0069E Missing Jazz SM & TCR InstallationYou must install Jazz SM along with TCR before installing TNPM Wireless Component.-------------------------------------------------------------

A full list of error messages is given in Appendix C, “Dependency Checker errors,”on page 125.


Chapter 7. Installing Oracle RDBMS and the Oracle client

Describes the Oracle RDBMS and Oracle client installation andconfiguration information.

Install the Oracle 11g RDBMS software on a stand-alone system or on the databaseserver in a distributed system. Do not install the Oracle 11g Client software on astand-alone system. Install the Oracle 11g Client software on the application serverin a distributed system only, to make SQL*Plus available to certain programs.

Configuring Oracle environment variables

If Oracle 11g is already installed on the stand-alone or databaseserver, then ensure that the correct Oracle environment variables are set in theprofile of the oracle user.

Before you begin

You must have created User and Group Accounts before you can ensure that thecorrect Oracle environment variables are set.

About this task

The procedure uses the default variables, ensure that you use the correct variablevalues for your Oracle installation.

Procedure

To set the correct Oracle environment variables, as user oracle, edit the file${HOME}/.profile to include the following variables:ORACLE_OWNER=oracleexport ORACLE_OWNERORACLE_BASE=/appl/oracleexport ORACLE_BASEORACLE_HOME=/appl/oracle/product/11.2.0/db_1export ORACLE_HOMEPATH=$PATH:$ORACLE_HOME/binexport PATHLD_LIBRARY_PATH=$ORACLE_HOME/libexport LD_LIBRARY_PATHNLS_LANG=_.WE8ISO8859P1export NLS_LANG


Installing Oracle 11gBefore you install the Oracle software, note the location of the following software.v Oracle 11.2.0.4 software and Patch Setv Oracle 11.2.0 client software, consists of:

– Oracle 11.2.0 Client– Oracle Instant Client basic– Oracle Instant Client SQL*Plus

Installing Oracle RDBMS (stand-alone system or databaseserver)

Install Oracle 11g by using the scripts that are provided in the platform package.Must be installed on a stand-alone server, or on the database server in adistributed environment. The Oracle installation takes approximately 30 minutesdepending on the specification of the server.

About this task

The Oracle RDBMS (stand-alone system or database server) must be installed on astand-alone server, or on the DB server in a distributed environment.

Note: If Oracle was previously installed on the server, you must respond to theon-screen questions. Default values are displayed and it is recommended that youoverwrite the files if they exist.

Note: Ignore the message ksh: : not found.

Note: If you have a problem with the installation, you can remove the <Oraclebase> directory and restart the Oracle 11g installation by running theoracle11gR204_install command again.

Procedure1. Run the commands as user root on the server:

#/var/install/sbin/oracle11gR204_install

The installation conducts a number of checks:Check Oracle User exists....... DoneCheck oinstall group exists....... OKCheck dba group exists....... OK-----------------------------------------------------------------------Please select the Type of Install you wish to executeby entering the number associated with the Install Type :

Full install (Oracle 11.2.0.4 + 11.2.0.x.x patch set update) (1)Oracle 11.2.0.4 Client only (2)Oracle 11.2.0.4 Instant Client only (3)11.2.0.x Patch Set (4)11.2.0.x.x Patch Set Update (5)Oracle 11.2.0.x oneoff patches (6)

-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6] :

2. For a full installation, select option 1.


3. At the prompts, specify the location of the Oracle Software and where youwant to install the software. Enter the paths to the Oracle software distributionas requested.Please enter the location of the Oracle 11.2.0.4 Software [cdrom/cdrom0/database]:

4. Enter the destinations for the Oracle software. In most cases, the defaults areacceptable.Please enter the install location of the Oracle Base [/appl/oracle]:

Please enter the value of ORACLE_HOME [/appl/oracle/product/11.2.0/db_1]:Please enter the value of ORACLE_HOME_NAME [OraDBHome11R204]:

When the Oracle Software installation is finished, the installation continues onto run the Oracle root.sh script.

5. You do not require any patches with Oracle 11.2.0.4. At the prompt, enter none:Please enter the location of the Oracle 11.2.0.4 compressed OPatch patch zip(’none’ for none) [/cdrom/cdrom0/patches/opatch]:noneNo OPatch patch available to be installedPlease enter the location of the Oracle PSU 11.2.0.x.x uncompressed patches(’none’ for none) [/cdrom/cdrom0/patches/psu]:noneNo PSU patches to be installed

6. At the prompt for the location of the Oracle one-off patches, enter none.Currently, there are no required one-off patches for Tivoli Netcool PerformanceManager, Version 1.4.1 and Oracle 11g.Please enter the location of the Oracle 11.2.0.4 uncompressed one-off patches

(’none’ for none) [/cdrom/cdrom0/patches/oneoff]:

none

What to do next

See the Oracle Installation log output in /var/install/logs/oracle11gR204_install_<PID>.log.

Installing Oracle database 11g Client (Application Server orTivoli Common Reporting server in Distributed Systems only)

Install the Oracle database 11g Client software only on an application server orTivoli Common Reporting server in a distributed system. The Oracle database 11gsoftware files must be on the application server or Tivoli Common Reportingserver during the Oracle database Client installation.

Before you begin

Important: Do not install Oracle database Client on a stand-alone system.

About this task

You must install the Oracle database 11g Client on any server where TivoliCommon Reporting is installed. Using the scripts that are provided in the platformpackage to install. The Oracle database Client installation takes approximately 5minutes depending on the specification of the server.

Note: You can ignore the message ksh: : not found.

Chapter 7. Installing Oracle RDBMS and the Oracle client 45

The Oracle Instant_Client 64-bit files are in the following format:v instantclient-basic-solaris.sparc64-11.2.0.4.0.zip

v instantclient-sqlplus-solaris.sparc64-11.2.0.4.0.zip

The Oracle Instant_Client 32-bit files are in the following format:v instantclient-basic-solaris.sparc32-11.2.0.4.0.zip

v instantclient-sqlplus-solaris.sparc32-11.2.0.4.0.zip

The Oracle Instant_Client 64-bit files are in the following format:v instantclient-basic-aix.ppc64-11.2.0.4.0.zipv instantclient-sqlplus-aix.ppc64-11.2.0.4.0.zip

The Oracle Instant_Client 32-bit files are in the following format:v instantclient-basic-aix.ppc32-11.2.0.4.0.zipv instantclient-sqlplus-aix.ppc32-11.2.0.4.0.zip

The Oracle Instant_Client 64-bit files are in the following format:v instantclient-basic-linux.x64-11.2.0.4.0.zipv instantclient-sqlplus-linux.x64-11.2.0.4.0.zip

The Oracle Instant_Client 32-bit files are in the following format:v instantclient-basic-linux-11.2.0.4.0-32.zipv instantclient-sqlplus-linux-11.2.0.4.0-32.zip

Procedure1. Copy the required Oracle files to the application server or Tivoli Common

Reporting server.2. To install the Oracle 11g client, run the following commands as user root on

the server:# /var/install/sbin/oracle11gR204_install

The installation conducts a number of checks:Check Oracle User exists....... DoneCheck oinstall group exists....... OKCheck dba group exists....... OK-----------------------------------------------------------------------Please select the Type of Install you wish to executeby entering the number associated with the Install Type :


-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 /6] : 2

3. To install the client, select option 2.


4. At the prompts, specify the location of the Oracle Software and the locationwhere you want to install the Oracle software. Enter the paths to the OracleClient software distribution as requested.Please enter the location of the Oracle 11.2.0.4 Software[/cdrom/cdrom0/client]:

5. Enter the destinations for the Oracle software. In most cases, the defaults areacceptable.Please enter the install location of the Oracle Base [/appl/oracle]:Please enter the value of ORACLE_HOME [/appl/oracle/product/11.2.0/db_1]:The directory /appl/oracle/product/11.2.0/db_1 does not exist and will be createdPlease enter the value of ORACLE_HOME_NAME [OraDBHome11R204]:

6. When the Oracle Software installation is finished, the installation continues onto run the Oracle root.sh script. When prompted, enter the location of theOracle 64-bit Instant Client and the SQL*Plus extension .zip files. In mostcases, the defaults are acceptable.Please enter the location of the Oracle Instant Client ziparchive(s): [/cdrom/cdrom0/Instant_Client]

7. When prompted, enter the location of the Oracle 32-bit Instant Clientcompressed file archive.Please enter the location of the Oracle 32 Bit Instant Clientzip archive(s): [/cdrom/cdrom0/Instant_Client]

What to do next

Note: If Oracle was previously installed on the server, you must respond to theon-screen questions. Default values are displayed and it is recommended that youoverwrite the files if they exist.

Note: If you have a problem during the installation, you can remove the <Oraclebase> directory and restart the Oracle 11g installation by running theoracle11gR204_install command again.

You can see the Oracle Installation log output in the /var/install/logs/oracle11gR204_install_<PID>.log file.

Installing Oracle 11.2.0.4 Instant Client (stand-alone Server ordatabase Server combined with Tivoli Common Reportingserver)

Install the Oracle database 11.2.0.4 Instant Client on the server where TivoliCommon Reporting is to be installed or upgraded. The Instant Client must beaccompanied by either the Oracle Client or Oracle Server.

Procedure1. Copy the Oracle files to the Tivoli Common Reporting server.2. To install the Oracle 11.2.0.4 Instant Client, run the following command as user

root on the server:# /var/install/sbin/oracle11gR204_install

The installation conducts a number of checks:Check Oracle User exists....... DoneCheck oinstall group exists....... OKCheck dba group exists...


.... OK-----------------------------------------------------------------------Please select the Type of Install you wish to executeby entering the number associated with the Install Type :


-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6] : 3

3. To install the Oracle Instant Client only, select option 3.4. Enter the destinations for the Oracle software. In most cases, the defaults are

acceptable.lease enter the install location of the Oracle Base[/appl/oracle]:Please enter the value of ORACLE_HOME[/appl/oracle/product/11.2.0/db_1]:Please enter the value of ORACLE_HOME_NAME[OraDBHome11R204]:

5. When prompted, enter the location of the Oracle Instant Client and theSQL*Plus extension .zip files. In most cases, the defaults are acceptable.Please enter the location of the Oracle Instant Client ziparchive(s): [/cdrom/cdrom0/Instant_Client]

6. When prompted, enter the location of the Oracle 32-Bit Instant Clientcompressed file.Please enter the location of the Oracle 32 Bit Instant Client zip archive(s):[/cdrom/cdrom0/Instant_Client]

Results

You see the output as follows:--------Oracle 11g installation completed-----

What to do next

Note: If you have a problem during the installation, you can remove the <Oraclebase> directory and restart the Oracle 11.2.0.4 installation by running theoracle11gR204_install command again.

You can see the Oracle Installation log output in the /var/install/logs/oracle11g_install_<PID>.log file.

Checking Oracle configurationYou use the dependency checker tool to validate Oracle configuration beforeproceeding.

Procedure

Run the following command to validate Oracle configuration, as user root:cd <target_directory>./dependency_checker -t db


The script validates that Oracle is installed correctly. If any FAIL messages display,investigate them and resolve the problems before you continue the installation.

Stopping the listener processBefore you start the installation, check that there is no listener process that isrunning on the system.

About this task

You must ensure that the listener process is stopped before you begin theinstallation:

Procedure1. Run the following command on the database server (or stand-alone server if

you are installing on a single computer):ps -ef | egrep [t]ns

If this command returns nothing, then proceed with the installation.2. If the previous step returns output similar to the following:

oracle 29466 28166 0 10:37:55 ?0:07 /appl/oracle/product/11.2.0/db_1/bin/tnslsnr LISTENER -inherit

Then, this process must be stopped by running the following command as thedatabase owner:$ lsnrctl stop <LISTENER_NAME>

Where <LISTENER_NAME> is the name of the listener that is returned by the pscommand. In the above example, the listener name is LISTENER.



Chapter 8. Installing the Security Directory Server and IBMDB2

You use the scripts that are provided in the platform package toinstall Security Directory Server and IBM DB2.

Note: Perform these procedures on a stand-alone directory server, or applicationserver.

Required packagesThe required packages for the installation are distributed on the Tivoli NetcoolPerformance Manager installation media in the folder /appl/depends/sds631.

v IBM Security Directory Server 6.3 Client-Server with entitlement Solaris(sds631-solaris-sparc-base.tar)

v IBM Security Directory Server 6.3 GSkit Solaris (sds631-solaris-sparc-gskit.tar)

v IBM Security Directory Server 6.3, DB2 v 9.7 Solaris (sds631-solaris-sparc-db2.tar)

v IBM Security Directory Server 6.3 Client-Server with entitlement Linux x86-64(sds631-linux-x86-64-base.tar)

v IBM Security Directory Server 6.3 GSkit Linux x86-64 (sds631-linux-x86-64-gskit.tar)

v IBM Security Directory Server 6.3, DB2 v 9.7 Linux x86-64 (sds631-linux-x86-64-db2.tar)

v IBM Security Directory Server 6.3 Client-Server with entitlement AIX x86-64(sds631-aix-ppc64-base.tar)

v IBM Security Directory Server 6.3 GSkit AIX x86-64 (sds631-aix-ppc64-gskit.tar)

v IBM Security Directory Server 6.3, DB2 v 9.7 AIX x86-64 (sds631-aix-ppc64-db2.tar)


Running the Security Directory Server installation scriptsYou install Security Directory Server and IBM DB2 by using the scripts that areprovided in the platform package.

About this task

Note: The default encryption seed for the LDAP instance referred to by theSecurity Directory Server and DB2 installation is autogenerated by the operatingsystem's pseudorandom number generator. The encryption seed that is used for theinstance is logged in /var/install/logs/sds_install_<PID>.log and must benoted securely for future reference.

Note:

If the idsinst user account becomes unavailable, for example, due to an expired orchanged password, Security Directory Server can no longer be able to authenticateaccess to DB2 and the LDAP server becomes inoperative. To rectify this issue, seethe following IBM technote for information about updating the Security DirectoryServer password for the DB2 instance: http://www-01.ibm.com/support/docview.wss?uid=swg21297067.

Ensure that you enter the correct password for the idsinst user.At the prompts, enter and confirm the password for the DB2 Administrator(idsinst user). This password was set up when the idsinst user was created (see“Creating user and group accounts” on page 18).

Procedure1. Run the following command as user root:

# /var/install/sbin/sds_install -base <target directory> -product virtuo -version 6.3.1

Use the /appl directory as the <target directory> value.2. Provide the required information at the prompts, including the requests for the

absolute path names of the Security Directory Server, DB2, and GSK packages:Enter the full pathname of the DS package:/appl/depends/sds631/sds631-<OS>-<arch>-base.tarEnter the full pathname of the DS DB2 package:/appl/depends/sds631/sds631-<OS>-<arch>-db2.tarEnter the full pathname of the GSK package:/appl/depends/sds631/sds631-<OS>-<arch>-gskit.tarEnter the full pathname of the sds patch package, if required:Enter the full pathname of the DB2 patch package, if required:

...performing pre-install steps for Security Directory ServerDOMAIN set to server.ibm.com

3. Enter the remaining information that is requested by the script. The defaultscan be used.Please, enter the DB2 Administrator (idsinst user) password: []---->----><idsinst password>

Please, enter the DB2 Administrator (idsinst user) password a second time: []

---->----><idsinst password>Please, Enter the LDAP instance location: [/appl/ldap]---->Instance location set to /appl/ldap




Please, Enter the encryption seed (12 digits): [240811423792]---->

Encryption seed set to 240811423792

Please, Enter the LDAP Administrator DN: [cn=Directory Manager]

---->Administrator DN set to cn=Directory Manager

Please, Enter the LDAP Administrator password: [Dirmgr01]

---->Administrator password set to Dirmgr01Please, Enter the LDAP port number: [1389]

---->Port number set to 1389

Please, Enter the LDAP secure port number: [1636]

---->

Secure port number set to 1636

Please, Enter the DB2 database name: [idsdb]DB name set to idsdb... Unpacking IBM Security Directory Server.

4. Enter 1 to accept the license agreement in the following screen:

Press Enter to continue viewing the licenseagreement, or, Enter 1" to accept the agreement, "2" to decline itor "99" to go back to the previous screen, "3" Print.

The installation log files are var/install/logs/sds_install_<PID>.log and/tmp/db2_install.log.<PID>.The sds_install script also supports a -remove option. You can completelyremove the Security Directory Server and DB2 installation by entering thefollowing command:# /var/install/sbin/sds_install –base <target directory> –product virtuo-remove -version 6.3.1

Note: You can ignore the mbind: Invalid argument error message that youmight see when you are installing Security Directory Server on a Linux 6.xserver.

What to do next

Set the Directory Server Password Policy. For more information about the DirectoryServer Password Policy, see Administering Tivoli Netcool Performance Manager -Wireless Component.

Chapter 8. Installing the Security Directory Server and IBM DB2 53

Installing the Security Directory Server clientInstall the Security Directory Server client on the application server if you areusing a remote directory server.

About this task

If you have the directory server that is installed on the application server, you donot need to install the directory server client.

Procedure1. To install the Security Directory Server client, as user root, enter the following

command in one line:# /var/install/sbin/sds_install -base <target directory>-product virtuo -version 6.3.1 -client

It is recommended to use the /appl directory as the <target directory> value.2. Provide the required information at the prompts, including the requests for the

absolute path names of the Security Directory Server package.Enter the full path name of the directory server package: /var/install/packages/sds63-<OS>-<arch>-base.tar

.... Unpacking IBM Security Directory Server.

The installation log files are in /var/install/logs/sds_install_<PID>.log

The sds_install script also supports a -remove option. You can completelyremove the Security Directory Server Client installation by entering thefollowing command on one line:# /var/install/sbin/sds_install -base <target directory> -productvirtuo -client -remove -version 6.3.1


Chapter 9. Installing the Tivoli Netcool Performance Managersoftware

Install the Tivoli Netcool Performance Manager software by usingone of the following scenarios.v Unattended installation of a stand-alone system (if a response file is available)v Installation of a stand-alone systemv Installation of a distributed system

Note: If you are upgrading Tivoli Netcool Performance Manager, consultUpgrading Tivoli Netcool Performance Manager - Wireless Component.

Important: Before installing Tivoli Netcool Performance Manager, you are stronglyadvised to read the Release Summary for Tivoli Netcool Performance Manager.Release Summary can contain information specific to your installation that is notcontained in this information. Failure to consult the release notes might result in acorrupted, incomplete or failed installation. You are also advised to refer to thefollowing link for all the existing known issues in Tivoli Netcool PerformanceManager, 1.4.1.

After the installation is complete, apply the Tivoli Netcool PerformanceManager1.4.1 patch that is available in the software distribution.

Note: It is recommended not to interrupt the installation at any point. Theinstallation will exit if there is a problem.Related tasks:“Applying Tivoli Netcool Performance Manager 1.4.1 patch” on page 82You must apply the 1.4.1 patch after you install Tivoli Netcool PerformanceManager 1.4 package from software distribution.

Prerequisites

The prerequisites for Tivoli Netcool Performance Manager softwareinstallation.

Installed software:v Oracle 11g RDBMSv Security Directory Server and IBM DB2v Jazz for Service Managementv All the required RHEL packages on RHEL serversv All the required AIX packages on AIX servers


Installing a stand-alone system unattended

You can install Tivoli Netcool Performance Manager on a singleserver by using a response file to provide the necessary configuration information.

About this task

Response files that are provided with some distributions provide all of theinformation necessary for an unattended installation. Check the Release Notes tosee if your software distribution includes a response file.

Note: If you are using a response file, ensure that all required software packagesare in the expected locations.

Note: If you want to install Tivoli Netcool Performance Manager in a directoryother than the default directory: /appl/virtuo, specify the directory by using the-wmcr switch.

Procedure1. To install Tivoli Netcool Performance Manager by using a response file, place

all of the Tivoli Netcool Performance Manager core packages in to the /appldirectory. Core packages are listed in section “Location of the Tivoli NetcoolPerformance Manager software” on page 6

2. Copy all the technology pack packages, the technology pack order file, andgateway packages in to /appl.

3. Run the following command as user root:# cd /appl# ksh pmw_install -wmcr /appl/virtuo -r <path to response file name>

<path to response_file name> is the name and path of the response file.

What to do next

After you have accepted the license agreement, the unattended installationproceeds. After you install the Tivoli Netcool Performance Manager software, theinstallation automatically installs the gateways and technology packs.

For detailed information about the installation and the database creation consultthe log files:

$WMCROOT/admin/logs/pmw_install.log

/appl/oracle/cfgtoollogs/dbca/vtdb/trace.log


Installation of a stand-alone system

Use the interactive installation scripts to install Tivoli NetcoolPerformance Manager on a single server.

Running an interactive installationYou start an interactive installation by running the pmw_install script. At theprompts, provide the required information.

Procedure1. Place all of the Tivoli Netcool Performance Manager software packages in the

/appl directory of the server.2. Run the following as user root:

# cd /appl# ksh pmw_install -wmcr <WMCROOT>

<WMCROOT> is the location where you want to install Tivoli Netcool PerformanceManager. The recommended installation directory is: /appl/virtuo.Read and accept the license agreement. The following menu is displayed:What Type of System Are you Installing?1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit PMW Install---->

3. To install a stand-alone system, select option 1.4. At the prompt, enter yes to deploy the packages.

Do you want to deploy the packages? [yes/no] >yesPlease, Verify Environment Settings..........................

The installation lists the default values of Tivoli Netcool Performance Managerenvironment variables. These variables set server host names and various TCPport numbers and varies from location to location. You can accept the defaultvalues, restore values to their default settings, or change individual values.

Important: It is important that you set each of these environment variables tothe correct value.

5. Accept the default values listed, or select individual values to change them.6. When you are satisfied that the environmental variable values are correct,

accept the values and proceed.

Chapter 9. Installing the Tivoli Netcool Performance Manager software 57

Installing the JBoss application serverThe installation proceeds to install the JBoss Application Server.

Procedure1. At the prompt, enter yes to install the JBoss Application Server.

Would you like to perform task JBOSS_INSTALL ? [yes/no] >yes

2. At the prompt, enter the location of the JBoss archive. The installation searchesthe location that you provide for version 4.0.3 SP1 of the JBoss ApplicationServer in .zip, .tar.gz , or .tar.bz2 format.Please enter the location of the JBoss 4.0.3SP1 archive(or q to quit)!: [/appl]---->/appl

The installation expands the archive into the necessary location:...........Buildfile: /appl/virtuo/admin/common/install/scripts/build.xmlinit:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/applfind-archive:expand-tar-gz:[echo] Expanding gzipped tarfile[untar] Expanding: /appl/jboss-4.0.3SP1.tar.gz into /appl/virtuo[untar] Expanding: /appl/jboss-4.0.3SP1.tar.gz into /appl/virtuoexpand-tar-bz2:expand-zip:all:[echo] Expansion complete[move] Moving 1273 files to /appl/virtuo/as...........init:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/applcopy-libs:[copy] Copying 3 files to /appl/virtuo/as/server/default/lib[copy] Copying 10 files to /appl/virtuo/lib/tp[delete] Deleting directory /appl/virtuo/jboss-4.0.3SP1...........BUILD SUCCESSFULTotal time: 34 seconds...........

If you provide an invalid location for the JBoss archive, the installer promptsagain until you provide a correct location.

Installing the directory server schemaThe installation proceeds to install the directory server schema.

Procedure1. At the prompt, enter yes to install the directory server schema.

Would you like to perform task DS_SCHEMA_INSTALL ? [yes/no] >yes

2. At the prompt, enter the LDAP passwords for the directory server users:Directory Manager and SysAdmin:Please enter the password for ’Directory Manager’,the Directory Server User [<Dirmgr01>]:Please enter the password for ’SysAdmin’,the Directory Server User [<Sysadm01>]:Directory Server "SysAdmin" user password set to "Sysadm01"


Installing Directory server schema...Performing sanity check on Directory Server schema......doneDS schema installed.

Installing the databaseThe installation proceeds to install the Tivoli Netcool Performance Managerdatabase. You must enter the required information at the prompts.

About this task

Do not interrupt the installation during database installation.

Procedure1. At the prompt, enter yes to install the Tivoli Netcool Performance Manager

database.Would you like to perform task DB_INSTALL ? [yes/no] >yes

2. At the prompts, enter your database System Identifier (SID) and the sys andsystem database user passwords. You can choose to specify a different databasecreation template. If you do, ensure that the templates name is of the format<template name>.dbt:Please enter your Database SID (8 character maximum): [vtdb]---->Found default template: /appl/virtuo/admin/oracle/conf/vtdb.dbtPlease enter the full path of the PMW database template:[/appl/virtuo/admin/oracle/conf/vtdb.dbt]---->/appl/virtuo/admin/oracle/conf/vtdb.dbtPMW database will be created using template/appl/virtuo/admin/oracle/conf/vtdb.dbtPlease enter your ADDM license type[NONE | DIAGNOSTIC | DIAGNOSTIC+TUNING ]: [NONE]---->ADDM license type is set to "NONE"You must create passwords for the sys and system database users.

Please enter a password for the sys user: [Sysdb01]---->Please enter a password for the system user: [Sysdb01]---->

Important: You must give vtdb as the database SID.

What to do next

The post installation step of creating OEM repository and console that is accessibleby a specific port might fail. To workaround this issue, see “Creating OEMrepository and console accessible by a specific port” on page 123.

Installing the database schemaThe installation proceeds to install the database schema.

Procedure

At the prompt, enter yes to install the database schema.Would you like to perform task DB_SCHEMA_INSTALL ? [yes/no] >yes--------------------------------------------------------------------Please, Enter the Virtuo Database SID: [vtdb]---->Database SID set to "vtdb"


Please, Enter the Database sys user password: [<password>]---->Database user sys password set to "<password>"Please, Enter the Database virtuo user password: [<password>]---->Database user virtuo password is set to "<password>".... Starting Database Schema ’core’Creating database schema ’core’ in SID ’vtdb’. This may take several minutes ........ Database Schema Creation finished successfully

What to do next

You might encounter the following error during the installation of databaseschema:Creating database schema ’core’ in SID ’vtdb’. This may take several minutes ...\### ERROR: Database Schema Created with errors.... Log file is located in /appl/virtuo/admin/oracle/schema/core/install_schema.logTask DB_SCHEMA_INSTALL exited with value 7. Quitting.

To resolve this issue, perform the following tasks:v Edit the following file:

/appl/virtuo/admin/oracle/schema/core/install_schema

Change the following line:LD_LIBRARY_PATH=/lib:/usr/lib

ToLD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib:/usr/lib

v Run the following command:#cd /appl#ksh pmw_install –wmcr <WMCROOT>

Database schema post-installation tasksThe installation proceeds to run post-installation tasks on the database schema.

Procedure

At the prompt, enter yes to run post-installation tasks on the schema:Would you like to perform task DB_SCHEMA_POST_INSTALL ? [yes/no] >yes--------------------------------------------------------------------Please, Enter the TNPMW Database SID: [vtdb]---->Database SID set to "vtdb"Please, Enter the SYSDBA Database user name: []---->sysDatabase user name with SYSDBA priv is set to "sys"Please, Enter the SYSDBA Database user sys password: []----><password>Database user sys password is set to "<password>"Please, Enter the Database user virtuo name: [virtuo]---->Database schema name is set to "virtuo"Please, Enter the Database user virtuo password: [<password>]---->Database user virtuo password is set to "<password>".... Starting Loading JAR Files To ’virtuo’ SchemaLoading JAR files to database schema ’virtuo’ in ’vtdb’ database...


...

...Trigger created..... Importing Stored Outline To ’virtuo’ Schema Is Completed

Installing the cronjobsThe installation proceeds to install the cronjobs. You must provide the requiredinformation when prompted. The recommended responses are shown.

Procedure

At the prompt, enter yes to install the cronjobs.Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no] >yesConfiguring core cronjobs.......

What Type of PMW System Are you Installing ?----------------------------------------------------------------------Please select the type of PMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)Database (5)Gateway (6)----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6] :Select option 1 to see all of the cronjobs on the system.Please enter the ORACLE_HOME Directory [/appl/oracle/product/11.2.0/db_1]:(Enter . if unknown)Please enter the ORACLE_BASE Directory [/appl/oracle]:(Enter . if unknown)Please enter the ORACLE_SID Parameter [vtdb]:(Enter . if unknown)Please enter the vtdb Database Archive Directory [/oradump/vtdb]:(Enter . if unknown)Please enter the Directory Server log Directory [/appl/ldap/idsslapd-idsinst/logs]:(Enter . if unknown)Please enter the PMW Log Directory [/appl/virtuo/logs]:(Enter . if unknown)Please enter the PMW Archive Logs Directory [/data/trace_archive1]:(Enter . if unknown)

What to do next

The installation continues on to install the root user and virtuo user cronjobs.

Once the cronjob installation has completed successfully, see the cronjobinstallation log output at the following location:


On completion of the cronjobs installation, the installation proceeds to install thegateways.


Installing the GatewaysThe installation proceeds to install the gateways and to deploy the gatewaypackages.

About this task

Note: The gateways do not function without the required Perl version is installed.Perl must be installed without threading enabled, and must be installed in the$WMCROOT/gways/ directory.

Procedure1. At the prompt, enter yes to deploy the gateways on the Tivoli Netcool

Performance Manager server.Would you like to perform task GATEWAYS_INSTALL ? [yes/no] >yes................................Checking packages: gwaysperl /appl/vallent-vt-gways-vallent-NA<version>.tar.gz................................Verified the following packages:* /appl/vallent-vt-gways-vallent-NA<version>.tar.gz

2. At the prompt, enter yes to deploy the packages.Do you want to deploy the packages? [yes/no] >yes

What to do next

On completion of the gateways installation, the installation proceeds to install thetechnology packs.

Installing the technology packsThe installation proceeds to install the technology packs. To install technologypacks, you must install and deploy packages, initialize the system, and apply thetechnology packs.

About this task

Note: It is recommended not to interrupt the installation during technology packinstallation.

Ensure that the technology pack packages and order file (vallent-vt-techpack_order) is in the /appl directory. The order file contains a list oftechnology packs for installation and the correct order for their deployment.

Note: By default, summary definition provisioning during technology packinstallation is switched off. If summary definition provisioning during technologypack installation is required, then edit the file $WMCROOT/conf/vmm/default.properties and change the value of the following property to true:vallent.vmm.techpack.provision.summaries.

Procedure1. At the prompt, enter yes to install the technology packs now.

Would you like to perform task TECHPACKS_INSTALL ? [yes/no] >yes................Techpack install order file found in /applChecking packages: vallent-vt-Neutral_Core_GOM vallent-vt-


................Verified the following packages:* /appl/vallent-vt-Neutral_Core_GOM-1.0.tar.gz............

2. At the prompt, enter yes to deploy the packages.Do you want to deploy the packages? [yes/no] >yes InstallingNeutral_Core_GOM (1.0) ... ok............Ericsson_UMTS_UTRAN (1.0) ... okAll packages installed successfullyDetails in pmw_install.log

You might notice the following error:Waiting for appserver...Tue Apr 1 16:20:13 IST 2014: as is at state exec. Waiting for state STARTEDTue Apr 1 16:20:33 IST 2014: as is at state unknown. Waiting for state STARTEDTue Apr 1 16:20:45 IST 2014: as is at state unknown. Waiting for state STARTEDTue Apr 1 16:20:59 IST 2014: as is at state unknown. Waiting for state STARTED

To resolve this issue, follow these steps:v Restart the sap, sapmgr and sapmon services. If you have any problem in

restarting the services, check the <WMCROOT>/var/pid file for these processesand kill them.

v If the problem persists, check the error log in <WMCROOT>/logs/sapmon/sapmon-server.log and <WMCROOT>/logs/sapmgr/sapmgr-server.log and fix it.

3. At the prompt, enter yes to initialize the system.Would you like to perform task SYSINIT ? [yes/no] >yes..............

4. At the prompt, enter yes to apply the technology packs.Would you like to perform task TECHPACK_ADMIN ? [yes/no] >yesBuildfile: /appl/virtuo/admin/techpacks/build.xml..............[wmcInit] 13:03:09,320 [main] DEBUG logging - Created Logging Directory :/appl/ virtuo/logs/vmm[applyTechPacks] About to install modules. View logs for installation results.

5. For each technology pack you are applying, the techpack_admin tool looks inthe conf/vmm directory for a table space mapping properties file specific to thattechnology pack.Table mappings are used to assign technology pack tables optimal table spaces.The file name consists of:tablespace_" + techpack_dir + "_" + release_version + ".properties"

For example: tablespace_Ericsson_UMTS_UTRAN_1.0.properties

Note: techpack_dir is the technology pack directory name underadmin/techpacks, for example Ericsson_UMTS_UTRAN, and not the technologypack name.If a properties file exists, it is loaded and validated:Using custom tablespace settings from file/appl/virtuo/conf/vmm/ tablespace_Ericsson_UMTS_UTRAN_1.0.propertiesfor techpack Ericsson UMTS UTRAN

Example parameters that are to be set in the properties file are as follows:v ERI_AAL2_PATH_VCC_TP_MBH, TRAFFIC_MEDIUMv ERI_RADIO_LINK_STATE_MBH,TRAFFIC_JUMBO


The techpack_admin tool maps each table name to a table space by matchingagainst patterns in the mappings file. It logs the warning messages todocument the table space that is used to create each table, for example:Creating table ERI_AAL2_PATH_VCC_TP_MBH in user defined tablespace

TRAFFIC_MEDIUM

Or;Creating table ERI_RADIO_LINK_STATE_MBH in default tablespace TRAFFIC_JUMBO

If the file is found to contain invalid syntax, the following error is returned andthe installation fails:Syntax error in tablespace properties file/appl/virtuo/conf/vmm/tablespace_Ericsson_UMTS_UTRAN_1.0.properties

If no file is found or if the file is not readable, you must confirm that you wantto proceed with the default table space configuration, for example:

Note: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Ericsson_UMTS_UTRAN_1.0.properties does notexist!

Enter y to use default table space settings. If you enter N the installation failsand no technology packs are applied.

6. If the specific or default table space settings are applied successfully, theinstallation continues:..............[applyTechPacks] All modules installed successfully.[delete] Deleting: /appl/virtuo/admin/techpacks/new_techpacks[echo] Analyzing Tech Pack tables ...[wsqlplus] Reading /appl/virtuo/admin/techpacks/analyze/vmm_analyze.pks..............[wsqlplus] Package dropped.[wsqlplus] Commit complete.[echo] Analyze completeBUILD SUCCESSFULTotal time: 40 minutes 18 seconds

Encrypting passwordsThe installation proceeds to encrypt all stored Tivoli Netcool Performance Managersystem passwords.

About this task

The installation prints an individual message for each file that is encrypted.

Procedure

At the prompt, enter yes to encode the system passwords.Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yesReplacing all passwords with encoded passwords...Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.propertiesEncoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties.NEncoding values in /appl/virtuo/conf/externalreporting/default.propertiesEncoding values in /appl/virtuo/conf/externalreporting/default.properties.NEncoding values in /appl/virtuo/conf/as/as-default.properties.NEncoding values in /appl/virtuo/conf/as/as-default.properties.BACKUPEncoding values in /appl/virtuo/conf/as/as-default.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.BACKUPEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.NEncoding values in /appl/virtuo/conf/ldap/default.properties


Encoding values in /appl/virtuo/conf/ldap/default.properties.NEncoding values in /appl/virtuo/conf/ldap/default.properties.BACKUPPasswords may also be stored in /appl/virtuo/admin/logs/pmw_install.log,so it should be removed when not needed anymore.

What to do next

The installation is now complete. To configure your Tivoli Netcool PerformanceManager system, see Chapter 11, “Postinstallation tasks,” on page 97.

Installing a distributed systemDetails the steps on installing a distributed system.

You can distribute Tivoli Netcool Performance Manager across a number of serversby using the interactive installation scripts that are provided.

Running an interactive installationSteps to start an interactive installation for a distributed system.

To install a distributed system, run the pmw_install script on each individualserver to install the required components. Enter information as required by theinstallation scripts. You must install the servers (or components on shared servers)in the following order:v Database serverv Directory serverv Application server (includes gateways and technology packs if applicable)v Loader serverv Gateway server (if installed separately)v Technology packs (if installed separately)

Installing a database serverThis section details the installation of the database server.

About this task

Interactive installation of a database server for a distributed system.

Procedure1. To install a database server, place all of the Tivoli Netcool Performance

Manager software packages in the /appl directory of the database server.2. Run the following as user root:

# cd /appl# ksh pmw_install -wmcr <WMCROOT> [ -a ]

<WMCROOT> is the location where you want to install Tivoli Netcool PerformanceManager. The default installation directory is: /appl/virtuo.


The –a option is used when a different type of Tivoli Netcool PerformanceManager server is to be installed “on top” of an existing one, for example, aLoader component on top of a previously installed application server.

3. Read and accept the license agreement and the following menu is displayed:What Type of System Are you Installing?

1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit PMW Install---->---->

4. Select option 5, Database Components only.5. At the prompt, enter yes to deploy the packages.

Do you want to deploy the packages? [yes/no] >yes

Configuring the databaseThis section details the configuration of the database.

About this task

The installation proceeds to configure the core software.

Procedure1. Verify the Environment Settings.

Please, Verify Environment Settings1. Accept Variable Values below2. Reset Variables to Default values3. Change WMCHOST=<server_name>..........................

The installation lists the default values of Tivoli Netcool Performance Managerenvironment variables. These variables set server hostnames and various TCPport numbers and will vary from location to location. You can accept thedefault values, restore values to their default settings or change individualvalues.

Important: It is extremely important that you set each of these environmentvariables to the correct value.

2. Select option 3 and change the value of WMCHOST to the hostname of theapplication server.

3. Change any other values that you want to change from the default values.4. When you are satisfied that the environment variable values are correct, accept

the values and proceed.

Installing the databaseDetails the installation of the database.

About this task

Do not interrupt the installation during database installation.


Procedure1. At the prompt, enter yes to install the database.

Would you like to perform task DB_INSTALL ? [yes/no] >yes

2. At the prompts, enter your database System Identifier (SID), ADDM licensetype, and system passwords. You can choose to specify a different databasecreation template. If you do, ensure that the template's name is of the format<template name>.dbt:Please enter your Database SID (8 character maximum): [vtdb]---->Found default template: /appl/virtuo/admin/oracle/conf/vtdb.dbtPlease enter the full path of the PMW databasetemplate: [/appl/virtuo/admin/oracle/conf/vtdb.dbt]---->/appl/virtuo/admin/oracle/conf/vtdb.dbtPMW database will be created usingtemplate /appl/virtuo/admin/oracle/conf/vtdb.dbtPlease enter your ADDM license type[NONE | DIAGNOSTIC | DIAGNOSTIC+TUNING ]: [NONE]---->ADDM license type is set to "NONE"You must create passwords for the sys and system database users.

Please enter a password for the sys user: [Sysdb01]---->Please enter a password for the system user: [Sysdb01]---->

Important: You must give vtdb as the database SID.

What to do next

The post installation step of creating OEM repository and console that is accessibleby a specific port might fail. To workaround this issue, see “Creating OEMrepository and console accessible by a specific port” on page 123.

Installing the database schemaDescribes the steps for installing the database schema.

About this task

The installation proceeds to install the database schema as follows.

Procedure1. At the prompt, enter yes to install the database schema:

Would you like to perform task DB_SCHEMA_INSTALL ? [yes/no] >yes

2. At the prompts, enter the database SID:Please, Enter the Virtuo Database SID:[vtdb]---->Database SID set to "vtdb"

3. At the prompt, enter the password for the database system user:Please, Enter the Database sys user password:[<password>]---->Database user sys password set to "<password>"

4. At the prompt, enter the password for the database virtuo user:Please, Enter the Database virtuo user password:[<password>]---->Database user virtuo password is set to "<password>".... Starting Database Schema ’core’Creating Database Schema ’core’ in SID ’vtdb’. This may take several minutes ......... Database Schema Creation finished successfully


What to do next

You might encounter the following error during installation of the databaseschema:Creating database schema ’core’ in SID ’vtdb’. This may take several minutes ...\### ERROR: Database Schema Created with errors.... Log file is located in /appl/virtuo/admin/oracle/schema/core/install_schema.logTask DB_SCHEMA_INSTALL exited with value 7. Quitting.

To resolve this issue, perform these tasks:v Edit the following file:

/appl/virtuo/admin/oracle/schema/core/install_schema

Change the following line:LD_LIBRARY_PATH=/lib:/usr/lib

ToLD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib:/usr/lib

v Run the following command:# cd /appl# ksh pmw_install -wmcr <WMCROOT> [-a]

Running postinstallation tasks on the database schemaSteps to run postinstallation tasks on the database schema for a distributed system.

About this task

The installation proceeds to run postinstallation tasks on the database schema asfollows.

Procedure1. At the prompt, enter yes to run postinstallation tasks on the Tivoli Netcool

Performance Manager database schema.Would you like to perform task DB_SCHEMA_POST_INSTALL ? [yes/no] >yes

2. At the prompt, enter the database SID:Please, Enter the TNPMW Database SID: [vtdb]---->Database SID set to "vtdb"

3. At the prompt, enter the name of the database system user:Please, Enter the SYSDBA Database user name: [sys]---->Database user name with SYSDBA priv is set to "sys"

4. At the prompt, enter the password for the database system user:Please, Enter the SYSDBA Database user sys password: [<password>]---->Database user sys as sysdba password is set to "[<password>]"

5. At the prompt, enter the name of the database virtuo user:Please, Enter the Database user virtuo name:[<virtuo>]---->Database schema name is set to "virtuo"

6. At the prompt, enter the password for the database virtuo user:Please, Enter the Database user virtuo password:[<password>]---->Database user virtuo password is set to "<password>".... Starting Loading JAR Files To ’virtuo’ SchemaLoading JAR files to database schema ’virtuo’ in ’vtdb’ database...|.... Loading JAR Files To ’virtuo’ Schema Is Completed


.... Starting Importing Stored Outline To ’virtuo’ SchemaImporting outline to database schema ’virtuo’ in ’vtdb’ database....... Importing Stored Outline To ’virtuo’ Schema Is Completed

Installing the cronjobsThe installation proceeds to install the cronjobs.

About this task

To install the cronjobs, provide the required information when prompted. Therecommended responses are shown.

Note: The prompts that are displayed can vary depending on your installation.

Procedure

At the prompt, enter yes to install the cronjobs.Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no] >yesWhat Type of PMW System Are you Installing ?-----------------------------------------------------------------------Please select the type of PMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)Database (5)Gateway (6)-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6] :5Server type selected: DBPlease enter the ORACLE_HOME Directory [/appl/oracle/product/11.2.0/db_1]:(Enter . if unknown)Please enter the ORACLE_BASE Directory [/appl/oracle]:(Enter . if unknown)Please enter the ORACLE_SID Parameter [vtdb]:(Enter . if unknown)Please enter the vtdb Database Archive Directory [/oradump/vtdb]:(Enter . if unknown)



About this task


Procedure

At the prompt, enter yes to encode the system passwords.Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yesReplacing all passwords with encoded passwords...Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.propertiesEncoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties.NEncoding values in /appl/virtuo/conf/externalreporting/default.propertiesEncoding values in /appl/virtuo/conf/externalreporting/default.properties.NEncoding values in /appl/virtuo/conf/as/as-default.properties.N


Encoding values in /appl/virtuo/conf/as/as-default.properties.BACKUPEncoding values in /appl/virtuo/conf/as/as-default.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.BACKUPEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.NEncoding values in /appl/virtuo/conf/ldap/default.propertiesEncoding values in /appl/virtuo/conf/ldap/default.properties.NEncoding values in /appl/virtuo/conf/ldap/default.properties.BACKUPPasswords may also be stored in /appl/virtuo/admin/logs/pmw_install.log,so it should be removed when not needed anymore.

What to do next

The installation is now complete. To configure your Tivoli Netcool PerformanceManager system, see Chapter 11, “Postinstallation tasks,” on page 97.

Installing a separate directory serverA directory server can be installed separately from the application server. Ensurethat the directory server schema is installed on the directory server.

About this task

You can separate the directory server from the application server by using thefollowing method:v Install the directory server packages and configure the directory server schema

on the directory server by using the pmw_install script, as described in thisprocedure. Enter extra information at the prompts, such as the locations of theapplication and database servers.


/appl directory of the directory server.2. Run the following as user root:

# cd /appl# ksh pmw_install -wmcr <WMCROOT> [-a]

<WMCROOT> is the location where you want to install Tivoli Netcool PerformanceManager. The default installation directory is /appl/virtuo.The –a option is used in a distributed installation scenario, where a differenttype of Tivoli Netcool Performance Manager server is to be installed “on top”of an existing one, for example, a Loader server on top of a previously installedapplication server.


1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit PMW Install---->

4. Select option 4, Directory Server Components only.5. At the prompt, enter yes to deploy the packages.









Installing the directory server schemaThe following section details the directory server schema installation.

About this task

The installation proceeds to install the directory server schema.

Procedure1. At the prompt, enter yes to install the directory server schema.


2. At the prompt, enter the LDAP password for the directory server userDirectory Manager:Please enter the password for ’Directory Manager’,the Directory Server User [<Dirmgr01>]:


3. At the prompt, enter the LDAP password for the directory server userSysAdmin:Please enter the password for ’SysAdmin’,the Directory Server User [<password>]:

4. At the prompt, enter the application server host name:Please enter the TNPMW appserver hostname:

5. At the prompt, enter the database server host name:Please enter the database server hostname:

(If the installation cannot find IP addresses for the application server anddatabase server, you must provide the IP addresses).

6. At the prompt, enter the LDAP password for the directory server user System:Please enter the password for 'System’,the Directory Server User [<password>]:

Installing the cronjobsThis section describes the steps to install the cronjobs.

About this task

The installation proceeds to install the cronjobs. To install the cronjobs, provide therequired information when prompted. The recommended responses are shownbelow.

Procedure

At the prompt, enter yes to install the cronjobs.Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no] >yes-----------------------------------------------------------------------Please select the type of TNPMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)Database (5)Gateway (6)-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6] : 4Please enter the Directory Server log Directory [/appl/ldap/idsslapd-idsinst/logs]:(Enter . if unknown)

What to do next


Once the cronjob installation has completed successfully, see the cronjobinstallation log output at the following location:


Encrypting the passwordsThe installation proceeds to encrypt all stored Tivoli Netcool Performance Managersystem passwords.

About this task



Procedure

At the prompt, enter yes to encode the system passwords.Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yesReplacing all passwords with encoded passwords......Passwords may also be stored in/appl/virtuo/admin/logs/pmw_install.log,so it should be removed when not needed anymore.

Installing the Application ServerDetails the steps to install the application server.

About this task

The installation proceeds to install the application server for the Tivoli NetcoolPerformance Manager.


/appl directory of the server.2. Run the following command as user root:


<WMCROOT> is the location in which you want to install Tivoli NetcoolPerformance Manager. The default installation directory is: /appl/virtuo.The –a option is used in a distributed installation scenario, where a differenttype of Tivoli Netcool Performance Manager system is to be installed “on top”of an existing one, for example, a Loader system on top of a previouslyinstalled application server.

3. Read and accept the license agreement and the following menu is displayed:What Type of System Are you Installing ?

1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit PMW Install---->

4. Select option 2, Application Components only.5. At the prompt, enter yes to deploy the packages.


6. Verify the correct values for the following variables:WMCHOST The hostname of the application serverVTDBHOST The hostname of the database serverLDAPHOST The hostname of the LDAP server

The installation proceeds to configure the core software.Please, Verify Environment Settings1. Accept Variable Values below2. Reset Variables to Default values3. Change WMCHOST=<server_name>


4. Change VTDBHOST=<server_name>5. Change LDAPHOST=<server_name>..........................

The installation lists the default values of Tivoli Netcool Performance Managerenvironment variables. These variables set server host names and various TCPport numbers vary from location to location. Accept the default values, restorevalues to their default settings, or change individual values.

Important: Set each of these environment variables to the correct value.7. Select option 4 and change the value of VTDBHOST to the host name of the

database server.8. Change any other values that you want to change from the default values.9. When you are satisfied that the environment variable values are correct, accept









Installing the directory server schemaDescribes the steps that are required to install the directory server schema.

About this task

The installation proceeds to install the directory server schema.

Note: If you have already configured the Directory server schema by using theprocedure in “Installing a separate directory server” on page 70, then answer no atthe prompt.

Procedure1. At the prompt, enter yes to install the directory server schema:


2. At the prompts, enter the LDAP passwords for the directory server users:Directory Manager, SysAdmin, and System:Please enter the password for ’Directory Manager’,

the Directory Server User [<password>]:

Please enter the password for ’SysAdmin’,


Please enter the password for 'System',


Installing the cronjobsDescribes the steps to install the cronjobs.

About this task

The installation proceeds to install the cronjobs. To install the cronjobs, provide therequired information when prompted. The recommended responses are shown asfollows.

Procedure1. At the prompt, enter yes to install the cronjobs. You see the following

information:

What Type of PMW System Are you Installing ?-----------------------------------------------------------------------Please select the type of PMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)Database (5)Gateway (6)-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6] :(Enter . if unknown)

2. Enter 2.


Server type selected: APPLPlease enter the Directory Server log Directory [/appl/ldap/idsslapd-idsinst/logs]:(Enter . if unknown)

Please enter the PMW Log Directory [/appl/virtuo/logs]:(Enter . if unknown)

Please enter the PMW Archive Logs Directory [/data/trace_archive1]:(Enter . if unknown)


Installing the GatewaysDescribes the Gateways installation procedure.

About this task

The Tivoli Netcool Performance Manager are installed in $WMCROOT/gways. Thegateways installation package must be placed in the same directory as the coreTivoli Netcool Performance Manager packages. The gateways installation packagefile is: gways-gateway-framework-<version>.tar.gz.

Procedure1. At the prompt, enter yes to deploy the gateways on the Tivoli Netcool

Performance Manager server:Would you like to perform task GATEWAYS_INSTALL ? [yes/no] > yes................................Checking packages: gwaysperl /appl/vallent-vt-gways-vallent-NA<version>.tar.gz................................Verified the following packages:* /appl/vallent-vt-gways-vallent-NA<version>.tar.gz

2. At the prompt, enter yes to deploy the packages:Do you want to deploy the packages? [yes/no] > yesInstallinggways-vallent (NA<version>) ... okAll packages installed successfullySee $WMCROOT/admin/logs/pmw_install.log log file for installation errors.

What to do next

On completion of the gateways installation, the installation proceeds to install thetechnology packs.

Installing the technology packsThe installation proceeds to install the technology packs. To install technologypacks, you must install and deploy packages, initialize the system, and apply thetechnology packs.

About this task

Note: It is recommended not to interrupt the installation during technology packinstallation.


Ensure that the technology pack packages and order file (vallent-vt-techpack_order) is in the /appl directory. The order file contains a list oftechnology packs for installation and the correct order for their deployment.

Note: By default, summary definition provisioning during technology packinstallation is switched off. If summary definition provisioning during technologypack installation is required, then edit the file $WMCROOT/conf/vmm/default.properties and change the value of the following property to true:vallent.vmm.techpack.provision.summaries.

Procedure1. At the prompt, enter yes to install the technology packs now.

Would you like to perform task TECHPACKS_INSTALL ? [yes/no] >yes................Techpack install order file found in /applChecking packages: vallent-vt-Neutral_Core_GOM vallent-vt-................Verified the following packages:* /appl/vallent-vt-Neutral_Core_GOM-1.0.tar.gz............

2. At the prompt, enter yes to deploy the packages.Do you want to deploy the packages? [yes/no] >yes InstallingNeutral_Core_GOM (1.0) ... ok............Ericsson_UMTS_UTRAN (1.0) ... okAll packages installed successfullyDetails in pmw_install.log

You might notice the following error:Waiting for appserver...Tue Apr 1 16:20:13 IST 2014: as is at state exec. Waiting for state STARTEDTue Apr 1 16:20:33 IST 2014: as is at state unknown. Waiting for state STARTEDTue Apr 1 16:20:45 IST 2014: as is at state unknown. Waiting for state STARTEDTue Apr 1 16:20:59 IST 2014: as is at state unknown. Waiting for state STARTED

To resolve this issue, follow these steps:v Restart the sap, sapmgr and sapmon services. If you have any problem in

restarting the services, check the <WMCROOT>/var/pid file for these processesand kill them.

v If the problem persists, check the error log in <WMCROOT>/logs/sapmon/sapmon-server.log and <WMCROOT>/logs/sapmgr/sapmgr-server.log and fix it.

3. At the prompt, enter yes to initialize the system.Would you like to perform task SYSINIT ? [yes/no] >yes..............

4. At the prompt, enter yes to apply the technology packs.Would you like to perform task TECHPACK_ADMIN ? [yes/no] >yesBuildfile: /appl/virtuo/admin/techpacks/build.xml..............[wmcInit] 13:03:09,320 [main] DEBUG logging - Created Logging Directory :/appl/ virtuo/logs/vmm[applyTechPacks] About to install modules. View logs for installation results.

5. For each technology pack you are applying, the techpack_admin tool looks inthe conf/vmm directory for a table space mapping properties file specific to thattechnology pack.Table mappings are used to assign technology pack tables optimal table spaces.The file name consists of:


tablespace_" + techpack_dir + "_" + release_version + ".properties"

For example: tablespace_Ericsson_UMTS_UTRAN_1.0.properties

Note: techpack_dir is the technology pack directory name underadmin/techpacks, for example Ericsson_UMTS_UTRAN, and not the technologypack name.If a properties file exists, it is loaded and validated:Using custom tablespace settings from file/appl/virtuo/conf/vmm/ tablespace_Ericsson_UMTS_UTRAN_1.0.propertiesfor techpack Ericsson UMTS UTRAN

Example parameters that are to be set in the properties file are as follows:v ERI_AAL2_PATH_VCC_TP_MBH, TRAFFIC_MEDIUMv ERI_RADIO_LINK_STATE_MBH,TRAFFIC_JUMBOThe techpack_admin tool maps each table name to a table space by matchingagainst patterns in the mappings file. It logs the warning messages todocument the table space that is used to create each table, for example:Creating table ERI_AAL2_PATH_VCC_TP_MBH in user defined tablespace

TRAFFIC_MEDIUM

Or;Creating table ERI_RADIO_LINK_STATE_MBH in default tablespace TRAFFIC_JUMBO

If the file is found to contain invalid syntax, the following error is returned andthe installation fails:Syntax error in tablespace properties file/appl/virtuo/conf/vmm/tablespace_Ericsson_UMTS_UTRAN_1.0.properties

If no file is found or if the file is not readable, you must confirm that you wantto proceed with the default table space configuration, for example:

Note: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Ericsson_UMTS_UTRAN_1.0.properties does notexist!

Enter y to use default table space settings. If you enter N the installation failsand no technology packs are applied.

6. If the specific or default table space settings are applied successfully, theinstallation continues:..............[applyTechPacks] All modules installed successfully.[delete] Deleting: /appl/virtuo/admin/techpacks/new_techpacks[echo] Analyzing Tech Pack tables ...[wsqlplus] Reading /appl/virtuo/admin/techpacks/analyze/vmm_analyze.pks..............[wsqlplus] Package dropped.[wsqlplus] Commit complete.[echo] Analyze completeBUILD SUCCESSFULTotal time: 40 minutes 18 seconds


About this task



Procedure

At the prompt, enter yes to encode the system passwords.Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yesReplacing all passwords with encoded passwords...Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.propertiesEncoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties.NEncoding values in /appl/virtuo/conf/externalreporting/default.propertiesEncoding values in /appl/virtuo/conf/externalreporting/default.properties.NEncoding values in /appl/virtuo/conf/as/as-default.properties.NEncoding values in /appl/virtuo/conf/as/as-default.properties.BACKUPEncoding values in /appl/virtuo/conf/as/as-default.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.BACKUPEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.NEncoding values in /appl/virtuo/conf/ldap/default.propertiesEncoding values in /appl/virtuo/conf/ldap/default.properties.NEncoding values in /appl/virtuo/conf/ldap/default.properties.BACKUPPasswords may also be stored in /appl/virtuo/admin/logs/pmw_install.log,so it should be removed when not needed anymore.

What to do next

You must also install the loader components on the application server. See“Installing a Loader Server.” When installing the loader components, run thepmw_install script with the -a option.

Installing a Loader ServerDescribes the installation of a loader server.

About this task

Follow the steps to install a loader server.


/appl directory of the server:2. Run the following as user root:


<WMCROOT> is the location where you want to install Tivoli Netcool PerformanceManager. The default installation directory is: /appl/virtuo.The –a option is used where a different type of Tivoli Netcool PerformanceManager system is to be installed “on top” of an existing one, for example, aLoader system on top of a previously installed Application server.


1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit PMW Install---->---->

4. Select option 3, Loader Components only.


5. At the prompt, enter yes to deploy the packages:Do you want to deploy the packages? [yes/no] >yes

Configuring the loadersEnter the configuration details for the loaders.

Procedure1. Ensure that you enter the correct values for the following variables:

WMCHOST The hostname of the application serverVTDBHOST The hostname of the database serverLDRHOST The hostname of the loader server

The installation proceeds to configure the core software.Please, Verify Environment Settings..........................1. Accept Variable Values below2. Reset Variables to Default values3. Change LDRHOST=<server_name>4. Change WMCHOST=<server_name>5. Change VTDBHOST=<server_name>

The installation lists the default values of Tivoli Netcool Performance Managerenvironment variables. These variables set server host names and various TCPport numbers vary from location to location. Accept the default values, restorevalues to their default settings, or change individual values.

Important: Set each of these environment variables to the correct value.2. Select option 4 and change the value of WMCHOST to the host name of the

application server.3. Select option 5 and change the value of VTDBHOST to the host name of the

database server.4. Change any other values that you want to change from the default values.5. When you are satisfied that the environment variable values are correct, accept


Installing the cronjobsThe installation proceeds to install the cronjobs.

About this task

To install the cronjobs, provide the required information when prompted. Therecommended responses are shown.

Procedure1. At the prompt, enter yes to install the cronjobs.

What Type of PMW System Are you Installing ?-----------------------------------------------------------------------Please select the type of PMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)Database (5)Gateway (6)----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6] :

2. Enter 3 to install the cronjobs.


What to do next


Once the cronjob installation is completed successfully, see the cronjob installationlog output at the following location:


Encrypting the passwordsThe installation proceeds to encrypt all stored Tivoli Netcool Performance Managersystem passwords.

About this task


Procedure

At the prompt, enter yes to encode the system passwords:Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yesReplacing all passwords with encoded passwords...Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.propertiesEncoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties.NEncoding values in /appl/virtuo/conf/externalreporting/default.propertiesEncoding values in /appl/virtuo/conf/externalreporting/default.properties.NEncoding values in /appl/virtuo/conf/as/as-default.properties.NEncoding values in /appl/virtuo/conf/as/as-default.properties.BACKUPEncoding values in /appl/virtuo/conf/as/as-default.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.BACKUPEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.NEncoding values in /appl/virtuo/conf/ldap/default.propertiesEncoding values in /appl/virtuo/conf/ldap/default.properties.NEncoding values in /appl/virtuo/conf/ldap/default.properties.BACKUPPasswords may also be stored in /appl/virtuo/admin/logs/pmw_install.log,so it should be removed when not needed anymore.

What to do next

Note: For instructions on how to proceed after the loader software is installed onthe new server, see “Creating a Loader on a distributed server” on page 95

Installing the Gateways separatelyDescribes separate Gateways installation procedure.

About this task

You can install the gateways separately from a core installation. The gateways areinstalled in $WMCROOT/gways. Place the gateways installation package in the samedirectory as the core Tivoli Netcool Performance Manager packages. Therecommended location is /appl.

Note:

To install the gateways, copy the EPM packages to a directory of your choice. Inthe following example, the /appl directory is used.


Procedure1. Run the following commands as user virtuo:

cd /appl/virtuo/admin/common/install/scripts./deploy_gateways -pkgdir /appl

The deploy_gateways script searches the location that you specify for files ofthe form gways-gateway-framework-*.tar.gz. If you do not specify a directory,it searches in the current directory. If no file names that match this pattern arefound, it looks for files that match the pattern vallent-vt-gway*.tar.gz.

Note: If you want to install gateways other than the standard ones, rundeploy_gateways as follows:./deploy_gateways -pkgdir /appl -gateways <gw1>,<gw2>,...

Where <gw1>,<gw2>,... is a comma-separated list of gateway packages.2. At the prompt, enter yes to deploy the packages.

Do you want to deploy the packages? [yes/no] > yesInstallinggways-vallent (NA9.1.2.18.01) ... okAll packages installed successfully

What to do next

For installation error messages, see the $WMCROOT/admin/logs/pmw_install.log logfile.

Applying Tivoli Netcool Performance Manager 1.4.1 patchYou must apply the 1.4.1 patch after you install Tivoli Netcool PerformanceManager 1.4 package from software distribution.

Installing Tivoli Netcool Performance Manager 1.4.1 patchAfter you apply the 1.4.1 patch, all other Tivoli Netcool Performance Manager 1.4post GA fix packs are also applied.

Before you begin

Run these steps before you start installing the Tivoli Netcool Performance Manager1.4.1 patch:1. Ensure that the Partition Maintenance process is not running. As user virtuo,

run the following commands:kshschedule_admin -list all

Check for the jobs that are named as pm_* in JOBS RUNNING section. Forexample, pm_weekly, pm_monthly, pm_daily.

2. Wait until all the pm jobs are complete and you do not see any PartitionMaintenance jobs reported by schedule_admin tool.

3. Also, ensure that no zombie Partition Maintenance processes exist. As uservirtuo, run the following command from sqlplus that is connected to a PMWdatabase:SELECT sid, serial# FROM v$session WHERE LOWER(module)=’partmaint’;

4. Stop the sessions that are returned by the SQL statement.5. All services apart from the database must be stopped by using the following

command:


sap stop

About this task

Install Tivoli Netcool Performance Manager 1.4.1 patch on the same server whereyou installed the JBoss application server.

Procedure1. As user virtuo set WMCROOT directory by using the following commands:

cd /applkshexport WMCROOT=/appl/virtuo

2. Run the deploy_patch command as follows:$WMCROOT/admin/common/install/scripts/deploy_patch-wmcr $WMCROOT -patch vallent-vt-patch-P1410110-TNPM1.4.1.0.110.tar.gz

3. Enter 1 to proceed with the installation.4. Enter the location of the patch vallent-vt-patch-P1410110-

TNPM1.4.1.0.110.tar.gz./appl

5. View pmw_install.log file for patch installation logs by running the followingcommands:cd $WMCROOT/admin/support/bin./post-install_TNPM141.ksh

6. Enter Oracle database sys password when you are prompted: <sys_password>

What to do next

After the installation is complete, do the following steps:v Back up your existing /appl/virtuo/jre folder.v Locate and copy the jre folder that is bundled with the Tivoli Netcool

Performance Manager core installer from /appl/jre to /appl/virtuo/jre.v Restart the processes by using the following command:

sap start

Uninstalling Tivoli Netcool Performance Manager 1.4.1 patchUninstall the Tivoli Netcool Performance Manager 1.4.1 patch.

Before you begin1. All services apart from the database must be stopped by using the following

command:sap stop

2. Verify that the services are not running by using the following command:sap disp

Procedure1. As user virtuo set WMCROOT directory by using the following commands:

kshexport WMCROOT=/appl/virtuo

2. Run the patch remove script as follows:cd $WMCROOT/admin/software/core./vallent-vt-patch-P1410110.remove


3. Run the following postinstallation script as user virtuo:cd $WMCROOT/admin/support/bin./post-uninstall_TNPMW141.ksh

4. Enter Oracle database sys password when you are prompted: <sys_password>


Chapter 10. Installing the technology packs separately

Instructions to install the technology packs.

Note: In a distributed installation, install the technology packs on the applicationserver only unless otherwise indicated.

Note: It is recommended not to interrupt the installation of technology packinstallation.

You install technology packs by using the deploy_techpacks script and thetechpack_admin tool. Before you install a technology pack, ensure that the mainTivoli Netcool Performance Manager schema is installed. For more informationabout using the techpack_admin tool, see the Administering Tivoli NetcoolPerformance Manager - Wireless Component.

Note: By default, summary definition provisioning during technology packinstallation is switched off. If summary definition provisioning during technologypack installation is required, then edit the file $WMCROOT/conf/vmm/default.properties and change the value of the following property to true:vallent.vmm.techpack.provision.summaries

Starting the systemStarting the SAP application server.

About this task

Follow these steps as user virtuo to start the system:

Procedure1. Check if the application server has started:

sap disp

2. If the application server is not started, run the following command:sap start as


Setting up users and data sourcesCreate the users and data sources before you install the technology packs.

About this task

Before you install the technology packs, create the users and data sources asfollows:

Procedure1. As user virtuo, run the command:

sys_init -u sysadm -p <password> -h <fully-qualified hostname>

If the users and data sources exist on the system, you see the followingmessage. You can continue the installation.ERROR: The system is already initialized

2. Alternatively, use a web browser to open:http://<hostname>:8080/sysinit

Log in with the user ID sysadm and password to create the users and datasources.

Checking database spaceCheck the database space to ensure that the table space sizing is correct.

About this task

Check the Tivoli Netcool Performance Manager database to make sure that tablespace sizing is correct, as per the customer sizing response file. All table spacesshould be the correct size for your network.

Before you install the technology packs, there should be at least 50% free space ineach table space.

To check table spaces using Oracle Enterprise Manage Console (or another tool),perform the following:

Procedure1. Connect to the database as user virtuo.2. Select Storage on Enterprise Manage Console; select table spaces.3. Check the Used % column (last column on right) and confirm that none have

exceeded 50%. If they have, add a new database file by: For example,WM_CLIENT.a. Double-click table space.b. Copy a database file entry that exists and pasting it into a new row.c. Modify the name to make it unique.


Installing the technology pack: step 1The first installation process for the technology pack.

Before you begin

Run the following commands as user virtuo:sapmon startsapmgr startsap start as

About this task

Follow the steps to install the technology pack:

Procedure1. As user virtuo copy the technology pack Enterprise Performance Management

(EPM) packages. For example, copy the vallent-vt-<techpack name1>.gz,vallent-vt-<techpack name2>.gz and the order file that is calledvallent-vt-techpack_order into the $WMCROOT/admin/techpacks/packagesdirectory. The order file contains a list of technology packs for installation andthe correct order for their deployment. For example:vallent-vt-Neutral_Core_GOMvallent-vt-Neutral_GSM_BSS_NSS_GOMvallent-vt-Neutral_GPRS_UMTS_CN_GOMvallent-vt-Neutral_GPRS_BSS_GOMvallent-vt-Neutral_UMTS_UTRAN_GOMvallent-vt-NOK_GOMletvallent-vt-GSM_Nokia_BSS_RG20

2. Install the technology packs as user virtuo as follows:cd /appl/virtuo/admin/common/install/scripts./deploy_techpacks -wmcr $WMCROOT -pkgdir $WMCROOT/admin/techpacks/packages

The installation searches the directory that is specified by -pkgdir for thevallent-vt-techpack_order file. The script uses this list and attempt to installeach of the technology packs in turn. The installation looks for the technologypack packages in the same directory as the vallent-vt-techpack_order file.To install a custom set of technology packs, run deploy_techpacks as follows:./deploy_techpacks -wmcr $WMCROOT -pkgdir $WMCROOT/admin/techpacks/packages -techpacks <techpack1>,<techpack2>,...

<techpack1>,<techpack2>,... is a comma-separated list of technology packpackages. The release notes for your distribution states if this step is necessary.The following output is displayed:Techpack install order file found in /appl/virtuo/admin/techpacks/packagesChecking packages: <techpacks>Verified the following packages:<package 1><package 2>...Do you want to deploy the packages? [yes/no] >

3. Enter yes to confirm the package deployment.

What to do next

After the installation is complete, check the following points:v The technology packs are installed in $WMCROOT/admin/techpacks directory.

Chapter 10. Installing the technology packs separately 87

v The generated file $WMCROOT/admin/techpacks/new_techpacks contains thecomplete list of installed technology packs in the correct order.

v If any errors occurred during the installation. See the $WMCROOT/admin/logs/pmw_install.log file for any error messages.

Installing the technology pack: step 2The second installation process for the technology pack.

Before you begin

Run the $WMCROOT/bin/techpack_admin script to configure the new technologypacks.

The techpack_admin script looks for a file that is called new_techpacks generatedduring “Installing the technology pack: step 1” on page 87. This file contains a listof technology packs to install in the database by using the techpack_admin script.

About this task

Follow the steps to install the technology pack:

Procedure

To apply the technology packs, as user virtuo, run the following command:techpack_admin -a

The techpack_admin -a script causes a number of changes that you must verify:v Creation of technology pack traffic tables in the databasev Loading of the technology pack loadmapsv Configuration of the new loadersv Service Application Server (SAP) configuration for new loaders

Performing postinstallation checks for the technology packs

Details the postinstallation checks for the technology packs.

About this task

To ensure that the technology packs are installed correctly, check the followingitems.

Procedure1. The technology packs are successfully installed under $WMCROOT/admin/

techpacks

2. There are no error messages in log file $WMCROOT/logs/vmm/vmm-server.log

3. The wmd_field_def table in the database is populated.4. Run this command as user virtuo:


schema_admin -checkmodel

This query determines the hierarchy that is used in reporting. If the queryreturns NULL, or if the reportable column in the output is set to N, then there isa problem. Uninstall and reinstall the technology packs.

5. Generic loader start script generated called $WMCROOT/bin/run_njloader.6. Check the database for rows that are entered in the following loadmap tables:

LC_DATASOURCELC_LOADMAPLC_RELATIONSLC_RULESETLC_LOADER_CONFIG_PROPERTIES

SOURCE_TABNAME can be null, this means that the nc table has noassociated performance tables.

7. Loader data directories created:$WMCROOT/var/loader/spool/<DSname_DSversion>/<DS_version>/$WMCROOT/var/loader/spool/<DSname_DSversion>/<DS_version>/good$WMCROOT/var/loader/spool/<DSname_DSversion>/<DS_version>/bad

8. To get information about the rulesets associated with the technology packsinstalled, enter the following query:SQL> select RULESET_ID, DESCRIPTION, TYPE from LC_RULESET;

9. Ensure that the source folder for loading files is set correctly in the loaderproperties.Run the following command as user virtuo:loader_admin -unload all_loader_properties.xml -instance ALL

A file that is called all_loader_properties.xml is created.Example content of a all_loader_properties.xml is shown:<loaderconfig><loader><name>alcgsmbss_b9</name><property><name>itm.enabled</name><value>FALSE</value></property>.....</loader><loader><name>motgsmbss_gsr80</name>....</loader></loaderconfig>

There must be a <loader> section for each installed loader. If there is not a<loader> section for each loader, then there is a problem during technologypack installation. In this case uninstall and reinstall the technology pack.Check that each <loader> section contains a datasource.folder property:<property><name>datasource.folder</name><value>/appl/virtuo/var/loader/spool/dsname_dsversion/dsversion</value></property>

The datasource name and version has white spaces and non-alphanumericcharacters removed. For example,<property> <name>datasource.folder</name> <value>/appl/virtuo/var/loader/spool/nkbss_oss31ed3/OSS3.1_ED3</value> </property>

The datasource folders do not need to exist when the technology pack isinstalled. If they do not exist, they are created by the loader on first start. Inthis case, they must to be specified in a location where the virtuo user has


permission to create them. The datasource.good and datasource.baddirectories must also be specified in a location where the virtuo user haspermission to create them. By default they are subdirectories of the datasourcefolder, and so have the correct permissions.If the datasource folder properties are not correct, update them. A fulldescription of how to update loader properties is given in the LoaderConfiguration section of the Administering Tivoli Netcool PerformanceManager - Wireless Component.The rest of the all_loader_properties.xml file can also be examined to seethat the properties are correct for the current installation. When you updateloader properties, it is better to export the properties for just the instance youwant to change by specifying the instance name when you use theloader_admin tool.

10. To get information on data sources associated with the loadmaps andtechnology packs installed, enter the following query:SQL> select DATASOURCE_NAME, DATASOURCE_VERSION from LC_DATASOURCE;

Ensure the following tasks:v The DATASOURCE_NAME and version are contained within the VALUE of the

property.v The directory that is specified in the DATASOURCE_NAME exists. For

example:DATASOURCE_NAME DATASOURCE_VERSION--------------- ------------------Nokia GSM BSS RG20Huawei LTE PCRF_UPCC V300R005C00

/appl/virtuo/var/loader/spool/nokiabss_oss31ed3/OSS3.1_ED3

v SAP property files that are created for each loader type:$WMCROOT/conf/processes/processes-load_<loader>.properties

Note: The timezone setting for a loader currently defaults to the time zone onthe installation server. Confirm that this setting is correct for the data you areloading. If necessary, change the setting by using the loader_admin tool.

Starting the SAP process monitor toolStart the Tivoli Netcool Performance Manager process management tool.

About this task

Perform the following steps to start the SAP process monitor tool.

Procedure1. Run the commands that are specified for the system, as root user:

v

/etc/rc.d/init.d/sapmgrvirtuo start

v

svcadm disable sapmgr-nasvcadm enable sapmgr-na

v

service sapmgrvirtuo --full-restart


2. Check that the application server is started and that all the configured loadersare stopped by running the following command as user virtuo:sap disp

The following output is displayed showing the application server is started andall the configured loaders are stopped:NAME STATE SINCEas STARTED 17:54:38nc_cache STARTED 17:55:07alarm_cache STARTED 17:55:13<loader> stopped -. . .. . .

Starting the Application ServerSteps to start the Application Server.

About this task

To check if the application server is started.

Procedure1. Run the following command as user virtuo:

sap disp

If the application server is started, you see output similar to the following:NAME STATE SINCEas STARTED 17:54:38nc_cache STARTED 17:55:07alarm_cache STARTED 17:55:13

2. If the application server is not started, run the following commands as uservirtuo.sap start assap disp

The application server status is shown as started.NAME STATE SINCEas STARTED 17:54:38nc_cache STARTED 17:55:07alarm_cache STARTED 17:55:13

Starting the LoadersSteps to start the Loaders.

About this task

You can now start the newly configured loaders.

Procedure1. Start the loaders as user virtuo:

$ sap start <loader name>

2. Check that the latest loaders are shown as added:$ sap dispNAME STATE SINCEas STARTED 12:15:55


nc_cache stopped 12:16:32alarm_cache stopped 12:17:48<loader> STARTED 12:15:50<loader>1 STARTED 12:15:52

3. Check the loader logs for startup issues with any of the loaders:$WMCROOT/logs/loader/*.log

Configuring multiple identical LoadersSteps to configure multiple identical Loaders.

About this task

Typically, you would configure and start more than one loader of a particular type.

The following examples illustrate how to add extra loaders of a particular type.Run commands as user virtuo unless otherwise indicated.

Procedure1. Create a loader instance by using default system properties, or by using the

properties of an existing loader instance. To create a loader instance by usingdefault properties, first use lcm_admin to check the data source name andversion of the loader you want to create:$ lcm_admin –listData Source InformationTechpack Name Version DataSource Name Version Technology Vendor----------------------------------------------------------------------Ericsson GSM BSS 1.0 Ericsson BSS R10 GSM Ericsson

2. Add a loader instance, by using the loader_admin command, giving anarbitrary name for the instance and the data source name and version from therequired technology pack:$ loader_admin –init –instance ericssconbss_r10_1 –dsname “Ericsson BSS”–dsversion R10Buildfile: /appl/virtuo/conf/loader/loader_admin.xmlinit:[initlog] 18:14:11,483 [main] WARN logging - TRCE-0022 :The name of the process is null or empty.initloader:[initloader] Initialise Loader:[initloader] Instance Name: [ericssconbss_r10_1][initloader] Datasource Name: [Ericsson BSS][initloader] Datasource Version: [R10][initloader] New properties created for [ericssconbss_r10_1][initloader] Created sap process file for [ericssconbss_r10_1][initloader] Restarted sapmgr[initloader] New instance creation completed

3. Create an instance from the properties of an existing instance:$ loader_admin –init –instance ericssconbss_r10_1 -copy ericssonbss_r10Buildfile: /appl/virtuo/conf/loader/loader_admin.xmlinit:[initlog] 18:17:27,389 [main] WARN logging - TRCE-0022 :The name of the process is null or empty.initloader:[initloader] Initialise Loader:[initloader] Instance Name: [ericssconbss_r10_1][initloader] Source instance name: [ericssonbss_r10][initloader] New properties created for [ericssconbss_r10_1][initloader] Created sap process file for [ericssconbss_r10_1]


[initloader] Restarted sapmgr[initloader] New instance creation completedBUILD SUCCESSFULTotal time: 8 seconds

4. Whichever method you use to create the new loader, use the sap dispcommand to check that it is now in the SAP process list. (Note SAP might beunavailable for a few seconds after loader_admin –init while the sapmgrprocess reinitializes):NAME STATE SINCEas STARTED Oct 23, 2008nc_cache STARTED Oct 29, 2008alarm_cache STARTED Oct 29, 2008load_ericsson bss_r10 stopped -load_ericssconbss_r10_1 stopped –

Loading dataDescribes the data loading on the loaders on the distributed systems.

Note: Distributed systems only. In a distributed installation, load data on theloader servers only.

Place data files (.lif) in the loader spool directory. Files are processed and placedin either the good or bad directory. You can configure Tivoli Netcool PerformanceManager gateways to generate .lif files in the appropriate loader directory.

For example:/appl/virtuo/var/loader/spool/<DSname_DSversion>/<DS_version>

Verifying data loadingThis procedure describes the verification process of the data loading on the loaderson the distributed systems.

About this task

Check the technology pack tables for network configuration (NC) and traffic dataloading into tables. Check if the data .lif files are processed and put in the rightdirectories.

Procedure1. Check if the Traffic tables are stored in the traffic_large table space in the

database pointed to by ORACLE_SID. For example.vtdb.2. Data .lif files must be processed and put in either the good or bad directories

under the generated loader directory for the configured loader. For example:$WMCROOT/var/loader/spool/<DSname_DSversion>/<DS_version>/good$WMCROOT/var/loader/spool/<DSname_DSversion>/<DS_version>/bad


Removing Loadmaps and Loader configurationUse this procedure if loader configuration fails or for a point release upgrade.

About this task

This procedure removes all of the loader properties files in /appl/virtuo/conf/processes/.

Important: Remove all installed technology packs before this procedure. Use thetechpack_admin -u command to uninstall technology packs. See the AdministeringTivoli Netcool Performance Manager - Wireless Component for information aboutuninstalling technology packs.

To perform a reinstall of the loader and loadmap configuration, complete thefollowing steps.

Procedure1. Stop LCM, sapmgr, and sapmon as user root:

v

/etc/rc.d/init.d/sapvirtuo stop/etc/rc.d/init.d/sapmgrvirtuo stop/etc/rc.d/init.d/sapmonvirtuo stop

v

svcadm disable sap-nasvcadm disable sapmgr-nasvcadm disable sapmon-na

v

service sapvirtuo stopservice sapmgrvirtuo stopservice sapmonvirtuo stop

2. Remove spool directories as user virtuo.rm -rf /appl/virtuo/var/loader/spool/*

3. Delete LC_* table rows as user virtuo.SQL> delete from lc_datasource;SQL> delete from lc_loadmap;SQL> delete from lc_relations;SQL> delete from lc_ruleset;SQL> delete from lc_loader_config_properties where loader_name != ’SYSTEM’;

4. Remove SAP loader properties files as user virtuo.rm -rf /appl/virtuo/conf/processes/*load*.properties

5. Reinstall the technology packs and loaders by using the procedures that start at“Starting the system” on page 85


Creating a Loader on a distributed serverSteps to create a Loader on a distributed server.

About this task

When you install technology packs on the application server, the installationcreates the loader instances on the application server by default. To configure aseparate loader server, you must relocate these instances to the loader server.

Note: Before you can move a loader instance to another server, you must installthe loader software packages on the new server.

Ensure that the loader server is installed by using the procedure in “Installing aLoader Server” on page 79. You must also install the loader components on theapplication server. When you install the loader components, run the pmw_installscript with the -a option.

To start a loader instance on a distributed server, it is necessary to relocate the sapprocess manually. (If a new instance is required, first create the instance on theapplication server as described in “Starting the Loaders” on page 91).

To relocate the SAP process, complete the following steps on the application server.

Procedure1. If the loader instance that you want to relocate is running, stop the instance:

$ sap stop load_<loadername>

2. Edit the SAP process file for the loader:$WMCROOT/conf/processes/processes-load_<loadername>.properties.

Change the value of the host name property to the required target server:com.comnitel.process.load_<loadername>.host=<servername>

Save the file.3. Stop and restart the SAP manager. To stop the SAP manager, run the following

commands as user root:

v

/etc/rc.d/init.d/sapmgrvirtuo stop

v

svcadm disable sapmgr-nasvcs "*-na*"

Check that the SAP manager is disabled:svcs "*-na*"

v

service sapmgrvirtuo stop

4. Restart the SAP manager:

v

/etc/rc.d/init.d/sapmgrvirtuo start

v

svcadm enable sapmgr-na


v

service sapmgrvirtuo start

5. Check the loader status:sap disp -l

The loader being moved shows the new host name:NAME STATE SINCE HOST GROUP STIME PIDas STARTED Oct 23 <core_host> asgroup Oct 23 17277nc_cache STARTED Oct 29 <core_host> loadercache Oct 29 6716alarm_cache STARTED Oct 29 <core_host> loadercache Oct 29 6726load_<loadername>stopped - <target_host> Ericsson GSM - -

You can now stop and start this loader as normal by using sap start fromeither the application server or the distributed loader server.

Note: When the loader first starts on the new server, it creates its data sourcefolder on the new server.


Chapter 11. Postinstallation tasks

The postinstallation tasks that are required for the Tivoli Netcool PerformanceManager installation

Complete the following postinstallation tasks:v Provisioning Stored Busy Hours, Summaries, and Data Availability.v Configuring Application Server Memory (optional).v Configuring Loader Server Memory (recommended).v Checking the Time Zone Settings for the Report Scheduler.v Changing the Default Client Ports.v Integrating IBM Tivoli Monitoring (optional).

Provisioning stored Busy Hours, Summaries, and Data AvailabilityDetails the provisioning of stored Busy Hours, Summaries, and Data Availability.

A number of technology packs contain Stored Busy Hour (SBH), Summary, andData Availability definitions. You must provision these definitions before you canuse them.

Stored Busy Hours definitionsIf a technology pack contains SBH definitions, these definitions are contained in anXML file.

Location

The SBH definition file for each technology pack is:

<TP_ROOT>/busyhours/BusyHourInstance.xmlwhere <TP_ROOT> is $WMCROOT/admin/techpacks/<techpack_name>/<techpack_version>

You can provision SBH definitions by using the sbh_admin tool to import an SBHdefinition file. The sbh_admin tool is in:$WMCROOT/bin

You can run the sbh_admin tool from any directory as user virtuo.

Usagesbh_admin -i [-f <file> | -p <directory>] -m [overwrite | ignore | fail]-i Import-f Import the Stored Busy Hour Definition from <file>.-p Import all busy hour definitions stored in <directory>.


All files with an .xml suffix are imported.-m mode:overwrite: If the definition already exists, update it.ignore: If the definition already exists, do not update it and do not fail the

importfail: If the definition already exists, fail the import.

sbh_admin -i -f BusyHourInstance.xml -m overwrite

Import the SBHs defined in BusyHourInstance.xml, overwriting the definitions ifthey exist.sbh_admin -i -p indir -m overwrite

If the two files SBH1.xml and SBH2.xml exist in the indir directory, the definitionsin SBH1.xml and SBH2.xml are imported.

Summary definitionsIf a technology pack contains Summary definitions, these definitions are containedin an XML file.

Location

The Summary definition file for each technology pack is:<TP_ROOT>/summaries/SummaryInstance.xml

You can provision summary definitions by using the summary_admin tool to createeach definition in a definition file. The summary_admin tool is in:$WMCROOT/bin

You can run the summary_admin tool from any directory as user virtuo.

Note: If Summary definitions are provided but not provisioned, an attempt to usethese definitions result in an error. For example, opening a report template thatuses KPIs with Summary definitions specified in a technology pack'sSummaryInstance.xml.

Usage

The full usage of the tool is not documented here. Only usage relevant toprovisioning a definition file is shown.summary_admin -c -f <file>-c Create-f Create Summary Definitions from <file>.

summary_admin -c -f SummaryInstance.xml

Create the Summaries that are defined in SummaryInstance.xml.

Data Availability definitionsIf a technology pack contains Data Availability definitions, these definitions arecontained in an XML file.

Location

This file contains information about the technology pack, and a list of blocks ofdata that is loaded for that technology pack.


If the value of the block is set to true, that is, <block name="ATMUSAGE">true</block>, then after the file is loaded the loader starts producing Data Availability(DA) statistics every time it loads a block of ATMUSAGE data.

Note: This file is intended to be user-customized: you can switch blocks on or off.It is important to realize that blocks, which are tracked take twice as long to loadas blocks that are not. Only high-level entities (MSC, BSC, ...) must be tracked, butnot low-level entities (TRX, ...).

The Data Availability definition file for each technology pack is:<TP_ROOT>/loadmaps/dataavailability/dataavailability<techpack_name>.xml

You can provision data availability definitions by using the lcm_admin tool. Thelcm_admin tool is in:$WMCROOT/bin

You can run the lcm_admin tool from any directory as user virtuo.

Usage

The full usage of the tool is not documented here. Only usage relevant toprovisioning a definition file is shown.lcm_admin -load <data_availability.xml>

lcm_admin -load dataavailability_umts_siemens_utran_umr050_1.0.0.0.xml

Configuration of the Application Server memory (Optional)On larger Tivoli Netcool Performance Manager installations, configuring Javavirtual machine (JVM) heap memory settings can improve performance and allowfor better application server usage.

You can configure the heap memory to suit the size of your system and theamount of system usage, particularly for running large reports.

To configure the heap memory, edit the jvm.args property in the$WMCROOT/conf/as/jvm-default.ini file.

The jvm.args propertyDescribes the jvm.args property for the heap memory configuration.

The jvm.args property contains the following settings:-Xms512m -Xmx512m -XX:+AggressiveHeap

-Xms<n>Describes the -Xms<n> argument.

-Xms<n> specifies the initial size of the memory allocation pool in bytes. Appendthe letter m or M to indicate megabytes, or g or G to indicate gigabytes. The defaultvalue is 1024 MB.v -Xms1024m

v -Xms1G

-Xmx<n>Describes the -Xmx<n> argument.

Chapter 11. Postinstallation tasks 99

-Xmx<n> specifies the maximum size of the memory allocation pool in bytes.Append the letter m or M to indicate megabytes, or g or G to indicate gigabytes. Thedefault value is 1024 MB.v -Xmx2048m

v -Xmx2G

-XX:+AggressiveHeapDescribes the -XX:+AggressiveHeap argument.

-XX:+AggressiveHeap is a Garbage Collection Tuning setting. The option inspectsthe server resources (size of memory and number of processors), and attempts toset various parameters to be optimal for long-running, memory allocation-intensivejobs. The physical memory on the servers must be at least 256 MB beforeAggressiveHeap can be used. The size of the initial heap is calculated based on thesize of the physical memory and attempts to make maximal use of the physicalmemory for the heap (that is, the algorithms attempt to use heaps nearly as largeas the total physical memory).

Recommended jvm.args Property settings for ApplicationServers

Describes the recommended jvm.args property settings for Application Servers.

It is highly recommended to set the same values for both –Xms and –Xmx. Table 6lists the recommended settings.

Table 6. Recommended jvm.args Property Settings for Application Servers

System Size Memory Setting

Demo -Xms512m and -Xmx512m

Small -Xms512m and -Xmx512m

Production At least -Xms2048m and -Xmx2048m (Confirm thisrecommendation with performance testing)

Complete documentation for all JVM settings is available from the Sun Javawebsite http://www.oracle.com/technetwork/java/index.html.

Configuration of Loader Server memory (Recommended)You can improve loader performance by configuring the Java virtual machine(JVM) memory settings.

You can configure each loader individually. It is recommended that you balancethe memory for loaders according to their throughput.

To configure the heap memory, edit the loader properties file for the loaderprocess.



The SAP configuration params propertyEach loader properties file contains a params property.

By default, it is of the form:com.comnitel.process.load_<instance-name>.params=<instance-name>

For example:com.comnitel.process.load_nokiabss_oss31ed3.params=nokiabss_oss31ed3

The location for a loader's properties file is:

<WMCROOT>/conf/processes/processes-load_<loader>.properties

By default, the JVM heap memory setting for loaders is 1,536 MB (1.5 GB) for bothmaximum and minimum. You can modify the default settings by providingalternate values for the initial size of the memory allocation pool as follows:com.comnitel.process.load_<instance-name>.params=<instance-name> <min> <max>

By default, the value is in bytes. Append the letter m or M to indicate megabytes,or g or G to indicate gigabytes. If you provide only one value, it becomes bothminimum and maximum. For optimal performance, it is highly recommended touse identical settings for both.

For example, enter the following to set both the minimum and maximum memoryto 2 GB:com.comnitel.process.load_nokiabss_oss31ed3.params=nokiabss_oss31ed3 2g

Note: It is only possible to set loader process settings in this way. You cannot setother SAP processes with this mechanism.

Restart sapmgr after you change a process configuration file. As user virtuo, runthe command:$ sapmgr restart

Note: This action does not restart any of the services, such as loaders or theapplication server.

When you change the configuration of a running loader, you must restart theloader process to use the new settings as follows:1. Run this command:

$ sap stop nokiabss_oss31ed3

2. Wait until the loader stops, and then run the following command:$ sap start nokiabss_oss31ed3


Recommended JVM memory size settings for Loader ServersThe amount of memory that you must allocate to each loader process depends onthe throughput and size of files that are handled by the loader.

Low-volume processes can be set with a maximum of 1 GB. High-volumeprocesses that are configured without multithreading must be set to at least 2 GB,and high-volume processes with multithreading set to at least 3 GB.

Table 7 lists the recommended settings for both maximum and minimum memory:

Table 7. Recommended JVM size settings for Loader servers

System Size Memory Setting

Demo 1 g

Small 1526 m

Production At least 2 g (Confirm this recommendationwith performance testing)

Checking the Time Zone settings for the Report SchedulerThe location to check the time zone settings.

Check that the time zone settings for the report scheduler correct in the followinglocation:

v

/etc/environment

v

/etc/default/login

v

/etc/localtime

Setting the Time ZoneIf the timezone is not set or is incorrectly set, use the tz_admin tool to set orchange the timezone.

For example:tz_admin -addcurtzr <timezone_name>

For more information on setting time zones for the report scheduler, see Timezonesupport for reporting section of the Administering Tivoli Netcool Performance Manager -Wireless Component.


Changing the default client portsThe defaults ports that are used by the Tivoli Netcool Performance Manager clientcan be changed.

The default ports that are used by the Tivoli Netcool Performance Manager clientare as follows:v HTTP server: 8080v Alarm service: 4444 (required for the alarm window)

After installation, information for these ports is stored in the two files:v $WMCROOT/conf/as/as-default.properties

v $WMCROOT/as/server/default/deploy/jbossweb-tomcat55.sar/server.xml

The conf/as/as-default.properties file contains both port values. The$WMCROOT/as/server/default/deploy/jbossweb-tomcat55.sar/server.xml filecontains the HTTP server port.

To change the default ports, update the port values in both files. After you makechanges, stop and restart the application server.

Note: For the Tivoli Netcool Performance Manager client to work, the two portsmust be open on any firewall between the server and the client PC.

Integrating IBM Tivoli MonitoringIBM Tivoli Monitoring integration is an optional feature. The Tivoli NetcoolPerformance Manager installation procedure will not automatically configure theTivoli Netcool Performance Manager Tivoli Monitoring agents.

For information on installing and configuring Tivoli Monitoring and TivoliMonitoring agents, integrating Tivoli Monitoring with Tivoli Netcool PerformanceManager and information on deploying agents to a server, see IBM TivoliMonitoring Integration. For information about the IBM Tivoli Monitoring productdocumentation, see:http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/welcome.htm

Integrating IBM Tivoli Netcool/OMINbus Web GUIIBM Tivoli Netcool/OMINbus Web GUI 8.1 integration is an optional feature. TheTivoli Netcool Performance Manager installation procedure does not automaticallyconfigure the Tivoli Netcool Performance Manager Tivoli Netcool/OMINbus WebGUI.

About this task

For more information about this integration, see Tivoli Netcool/OMNIbus Web GUIIntegration - Wireless Component.


http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/welcome.htm

http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/welcome.htm


Chapter 12. Starting Tivoli Netcool Performance Manager

Start Tivoli Netcool Performance Manager after installation.

Rebooting the serverReboot the server to ensure all the Tivoli Netcool Performance Manager processesstart automatically and correctly.

Before you begin

Before you reboot a server, stop all processes by running the command as uservirtuo:$ sap stop -f

About this task

Run the commands to reboot the server.

Procedure

To reboot the server, run the commands as user root on each of the Tivoli NetcoolPerformance Manager servers:

v

# shutdown -Fr

v

# /usr/sbin/shutdown -i6 -g0 -y

v

# shutdown -r now

Important: Distributed systems only. In a distributed system, you must reboot theTivoli Netcool Performance Manager servers in the following order: databaseserver, directory server, application server, and loader servers.


Process checks for Solaris

Run process checks to ensure that the processes are running correctly.

On Solaris 10, run this command as user root to check the status of the system:# svcs -x "application/virtuo*"

Sample output from a monolithic server.svc:/application/virtuo/database-na:global(NetworkAssure Database instance)State: online since Tue Oct 04 13:28:41 2011

See: /var/svc/log/application-virtuo-database-na:global.logImpact: None.

svc:/application/virtuo/sap-na:na (Virtuo SAP server instance na)State: online since Fri Sep 23 04:47:27 2011

See: /var/svc/log/application-virtuo-sap-na:na.logImpact: None.

svc:/application/virtuo/sapmgr-na:na (Virtuo SAP manager instance na)State: online since Fri Sep 23 04:45:13 2011

See: /var/svc/log/application-virtuo-sapmgr-na:na.logImpact: None.

svc:/application/virtuo/sapmon-na:na (Virtuo SAP monitor instance na)State: online since Fri Sep 23 04:44:56 2011

See: /var/svc/log/application-virtuo-sapmon-na:na.logImpact: None.

svc:/application/virtuo/sds-na:na (PMW sds instance na)State: online since Fri Sep 23 04:45:19 2011

See: /var/svc/log/application-virtuo-sds-na:na.logImpact: None.

svc:/application/virtuo/database-na:global (NetworkAssure Database instance)State: online since Fri Sep 23 04:42:59 2011

See: /var/svc/log/application-virtuo-database-na:global.logImpact: None.

Process checks for AIXRun process checks to ensure that the processes are running correctly.

On AIX, run the following commands to check the status ofprocesses:/etc/rc.d/init.d/dboravirtuo status/etc/rc.d/init.d/sdsna status/etc/rc.d/init.d/sapmonvirtuo status/etc/rc.d/init.d/sapmgrvirtuo status/etc/rc.d/init.d/sapvirtuo status

Sample output:# /etc/rc.d/init.d/dboravirtuo statusDatabase listener is running.Database instance vtdb is running.

# /etc/rc.d/init.d/sdsna statusSDS LDAP server is runningSDS admin server is running


# /etc/rc.d/init.d/sapmonvirtuo statussapmon process running

# /etc/rc.d/init.d/sapmgrvirtuo statussapmgr process running

# /etc/rc.d/init.d/sapvirtuo status

............

............

NAME STATE SINCEas STARTED Oct 08, 2010asd STARTED Oct 08, 2010nc_cache STARTED Oct 08, 2010alarm_cache STARTED Oct 08, 2010load_erics_r10 STARTED Oct 08, 2010load_nok_oss31ed3 STARTED Oct 08, 2010load_motor_gsr7 STARTED Oct 08, 2010load_erics_r30 STARTED Oct 08, 2010

Separate services are installed for each instance of Tivoli Common Reporting youinstalled on each server. Use the trcmd -checkstatus command to check the statusof a specific Tivoli Common Reporting component.Related information:

Tivoli Common Reporting commands

Process checks for Linux

Process checks can ensure that the processes are running correctly.

On Linux, use the following status commands to the init.d services as root user:# service dboravirtuo status# service sdsna status# service sapmonvirtuo status# service sapmgrvirtuo status# service sapvirtuo status

Separate services are installed for each instance of Tivoli Common Reporting youinstalled on each server. Use the trcmd -checkstatus command to check the statusof a specific Tivoli Common Reporting component. For more information aboutTivoli Common Reporting commands, see http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/tcr_original/ctcr_cli.html

Sample output:# service dboravirtuo statusDatabase listener is running.Database instance vtdb is running.# service sdsna statussds LDAP server is runningsds admin server is running# service sapmonvirtuo statussapmon process running# service sapmgrvirtuo statussapmgr process running# service sapvirtuo status

Chapter 12. Starting Tivoli Netcool Performance Manager 107

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/tcr_original/ctcr_cli.html




NAME STATE SINCEas STARTED 17:21:28asd STARTED 17:25:04nc_cache STARTED 17:25:51alarm_cache STARTED 17:26:34load_ericssonbss_r10 STARTED 17:26:39load_nokiabss_oss31ed3 STARTED 17:26:44load_motorolabss_gsr7 STARTED 17:26:49load_motorolautran_usr10 STARTED 17:26:54load_ericssonutran_r30 STARTED 17:26:59

Completing startup of Tivoli Netcool Performance Manager - Wirelesscomponent

Details the final steps of completing the startup of Tivoli Netcool PerformanceManager - Wireless component.

About this task

Important: Distributed systems only. In a distributed system, perform a completestartup on the server that is hosting the application component.

Run the following commands to ensure that SAP process management is running,and then start the remaining Tivoli Netcool Performance Manager processes.

Procedure1. Run the following commands as user root:

v

/etc/rc.d/init.d/sapmonvirtuo start/etc/rc.d/init.d/sapmgrvirtuo start

v

svcadm enable sapmon-nasvcadm enable sapmgr-na

v

service sapmonvirtuo startservice sapmgrvirtuo start

2. Run the following command as user virtuo:sap disp

3. Run the following command as user root:

v

/etc/rc.d/init.d/sapvirtuo start

v

svcadm enable sap-na

v

service sapvirtuo start

What to do next

The location of the process log files is determined by the WMCLOGDIR setting in the$WMCROOT/conf/environment/default.properties file.


Ensure that no exceptions occurred in these files. If the process started successfully,each process log file must return the line Process Startup done when it is startedsuccessfully.

Chapter 12. Starting Tivoli Netcool Performance Manager 109


Chapter 13. Enable Common Reporting on Tivoli NetcoolPerformance Manager

Extra software is required if you want to use the Tivoli Common Reporting serverthat is installed with Tivoli Netcool Performance Manager.

IBM Tivoli Common Reporting is an enterprise reporting solution that delivers acommon reporting platform across the Tivoli portfolio. To make full use ofCommon Reporting, you must install Tivoli Netcool Performance Manager -Application Studio in your system.

The Tivoli Netcool Performance Manager - Application Studio tooling greatlysimplifies the task of reporting on network performance by using Tivoli CommonReporting.

For more information about Tivoli Netcool Performance Manager - ApplicationStudio, see http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.1/com.ibm.tnpm_1.4.1_kc.doc/tnpm_1.4.1_kc_welcome.html.

Tivoli Netcool® Performance Manager - Application StudioA new tool for creating and publishing simplified and enhanced data models onDashboard Application Services Hub with IBM Cognos 10 support.

For information about this tool, see Installing and Using Tivoli Netcool PerformanceManager - Application Studio from the following link:http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.0/com.ibm.tnpm_1.4_kc.doc/npm_as/ctnpm_npm_as_intro_14.dita.


http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.1/com.ibm.tnpm_1.4.1_kc.doc/tnpm_1.4.1_kc_welcome.html

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.1/com.ibm.tnpm_1.4.1_kc.doc/tnpm_1.4.1_kc_welcome.html

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.0/com.ibm.tnpm_1.4_kc.doc/npm_as/ctnpm_npm_as_intro_14.dita

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.0/com.ibm.tnpm_1.4_kc.doc/npm_as/ctnpm_npm_as_intro_14.dita


Appendix A. Installation output

This appendix details example output associated with the installation of all thepackages on a distributed Tivoli Netcool Performance Manager server.

The output shown is for an interactive installation.[server.ibm.com]# ksh pmw_install -wmcr /appl/virtuoMaking PMW top-level directory: /appl/virtuoMaking software archive directories: under /appl/virtuo/admin/softwareLooking for bootstrap packageFound vallent-vt-common-TNPM1.4.0.0.tar.gzExtracting and running bootstrap packageLooking for bootstrap scriptRunning vallent-vt-common.installCopyright 2013 IBM Corporation, All Rights ReservedThis installation script will install theTivoli Netcool Performance Manager commonsoftware version TNPM1.4.0.0 on your system.

Do you wish to continue? y

Do you agree with the terms of this license? yRunning pre-install commands...Backing up old versions of non-shared files to be installed...Creating installation directories...Installing software...Checking configuration files...Updating file permissions...Setting up init scripts...Running post-install commands...... Checking Virtuo File Permissions... Setup Virtuo profileSetting up virtuo User Profile....done

Completed Virtuo Software InstallationLogs can be seen in pmw_install.logInstallation is complete.

What Type of System Are you Installing?

1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit PMW Install

---->1Checking packages: jre ant java-libs as-core core sap njloaderds-conf db-install db-conf tcrVerified the following packages:

* /appl/vallent-vt-jre-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-ant-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-java-libs-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-as-core-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-core-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-sap-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-njloader-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-ds-conf-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-db-install-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-db-conf-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-tcr-TNPM1.4.0.0.tar.gz

Do you want to deploy the packages? [yes/no] >yesInstalling

jre (TNPM1.4.0.0) ... okant (TNPM1.4.0.0) ... okjava-libs (TNPM1.4.0.0) ... okas-core (TNPM1.4.0.0) ... okcore (TNPM1.4.0.0) ...

Please Verify Environment Settings


1. Accept Variable Values below2. Reset Variables to Default values3. Change WMCHOST=<myserver.ibm.com>4. Change VTDBHOST=<myserver.ibm.com>5. Change LDAPHOST=<myserver.ibm.com>6. Change SMTP_HOST=<myserver.ibm.com>7. Change SMTP_PORT=258. Change REPLY_ADDRESS=<myserver.ibm.com>9. Change SERVER_IP_ADDRESS=10.55.236.13810. Change SHORT_IP_ADDRESS=10.55.23611. Change WMCROOT=/appl/virtuo12. Change WMCLOGDIR=/appl/virtuo/logs/13. Change WMCVARDIR=/appl/virtuo/var/14. Change LDAPPORT=138915. Change LDAPROOT=dc=persistent,dc=co,dc=in16. Change LDAP_PASSWORD=Virtuo0117. Change OPERATOR=Company118. Change ORACLEPORT=152119. Change VTDBSID=vtdb20. Change VTDB_USERNAME=virtuo21. Change VTDB_PASSWORD=Virtuo0122. Change SAPMONPORT=900923. Change OMPORT=900824. Change ASHTTPPORT=808025. Change ASREDIRPORT=844326. Change ASAJPPORT=808627. Change ASWEBSRVPORT=808328. Change ASBRIDGEPORT=1009129. Change ASNSPORT=109930. Change ASJRMPINVOKPORT=444431. Change ASPOOLINVOKPORT=444532. Change ASRMIPORT=109833. Change ASUIL2PORT=809334. Change ASHSQLPORT=170135. Change ORBPORT=352836. Change ORBSSLPORT=3529

---->1Configuring /appl/virtuo files .......doneok

sap (TNPM1.4.0.0) ... oknjloader (TNPM1.4.0.0) ...


1. Accept Variable Values below2. Reset Variables to Default values3. Change LDRHOST=<myserver.ibm.com>4. Change WMCHOST=<myserver.ibm.com>5. Change VTDBHOST=<myserver.ibm.com>6. Change ORACLEPORT=15217. Change VTDBSID=vtdb8. Change VTDB_USERNAME=virtuo9. Change VTDB_PASSWORD=Virtuo0110. Change WMCROOT=/appl/virtuo11. Change WMCLOGDIR=/appl/virtuo/logs/12. Change WMCVARDIR=/appl/virtuo/var/13. Change SAPMONPORT=900914. Change OMPORT=900815. Change ASNSPORT=1099

---->1Configuring /appl/virtuo files .......doneok

ds-conf (TNPM1.4.0.0) ... okdb-install (TNPM1.4.0.0) ... okdb-conf (TNPM1.4.0.0) ...


1. Accept Variable Values below2. Reset Variables to Default values3. Change WMCHOST=<myserver.ibm.com>4. Change WMCLOGDIR=/appl/virtuo/logs/5. Change WMCVARDIR=/appl/virtuo/var/6. Change ASNSPORT=10997. Change MSTRCACHE_RMI=98768. Change ALRMCACHE_RMI=9877

---->1


Configuring /appl/virtuo files .......doneok

tcr (TNPM1.4.0.0) ... okAll packages installed successfully

Details in pmw_install.log

Would you like to perform task JBOSS_INSTALL ? [yes/no] >yesPlease enter the location of the JBoss 4.0.3SP1 archive (or q to quit)!: [/appl]---->Deploying JBoss 4.0.3SP1...Buildfile: /appl/virtuo/admin/common/install/scripts/build.xml

init:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/appl

find-archive:

expand-tar-gz:[echo] Expanding gzipped tarfile[untar] Expanding: /appl/jboss-4.0.3SP1.tar.gz into /appl/virtuo[untar] Expanding: /appl/jboss-4.0.3SP1.tar.gz into /appl/virtuo

expand-tar-bz2:

expand-zip:

all:[echo] Expansion complete[move] Moving 1272 files to /appl/virtuo/as[move] Moving 5 files to /appl/virtuo/as/server/default


copy-libs:[copy] Copying 3 files to /appl/virtuo/as/server/default/lib[copy] Copying 10 files to /appl/virtuo/lib/tp

[delete] Deleting directory /appl/virtuo/jboss-4.0.3SP1


fix-alarm-war:[mkdir] Created dir: /appl/virtuo/temp[mkdir] Created dir: /appl/virtuo/temp/war/apps/lib[unjar] Expanding: /appl/virtuo/as/server/default/deploy_core/

S02-na-alarm-manager.ear into /appl/virtuo/temp[unjar] Expanding: /appl/virtuo/lib/na-alarm-service-server.jar into

/appl/virtuo/temp


signjarpmw:[echo] Signing JBoss client jar[exec][exec] Warning:[exec] The signer certificate will expire within six months.[copy] Copying 1 file to /appl/virtuo/temp/war/apps/lib[jar] Updating jar: /appl/virtuo/temp/S02-na-alarm-manager.war[jar] Updating jar: /appl/virtuo/as/server/default/deploy_core/S02-na-alarm-manager.ear

BUILD SUCCESSFULTotal time: 13 secondsWould you like to perform task DS_SCHEMA_INSTALL ? [yes/no] >yesUsing local LDAP server, port 1389... OK.Please enter the password for ’Directory Manager’, the Directory Server User [Dirmgr01]:

Please enter the password for ’SysAdmin’, the Directory Server User [Sysadm01]:Directory Server "SysAdmin" user password set to "Sysadm01"

Installing Directory server schema...Performing sanity check on Directory Server schema......doneDS schema installed.

Appendix A. Installation output 115

Would you like to perform task DB_INSTALL ? [yes/no] >yes--------------------------------------------------------------------Please enter your Database SID (8 character maximum): [vtdb]---->Found default template: /appl/virtuo/admin/oracle/conf/vtdb.dbtPlease enter the full path of the PMW database template: [/appl/virtuo/admin/oracle/conf/vtdb.dbt]---->/appl/virtuo/admin/oracle/conf/vtdb_test.dbtPMW database will be created using template /appl/virtuo/admin/oracle/conf/vtdb_test.dbtPlease enter your ADDM license type [NONE | DIAGNOSTIC | DIAGNOSTIC+TUNING ]: [NONE]---->ADDM license type is set to "NONE"You must create passwords for the sys and system database users.

Please enter a password for the sys user: [Sysdb01]---->Please enter a password for the system user: [Sysdb01]---->Creating and starting Oracle instance------------100% completeLook at the log file "/appl/oracle/cfgtoollogs/dbca/vtdb/vtdb.log" for further details.Completed vtdb database creationRunning Oracle Net ConfigurationGenerating dbora startup scripts ....Waiting for DB listener for vtdbListener is up. Continuing...Running post-install procedures for vtdb database.Making post-install changesCreating OEM repository and console accessible by port 1158. This may take a while...|Would you like to perform task DB_SCHEMA_INSTALL ? [yes/no] >yes--------------------------------------------------------------------Please enter the Virtuo Database SID: [vtdb]---->Database SID set to "vtdb"Please enter the Database sys user password: [Sysdb01]---->Database user sys password set to "Sysdb01"Please enter the Database virtuo user password: [Virtuo01]---->Database user virtuo password is set to "Virtuo01".... Starting Database Schema ’core’Creating database schema ’core’ in SID ’vtdb’. This may take several minutes ...|.... Database Schema Creation finished successfully.... Log file is located in /appl/virtuo/admin/oracle/schema/core/install_schema.log.... Database Schema ’core’ Creation completedWould you like to perform task DB_SCHEMA_POST_INSTALL ? [yes/no] >yes--------------------------------------------------------------------Please enter the TNPMW Database SID: [vtdb]---->Database SID set to "vtdb"Please enter the SYSDBA Database user name: [sys]---->Database user name with SYSDBA priv is set to "sys"Please enter the SYSDBA Database user sys password: [Sysdb01]---->Database user sys password is set to "Sysdb01"Please enter the Database user name: [virtuo]---->Database schema name is set to "virtuo"Please enter the Database user virtuo password: [Virtuo01]---->Database user virtuo password is set to "Virtuo01".... Starting Loading JAR Files To ’virtuo’ SchemaLoading JAR files to database schema ’virtuo’ in ’vtdb’ database...-.... Loading JAR Files To ’virtuo’ Schema Is Completed.... Starting Importing Stored Outline To ’virtuo’ SchemaImporting outline to database schema ’virtuo’ in ’vtdb’ database....... Importing Stored Outline To ’virtuo’ Schema Is Completed.... Setting Compatible to 11.2.0 and restarting DatabaseSet COMPATIBLE parameter to 11.2.0 in ’vtdb’ database...Database is up and runningConfigure Dictionary Statistics Refresh in ’vtdb’ database...Copying database JDBC library files...Copying database library files...Done..... Adding overflow tablepaces.... Adding overflow tablepaces Complete.... Creating Part Maint views ext.... Creating Part Maint views ext Complete


Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no] >yesConfiguring core cronjobs.......

What Type of PMW System Are you Installing ?-----------------------------------------------------------------------Please select the type of PMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)Database (5)Gateway (6)-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6 ] :1Server type selected: ALLPlease enter the ORACLE_HOME Directory [/appl/oracle/product/11.2.0/db_1]:(Enter . if unknown)

Please enter the ORACLE_BASE Directory [/appl/oracle]:(Enter . if unknown)

Please enter the ORACLE_SID Parameter [vtdb]:(Enter . if unknown)

Please enter the vtdb Database Archive Directory [/oradump/vtdb]:(Enter . if unknown)

Please enter the Directory Server log Directory [/appl/ldap/idsslapd-idsinst/logs]:(Enter . if unknown)

Please enter the PMW Log Directory [/appl/virtuo/logs]:(Enter . if unknown)

Please enter the PMW Archive Logs Directory [/data/trace_archive1]:(Enter . if unknown)

Setting up CRON environment ...

Filtering old cronjobs ....... Done

Setting up root cronjobs ...Finished setting up root cronjobsSetting up virtuo user cronjobs ...Finished setting up virtuo cronjobsRestarting Cron ...Stopping crond: [ OK ].... cron daemon stoppedStarting crond: [ OK ].... cron daemon started

Please view pmw_install.log for install details

Would you like to perform task GATEWAYS_INSTALL ? [yes/no] >noWould you like to perform task TECHPACKS_INSTALL ? [yes/no] >yesTechpack install order file found in /applChecking packages:vallent-vt-Neutral_Core_GOMvallent-vt-Neutral_GSM_BSS_NSS_GOMvallent-vt-Neutral_GPRS_UMTS_CN_GOMvallent-vt-Neutral_GPRS_BSS_GOMvallent-vt-Neutral_UMTS_UTRAN_GOMvallent-vt-NOK_GOMletvallent-vt-GSM_Nokia_BSS_RG20Verified the following packages:

* /appl/vallent-vt-Neutral_Core_GOM-1.0.tar.gz* /appl/vallent-vt-Neutral_GSM_BSS_NSS_GOM-1.0.tar.gz* /appl/vallent-vt-Neutral_GPRS_UMTS_CN_GOM-1.0.tar.gz* /appl/vallent-vt-Neutral_GPRS_BSS_GOM-1.0.tar.gz* /appl/vallent-vt-Neutral_UMTS_UTRAN_GOM-1.0.tar.gz* /appl/vallent-vt-NOK_GOMlet-2.1.tar.gz* /appl/vallent-vt-GSM_Nokia_BSS_RG20-4.0.0.tar.gz

Do you want to deploy the packages? [yes/no] >yesInstalling

Neutral_Core_GOM (1.0) ... okNeutral_GSM_BSS_NSS_GOM (1.0) ... tar: Read 5120 bytes from -

ok


Neutral_GPRS_UMTS_CN_GOM (1.0) ... tar: Read 5120 bytes from -ok

Neutral_GPRS_BSS_GOM (1.0) ... tar: Read 5120 bytes from -ok

Neutral_UMTS_UTRAN_GOM (1.0) ... okNOK_GOMlet (2.1) ... okGSM_Nokia_BSS_RG20 (4.0.0) ... tar: Read 5120 bytes from -

okAll packages installed successfully

Details in pmw_install.log

Starting application server...

Licensed Materials - Property of IBM

5724W86

(C) Copyright IBM Corp. 2005, 2009 All Rights Reserved.

Waiting for appserver...Mon May 25 10:48:40 IST 2015: as is at state exec. Waiting for state STARTEDMon May 25 10:48:52 IST 2015: as is at state exec. Waiting for state STARTEDMon May 25 10:49:04 IST 2015: as is at state exec. Waiting for state STARTEDMon May 25 10:49:25 IST 2015 as now up, clock started 104828000, now 104925000Appserver ready.Would you like to perform task SYSINIT ? [yes/no] >yes


5724W86


10:49:29,613 INFO [SystemInit] Login...10:49:41,427 INFO [SystemInit] Operation SucceededWould you like to perform task TECHPACK_ADMIN ? [yes/no] >yesBuildfile: /appl/virtuo/admin/techpacks/build.xml

copyright-info:[echo] Licensed Materials - Property of IBM[echo] 5724W86[echo] (C) Copyright IBM Corp. 2005, 2009 All Rights Reserved.

set-install-mode-from-env:

set-default-install-mode:

set-install-mode:

init:[wmcInit] 10:55:15,057 [main] DEBUG logging - Created Logging Directory :/appl/virtuo/logs/vmm

apply:[applyTechPacks] About to install modules. View logs for installation results.[applyTechPacks][applyTechPacks] WARNING: Tablespace properties file/appl/virtuo/conf/vmm/tablespace_Neutral_Core_GOM_1.0.properties does not exist![applyTechPacks] Do you want to continue with techpack default tablespace settings? [y|n]y[applyTechPacks] Using default tablespace settings for techpack Neutral Core GOM[applyTechPacks][applyTechPacks] No report templates to apply.[applyTechPacks] elapsedTime for Install = 14826[applyTechPacks] Module Neutral_Core_GOM 1.0 processed in under 15 seconds.[applyTechPacks][applyTechPacks] WARNING: Tablespace properties file/appl/virtuo/conf/vmm/tablespace_Neutral_GSM_BSS_NSS_GOM_1.0.properties does not exist![applyTechPacks] Do you want to continue with techpack default tablespace settings? [y|n]y[applyTechPacks] Using default tablespace settings for techpack Neutral GSM BSS/NSS GOM[applyTechPacks][applyTechPacks] No report templates to apply.[applyTechPacks] elapsedTime for Install = 47089[applyTechPacks] Module Neutral_GSM_BSS_NSS_GOM 1.0 processed in under 48 seconds.[applyTechPacks][applyTechPacks] WARNING: Tablespace properties file/appl/virtuo/conf/vmm/tablespace_Neutral_GPRS_UMTS_CN_GOM_1.0.properties does not exist![applyTechPacks] Do you want to continue with techpack default tablespace settings? [y|n]


y[applyTechPacks] Using default tablespace settings for techpack Neutral GPRS/UMTS CN GOM[applyTechPacks][applyTechPacks] No report templates to apply.[applyTechPacks] elapsedTime for Install = 9740[applyTechPacks] Module Neutral_GPRS_UMTS_CN_GOM 1.0 processed in under 10 seconds.[applyTechPacks][applyTechPacks] WARNING: Tablespace properties file/appl/virtuo/conf/vmm/tablespace_Neutral_GPRS_BSS_GOM_1.0.properties does not exist![applyTechPacks] Do you want to continue with techpack default tablespace settings? [y|n]y[applyTechPacks] Using default tablespace settings for techpack Neutral GPRS BSS GOM[applyTechPacks][applyTechPacks][applyTechPacks][applyTechPacks][applyTechPacks] No report templates to apply.[applyTechPacks] elapsedTime for Install = 4061[applyTechPacks] Module Neutral_GPRS_BSS_GOM 1.0 processed in under 5 seconds.[applyTechPacks][applyTechPacks] WARNING: Tablespace properties file/appl/virtuo/conf/vmm/tablespace_Neutral_UMTS_UTRAN_GOM_1.0.properties does not exist![applyTechPacks] Do you want to continue with techpack default tablespace settings? [y|n]y[applyTechPacks] Using default tablespace settings for techpack Neutral UMTS UTRAN GOM[applyTechPacks][applyTechPacks][applyTechPacks][applyTechPacks][applyTechPacks] No report templates to apply.[applyTechPacks] elapsedTime for Install = 15652[applyTechPacks] Module Neutral_UMTS_UTRAN_GOM 1.0 processed in under 16 seconds.[applyTechPacks][applyTechPacks] WARNING: Tablespace properties file/appl/virtuo/conf/vmm/tablespace_NOK_GOMlet_2.1.properties does not exist![applyTechPacks] Do you want to continue with techpack default tablespace settings? [y|n]y[applyTechPacks] Using default tablespace settings for techpack NOK GOMlet[applyTechPacks][applyTechPacks][applyTechPacks][applyTechPacks][applyTechPacks][applyTechPacks] No report templates to apply.[applyTechPacks] elapsedTime for Install = 99964[applyTechPacks] Module NOK_GOMlet 2.1 processed in under 100 seconds.[applyTechPacks][applyTechPacks] WARNING: Tablespace properties file/appl/virtuo/conf/vmm/tablespace_GSM_Nokia_BSS_RG20_4.0.0.properties does not exist![applyTechPacks] Do you want to continue with techpack default tablespace settings? [y|n]y[applyTechPacks] Using default tablespace settings for techpack Nokia GSM BSS[applyTechPacks][applyTechPacks][applyTechPacks][applyTechPacks][applyTechPacks] Configuring LocalizedMessageFactory with country’United States’ and language ’English’ with bundle ’localization.LocalizedMessages’[applyTechPacks] elapsedTime for Install = 196951[applyTechPacks] Module GSM_Nokia_BSS_RG20 4.0.0 processed in under 4 minutes.

[delete] Deleting: /appl/virtuo/admin/techpacks/new_techpacks

BUILD SUCCESSFULTotal time: 6 minutes 37 seconds[applyTechPacks] All modules installed successfully.


5724W86


INFO: Shutting down the framework manager (does not stop framework processes).


5724W86



Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yes

Replacing all passwords with encoded passwords...

Encoding values in /appl/virtuo/conf/as/as-default.propertiesEncoding values in /appl/virtuo/conf/as/as-default.properties.NEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.NEncoding values in /appl/virtuo/conf/dbconnection/vtdb.propertiesEncoding values in /appl/virtuo/conf/externalreporting/default.properties.NEncoding values in /appl/virtuo/conf/externalreporting/default.propertiesEncoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.propertiesEncoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties.NEncoding values in /appl/virtuo/conf/dbspace_admin/dbspace_admin.xmlEncoding values in /appl/virtuo/conf/dbspace_admin.xmlEncoding values in /appl/virtuo/conf/ldap/default.properties.NEncoding values in /appl/virtuo/conf/ldap/default.properties

Passwords may also be stored in /appl/virtuo/admin/logs/pmw_install.log,so it should be removed when not needed anymore.Enabling sap...Done.

Installation output for patchExample output associated with the installation of patch.# ksh pmw_install -wmcr /appl/virtuoMaking PMW top-level directory: /appl/virtuoMaking software archive directories: under /appl/virtuo/admin/softwareLooking for bootstrap packageFound vallent-vt-common-TNPM1.4.0.0.tar.gzExtracting and running bootstrap packageLooking for bootstrap scriptRunning vallent-vt-common.installCopyright 2013 IBM Corporation, All Rights ReservedThis installation script will install the Tivoli Netcool Performance Manager commonsoftware version TNPM1.4.0.0 on your system.Do you wish to continue? yDo you agree with the terms of this license? yRunning pre-install commands...Backing up old versions of non-shared files to be installed...Creating installation directories...Installing software...Checking configuration files...Updating file permissions...Setting up init scripts...Running post-install commands...... Checking Virtuo File Permissions... Setup Virtuo profileSetting up virtuo User Profile....doneCompleted Virtuo Software InstallationLogs can be seen in pmw_install.logInstallation is complete.What Type of System Are you Installing?1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit PMW Install---->5Checking packages: jre ant db-install db-confVerified the following packages:* /appl/vallent-vt-jre-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-ant-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-db-install-TNPM1.4.0.0.tar.gz* /appl/vallent-vt-db-conf-TNPM1.4.0.0.tar.gzDo you want to deploy the packages? [yes/no] >yesInstallingjre (TNPM1.4.0.0) ... okant (TNPM1.4.0.0) ... okdb-install (TNPM1.4.0.0) ... okdb-conf (TNPM1.4.0.0) ...Please Verify Environment Settings1. Accept Variable Values below2. Reset Variables to Default values3. Change WMCHOST=<myserver.ibm.com>


4. Change WMCLOGDIR=/appl/virtuo/logs/5. Change WMCVARDIR=/appl/virtuo/var/6. Change ASNSPORT=10997. Change MSTRCACHE_RMI=98768. Change ALRMCACHE_RMI=9877---->3Set the value of variable WMCHOST: [<myserver.ibm.com>]----><myserver.ibm.com>Please Verify Environment Settings1. Accept Variable Values below2. Reset Variables to Default values3. Change WMCHOST=<myserver.ibm.com>4. Change WMCLOGDIR=/appl/virtuo/logs/5. Change WMCVARDIR=/appl/virtuo/var/6. Change ASNSPORT=10997. Change MSTRCACHE_RMI=98768. Change ALRMCACHE_RMI=9877---->1Configuring /appl/virtuo files .......doneokAll packages installed successfullyDetails in pmw_install.logWould you like to perform task DB_INSTALL ? [yes/no] >yes--------------------------------------------------------------------Please enter your Database SID (8 character maximum): [vtdb]---->Found default template: /appl/virtuo/admin/oracle/conf/vtdb.dbtPlease enter the full path of the PMW database template:[/appl/virtuo/admin/oracle/conf/vtdb.dbt]---->/appl/virtuo/admin/oracle/conf/vtdb_test.dbtPMW database will be created using template/appl/virtuo/admin/oracle/conf/vtdb_test.dbtPlease enter your ADDM license type[NONE | DIAGNOSTIC | DIAGNOSTIC+TUNING ]: [NONE]---->ADDM license type is set to "NONE"You must create passwords for the sys and system database users.Please enter a password for the sys user: [Sysdb01]---->Please enter a password for the system user: [Sysdb01]---->Creating and starting Oracle instance



Appendix B. Log file errors

This appendix shows the Oracle installation errors that can be safely ignored.

Oracle installation1. Checking for noexec_user_stack=1; found no entry. Failed

The Oracle Installation log output is found in:/var/install/logs/oracle11gR204_install_6451.log

Following the installation of Oracle, the following error may be seen in theOracle Installation log.Checking for noexec_user_stack=1; found no entry. Failed

This error can be safely ignored.2. Performing check for SwapSpace

The Oracle Inventory log output is found in:/appl/oracle/product/oraInventory/logs/oraInstall<timestamp>.out

Following the installation of Oracle, the following error may be seen in theInventory log.Performing check for SwapSpaceChecking available swap space requirements ...Expected result: <size>MBActual Result: <size>MBCheck complete. The overall result of this check is: Failed <<<<

This error can be safely ignored.

Creating OEM repository and console accessible by a specific portHow to deal with the failure you might encounter when the post installation stepof creating OEM repository and console that is accessible by a specific port fails.

Creating OEM repository and console accessible by specific port results in thefollowing error.\ERROR: failed to create EM repository

Task DB_INSTALL exited with value 1.

The DB is created successfully.

User action:1. Edit $WMCROOT/admin/oracle/install/scripts/database_install and comment

out the last line.run_task config_oem_repos

to be, for example:#run_task config_oem_repos

2. Rerun pmw_install and answer yes to DB_INSTALL.



Appendix C. Dependency Checker errors

Dependency Checker errors.

ErrorsGYMWI0001E Directories missing from root user PATHThe following directories are missing from the root user PATH: <missing_dirs>You must ensure that the root user profile is sourced beforerunning the installation.Hint: If you use ’su’ to change to the root user, use the ’-’argument to source the profile, i.e. ’su -’-------------------------------------------------------------GYMWI0002E No domain name configuredYou must set up a domain name on the server and ensure the fully qualified hostname is valid-------------------------------------------------------------GYMWI0003E Hostname <FQDN> resolves to loopbackIP address x.x.x.x - must be a real IP addressThe server hostname must resolve to a non-loopback IP address.Otherwise the alarms UI will not function correctly.-------------------------------------------------------------GYMWI0004E Hosts entry for <FQDN> not found-------------------------------------------------------------GYMWI0054E Invalid umask for root user:022 The umask for the root user must be set to 0022-------------------------------------------------------------GYMWI0005E OS <OS> is not supported. Must be one of: Linux SunOS AIXOnly Linux, AIX and SunOS (Solaris) are supported-------------------------------------------------------------GYMWI0006E SunOS version <OS_VER> is not supported. Must be 5.10Solaris 10 is the only supported version-------------------------------------------------------------GYMWI0007E Processor type <PROC_TYPE> is not supported for <OS>Solaris is only supported on SPARC processors-------------------------------------------------------------GYMWI0008E Platform must support 64-bit kernel-------------------------------------------------------------GYMWI0009E Unable to determine update level for SunOS-------------------------------------------------------------GYMWI0011E Update level for SunOS is &ltSOLARIS_UPDATE>:required level is &ltREQUIRED_UPDATE>You must install the latest recommended update-------------------------------------------------------------GYMWI0012E Processor type <PROC_TYPE> is not supported for LinuxLinux is only supported on x86_64 architecture-------------------------------------------------------------GYMWI0013E Linux distribution must be Red Hat-------------------------------------------------------------GYMWI0014E Linux distribution must be Red Hat Enterprise Linux Server-------------------------------------------------------------GYMWI0015E Red Hat Release <RHEL_VERSION> is not supported:must be 5.9 or later-------------------------------------------------------------GYMWI0016E &ltdir>is not a directory-------------------------------------------------------------GYMWI0017E Insufficient space on <fs> partition.Space required on this partition:KB Space available: KBThe following required directories are mounted on this partition:-------------------------------------------------------------GYMWI0018E One or more required <OS> packages not installedMissing packages:-------------------------------------------------------------GYMWI0019E ERROR: invalid argument to linux_pkg_checks():-------------------------------------------------------------GYMWI0049E ERROR: invalid format for package info: <pkg>


-------------------------------------------------------------GYMWI0050E ERROR: incomplete package information: <pkg>-------------------------------------------------------------GYMWI0051E ERROR: invalid package version for <pkg>: <ver>-------------------------------------------------------------GYMWI0052E ERROR: invalid package release for <pkg>: <rel>-------------------------------------------------------------GYMWI0020E <tpp_type> <OS> packages are missing-------------------------------------------------------------GYMWI0021E <tpp_type> <OS> packages require upgrade-------------------------------------------------------------GYMWI0022E User oracle shell <ORACLE_USER_SHELL> is not supported:must be /bin/ksh-------------------------------------------------------------GYMWI0055E Invalid oracle user umask: <ORACLE_USER_UMASK>The oracle user umask must be set to 022-------------------------------------------------------------GYMWI0023E ORACLE_BASE environment variable not set-------------------------------------------------------------GYMWI0024E ORACLE_BASE directory /appl/oracle does not exist-------------------------------------------------------------GYMWI0025E ORACLE_OWNER: <ORACLE_OWNER> is expected to be oracle-------------------------------------------------------------GYMWI0026E ORACLE_HOME environment variable not set-------------------------------------------------------------GYMWI0027E ORACLE_HOME directory <ORACLE_HOME> does not exist-------------------------------------------------------------GYMWI0028E PATH for oracle does not contain <ORACLE_HOME>/bin-------------------------------------------------------------GYMWI0029E LD_LIBRARY_PATH for oracle does not contain <ORACLE_HOME>/lib-------------------------------------------------------------GYMWI0030E NLS_LANG environment variable for oracle user must be set to<VALID_NLS_LANG>-------------------------------------------------------------GYMWI0031E Installed Oracle version is invalidInstalled Oracle version is <installed_ver>- required version is<required_ver>-------------------------------------------------------------GYMWI0032E Oracle oneoff patches not installedThe following oneoff Oracle patches are missing:-------------------------------------------------------------GYMWI0033E Oracle Partitioning is not installed-------------------------------------------------------------GYMWI0034E <dir> does not exist-------------------------------------------------------------GYMWI0035E <dir> must be owned by oracle-------------------------------------------------------------GYMWI0036E <dir> must be executable by owner oracle-------------------------------------------------------------GYMWI0037E <dir> must be executable for non-oracle users-------------------------------------------------------------GYMWI0038E <binary> does not exist-------------------------------------------------------------GYMWI0039E <binary> must be owned by oracle-------------------------------------------------------------GYMWI0040E <binary> must be executable by owner oracle-------------------------------------------------------------GYMWI0041E <binary> must be executable for non-oracle users-------------------------------------------------------------GYMWI0042E <ORACLE_HOME>/network/admin/<ora_file> must be owned by oracle-------------------------------------------------------------GYMWI0043E <ora_file> must be writable by owner oracle-------------------------------------------------------------GYMWI0044E <ora_file> must be readable for non-oracle users-------------------------------------------------------------GYMWI0045E <ORACLE_HOME>/network/admin/<ora_file> must be an empty fileDB creation may fail if this file has invalid contents.-------------------------------------------------------------GYMWI0046E <pkg_count> versions of <core_pkg> foundThere can only be 1 version of each package in <pkg_dir>-------------------------------------------------------------


GYMWI0047E TNPM core packages not foundThe following core packages could not be found: <missing_pkgs>-------------------------------------------------------------GYMWI0053E JBoss archive not foundThe JBoss 4.0.3 SP1 package should be located in <BASE_DIR>-------------------------------------------------------------GYMWI0046E <pkg_count> versions foundThere can only be 1 version of each package in <pkg_dir>-------------------------------------------------------------GYMWI0048E SDS/DB2 packages not foundThe following SDS/DB2 packages could not be found:-------------------------------------------------------------GYMWI0056E AIX version <version> is not supported.Must be 5.3 or greater-------------------------------------------------------------GYMWI0057E Processor type <PROC_TYPE> is not supported for AIXAIX is only supported on powerpc processors-------------------------------------------------------------GYMWI0059E Platform must support 64-bit hardware-------------------------------------------------------------GYMWI0060E Maintenance level for AIX is <OS_LEVEL>:Minimum required level is 5300-09-------------------------------------------------------------GYMWI0061E <req_fs>is required for SDS. Please install it.-------------------------------------------------------------GYMWI0063E <req_fs>is required for Oracle. Please install it.-------------------------------------------------------------GYMWI0064E Physical RAM is <P_RAM>KB which is under the minimum requirement of262144 KB (256 MB)-------------------------------------------------------------GYMWI0065E Swap space does not meet requirements.Should be twice the size of RAM or 1 GB (2097152 KB), whichever is smaller-------------------------------------------------------------GYMWI0066E Free disk space in /tmp directory is <tmpSpace>which is less than the minimum requirement of 400 MB.-------------------------------------------------------------GYMWI0067E oracle is not in <DBA_GROUP>group-------------------------------------------------------------GYMWI0068E SDS/DB2 fixpack not installedThe following db2fixpack is not installed: <SDS_FP_PREFIX>_fixpack.tar.gz }-------------------------------------------------------------GYMWI0069E Missing Jazz SM & TCR InstallationYou must install Jazz SM along with TCR before installing TNPM Wireless Component.-------------------------------------------------------------GYMWI0070E Required file missing. The following files are missing from the root user: <missing_dirs>You must ensure that the required file exist at the specified path.If the file exists in another path, you may add a softlink-------------------------------------------------------------

Warnings-------------------------------------------------------------WARNING: 1GYMWI0001W Default Jazz SM Port <port> is already in useYou must check the port configuration if you are installing Jazz SM on this Server.-------------------------------------------------------------

Additional note when you run the dependency_checker with -t app option forApplication Server:------------------------------------------------------------------------------------Note: Please make sure to install Jazz SM & TCR before installing Application server"when you plan to install Jazz SM, TCR and SDS on the same server.------------------------------------------------------------------------------------

Appendix C. Dependency Checker errors 127


Notices

This information was developed for products and services that are offered in theUSA.

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

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785United States of America

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience 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 IBMproduct and use of those websites is at your own risk.

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

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

IBM CorporationDepartment number/Building numberSite mailing address_City, State; Zip Code_USA (or appropriate country)

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

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

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

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

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

COPYRIGHT LICENSE:


This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

Portions of this code are derived from IBM Corp. Sample Programs.

© Copyright IBM Corp. _enter the year or years_. All rights reserved.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the followingterms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal use

You may reproduce these publications for your personal, noncommercial useprovided that all proprietary notices are preserved. You may not distribute, displayor make derivative work of these publications, or any portion thereof, without theexpress consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within yourenterprise provided that all proprietary notices are preserved. You may not makederivative works of these publications, or reproduce, distribute or display thesepublications or any portion thereof outside your enterprise, without the expressconsent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses orrights are granted, either express or implied, to the publications or anyinformation, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in itsdiscretion, the use of the publications is detrimental to its interest or, asdetermined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all United Statesexport laws and regulations.

Notices 131

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDINGBUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.

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

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of TheMinister for the Cabinet Office, and is registered in the U.S. Patent and TrademarkOffice.

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

Java and all Java-based trademarks and logos are trademarks orregistered trademarks of Oracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.


http://www.ibm.com/legal/us/en/copytrade.shtml

http://www.ibm.com/legal/us/en/copytrade.shtml

Index

Special characters-Xms<n>

property 99-Xmx<n>

property 100-XX:+AggressiveHeap

property 100

AAIX 106AIX software location 11Application server installation 73Application server memory

configuration 99Audience v

BBuilding

Perl on Gateway servers 21Bundled software 6Busy Hours definitions 97

CCheck

Oracle configuration 48Checking

time zone 102Checking database space 86Client

hardware and softwarerequirements 12

Client hardware requirements 12Client software requirements 12Complete startup 108Components 3Configuration

ports and firewalls 15, 17SAP params property 101

Configurekernel 19Oracle environment variables 43

Configuringapplication server memory 99database 66loader server memory 100loaders 80multiple identical loaders 92

conventionstypeface vii

Copy packages 51Create

user and group accounts 18Creating

loader 95Cronjobs installation

application server 75

Cronjobs installation (continued)distributed system 69loaders 80separate directory server 72standalone system 61

DData Availability definitions 98Database configuration 66Database installation

distributed system 66standalone system 59

Database schemapost-installation 60

Database schema installationdistributed system 67standalone system 59

Database server installation 65DB2 Installation 51Definitions

Busy Hours 97Data Availability 98Summary 98

Dependency Checker 39Dependency Checker errors 125Directory ownership configuration 18Directory server schema installation 58,

71application server 75

Distributed installation 65Distributed system installation 65Domain name set up 19Download

Java Runtime Environment 12

Eeducation

See Tivoli technical trainingEnabling

Tivoli Common Reporting 111Encrypting

distributed system passwords,separate directory server 72

passwords 64, 69, 78passwords, loaders 81

FFile systems 13

GGateways installation

distributed system 76separately 81stand-alone system 62

Hhostname set up 21

IIBM Security Directory Server client

installation 54IBM Tivoli Monitoring integration 103installation

Security Directory Server and IBMDB2 9

InstallationApplication Server in Distributed

Systems 45copy packages 51database server 47distributed 16IBM DB2 51IBM Security Directory Server

client 54interactive distributed system 65interactive standalone system 57JBoss 10Oracle 11.2.0.4 client 47Oracle 11g 8, 11Oracle 11g client 45Oracle client 43Oracle RDBMS 43, 44Oracle stand-alone or database

server 44output 113planning 3preparation 5prerequisites 13process 1roadmap 2Security Directory Server 51Software installation 55standalone system 56TCR 10Technology Packs 85Tivoli Netcool Performance Manager

software 55unattended 56

Installation prerequisitesSoftware installation prerequisites 55Tivoli Netcool Performance Manager

software 55Installation script 52installing vInstalling

application server 73cronjobs, application server 75cronjobs, distributed system 69cronjobs, loaders 80cronjobs, separate directory server 72cronjobs, standalone system 61database server 65directory server schema 58, 71


Installing (continued)directory server schema, application

server 75distributed system 65gateways, distributed system 76gateways, separately 81gateways, stand-alone system 62JBoss application server 58, 71, 74loader server 79separate directory server 70stand-alone system 57Technology Pack Step 1 87Technology Pack Step 2 88technology packs 62, 76

Installing distributed systemdatabase 66database schema 67

Installing standalone systemdatabase 59database schema 59

IntegratingIBM Tivoli Monitoring 103

Interactive installation 57

JJava memory configuration 22Java Runtime Environment

download 12Jazz for Service Management

location 27JBoss Application Server

location 11JBoss application server installation 58,

71, 74JVM memory

loader servers 102jvm.args

property 99

KKernel configuration 19

Llistener 49Loader

creation 95Loader configuration removal 94Loader server

JVM memory 102Loader server installation 79Loader server memory

configuration 100Loaders configuration 80Loading data

distributed systems 93loaders 93verifying 93

Loadmaps removal 94Locating

Oracle RDBMS and Clientsoftware 11

Locating softwareAIX 11

LocationJazz for Service Management 27JBoss Application Server 11Oracle 11g 44Oracle software 44Oracle Solaris 7Perl 11Red Hat Enterprise Linux 8software 6

Log file errors 123

OOracle 11.2.0.4 client installation 47Oracle 11g client installation 45Oracle client

installation 43Oracle configuration validation 48Oracle environment variables

configuration 43Oracle RDBMS

installation 43Oracle RDBMS and Client software

location 11Oracle RDBMS installation 44Oracle software location 44Oracle Solaris location 7

Ppackages

DB2 9Security Directory Server 9

Packages for installation 51Passwords encryption 64, 69, 78

distributed system, separate directoryserver 72

loaders 81Performing post-installation checks

Technology Packs 88Perl location 11Perl on Gateway servers set up 21Planning installation 3Ports and firewalls configuration 15, 17Post-installation

database schema 60, 68distributed system 68

Post-installation tasks 97Preinstallation

road map 1Preinstallation tasks 13Preparing installation 5Prerequisite

server software 6Prerequisites 13Process checks 106

Linux 107Property

-Xms<n> 99-Xmx<n> 100-XX:+AggressiveHeap 100jvm.args 99recommended jvm.args 100

ProvisioningBusy Hours 97Data Availability 97

Provisioning (continued)Summaries 97

Publications vi

RReboot

server 105Recommended jvm.args

property 100Red Hat Enterprise Linux location 8Remove

Loader configuration 94Loadmaps 94

Required file systems 13Required server information 13Required skills and knowledge viRequirements

client hardware 12Client hardware and software 12client software 12server hardware 5server hardware and software 5server software 5

RHELdistributed installation 16

RHEL packagesDB2 9JBoss installation 10Oracle 11g installation 8, 11Security Directory Server 9TCR 10Tivoli Common Reporting 10

Road mappreinstallation 1

Roadmapinstallation 2

Runinstallation script 52

RunningDependency Checker 39

SSAP configuration

params property 101Security Directory Server client 54Security Directory Server Installation 51Separate directory server installation 70Server hardware and software

requirements 5Server hardware requirements 5Server rebooting 105Server software

prerequisite 6Server software requirements 5service viiservice management connect viiSet

directory ownership 18Set up

domain name 19host name 21

SettingJava memory 22time zone 102


Setting updata sources 86users 86

Skills and knowledge viSMC viiSoftware

bundled 6Software location 6Stand-alone system installation 57Starting

SAP application server 85SAP process monitor tool 90SAP system 85Tivoli Netcool Performance

Manager 105Starting Application Server 91Starting Loaders Server 91Starting TNPM 105startup 108Summary definitions 98support viiSupported configurations

distributed system 4stand-alone system 4

TTechnology packs installation 62, 76Technology Packs installation 85Time zone checking 102Time zone settings 102Tivoli Common Reporting

enabling 111Tivoli Netcool Performance Manager

components 3Tivoli technical training viitraining, Tivoli technical viitypeface conventions vii

UUnattended installation on standalone

system 56User and group accounts creation 18

VVerifying data loading 93

Index 135


��

Printed in USA

Documents

IBMTivoli Netcool Performance Manager 1.4.1 Wireless Component Document ... · Wireless Component Document Revision R2E1 Installation Guide. Note Before using this information and