Embed Size (px)
Citation preview
IBM Tivoli Netcool Performance Manager 1.4.1Wireless ComponentDocument Revision R2E1
Upgrade Guide
���
NoteBefore using this information and the product it supports, read the information in “Notices” on page 49.
© Copyright IBM Corporation 2006, 2015.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.
Contents
About this information . . . . . . . . vIntended audience . . . . . . . . . . . . vThe Tivoli Netcool Performance Manager - Wirelesscomponent user publications . . . . . . . . . vService Management Connect . . . . . . . . viTivoli Netcool Performance Manager technicaltraining . . . . . . . . . . . . . . . . viSupport information . . . . . . . . . . . viConventions used in this publication . . . . . . vii
Typeface conventions . . . . . . . . . . vii
Chapter 1. Pre-upgrade tasks . . . . . 1Supported upgrade path . . . . . . . . . . 1Overview of the Oracle Database 11g Release 2(11.2.0.4) upgrade . . . . . . . . . . . . . 1Server hardware and software requirements . . . . 1
Server hardware requirements . . . . . . . 1Server software requirements . . . . . . . . 2
Gateways . . . . . . . . . . . . . . . 7Upgrading the platform package . . . . . . . 7Stopping Tivoli Netcool Performance Manager clients 8Stopping the application server and loaders . . . . 8Stopping the Tivoli Netcool Performance Managerframework . . . . . . . . . . . . . . . 8Stopping the SAP manager . . . . . . . . . 9Stopping the SAP monitor . . . . . . . . . . 9Running the Dependency Checker tool . . . . . 10Upgrading to Oracle 11g (11.2.0.4) . . . . . . . 14Restarting the database . . . . . . . . . . 14Upgrading the Tivoli Directory Server and IBM DB2 15
Locating the required packages . . . . . . . 16Checking the installed versions . . . . . . . 17
Upgrading Jazz for Service Management . . . . 17Common directory locations for Jazz for ServiceManagement . . . . . . . . . . . . . 18Preparing your environment for a full installationof Jazz for Service Management . . . . . . 21Location of Jazz for Service Managementsoftware . . . . . . . . . . . . . . 22
Overview of Jazz for Service Managementinstallation . . . . . . . . . . . . . 22Verifying the installation . . . . . . . . . 27Uninstalling Jazz for Service Management . . . 31
Upgrading Tivoli Common Reporting . . . . . 31Adding the LDAP user registry as a federatedrepository . . . . . . . . . . . . . . 32Configuring the LDAP federated repository . . 33Single sign-on . . . . . . . . . . . . 34Configuring single sign-on . . . . . . . . 35Upgrading from Tivoli Common Reporting 2.1and 2.1.1 . . . . . . . . . . . . . . 36Upgrading the content store from older versionsof Tivoli Common Reporting . . . . . . . 37
Chapter 2. Tivoli Netcool PerformanceManager Software Upgrade . . . . . . 39Applying Tivoli Netcool Performance Manager 1.4.1patch . . . . . . . . . . . . . . . . 39
Installing Tivoli Netcool Performance Manager1.4.1 patch . . . . . . . . . . . . . . 39Uninstalling Tivoli Netcool Performance Manager1.4.1 patch . . . . . . . . . . . . . . 40
Pre-upgrade checklist . . . . . . . . . . . 41
Chapter 3. Enabling Tivoli CommonReporting on Tivoli NetcoolPerformance Manager . . . . . . . . 43
Appendix. Dependency Checker errors 45
Notices . . . . . . . . . . . . . . 49Terms and conditions for product documentation. . 51Trademarks . . . . . . . . . . . . . . 52
© Copyright IBM Corp. 2006, 2015 iii
iv IBM Tivoli Netcool Performance Manager: Upgrade Guide
About this information
Provides instructions and general information on how to use IBM® Tivoli®
Netcool® Performance Manager software to create and view performance analysisreports for a telecommunications network.
Intended audienceThis guide is intended for the following audiences:v Managers and others who track network performance metricsv Technicians and engineers who use the Tivoli Netcool Performance Manager
software to manage and analyze network performance.In general, the reader of this guide is referred to as "you." By contrast, "we"refers to the Tivoli Netcool Performance Manager development and technicalstaff who support this product.
Required skills and knowledge
Readers need to be familiar with the following:v Operating System:
– Microsoft® Windows®
– Basics of the Microsoft Internet Explorer browser
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.
© Copyright IBM Corp. 2006, 2015 v
Table 1. Tivoli Netcool Performance Manager - Wireless component userdocumentation (continued)
Document Description
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.
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.
vi IBM Tivoli Netcool Performance Manager: Upgrade Guide
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
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
About this information vii
viii IBM Tivoli Netcool Performance Manager: Upgrade Guide
Chapter 1. Pre-upgrade tasks
Before you upgrade, acquire all of the prerequisite software and information, andcomplete each of the pre-upgrade tasks.
Supported upgrade pathThe supported upgrade path is from IBM Tivoli Netcool Performance Manager -Wireless Component 1.4 to 1.4.1.
Upgrading to Tivoli Netcool Performance Manager 1.4.1 is supported on thefollowing operating systems:v Oracle Solaris SPARCv Red Hat Enterprise Linux (RHEL) x86-64v IBM AIX®
Upgrading only to the same configuration is supported.v A single-server platform deployment can be upgraded only to a single-server
deployment.v Distributed deployments can be upgraded only to the same distributed
configuration. For example, a separated database deployment can be upgradedonly to a separated database deployment.
Overview of the Oracle Database 11g Release 2 (11.2.0.4) upgradeUpgrading to Oracle database version 11.2.0.3 to 11.2.0.4.
You must upgrade Oracle database version 11.2.0.3 to 11.2.0.4 separately.
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)
© Copyright IBM Corp. 2006, 2015 1
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
2 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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
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
Chapter 1. Pre-upgrade tasks 3
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
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 “Running theDependency Checker tool” on page 10 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_64
4 IBM Tivoli Netcool Performance Manager: Upgrade Guide
compat-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_64libstdc++-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.
Chapter 1. Pre-upgrade tasks 5
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_64compat-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
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.
6 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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 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.
GatewaysGateway upgrades are not part of the core upgrade procedure.
For information about upgrading gateways, see the IBM Tivoli Netcool PerformanceManager Gateways Installation Note.
Upgrading the platform packageBefore you start the upgrade, you must install the latest version of the Platformpackage that is provided with your software distribution. The Platform packagecontains scripts that help you to prepare your system for an upgrade, and somesystem administration functions.
About this task
Note: In a distributed installation, the Platform package must be installed on allTivoli Netcool Performance Manager servers.
There is no need to remove the old Platform package.
The name of the Platform package file is ibm-tn-plat-install-PLAT<version>.tar.gz.
Chapter 1. Pre-upgrade tasks 7
The Platform package consists of the 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
Procedure1. Copy the package file into a directory on the Tivoli Netcool Performance
Manager server.2. Extract the package contents as user root:
gzip -dc ibm-tn-plat-install-PLAT<version>.tar.gz | tar xf -
3. Run the installation script as user root:./ibm-tn-plat-install.install now
The platform package is installed under: /var/install.
Stopping Tivoli Netcool Performance Manager clientsAll Tivoli Netcool Performance Manager clients must be stopped before youcontinue with the upgrade. Notify all users that an upgrade is taking place.
Stopping the application server and loadersRun the required CLI commands to stop the application server and loaders.
Before you begin
Note: In a distributed installation, this procedure must be performed for theapplication server only.
Procedure1. To stop the application server and loaders processes, run the following
command as user virtuo:sap stop -f
2. To check that all the processes are stopped, run the following command as uservirtuo:sap disp
Stopping the Tivoli Netcool Performance Manager frameworkRun the required CLI commands to stop and to monitor the process state of theTivoli Netcool Performance Manager framework.
About this task
Note: In a distributed installation, this procedure must be performed for theapplication server only.
Procedure1. Run the following command as user virtuo:
sap stop -f
2. To monitor the process state, run the command as user root:
8 IBM Tivoli Netcool Performance Manager: Upgrade Guide
v svcs sap-na
v service sapvirtuo status
v /etc/rc.d/init.d/sapvirtuo status
Stopping the SAP managerStopping the SAP manager and confirming that it is stopped.
About this task
Note: In a distributed installation, this procedure must be performed for theapplication server only.
Procedure1. Run the command as user root:
v svcadm disable sapmgr-na
v service sapmgrvirtuo stop
v /etc/rc.d/init.d/sapmgrvirtuo stop
2. To monitor the process state, run the command as user root:
v svcs sapmgr-na
v service sapmgrvirtuo status
v /etc/rc.d/init.d/sapmgrvirtuo status
Stopping the SAP monitorStopping and monitoring the SAP monitor for the application and loader serveronly.
About this task
Note: In a distributed installation, this procedure must be performed for theapplication and loader server only.
To stop the SAP monitor:
Procedure1. Run the command as user root:
v svcadm disable sapmon-na
v service sapmonvirtuo stop
v /etc/rc.d/init.d/sapmonvirtuo stop
2. To monitor the process state, run the command:
v svcs sapmon-na
v service sapmonvirtuo status
v /etc/rc.d/init.d/sapmonvirtuo status
Chapter 1. Pre-upgrade tasks 9
Running the Dependency Checker toolThe 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:
10 IBM Tivoli Netcool Performance Manager: Upgrade Guide
./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: OKChecking 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: OK
Chapter 1. Pre-upgrade tasks 11
Checking 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
-------------------------------------------------------------Checking for JBoss package-------------------------------------------------------------
-------------------------------------------------------------
12 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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 “Dependency Checker errors,” on page 45.
Chapter 1. Pre-upgrade tasks 13
Upgrading to Oracle 11g (11.2.0.4)You must manually upgrade Oracle 11.2.0.3 to 11.2.0.4.
For stand-alone server, manually upgrade the Oracle database and instance client.For distributed server (Application server/Tivoli Common Reporting server),manually upgrade the Oracle client and instant client. For distributed server (dbserver), manually upgrade the Oracle database.
Note: Copy the *ora files from old ORACLE_HOME/network/admin to the newORACLE_HOME/network/admin directory. Example: cp /appl/oracle/product/11.2.0/db_1/network/admin/*ora /appl/oracle/product/11.2.0/db_2/network/admin/
Restarting the databaseIn a distributed installation, this procedure must be performed for the databaseserver only.
About this task
Use the command to verify whether the database is running or not:
svcs database-na
service dboravirtuo status
/etc/rc.d/init.d/dboravirtuo status
To restart the database:
Procedure
Run the command as user root:
v Stop a database service:svcadm disable database-na
Wait until the database instance is down; the command returns no rows:ps -ef|grep smon
Start a database instance:svcadm enable database-na
v Stop a database service:service dboravirtuo stop
Wait until the database instance is down; the command returns no rows:ps -ef|grep smon
Start a database instance:service dboravirtuo start
v Stop a database service:/etc/rc.d/init.d/dboravirtuo stop
Wait until the database instance is down; the command returns no rows:ps -ef|grep smon
14 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Start a database instance:/etc/rc.d/init.d/dboravirtuo start
Upgrading the Tivoli Directory Server and IBM DB2Tivoli Netcool Performance Manager, 1.4.1 supports the Security Directory Server6.3.1 and IBM DB2 9.7.0.6. If you installed these versions, you can ignore thissection.
Before you begin
The required packages for the installation are distributed on the Tivoli NetcoolPerformance Manager installation media.
Security Directory Server and IBM DB2 require certain minimum versions on theserver before upgrade.
About this task
Note: Perform these procedures on a stand-alone server, directory server, orapplication server.
The upgrade procedure installs the required Security Directory Server and DB2software versions on the system and migrates the DB2 instance from the previousversion. The previous Tivoli Directory Server and DB2 versions remains on thesystem so that they can be rolled back if necessary. If the new version validates onthe system and it is certain that a rollback is not required, remove the old versionfrom the system. See Removing the previous Tivoli Directory Server version.
Procedure1. Stop the tdsna.
For AIX, run the following command:/etc/rc.d/init.d/tdsna stop
For Solaris, run the following command:svcadm disable tds-na
For Linux, run the following command:service tdsna stop
2. To install Security Directory Server 6.3.1 and DB2 fix pack, run the followingcommand as the root user:/var/install/sbin/sds_install -base /appl -product virtuo -version 6.3.1 -upgradeEnter the full pathname of the DS package:/appl/depends/sds631/sds631-linux-x86-64-base.tarEnter the full pathname of the DS DB2 package:/appl/depends/sds631/sds631-linux-x86-64-db2.tarEnter the full pathname of the GSK package:/appl/depends/sds631/sds631-linux-x86-64-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 ServerNo domain name configured.Shutting down TDS....... Unpacking IBM Security Directory Server.|||Backing up the DB2 database...DoneBacking up configuration and schema files...Done.... Installing IBM DB2 ESE. This may take several minutes...|WARNING:DBT3534W The db2prereqcheck utility determined that ASLR is set to ON and that
Chapter 1. Pre-upgrade tasks 15
this could cause issues with some tools.WARNING:The 32-bit library file libpam.so is not found on the system.WARNING:DBT3534W The db2prereqcheck utility determined that ASLR is set to ON and thatthis could cause issues with some tools.WARNING:The 32-bit library file libpam.so is not found on the system.AIX 6.x detected - DB2 ESE failure is most likely related to AIO.If TDS is configured and started successfully, this condition can be ignored.Please check /tmp/db2_install.log.7789 when this program completes..... log can be seen in /var/install/logs/sds_install_6738.log and /tmp/db2_install.log.7789.... Installing IBM GSKIT...|....done....done.... Installing IBM Security Directory Server. This may take several minutes...International Program License Agreement
..Press Enter to continue viewing the license agreement, or, Enter "1" to accept the agreement,"2" to decline it or "99" to go back to the previous screen, "3" Print.1\....Done. Log can be seen in /var/install/logs/sds_install_6738.logRemoving temporary install files...|Migrating TDS instance from version 6.3. This may take several minutes...|DoneGenerating sds startup scripts ....Starting SDS processes...Done.
Note: See /var/install/logs/install_db2_patch_14134.log for log details.
Locating the required packagesThe required packages for the installation are distributed on the Tivoli NetcoolPerformance Manager installation media in the folder depends/tds63.
v IBM Security Directory Server 6.3.1 Client-Server with entitlement Solaris(sds631-solaris-sparc-base.tar)
v IBM Security Directory Server 6.3.1 GSkit Solaris (sds631-solaris-sparc-gskit.tar)
v IBM Security Directory Server 6.3.1, DB2 v 9.7 Solaris (sds631-solaris-sparc-db2.tar)
v IBM Security Directory Server 6.3.1 Client-Server with entitlement Linux x86-64(sds631-linux-x86_64-base.tar)
v IBMSecurity Directory Server 6.3.1 GSkit Linux x86-64 (sds631-linux-x86_64-gskit.tar)
v IBM Security Directory Server 6.3.1, DB2 v 9.7 Linux x86-64 (sds631-linux-x86_64-db2.tar)
v IBM Security Directory Server 6.3.1 Client-Server with entitlement AIX(sds631-aix-ppc64-base.tar)
vIBM Security Directory Server 6.3.1 GSkit AIX (sds631-aix-ppc64-gskit.tar)
v IBM Security Directory Server 6.3.1, DB2 v 9.7 AIX (sds631-aix-ppc64-db2.tar)
16 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Required DB2 patches
v9.7fp6_aix64_universal_fixpack.tar.gz
v9.7fp6_linuxx64_universal_fixpack.tar.gz
v9.7fp6_sun64_universal_fixpack.tar.gz
Checking the installed versionsTivoli Netcool Performance Manager, version 1.4.1 supports IBM Security DirectoryServer 6.3.1 and DB2 9.7 Fix Pack 6.
Procedure1. Run the following command as root user to check the Security Directory Server
version that is installed: # /opt/IBM/ldap/V6.3.1/bin/idsversion
2. Run the following command as root user check the DB2 version that isinstalled: # /usr/local/bin/db2ls
Upgrading Jazz for Service ManagementThe Jazz™ for Service Management installation supports different installation andupgrade scenarios, user types, installation modes, and server topologies dependingon your organization needs and target server environments. You can use either alaunchpad or IBM Installation Manager to install and configure Jazz for ServiceManagement. You can install and configure one or more integration services on aone, two, or three servers. You can optionally install IBM DB2® and IBMWebSphere® 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
Chapter 1. Pre-upgrade tasks 17
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
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.
18 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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/registry
Chapter 1. Pre-upgrade tasks 19
v 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
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/
20 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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
Preparing your environment for a full installation of Jazz forService Management
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 22.
Related information:
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
Chapter 1. Pre-upgrade tasks 21
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/Related information:
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 24.
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.
22 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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 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:
Chapter 1. Pre-upgrade tasks 23
Applying fix packs
Jazz for Service Management Version 1.1.1.0 Readme
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.
24 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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.
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.
Chapter 1. Pre-upgrade tasks 25
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 22
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 2. Location of the db2ese.rsp file
Option Description
On AIX systems Install_Imgs_Home/ese/db2/aix/samples
On Linux systems Install_Imgs_Home/ese/db2/linuxamd64/samples
26 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Table 2. Location of the db2ese.rsp file (continued)
Option Description
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.
What to do next
If you cannot access the web page in step 3, restart Jazz for Service Managementapplication server.
Chapter 1. Pre-upgrade tasks 27
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– host.domain is the fully qualified host name or IP address of the Jazz for
Service 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 Management
28 IBM Tivoli Netcool Performance Manager: Upgrade Guide
reporting 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.
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.
Chapter 1. Pre-upgrade tasks 29
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
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:
30 IBM Tivoli Netcool Performance Manager: Upgrade Guide
./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
Upgrading Tivoli Common ReportingYou can upgrade from previous versions of Tivoli Common Reporting to theversions of integration service in Jazz™ for Service Management V1.1.1.0. You canupgrade your Tivoli Common Reporting versions 2.1, and later to Version 3.1.0.2.The upgrade is a manual procedure in which you first create packages with data,and then move the data to a previously installed Tivoli Common ReportingVersion 3.1.0.2.
About this task
Note: There is no change in the supported Tivoli Common Reporting version fromTivoli Netcool Performance Manager 1.4.0.v The upgrade is a side-by-side process, which results in two instances of Tivoli
Common Reporting on your system - the Version 3.1.0.2 and the older version.To keep only the newest version of Tivoli Common Reporting on your computer,uninstall the older version. If your content store is less than 1 GB, see“Upgrading from Tivoli Common Reporting 2.1 and 2.1.1” on page 36Users and groups are not migrated because they are stored in LDAP. You canuse the DASH_HOME\upgrade\bin\exportLDAPconfig.sh file to export the LDAPsettings. The installer creates tipadmin as the default user present before andafter upgrade.
Chapter 1. Pre-upgrade tasks 31
v If your content store is more than 1 GB, see “Upgrading the content store fromolder versions of Tivoli Common Reporting” on page 37.
Adding the LDAP user registry as a federated repositoryAfter setting up the LDAP server, you must add it as a federated repository in theFederated Repositories > Repository references > New window.
About this task
To add a new LDAP repository:
Procedure1. Log in to Dashboard Application Services Hub.2. In the navigation pane, click Console Settings > Websphere Administrative
Console and click Launch Websphere administrative console.3. In the WebSphere Application Server administrative console navigation pane,
click Security > Global security.4. From the Available realm definitions list, select Federated repositories and
click Configure.5. In the Related Items area, click the Manage repositories link and then click
Add repositories to add the LDAP user registry as a federated repository.6. Click New Repository > LDAP repository.7. In the Repository identifier field, provide a unique identifier for the
repository. The identifier uniquely identifies the repository within the cell, forexample, LDAP1
8. From the Directory type list, select the type of LDAP server. The type ofLDAP server determines the default filters that are used by WebSphereApplication Server.
9. In the Primary host name field, enter the fully qualified host name of theprimary LDAP server. The primary host name and the distinguished namemust contain no spaces. You can enter either the IP address or the domainname system (DNS) name.
10. In the Port field, enter the server port of the LDAP user registry password.The host name and the port number represent the realm for this LDAP serverin a mixed version nodes cell. If servers in different cells are communicatingwith each other using Lightweight Third Party Authentication (LTPA) tokens,these realms must match exactly in all the cells.
Note: The default port value is 389, which is not a Secure Sockets Layer (SSL)connection port. Use port 636 for a Secure Sockets Layer (SSL) connection. Forsome LDAP servers, you can specify a different port. If you do not know theport to use, contact your LDAP server administrator.
11. Optional: In the Bind distinguished name and Bind password fields, enterthe bind distinguished name (DN) (for example, cn=root) and password.
Note: The bind DN is required for write operations or to obtain user andgroup information if anonymous binds are not possible on the LDAP server.In most cases, a bind DN and bind password are needed, except when ananonymous bind can satisfy all of the required functions. Therefore, if theLDAP server is set up to use anonymous binds, leave these fields blank.
32 IBM Tivoli Netcool Performance Manager: Upgrade Guide
12. Optional: In the Login properties field, enter the property names used to loginto the WebSphere Application Server. This field takes multiple loginproperties, delimited by a semicolon (;). For example, cn.
13. From the Certificate mapping list, select your preferred certificate map mode.You can use the X.590 certificates for user authentication when LDAP isselected as the repository.
Note: The Certificate mapping field is used to indicate whether to map theX.509 certificates into an LDAP directory user by EXACT_DN orCERTIFICATE_FILTER. If you select EXACT_DN, the DN in the certificate mustmatch the user entry in the LDAP server, including case and spaces.
14. Click Apply and then Save
15. Log out of the WebSphere administrative console.
What to do next
Configure the Jazz for Service Management server to communicate with anexternal LDAP repository.
Configuring the LDAP federated repositoryYou can configure each Jazz™ for Service Management application server to useand communicate with the LDAP federated repository.
About this task
In a Jazz for Service Management distributed environment or in a DashboardApplication Services Hub load balanced environment, all application serverinstances must be configured separately for the LDAP server.
Procedure1. Log in to Dashboard Application Services Hub.2. In the navigation pane, click Console Settings > Websphere Administrative
Console and click Launch Websphere administrative console.3. In the WebSphere Application Server administrative console navigation pane,
click Security > Global security.4. From the Available realm definitions list, select Federated repositories and
click Configure.5. To add an entry to the base realm:
a. Ensure that the LDAP federated repository is selected from the Repositorylist.
b. In the field, enter the distinguished name (DN) of a base entry thatuniquely identifies this set of entries in the realm. This base entry mustuniquely identify the external repository in the realm.
Note: If multiple repositories are included in the realm, use the DN field todefine an additional distinguished name that uniquely identifies this set ofentries within the realm. For example, repositories LDAP1 and LDAP2might both use o=ibm,c=us as the base entry in the repository. Soo=ibm,c=us is used for LDAP1 and o=ibm2,c=us for LDAP2. The specifiedDN in this field maps to the LDAP DN of the base entry within therepository (such as o=ibm,c=us b). The base entry indicates the startingpoint for searches in this LDAP server (such as o=ibm,c=us c).
c. Click Apply and then Save.
Chapter 1. Pre-upgrade tasks 33
6. In the WebSphereadministrative console, select Security > Global security.7. From the Available realm definitions list, select Federated repositories and
click Set as current to mark the federated repository as the current realm.8. Restart each Jazz for Service Management application server.9. Verify that the federated repository is correctly configured:
a. In the Dashboard Application Services Hub navigation pane, click Usersand Groups > Manage Users.
b. Select User ID from the Search by list.c. Click Search to search for users in the federated repository.d. Confirm that the list includes users from both the LDAP repository and the
local file registry.On the Jazz for Service Management application server, LDAP users arequeried only by the userid attribute. When users are imported into LDAPfederated repository by using an LDAP Data Interchange Format (LDIF) file,an auxiliary class of type eperson and an uid attribute is added to theLDAP user ID. Only perform this task, if you want to search the LDAPfederated repository by using VMM from the server.
What to do next
You can create or manage users in Dashboard Application Services Hub that aredefined in your LDAP federated repository. In the WebSphere administrativeconsole, you must specify the supported entity types.
Single sign-onThe single sign-on (SSO) capability in Tivoli products means that you can log on toone Tivoli application and then launch to other Tivoli Web-based or Web-enabledapplications without having to re-enter your user credentials.
The repository for the user IDs can be the Tivoli Netcool/OMNIbus ObjectServeror a Lightweight Directory Access Protocol (LDAP) registry. A user logs on to oneof the participating applications, at which time their credentials are authenticatedat a central repository. With the credentials authenticated to a central location, theuser can then launch from one application to another to view related data orperform actions. Single sign-on can be achieved between applications deployed toJazz for Service Management servers on multiple machines.
Single sign-on capabilities require that the participating products use LightweightThird Party Authentication (LTPA) as the authentication mechanism. When SSO isenabled, a cookie is created containing the LTPA token and inserted into the HTTPresponse. When the user accesses other Web resources (portlets) in any otherapplication server process in the same Domain Name Service (DNS) domain, thecookie is sent with the request. The LTPA token is then extracted from tDahecookie and validated. If the request is between different cells of application servers,you must share the LTPA keys and the user registry between the cells for SSO towork. The realm names on each system in the SSO domain are case sensitive andmust match exactly.
34 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Configuring single sign-onUse these instructions to establish single sign-on support and configure a federatedrepository.
Before you begin
Configuring SSO is a prerequisite to integrating products that are deployed onmultiple servers. All Jazz for Service Management Server instances must point tothe central user registry (such as a Lightweight Directory Access Protocol server).
Attention: ITM single sign on (SSO) support is only available with ITM Version6.2 Fix Pack 1 or higher.
About this task
To configure the WebSphere federated repositories functionality for LDAP:
Procedure1. Log in to Dash.2. In the navigation pane, click Console Settings > Websphere Administrative
Console and click Launch Websphere administrative console.3. In the WebSphere Application Server administrative console navigation pane,
click Security > Global security.4. In the Authentication area, expand Web security and click Single sign-on.5. Click the Enabled option if SSO is disabled.6. Click Requires SSL if all of the requests are expected to use HTTPS.7. Enter the fully-qualified domain names in the Domain name field where SSO
is effective. If the domain name is not fully qualified, the Jazz for ServiceManagement Server does not set a domain name value for the LtpaTokencookie and SSO is valid only for the server that created the cookie. For SSO towork across Tivoli applications, their application servers must be installed insame domain (use the same domain name).
8. Optional: Enable the Interoperability Mode option if you want to supportSSO connections in WebSphere Application Server version 5.1.1 or later tointeroperate with previous versions of the application server.
9. Optional: Enable the Web inbound security attribute propagation option ifyou want information added during the login at a specific Tivoli EnterprisePortal Server to propagate to other application server instances.
10. After clicking OK to save your changes, stop and restart all the Jazz forService Management Server instances.
What to do next
Note: When you launch Jazz for Service Management, you must use a URL in theformat protocol://host.domain:port /*. If you do not use a fully-qualifieddomain name, Jazz for Service Management cannot use SSO between Tivoliproducts.
Chapter 1. Pre-upgrade tasks 35
Upgrading from Tivoli Common Reporting 2.1 and 2.1.1Upgrade your Tivoli Common Reporting Version 2.1 or 2.1.1 to Version 3.1.0.2.
Before you begin
Perform these tasks before you upgrade:v Install Jazz for Service Managementv Install Tivoli Common Reporting 3.1.0.2
About this task
During the upgrade procedure, IBM Cognos configuration is not migrated, youmust migrate it manually.
Perform this task as an administrative user.
Procedure
Follow these steps if the content store is less than 1 GB.1. Run the following command to create a package with Tivoli Common
Reporting 2.1 and later data:
TCR_2x_install_dir/profiles/TIPProfile/upgrade/bin/preupgrade.shpreupgrade tip_path -username user -password user_pass --productId TCR-ignoreTIPCharting true
By default, the TCR_2x_install_dir is /opt/IBM/tivoli/tipv2
TCR_2x_install_dir/profiles/TIPProfile/upgrade/bin/preupgrade.shpreupgrade tip_path -username user -password user_pass --productId TCR
By default, the TCR_2x_install_dir is /opt/IBM/tivoli/tipv2
Note: If you hit out of memory error, increase xmx in preupgrade.sh 64 - 512.The package is created in the following location:TCR2x_install_dir\profiles\TIPProfile\upgrade\data\upgradeData.zip.
2. Copy the upgradeData.zip package to the computer with Tivoli CommonReporting Version 3.1.0.2.
Note: The reports that are saved in private folders are not be available whenyou migrate to the new Tivoli Common Reporting if:v You are not migrated to the LDAP repository.v The users were created before the LDAP repository was configured.
You must move the reports to public folders and then take a back up.3. Go to REPORTING_HOME\bin\ and run the following command to import the
package:
./trcmd.sh -upgrade-importPackage path_to_upgradeData.zip-username <username> -password <password>
The default username is smadmin.
36 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Results
You have upgraded your Tivoli Common Reporting to Version 3.1.0.2 together withall your reporting data. The following items were moved to Version 3.1.0.2:v The content of the Content Store, which includes reporting artifacts such as
report designs, saved reports, and schedules.
Note: This move applies only if you used the embedded database in theprevious Tivoli Common Reporting instance. If you used an external database asContent Store, you must migrate its content manually.
v Static resources for Cognos reports, such as images, css, and js files.
What to do next1. Verify whether Tivoli Common ReportingVersion 3.1.0.2 works correctly, the
migrated reports are available and can be run.2. Finish configuring Cognos. Open the Cognos Configuration by running:
v c10_location/bin64/tcr_cogconfig.sh
Supply the missing information such as mail server details to email yourreports, cryptography settings, and authentication details.
3. Configure Tivoli Common Reporting 3.1.0.2 to connect to Oracle database(vtdb).
Upgrading the content store from older versions of TivoliCommon Reporting
If you are using Derby as the content store for Tivoli Common Reporting, you areencouraged to plan a migration to a supported enterprise database like IBM DB2or Oracle.
If you Derby database size is more than 1 GB, follow the instructions in thisdocument:https://www.ibm.com/developerworks/mydeveloperworks/files/form/anonymous/api/library/9641dcf4-c5b8-413c-8ae8-9c461dd84a09/document/0cdff487-dee6-4070-941c-f40ed8d0afd1/media/Exporting-Importing%20Derby%20Content%20Store_v01.pdf
Chapter 1. Pre-upgrade tasks 37
38 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Chapter 2. Tivoli Netcool Performance Manager SoftwareUpgrade
Steps to upgrade Tivoli Netcool Performance Manager software to the currentversion.
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
© Copyright IBM Corp. 2006, 2015 39
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>
40 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Pre-upgrade checklistBefore you continue with the upgrade, ensure that the pre-upgrade steps arecomplete without errors.
Procedure Topic
The correct platform package is installed. The Platform package
Important: Before you attempt an upgrade of Tivoli Netcool PerformanceManager, you are advised to read any Release Notes and any readme files that aredistributed with your Tivoli Netcool Performance Manager software. Release Notesand readme files can contain information specific to your upgrade not contained inthis guide. Failure to consult the Release Notes or readme files can result in acorrupted, incomplete, or failed installation. For all current known issues, see theKnown issues technical note for the current version.
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 41
42 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Chapter 3. Enabling Tivoli Common Reporting on TivoliNetcool Performance Manager
Once you upgrade the core system, install the latest version of Tivoli NetcoolPerformance Manager - Application Studio tool to enable Common Reporting onTivoli Netcool Performance Manager.
If you previously used the Tivoli Netcool Performance Manager - ApplicationStudio tool with your Tivoli Netcool Performance Manager 1.3.2 system, you mustupgrade to the latest version.
For more information about installing or upgrading Tivoli Netcool PerformanceManager - Application Studio, see the latest versions of the following guides:v Installing and using Tivoli Netcool Performance Manager - Application Studio
v Installing Tivoli Netcool Performance Manager - Wireless Component, EnablingCommon Reporting on Tivoli Netcool Performance Manager.
v Installing and using Model Maker. Model Maker is used for the legacy Cognos 8models.
© Copyright IBM Corp. 2006, 2015 43
44 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Appendix. 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 <SOLARIS_UPDATE>:required level is <REQUIRED_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 <dir>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>
© Copyright IBM Corp. 2006, 2015 45
-------------------------------------------------------------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>-------------------------------------------------------------
46 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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. Dependency Checker errors 47
48 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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
© Copyright IBM Corp. 2006, 2015 49
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:
50 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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 51
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.
52 IBM Tivoli Netcool Performance Manager: Upgrade Guide
����
Printed in USA
