with ibm corp. · performing a cold backup of the oracle 1 1g database ..... . 18 changing...

IBM Tivoli Netcool Performance Manager 1.4.2Wireless ComponentDocument Revision R2E2

Upgrade Guide

IBM

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

© Copyright IBM Corporation 2006, 2016.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 . . . . . . . . . . 7Removing the Oracle 11g platform packages . . . . 8Upgrading the platform package . . . . . . . 9Stopping Tivoli Netcool Performance Manager clients 9Stopping the application server and loaders . . . . 9Stopping the Tivoli Netcool Performance Managerframework . . . . . . . . . . . . . . 10Stopping the SAP manager . . . . . . . . . 10Stopping the SAP monitor . . . . . . . . . 11Stopping the Tivoli Netcool Performance Managercron jobs . . . . . . . . . . . . . . . 11Checking the database status . . . . . . . . 12Running the Dependency Checker tool . . . . . 14Performing a cold backup of the Oracle 11gdatabase . . . . . . . . . . . . . . . 18Changing ORACLE_HOME path . . . . . . . 18Running Oracle installation with upgrade option . . 19Changing ORACLE_HOME path to previousversion . . . . . . . . . . . . . . . . 21Upgrading to Oracle 12c (12.1.0.2) . . . . . . . 21Upgrading Oracle database . . . . . . . . . 21Running the post-installation SQL scripts . . . . 22Updating the oratab file . . . . . . . . . . 23Updating the .profile file . . . . . . . . . . 23

Restarting the database . . . . . . . . . 24Verifying the Oracle upgrade . . . . . . . . 25Upgrading Jazz for Service Management . . . . 25

Common directory locations for Jazz for ServiceManagement . . . . . . . . . . . . . 25Preparing your environment for a full installationof Jazz for Service Management . . . . . . 29Location of Jazz for Service Managementsoftware . . . . . . . . . . . . . . 30Overview of Jazz for Service Managementinstallation . . . . . . . . . . . . . 30Verifying the installation . . . . . . . . . 36

Uninstalling Jazz for Service Management . . . 39Adding the LDAP user registry as a federatedrepository . . . . . . . . . . . . . . . 40

Configuring the LDAP federated repository . . 41Single sign-on . . . . . . . . . . . . 42Configuring single sign-on . . . . . . . . 43

Upgrading Tivoli Common Reporting . . . . . 44Upgrading Tivoli Common Reporting to 3.1.2.1 44Upgrading the content store from older versionsof Tivoli Common Reporting . . . . . . . 46

Chapter 2. Tivoli Netcool PerformanceManager Software Upgrade . . . . . . 47Pre-upgrade checklist . . . . . . . . . . . 47Archiving the previous release . . . . . . . . 47Upgrade scenarios . . . . . . . . . . . . 48Upgrading a stand-alone system . . . . . . . 48

Configuring core software . . . . . . . . 49Upgrading the JBoss application server . . . . 50Cronjob installation. . . . . . . . . . . 51Restoring configuration . . . . . . . . . 52Migrating loaders . . . . . . . . . . . 53Synchronizing users . . . . . . . . . . 53Encoding Passwords . . . . . . . . . . 53

Upgrading a distributed system . . . . . . . 54Running an interactive upgrade . . . . . . 54Upgrading the database server . . . . . . . 55Upgrading a separate directory server . . . . 60Upgrading the application server . . . . . . 63Upgrading the loader server . . . . . . . . 68

Chapter 3. Upgrading the SecurityDirectory Server and IBM DB2 . . . . 73Upgrading from Tivoli Directory Server v6.3 toSecurity Directory Server v6.4 . . . . . . . . 74Manually cleaning up after a failed upgrade orinstallation of Security Directory Server . . . . . 76Locating the required packages . . . . . . . . 77Checking the installed versions . . . . . . . . 77

Chapter 4. Post-upgrade tasks . . . . 79Customizing JBoss settings . . . . . . . . . 80Process checks for Solaris . . . . . . . . . . 80Process checks for Linux . . . . . . . . . . 81Process checks for AIX. . . . . . . . . . . 82Checking SAP process . . . . . . . . . . . 82Rebooting the server . . . . . . . . . . . 83Starting the SAP services . . . . . . . . . . 84Tivoli Netcool Performance Manager core processesstop/start . . . . . . . . . . . . . . . 84Starting the loaders . . . . . . . . . . . . 85

© Copyright IBM Corp. 2006, 2016 iii

Chapter 5. Enabling Tivoli CommonReporting on Tivoli NetcoolPerformance Manager . . . . . . . . 87

Chapter 6. Rolling back to the previousTivoli Netcool Performance Managerversion . . . . . . . . . . . . . . 89Stopping Tivoli Netcool Performance Managerclients . . . . . . . . . . . . . . . . 89Stopping the Tivoli Netcool Performance Managerframework . . . . . . . . . . . . . . 89Stopping the SAP manager . . . . . . . . . 90Stopping the SAP monitor . . . . . . . . . 90Stopping the directory server . . . . . . . . 91

Restoring the previous version of software . . . . 91Checking process . . . . . . . . . . . . 92

Checking process status . . . . . . . . . 92Stopping and starting the Tivoli NetcoolPerformance Manager core processes . . . . . 95

Starting the Tivoli Netcool Performance Managercron jobs . . . . . . . . . . . . . . . 95

Appendix. Dependency Checker errors 97

Notices . . . . . . . . . . . . . . 101Trademarks . . . . . . . . . . . . . . 103Terms and conditions for product documentation 104

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, 2016 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

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

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

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

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

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

https://tnpmsupport.persistentsys.com/training

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

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

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

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

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.1 to 1.4.2.

Upgrading to Tivoli Netcool Performance Manager 1.4.2 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) upgradeUpgrading to Oracle database version 11.2.0.4 to 12.1.0.2.

You must upgrade Oracle database version 11.2.0.4 to 12.1.0.2 separately.

Server hardware and software requirements

Ensure that you have the necessary server hardware and softwarerequirements.

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

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

v 4 x UltraSPARC IV, IV+

v 4 x x86-64 dual-core processors

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

© Copyright IBM Corp. 2006, 2016 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) 6.x, and 7.x

v IBM AIX 6.1 and 7.1

v Oracle Solaris 10 Update 8

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.2.1

Tivoli Common Reporting 3.1.2.1

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

JBoss Application Server 4.0.3 Service Pack 1

Perl 5.6.1 for Gateway servers on Solaris and RHEL

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

Product Version

IBM Security Directory Server (required) 6.4

IBM DB2 (required) 10.5 (version 10.5.0.4)

2 IBM Tivoli Netcool Performance Manager: Upgrade Guide

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


Product Version

IBM Tivoli Monitoring agent script(optional)

6.3

IBM Java 1.7.0 SR8 FP10 64-bit

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

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

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

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

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

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

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

SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt SUNWcsl 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 14 for details of the tool.

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

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

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

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

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


The architecture is displayed in bold for each package listed.

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

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 6.xcompat-libstdc++-296,2.96,144.el6,i686libstdc++,4.4.6,3.el6,i686compat-libstdc++-33,3.2.3,69.el6,x86_64compat-libstdc++-33,3.2.3,69.el6,i686compat-gcc-34,3.4.6,4,x86_64compat-gcc-34-c++,3.4.6,4,x86_64compat-libf2c-34,3.4.6,19.el6,x86_64compat-libf2c-34,3.4.6,19.el6,i686kernel-headers,2.6.18,53.el5,x86_64glibc-headers,2.5,18,x86_64glibc-devel,2.12,1.47.el6,x86_64glibc-devel,2.12,1.47.el6,i686libgomp,4.1.2,14.el5,x86_64

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_64glibc-headers,2.5,18,x86_64glibc-devel,2.5,18,x86_64glibc-devel,2.5,18,i386libgomp,4.1.2,14.el5,x86_64

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 6.xcompat-libstdc++-33,3.2.3,69.el6,x86_64compat-libstdc++-33,3.2.3,69.el6,i686glibc,2.5,24,x86_64glibc,2.3.4,2,i686openmotif22,2.2.3,19.el6,x86_64openmotif22,2.2.3,19.el6,i686

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



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

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

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.proctoolsxlC.aix61.rte:9.0.0.1 or later (AIX 6.1)xlC.rte:9.0.0.1 or later (AIX 6.1)

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

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

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

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

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

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

GatewaysGateway upgrades are not part of the core upgrade procedure.

For information about upgrading gateways, see the IBM Tivoli Netcool PerformanceManager Gateways Installation Note.

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


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

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

Note: This command updates /etc/sysctl.conf file and the original file/etc/original_sysctl.conf is backed up.

# shutdown –Fr

Removing the Oracle 11g platform packagesBefore you start the upgrade, you must remove the Oracle 11g Platform package.

Procedure

Run the remove script as root user by using the following commands:./ibm-tn-plat-install.remove

All the platform packages are removed.


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.

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


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


Procedure1. Run the command as user root:

v svcadm disable sapmgr-na

v service sapmgrvirtuo stop

v /etc/rc.d/init.d/sapmgrvirtuo stop


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:


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/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:

vps -ef | egrep [c]ron | awk ’{ print $2 }’ | xargs kill

vsvcadm restart cron


vservice crond restart

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

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.

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)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: OKPerforming 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 6.5(Santiago) is at supported level.-------------------------------------------------------------Perform Host Setup configuration checks-------------------------------------------------------------Domain (none) is set but tnpminlnx0204.(none) cannot be reachedGYMWI0002E FAIL: No domain name configured-------------------------------------------------------------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: 2.96.138Checking package: compat-libstdc++-296 i386... Status: *** Missing ***pkg_full_version: 3.2.3.61Checking package: compat-libstdc++-33 x86_64... Status: OKpkg_full_version: 3.2.3.61Checking package: compat-libstdc++-33 i386... Status: *** Missing ***pkg_full_version: 3.4.6.4Checking package: compat-gcc-34 x86_64... Status: OKpkg_full_version: 3.4.6.4Checking package: compat-gcc-34-c++ x86_64... Status: OKpkg_full_version: 3.4.6.4Checking package: compat-libf2c-34 x86_64... Status: OKpkg_full_version: 3.4.6.4Checking package: compat-libf2c-34 i386... Status: *** Missing ***pkg_full_version: 2.6.18.53.el5LinuxFriday, April 08, 2016 10:15 AMpkg_full_version: 2.6.18.53.el5Checking package: kernel-headers x86_64... Status: OKpkg_full_version: 2.5.18Checking package: glibc-headers x86_64... Status: OKpkg_full_version: 2.5.18Checking package: glibc-devel x86_64... Status: OKpkg_full_version: 2.5.18Checking package: glibc-devel i386... Status: *** Missing ***pkg_full_version: 4.1.2.14.el5Checking package: libgomp x86_64... Status: OKGYMWI0020E FAIL: sds Linux packages are missing-------------------------------------------------------------Checking installed Linux packages for oracle-------------------------------------------------------------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.17.50.0.6.0.el5Checking package: binutils x86_64... Status: OKpkg_full_version: 4.1.25.9Checking package: compat-db x86_64... Status: OKpkg_full_version: 3.2.3.61Checking package: compat-libstdc++-33 x86_64... Status: OKpkg_full_version: 3.2.3.61Checking package: compat-libstdc++-33 i386... Status: *** Missing ***pkg_full_version: 2.96.138


Checking package: compat-libstdc++-296 i386... Status: *** Missing ***pkg_full_version: 2.16.0.14.el5Checking package: control-center x86_64... Status: OKpkg_full_version: 0.125.0Checking package: elfutils-libelf-devel x86_64... Status: OKpkg_full_version: 4.1.2.0.el5Checking package: gcc x86_64... Status: OKpkg_full_version: 4.1.2.0.el5Checking package: gcc-c++ x86_64... Status: OKpkg_full_version: 2.5.24Checking package: glibc x86_64... Status: OKpkg_full_version: 2.3.4.2Checking package: glibc i686... Status: OKpkg_full_version: 2.5.12Checking package: glibc-common x86_64... Status: OKpkg_full_version: 2.5.12Checking package: glibc-devel x86_64... Status: OKpkg_full_version: 2.5.12Checking package: glibc-devel i386... Status: *** Missing ***pkg_full_version: 2.5.12Checking package: glibc-headers x86_64... Status: OKpkg_full_version: 4.1.2.0.el5Checking package: libgcc x86_64... Status: OKpkg_full_version: 4.1.1.52.el5Checking package: libgcc i386... Status: *** Missing ***Checking package: libgcc i386... Status: *** Missing ***pkg_full_version: 0.3.106.0Checking package: libaio x86_64... Status: OKpkg_full_version: 0.3.106.0Checking package: libaio i386... Status: *** Missing ***pkg_full_version: 0.3.106.0Checking package: libaio-devel x86_64... Status: OKpkg_full_version: 0.3.106.0Checking package: libaio-devel i386... Status: *** Missing ***pkg_full_version: 3.4.3.9.EL4Checking package: libstdc++ x86_64... Status: OKpkg_full_version: 3.4.3.22.1Checking package: libstdc++-devel x86_64... Status: OKpkg_full_version: 4.1.2.0.EL5Checking package: libgomp x86_64... Status: OKpkg_full_version: 1.0.0.8.el5Checking package: libXp i386... Status: *** Missing ***pkg_full_version: 1.0.0.8.el5Checking package: libXp x86_64... Status: OKpkg_full_version: 3.81.1.1Checking package: make x86_64... Status: OKpkg_full_version: 7.0.2.0.el5Checking package: sysstat x86_64... Status: OKGYMWI0020E FAIL: oracle Linux packages are missing-------------------------------------------------------------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: 3.2.1.18.el5Checking package: eclipse-ecj x86_64... Status: *** Missing ***pkg_full_version: 1.2.3.3Checking package: zlib-devel x86_64... Status: OKpkg_full_version: 4.1.2.14.el5Checking package: libgcj-devel x86_64... Status: OKpkg_full_version: 4.1.2.14.el5Checking package: gcc-java x86_64... Status: OKpkg_full_version: 1.4.2.0.40jpp.112Checking package: java-1.4.2-gcj-compat-devel x86_64...

Status: *** Missing ***GYMWI0020E FAIL: jboss Linux packages are missing-------------------------------------------------------------Perform Filesystem configuration checks-------------------------------------------------------------Using /home instead of /export/homeChecking space on / partition...OK-------------------------------------------------------------Perform Oracle configuration checksPerform Oracle configuration checks-------------------------------------------------------------Checking if Oracle User exists... OKChecking oracle user shell... OKChecking oracle user umask... OK


Checking oracle group... OKOracle inventory directory /appl/oracle/product/oraInventory does not exist-------------------------------------------------------------Perform TNPM core package checks-------------------------------------------------------------Checking for core packages in /applChecking for package jre... OKChecking for package ant... OKChecking for package java-libs... OKChecking for package as-core... OKChecking for package core... OKChecking for package sap... OKChecking for package njloader... OKChecking for package ds-conf... OKChecking for package db-install... OKChecking for package db-conf... OKChecking for pmw_install... OKChecking for Platform package... missingEnter an alternative location for the core packages or Q to skip this check: QGYMWI0047E FAIL: TNPM core packages not found-------------------------------------------------------------Checking for JBoss package--------------------------------------------------------------------------------------------------------------------------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 ... MissingJazz SM and TCR are not installed on the system.GYMWI0069E FAIL: Missing Jazz SM & TCR Installation-------------------------------------------------------------Perform files checks-------------------------------------------------------------Checking required files.../usr/bin/ksh: OK-------------------------------------------------------------The following tests failed --you must investigate and fixthese failures before beginning the installation-------------------------------------------------------------FAILURE: 1GYMWI0002E No domain name configuredYou must set up a domain name on the server and ensure the fully qualified hostname is valid-------------------------------------------------------------FAILURE: 2GYMWI0020E sds Linux packages are missingcompat-libstdc++-296:i386 compat-libstdc++-33:i386compat-libf2c-34:i386 glibc-devel:i386-------------------------------------------------------------FAILURE: 3GYMWI0020E oracle Linux packages are missingcompat-libstdc++-33:i386 compat-libstdc++-296:i386 glibc-devel:i386libgcc:i386 libaio:i386 libaio-devel:i386 libXp:i386-------------------------------------------------------------FAILURE: 4GYMWI0020E jboss Linux packages are missingeclipse-ecj:x86_64 java-1.4.2-gcj-compat-devel:x86_64-------------------------------------------------------------FAILURE: 5GYMWI0047E TNPM core packages not foundThe following core packages could not be found: ibm-tn-plat-install-------------------------------------------------------------FAILURE: 6GYMWI0069E 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 97.

Performing a cold backup of the Oracle 11g databaseCopy of all database files; data files (*.dbf) files, online redo log files (*.log), anddatabase control files (*.ctl) that are associated with the Oracle 11g databaseinstance.

About this task

Take complete backup of the following files:v oradata01v oradata02v oradata03v oradata04v oratempv oradumpv oralogs1v oralogs2

.

Changing ORACLE_HOME pathChange the ORACLE_HOME path with these instructions. Ensure that all variables areset to point to Oracle 12.1.0.2.

Procedure1. Update ${HOME}/.profile file as oracle user as follows:

From:/appl/oracle/product/11.2.0/db_1

To:/appl/oracle/product/12.1.0.2.0/db_1

2. Change the following variables to show correct ORACLE_HOME as oracle user:v PATH

v LD_LIBRARY_PATH

v ORACLE_HOME

v ORACLE_SID


export PATH=/usr/bin::/appl/oracle/product/12.1.0.2.0/db_1/bin:/usr/sbinexport LD_LIBRARY_PATH=/appl/oracle/product/12.1.0.2.0/db_1/libexport ORACLE_HOME=/appl/oracle/product/12.1.0.2.0/db_1export ORACLE_SID=vtdb

3. Update Oracle bin location in PATH variable as follows:Check the existing path location by using the following command:echo $PATH/usr/bin::/appl/oracle/product/11.2.0.4/db_1/bin:/usr/sbin

Change to new path location in the PATH variable as follows:appl/oracle/product/12.1.0.2.0/db_1/bin

4. Run the following command to ensure that all variables are pointing to correctORACLE_HOME:$env

Running Oracle installation with upgrade optionRun the oracle12C_install script to install Oracle 12c.

Procedure

Run the following command as root user with -upgrade option:#/var/install/sbin/oracle12C_install –upgrade


# /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


Changing ORACLE_HOME path to previous versionChange the ORACLE_HOME path with these instructions. Ensure that all variables areset to point to Oracle 11.2.0.4.

Procedure1. Update ${HOME}/.profile file as oracle user as follows:

From:/appl/oracle/product/12.1.0.2.0/db_1

To:/appl/oracle/product/11.2.0/db_1

2. Change the following variables to show correct ORACLE_HOME as oracle user:v PATH

v LD_LIBRARY_PATH

v ORACLE_HOME

v ORACLE_SID

export PATH=/usr/bin::/appl/oracle/product/11.2.0/db_1/bin:/usr/sbinexport LD_LIBRARY_PATH=/appl/oracle/product/11.2.0/db_1/libexport ORACLE_HOME=/appl/oracle/product/11.2.0/db_1

3. Update Oracle bin location in PATH variable as follows:Check the existing path location by using the following command:echo $PATH/usr/bin::/appl/oracle/product/12.1.0.2.0/db_1/bin:/usr/sbin

Change to new path location in the PATH variable as follows:appl/oracle/product/11.2.0/db_1/bin

4. Run the following command to ensure that all variables are pointing to correctORACLE_HOME:$env

Upgrading to Oracle 12c (12.1.0.2)You must manually upgrade Oracle 11.2.0.4 to 12.1.0.2.

Run script/var/install/sbin/fetch_files_for_oracle12c as root user by usingthe following command:#/var/install/sbin/fetch_files_for_oracle12c

This script copies the files from old ORACLE_HOME/dbs and ORACLE_HOME/network/admin to new ORACLE_HOME/dbs and ORACLE_HOME/network/admin.

Upgrading Oracle databaseYou require approximately 50 GB disk space available on the system.

Before you beginv Make sure that all paths are pointing to Oracle 11.2.0.

Procedure1. Run the following pre-upgrade SQL scripts to perform the needed tasks by

Oracle:


SQL> @/appl/oracle/product/12.1.0.2.0/db_1/rdbms/admin/preupgrd.sqlSQL> EXECUTE dbms_preup.purge_recyclebin_fixup;SQL>EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;

2. Run the following pre-upgrade fix up SQL scripts to recover any missing files:SQL>@/appl/oracle/cfgtoollogs/vtdb/preupgrade/preupgrade_fixups.sqlSQL>EXECUTE dbms_stats.gather_dictionary_stats;

3. Shut down the Oracle database by using this script:SQL>shutdown immediate

4. Change ORACLE_HOME path in PATH, LD_LIBRARY_PATH, ORACLE_HOME, andORACLE_SID variables as oracle user. See “Changing ORACLE_HOME path” onpage 18.

5. Run the following upgrade SQL scripts:SQL> startup upgradeSQL> exit sqlplus$ cd /appl/oracle/product/12.1.0.2.0/db_1/rdbms/admin$ /appl/oracle/product/12.1.0.2.0/db_1/perl/bin/perl catctl.pl catupgrd.sql

Note: The upgrade process might take a while to complete.Check the log files that available in the following locations for any errors:/appl/oracle/product/12.1.0.2.0/db_1/cfgtoollogs/vtdb/upgrade/upg_summary.log/appl/oracle/product/12.1.0.2.0/db_1/rdbms/admin/catupgrd0.log/appl/oracle/product/12.1.0.2.0/db_1/rdbms/admin/catupgrd1.log/appl/oracle/product/12.1.0.2.0/db_1/rdbms/admin/catupgrd2.log/appl/oracle/product/12.1.0.2.0/db_1/rdbms/admin/catupgrd3.log

Results

Oracle runs 73 processes run simultaneously as a part of this upgrade. It mighttake sometime for the completion of these processes.

What to do next

After these processes complete, run the post-upgrade fix scripts to commits all thechanges.

Running the post-installation SQL scriptsRun these SQL scripts.

Procedure1. Stop the database with the following command:

shutdown

Orshutdown immediate

2. Start the database with the following command:startup

3. Run the following post-upgrade scripts:SQL>@/appl/oracle/product/12.1.0.2.0/db_1/rdbms/admin/catuppst.sqlSQL>@/appl/oracle/product/12.1.0.2.0/db_1/rdbms/admin/utlrp.sqlSQL>@/appl/oracle/product/12.1.0.2.0/db_1/rdbms/admin/utluiobj.sqlSQL>@/appl/oracle/cfgtoollogs/vtdb/preupgrade/postupgrade_fixups.sqlSQL>EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;


Updating the oratab fileoratab is a file created by Oracle in the /etc or /var/opt/oracle directory whenyou install the software.

About this task

Update the oratab file as oracle user from Oracle 11 to 12 on AIX and Linuxsystems.

Procedure

1. oratab file is located in /var/opt/oracle directory. Edit the fileas follows:From:vtdb:/appl/oracle/product/11.2.0/db_1:Y

To:vtdb:/appl/oracle/product/12.1.0.2.0/db_1:Y

2. oratab file is located in /etc directory. Edit thefile as follows:From:vtdb:/appl/oracle/product/11.2.0/db_1:Y

To:vtdb:/appl/oracle/product/12.1.0.2.0/db_1:Y

Updating the .profile fileEdit the Oracle user .profile file to set the path to ORACLE_HOME permanently.

About this task

Update the .profile file that is available in /export/home/oracle directory asoracle user from Oracle 11 to 12.

Procedure

Edit the file as follows:From:ORACLE_HOME=/appl/oracle/product/11.2.0/db_1

To:ORACLE_HOME=/appl/oracle/product/12.1.0.2.0/db_1

What to do next

Shutdown the database and restart.Related tasks:“Restarting the database” on page 24In a distributed installation, this procedure must be performed for the databaseserver only.


Restarting the databaseIn a distributed installation, this procedure must be performed for the databaseserver only.

About this task

Use the command to verify whether the database is running or not:

svcs database-na

service dboravirtuo status

/etc/rc.d/init.d/dboravirtuo status

To restart the database:

Procedure

Run the command as user root:

v Stop a database service:svcadm disable database-na

Wait until the database instance is down; the command returns no rows:ps -ef|grep smon

Start a database instance:svcadm enable database-na

v Stop a database service:service dboravirtuo stop


Start a database instance:service dboravirtuo start

v Stop a database service:/etc/rc.d/init.d/dboravirtuo stop


Start a database instance:/etc/rc.d/init.d/dboravirtuo start


Verifying the Oracle upgradeCheck the version of Oracle.

Procedure

Run the following SQL command to check the version of Oracle that is running onyour system:select version from v$instance;

-----------------12.1.0.2.0

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.2.1 on a Solaris machinein a distributed or a stand-alone environment.Related information:

Installing Jazz for Service Management

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

Jazz for Service Management home directory

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

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


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_c_install_plan_maps.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_c_install_plan_maps.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_c_install.html

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.

Jazz for Service Management installation images home directory

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

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

IBM DB2 home

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


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

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

WebSphere Application Server home directory

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

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

Administration Services home directory

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

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

Administration Services UI home directory

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

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

Registry Services home directory

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

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

Security Services home directory

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

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

Dashboard Application Services Hub home directory

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


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

Dashboard Application Services Hub profile directory

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

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

Tivoli Common Reporting home directory

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

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

IBM Cognos installation directory

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

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

cognos

Full installation log directory

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

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

IBM Prerequisite Scanner installation directory

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

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

Common directory locations


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/ref/psc_r_pathnames.html

Preparing your environment for a full installation of Jazz forService Management

Perform these tasks to ensure that your environment is ready for the fullinstallation of Jazz for Service Management, such as checking prerequisites.

Before you begin

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

Note: Some antivirus software can interfere with the Jazz for Service Managementinstallation process. Before you install Jazz for Service Management, ensure thatyou disable the antivirus software and restart the target machine.

About this task

If your target system does not have a browser that is installed to supportinstallation by using the launchpad, use the Installation Manager GUI.

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

requirements for Jazz for Service Management and its integration services.See Hardware and software requirements.

2. Set up a local file system.See Setting up a local file system for a full installation.

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

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

5. Perform the full installation.See “Performing a fresh installation” on page 32.

Related information:

Jazz for Service Management on IBM Knowledge Center

IBM DB2 on IBM Knowledge Center

IBM Installation Manager on IBM Knowledge Center

IBM Prerequisite Scanner on IBM Knowledge Center

IBM WebSphere Application Server on IBM Knowledge Center


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


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_c_install_prereqs.html?lang=en-us

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_install_typical_local_sys.html?lang=en-us

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_c_install_alt_dir.html?lang=en-us

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_c_install_alt_dir.html?lang=en-us

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/ips_edit_jazzsm_cfg_files.html?lang=en-us

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/ips_edit_jazzsm_cfg_files.html?lang=en-us

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

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

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

http://www-01.ibm.com/support/knowledgecenter/SS2RKB_1.2.0.9/com.ibm.ips.doc_1.2.0.9/ips_ic-homepage.html

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

Location of Jazz for Service Management softwareDescribes the location of the Jazz for Service Management 1.1.2.1 software.

1.1.2-TIV-JazzSM-multi-FP001.zip - 64 bit, multiplatform software packagerepository contains the following Jazz for Service Management integration servicesand components:v Administration Services Version 1.1.2.1v Administration Services UI Version 1.1.2.1v IBM Dashboard Application Services Hub 3.1.2.1v Jazz for Service Management extension for IBM WebSphere Version 1.1.2.1v Registry Services 1.1.2.1v Security Services 1.1.2.1v IBM Tivoli Common Reporting 3.1.2.1

Note: Jazz for Service Management Version 1.1.2.1 is a full refresh of Jazz forService Management Version 1.1 Base with Modification 2, Fix Pack 1.

You can download Jazz for Service Management, Version 1.1.2.1 from IBM FixCentral.Related information:

Jazz for Service Management Version 1.1.2.1 Readme

Download Jazz for Service Management Version 1.1.2.1

Overview of Jazz for Service Management installationJazz for Service Management, Version 1.1.2.1 can be installed or updated, whenyou install it along with earlier Jazz for Service Management versions, for example,1.1.1.0.

Before you begin

Attention: Ensure that the package that you have downloaded is the latestrefresh of Jazz for Service Management, Version 1.1.2.1.1. Check that your environment meets the current requirements by running IBM

Prerequisite Scanner. Specify the update parameter when you run the relevantPrerequisite Scanner convenience script.See Running Prerequisite Scanner by running the convenience scriptsSee Running Prerequisite Scanner manually

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

3. Update your existing Installation Manager to Version 1.8.1 or later, before youupdate Jazz for Service Management.

4. Tivoli Common Reporting 3.1.2.1 supports rolling back and upgrading, but if arollback fails in its early stages, then you need to manually roll it back.See Restoring Cognos if Tivoli Common Reporting update fails on multipleplatforms.Back up your jazzSM_Home/reporting/cognos directory before you begin theupdate.


http://www.ibm.com/support/fixcentral/

http://www.ibm.com/support/fixcentral/



http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_install_prs_prereqs.html

https://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_install_run_prs_cli.html


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/tcr_original/tstcr_install_restoring_cognos.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/tcr_original/tstcr_install_restoring_cognos.html

About this task

Typically, there are two scenarios for installing Jazz for Service Management:v Upgrade installation, if you have an earlier version of Jazz for Service

Management on your system.See “Performing an upgrade installation.”

v Fresh installation.See “Performing a fresh installation” on page 32.

Performing an upgrade installationUse this installation procedure if you already have an earlier version of Jazz forService Management on your system. For example, 1.1.1.0.

Before you begin

Download platform-specific IBM Cognos Business Intelligence Reporting for TivoliCommon Reporting Version 3.1.2.1 (3.1.2.1-TIV-JazzSM-TCR-COGNOS-platform.tar.gz or the .zip) from Passport Advantage.

Note: You must update the installed integration services in the same applicationserver profile to the same fix pack level.

About this task

Use IBM Installation Manager in GUI or silent modes to first update the Jazz forService Management extension for IBM WebSphere. Then install Jazz for ServiceManagement Version 1.1.2.1 for the following installed integration services:v Administration Servicesv Administration Services UIv IBM Dashboard Application Services Hubv Registry Servicesv Security Servicesv Tivoli Common Reporting

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

Procedure1. Download and extract 1.1.2-TIV-JazzSM-multi-FP001.zip file to a local

directory from Fix Central page.For example, <JazzSM_FP_Home>

2. On each machine that has an Jazz for Service Management application server,update the Jazz for Service Management extension for IBM WebSphere.Updating the WebSphere security extension by using Installation ManagerGUI modeUpdating the WebSphere security extension by using Installation Managersilent mode

3. In a command window, open the /opt/IBM/InstallationManager/eclipse/IBM/InstallationManager/eclipse directory and run the following command:

./IBMIM

4. Set up the fix pack repository preference.


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

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_update_im_ext_fp3.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_update_im_ext_fp3.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_update_im_ext_fp3_silent.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_update_im_ext_fp3_silent.html

a. Select File > Preferences.b. In the Preferences > Repositories pane, click Add Repository.c. Click Browse and browse to the following location of the file:

<JazzSM_FP_Home>/1.1.2-TIV-JazzSM-multi-FP001/JazzSMFPRepository/disk1/diskTag.inf

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

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

6. Select the Jazz for Service Management software package group in which theintegration services are installed, and then click Next.

7. Select each check box that is associated with each installed component thatyou want to update, and click Next.The Licenses pane opens.

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

9. Select the features that you want to update, and click Next.10. In the Common Configurations tab, enter password for smadmin user.11. Click Validate.12. After the validation completes successfully, click Next.13. Continue with the installation and specify the configuration details for the

integration service that you want to update.For more information, see Integration services installation overview.

14. In the Summary pane, review the software packages that you want to installand click Update. After Installation Manager updates the fix pack, it displaysa message.

15. Click Finish.

What to do nextv Apply the 1.1.2.1-TIV-JazzSM-DASH-Cumulative-Patch-0005 interim fix of Jazz

for Service Management.v Verify the installation of the integration services.Related information:

Applying fix pack by using Installation Manager GUI mode

Applying fix pack by using Installation Manager silent mode

Jazz for Service Management Version 1.1.2.1 Readme

Restarting Jazz for Service Management application servers

Download Cumulative Patches - UI Services (DASH)

Performing a fresh installation20 GB of free disk space is required for a fresh installation.

Procedure1. Download and extract 1.1.2-TIV-JazzSM-multi-FP001.zip file to a different

local directory from Fix Central.


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_ctr_install_int_srvs.html?lang=en-us

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_update_im_fp3.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_update_im_fp3_silent.html


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/admin/psc_ctr_admin_restart_jazzsm_servers.html

https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7ETivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=all&source=fc

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

For example, <JazzSM_FP_Home>

Note: 6 GB of free disk space is needed for a fresh installation.2. Add the <JazzSM_FP_Home>/1.1.2-TIV-JazzSM-multi-FP001/

JazzSMFPRepository/disk1/diskTag.inf file along with the repositorylocations for any other earlier Jazz for Service Management versions toInstallation Manager > File > Preferences > Add Repository.

3. Start the launchpad by using the following command:<<JazzSM_FP_Home>>/launchpad.sh

Restriction: Ensure that the path to the <JazzSM_FP_Home> directory does notcontain any spaces or special characters, otherwise the launchpad does notstart.

Important:

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

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

4. Click Full.The Full Installation window opens.

5. Review the instructions in the Full Installation window, and click Next. TheFull Installation > Software License Agreement window opens.

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

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

7. Click Scan to run Prerequisite Scanner and scan your environment for the Jazzfor Service Management requirements.The launchpad runs the convenience script for a full installation and displaysthe overall result in the Prerequisite Scan window. To view the details, clickDetailed Scan Results. The results can be as follows:

Fail

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

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

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


Pass

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

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

8. Click Next.The Basic Settings window opens.

9. Verify, use, or enter the default values as needed:

Option Description

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

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

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

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

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

Important: If you are installing TivoliNetcool Performance Manager with DB2database, make sure that you set the DB2HOME directory to /opt/db2/product/10.5.0 during Jazz for Service Managementinstallation.

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

10. Click Next.The Installation Summary window opens.

11. Click Install.


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/ref/psc_r_pathnames.html?lang=en-us#psc_r_pathnames__was_home

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/ref/psc_r_pathnames.html?lang=en-us#psc_r_pathnames__db2_home

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/ref/psc_r_pathnames.html?lang=en-us#psc_r_pathnames__psc_home

After the installation is complete, the launchpad displays the overall result ofthe installation in the Installation Results window.

Results

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

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

What to do nextv Apply the 1.1.2.1-TIV-JazzSM-DASH-Cumulative-Patch-0005 interim fix of Jazz

for Service Management.v Verify the installation of the integration services.Related tasks:“Performing an upgrade installation” on page 31Use this installation procedure if you already have an earlier version of Jazz forService Management on your system. For example, 1.1.1.0.Related information:

Installing Reporting Services

Verifying the installation

Verifying the Reporting Services installation

Restarting Jazz for Service Management application servers

Download Cumulative Patches - UI Services (DASH)

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

Before you begin

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

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

Table 2. Location of the db2ese.rsp file

Option Description

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

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

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

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

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


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/tcr_t_install.html

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

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_install_adv_verification_tcr.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/admin/psc_ctr_admin_restart_jazzsm_servers.html

https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7ETivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=all&source=fc

Verifying the installationYou can verify the installation of IBM WebSphere Application Server Version 8.5.0.4and 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: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.


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/tip_original/ttip_start_logon.html?lang=en-us

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_ctr_install_post_install.html?lang=en

About this task

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

Dashboard Application Services Hub

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

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

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

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

Procedurev Access the reporting interface from Dashboard Application Services Hub as

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

Management UI and reporting server:https://host.domain:port/<DASH_context_root>For example: https://<myJazzSMserver.ibm.com>:16311/ibm/console– host.domain is the fully qualified host name or IP address of the Jazz for

Service Management UI and reporting server.

Note: When single sign-on (SSO) is enabled, ensure that you use the fullyqualified host name in the URL of the Jazz for Service 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.


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/tcr_original/ttcr_run_moswos.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/tcr_original/ttcr_run_moswos.html

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

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

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

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

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

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

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

What to do next

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

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

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

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


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/tcr_original/ttcr_config_sec.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_install_adv_verification_tcr.html

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

WAS_admin_user_nameThe default user name is smadmin.

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

Example

stopServer.sh server1 -username smadmin -password jazzsmpwd

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

About this task

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

Procedure1. On the 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.

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 yourenvironment after either a successful uninstallation or a failed installation.

About this task

Attention: You cannot roll back Tivoli Common Reporting Version 3.1.2.1 as itsupports only fresh installation. You can perform a full uninstallation of TivoliCommon Reporting.

Procedure

Use IBM Installation Manager in GUI or silent modes to uninstall Jazz for ServiceManagement Version 1.1.2.1.See Uninstalling fix packs by using Installation Manager GUI mode.See Uninstalling fix packs by using Installation Manager silent mode.


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_rollback_im_fp3.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_rollback_silent_fp3.html

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 fix packs

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

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.


https://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_t_rollback_fp3_oview.html

https://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/psc_c_install_uninstall_oview.html

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.

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


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. So


o=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.

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


click Security > Global security.4. In the Authentication area, expand Web security and click Single sign-on.5. Click the Enabled option if SSO is disabled.6. Click Requires SSL if all of the requests are expected to use HTTPS.7. Enter the fully-qualified domain names in the Domain name field where SSO

is effective. If the domain name is not fully qualified, the Jazz for ServiceManagement Server does not set a domain name value for the LtpaTokencookie and SSO is valid only for the server that created the cookie. For SSO towork across Tivoli applications, their application servers must be installed insame domain (use the same domain name).

8. Optional: Enable the Interoperability Mode option if you want to supportSSO connections in WebSphere Application Server version 5.1.1 or later tointeroperate with previous versions of the application server.

9. Optional: Enable the Web inbound security attribute propagation option ifyou want information added during the login at a specific Tivoli EnterprisePortal Server to propagate to other application server instances.

10. After clicking OK to save your changes, stop and restart all the Jazz forService Management Server instances.

What to do next

Note: When you launch Jazz for Service Management, you must use a URL in theformat protocol://host.domain:port /*. If you do not use a fully-qualifieddomain name, Jazz for Service Management cannot use SSO between Tivoliproducts.


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.2.1. 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.2.1.

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.2.1 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.2.1”Users 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 46.

Upgrading Tivoli Common Reporting to 3.1.2.1Upgrade your Tivoli Common Reporting Version 3.1.0.2 or 3.1.0.3 to Version 3.1.2.1.

Before you begin

Perform these tasks before you upgrade:v Install Jazz for Service Managementv Install Tivoli Common Reporting 3.1.2.1

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.2.1:

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.2.1.

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.

Results

You have upgraded your Tivoli Common Reporting to Version 3.1.2.1 together withall your reporting data. The following items were moved to Version 3.1.2.1: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.2.1 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.2.1 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


https://www.ibm.com/developerworks/mydeveloperworks/files/form/anonymous/api/library/9641dcf4-c5b8-413c-8ae8-9c461dd84a09/document/0cdff487-dee6-4070-941c-f40ed8d0afd1/media/Exporting-Importing%20Derby%20Content%20Store_v01.pdf




Chapter 2. Tivoli Netcool Performance Manager SoftwareUpgrade

Steps to upgrade Tivoli Netcool Performance Manager software to the currentversion.

Pre-upgrade checklistBefore you continue with the upgrade, ensure that the pre-upgrade steps arecomplete without errors.

Procedure Topic

The correct platform package is installed. The Platform packageNote: Make sure that Tivoli NetcoolPerformance Manager 1.4.1 patch is installedbefore you upgrade to 1.4.2

Correct version of Security Directory Serveris installed.

Make sure that you have Security DirectoryServer 6.3.1 on the system to upgrade to 6.4.

Important: Before you attempt an upgrade of Tivoli Netcool PerformanceManager, you are advised to read any Release Notes and any readme files that aredistributed with your Tivoli Netcool Performance Manager software. Release Notesand readme files can contain information specific to your upgrade that is notavailable in this information. Failure to consult the Release Notes or readme filescan result in a corrupted, incomplete, or failed installation. For all current knownissues, see the Known issues technical note for the current version.

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.


/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).

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.1.0 package files to /appl/archive/TNPM1.4.1.0_pkgs......doneArchiving /appl/virtuo to /appl/archive/virtuo.TNPM1.4.1.0......doneArchiving release TNPM1.4.1.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 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.2 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 packageFound vallent-vt-common-TNPM1.4.2.0.tar.gzExtracting and running bootstrap packageLooking for bootstrap scriptRunning vallent-vt-common.installCopyright 2016 IBM Corporation, All Rights ReservedThis installation script will install the Tivoli Netcool Performance Manager commonsoftware version TNPM1.4.2.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.

Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 49

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.2. When the variable values are correct, select the appropriate menu option to

accept the values.3. Repeat this procedure for each package that requires environment variables to

be 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:


copy-libs:[copy] Copying 2 files to /appl/virtuo/as/server/default/lib[copy] Copying 10 files to /appl/virtuo/lib/tp


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



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/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/11.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]:


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]:



Manager archive logs directory:Please enter the PMW Archive Logs Directory[/data/trace_archive1]:


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...

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

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.2 core software packages must be copied to the target directory.

Procedure1. Copy all of the Tivoli Netcool Performance Manager 1.4.2 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:Making PMW top-level directory: /appl/virtuoMaking software archive directories: under /appl/virtuo/admin/softwareLooking for bootstrap packageFound vallent-vt-common-TNPM1.4.2.0.tar.gzExtracting and running bootstrap packageLooking for bootstrap scriptRunning vallent-vt-common.installCopyright 2016 IBM Corporation, All Rights ReservedThis installation script will install the Tivoli Netcool Performance Manager commonsoftware version TNPM1.4.2.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.2.0.tar.gz/appl/vallent-vt-ant-TNPM1.4.2.0.tar.gz/appl/vallent-vt-db-install-TNPM1.4.2.0.tar.gz/appl/vallent-vt-db-conf-TNPM1.4.2.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.2.0) ... okant (TNPM1.4.2.0) ... tar: Read 5120 bytes from -okdb-install (TNPM1.4.2.0) ... okdb-conf (TNPM1.4.2.0) ... tar: Read 5120 bytes from

Configuring databaseThe system proceeds to install and configure the core database software.

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.

Upgrading database to Oracle 12.1.0.2The system proceeds to upgrade the database to Oracle 12.1.0.2.

Procedure1. Enter yes at the prompt to upgrade the database:

Would you like to perform task DB_UPGRADE? [yes/no]: yes

2. When prompted for the database System Identifier (SID), accept the defaultidentifier. If your SID differs from the default SID value, enter your SID.Please enter the Database SID: [vtdb]


3. You are prompted for the ADDM license type you have from Oracle. ADDM isan extra license that is required by Oracle for running Diagnostic or Tuningpacks. The valid options are NONE, DIAGNOSTIC, orDIAGNOSTIC+TUNING.Please enter your ADDM license type [NONE | DIAGNOSTIC | DIAGNOSTIC+TUNING ]: [NONE]---->ADDM license type is set to "NONE"

Accept the default or update it to the correct license type.4. You are prompted for the location of Oracle Home for 12.1.0.2.

Please enter the Oracle 12.1.0.2 Home: [/appl/oracle/product/12.1.0.2/db_1]---->Oracle 12.1.0.2 Home is set to "/appl/oracle/product/12.1.0.2/db_1"

Accept the default Oracle Home for 12.1.0.2 or update it to the correct locationto available on your server.

5. You are prompted for the location of Oracle Home for 12.1.0.2.Please enter the Oracle 12.1.0.2 Home: [/appl/oracle/product/12.1.0.2/db_2]

Oracle 12.1.0.2 Home is set to "/appl/oracle/product/12.1.0.2/db_2"

Accept the default Oracle Home for 12.1.0.2 or update it to the correct location.6. You are prompted for the password for the system database user.

Please enter the Database sys user password: [Sysdb01]Database user sys password set to "Sysdb01"

Either accept the default password or enter the correct password as Sysdb01.7. You are prompted for the password for the database system user.

Please enter the Database system user password: [Sysdb01]Database user system password is set to "Sysdb01"

Accept the default password or enter the correct password as Sysdb01.8. The system proceeds to upgrade the database from 11.2.0.4 to 12.1.0.2:

The time that it takes to upgrade the schema depends on the size of thedatabase. Upgrading a database from 11.2.0.4 to 12.1.0.2 takes a minimum of 2hours.Running Pre-Upgrade Checks... recompiling invalid objects... gather dictionary statisticsRunning the Database UpgradeStopping Oracle 11.2.0.4 listenerSetting up oracle User Profile.... Backing up existing profile to /export/home/oracle/.profile_20130607_11431Setting up virtuo User Profile.... Backing up existing profile to /export/home/virtuo/.profile_20130607_11431Setup Oracle 12.1.0.2 environment... create required Oracle 12.1.0.2 admin directoriesRunning Oracle 12.1.0.2 Net Configuration... start 12.1.0.2 listenerGenerating dbora startup scripts ....Waiting for DB listener for vtdbListener is up. Continuing...Run post upgrade actions to finish upgrade... create new VIRTUO_PROFILE and assign to VIRTUO user... disable audit_trail... Set control_management_pack_access to customer specified license... reset the aq_tm_processes parameter... disable default maintenance jobs... configure Dictionary Statistics Refresh... gather sys schema statistics

Upgrade has completedFor details check /appl/virtuo/admin/logs/pmw_install.log file


The upgrade log files can be found in the locations:$WMCROOT/admin/logs/pmw_install.log

$ORACLE_BASE/cfgtoollogs/dbua/logs/silent<x>.log

Database status checkThe dbstatus_report script is automatically run during the database engineversion upgrade. Examine the results at $WMCROOT/admin/oracle/upgrade/log/upgrade_database_<timestamp>.log for details.If there are any database components or objects with a status of INVALID orconstraints in a DISABLED state, the upgrade reports errors like the followingerrors.ERROR: Disabled constraints found after DB upgrade:

Constraint name: <constraint>

...

The cause of these disabled constraints should be investigatedbefore continuing the upgrade.

See/appl/virtuo/admin/oracle/upgrade/log/upgrade_database_<timestamp>.logfor details.

ERROR: Invalid objects found after DB upgrade:

Object name: <object>

...

The cause of these invalid objects should be investigated beforecontinuing the upgrade.

See/appl/virtuo/admin/oracle/upgrade/log/upgrade_database_<timestamp>.logfor details.

Do you want to continue the upgrade? (Enter "Yes" to continue): Yes

You must determine the cause of the errors before you continue the upgrade.v If the database errors are satisfactorily investigated and you want to

continue,Enter Yes.

v If the database issues are not satisfactorily investigated and you want to exitthe upgrade,Enter No to exit the upgrade.To resume the upgrade, run the pmw_install command again as described in“Upgrading a distributed system” on page 54. You receive the prompt:

Would you like to perform task DB_UPGRADE? [yes/no]:

Enter yes at the prompt.


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/11.2.0/db_2]:(Enter . if unknown)

Accept the default or /appl/oracle/product/11.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)

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

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 63.

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.


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 2016 IBM Ireland PDL, All Rights Reserved

This installation script will install the Performance Managementfor Wirelesscommon software version TNPM1.4.2 on your system.

Do you wish to continue?

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? Yes



Select 4.6. The installation asks whether you want to deploy packages:


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 TCP


port 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.



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


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 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/11.2.0/db_2]:(Enter . if unknown)

Accept the default or /appl/oracle/product/11.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]:



Manager log directory:Please enter the PMW Log Directory[/appl/virtuo/logs]:


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]:



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


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:$WMCROOT/admin/logs/pmw_install.log

Upgrading the application serverUpgrade the application server as described in the following procedure.


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.2.0.tar.gzExtracting and running bootstrap packageLooking for bootstrap scriptRunning vallent-vt-common.installCopyright 2016 IBM Corporation, All Rights Reserved


This installation script will install the Tivoli Netcool Performance Manager commonsoftware version TNPM1.4.2.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




6. Select 2 for Application Server Components only.7. You are asked if you want to deploy packages:


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


upgrade:


copy-libs:[copy] Copying 2 files to /appl/virtuo/as/server/default/lib[copy] Copying 10 files to /appl/virtuo/lib/tp


fix-alarm-war:[mkdir] Created dir: /appl/virtuo/temp[mkdir] Created dir: /appl/virtuo/temp/war/apps/lib[unjar] Expanding: /appl/virtuo/as/server/default/deploy_core/

S02-na-alarm-manager.ear into /appl/virtuo/temp[unjar] Expanding: /appl/virtuo/lib/na-alarm-service-server.jar

into /appl/virtuo/temp


signjarpmw:[echo] Signing JBoss client jar[exec][exec] Warning:[exec] The signer certificate 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




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


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)

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 theprevious 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


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.2 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.2.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.2.0 on your system.

Do you wish to continue?

2. Enter yes to continue.3. When prompted, enter yes to accept the license terms.

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


The menu is displayed.What Type of System Are you Installing?

1. Standalone server


2. 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.2.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.2.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

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.



Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no]>yesConfiguring core cronjobs.......


What Type of PMW System Are you Installing ?-----------------------------------------------------------------------Please select the type of PMW System you are installing byentering the number associate with the system type :All Inclusive (1)Application (2)Loader (3)Directory Server (4)Database (5)Gateway (6)-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 / 6 ] :3

Enter 3 for Loader.3. You are prompted to enter the location of the Tivoli Netcool Performance

Manager log directory:Server type selected: LDRPlease enter the PMW Log Directory[/appl/virtuo/logs]:(Enter . if unknown)


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 3. Upgrading the Security Directory Server and IBMDB2

Tivoli Netcool Performance Manager, 1.4.2 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.


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.

3. Optional:

Note: Manually, create a link to the ldap folder if you see a failure message tocreate a symbolic link during upgrade.Create a link to the ldap folder, by following these steps:a. Create a folder ldap in /opt/IBM folder.b. Create a link to the /opt/IBM/ldap by using the following command:

ln /opt/IBM/ldap/V6.4 V6.4

c. Run the upgrade script again.

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.2 before theSecurity Directory Server upgrade.

Procedure1. Stop the tdsna.

Run the following command:

/etc/rc.d/init.d/tdsna stop

Run the following command:


https://www.ibm.com/support/knowledgecenter/SSBNJ7_1.3.2/com.ibm.tnpm.doc/upgrade/t_tnpm_post_%20remove_pre_tbs%20_db2ver.html

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:/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:

Chapter 3. Upgrading the Security Directory Server and IBM DB2 75

/var/install/sbin/sds_install -base /appl -product virtuo -version 6.4 -upgrade

# /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

6.

Note: Manually, create a link to the ldap folder if you see a failure message tocreate a symbolic link during upgrade.Create a link to the ldap folder, by following these steps:a. Create a folder ldap in /opt/IBM folder.b. Create a link to the /opt/IBM/ldap by using the following command:

ln /opt/IBM/ldap/V6.4 V6.4

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/tdsdb2V*

v /opt/ibm/tdsdb2V*

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.

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.2 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 77

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.2Enter 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.2 completed

Note: <package_location> is the directory where the Tivoli Netcool PerformanceManager 1.4.2 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.


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=True

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

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.logImpact: 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: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 4. Post-upgrade tasks 81

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, 2010asd STARTED Oct 08, 2010nc_cache STARTED Oct 08, 2010alarm_cache STARTED Oct 08, 2010load_erics_r10 STARTED Oct 08, 2010load_nok_oss31ed3 STARTED Oct 08, 2010load_motor_gsr7 STARTED Oct 08, 2010load_erics_r30 STARTED Oct 08, 2010

Separate services are installed for each instance of Tivoli Common Reporting youinstalled on each server. Use the trcmd -checkstatus command to check the statusof a specific Tivoli Common Reporting component.Related information:

Tivoli Common Reporting commands

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.


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/tcr_original/ctcr_cli.html

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

What to do next

Disable the firewall. To check if the firewall is disabled, follow these steps:

For RHEL 6.x# service iptables status

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.2.

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: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 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.1 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.


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.1 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


Procedure1. Run the following command as user virtuo:

sap stop -f


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



v svcadm disable sapmgr-na

v service sapmgrvirtuo stop

v /etc/rc.d/init.d/sapmgrvirtuo stop


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:


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 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.0.0Removing existing /appl/virtuo......doneRestoring TNPM1.4.0.0 to /appl/virtuo......doneStarting Sds......doneRestoring package files from /appl/archive/software.TNPM1.4.0.0......doneRestoring user cron jobs......doneRestarting Cron ...Stopping crond: [ OK ].... cron daemon stoppedStarting crond: [ OK ].... cron daemon startedRestoring user profiles......doneRestoring release TNPM1.4.0.0 complete

Chapter 6. Rolling back to the previous Tivoli Netcool Performance Manager version 91

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:


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


/etc/rc.d/init.d/dboravirtuo status/etc/rc.d/init.d/sdsna status/etc/rc.d/init.d/sapmonvirtuo status/etc/rc.d/init.d/sapmgrvirtuo status/etc/rc.d/init.d/sapvirtuo status

Sample output:

# /etc/rc.d/init.d/dboravirtuo statusDatabase listener is running.Database instance vtdb is running.

# /etc/rc.d/init.d/sdsna statusSDS LDAP server is runningSDS admin server is running

# /etc/rc.d/init.d/sapmonvirtuo statussapmon process running

# /etc/rc.d/init.d/sapmgrvirtuo statussapmgr process running

# /etc/rc.d/init.d/sapvirtuo status

............

............

NAME STATE SINCEas STARTED Oct 08, 2010asd STARTED Oct 08, 2010nc_cache STARTED Oct 08, 2010alarm_cache STARTED Oct 08, 2010load_erics_r10 STARTED Oct 08, 2010load_nok_oss31ed3 STARTED Oct 08, 2010load_motor_gsr7 STARTED Oct 08, 2010load_erics_r30 STARTED Oct 08, 2010

Tivoli Netcool Performance Manager core processes checkCheck the status of the Tivoli Netcool Performance Manager core processes.

About this task


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.


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 11.2.0.2 home directory.

2. Ensure the environment variables for each user on each server in the systemare changed to use Oracle 11.2.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 11.To edit the crontab directly, modify the following files:

Procedure1. Edit the following files:




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

vservice crond restart


Appendix. Dependency Checker errors

Dependency Checker errors.

ErrorsGYMWI0001E Directories missing from root user PATHThe following directories are missing from the root user PATH: <missing_dirs>You must ensure that the root user profile is sourced beforerunning the installation.Hint: If you use ’su’ to change to the root user, use the ’-’argument to source the profile, i.e. ’su -’-------------------------------------------------------------GYMWI0002E No domain name configuredYou must set up a domain name on the server and ensure the fully qualified hostname is valid-------------------------------------------------------------GYMWI0003E Hostname <FQDN> resolves to loopbackIP address x.x.x.x - must be a real IP addressThe server hostname must resolve to a non-loopback IP address.Otherwise the alarms UI will not function correctly.-------------------------------------------------------------GYMWI0004E Hosts entry for <FQDN> not found-------------------------------------------------------------GYMWI0054E Invalid umask for root user:022 The umask for the root user must be set to 0022-------------------------------------------------------------GYMWI0005E OS <OS> is not supported. Must be one of: Linux SunOS AIXOnly Linux, AIX and SunOS (Solaris) are supported-------------------------------------------------------------GYMWI0006E SunOS version <OS_VER> is not supported. Must be 5.10Solaris 10 is the only supported version-------------------------------------------------------------GYMWI0007E Processor type <PROC_TYPE> is not supported for <OS>Solaris is only supported on SPARC processors-------------------------------------------------------------GYMWI0008E Platform must support 64-bit kernel-------------------------------------------------------------GYMWI0009E Unable to determine update level for SunOS-------------------------------------------------------------GYMWI0011E Update level for SunOS is &ltSOLARIS_UPDATE>:required level is &ltREQUIRED_UPDATE>You must install the latest recommended update-------------------------------------------------------------GYMWI0012E Processor type <PROC_TYPE> is not supported for LinuxLinux is only supported on x86_64 architecture-------------------------------------------------------------GYMWI0013E Linux distribution must be Red Hat-------------------------------------------------------------GYMWI0014E Linux distribution must be Red Hat Enterprise Linux Server-------------------------------------------------------------GYMWI0015E Red Hat Release <RHEL_VERSION> is not supported:must be 5.9 or later-------------------------------------------------------------GYMWI0016E &ltdir>is not a directory-------------------------------------------------------------GYMWI0017E Insufficient space on <fs> partition.Space required on this partition:KB Space available: KBThe following required directories are mounted on this partition:-------------------------------------------------------------GYMWI0018E One or more required <OS> packages not installedMissing packages:-------------------------------------------------------------GYMWI0019E ERROR: invalid argument to linux_pkg_checks():-------------------------------------------------------------GYMWI0049E ERROR: invalid format for package info: <pkg>


-------------------------------------------------------------GYMWI0050E ERROR: incomplete package information: <pkg>-------------------------------------------------------------GYMWI0051E ERROR: invalid package version for <pkg>: <ver>-------------------------------------------------------------GYMWI0052E ERROR: invalid package release for <pkg>: <rel>-------------------------------------------------------------GYMWI0020E <tpp_type> <OS> packages are missing-------------------------------------------------------------GYMWI0021E <tpp_type> <OS> packages require upgrade-------------------------------------------------------------GYMWI0022E User oracle shell <ORACLE_USER_SHELL> is not supported:must be /bin/ksh-------------------------------------------------------------GYMWI0055E Invalid oracle user umask: <ORACLE_USER_UMASK>The oracle user umask must be set to 022-------------------------------------------------------------GYMWI0023E ORACLE_BASE environment variable not set-------------------------------------------------------------GYMWI0024E ORACLE_BASE directory /appl/oracle does not exist-------------------------------------------------------------GYMWI0025E ORACLE_OWNER: <ORACLE_OWNER> is expected to be oracle-------------------------------------------------------------GYMWI0026E ORACLE_HOME environment variable not set-------------------------------------------------------------GYMWI0027E ORACLE_HOME directory <ORACLE_HOME> does not exist-------------------------------------------------------------GYMWI0028E PATH for oracle does not contain <ORACLE_HOME>/bin-------------------------------------------------------------GYMWI0029E LD_LIBRARY_PATH for oracle does not contain <ORACLE_HOME>/lib-------------------------------------------------------------GYMWI0030E NLS_LANG environment variable for oracle user must be set to<VALID_NLS_LANG>-------------------------------------------------------------GYMWI0031E Installed Oracle version is invalidInstalled Oracle version is <installed_ver>- required version is<required_ver>-------------------------------------------------------------GYMWI0032E Oracle oneoff patches not installedThe following oneoff Oracle patches are missing:-------------------------------------------------------------GYMWI0033E Oracle Partitioning is not installed-------------------------------------------------------------GYMWI0034E <dir> does not exist-------------------------------------------------------------GYMWI0035E <dir> must be owned by oracle-------------------------------------------------------------GYMWI0036E <dir> must be executable by owner oracle-------------------------------------------------------------GYMWI0037E <dir> must be executable for non-oracle users-------------------------------------------------------------GYMWI0038E <binary> does not exist-------------------------------------------------------------GYMWI0039E <binary> must be owned by oracle-------------------------------------------------------------GYMWI0040E <binary> must be executable by owner oracle-------------------------------------------------------------GYMWI0041E <binary> must be executable for non-oracle users-------------------------------------------------------------GYMWI0042E <ORACLE_HOME>/network/admin/<ora_file> must be owned by oracle-------------------------------------------------------------GYMWI0043E <ora_file> must be writable by owner oracle-------------------------------------------------------------GYMWI0044E <ora_file> must be readable for non-oracle users-------------------------------------------------------------GYMWI0045E <ORACLE_HOME>/network/admin/<ora_file> must be an empty fileDB creation may fail if this file has invalid contents.-------------------------------------------------------------GYMWI0046E <pkg_count> versions of <core_pkg> foundThere can only be 1 version of each package in <pkg_dir>-------------------------------------------------------------


GYMWI0047E TNPM core packages not foundThe following core packages could not be found: <missing_pkgs>-------------------------------------------------------------GYMWI0053E JBoss archive not foundThe JBoss 4.0.3 SP1 package should be located in <BASE_DIR>-------------------------------------------------------------GYMWI0046E <pkg_count> versions foundThere can only be 1 version of each package in <pkg_dir>-------------------------------------------------------------GYMWI0048E SDS/DB2 packages not foundThe following SDS/DB2 packages could not be found:-------------------------------------------------------------GYMWI0056E AIX version <version> is not supported.Must be 5.3 or greater-------------------------------------------------------------GYMWI0057E Processor type <PROC_TYPE> is not supported for AIXAIX is only supported on powerpc processors-------------------------------------------------------------GYMWI0059E Platform must support 64-bit hardware-------------------------------------------------------------GYMWI0060E Maintenance level for AIX is <OS_LEVEL>:Minimum required level is 5300-09-------------------------------------------------------------GYMWI0061E <req_fs>is required for SDS. Please install it.-------------------------------------------------------------GYMWI0063E <req_fs>is required for Oracle. Please install it.-------------------------------------------------------------GYMWI0064E Physical RAM is <P_RAM>KB which is under the minimum requirement of262144 KB (256 MB)-------------------------------------------------------------GYMWI0065E Swap space does not meet requirements.Should be twice the size of RAM or 1 GB (2097152 KB), whichever is smaller-------------------------------------------------------------GYMWI0066E Free disk space in /tmp directory is <tmpSpace>which is less than the minimum requirement of 400 MB.-------------------------------------------------------------GYMWI0067E oracle is not in <DBA_GROUP>group-------------------------------------------------------------GYMWI0068E SDS/DB2 fixpack not installedThe following db2fixpack is not installed: <SDS_FP_PREFIX>_fixpack.tar.gz }-------------------------------------------------------------GYMWI0069E Missing Jazz SM & TCR InstallationYou must install Jazz SM along with TCR before installing TNPM Wireless Component.-------------------------------------------------------------GYMWI0070E Required file missing. The following files are missing from the root user: <missing_dirs>You must ensure that the required file exist at the specified path.If the file exists in another path, you may add a softlink-------------------------------------------------------------

Warnings-------------------------------------------------------------WARNING: 1GYMWI0001W Default Jazz SM Port <port> is already in useYou must check the port configuration if you are installing Jazz SM on this Server.-------------------------------------------------------------

Additional note when you run the dependency_checker with -t app option forApplication Server:------------------------------------------------------------------------------------Note: Please make sure to install Jazz SM & TCR before installing Application server"when you plan to install Jazz SM, TCR and SDS on the same server.------------------------------------------------------------------------------------

Appendix. Dependency Checker errors 99

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


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:


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 103

http://www.ibm.com/legal/us/en/copytrade.shtml

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.


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 105

IBM®

Printed in USA

with ibm corp. · performing a cold backup of the oracle 1 1g database ..... . 18 changing...

Documents