Embed Size (px)
Citation preview
IBM Tivoli Netcool Performance Manager 1.4.3Wireless ComponentDocument Revision R2E1
Upgrade Guide
IBM
NoteBefore using this information and the product it supports, read the information in “Notices” on page 91.
© Copyright IBM Corporation 2006, 2017.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 12c (12.1.0.2)upgrade . . . . . . . . . . . . . . . . 1Server hardware and software requirements . . . . 1
Server hardware requirements . . . . . . . 1Server software requirements . . . . . . . . 2
Gateways . . . . . . . . . . . . . . . 7Setting kernel parameters . . . . . . . . . . 7Upgrading the platform package . . . . . . . 8Stopping Tivoli Netcool Performance Manager clients 8Stopping the application server and loaders . . . . 9Stopping the Tivoli Netcool Performance Managerframework . . . . . . . . . . . . . . . 9Stopping the SAP manager . . . . . . . . . 9Stopping the SAP monitor . . . . . . . . . 10Stopping the Tivoli Netcool Performance Managercron jobs . . . . . . . . . . . . . . . 10Checking the database status . . . . . . . . 11Running the Dependency Checker tool . . . . . 13Running Oracle installation with upgrade option . . 17Upgrading Jazz for Service Management . . . . 19
Hardware and software requirements forinstalling Jazz for Service Management . . . . 19Common directory locations for Jazz for ServiceManagement . . . . . . . . . . . . . 20Quick reference to Jazz for Service Managementinstallation . . . . . . . . . . . . . 23Disabling the Cognos Application Firewall forbrowser security . . . . . . . . . . . . 27Verifying the installation . . . . . . . . . 27Uninstalling Jazz for Service Management . . . 30
Adding the LDAP user registry as a federatedrepository . . . . . . . . . . . . . . . 30
Configuring the LDAP federated repository . . 32Single sign-on . . . . . . . . . . . . 33Configuring single sign-on . . . . . . . . 33
Upgrading Tivoli Common Reporting . . . . . 34Upgrading Tivoli Common Reporting to 3.1.3.0 35Upgrading the content store from older versionsof Tivoli Common Reporting . . . . . . . 36
Chapter 2. Tivoli Netcool PerformanceManager Software Upgrade . . . . . . 37Archiving the previous release . . . . . . . . 37Upgrade scenarios . . . . . . . . . . . . 38Upgrading Tivoli Netcool Performance Manager onOracle Solaris 11 . . . . . . . . . . . . . 38Upgrading a stand-alone system . . . . . . . 39
Configuring core software . . . . . . . . 40Upgrading the JBoss application server . . . . 41Cronjob installation. . . . . . . . . . . 42Restoring configuration . . . . . . . . . 43Migrating loaders . . . . . . . . . . . 43Synchronizing users . . . . . . . . . . 44Encoding Passwords . . . . . . . . . . 44
Upgrading a distributed system . . . . . . . 45Running an interactive upgrade . . . . . . 45Upgrading the database server . . . . . . . 45Upgrading a separate directory server . . . . 49Upgrading the application server . . . . . . 52Upgrading the loader server . . . . . . . . 56
Editing the default.properties file . . . . . . 60Optional: Compiling SQL packages for ncmanagerand ncarchiver manually. . . . . . . . . . 60
Chapter 3. Upgrading the SecurityDirectory Server and IBM DB2 . . . . 63Upgrading from Tivoli Directory Server v6.3 toSecurity Directory Server v6.4 . . . . . . . . 64Manually cleaning up after a failed upgrade orinstallation of Security Directory Server . . . . . 66Locating the required packages . . . . . . . . 67Checking the installed versions . . . . . . . . 67
Chapter 4. Post-upgrade tasks . . . . 69Customizing JBoss settings . . . . . . . . . 70Process checks for Solaris . . . . . . . . . . 70Process checks for Linux . . . . . . . . . . 71Process checks for AIX. . . . . . . . . . . 72Checking SAP process . . . . . . . . . . . 73Rebooting the server . . . . . . . . . . . 73Starting the SAP services . . . . . . . . . . 74Tivoli Netcool Performance Manager core processesstop/start . . . . . . . . . . . . . . . 74Starting the loaders . . . . . . . . . . . . 75
© Copyright IBM Corp. 2006, 2017 iii
Chapter 5. Enabling Tivoli CommonReporting on Tivoli NetcoolPerformance Manager . . . . . . . . 77
Chapter 6. Rolling back to the previousTivoli Netcool Performance Managerversion . . . . . . . . . . . . . . 79Stopping Tivoli Netcool Performance Managerclients . . . . . . . . . . . . . . . . 79Stopping the Tivoli Netcool Performance Managerframework . . . . . . . . . . . . . . 79Stopping the SAP manager . . . . . . . . . 80Stopping the SAP monitor . . . . . . . . . 80Stopping the directory server . . . . . . . . 81
Restoring the previous version of software . . . . 81Checking process . . . . . . . . . . . . 82
Checking process status . . . . . . . . . 82Stopping and starting the Tivoli NetcoolPerformance Manager core processes . . . . . 85
Starting the Tivoli Netcool Performance Managercron jobs . . . . . . . . . . . . . . . 85
Appendix. Dependency Checker errors 87
Notices . . . . . . . . . . . . . . 91Trademarks . . . . . . . . . . . . . . 93Terms and conditions for product documentation. . 94
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.
Integrating with Tivoli Monitoring - WirelessComponent
Provides instructions for integrating IBM TivoliMonitoring with Tivoli Netcool PerformanceManager.
© Copyright IBM Corp. 2006, 2017 v
Table 1. Tivoli Netcool Performance Manager - Wireless component userdocumentation (continued)
Document Description
Integrating with Tivoli Netcool/OMNIbus Web GUI -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.2 to 1.4.3.
Upgrading to Tivoli Netcool Performance Manager 1.4.3 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 12c (12.1.0.2) upgradeThe supported upgrade path is from Tivoli Netcool Performance Manager 1.4.2 to1.4.3. Therefore, you do not require to upgrade your Oracle database that isalready at version 12.1.0.2.
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 POWER7 and POWER8 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, 2017 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) 7.x
v IBM AIX 7.1
v Oracle Solaris 11
v MicrosoftWindows 7 (For Cognos® 10 modelsthat are created by using Tivoli NetcoolPerformance Manager - Application Studio ).
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 12.1.0.2.0, 64-bitwith partitioning option.Note: Oracle 12.1.0.2.0 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.3.0
Tivoli Common Reporting 3.1.3.0
JBoss Application Server 4.0.3 Service Pack 1
Perl 5.6.1 for Gateway servers on Solaris and RHEL
Related information:
Download Jazz for Service Management Version 1.1.3.0
Bundled softwareThe software that is bundled with Tivoli Netcool Performance Manager.
Product Version
IBM Security Directory Server (required) 6.4
IBM DB2 (required) 10.5 (version 10.5.0.3)
2 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Product Version
IBM Tivoli Monitoring agent script(optional)
6.3
IBM Java 1.8.0 SR3 FP20 64-bit
Location of the Tivoli Netcool Performance Manager softwareNote the location of the Tivoli Netcool Performance Manager software before youstart the installation.
In addition to the Tivoli Netcool Performance Manager software, the followingIBM products are included.v IBM Security Directory Serverv Jazz for Service Managementv WebSphere Application Serverv Tivoli Common Reportingv IBM DB2v IBM Tivoli Monitoring
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 TNPMWAppserverAgent.tar.gz
v TNPMWGatewayAgent.tar.gz
v TNPMWLoaderAgent.tar.gz
Location of Oracle Solaris software
Chapter 1. Pre-upgrade tasks 3
For each server that runs on Oracle Solaris, a full installation (all components) ofSolaris 11 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 SUNWeu8os
Note: In Solaris 11, some packages are renamed and some are obsolete. Make surethat renamed packages are installed. The obsolete packages can be ignored.
Renamed packages:v SUNWhea renamed to consolidation/osnet/osnet-incorporationv SUNWsprot renamed to consolidation/sunpro/sunpro-incorporation
Obsolete packages:v SUNWi15csv SUNWeu8os
Extra Solaris packages required for installing Oracle 12c:
The following packages (or later versions) are required for Oracle database 12c forOracle Solaris.SUNWarcSUNWbtoolSUNWheaSUNWlibCSUNWlibmSUNWlibmsSUNWsprotSUNWtooSUNWi1ofSUNWi1cs (ISO8859-1)SUNWi15cs (ISO8859-15)SUNWxwfntSUNWcslSUNWeu8os
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 13 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:
4 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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 12.1.0.2:
Before you install Oracle 12c on an RHEL server, install each of the followingpackages (specified versions or higher) on the server.
RHEL 7.xbinutils,2.23.52.0.1,16.el7,x86_64compat-db,4.7.25,27.el7,x86_64compat-libstdc++-33,3.2.3,71.el7,x86_64compat-libstdc++-33,3.2.3,71.el7,i686control-center,3.8.6,15.el7,x86_64elfutils-libelf-devel,0.158,3.el7,x86_64gcc,4.8.2,16.2.el7,x86_64gcc-c++,4.8.2,16.2.el7,x86_64glibc,2.17,55.el7,x86_64glibc,2.17,55.el7,i686glibc-common,2.17,55.el7,x86_64glibc-devel,2.17,55.el7,x86_64glibc-devel,2.17,55.el7,i686glibc-headers,2.17,55.el7,x86_64libgcc,4.8.2,16.2.el7,x86_64libgcc,4.8.2,16.2.el7,i686libaio,0.3.109,12.el7,x86_64libaio,0.3.109,12.el7,i686libaio-devel,0.3.109,12.el7,x86_64libaio-devel,0.3.109,12.el7,i686libstdc++,4.8.2,16.2.el7,x86_64libstdc++-devel,4.8.2,16.2.el7,x86_64libgomp,4.8.2,16.2.el7,x86_64libXp,1.0.2,2.1.el7,x86_64make,3.82,21.el7,x86_64sysstat,10.1.5,4.el7,x86_64
Extra RHEL packages required for installing IBM Security Directory Server andIBM DB2:
Before you install IBM Security Directory Server and IBM DB2 on an RHEL server,you must install each of the following packages (specified versions or higher) onthe server.
RHEL 7.xcompat-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_64
Chapter 1. Pre-upgrade tasks 5
glibc-headers,2.5,18,x86_64glibc-devel,2.5,18,x86_64glibc-devel,2.5,18,i386libgomp,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 7.xcompat-libstdc++-33,3.2.3,71.el7,x86_64compat-libstdc++-33,3.2.3,71.el7,i686glibc,2.17,55.el7,x86_64glibc,2.17,55.el7,i686motif,2.3.4,7.el7,x86_64
Related information:
Jazz for Service Management Detailed System Requirements
Reporting Services requirements
Location of AIX software
For each server that runs on AIX, a full installation (all components) of AIX 7.1must be available on the server. Ensure that you have the required AIX softwarebefore you start with the installation.
Extra AIX packages required for installing Oracle 12c:
Before you install Oracle 12c 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.proctools
AIX packages for AIX 6.1xlC.aix61.rte:9.0.0.1 or laterxlC.rte:9.0.0.1 or later
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.
6 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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.
Setting kernel parametersSetting the appropriate ulimit values on your operating system can affect how theOracle database performs.
About this task
Follow these commands on different operating systems to set ulimits:
Procedure
v ulimit –n 65536
Do not restart the system after this task or close session. If needed, set theulimits again.
v Add the following lines to etc/security/limits.conf file:* soft nofile 65536* hard nofile 65536* soft nproc 65536* hard nproc 65536
Restart the system after this taskIf the limits.conf file is not available then run system configuration by using thefollowing steps:v To configure the kernel, run the following commands as root on the database
and application servers:
# /var/install/sbin/system_configure
The system_configure command must be run on the global zone.v Restart the server by using the appropriate commands:
# /usr/sbin/shutdown -i6 -g0 -y
Note: This command updates /etc/system file and the original file/etc/system.backup.IBM.<datestamp> is backed up.
# shutdown -r now
Chapter 1. Pre-upgrade tasks 7
Note: This command updates /etc/sysctl.conf file and the original file/etc/original_sysctl.conf is backed up.
# shutdown –Fr
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.
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 the following folder:/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.
8 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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:
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:
Chapter 1. Pre-upgrade tasks 9
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
Stopping the Tivoli Netcool Performance Manager cron jobsStop all of the Tivoli Netcool Performance Manager cron jobs on each server.
About this task
To edit the crontab directly, you need to modify the following virtuo files.
Procedure1. Edit the following files:
v /var/spool/cron/crontabs/virtuo
v /var/spool/cron/crontabs/virtuo
v /var/spool/cron/virtuo
2. Insert a comment (#) at the start of the lines that contain the following jobs:v /appl/virtuo/bin/alarmapi_admin -da
v /appl/virtuo/bin/run_loader_cleanup
v /appl/virtuo/bin/run_itm_rawcoverage_logger
v /appl/virtuo/bin/run_itm_usage_logger
3. Restart the cron daemons:
10 IBM Tivoli Netcool Performance Manager: Upgrade Guide
vps -ef | egrep [c]ron | awk ’{ print $2 }’ | xargs kill
vsvcadm restart cron
vsystemctl restart crond.service
Checking the database statusYou must check the current state of the Tivoli Netcool Performance Managerdatabase before performing the upgrade. Do not proceed with the databaseupgrade if any database components or objects are in an INVALID state or if anyconstraints are in DISABLED state.
About this task
Note: In a distributed installation, this procedure must be performed for thedatabase server only.
You use the dbstatus_report script to check the database.
Procedure1. As user root, ensure that the log and tmp directories used by the script are
owned by the Oracle:<database> owner user, by default oracle:dba.cd <WMCROOT>/admin/oracle/upgrade
chown oracle:dba log tmp
2. As user oracle, enter the following command to ensure that the environmentvariable ORACLE_SID is set.export ORACLE_SID=<SID>
3. As the oracle user, run the dbstatus_report script:cd <WMCROOT>/admin/oracle/upgrade/bin./dbstatus_report -sysdba_pwd <sysdba PASSWORD> -appusr_pwd <virtuo PASSWORD>
Where <sysdba PASSWORD> is the password for the Oracle sysdba user and<virtuo PASSWORD> is the password for the Oracle virtuo user.The script generates a log file in <WMCROOT>admin/oracle/upgrade/log with thename dbstatus_report_<timestamp>.log.Review this log file to check the status of the database.The current state of the database schema is reported. The reports appears:*** Constraints ***
Schema constraints summary
DB_SCHEMA C_STATUS TOTAL
============================== ======== ==========
VIRTUO ENABLED 12151
Chapter 1. Pre-upgrade tasks 11
Disabled schema constraint details
*** Objects ***
DB_SCHEMA OBJECT_TYPE O_STATUS TOTAL
==================== =================== ======== ========
VIRTUO FUNCTION VALID 31
VIRTUO INDEX VALID 3800
VIRTUO INDEX PARTITION VALID 9180
VIRTUO JAVA CLASS VALID 21
VIRTUO JAVA RESOURCE VALID 3
VIRTUO LIBRARY VALID 1
VIRTUO LOB VALID 22
VIRTUO PACKAGE VALID 158
VIRTUO PACKAGE BODY VALID 157
VIRTUO PROCEDURE VALID 61
VIRTUO QUEUE VALID 18
VIRTUO SEQUENCE VALID 304
VIRTUO SYNONYM VALID 3
VIRTUO TABLE VALID 5017
VIRTUO TABLE PARTITION VALID 17695
VIRTUO TRIGGER VALID 107
VIRTUO TYPE VALID 22
VIRTUO TYPE BODY VALID 4
VIRTUO VIEW VALID 1781
List of invalid objects in application schema (NONE if list below is empty)
*****************************************************************************
Note, please contact feature development team for any constraints remaining
in ’DISABLED’ state or for any package that has ’INVALID’ state !
*****************************************************************************
Script completed.
CAUTION:Do not proceed with the database upgrade if any database components orobjects are in an INVALID state or constraints are in DISABLED state.
12 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Important: Check if any database components or objects appear in a reportwith an INVALID status, or if some constraints are in a DISABLED state. If so, runthe following commands as the database owner and check the log fileproduced:cd <WMCROOT>/admin/oracle/upgrade/bin./recompile_invalid -sysdba_pwd <sysdba PASSWORD> -appusr_pwd <virtuo PASSWORD>./enable_constraints -sysdba_pwd <sysdba PASSWORD> -appusr_pwd <virtuo PASSWORD>./dbstatus_report -sysdba_pwd <sysdba PASSWORD> -appusr_pwd <virtuo PASSWORD>
If the problem persists, contact your support representative to identify thecause and resolve the problem.
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)
Chapter 1. Pre-upgrade tasks 13
v -t db (Database server)v -t ds (Directory server)v -t ldr (Loader server)v -t standalone (Stand-alone Server)v -upgrade (All servers)
Results
The script performs a number of checks on the system. The following exampleoutput shows a successful check with no reported problems:./dependency_checker======================================================================Tivoli Netcool Performance Manager pre-installation check======================================================================
Checking PATH.../usr/sbin: OK/usr/bin: OK
Performing checks for server type: all
-------------------------------------------------------------Perform Operating System configuration checks-------------------------------------------------------------
Hostname: tnpminlnx0204Processor type x86_64 is supported.Operating system version Red Hat Enterprise Linux Server release 7.2 (Maipo) is at supported level.
-------------------------------------------------------------Perform Host Setup configuration checks-------------------------------------------------------------
Fully Qualified Domain name: tnpminlnx0204.persistent.co.inChecking IP address... OKChecking root user umask...OK
-------------------------------------------------------------Checking installed Linux packages for sds-------------------------------------------------------------
pkg_full_version: 1.9.29.2.2Checking package: byacc x86_64... Status: OKpkg_full_version: 2.5.18Checking package: nscd x86_64... Status: OKpkg_full_version: 3.2.3.71.el7Checking package: compat-libstdc++-33 i686... Status: OKpkg_full_version: 4.8.2.16.2.el7Checking package: libstdc++ i686... Status: OKpkg_full_version: 3.2.3.71.el7Checking package: compat-libstdc++-33 x86_64... Status: OKpkg_full_version: 3.2.3.71.el7Checking package: compat-libstdc++-33 i686... Status: OKpkg_full_version: 4.4.7.8.el7Checking package: compat-gcc-44 x86_64... Status: OKpkg_full_version: 4.4.7.8.el7Checking package: compat-gcc-44-c++ x86_64... Status: OKpkg_full_version: 3.4.6.32.el7Checking package: compat-libf2c-34 x86_64... Status: OKpkg_full_version: 3.4.6.32.el7Checking package: compat-libf2c-34 i686... Status: OKpkg_full_version: 3.10.0.123.20.1.el7Checking package: kernel-headers x86_64... Status: OKpkg_full_version: 2.17.55.el7Checking package: glibc-headers x86_64... Status: OKpkg_full_version: 2.17.55.el7Checking package: glibc-devel x86_64... Status: OKpkg_full_version: 2.17.55.el7Checking package: glibc-devel i686... Status: OKpkg_full_version: 4.8.2.16.2.EL7Checking package: libgomp x86_64... Status: OK
-------------------------------------------------------------Checking installed Linux packages for oracle-------------------------------------------------------------
14 IBM Tivoli Netcool Performance Manager: Upgrade Guide
pkg_full_version: 1.9.29.2.2Checking package: byacc x86_64... Status: OKpkg_full_version: 2.5.18Checking package: nscd x86_64... Status: OKpkg_full_version: 2.23.52.0.1.16.el7Checking package: binutils x86_64... Status: OKpkg_full_version: 4.7.25.27.el7Checking package: compat-db x86_64... Status: OKpkg_full_version: 3.2.3.71.el7Checking package: compat-libstdc++-33 x86_64... Status: OKpkg_full_version: 3.2.3.71.el7Checking package: compat-libstdc++-33 i686... Status: OKpkg_full_version: 3.8.6.15.el7Checking package: control-center x86_64... Status: OKpkg_full_version: 0.158.3.el7Checking package: elfutils-libelf-devel x86_64... Status: OKpkg_full_version: 4.8.2.16.2.el7Checking package: gcc x86_64... Status: OKpkg_full_version: 4.8.2.16.2.el7Checking package: gcc-c++ x86_64... Status: OKpkg_full_version: 2.17.55.el7Checking package: glibc x86_64... Status: OKpkg_full_version: 2.17.55.el7Checking package: glibc i686... Status: OKpkg_full_version: 2.17.55.el7Checking package: glibc-common x86_64... Status: OKpkg_full_version: 2.17.55.el7Checking package: glibc-devel x86_64... Status: OKpkg_full_version: 2.17.55.el7Checking package: glibc-devel i686... Status: OKpkg_full_version: 2.17.55.el7Checking package: glibc-headers x86_64... Status: OKpkg_full_version: 4.8.2.16.2.el7Checking package: libgcc x86_64... Status: OKpkg_full_version: 4.8.2.16.2.el7Checking package: libgcc i686... Status: OKpkg_full_version: 0.3.109.12.el7Checking package: libaio x86_64... Status: OKpkg_full_version: 0.3.109.12.el7Checking package: libaio i686... Status: OKpkg_full_version: 0.3.109.12.el7Checking package: libaio-devel x86_64... Status: OKpkg_full_version: 0.3.109.12.el7Checking package: libaio-devel i686... Status: OKpkg_full_version: 4.8.2.16.2.el7Checking package: libstdc++ x86_64... Status: OKpkg_full_version: 4.8.2.16.2.el7Checking package: libstdc++-devel x86_64... Status: OKpkg_full_version: 4.8.2.16.2.el7Checking package: libgomp x86_64... Status: OKpkg_full_version: 1.0.2.2.1.el7Checking package: libXp x86_64... Status: OKpkg_full_version: 3.82.21.el7Checking package: make x86_64... Status: OKpkg_full_version: 10.1.5.4.el7Checking package: sysstat x86_64... Status: OK
-------------------------------------------------------------Checking installed Linux packages for jboss-------------------------------------------------------------
pkg_full_version: 1.9.29.2.2Checking package: byacc x86_64... Status: OKpkg_full_version: 2.5.18Checking package: nscd x86_64... Status: OKpkg_full_version: 4.2.1.6.el7Checking package: ecj x86_64... Status: OKpkg_full_version: 1.2.7.13Checking package: zlib-devel x86_64... Status: OKpkg_full_version: 1.8.0.65.2.4.5.5.el7Checking package: java-1.8.0-openjdk x86_64... Status: OK
-------------------------------------------------------------Perform Filesystem configuration checks-------------------------------------------------------------
Checking space on / partition...OK
-------------------------------------------------------------
Chapter 1. Pre-upgrade tasks 15
Perform Oracle configuration checks-------------------------------------------------------------
Checking if Oracle User exists... OKChecking oracle user shell... OKChecking oracle user umask... OKChecking oracle group... OKChecking oracle profile......OKChecking installed oracle version 12.1.0.2.0Oracle Release is: 12.1Checking Oracle is installed correctly in /appl/oracle/product/12.1.0.2.0/db_1Checking Oracle version in /appl/oracle/product/12.1.0.2.0/db_1Oracle Database 12c is installed.GYMWI0033E FAIL: Oracle Partitioning is not installedChecking Oracle directory /appl/oracle/product/12.1.0.2.0/db_1/network...OKChecking Oracle directory /appl/oracle/product/12.1.0.2.0/db_1/network/admin...OKChecking Oracle binary /appl/oracle/product/12.1.0.2.0/db_1/bin/dbca...GYMWI0038E FAIL: dbca does not existChecking Oracle binary /appl/oracle/product/12.1.0.2.0/db_1/bin/sqlplus...OKChecking Oracle binary /appl/oracle/product/12.1.0.2.0/db_1/bin/netca...OKChecking Oracle binary /appl/oracle/product/12.1.0.2.0/db_1/bin/emca...GYMWI0038E FAIL: emca does not existChecking for listener.ora... not found, OKChecking for tnsnames.ora...GYMWI0042E FAIL: /appl/oracle/product/12.1.0.2.0/db_1/network/admin/tnsnames.ora must be owned by oracle
-------------------------------------------------------------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-------------------------------------------------------------
Checking for package jboss-4.0.3SP1.tar.gz ... OK
-------------------------------------------------------------Perform SDS / DB2 package checks-------------------------------------------------------------
Checking for SDS packages in /appl/depends/sds64Checking 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
-------------------------------------------------------------
16 IBM Tivoli Netcool Performance Manager: Upgrade Guide
The following tests failed -- you must investigate and fixthese failures before beginning the installation-------------------------------------------------------------
FAILURE: 1GYMWI0033E Oracle Partitioning is not installed
-------------------------------------------------------------FAILURE: 2GYMWI0038E dbca does not exist
-------------------------------------------------------------FAILURE: 3GYMWI0038E emca does not exist
-------------------------------------------------------------FAILURE: 4GYMWI0042E /appl/oracle/product/12.1.0.2.0/db_1/network/admin/tnsnames.ora must be owned by oracle
-------------------------------------------------------------FAILURE: 5GYMWI0069E 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 87.
Running Oracle installation with upgrade optionRun the oracle12C_install script to install Oracle 12c.
Before you begin
For Solaris 11, make sure that following packages are installedbefore you start the Oracle upgrade:v pkg://solaris/system/dtrace
v pkg://solaris/developer/assembler
v pkg://solaris/developer/build/make
v pkg://solaris/system/xopen/xcu4 (If it is not installed as part of standardOracle Solaris 11 installation)
v pkg://solaris/x11/diagnostic/x11-info-clients
v pkg://solaris/compress/unzip
Procedure
Run the following command as root user with -upgrade option:#/var/install/sbin/oracle12C_install –upgrade
Chapter 1. Pre-upgrade tasks 17
# /var/install/sbin/oracle12C_install -upgradeChecking for unzip... found it.----------------------------------------------------------------------------------------------------------------------------------------------
__/ \_/ \_/ \ Oracle 12C Software Installation\_/ \_/
\_/
----------------------------------------------------------------------------------------------------------------------------------------------
Check Oracle User exists....... DoneCheck oinstall group exists....... OKCheck dba group exists....... OK-----------------------------------------------------------------------Please select the Type of Install you wish to executeby entering the number associated with the Install Type :
Full install (Oracle 12.1.0.2.0 + 12.1.0.x.x patch set update) (1)Oracle 12.1.0.2.0 Client only (2)Oracle 12.1.0.2.0 Instant Client only (3)12.1.0.x Patch Set (4)12.1.0.x.x Patch Set Update (5)Oracle 12.1.0.x oneoff patches (6)
-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6 ] :1Please enter the location of the Oracle 12.1.0.2.0 Software [/cdrom/cdrom0/database]:/appl/Oracle_Installer/12.1.0.2/databasePlease enter the install location of the Oracle Base [/appl/oracle]:
Please enter the value of ORACLE_HOME [/appl/oracle/product/12.1.0.2.0/db_1]:
The directory /appl/oracle/product/12.1.0.2.0/db_1 does not exist and will be createdPlease enter the value of ORACLE_HOME_NAME [OraDBHome12C]:
Performing pre installation steps...Done
Installing Oracle 12.1.0.2.0.......logging to /var/install/logs/oracle12C_install_25558.log\Installation of Oracle 12.1.0.2.0 complete
Running post-install steps ....... Running root.sh - Please Respond to the Onscreen Questions if requiredCheck /appl/oracle/product/12.1.0.2.0/db_1/install/root_<myserver.ibm.com>_2016-10-05_11-38-31.logfor the output of root script....donePlease enter the location of the Oracle 12.1.0.2.0 compressed OPatch patch zip(’none’ for none) [/cdrom/cdrom0/patches/opatch]:noneNo OPatch patch available to be installedPlease enter the location of the Oracle PSU 12.1.0.x.x uncompressed patches(’none’ for none) [/cdrom/cdrom0/patches/psu]:noneNo PSU patches to be installedPlease enter the location of the Oracle 12.1.0.2.0 uncompressed one-off patches(’none’ for none) [/cdrom/cdrom0/patches/oneoff]:noneNo one-off patches to be installed
--------Oracle 12C installation
18 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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.3.0 on a Solaris machinein a distributed or a stand-alone environment.Related information:
Installing Jazz for Service Management
Hardware and software requirements for installing Jazz forService Management
Jazz for Service Management and its integration services have hardware andsoftware requirements, including supported middleware and installationtechnologies.
Important: Jazz for Service Management installation is not supported on Solarisplatform.
Important: You must add the following list of Linux libraries, which areprerequisite when you install Jazz for Service Management. If you do not includethese libraries, it can cause failure of prerequisite scanner or the installation of Jazzfor Service Management.os.lib.libSM.so.6_32os.lib.libICE.so.6_32os.lib.libfreetype.so.6_32os.lib.libuuid.so.1_32os.lib.libfontconfig.so.1_32os.lib.libjpeg.so.62_32os.lib.libpng12.so.0_32os.lib.libz.so.1_32os.lib.libstdc.so.5_32os.lib.libstdc.so.6_32
Related information:
Jazz for Service Management Detailed System Requirements
Chapter 1. Pre-upgrade tasks 19
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.
20 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 21
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/
22 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
Quick reference to Jazz for Service Management installationUse this information to download and install Jazz for Service Management 1.1.3.0.Jazz for Service Management Version 1.1.3.0 is a full refresh of Jazz for ServiceManagement Version 1.1 Base with Modification 3.
This table summarizes the steps to plan and install Jazz for Service Management.1. This table summarizes the steps to plan and install Jazz for Service
Management.
Task Description
Download and extract the softwareDownload and extract the Jazz for ServiceManagement Version 1.1.3.0 and otherrequired components from IBM PassportAdvantage.
v 1.1.3.0-TIV-JazzSM-multi.zip: 64-bit,multiplatform IBM Installation Managersoftware package repository for thefollowing Jazz for Service Managementintegration services and components:
– IBM Dashboard Application ServicesHub 3.1.3.0
– Jazz for Service Management extensionfor IBM WebSphere Version 1.1.3.0
– IBM Tivoli Common Reporting 3.1.3.0
v IBM-was-8.5.5.9-platform.zip:Platform-specific WebSphere ApplicationServer Version 8.5.5.9
v 3.1.3.0-TIV-JazzSM-TCR-COGNOS-platform.tar.gz|.zip: Platform-specificIBM Cognos Business IntelligenceReporting for Tivoli Common ReportingVersion 3.1.3.0.
System requirementsAssess the hardware and softwarerequirements. See Hardware and softwarerequirements.
Chapter 1. Pre-upgrade tasks 23
Task Description
Plan your installationYou can choose to perform a full or custominstallation of Jazz for Service Management.Different factors determine whichinstallation scenario you must choose, forexample, the integration services to install,business and security policies, your targetenvironments, and user types. See Planningyour deployment.
Prepare your environmentPrepare your environment whether youperform a fresh or upgrade. See Preparingyour environment.
Perform a fresh installation20 GB of free disk space is required for afresh installation. Follow these steps:
v Download and extract1.1.3.0-TIV-JazzSM-multi.zip and otherrequired software to a local directory, forexample, <JazzSM_FP_Home>.
v Add the JazzSM_FP_Home/1.1.3.0-TIV-JazzSM-multi/JazzSMFPRepository/disk1/diskTag.inf file along with the repositorylocations for any other earlier Jazz forService Management versions toInstallation Manager > File > Preferences> Add Repository.
v Follow the installation instructions. SeePerforming a full installation.
Important: Jazz for Service Management1.1.3.0 installation fails on RHEL 7.2 usingFull Installation option.
To troubleshoot, see Issues with Jazz forService Management 1.1.3.0 Full Installationmode on RHEL 7.2 in Troubleshooting TivoliNetcool Performance Manager guide.
Perform an upgradeJazz for Service Management Version 1.1.3.0can be installed on top of earlier Jazz forService Management releases (1.1, 1.1.0.1,1.1.0.2, 1.1.0.3, 1.1.1.0, 1.1.2.0, 1.1.2.1). UseIBM Installation Manager in GUI or silentmodes to first update the Jazz for ServiceManagement extension for IBM WebSphereand then install Jazz for ServiceManagement Version 1.1.3.0 for DashboardApplication Services Hub installation. SeeApplying fix pack by using InstallationManager GUI mode.
Perform post-installation tasksVerify the installation. See Post-installationtasks.
Configuring Jazz for Service Management
24 IBM Tivoli Netcool Performance Manager: Upgrade Guide
2. This table summarizes the steps to configure Jazz for Service Management.
Task Description
Cross-serviceYou can configure a central user registry,such as a Lightweight Directory AccessProtocol (LDAP) registry, for Jazz for ServiceManagement user management andauthentication.
Configure WebSphere Application Server touse a central federated repository with anLDAP user registry. After configuration, youcan add users to the federated repository.
You can configure the integration servicesfor single sign-on, so that users can accessJazz for Service Management applications bylogging in only once.
During installation, the global securityconfiguration is enabled that applies to thesecurity policy for all administrativefunctions in each Jazz for ServiceManagement application server. Theconfiguration is also used as a defaultsecurity policy for user applications.
See Configuring Jazz for ServiceManagement.
Dashboard Application Services HubFor installations of Dashboard ApplicationServices Hub with large user populations,you can set up a load balancing cluster ofconsole nodes with identical configurationsto evenly distribute user sessions.
You can choose to configure DashboardApplication Services Hub to use TivoliAccess Manager WebSEAL Version tomanage authentication.
You can also configure the Context MenuService (CMS) to use a remote database,which can be used by products to shareinformation outside of the DashboardApplication Services Hub environment.
See Configuring Dashboard ApplicationServices Hub.
Tivoli Common ReportingAfter you install Tivoli Common Reporting,prepare your report packages to be able togenerate, publish, and edit your reports.
You can configure database connectiondetails to a data source other than DB2.
See Configuring Tivoli Common Reporting.
Related information:
Chapter 1. Pre-upgrade tasks 25
Download Jazz for Service Management Version 1.1.3.0
Getting started with Jazz for Service Management
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 stop the application server for maintenance.
About this task
The same procedure applies to any Jazz for Service Management applicationserver.
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:
./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.Related information:
Common directory locations
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.
26 IBM Tivoli Netcool Performance Manager: Upgrade Guide
WAS_admin_user_nameThe default user name is smadmin.
WAS_admin_passwordPassword that is specified at the time of installation.
Example
stopServer.sh server1 -username smadmin -password jazzsmpwd
Related information:
Common directory locations
Disabling the Cognos Application Firewall for browsersecurity
To prevent URL redirection attacks in Cognos, enable Cognos Application Firewall.IBM Cognos Application Firewall (CAF) analyzes and validates HTTP and XMLrequests before they are processed.
Procedure1. Log on to the reporting server as a user with administrative privileges.2. Start IBM Cognos Configuration by using the following commands:
<JazzSM_Home>/reporting/cognos/bin64/cogconfig.sh
Where <JazzSM_Home> is /opt/IBM/JazzSM.3. In the Explorer pane, under Security, click IBM Cognos Application Firewall.4. In right pane, set Enable CAF validation and Is third party XSS checking
enabled properties to False.
Verifying the installationYou can verify the installation of IBM WebSphere Application Server Version 8.5.5.9and the Jazz for Service Management integration services.
Procedure
Verify the Dashboard Application Services Hub installation:1. Log in to the reporting interface from the Dashboard Application Services Hub
login page.See Logging in.
2. Optional: 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. Optional: Log in to the Dashboard Application Services Hub, and verify that
the Administration Services icon in the navigation bar.5. Assign an Administration Services role to your user ID, if the Administration
Services icon is not visible as follows:
Chapter 1. Pre-upgrade tasks 27
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 whether the Applications view displaysthe managed 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.
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 information:
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.
28 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Note: When single sign-on (SSO) is enabled, ensure that you use the fullyqualified host name in the URL of the Jazz for Service Managementreporting and UI server. SSO requires that the browser pass LTPA cookiesto the Jazz for Service Management application server, and these cookiescontain the fully qualified host name.
– port is the secure HTTPs port number that was specified duringinstallation. The default value is 16311.
– /DASH_context_root is the context root for the console that was specifiedduring installation. The default value is /ibm/console.
2. On the Dashboard Application Services Hub login page, enter the WebSphereadministrator user ID and password that were specified during installation.Click Log in. The Dashboard Application Services Hub Welcome page opens.
3. In the navigation bar, verify that Reporting icon > Common Reportingexists. If Reporting icon does not exist in the navigation bar, complete thefollowing steps:a. Click Console Settings > User Roles. The User Roles page opens.b. In the User ID field, enter your user ID and click Search.c. In the table, select your user ID. The User Roles > Available Roles page
opens.d. In the table, select the tcrPortalOperator role and click Save.e. Log out and then log in again.
v In the navigation bar, click Reporting icon > Common Reporting. The CommonReporting portal is displayed within a Dashboard Application Services Hubportlet page.
v Verify that you can run and view the sample report. See Running the sampleoverview report.
v Access the reporting interface directly as follows:1. Open a web browser and enter the following URL for the reporting interface:
http://<host.domain:port>/tarf/servlet/dispatchFor example: http://<myJazzSMserver.ibm.com>:16310/tarf/servlet/dispatch
– host.domain is the fully qualified host name or IP address of the Jazz forService Management reporting server.
Note: When single sign-on (SSO) is enabled, ensure that you use the fullyqualified host name in the URL of the Jazz for Service Managementreporting server.
– port is the non-secure HTTP port number that was specified duringinstallation. The default value is 16310.
2. On the Log on to IBM Cognos Software page, enter the WebSphereadministrator user ID and password that were specified during installation.Click OK. The Common Reporting portal opens.
3. Verify that you can run and view the sample report.
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.
Chapter 1. Pre-upgrade tasks 29
In a Dashboard Application Services Hub environment, you must assigntcrPortalOperator role to new users and user groups, otherwise they cannotaccess the reporting interface from the console.
In any of the supported environments, you can also change permissions in thereporting interface to restrict access to various reporting resources and functionsafter you configure the security permissions. See Configuring security permissions.Related information:
Verifying the Reporting Services installation
Uninstalling Jazz for Service ManagementYou can uninstall most integration services and the application server by usingInstallation Manager GUI mode or silent mode. You might need to clean up theremaining directories after a successful uninstallation or a failed installation.
Procedure
Use IBM Installation Manager in GUI or silent modes to uninstall Jazz for ServiceManagement Version 1.1.3.0.See Uninstalling fix packs by using Installation Manager GUI mode.See Uninstalling fix pack by using Installation Manager silent mode.
Important: When you revert to the previous version of Jazz for ServiceManagement, Installation Manager does not automatically account for interimfixes. You must manually install interim fixes after you roll back.Related information:
Uninstalling Jazz for Service Management and related software
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
30 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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.
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.
Chapter 1. Pre-upgrade tasks 31
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.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.
32 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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.
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.
Chapter 1. Pre-upgrade tasks 33
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.
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.3.0. Theupgrade is a manual procedure in which you first create packages with data, andthen move the data to a previously installed Tivoli Common Reporting Version3.1.3.0.
About this taskv The upgrade is a side-by-side process, which results in two instances of Tivoli
Common Reporting on your system - the Version 3.1.3.0 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 Tivoli Common Reporting to 3.1.3.0” on page 35Users 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.
v If your content store is more than 1 GB, see “Upgrading the content store fromolder versions of Tivoli Common Reporting” on page 36.
34 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Upgrading Tivoli Common Reporting to 3.1.3.0Upgrade your Tivoli Common Reporting earlier versions to v3.1.3.0.
Before you begin
Perform these tasks before you upgrade:v Install Jazz for Service Managementv Install Tivoli Common Reporting 3.1.3.0
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 3.1.3.0:
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 see 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.3.0.
Note: The reports that are saved in private folders are not available when youmigrate 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 backup.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.
Chapter 1. Pre-upgrade tasks 35
Results
You have upgraded your Tivoli Common Reporting to Version 3.1.3.0 together withall your reporting data. The following items were moved to Version 3.1.3.0: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.3.0 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.3.0 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
36 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.
Archiving the previous releaseTo archive the previous release, you must remove the previous release of IBMTivoli Netcool Performance Manager and move the release contents to an archivedirectory.
About this task
Important: On a distributed server or a stand-alone server, this procedure mustbe performed on all IBM Tivoli Netcool Performance Manager servers. In adistributed installation, no specific sequence needs to be followed for archivingservers.
Procedure1. Run the command as user root:
/var/install/sbin/archive_release -wmcr /appl/virtuo -product virtuo
The following output is displayed:-----------------------------------------------------------------------
WARNING!!!
This command will disable and archive the current software release.It should only be executed as part of an upgrade.
-----------------------------------------------------------------------
Are you sure you wish to continue? (Y/N) :
2. Enter y to continue.-----------------------------------------------------------------------
Please select the type of system you are upgrading by
entering the number associated with the system type :
All Inclusive (1)
Application (2)
Loader (3)
Directory Server (4)
Database (5)
-----------------------------------------------------------------------
[ 1 / 2 / 3 / 4 / 5 ]For stand-alone server, select 1.For distributed server, select 2/3/4/5).
© Copyright IBM Corp. 2006, 2017 37
3. Enter the number corresponding to the type of system you are archiving.
Important: If more than one application is installed on the same computer,archive once for all applications on that computer. For example, if theapplication server, the loader, and the directory server all are on the samecomputer, select 2 for the application server to be archived.Current release is TNPM1.4.2.0Checking processes...Process sap is not runningProcess sapmon is not runningProcess sapmgr is not runningArchiving TNPM1.4.2.0 package files to /appl/archive/TNPM1.4.2.0_pkgs......doneArchiving /appl/virtuo to /appl/archive/virtuo.TNPM1.4.2.0......doneArchiving release TNPM1.4.2.0 complete
Upgrade scenariosThere are two scenarios for upgrading Tivoli Netcool Performance Manager:v Upgrading a standalone systemv Upgrading a distributed system
Determine which scenario applies and follow the appropriate procedure.
Upgrading Tivoli Netcool Performance Manager on Oracle Solaris 11When you install Tivoli Netcool Performance Manager on Solaris 11, you mightencounter some issues.
Procedure1. After you install the database and before the installation of the database
schema, the database schema installation might fail as services are notregistered due to svccfg import and delete changes. The behavior of svccfgimport and svccfg delete fmri are changed in Solaris 11. You might see thefollowing error message during the pmw_install:svccfg: Restarting svc:/system/manifest-import
Use the following steps to work around this issue:a. Check whether all services are registered and are up and running by using
the following command:svcs *-na*
You must see the status as follows:
STATE STIME FMRIonline 17:58:26 svc:/application/virtuo/sds-na:naonline 17:59:27 svc:/application/virtuo/sapmon-na:naonline 18:23:17 svc:/application/virtuo/database-na:globalonline 18:43:10 svc:/application/virtuo/sap-na:naonline 19:12:57 svc:/application/virtuo/sapmgr-na:na
If any of the services are not displayed with the svcs command, you mightencounter a failure in DB_SCHEMA_INSTALL and might see the following errormessages:svcs: Pattern ’database-na’ doesn’t match any instancesERROR: Database not running. The database must be running to install the schemaTask DB_SCHEMA_INSTALL exited with value 1. Quitting.
38 IBM Tivoli Netcool Performance Manager: Upgrade Guide
b. Check whether the service is unmasked by using the following command:# svccfg listcust -M | grep <service-name>
For example:# svccfg listcust -M | grep sapmon-na
If the service is masked, you might see the following output:
svc:/application/virtuo/sapmon-na manifest MASKEDmanifestfiles/var_svc_manifest_site_application_virtuo_sapmon-na_xml astring adminMASKED /var/svc/manifest/site/application/virtuo/sapmon-na.xmlsvc:/application/virtuo/sapmon-na:na manifest MASKED
c. Unmask the service by using the following command:# svccfgsvc:> select <service-name>svc:/application/virtuo/<service-name> delcustDeleting customizations for service: application/virtuo/<service-name>svc:/application/virtuo/<service-name>>quit
d. Confirm that the service is unmasked by using the following command:# svcs <service_name>STATE STIME FMRIoffline* 12:36:59 svc:/application/virtuo/<service_name>:na
e. Proceed with the installation.2. If you encounter the following error message during the
DB_SCHEMA_POST_INSTALL step:Inventory load failed... OPatch cannot load inventory for the given Oracle Home.
LsInventorySession failed: LsInventory cannot create the log directory/appl/oracle/product/12.1.0.2.0/db_1/cfgtoollogs/opatch/lsinv/lsinventory2016-11-08_12-18-03PM.txt
This error message has no functional impact and can be ignored.
Upgrading a stand-alone systemOn a stand-alone system, copy the required files to the system and run theappropriate command to start the interactive installation scripts. Enter the requiredinformation at each of the prompts.
Procedure1. Copy all of the Tivoli Netcool Performance Manager 1.4.3 software packages
into the target directory of the stand-alone server.The target directory is the parent directory of the $WMCROOT directory where thecurrent release is installed. If $WMCROOT is set to /appl/virtuo, then the targetdirectory is /appl.
2. Change to the target directory:cd <target_directory>
3. Run the following command as user root:ksh pmw_install -wmcr <WMCROOT> -upgrade
where <WMCROOT> is the location where Tivoli Netcool Performance Managerwas previously installed.The default installation directory is /appl/virtuo.The following output is displayed:Making PMW top-level directory:/appl/virtuoMaking software archive directories: under /appl/virtuo/admin/softwareLooking for bootstrap package
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 39
Found vallent-vt-common-TNPM1.4.3.0.tar.gzExtracting and running bootstrap packageLooking for bootstrap scriptRunning vallent-vt-common.installCopyright 2017 IBM Corporation, All Rights ReservedThis installation script will install the Tivoli Netcool Performance Manager commonsoftware version TNPM1.4.3.0 on your system.Do you wish to continue?
4. Enter yes to continue with the installation.5. The license agreement is displayed. You are prompted to accept the license
termsDo you agree with the terms of this license? Yes
Enter yes to agree to the license terms.6. The menu is displayed:
What Type of System Are you Installing ?1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit TNPMW Install---->
Select Standalone server.7. Enter yes when prompted to deploy the packages:
Do you want to deploy the packages? [yes/no] >yes
Configuring core softwareThe system proceeds to install and configure the core software. Check eachenvironmental variable as it is displayed.
About this task
The installation displays a list of Tivoli Netcool Performance Managerenvironmental variables and their default values.
Important: You must check each of the environmental variables to ensure that theyare set to the correct value and update the value if appropriate. These variables setserver host names and various TCP port numbers. They vary from location tolocation.
Procedure1. You are prompted to verify the environment variables for certain packages:
Please, Verify Environment Settings
.............
.............
A list of environment variables is displayed. You can accept the default valueslisted or to edit individual values.
Note: The display time of the values depends on the speed of the server thatis being installed.v If you accept the default values, the installation proceeds.v If you choose not to not accept the defaults, a series of prompts is presented
for you to enter the variable values.
40 IBM Tivoli Netcool Performance Manager: Upgrade Guide
2. When the variable values are correct, select the appropriate menu option toaccept the values.
3. Repeat this procedure for each package that requires environment variables tobe configured.
Upgrading the JBoss application serverThe system proceeds to upgrade the JBoss application server configuration.
Procedure
Enter yes when prompted to upgrade the JBoss application server:Would you like to perform task JBOSS_INSTALL ? [yes/no] >yes
The output is displayed:Deploying JBoss 4.0.3SP1...Buildfile: /appl/virtuo/admin/common/install/scripts/build.xml
init:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/appl
upgrade:
init:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/appl
copy-libs:[copy] Copying 2 files to /appl/virtuo/as/server/default/lib[copy] Copying 10 files to /appl/virtuo/lib/tp
init:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/appl
fix-alarm-war:[mkdir] Created dir: /appl/virtuo/temp[mkdir] Created dir: /appl/virtuo/temp/war/apps/lib[unjar] Expanding:
/appl/virtuo/as/server/default/deploy_core/S02-na-alarm-manager.ear into /appl/virtuo/temp
[unjar] Expanding: /appl/virtuo/lib/na-alarm-service-server.jar into /appl/virtuo/temp
init:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/appl
fix-alarm-war:[mkdir] Created dir: /appl/virtuo/temp[mkdir] Created dir: /appl/virtuo/temp/war/apps/lib[unjar] Expanding: /appl/virtuo/as/server/default/deploy_core/S02-na-alarm-manager.ear into /appl/virtuo/temp[unjar] Expanding: /appl/virtuo/temp/S02-na-alarm-manager.war into/appl/virtuo/temp/war/apps/lib[unjar] Expanding: /appl/virtuo/lib/na-alarm-service-server.jar into/appl/virtuo/temp[copy] Copying 1 file to /appl/virtuo/temp/war/apps/lib[copy] Copying 1 file to /appl/virtuo/as/client[jar] Updating jar: /appl/virtuo/temp/S02-na-alarm-manager.war[jar] Updating jar: /appl/virtuo/as/server/default/deploy_core/
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 41
S02-na-alarm-manager.ear
BUILD SUCCESSFULTotal time: 14 seconds
Cronjob installationThe system proceeds to install the Tivoli Netcool Performance Manager cronjobs.
Procedure1. Enter yes when prompted to install the cronjobs:
Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no]>yes
Configuring core cronjobsWhat Type of PMW System Are you Installing?
2. You are prompted to select the type of system you are installing:Please select the type of PMW System you are installingby entering the number associated with the system type:All Inclusive (1)
Application (2)
Loader (3)
Directory Server (4)
Database (5)
Gateway (6)
-----------------------------------------------------------------------
[ 1 / 2 / 3 / 4 / 5 / 6 ] :
Enter 1 for all inclusive.3. You are prompted to enter the location of the Oracle home directory:
Please enter the ORACLE_HOME Directory[/appl/oracle/product/12.1.0.2.0/db_2]:
(Enter . if unknown)
Please enter the ORACLE_BASE Directory [/appl/oracle]:(Enter . if unknown)
Please enter the ORACLE_SID Parameter [vtdb]:(Enter . if unknown)
Accept the default.4. You are prompted to enter the location of the vtdb database archive directory:
Please enter the vtdb Database Archive Directory [/oradump/vtdb]:
(Enter . if unknown)
Accept the default.5. You are prompted to enter the location of the Tivoli Netcool Performance
Manager log directory:Please enter the PMW Log Directory [/appl/virtuo/logs]:
(Enter . if unknown)
Accept the default.
42 IBM Tivoli Netcool Performance Manager: Upgrade Guide
6. You are prompted to enter the location of the Tivoli Netcool PerformanceManager archive logs directory:Please enter the PMW Archive Logs Directory[/data/trace_archive1]:
(Enter . if unknown)
Setting up CRON environment
Filtering old cronjobsDone
Setting up root cronjobsFinished setting up root cronjobsSetting up virtuo user cronjobsFinished setting up virtuo cronjobsRestarting Croncron daemon stoppedcron daemon started
Accept the default.The installation proceeds to install the root user and virtuo user cronjobs.The cronjob installation log file output can be found at the following location:$WMCROOT/admin/logs/pmw_install.log
Restoring configurationYou can restore all the configuration values that were archived from the previousrelease.
About this task
Restore all of the configuration values if specific changes are made to the previousconfiguration that you want to preserve in the new release.
If you do not want to keep any of the previous configuration values enter no whenprompted, and proceed to Migrating loaders.
Procedure
You are asked if you want to restore the configuration from the previous release.v Enter yes to restore all of the configuration settings from the previous release.v Enter no if you do not want to restore all of the configuration settings from the
previous release.
For a yes response, the system proceeds to restore configuration settings.
Migrating loadersThe system migrates the loaders from the previous release. The migration is doneautomatically and no user intervention is required.
The process is logged in the <WMCROOT>/admin/logs/pmw_install.log log file.Appserver ready.
Executing /appl/virtuo/admin/common/install/upgrade/scripts/
UPG01_loader_migrate...
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 43
UPG01_loader_migrate: INFO: Restarting sapmgr...
/appl/virtuo/admin/common/install/upgrade/scripts/UPG01_loader_migratecomplete.
Synchronizing usersThe system proceeds to synchronize Tivoli Netcool Performance Manager andLDAP users.
Procedure
You are prompted to enter or confirm the system administrator user name andpassword.Executing /appl/virtuo/admin/common/install/upgrade/scripts/UPG01_loader_migrate...UPG01_loader_migrate: INFO: Restarting sapmgr.../appl/virtuo/admin/common/install/upgrade/scripts/UPG01_loader_migrate complete.Executing /appl/virtuo/admin/common/install/upgrade/scripts/UPG06_sync_tnpm_ldap_admin...UPG06_sync_tnpm_ldap_admin: INFO: syncing tnpm and ldap usersEnter administrator username: : [sysadm]---->Enter administrator password: [Sysadm01]---->
UPG06_sync_tnpm_ldap_admin: INFO: syncing of tnpm and ldap users complete/appl/virtuo/admin/common/install/upgrade/scripts/UPG06_sync_tnpm_ldap_admin complete.
Encoding PasswordsThe system proceeds to encode the passwords that are stored in the configurationfiles.
Procedure1. Enter yes when prompted to encode the passwords:
Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yes
Replacing all passwords with encoded passwords.
Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.N
Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.BACKUP
Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties.N
Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties.BACKUP
Encoding values in /appl/virtuo/conf/as/as-default.properties.N
Encoding values in /appl/virtuo/conf/as/as-default.properties.BACKUP
Encoding values in /appl/virtuo/conf/externalreporting/default.properties.N
Encoding values in /appl/virtuo/conf/externalreporting/default.properties
Encoding values in /appl/virtuo/conf/externalreporting/default.properties.BACKUP
Encoding values in /appl/virtuo/conf/dbspace_admin.xml
Encoding values in /appl/virtuo/conf/dbspace_admin/dbspace_admin.xml
Encoding values in /appl/virtuo/conf/ldap/default.properties.N
Encoding values in /appl/virtuo/conf/ldap/default.properties.BACKUP
44 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Passwords may also be stored in /appl/virtuo/admin/logs/pmw_install.log,so it should be removed when not needed anymore.
2. The upgrade of the core software is complete. The upgrade output is logged inthe location:$WMCROOT/admin/logs/pmw_install.log
Upgrading a distributed systemTo upgrade a distributed system, copy the required files to the target server andrun the individual scripts on each server to upgrade the required components.
Running an interactive upgradeTo upgrade the required components, run the script on each individual server.
To upgrade a distributed system, run the pmw_install script on each individualserver to upgrade the required components. Enter information as required by theinstallation scripts. Upgrade the servers, or components on shared servers, in thefollowing order:1. Database server2. Directory server3. Application server4. Loader server
Application and loader serverIn a distributed system, the application server can also be configured as a loaderserver.
The pmw_install script must be run twice on this server:v The first time to upgrade the application componentsv The second time to upgrade the loader components
You can also install the loader server on a separate server. In that case, you need torun the pmw_install only once on the separate server.
Upgrading the database serverTo upgrade the database server, all of the Tivoli Netcool Performance Manager1.4.3 core software packages must be copied to the target directory.
Procedure1. Copy all of the Tivoli Netcool Performance Manager 1.4.3 core software
packages to the target directory.The target directory is the parent of the $WMCROOT directory where the currentrelease is installed.If $WMCROOT is set to /appl/virtuo, then the target directory is /appl.
2. Run the commands user root:cd /<target_directory>
# ksh pmw_install -wmcr /appl/virtuo -upgrade
Where <WMCROOT> is the location where Tivoli Netcool Performance Managerwas previously installed. The default installation directory is /appl/virtuo.The output is displayed:
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 45
Making PMW top-level directory: /appl/virtuoMaking software archive directories: under /appl/virtuo/admin/softwareLooking for bootstrap packageFound vallent-vt-common-TNPM1.4.3.0.tar.gzExtracting and running bootstrap packageLooking for bootstrap scriptRunning vallent-vt-common.installCopyright 2017 IBM Corporation, All Rights ReservedThis installation script will install the Tivoli Netcool Performance Manager commonsoftware version TNPM1.4.3.0 on your system.
Do you wish to continue? Yes
3. Enter yes to continue.4. Enter yes at the prompt to agree to the license terms.
Do you agree with the terms of this license? Yes
Installation continues:Running pre-install commands...Backing up old versions of non-shared files to be installed...Creating installation directories...Installing software...Checking configuration files...Updating file permissions...Setting up init scripts...Running post-install commands...... Checking Virtuo File Permissions... Setup Virtuo profileSetting up virtuo User Profile....done
Completed Virtuo Software InstallationLogs can be seen in pmw_install.logInstallation is complete.
5. The menu is displayed:What Type of System Are you Installing ?
1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit TNPMW Install
6. Select 5.---->
Checking packages: jre ant db-install db-confVerified the following packages:
/appl/vallent-vt-jre-TNPM1.4.3.0.tar.gz/appl/vallent-vt-ant-TNPM1.4.3.0.tar.gz/appl/vallent-vt-db-install-TNPM1.4.3.0.tar.gz/appl/vallent-vt-db-conf-TNPM1.4.3.0.tar.gz
7. The installer asks whether you want to deploy packages:Do you want to deploy the packages? [yes/no] >yes
Enter yes.Installing
jre (TNPM1.4.3.0) ... okant (TNPM1.4.3.0) ... tar: Read 5120 bytes from -okdb-install (TNPM1.4.3.0) ... okdb-conf (TNPM1.4.3.0) ... tar: Read 5120 bytes from
Configuring databaseThe system proceeds to install and configure the core database software.
46 IBM Tivoli Netcool Performance Manager: Upgrade Guide
About this task
The installation lists the default values of Tivoli Netcool Performance Managerenvironment variables. These variables set server host names and various TCP portnumbers and varies from location to location. You can accept the default values,restore values to their default settings, or change individual values.Please, Verify Environment Settings
1. Accept Variable Values below
2. Reset Variables to Default values
3. Change WMCHOST=<server_name>
.............
Important: You must check all the variables to ensure that they are set to thecorrect value.
Procedure1. Select option 3, and change the value of WMCHOST to the host name of the
application server.2. If required, change any other values.3. When the environment variable values are correct, accept the values and
proceed.
Cronjob installationThe system proceeds to install the Tivoli Netcool Performance Manager cronjobs.
Procedure1. You are prompted to install cronjobs:
Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no]>yesConfiguring core cronjobs.......
Enter yes.2. You are prompted to select the type of system you are installing:
What Type of PMW System Are you Installing ?-----------------------------------------------------------------------Please select the type of PMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)Database (5)Gateway (6)-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6 ] :
Enter 5 for database.3. You are prompted to enter the location of the Oracle home directory:
Server type selected: DBPlease enter the ORACLE_HOME Directory [/appl/oracle/product/12.1.0.2.0/db_2]:(Enter . if unknown)
Accept the default or /appl/oracle/product/12.1.0.2.0/db_2.4. You are prompted to enter the location of the Oracle base directory:
Please enter the ORACLE_BASE Directory [/appl/oracle]:(Enter . if unknown)
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 47
Accept the default path or enter the location of the Oracle base directory onyour computer.
5. You are prompted to enter the ORACLE_SID parameter:Please enter the ORACLE_SID Parameter [vtdb]:(Enter . if unknown)
Accept the default parameters or enter your Oracle SID parameters.6. You are prompted to enter the location of the vtdb database archive directory:
Please enter the vtdb Database Archive Directory [/oradump/vtdb]:(Enter . if unknown)
Accept the default path or enter the location of the vtdb database archivedirectory on your computer.The installation continues on to install the root user and virtuo user cronjobs.Setting up CRON environment ...
Filtering old cronjobs ....... Done
Setting up root cronjobs ...Finished setting up root cronjobsSetting up virtuo user cronjobs ...Finished setting up virtuo cronjobsRestarting Cron ...Stopping crond: [ OK ].... cron daemon stoppedStarting crond: [ OK ].... cron daemon started
Please view pmw_install.log for install details
Restarting Cron ...Stopping crond: [ OK ].... cron daemon stoppedStarting crond: [ OK ].... cron daemon started
The cronjob installation log output can be found at the following location:$WMCROOT/admin/logs/pmw_install.log
Encoding PasswordsThe system proceeds to encode the passwords that are stored in configuration files.
Procedure
You are asked if you want to encode the passwords:Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yes
Enter yes.The system proceeds to encode the passwords in the configuration files:Encoding values in /appl/virtuo/conf/as/as-default.propertiesEncoding values in /appl/virtuo/conf/as/as-default.properties.NEncoding values in /appl/virtuo/conf/dbconnection/vtdb.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.NEncoding values in /appl/virtuo/conf/ldap/default.properties.NEncoding values in /appl/virtuo/conf/ldap/default.propertiesPasswords may also be stored in/appl/virtuo/admin/logs/pmw_install.log,so it should be removed when not needed anymore.
The upgrade output is logged in the location:$WMCROOT/admin/logs/pmw_install.log
48 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Upgrading a separate directory serverThe installation of the directory server schema must be complete before youupgrade a separate directory server.
About this task
Important: This section must be completed only if the directory server schema isinstalled on a separate directory server.
Note: If the directory server schema is installed on the application server, see to“Upgrading the application server” on page 52.
To determine whether the directory server schema is installed on a directory server,check for the existence of the <WMCROOT> directory on the directory server. If thedirectory exists, the schema is installed. The <WMCROOT> directory is the locationwhere Tivoli Netcool Performance Manager, was previously installed. The defaultinstallation directory is /appl/virtuo.
Procedure1. Copy all of the Tivoli Netcool Performance Manager 1.4.3 core software
packages to the target directory.The target directory is the parent of the $WMCROOT directory where the currentrelease is installed.If $WMCROOT is set to /appl/virtuo, then the target directory is /appl
2. Run the following commands as user root: cd /<target_directory> kshpmw_install -wmcr <WMCROOT> -upgrade [-a]
where <WMCROOT> is the location where Tivoli Netcool Performance Manager,was previously installed. The default installation directory is /appl/virtuo.Use the -a option if you are installing a component in addition to an existingone. For example, a loader server in addition to a previously existingapplication server.The output is displayed:Making PMW top-level directory: /appl/virtuo
Making installation tasks record: /appl/virtuo/admin/install_tasks
Making software archive directories: under/appl/virtuo/admin/software
Looking for bootstrap package
Found vallent-vt-common-<version>.tar.gz
Extracting and running bootstrap package
Looking for bootstrap script
Running vallent-vt-common.install
Copyright 2017 IBM Ireland PDL, All Rights Reserved
This installation script will install the Performance Managementfor Wirelesscommon software version TNPM1.4.3 on your system.
Do you wish to continue?
3. Enter yes to continue.
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 49
4. The license agreement is displayed. You are prompted to accept the licenseterms.Do you agree with the terms of this license? Yes
Enter yes to agree to the license terms.5. The menu is displayed:
What Type of System Are you Installing ?1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit TNPMW Install---->
Select 4.6. The installation asks whether you want to deploy packages:
Do you want to deploy the packages? [yes/no] >yes
Enter yes.7. Verify the Environment Settings.
Please, Verify Environment Settings1. Accept Variable Values below2. Reset Variables to Default values3. Change WMCHOST=<server_name>..........................
The installation lists the default values of Tivoli Netcool Performance Managerenvironment variables. These variables set server host names and various TCPport numbers and varies from location to location. You can accept the defaultvalues, restore values to their default settings, or change individual values.
Important: You must set each of these environment variables to the correctvalue.
8. Select option 3 and change the value of WMCHOST to the host name of theapplication server.
9. Change any other values that you want to change from the default values.10. When you are satisfied that the environment variable values are correct,
accept the values and proceed.
Cronjob installationThe system proceeds to install the Tivoli Netcool Performance Manager cronjobs.
Procedure1. You are prompted to install cronjobs:
Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no]
Enter yes.2. You are prompted to select the type of system you are installing:
Please select the type of PMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)
50 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Database (5)Gateway (6)-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6 ] :
Enter 4 for directory server.3. You are prompted to enter the location of the Oracle home directory:
Server type selected: DBPlease enter the ORACLE_HOME Directory [/appl/oracle/product/12.1.0.2.0/db_2]:(Enter . if unknown)
Accept the default or /appl/oracle/product/12.1.0.2.0/db_2.4. You are prompted to enter the location of the vtdb database archive directory:
Please enter the vtdb Database Archive Directory [/oradump/vtdb]:
Accept the default.5. You are prompted to enter the location of the directory server log directory:
Please enter the Directory Server log Directory[/appl/ldap/idsslapd-idsinst/logs]:
(Enter . if unknown)
Accept the default.6. You are prompted to enter the location of the Tivoli Netcool Performance
Manager log directory:Please enter the PMW Log Directory[/appl/virtuo/logs]:
(Enter . if unknown)
Accept the default.7. You are prompted to enter the location of the PMW archive logs directory:
Please enter the PMW Archive Logs Directory[/data/trace_archive1]:
(Enter . if unknown)
Accept the default.The installation continues on to install the root user and virtuo user cronjobs.The cronjob installation log output can be found at the location:$WMCROOT/admin/logs/pmw_install.log
Encoding PasswordsThe system proceeds to encode the passwords that are stored in configuration files.
Procedure
You are asked if you want to encode the passwords:Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yes
Enter yes.The system proceeds to encode the passwords in the configuration files:Encoding values in /appl/virtuo/conf/as/as-default.propertiesEncoding values in /appl/virtuo/conf/as/as-default.properties.NEncoding values in /appl/virtuo/conf/dbconnection/vtdb.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.NEncoding values in /appl/virtuo/conf/ldap/default.properties.NEncoding values in /appl/virtuo/conf/ldap/default.propertiesPasswords may also be stored in/appl/virtuo/admin/logs/pmw_install.log.It should be removed when not needed.
The upgrade output is logged in the location:
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 51
$WMCROOT/admin/logs/pmw_install.log
Upgrading the application serverUpgrade the application server as described in the following procedure.
Procedure1. Copy all of the Tivoli Netcool Performance Manager 1.4.3 core software
packages to the target directory.The target directory is the parent of the $WMCROOT directory where the currentrelease is installed.For example, when $WMCROOT is set to /appl/virtuo, then the target directory is/appl.
2. Run the commands user root:cd <target_directory># ksh pmw_install -wmcr <WMCROOT> -upgrade
Where <WMCROOT> is the location where Tivoli Netcool Performance Managerwas previously installed.The default installation directory is /appl/virtuo.The output is displayed:Making PMW top-level directory: /appl/virtuoMaking software archive directories: under /appl/virtuo/admin/softwareLooking for bootstrap packageFound vallent-vt-common-TNPM1.4.3.0.tar.gzExtracting and running bootstrap packageLooking for bootstrap scriptRunning vallent-vt-common.installCopyright 2017 IBM Corporation, All Rights ReservedThis installation script will install the Tivoli Netcool Performance Manager commonsoftware version TNPM1.4.3.0 on your system.
Do you wish to continue? yes
3. Enter yes to continue.4. The license agreement is displayed. You are prompted to accept the license
terms.Do you agree with the terms of this license? YesRunning pre-install commandsBacking up old versions of non-shared files to be installedCreating installation directoriesInstalling softwareChecking configuration filesUpdating file permissionsSetting up init scriptsRunning post-install commands
Checking Virtuo File PermissionsSetup Virtuo profile
Setting up virtuo User Profiledone
Completed Virtuo Software InstallationLogs can be seen in pmw_install.logInstallation is complete.
Enter yes to agree to the license terms.5. The menu is displayed:
What Type of System Are you Installing ?1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only
52 IBM Tivoli Netcool Performance Manager: Upgrade Guide
5. Database Components only6. Skip package deployment7. Exit TNPMW Install---->
6. Select 2 for Application Server Components only.7. You are asked if you want to deploy packages:
Do you want to deploy the packages? [yes/no] >yes
Enter yes.
Configuring core softwareAbout this task
The system proceeds to install and configure the core software. You are promptedto verify the environment variables for certain packages:Please, Verify Environment Settings1. Accept Variable Values below2. Reset Variables to Default values3. Change WMCHOST=<server_name>4. Change VTDBHOST=<server_name>5. Change LDAPHOST=<server_name>
Environmental variablesThe installation displays a list of Tivoli Netcool Performance Managervariables. The variables have default values.
Important: You must check all the variables to ensure that they are set to thecorrect value and updated if appropriate. These variables set server host namesand various TCP port numbers. They vary from location to location.
A list is displayed. You can accept the default values listed, or to edit individualvalues.
Procedure1. Select option 4 and change the value of VTDBHOST to the host name of the
database server.2. If a separate directory server is configured, select option 5 and set the value of
LDAPHOST to the host name of the directory server.3. If required, change any other values.
JBoss application server updateThe system proceeds to update the JBoss application server configuration.
Procedure
You are asked if you would like to update the JBoss application server:Deploying JBoss 4.0.3SP1...Buildfile: /appl/virtuo/admin/common/install/scripts/build.xml
init:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/appl
upgrade:
init:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/appl
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 53
copy-libs:[copy] Copying 2 files to /appl/virtuo/as/server/default/lib[copy] Copying 10 files to /appl/virtuo/lib/tp
init:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/appl
fix-alarm-war:[mkdir] Created dir: /appl/virtuo/temp[mkdir] Created dir: /appl/virtuo/temp/war/apps/lib[unjar] Expanding: /appl/virtuo/as/server/default/deploy_core/
S02-na-alarm-manager.ear into /appl/virtuo/temp[unjar] Expanding: /appl/virtuo/lib/na-alarm-service-server.jar
into /appl/virtuo/temp
init:[echo] JBOSS VERSION=4.0.3SP1[echo] JBoss Location=/appl
signjarpmw:[echo] Signing JBoss client jar[exec][exec] Warning:[exec] The signer certificate has expired.[copy] Copying 1 file to /appl/virtuo/temp/war/apps/lib[jar] Updating jar: /appl/virtuo/temp/S02-na-alarm-manager.war[jar] Updating jar: /appl/virtuo/as/server/default/deploy_core/
S02-na-alarm-manager.ear
BUILD SUCCESSFULTotal time: 9 seconds
Cronjob installationThe system proceeds to install the Tivoli Netcool Performance Manager cronjobs.
Procedure1. You are prompted to install cronjobs:
Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no]>yes
Enter yes.2. You are prompted to select the type of system you are installing:
What Type of PMW System Are you Installing ?-----------------------------------------------------------------------Please select the type of PMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)Database (5)Gateway (6)-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6 ] :
Enter 2 for application.3. You are prompted to enter the location of the directory server log directory and
the Tivoli Netcool Performance Manager log directory:Please enter the Directory Server log Directory[/appl/ldap/idsslapd-idsinst/logs]:(Enter . if unknown)Please enter the PMW Log Directory [/appl/virtuo/logs]:(Enter . if unknown)
54 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Accept the defaults.4. You are prompted to enter the location of the Tivoli Netcool Performance
Manager archive logs directory:Please enter the PMW Archive Logs Directory[/data/trace_archive1]:(Enter . if unknown)
Accept the default.The installation continues on to install the root user and virtuo user cronjobs.The cronjob installation log output can be found at the location:$WMCROOT/admin/logs/pmw_install.log
Restoring configurationYou can automatically restore all the configuration values that were archived fromthe previous release.
About this task
If you do not want to keep any of the previous configuration values, enter nowhen prompted, and proceed to Synchronizing users.
Procedure
You are asked if you want to restore the configuration from the previous release.v Enter yes to restore all of the configuration settings from the previous release.
For a yes response, the system proceeds to restore configuration settings.v Enter no if you do not want to restore the configuration settings from the
previous release.
Synchronizing usersThe system proceeds to synchronize Tivoli Netcool Performance Manager andLDAP users.
Procedure
You are prompted to enter or confirm the system administrator user name andpassword.Executing/appl/virtuo/admin/common/install/upgrade/scripts/UPG06_sync_tnpm_ldap_admin...UPG06_sync_tnpm_ldap_admin: INFO: syncing tnpm and ldap usersEnter administrator username: : [<username>]---->Enter administrator password: [<password>]UPG06_sync_tnpm_ldap_admin: INFO: syncing of tnpm and ldap userscomplete/appl/virtuo/admin/common/install/upgrade/scripts/UPG06_sync_tnpm_ldap_admincomplete.
Encoding passwordsThe system proceeds to encode the passwords that are stored in configuration files.
Procedure
You are asked if you want to encode the passwords:Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yes
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 55
Enter yes.The system proceeds to encode the passwords in the configuration files:Encoding values in /appl/virtuo/conf/as/as-default.propertiesEncoding values in /appl/virtuo/conf/as/as-default.properties.NEncoding values in /appl/virtuo/conf/dbconnection/vtdb.propertiesEncoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.NEncoding values in /appl/virtuo/conf/ldap/default.properties.NEncoding values in /appl/virtuo/conf/ldap/default.propertiesPasswords may also be stored in/appl/virtuo/admin/logs/pmw_install.log.It should be removed if not needed.
Upgrading loader components on the application serverThe loader packages on the application server must be upgraded.
Procedure
Follow the instructions in Upgrading the loader server on the application server.When you run the pmw_install script again, you must use the -a option.
Upgrading the loader serverTo upgrade the loader server, copy all the Tivoli Netcool Performance Manager1.4.3 core software packages to the target directory.
Before you begin
The target directory is the parent of the $WMCROOT directory where the currentrelease is installed. For example, when $WMCROOT is set to /appl/virtuo, then thetarget directory is /appl.
Procedure1. Run the following commands as user root:
cd <target_directory>
# ksh pmw_install -wmcr <WMCROOT> -upgrade -a
Where <$WMCROOT> is the location where Tivoli Netcool Performance Managerwas previously installed.Use the -a option if you are installing the component in addition to an existingone. For example, a loader server in addition to a previously existingapplication server.The output is displayed:Making PMW top-level directory: /appl/virtuoMaking software archive directories: under /appl/virtuo/admin/softwareLooking for bootstrap packageFound vallent-vt-common-TNPM1.4.3.0.tar.gzExtracting and running bootstrap packageLooking for bootstrap scriptRunning vallent-vt-common.installCopyright 2012 IBM Corporation, All Rights ReservedThis installation script will install the Tivoli Netcool Performance Manager commonsoftware version TNPM1.4.3.0 on your system.
Do you wish to continue?
2. Enter yes to continue.3. When prompted, enter yes to accept the license terms.
56 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Do you agree with the terms of this license? Yes
Running pre-install commandsBacking up old versions of non-shared files to be installedCreating installation directoriesInstalling softwareChecking configuration filesUpdating file permissionsSetting up init scriptsRunning post-install commands
Checking Virtuo File PermissionsSetup Virtuo profile
Setting up virtuo User Profiledone
Completed Virtuo Software InstallationLogs can be seen in pmw_install.logInstallation is complete.
The menu is displayed.What Type of System Are you Installing?
1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Skip package deployment7. Exit PMW Install
4. Select 3 for Loader Components only.Checking packages: njloaderVerified the following packages:
* /appl/vallent-vt-njloader-TNPM1.4.3.0.tar.gz
5. You are asked if you want to deploy packages:Do you want to deploy the packages? [yes/no] >yes
Enter yes. You see the following output:Installing
njloader (TNPM1.4.3.0) ...
Please Verify Environment Settings
1. Accept Variable Values below2. Reset Variables to Default values3. Change LDRHOST=server.ibm.com4. Change WMCHOST=server.ibm.com5. Change VTDBHOST=server.ibm.com6. Change ORACLEPORT=15217. Change VTDBSID=vtdb8. Change VTDB_USERNAME=virtuo9. Change VTDB_PASSWORD=Virtuo0110. Change WMCROOT=/appl/virtuo11. Change WMCLOGDIR=/appl/virtuo/logs/12. Change WMCVARDIR=/appl/virtuo/var/13. Change SAPMONPORT=900914. Change OMPORT=900815. Change ASNSPORT=1099
6. Select 1 for Accept Variable Values below.The log output can be found at the following location:$WMCROOT/admin/logs/pmw_install.log
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 57
Configuring LoaderThe system proceeds to install and configure the loader software.
About this taskPlease, Verify Environment Settings1. Accept Variable Values below2. Reset Variables to Default values3. Change LDRHOST=<server_name>4. Change WMCHOST=<server_name>5. Change VTDBHOST=<server_name>.............
Environment variablesThe installation displays a list of Tivoli Netcool Performance Managervariables. The variables have default values. These variables set server hostnames and various TCP port numbers. They vary from location to location.You can accept the default values, restore values to their default settings,or change individual values.
Important: You must check all the variables to ensure that they are set to thecorrect value and updated if needed.
Procedure1. Select option 4 and change the value of WMCHOST to the host name of the
application server.2. Select option 5 and change the value of VTDBHOST to the host name of the
database server.3. If required, change other values.4. When the values are correct, accept the values and proceed.
Cronjob installationThe system proceeds to install the Tivoli Netcool Performance Manager cronjobs.
Procedure1. You are prompted to install cronjobs:
Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no]>yesConfiguring core cronjobs.......
Enter yes.2. You are prompted to select the type of system you are installing:
What Type of PMW System Are you Installing ?-----------------------------------------------------------------------Please select the type of PMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)Database (5)Gateway (6)-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6 ] :3
Enter 3 for Loader.3. You are prompted to enter the location of the Tivoli Netcool Performance
Manager log directory:
58 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Server type selected: LDRPlease enter the PMW Log Directory[/appl/virtuo/logs]:(Enter . if unknown)
Accept the default.4. You are prompted to enter the location of the Tivoli Netcool Performance
Manager archive logs directory:Please enter the PMW Archive Logs Directory[/data/trace_archive1]:(Enter . if unknown)
Accept the default.The installation continues on to install the root user and virtuo user cronjobs.Filtering old cronjobs ....... Done
Setting up root cronjobs ...Finished setting up root cronjobsSetting up virtuo user cronjobs ...Finished setting up virtuo cronjobsRestarting Cron ....... cron daemon stopped.... cron daemon started
Please view pmw_install.log for install details
The cronjob installation log output can be found at the location:$WMCROOT/admin/logs/pmw_install.log
Migrating loadersThe system migrates the loaders from the previous release. The migration is doneautomatically and no user intervention is required. The process is logged in the file<WMCROOT>/admin/logs/pmw_install.log.
About this task
Note: Complete this task on the application server only, and not on stand-aloneloader servers.Appserver ready.
Executing /appl/virtuo/admin/common/install/upgrade/scripts/
UPG01_loader_migrate...
UPG01_loader_migrate: INFO: Restarting sapmgr...
/appl/virtuo/admin/common/install/upgrade/scripts/UPG01_loader_migratecomplete.
The upgrade of the core software is complete. The upgrade output is logged in thelocation:$WMCROOT/admin/logs/pmw_install.log
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 59
Editing the default.properties fileEdit the default.properties file to add additional entries to deactivate thenetwork elements that do not have data for a specified number of days.
About this task
the default.properties file is located here:
/appl/virtuo/conf/nc_manager/default.properties
Procedure
Edit the file to add the following entries to thecom.ibm.tivoli.tnpmw.ncmanager.entities field:EUtranCell,EUtranRelation
Optional: Compiling SQL packages for ncmanager and ncarchivermanually
Use this information to compile create_nc_wk.sql, nc_mgr.sql, and nc_mgrb.sqlfiles manually.
About this task
This task is required only when ncmanager fails to run with the following error:PLS-00201: identifier ’NC_MGR.DEACTIVATE_NC’ must be declared
The create_nc_wk.sql located in the following path:/appl/virtuo/admin/oracle/schema/core/db/Oracle/nc_manager
Procedure1. Place the create_nc_wk.sql package in your local directory. For example, /appl.2. Change to the directory:
cd /appl
3. Connect to the database server by using sqlplus command as follows:virtuo/Virtuo01@vtdb
Where:v virtuo is the user namev Virtuo01 is the passwordv vtdb is the SID
4. Run the following command to compile:@create_nc_wk.sql
5. Compile the nc_archiver_update.sql, nc_archiver_updateb.sql,nc_archiver_pkg.sql, and nc_archiver_pkgb.sql by using the following steps:a. Change the directory:
cd /appl/virtuo/admin/oracle/schema/core/db/Oracle/nc_archiver
b. Connect to the database server by using sqlplus command as follows:virtuo/Virtuo01@vtdb
Where:
60 IBM Tivoli Netcool Performance Manager: Upgrade Guide
v virtuo is the user namev Virtuo01 is the passwordv vtdb is the SID
c. Run the following command to compile declaration package:@nc_archiver_update.sql
d. Run the following command to compile body of package:@nc_archiver_updateb.sql
e. Run the following command to compile declaration package:@nc_archiver_pkg.sql
f. Run the following command to compile body of package:@nc_archiver_pkgb.sql
Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 61
62 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Chapter 3. Upgrading the Security Directory Server and IBMDB2
Tivoli Netcool Performance Manager, 1.4.3 supports the Security Directory Server6.4 and IBM DB2 v10.5.0.4. If you installed these versions, you can ignore theinformation.
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.
Procedure1. Stop the sdsna.
For AIX, run the following command:
/etc/rc.d/init.d/sdsna stop
For Solaris, run the following command:svcadm disable sds-na
For Linux, run the following command:service sdsna stop
2. To upgrade Security Directory Server 6.4 and DB2 fix pack, run the followingcommand as the root user:/var/install/sbin/sds_install -base /appl -product virtuo -version 6.4 -upgradeEnter the full pathname of the DS package:/appl/depends/sds64/sds64-linux-x86-64-base.tarEnter the full pathname of the DS DB2 package:/appl/depends/sds64/sds64-linux-x86-64-db2.tarEnter the full pathname of the GSK package:/appl/depends/sds64/sds64-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 SDS....... 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 thatthis could cause issues with some tools.WARNING:The 32-bit library file libpam.so is not found on the system.
© Copyright IBM Corp. 2006, 2017 63
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 SDS 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 SDS instance from version 6.4. This may take several minutes...|DoneGenerating sds startup scripts ....Starting SDS processes...Done.
What to do next
See /var/install/logs/install_db2_patch_14134.log for log details.Related information:
Removing the previous Tivoli Directory Server and IBM DB2 Version
Upgrading from Tivoli Directory Server v6.3 to Security DirectoryServer v6.4
There is no direct upgrade from Tivoli Directory Server v6.3 to Security DirectoryServer v6.4 on RHEL 7.x system. You must first upgrade from Tivoli DirectoryServer 6.3 to Security Directory Server 6.3.1, and then proceed to upgrade toSecurity Directory Server 6.4.
Before you begin
Upgrade your Tivoli Netcool Performance Manager system to 1.4.3 before theSecurity Directory Server upgrade.
Procedure1. Stop the tdsna.
Run the following command:
/etc/rc.d/init.d/tdsna stop
Run the following command:svcadm disable tds-na
Run the following command:service tdsna stop
2. To upgrade 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:
64 IBM Tivoli Netcool Performance Manager: Upgrade Guide
/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 thatthis 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.3. Rename the existing 6.3 folder in /opt/IBM/ldap. For example,
/opt/IBM/ldap/old
4. Stop the sdsna.
Run the following command:/etc/rc.d/init.d/sdsna stop
Run the following command:svcadm disable sds-na
Run the following command:service sdsna stop
5. To install Security Directory Server 6.4 and DB2 fix pack, run the followingcommand as the root user:/var/install/sbin/sds_install -base /appl -product virtuo -version 6.4 -upgrade
Chapter 3. Upgrading the Security Directory Server and IBM DB2 65
# /var/install/sbin/sds_install -base /appl -product virtuo -version 6.4 -upgradeEnter the full pathname of the DS package: /appl/depends/sds64/sds64-solaris-sparc-base.tarEnter the full pathname of the DS DB2 package: /appl/depends/sds64/sds64-solaris-sparc-db2.tarEnter the full pathname of the GSK package: /appl/depends/sds64/sds64-solaris-sparc-gskit.tarEnter the full pathname of the SDS patch package, if required:Enter the full pathname of the DB2 patch package, if required:...performing pre-install steps for Security Directory ServerDOMAIN set to persistent.co.inShutting down TDS....... Unpacking IBM Security Directory Server.|\- taking backup for current tds instance OS SunOS TDSVERSION 6.4Backing up the DB2 database...DoneBacking up configuration and schema files...Done=== install_itds_files START ===Getting install file for DB2.... Installing IBM DB2 ESE. This may take several minutes...|DBI1324W Support of the db2_install command is deprecated. For
more information, see the DB2 Information Center.|The execution completed successfully.For more information see the DB2 installation log at "/tmp/db2_install.log.17480".LIC1402I License added successfully.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_14116.logRemoving temporary install files...|Make sure ldapdb.properties exist before migratingMigrating TDS instance from version 6.3.1. This may take several minutes.../DoneImporting /tmp/sdsvirtuo-na.xml into SMF repository... done
Manually cleaning up after a failed upgrade or installation of SecurityDirectory Server
Use this information to manually cleanup a failed upgrade or installation ofSecurity Directory Server.
Procedure1. Drop the ids instance by using this command:
/opt/ibm/ldap/V6.4/sbin/idsidrop -I idsinst
2. Delete the user idsinstall with this command:userdel idsinst
3. Uninstall the rpm packages with this command:rpm -e --nodeps --noscirtps <rpm_name>
4. Uninstall DB2 database with this command:/opt/ibm/sdsdb2V10.5/install/db2_deinstall -a
5. Remove the following folders:v /opt/IBM/ldap
v /opt/ibm/sdsdb2V10.5
v /appl/ldap
v /appl/idsinst
v /var/idsldap
v /usr/lib/ldap/idsconfig
v ~idsinst/sqllib
v /var/db2/global.reg
6. Restart the server and start your upgrade or installation again.
66 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Locating the required packagesThe required packages for the installation are distributed on the Tivoli NetcoolPerformance Manager installation media in the folder depends/sds63.
v IBM Security Directory Server 6.4 Client-Server with entitlement Solaris(sds64-solaris-sparc-base.tar)
v IBM Security Directory Server 6.4 GSkit Solaris (sds64-solaris-sparc-gskit.tar)
v IBM Security Directory Server 6.4, DB2 v10.5 Solaris (sds64-solaris-sparc-db2.tar)
v IBM Security Directory Server 6.4 Client-Server with entitlement Linux x86-64(sds64-linux-x86_64-base.tar)
v IBMSecurity Directory Server 6.4 GSkit Linux x86-64 (sds64-linux-x86_64-gskit.tar)
v IBM Security Directory Server 6.4, DB2 v10.5 Linux x86-64 (sds64-linux-x86_64-db2.tar)
v IBM Security Directory Server 6.4 Client-Server with entitlement AIX(sds64-aix-ppc64-base.tar)
vIBM Security Directory Server 6.4 GSkit AIX (sds64-aix-ppc64-gskit.tar)
v IBM Security Directory Server 6.4, DB2 v10.5 AIX (sds64-aix-ppc64-db2.tar)
Checking the installed versionsTivoli Netcool Performance Manager, version 1.4.3 supports IBM Security DirectoryServer 6.4 and DB2 10.5.
Procedure1. Run the following command as root user to check the Security Directory Server
version that is installed: # /opt/IBM/ldap/V6.4/bin/idsversion2. Run the following command as root user check the DB2 version that is
installed: # /usr/local/bin/db2ls
Chapter 3. Upgrading the Security Directory Server and IBM DB2 67
68 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Chapter 4. Post-upgrade tasks
After you upgrade the database to Oracle 12.1.0.2, complete the followingpost-upgrade tasks.
Before you begin
Ensure that the Oracle environment variables point to Oracle 12.1.0.2 as uservirtuo. To check this, follow these steps:1. Use the following command to show if any environment variable points to
Oracle 12.1.0.2 ORACLE_HOME path:env|grep 12.1.0.2
Example,$ env | grep 12.1.0.2PATH=/appl/virtuo/bin:/opt/IBM/ldap/V6.4/bin:/opt/IBM/ldap/V6.4/bin:/opt/IBM/ldap/V6.4/sbin:/usr/bin:/usr/sbin:/bin:/appl/oracle/product/12.1.0.2/db_2/bin
LD_LIBRARY_PATH=/appl/virtuo/shlib:/opt/IBM/ldap/V6.4/lib:/opt/IBM/ldap/V6.4/bin:/appl/oracle/product/12.1.0.2/db_2/lib
ORACLE_HOME=/appl/oracle/product/12.1.0.2/db_2virtuo@tnpminsunz10:
2. If any environment variable still points to Oracle 12.1.0.2 ORACLE_HOME Path,update the $HOME/.profile then log out and log back in.
3. Run the command that is mentioned in step number 1 again to make sure thatthere are no references to Oracle 12.1.0.2.
4. Run the following command in the application server as user virtuo:ksh <package_location>/wireless_db_post_install.kshksh wireless_db_post_install.kshThis will perform SCHEMA UPGRADE do you want to continue? [Y]YOK, continuing...Post-upgrade updates for TNPM Wireless Version 1.4.3Enter Oracle DB sys password:Adding Changes for Reenqueueing messages featureNo errors.No errors.No errors.No errors.Post-upgrade updates for TNPM Wireless Version 1.4.3 completed
Note: <package_location> is the directory where the Tivoli Netcool PerformanceManager 1.4.3 Wireless packages are located.
5. Check if /appl/oracle/product/12.1.0.2.0/db_1/network/admin/sqlnet.orafile has following setting:SQLNET.ALLOWED_LOGON_VERSION=8
If sqlnet.ora does not have SQLNET.ALLOWED_LOGON_VERSION=8, login as oracle,and then run following command:bash: echo ’SQLNET.ALLOWED_LOGON_VERSION=8’ >>/appl/oracle/product/12.1.0.2.0/db_1/network/admin/sqlnet.ora
6. Copy JDBC library files to Tivoli Netcool Performance Manager system.7. Ensure that oraclejdbc.jar from /appl/virtuo/lib/tp has same file size as
ojdbc7.jar from /appl/oracle/product/12.1.0.2.0/db_1/jdbc/lib.
© Copyright IBM Corp. 2006, 2017 69
If the file size is not the same, then run the following command as user virtuo:${WMCROOT}/admin/oracle/install/scripts/copy_jdbc_libs -wmcr ${WMCROOT}Copying database JDBC library files...Copying database library files...Done.
8.
Ensure that environment variableJAVA_TOOL_OPTIONS for virtuo user is correctly set as follows:env | grep JAVA_TOOL_OPTIONSJAVA_TOOL_OPTIONS=-Doracle.jdbc.autoCommitSpecCompliant=false
If it is not set, run following as user virtuo and confirm that it is set correctlyby using these commands:echo ’export JAVA_TOOL_OPTIONS=-Doracle.jdbc.autoCommitSpecCompliant=false’>> /export/home/virtuo/.profile
Set JAVA_TOOL_OPTIONS in /appl/virtuo/conf/as/jvm-default.ini by adding following line:export JAVA_TOOL_OPTIONS=-Doracle.jdbc.autoCommitSpecCompliant=false
What to do next
Complete the rest of the tasks as described in the following sections.
Customizing JBoss settingsIf you customize log settings for the JBoss, you must redo these changes.
About this task
If you modify the file <$WMCROOT>/as/server/default/conf/log4j.xml before youupgrade, and if you want to retain these changes, then you must edit the file againto retain these changes.
Procedure1. Open the 1.4.2 version of the log4j.xml file.
The 1.4.2 version of the file is archived in /appl/archive/virtuo.TNPM1.4.2.0/as/server/default/conf/log4j.xml.
2. Transfer all identified changes to the 1.4.2 log4j.xml contained in$WMCROOT/as/server/default/conf/log4j.xml
Process checks for SolarisCheck that all Tivoli Netcool Performance Manager processes start successfully forthe Solaris operating system.
A single command can be used to check the status of the system, as
user root:svcs -x appli*/virtuo*
Sample output:svc:/application/virtuo/sap-na:na (Virtuo SAP server instance na)State: online since Fri Oct 17 15:24:06 2011See: /var/svc/log/application-virtuo-sap-na:na.log
70 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Impact: None.svc:/application/virtuo/sapmgr-na:na (Virtuo SAP manager instancena)State: online since Fri Oct 17 16:26:21 2011See: /var/svc/log/application-virtuo-sapmgr-na:na.logImpact: None.svc:/application/virtuo/sapmon-na:na (Virtuo SAP monitor instancena)State: online since Fri Oct 17 15:13:32 2011See: /var/svc/log/application-virtuo-sapmon-na:na.logImpact: None.svc:/application/virtuo/sds-na:na(PMW SDS instance na)State: online since Fri Oct 17 15:08:53 2011See: /var/svc/log/application-virtuo-sds-na:na.logImpact: None.svc:/application/virtuo/database-na:global (NetworkAssure Databaseinstance)State: online since Fri Oct 17 14:33:49 2011See: /var/svc/log/application-virtuo-database-na:global.logImpact: None.
A status check can be run individually on each of the system's applications, thedirectory server, and the database.
For example:svcs -x /application/virtuo/sap-na
svcs -x /application/virtuo/database-na
Process checks for LinuxCheck that all Tivoli Netcool Performance Manager processes start successfully forthe Linux operating system.
Pass the status command to the init.d services, as user root:
service dboravirtuo statusservice sdsna statusservice sapmonvirtuo statusservice sapmgrvirtuo statusservice sapvirtuo status
Sample output:# service dboravirtuo statusDatabase listener is running.Database instance vtdb is running.
# service sdsna statusSDS LDAP server is runningSDS admin server is running
# service sapmonvirtuo statussapmon process running
# service sapmgrvirtuo statussapmgr process running
# service sapvirtuo statusNAME STATE SINCEas STARTED 17:21:28asd STARTED 17:25:04nc_cache STARTED 17:25:51alarm_cache STARTED 17:26:34
Chapter 4. Post-upgrade tasks 71
load_ericssonbss_r10 STARTED 17:26:39load_nokiabss_oss31ed3 STARTED 17:26:44load_motorolabss_gsr7 STARTED 17:26:49load_motorolautran_usr10 STARTED 17:26:54load_ericssonutran_r30 STARTED 17:26:59
Process checks for AIXRun process checks to ensure that the processes are running correctly.
On AIX, run the following commands to check the status of
processes:/etc/rc.d/init.d/dboravirtuo status/etc/rc.d/init.d/sdsna status/etc/rc.d/init.d/sapmonvirtuo status/etc/rc.d/init.d/sapmgrvirtuo status/etc/rc.d/init.d/sapvirtuo status
Sample output:# /etc/rc.d/init.d/dboravirtuo statusDatabase listener is running.Database instance vtdb is running.
# /etc/rc.d/init.d/sdsna statusSDS LDAP server is runningSDS admin server is running
# /etc/rc.d/init.d/sapmonvirtuo statussapmon process running
# /etc/rc.d/init.d/sapmgrvirtuo statussapmgr process running
# /etc/rc.d/init.d/sapvirtuo status
............
............
NAME STATE SINCEas STARTED Oct 08, 2017asd STARTED Oct 08, 2017nc_cache STARTED Oct 08, 2017alarm_cache STARTED Oct 08, 2017load_erics_r10 STARTED Oct 08, 2017load_nok_oss31ed3 STARTED Oct 08, 2017load_motor_gsr7 STARTED Oct 08, 2017load_erics_r30 STARTED Oct 08, 2017
Separate services are installed for each instance of Tivoli Common Reporting youinstalled on each server. Use the trcmd -checkstatus command to check the statusof a specific Tivoli Common Reporting component.Related information:
Tivoli Common Reporting commands
72 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Checking SAP processCheck that the Tivoli Netcool Performance Manager framework is started.
About this task
Process log files can be found in the location that is given by the value forWMCLOGDIR in the $WMCROOT/conf/environment/default.properties file. Ensure thatno exceptions occur in these files. If the process starts successfully, each process logfile returns a message that the process started successfully.
Procedure
Run the commands as user virtuo on the Tivoli Netcool Performance Managerserver:sap disp
The status of each process is displayed.Start any process that did not start, as user virtuo:sap start <process>
Rebooting the serverYou must reboot each server to ensure all of the processes start automatically andcorrectly.
About this task
Important: In a distributed installation, reboot each of the Tivoli NetcoolPerformance Manager servers in the following order:1. Database server2. Directory server3. Application server4. Loader servers
If any process is in a disabled state, it does not start automatically on reboot. If anySolaris SMF service is in a disabled state, it does not start automatically on reboot.
Procedure1. Check that all of the processes are running.2. Run the following command as user root on the server:
vshutdown -Fr
v/usr/sbin/shutdown -i6 -g0 -y
vshutdown -r now
Chapter 4. Post-upgrade tasks 73
What to do next
Disable the firewall. To check if the firewall is disabled, follow these steps:
For RHEL 7.x:v Checking status:
systemctl status firewalld
v Stopping the firewall:service firewalld stop
v Starting the firewall:service firewalld start
Starting the SAP servicesSAP services do not start automatically after the installation or upgrade for TivoliNetcool Performance Manager 1.4.3.
Procedure
Start the SAP services manually by following these steps:
# svcadm enable tatabase-na sds-na sapmon-sa sapmgr-na sap-na
# /etc/rc.d/init.d/dboravirtuo start# /etc/rc.d/init.d/sdsna start# /etc/rc.d/init.d/sapmonvirtuo start# /etc/rc.d/init.d/sapmgrvirtuo start# /etc/rc.d/init.d/sapvirtuo start
service dboravirtuo statusservice sdsna statusservice sapmonvirtuo statusservice sapmgrvirtuo statusservice sapvirtuo status
Tivoli Netcool Performance Manager core processes stop/startThe Tivoli Netcool Performance Manager core processes have a stop/start function
About this task
Stop the core framework:
Procedure1. Running the commands as user virtuo on the Tivoli Netcool Performance
Manager server:sap stop
2. Enter y to the prompt:Stop all registered processes [y/n]?
3. To start all the stopped services, run the following command as user virtuo onthe Tivoli Netcool Performance Manager server:
74 IBM Tivoli Netcool Performance Manager: Upgrade Guide
sap start assap start asdsap start nc_cachesap start alarm_cache
Starting the loadersEach installed loader must be started for the upgrade to take effect.
Procedure
For each installed loader run the command, as user virtuo:sap start <loadername>
Where <loadername> is the name of the installed loader.
Chapter 4. Post-upgrade tasks 75
76 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Chapter 5. Enabling Tivoli Common Reporting on TivoliNetcool Performance Manager
After 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.4.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.
Note: No support is provided for Model Maker.
© Copyright IBM Corp. 2006, 2017 77
78 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Chapter 6. Rolling back to the previous Tivoli NetcoolPerformance Manager version
During the Oracle 12c database upgrade trial period, if the performance or stabilityof the application is negatively impacted, you can revert to Tivoli NetcoolPerformance Manager Version 1.4.2. You can also roll back the database to OracleServer Version 12.1.0.2.
To reduce the application downtime, you must roll back the Oracle database to theprevious version. Oracle provides a database rollback procedure that Tivoli NetcoolPerformance Manager uses.
You can roll back Tivoli Netcool Performance Manager in two steps.1. Roll back the database to version 12.1.0.2 or restore the database from a
database backup that is taken before the upgrade.2. Restore Tivoli Netcool Performance Manager Version 1.4.2 from an archive that
is created during the application upgrade.
The exact database restoration procedure from the full pre-upgrade databasebackup depends on your backup environment and is not described in the guide.
Stopping Tivoli Netcool Performance Manager clientsAll clients must be notified that a rollback is taking place and all clients must bestopped before they continue with the rollback.
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:
v svcs sap-na
v service sapvirtuo status
v /etc/rc.d/init.d/sapvirtuo status
© Copyright IBM Corp. 2006, 2017 79
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
80 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Stopping the directory serverStop the server that acts as the directory server.
About this task
Note: In a distributed installation, this procedure must be performed on the serverthat acts as the directory server. It can be the application server or a separatedirectory server.
Stop the directory server.
Procedure
Run the command as user root:
v svcadm disable sds-na
v service sdsna stop
v /etc/rc.d/init.d/sdsna stop
Restoring the previous version of softwarePrevious versions must be restored on all Tivoli Netcool Performance Managerservers.
About this task
Note: Distributed system only. On a distributed installation, perform these stepson all the Tivoli Netcool Performance Manager servers.
To restore the previous version of the software:
Procedure
As user root on the Tivoli Netcool Performance Manager server run thecommands:# /var/install/sbin/archive_release -wmcr /appl/virtuo -product virtuo -restore
Process sap is not runningProcess sapmon is not runningProcess sapmgr is not runningdboravirtuo: unrecognized serviceProcess database is not runningPrevious release is TNPM1.4.2.0Removing existing /appl/virtuo......doneRestoring TNPM1.4.2.0 to /appl/virtuo......doneStarting Sds......doneRestoring package files from /appl/archive/software.TNPM1.4.2.0......doneRestoring user cron jobs......doneRestarting Cron ...Stopping crond: [ OK ].... cron daemon stoppedStarting crond: [ OK ].... cron daemon startedRestoring user profiles......doneRestoring release TNPM1.4.2.0 complete
Chapter 6. Rolling back to the previous Tivoli Netcool Performance Manager version 81
Checking processCheck all services and processes to ensure that they are running.
About this task
Note: In a distributed installation, perform these steps for all the Tivoli NetcoolPerformance Manager servers.
If some services or processes are not running, start them manually. Processes canbe checked using Checking process status.
To start processes manually:
Procedure1. Run the commands as user root:
svcadm enable tds-nasvcadm enable database-nasvcadm enable sapmon-nasvcadm enable sapmgr-nasvcadm enable sap-na
service tdsna startservice dboravirtuo startservice sapmonvirtuo startservice sapmgrvirtuo start
2. Run the commands as virtuo:sap start
3. Verify that all the processes start successfully:sap disp
Checking process statusUse process status checks if some services or processes are not running.
About this task
A single command can be used to check the status of the system, asuser root:svcs -x appli*/virtuo*
v Sample output:
82 IBM Tivoli Netcool Performance Manager: Upgrade Guide
svc:/application/virtuo/sap-na:na (Virtuo SAP server instance na)State: online since Fri Oct 17 15:24:06 2011See: /var/svc/log/application-virtuo-sap-na:na.logImpact: None.svc:/application/virtuo/sapmgr-na:na (Virtuo SAP manager instance na)State: online since Fri Oct 17 16:26:21 2011See: /var/svc/log/application-virtuo-sapmgr-na:na.logImpact: None.svc:/application/virtuo/sapmon-na:na (Virtuo SAP monitor instance na)State: online since Fri Oct 17 15:13:32 2011See: /var/svc/log/application-virtuo-sapmon-na:na.logImpact: None.svc:/application/virtuo/sds-na:na (PMW TDS instance na)State: online since Fri Oct 17 15:08:53 2011See: /var/svc/log/application-virtuo-sds-na:na.logImpact: None.svc:/application/virtuo/database-na:global (NetworkAssure Database instance)State: online since Fri Oct 17 14:33:49 2011See: /var/svc/log/application-virtuo-database-na:global.logImpact: None.
A status check can be run individually for each of the system's applications, thedirectory server, and the database. For example:
svcs -x /application/virtuo/sap-nasvcs -x /application/virtuo/database-na
Pass the status command to the init.d services, as user root:
service dboravirtuo statusservice tdsna statusservice sapmonvirtuo statusservice sapmgrvirtuo statusservice sapvirtuo status
Sample output:
# service dboravirtuo statusDatabase listener is running.
Database instance vtdb is running.
# service sdsna statusSDS LDAP server is runningSDS admin server is running# service sapmonvirtuo statussapmon process running
# service sapmgrvirtuo statussapmgr process running
# service sapvirtuo statusNAME STATE SINCEas STARTED 17:21:28asd STARTED 17:25:04nc_cache STARTED 17:25:51alarm_cache STARTED 17:26:34load_ericssonbss_r10 STARTED 17:26:39load_nokiabss_oss31ed3 STARTED 17:26:44load_motorolabss_gsr7 STARTED 17:26:49load_motorolautran_usr10 STARTED 17:26:54load_ericssonutran_r30 STARTED 17:26:59
Chapter 6. Rolling back to the previous Tivoli Netcool Performance Manager version 83
/etc/rc.d/init.d/dboravirtuo status/etc/rc.d/init.d/sdsna status/etc/rc.d/init.d/sapmonvirtuo status/etc/rc.d/init.d/sapmgrvirtuo status/etc/rc.d/init.d/sapvirtuo status
Sample output:
# /etc/rc.d/init.d/dboravirtuo statusDatabase listener is running.Database instance vtdb is running.
# /etc/rc.d/init.d/sdsna statusSDS LDAP server is runningSDS admin server is running
# /etc/rc.d/init.d/sapmonvirtuo statussapmon process running
# /etc/rc.d/init.d/sapmgrvirtuo statussapmgr process running
# /etc/rc.d/init.d/sapvirtuo status
............
............
NAME STATE SINCEas STARTED Oct 08, 2017asd STARTED Oct 08, 2017nc_cache STARTED Oct 08, 2017alarm_cache STARTED Oct 08, 2017load_erics_r10 STARTED Oct 08, 2017load_nok_oss31ed3 STARTED Oct 08, 2017load_motor_gsr7 STARTED Oct 08, 2017load_erics_r30 STARTED Oct 08, 2017
Tivoli Netcool Performance Manager core processes checkCheck the status of the Tivoli Netcool Performance Manager core processes.
About this task
Note: In a distributed installation, this procedure must be performed for theapplication server only.
Procedure
Run the commands as user virtuo:sap disp
The status of each process is displayed.Process log files can be found in the location set by the WMCLOGDIR value in the$WMCROOT/conf/environment/default.properties file.Ensure that no exceptions occur in these files. If the process starts successfully,each process log file must return the line Process Startup done when it startssuccessfully.
84 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Stopping and starting the Tivoli Netcool Performance Managercore processes
The Tivoli Netcool Performance Manager core processes have a stop/start function
About this task
Note: In a distributed installation, perform the steps for the application serveronly.
Stop the Tivoli Netcool Performance Manager for Wireless framework.
Procedure1. Run the commands as user virtuo:
sap stop
2. Restart the framework by running the command as user virtuo on the TivoliNetcool Performance Manager for Wireless server:sap start as
What to do next
Tivoli Netcool Performance Manager rollback requires that you edit thestartTCRserver.sh script and then use it to start Tivoli Common Reporting.1. Edit the Tivoli Common Reporting startup script at /opt/IBM/tivoli/
tipv2Components/TCRComponent/bin/startTCRServer.sh so that the$ORACLE_HOME parameter to points to the Oracle 12.1.0.2 home directory.
2. Ensure the environment variables for each user on each server in the systemare changed to use Oracle 12.1.0.2.
3. Restart Tivoli Common Reporting using the command:<tipComponents>/TCRComponent/bin/startTCRserver.sh <username> <password>
Where:v User: the Tivoli Integrated Portal administrator name.v Password: the Tivoli Integrated Portal administrator password.For example:/opt/IBM/tivoli/tip2Components/TCRComponent/bin/startTCRserver.sh tipadmin tipadmin
Starting the Tivoli Netcool Performance Manager cron jobsStart all the Tivoli Netcool Performance Manager cron jobs that are previouslystopped on each server.
About this task
For more information on stopping the cron jobs, see “Stopping the Tivoli NetcoolPerformance Manager cron jobs” on page 10.To edit the crontab directly, modify the following files:
Procedure1. Edit the following files:
v /var/spool/cron/crontabs/virtuo
v /var/spool/cron/crontabs/virtuo
Chapter 6. Rolling back to the previous Tivoli Netcool Performance Manager version 85
v /var/spool/cron/virtuo
2. Enable all those cron jobs that are commented out.3. Restart the cron daemons:
vps -ef | egrep [c]ron | awk ’{ print $2 }’ | xargs kill
vsvcadm restart cron
vsystemctl restart crond.service
86 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.11Solaris 11 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, 2017 87
-------------------------------------------------------------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>-------------------------------------------------------------
88 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 89
90 IBM Tivoli Netcool Performance Manager: Upgrade Guide
Notices
This information was developed for products and services offered in the US. Thismaterial might be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.
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-1785US
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
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 jurisdictions do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement maynot apply to 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, 2017 91
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 provide 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 Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US
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.
The performance data discussed herein is presented as derived under specificoperating conditions. Actual results may vary.
The client examples cited are presented for illustrative purposes only. Actualperformance results may vary depending on specific configurations and operatingconditions.
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.
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 actual people or business enterprises is entirelycoincidental.
COPYRIGHT LICENSE:
92 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:
© (your company name) (year).Portions of this code are derived from IBM Corp. Sample Programs.© Copyright IBM Corp. _enter the year or years_.
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 "Copyright andtrademark information" 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.
Notices 93
Java and all Java-based trademarks and logosare trademarks or registered trademarks ofOracle 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.
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.
94 IBM Tivoli Netcool Performance Manager: Upgrade Guide
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.
Notices 95
96 IBM Tivoli Netcool Performance Manager: Upgrade Guide
IBM®
Printed in USA
