Tivoli Netcool Performance Manager: Installation Guide ... · PDF fileNetcool Performance Manager 1.3.1 Document Revision R2E1 Tivoli Netcool Performance Manager: Installation Guide

Netcool Performance Manager 1.3.1 Document Revision R2E1

Tivoli Netcool Performance Manager: Installation Guide - Wireless Component

Note: Before using this information and the product it supports, read the information in Notices on page 107.

This edition applies to version 1, release 2, modification 1 of IBM Tivoli Netcool Performance Manager and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corp. 2007, 2011 US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents About This Guide .................................................................................................................................................................................. 1

Viewing the Online help............................................................................................................................................................... 2 Chapter 1. Installing Tivoli Netcool Performance Manager .................................................................................................... 3

1.1 Installation Process ................................................................................................................................................................ 3 1.1.1 Pre-installation Road Map ........................................................................................................................................ 3 1.1.2 Installation Road Map ............................................................................................................................................... 4

1.2 Planning your Installation .................................................................................................................................................... 5 1.2.1 Components of Tivoli Netcool Performance Manager.......................................................................................... 5

Chapter 2. Preparing for the Installation ..................................................................................................................................... 6 2.1 Server Hardware and Software Requirements .................................................................................................................. 6

2.1.1 Server Hardware Requirements............................................................................................................................... 6 2.1.2 Server Software Requirements ................................................................................................................................. 7

2.2 Client PC Hardware and Software Requirements........................................................................................................... 11 2.2.1 Client Hardware Requirements.............................................................................................................................. 11 2.2.2 Client Software Requirements ................................................................................................................................ 11

Chapter 3. Pre-installation Tasks................................................................................................................................................. 12 3.1 Prerequisites.......................................................................................................................................................................... 12

3.1.1 Required Server Information .................................................................................................................................. 12 3.1.2 Run the Dependency Checker ................................................................................................................................ 12

3.2 Required Filesystems........................................................................................................................................................... 15 3.3 Configuring Ports and Firewalls........................................................................................................................................ 16

3.3.1 Distributed Installations with Application, Loader or Directory Servers on RHEL ....................................... 17 3.4 Installing the Platform Package.......................................................................................................................................... 19 3.5 Creating User and Group Accounts .................................................................................................................................. 20 3.6 Setting Directory Ownership.............................................................................................................................................. 20 3.7 Configuring the Kernel........................................................................................................................................................ 21 3.8 Setting Up the Domain Name ............................................................................................................................................ 21 3.9 Setting Up the Hostname .................................................................................................................................................... 22 3.10 Building Perl on Gateway Servers ..................................................................................................................................... 23 3.11 Setting memory for Java client processes ......................................................................................................................... 24

Chapter 4. Installing Oracle RDBMS and the Oracle Client.................................................................................................. 25 4.1 Configuring Oracle Environment Variables..................................................................................................................... 25 4.2 Before installing Oracle 10g ................................................................................................................................................ 26

4.2.1 Organizing Oracle one-off patches ........................................................................................................................ 26 4.2.2 Installing Oracle RDBMS (Standalone System or Database Server).................................................................. 26 4.2.3 Installing Oracle 10g Client (Application Server in Distributed Systems only) .............................................. 28

Chapter 5. Installing the IBM Tivoli Directory Server and IBM DB2.................................................................................. 31 5.1 Copying the Required Packages ........................................................................................................................................ 31 5.2 Running the Installation Scripts......................................................................................................................................... 31 5.3 Installing the IBM Tivoli Directory Server Client ............................................................................................................ 33

Chapter 6. Installing the Tivoli Netcool Performance Manager Software .......................................................................... 34 6.1 Prerequisites.......................................................................................................................................................................... 34 6.2 Unattended Installation of a Standalone System............................................................................................................. 35 6.3 Installing a Standalone System........................................................................................................................................... 36

6.3.1 Running an Interactive Installation ....................................................................................................................... 36 6.3.2 Installing the JBoss Application Server ................................................................................................................. 37 6.3.3 Installing the Directory Server schema.................................................................................................................. 38 6.3.4 Installing the Database ............................................................................................................................................ 38 6.3.5 Installing the Database Schema.............................................................................................................................. 39 6.3.6 Database Schema Post-Installation Tasks ............................................................................................................. 39

© Copyright IBM Corp. 2007, 2011 iii

6.3.7 Installing the Cronjobs............................................................................................................................................. 40 6.3.8 Installing the Gateways ........................................................................................................................................... 41 6.3.9 Installing the Technology Packs............................................................................................................................. 41 6.3.10 Encrypting Passwords ............................................................................................................................................. 43

6.4 Installing a Distributed System .......................................................................................................................................... 44 6.4.1 Running an Interactive Installation ....................................................................................................................... 44 6.4.2 Installing a Database Server.................................................................................................................................... 44 6.4.3 Installing a Separate Directory Server ................................................................................................................... 48 6.4.4 Installing the Application Server............................................................................................................................ 50 6.4.5 Installing a Loader Server ....................................................................................................................................... 57 6.4.6 Installing the Gateways Separately........................................................................................................................ 59

Chapter 7. Installing the Technology Packs Separately.......................................................................................................... 61 7.1 Starting the System .............................................................................................................................................................. 61 7.2 Setting up Users and Data Sources.................................................................................................................................... 61 7.3 Checking Database Space.................................................................................................................................................... 62 7.4 Installing the Technology Pack Step 1............................................................................................................................... 62 7.5 Installing the Technology Pack Step 2............................................................................................................................... 63 7.6 Performing Post-Installation Checks for the Technology Packs.................................................................................... 63 7.7 Starting the SAP Process Monitor Tool ............................................................................................................................. 65 7.8 Starting the Application Server.......................................................................................................................................... 66 7.9 Starting the Loaders............................................................................................................................................................. 66 7.10 Configuring Multiple Identical Loaders ........................................................................................................................... 67 7.11 Loading Data ........................................................................................................................................................................ 68

7.11.1 Verifying Data Loading........................................................................................................................................... 68 7.12 Removal of Loadmaps and Loader Configuration.......................................................................................................... 69 7.13 Creating a Loader on a Distributed Server....................................................................................................................... 69

Chapter 8. Post-Installation Tasks............................................................................................................................................... 72 8.1 Provisioning Stored Busy Hours, Summaries and Data Availability ........................................................................... 72

8.1.1 Stored Busy Hours Definitions............................................................................................................................... 72 8.1.2 Summary Definitions............................................................................................................................................... 73 8.1.3 Data Availability Definitions .................................................................................................................................. 73

8.2 Configuring Application Server Memory (Optional) ..................................................................................................... 74 8.2.1 The jvm.args Property ............................................................................................................................................. 74 8.2.2 Recommended jvm.args Property Settings for Application Servers................................................................. 75

8.3 Configuring Loader Server Memory (Recommended)................................................................................................... 75 8.3.1 The SAP Configuration params Property ............................................................................................................. 75 8.3.2 Recommended JVM Memory Size Settings for Loader Servers......................................................................... 76

8.4 Checking the Time Zone Settings for the Report Scheduler .......................................................................................... 77 8.4.1 Setting the Time Zone.............................................................................................................................................. 77

8.5 Changing the Default Client Ports..................................................................................................................................... 77 8.6 Configuring a Multi-homed application server............................................................................................................... 77 8.7 Integrating IBM Tivoli Monitoring.................................................................................................................................... 78 8.8 Integrating Tivoli Common Reporting ............................................................................................................................. 79

8.8.1 Prerequisites.............................................................................................................................................................. 79 8.8.2 Tivoli Common Reporting ...................................................................................................................................... 79 8.8.3 Oracle client............................................................................................................................................................... 79 8.8.4 LDAP configuration................................................................................................................................................. 80

Chapter 9. Starting Tivoli Netcool Performance Manager...................................................................................................... 84 9.1 Reboot the Server ................................................................................................................................................................. 84 9.2 Process Checks...................................................................................................................................................................... 84 9.3 Complete Startup of Netcool Performance Manager ...................................................................................................... 87

Appendix A: Installation Output ..................................................................................................................................................... 88 Appendix B: Log file errors............................................................................................................................................................. 103 Appendix C: Dependency Checker errors.................................................................................................................................... 104

iv IBM Tivoli Netcool Performance Manager: Installation Guide – Wireless Component

About This Guide

Introduction

The Installation Guide tells you how to install and configure IBM® Tivoli® Netcool® Performance Manager.

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

Important: Before installing Tivoli Netcool Performance Manager, you are strongly advised to read the Tivoli Netcool Performance Manager - Wireless Component: Release Notes. Release notes can contain information specific to your installation that is not contained in this guide. Failure to consult the release notes might result in a corrupted, incomplete or failed installation. You are also advised to refer to the following link for all current known issues: Known Issues with Tivoli Netcool Performance Manager

Audience

The audience for this information is anyone who must install Tivoli Netcool Performance Manager. Typically, the audience consists of experienced system administrators, database administrators, installers, or supervisors.

Required Skills and Knowledge

To install Tivoli Netcool Performance Manager, you should be familiar with the following technologies:

• Sun Microsystems hardware • x86-64 hardware • Sun Microsystems Solaris operating system • Red Hat Enterprise Linux® operating system • Oracle database software • Microsoft® Windows® operating systems

© Copyright IBM Corp. 2007, 2011 1

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

User Publications

Tivoli Netcool Performance Manager software provides the following user publications:

• release notes • user guides • online help

The documentation is available for viewing and downloading on the infocenter at:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/ welcome_tnpm.html

Viewing the Online help

You can view Online Help for the Tivoli Netcool Performance Manager Web client. Using the Tivoli Netcool Performance Manager user interface, you can select HELP tabs or the HELP links for context-sensitive Help.

2 IBM Tivoli Netcool Performance Manager: Installation Guide – Wireless Component

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/%20welcome_tnpm.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/%20welcome_tnpm.html

Chapter 1. Installing Tivoli Netcool Performance Manager

1.1 Installation Process

The pre-installation and installation road maps describe how install Tivoli Netcool Performance Manager. Before installation, ensure that you have all the hardware you need, and have the appropriate software ready to install.

1.1.1 Pre-installation Road Map

Before installing Tivoli Netcool Performance Manager, complete the actions in the pre-installation road map shown in Figure 1.

Figure 1: Pre-installation Road Map


1.1.2 Installation Road Map

To install Netcool Performance Manager, complete the actions shown in the installation road map in Figure 2.

Figure 2: Installation Road Map


1.2 Planning your Installation

You must install Tivoli Netcool Performance Manager on a high-performance and scalable platform. Choose between the various installation options and ensure that you follow the instructions that apply to your installation.

1.2.1 Components of Tivoli Netcool Performance Manager

A typical Tivoli Netcool Performance Manager installation consists of the following components:

• Database component - Stores data in an Oracle database. • Application server component - Runs a core Framework. • Gateway component - Processes data downloaded from the adapter data sources. • Loader components - Parse and load data into a database.

A directory server provides directory services. Client software provides graphical user interface (GUI) access from client PCs.

1.2.1.1 Supported Configurations

Install Tivoli Netcool Performance Manager components in one of the two main configurations as follows:

• A Standalone system, where you install all components on a single standalone server. • A Distributed system, where you can install components over several servers in different

combinations.

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

Servers may also be defined using Solaris Containers. This is a virtualisation technology in Solaris 10 that provides isolated and secure runtime environments for applications. It makes use of zones, which are separate environments that can be viewed as individual OS instances running on the same server. A container can be defined as a zone with resources (CPU, memory) allocated using the resource management features available in Solaris 10. A distributed system can consist of components installed on separate zones that can span one or more Solaris 10 servers.

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

In this guide a server refers to the individual OS instance on which the Tivoli Netcool Performance Manager - Wireless component software is installed. This can be a non-global Solaris 10 zone or a RHEL instance running on VMWare ESX. If the servers are defined as non-global Solaris 10 zones, all installation tasks should be performed on these zones rather than on the global zone, unless otherwise specified.

IBM Tivoli Netcool Performance Manager: Installation Guide – Wireless Component 5

Chapter 2. Preparing for the Installation

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

2.1 Server Hardware and Software Requirements

Ensure that you have the necessary server hardware and software requirements.

2.1.1 Server Hardware Requirements

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

• 2 x UltraSPARC IV, IV+ or UltraSPARC T2+/T2/T1 Processors (for Solaris) • 2 x x86-64 dual-core processors (for Linux) • 16 GB core memory • 4 x 72 GB and 6 x 146 GB hard disks • Optical drive (DVD ROM/R/RW)


2.1.2 Server Software Requirements

To install a Tivoli Netcool Performance Manager system, you need the appropriate number of Linux or UNIX® servers, plus additional IBM and third-party software for each server. Depending on the server type, you need some or all of the following additional software.

2.1.2.1 Prerequisite Software

Table 1 lists the prerequisite software for installing Tivoli Netcool Performance Manager.

Table 1: Prerequisite Server Software

Product Version

Operating System

Solaris SPARC or Red Hat Enterprise Linux (RHEL)

Solaris 10 (HW 8/07 or later with latest Recommended Patch Cluster)

RHEL 5.1, or 5.5

Oracle Enterprise Edition

Oracle Client

Oracle Instant Client

Oracle Instant Client SQL*Plus Extension package

10.2.0.4

Tivoli Netcool Performance Manager supports: Oracle 10.2.0.1 with the 10.2.0.4 patchset applied - after the patchset is applied the Oracle version becomes 10.2.0.4.

In addition, the following Oracle patches are required: 7306915 and 8350262.

JBoss Application Server 4.0.3 Service Pack 1

Perl 5.6.1 for Solaris or RHEL

2.1.2.2 Bundled Software

Table 3 lists the software bundled with Tivoli Netcool Performance Manager.

Table 2: Bundled Server Software

Product Version

IBM Tivoli Directory Server (required)

6.2 with fix pack 1 IF 4 (version 6.2.0.7)

IBM DB2 (required) 9.5 with fix pack 3 (version 9.5.0.3)

IBM Tivoli Monitoring (optional) 6.2.1


2.1.2.3 Locating the Tivoli Netcool Performance Manager Software

Note the location of the Tivoli Netcool Performance Manager software before you start the installation.

In addition to the Tivoli Netcool Performance Manager software, the following IBM products are included: IBM Tivoli Directory Server, IBM DB2, and IBM Tivoli Monitoring.

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

The following is a list of the core package files:

• vallent-vt-ant-<version>.tar.gz • vallent-vt-as-core-<version>.tar.gz • vallent-vt-common-<version>.tar.gz • vallent-vt-core-<version>.tar.gz • vallent-vt-db-conf-<version>.tar.gz • vallent-vt-db-install-<version>.tar.gz • vallent-vt-ds-conf-<version>.tar.gz • vallent-vt-java-libs-<version>.tar.gz • vallent-vt-jre-<version>.tar.gz • vallent-vt-njloader-<version>.tar.gz • vallent-vt-sap-<version>.tar.gz • pmw_install • default.rsp • dependency_checker

2.1.2.4 Locating the Sun Solaris Software

Note the location of the Solaris software before starting the installation.

For each server that runs on Sun Solaris, a full installation (all components) of Solaris 10 should be available on the server.

2.1.2.5 Locating the Red Hat Enterprise Linux Software

Note the location of the Red Hat Enterprise Linux (RHEL) software before starting the installation.

For each server that runs on Red Hat Enterprise Linux (RHEL), you need a basic RHEL installation. In addition, depending on the server type, install the additional RHEL packages specified below.

To check if a package is installed, run the following command:

rpm -qa | grep <package_name>


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

The dependency_checker tool will also report any missing packages. Refer to Run the Dependency Checker for details of the tool.

Any additional required packages should be located in the Server directory of the RHEL installation media.

If any packages are missing, install them by executing the following command as user root:

rpm -i <RPM package file>

All the additional packages listed in the following sections are x86_64 versions unless otherwise stated. You need to have all the packages installed, regardless of whether they are 32 bit or 64 bit. For example, the libXp package has two packages listed, the i386 and the x86_64 version. You need to install both of these. The architecture is displayed in bold for each package below.

Additional RHEL packages required for installing Oracle 10g

Before you install Oracle 10g on a RHEL server, install each of the following packages (specified versions or higher) on the server:

binutils-2.17.50.0.6-2.el5 x86_64 compat-db-4.1.25-9 x86_64 compat-libstdc++-33-3.2.3-61 x86_64 compat-libstdc++-33-3.2.3-61(i386) compat-libstdc++-296(i386) control-center-2.16.0-14.el5 x86_64 gcc-4.1.1-52.el5 x86_64 gcc-c++-4.1.1-52.el5 x86_64 glibc-2.5-12 x86_64 glibc-2.3.4-2 (i686) glibc-common-2.5-12 x86_64 glibc-devel-2.5-12 x86_64 glibc-devel-2.5-12(i386) glibc-headers-2.5-12 x86_64 libgcc-4.1.1-52.el5 x86_64 libgcc-4.1.1-52.el5(i386) libaio-0.3.96-3 x86_64 libgcc-4.1.1-52.el5(x86_64) libgcc-4.1.1-52.el5(i386) libstdc++-3.4.3-9.EL4 x86_64 libstdc++-devel-3.4.3-22.1 x86_64 libgomp-4.1.1-52.EL5 x86_64 libXp-1.0.0-8.el5 (i386) libXp-1.0.0-8.el5 (x86_64) make-3.81-1.1 x86_64 sysstat-7.0.0-3.el5 x86_64

Additional RHEL packages required for installing IBM TDS and IBM DB2

Before you install IBM Tivoli Directory Server and IBM DB2 on a RHEL server, install each of the following packages (specified versions or higher) on the server:

compat-libstdc++-296-2.96-138 i386 compat-libstdc++-33-3.2.3-61 x86_64 compat-libstdc++-33-3.2.3-61 i386 compat-gcc-34-3.4.6-4 x86_64 compat-gcc-34-c++-3.4.6-4 x86_64 compat-libf2c-34-3.4.6-4 x86_64 compat-libf2c-34-3.4.6-4 i386 kernel-headers-2.6.18-53.el5 x86_64 glibc-headers-2.5-18 x86_64


glibc-devel-2.5-18 x86_64 glibc-devel-2.5-18 i386 libgomp-4.1.2-14.el5 x86_64

Additional RHEL packages required for installing JBoss

Before you install JBoss on a RHEL server, install each of the following packages (specified versions or higher) on the server:

eclipse-ecj-3.2.1-18.el5 x86_64 zlib-devel-1.2.3-3 x86_64 libgcj-devel-4.1.2-14.el5 x86_64 gcc-java-4.1.2-14.el5 x86_64 java-1.4.2-gcj-compat-devel-1.4.2.0-40jpp.112 x86_64

2.1.2.6 Locating the Oracle RDBMS and Client Software

Note the location of the Oracle RDBMS and Client software before starting the installation.

2.1.2.7 Locating the JBoss Application Server Software

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

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

If necessary, download the JBoss Application Server software from the location below. The version required is 4.0.3 Service Pack 1. For example: jboss-4.0.3SP1.tar.gz. http://www.jboss.org/jbossas/downloads/.

2.1.2.8 Locating the Perl Software

Note the location of the Perl software before starting the installation.

If necessary, download the Perl 5.6.1 source code (perl-5.6.1.tar.gz) from http://www.perl.com/CPAN/src.


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

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

2.2 Client PC Hardware and Software Requirements

Ensure that you have the necessary client PC hardware and software requirements.

2.2.1 Client Hardware Requirements

The minimum hardware requirements for a Tivoli Netcool Performance Manager Client are:

• 1.4GHz Pentium® III (or above) processor • 1 GB memory

2.2.2 Client Software Requirements

Table 3 lists the software products you need on a client PC to access the Tivoli Netcool Performance Manager system. The required software must be installed on the client PC before starting the installation.

Table 3: Prerequisite Software for Client

Product Version

Operating system Windows® 2000 SP4, Windows 2003, Windows XP, Windows Vista, Windows 7

Web browser Microsoft Internet Explorer version 7 or 8 , or Mozilla Firefox version 3 or 3.5.

Java™ Runtime Environment (JRE) Sun JRE 1.6

Flash Player Adobe® Flash Player 10.0.22 or later

2.2.2.1 Downloading the Java Runtime Environment Software

Download the Java Runtime Environment from http://java.sun.com/javase/downloads/.


http://java.sun.com/javase/downloads/

Chapter 3. Pre-installation Tasks

You must prepare and configure each server individually.

3.1 Prerequisites

Before starting the installation, ensure that you have installed the appropriate operating system on each of the servers. Also, depending on the components that you want to install on a particular server, ensure that you install any additional operating system packages required.

3.1.1 Required Server Information

Before you start the installation, you will need the following information for each of the servers in your configuration.

• Server IP address • Server hostname • Server domain name • Router IP address

3.1.2 Run the Dependency Checker

The dependency_checker tool helps validate the configuration of the server before you begin the installation. It detects any problems with the platform configuration. The checks that it performs include:

• operating system type and version • existing filesystems and available disk space • installation of prerequisite packages • location of Tivoli Netcool Performance Manager packages • Oracle configuration, if Oracle is already installed

To run the dependency_checker:

1. Copy all of the Tivoli Netcool Performance Manager package files to a designated target directory on the server. The recommended location for the package files is /appl.

2. Run the following commands as user root:

cd <package location>

./dependency_checker [ -t app|db|ds|ldr ]


Use the -t option for a distributed server to specify the type of server you are checking:

-t app Application server

-t db Database server

-t ds Directory server

-t ldr Loader server

The script will perform a number of checks on the system. The following example output shows a successful check with no reported problems:

====================================================================== Tivoli Netcool Performance Manager pre-installation check ====================================================================== Checking PATH... /usr/sbin: OK /usr/bin: OK Performing checks for server type: all ------------------------------------------------------------- Perform Operating System configuration checks ------------------------------------------------------------- Hostname: server-zone2 Processor type sparc is supported. Platform supports 64-bit kernel. Operating system version Solaris 10 5/08 is at supported level. ------------------------------------------------------------- Perform Host Setup configuration checks ------------------------------------------------------------- Fully Qualified Domain name: server-zone2.com Checking IP address... OK Checking root user umask...OK Checking package SUNWarc...OK Checking package SUNWbtool...OK Checking package SUNWhea...OK Checking package SUNWlibm...OK Checking package SUNWlibms...OK Checking package SUNWsprot...OK Checking package SUNWtoo...OK Checking package SUNWi1of...OK Checking package SUNWi1cs...OK Checking package SUNWi15cs...OK Checking package SUNWxwfnt...OK Checking package SUNWsprot...OK ------------------------------------------------------------- Perform Filesystem configuration checks ------------------------------------------------------------- Checking space on / partition...OK Checking space on /appl partition...OK Checking space on /export/home partition...OK Checking space on /data/trace_log1 partition...OK Checking space on /data/trace_archive1 partition...OK Checking space on /opt partition...OK Checking space on /oradata01 partition...OK Checking space on /oradata02 partition...OK Checking space on /oradata03 partition...OK


Checking space on /oradata04 partition...OK Checking space on /oralogs1 partition...OK Checking space on /oralogs2 partition...OK Checking space on /oradump partition...OK ------------------------------------------------------------- Perform Oracle configuration checks ------------------------------------------------------------- Checking if Oracle User exists... no oracle user on this server. ------------------------------------------------------------- Perform TNPM core package checks ------------------------------------------------------------- Checking for core packages in /appl Checking for package jre... OK Checking for package ant... OK Checking for package java-libs... OK Checking for package as-core... OK Checking for package core... OK Checking for package sap... OK Checking for package njloader... OK Checking for package ds-conf... OK Checking for package db-install... OK Checking for package db-conf... OK Checking for pmw_install... OK Checking for Platform package... OK ------------------------------------------------------------- Checking for JBoss package ------------------------------------------------------------- ------------------------------------------------------------- Perform TDS / DB2 package checks ------------------------------------------------------------- Checking for TDS packages in /appl/depends/tds62 Checking for TDS package base... OK Checking for TDS package db2... OK Checking for TDS package gskit... OK

The script will report a FAIL message for any checks which return an invalid result. A summary of these errors will be displayed when the script completes. The following example output shows a number of fail messages:

------------------------------------------------------------- The following tests failed -- you must investigate and fix these failures before beginning the installation ------------------------------------------------------------- FAILURE: 1 GYMWI0054E Invalid umask for root user: 077 The umask for the root user must be set to 022 ------------------------------------------------------------- FAILURE: 2 GYMWI0017E Insufficient space on / partition. Space required on this partition: 14155776 KB Space available: 8391242 KB The following required directories are mounted on this partition: /var /oradata01 /oradata02 /oratemp ------------------------------------------------------------- FAILURE: 3


GYMWI0047E TNPM core packages not found The following core packages could not be found: jre ant java-libs as-core core sap njloader ds-conf db-install db-conf

A full list of error messages is given in 9.3Appendix C: Dependency Checker errors.

Note: A number of FAIL messages are expected when you first run the command. This is because the pre-installation tasks have not been completed yet. You should re-run the dependency_checker after the pre-installation tasks have been completed to verify that there are no remaining FAIL messages.

3.2 Required Filesystems

Ensure that you have set up the filesystems you need to install Tivoli Netcool Performance Manager.

Using Table 4 as a guide, create the required filesystems on each server. Ensure that the filesystem sizes meet your specific requirements; the minimum filesystem sizes in this table are only sufficient for a base application setup. Refer to the sizing document provided for your system for accurate sizings.

Note: In a default installation, the Oracle database is configured in NOARCHIVELOG mode and archived redo log files are not created. Online redo log files are placed in both the /oralogs1/vtdb and /oralogs2/vtdb directories. You must keep archived Oracle redo log files and online redo log files on separate devices/LUNs. If you want to use ARCHIVELOG mode, update the Oracle database configuration parameter log_archive_dest to point to a directory on a separate device/LUN than the online redo log files, such as the /oradump mount point.

Note: If installing the database server on a Solaris non-global zone, the zone should be configured with access to the raw disk devices in order to implement RAID 1+0 for the Oracle DB filesystems.

Table 4: Required Filesystems

Filesystem Description Minimum Size

Partition Type Server Type

/ Operating System 8 GB System disk partition or LVM device

All

swap Operating System 8 GB System disk partition or LVM device

All

/var Operating System 4 GB System disk partition or LVM device

All

/appl Oracle and Tivoli Netcool Performance Manager application software

24 GB Non-system disk partition or LVM device

All

/export/home Users Home Accounts 2 GB Non-system disk partition or LVM device

All

/oradata01 Oracle database files Storage Location 1


Database


Filesystem Description Minimum Partition Type Server Type Size



Database



Database



Database

/oralogs1 Oracle Redo Log location 1 8 GB Non-system disk partition or LVM device

Database

/oralogs2 Oracle Redo Log location 2 8 GB Non-system disk partition or LVM device

Database

/oratemp Oracle Temporary Tablespace storage location


Database

/oradump Oracle Dump Location for archive logs and for database backups


Database

/data/trace_log1 Trace Log Location for application logs


Application, Loader

/data/trace_archive1 Trace Archive Location for archived application logs


Application, Loader

Note: IBM recommends RAID 1+0 (implemented in hardware if possible) for the non-system filesystems.

3.3 Configuring Ports and Firewalls

Table 5 lists the ports used by a Tivoli Netcool Performance Manager system.

Table 5: Ports needed for Tivoli Netcool Performance Manager

Port Description

LDAPPORT=1389 LDAP authentication interface

ORACLEPORT=1521 Oracle database port

SAPMONPORT=9009 Port for Service Application Processor (SAP)

OMPORT=9008 Framework RMI communication

ASHTTPPORT=8080 Application server HTTP port

ASREDIRPORT=8443 Application server Redirect port

ASAJPPORT=8086 Apache Integration

ASWEBSRVPORT=8083 Application server Web port


Port Description

ASBRIDGEPORT=10091 Application server Bridge port

ASNSPORT=1099 JNDI Communications

ASJRMPINVOKPORT=4444 EJB Communications

ASPOOLINVOKPORT=4445 EJB Communications

ASRMIPORT=1098 EJB Communications

ASUIL2PORT=8093 JMS Communications

ASHSQLPORT=1701 Internal DB

ORBPORT=3528 CORBA Alarm notification

ORBSSLPORT=3529 Secure CORBA alarm notification

SMTP_PORT=25 Mail relay port

MSTRCACHE_RMI=9876 Java Remote Method Invocation port for Master Cache

ALRMCACHE_RMI=9877 Java Remote Method Invocation port for Alarm Cache

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

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

The ports identified by ASHTTPPORT, ASJRMPINVOKPORT and ORACLEPORT are required for communication between the client workstations and the server. Allow these ports through any firewalls present between the client and the servers.

3.3.1 Distributed Installations with Application, Loader or Directory Servers on RHEL

When deploying application, directory or loaders servers on RHEL as part of a distributed installation, configure the firewall on each RHEL server to allow communication to and from each of the other servers, regardless of the operating system. To allow this, configure the IPTables service on the RHEL system using the IP addresses of the other servers as follows:

1. Determine if the firewall is enabled:

# service iptables status

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

2. Allow a server through the RHEL firewall by editing the /etc/sysconfig/iptables file as user root and specifying the server IP address. For each server, place an entry similar to the following after the first -A RH-Firewall entry in the file:

A RH-Firewall-1-INPUT -p all -s <IP address> -j ACCEPT

This entry will allow access from the specified server through the firewall on all ports.


3. Ensure that you add the following ports to allow clients to access the application server and alarms component:

-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp -dport <ASHTTPPORT> -j ACCEPT

-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp -dport <ASJRMPINVOKPORT> -j ACCEPT

-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp -dport <ORACLEPORT> -j ACCEPT

Substitute the correct port numbers for <ASHTTPPORT>, <ASJRMPINVOKPORT> and <ORACLEPORT>.

Here is an example of how the /etc/sysconfig/iptables file should look afterwards:

*filter

:INPUT ACCEPT [0:0]

:FORWARD ACCEPT [0:0]

:OUTPUT ACCEPT [0:0]

:RH-Firewall-1-INPUT - [0:0]

-A INPUT -j RH-Firewall-1-INPUT

-A FORWARD -j RH-Firewall-1-INPUT

-A RH-Firewall-1-INPUT -i lo -j ACCEPT

-A RH-Firewall-1-INPUT -p all -s <IP address> -j ACCEPT

-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT

-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 8080 -j ACCEPT



-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited

COMMIT

4. Run the following command as user root:

# service iptables restart


3.4 Installing the Platform Package

Install the platform package provided with your software distribution. The Platform package provides some system administration functions and installation scripts to help you correctly install the Oracle database and the directory server.

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

The name of the package is ibm-tn-plat-install-PLAT<version>.tar.gz. Install this package on all Tivoli Netcool Performance Manager servers. The package consists of the following files:

• ibm-tn-plat-install.install • ibm-tn-plat-install.remove • ibm-tn-plat-install.sw • ibm-tn-plat-install.license

To install the platform package under /var/install, run the following commands as user root:

1. Unpack the package:

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

2. Run the installation script:

# ./ibm-tn-plat-install.install now


3.5 Creating User and Group Accounts

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

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

1. On the server on which you want to install the TDS software, run the following command as user root:

# /var/install/sbin/setup_users -product virtuo -tds

2. On all other servers, run the following command as user root:

# /var/install/sbin/setup_users -product virtuo

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

Important: You need the password for the idsinst user when installing IBM Tivoli Directory Server and IBM DB2 (see Chapter 5 Installing the IBM Tivoli Directory Server and IBM DB2).

3.6 Setting Directory Ownership

To set the owner of the Oracle database directories to oracle, run the following command as user root on the database server:

# chown oracle:dba /ora*


3.7 Configuring the Kernel

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

1. To configure the kernel, run the following command as user root on the database and application servers:

# /var/install/sbin/system_configure

On Solaris, the system_configure command must be run on the global zone and on any non-global zones.

2. Reboot the server by using the appropriate commands:

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

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

# shutdown -r now

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

3.8 Setting Up the Domain Name

You must set up each of the servers on a common domain, typically, a DNS domain.

To set up the servers on a common domain:


# grep domain /etc/resolv.conf

If a DNS domain is configured, you will see output like the following:

domain this.domain.com

If a DNS domain is not being used, set up the domain name by completing the following:

a. As user root on the servers, check to see if the domain name is set by executing the following command:

# domainname


If nothing is returned, the domain is not set.

b. To set the domain, run the following command:

# domainname <domain>

<domain> is the selected domain name for the system, for example, ibm.com.

2. On Solaris systems, edit the /etc/hosts file and change the <hostname>.domainname entry to the

local hostname appended with the domainname. The entry in /etc/hosts should be similar to the following:

<IP address> <hostname>.<domainname> <hostname> loghost

3. On systems with Linux application servers that are using DNS, edit the /etc/hosts file. If the

entry for localhost in /etc/hosts looks like the following;

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

then, change the localhost entry so that it looks like the following;

127.0.0.1 localhost.localdomain localhost

If the system is not using DNS, add the following line to /etc/hosts:

<IP address> <hostname>.<domainname> <hostname>

4. On Solaris systems, add the domain name to the /etc/defaultdomain file:

<domainname>

3.9 Setting Up the Hostname

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

As user root on each server, modify the /etc/hosts file and ensure the hostname and IP addresses of the application server, database server, and loader servers and, if separate, the directory server are present in the /etc/hosts file.


3.10 Building Perl on Gateway Servers

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

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

http://www-01.ibm.com/support/docview.wss?rs=0&q1=TNPMW+Gateways&q2=TNPMW+Gateways+Solaris&q3=TNPMW+Gateways&q4=Build+Instructions+TNPMW+Gateways&uid=swg27015401&loc=en_US&cs=utf-8&cc=us&lang=en

http://www-01.ibm.com/support/docview.wss?rs=0&dc=DA400&q1=Perl+Build+Instruction&uid=swg27015399&loc=en_US&cs=utf-8&cc=us&lang=en









3.11 Setting memory for Java client processes

If a Java client process requires an extensive use of memory and the default Java heap size is insufficient, then the process can fail with an OutOfMemoryError Java exception:

java.lang.OutOfMemoryError: Java heap space

This error can occur:

• when installing or upgrading large technology packs.

• when running the secondary key removal tool sbh_sk_remover to remove secondary key fields prior to the provisioning of SBH definitions.

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

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

See section 8.9 of the Tivoli Netcool Performance Manager: Administration Guide - Wireless Component, for information on increasing the memory available to Java client processes.


Chapter 4. Installing Oracle RDBMS and the Oracle Client

Install the Oracle 10g RDBMS software on a standalone system or on the database server in a distributed system. Do not install the Oracle 10g Client software on a standalone system. Install the Oracle 10g Client software on the application server in a distributed system only, to make SQL*Plus available to certain programs.

4.1 Configuring Oracle Environment Variables

If Oracle 10g is already installed on the standalone or database server, then you should ensure that the correct Oracle environment variables are set in the profile of the oracle user:

Note: You can only ensure the correct Oracle environment variables are set after you have created User and Group Accounts.

To set the correct Oracle environment variables, as user oracle edit the file ${HOME}/.profile to include the following variables:

ORACLE_OWNER=oracle

export ORACLE_OWNER

ORACLE_BASE=/appl/oracle

export ORACLE_BASE

ORACLE_HOME=/appl/oracle/product/10.2.0/db_1

export ORACLE_HOME

PATH=$PATH:$ORACLE_HOME/bin

export PATH

LD_LIBRARY_PATH=$ORACLE_HOME/lib

export LD_LIBRARY_PATH

NLS_LANG=_.WE8ISO8859P1

export NLS_LANG


4.2 Before installing Oracle 10g

Before installing the Oracle software, note the location of the following software:

• Oracle 10.2.0 software • Oracle 10.2.0.4 patchset • Oracle one-off patches • Oracle 10.2.0 client software, consisting of:

• Oracle 10.2.0 Client • Oracle Instant Client basic • Oracle Instant Client sqlplus

4.2.1 Organizing Oracle one-off patches

Oracle one-off patches are distributed as zip files. These zip files should be copied to, and unzipped in, a separate directory different from the 10.2.0.1 software and the 10.2.0.4 patchset. There are two one-off patches to install: patch numbers 7306915 and 8350262.

1. Create a directory for the one-off patches. For example, create a directory named:

/appl/oracle_software/patches/oneoff

2. Copy the one-off patch zip files into the directory you created.

3. Unzip all the one-off patches in to the directory you created.

4. Remove the zip files from the directory. Ensure that the directory contains only the one-off patch directories and no other files or directories.

The directory you created should contain two directories: 7306915 and 8350262. When the Oracle installation prompts for the location of the one-off patches, enter the directory path, for example:

/appl/oracle_software/patches/oneoff

Important! To install Oracle 10g on RHEL 5.x, make a copy of the /etc/redhat-release file and edit the file to change the release number to 4.x. Use the copy of the /etc/redhat-release file to reverse the change when the Oracle 10g installation is complete.

4.2.2 Installing Oracle RDBMS (Standalone System or Database Server)

Note: Ignore the message ksh: : not found.

The Oracle installation will take approximately 30 minutes depending on the specification of the server. Install Oracle 10g by using the scripts provided in the platform package as follows:

1. Run the following commands as user root on the server:

# /var/install/sbin/oracle10gR2_install

The installation conducts a number of checks:


Check Oracle User exists...

.... Done

Check oinstall group exists...

.... OK

Check dba group exists...

.... OK

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

Please select the Type of Install you wish to execute

by entering the number associated with the Install Type :

Full install (Oracle 10.2.0.1 + 10.2.0.x patch set) (1)

Oracle 10.2.0.1 Client only (2)

10.2.0.x patch set (3)

Oracle 10.2.0.x oneoff patches (4)

Oracle 10.2.0.1 Companion CD Products (5)

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

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

2. For a full installation, select option 1. 3. At the prompts, specify the location of the Oracle Software and where you want to install the

software. Enter the paths to the Oracle software distribution as requested. 4. Enter the destinations for the Oracle software. In most cases, the defaults are acceptable. When the

Oracle Software installation is finished, the installation continues on to run the Oracle root.sh script.

Note: If Oracle was previously installed on the server, you might have to respond to the onscreen questions. Default values are displayed and it is recommended that you overwrite the files if they already exist.

5. At the prompt, enter n to installing the Oracle Companion software.

Would you like to install the Oracle companion software? n

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

6. The Oracle installation proceeds to install the 10.2.0.4 patch set. At the prompt, enter the location of the Oracle patchset:

Note: It is recommended that you overwrite the files if they already exist.

Please enter the location of the Oracle 10.2.0.x patch set [/cdrom/cdrom0/

patches/patchset/Disk1]:

Checking Running Oracle Processes...

.... no running oracle processes

.... no running oracle listeners

done

....


Running post-patch install steps ....

... Running root.sh - Please Respond to the Onscreen Questions if required

Running Oracle10 root.sh script...

The following environment variables are set as:

ORACLE_OWNER= oracle

ORACLE_HOME= /appl/oracle/product/10.2.0/db_1

Enter the full pathname of the local bin directory: [/usr/local/bin]:

The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

Entries will be added to the /var/opt/oracle/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root.sh script.

Now product-specific root actions will be performed.

....done

7. At the prompt for the location of the Oracle one-off patches, enter the location of the one-off patches. This must be a directory location containing the unzipped patches. For example:

/cdrom/cdrom0/patches/oneoff

Please enter the location of the Oracle 10.2.0.x uncompressed one-off patches

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

---->

No one-off patches to be installed

Running changePerm.sh script to relax permissions on Oracle Home...

.... Done

Setting up oracle User Profile

.... Done

The Oracle Patch installation will take approximately 20 minutes. See the Oracle Installation log output in /var/install/logs/oracle10g_install_<PID>.log.

4.2.3 Installing Oracle 10g Client (Application Server in Distributed Systems only)

Only install the Oracle 10g client software on an application server in a distributed system.

Important: Do not install Oracle Client on a standalone system. It must only be installed on the application server in a distributed system.


The Oracle installation will take approximately 5 minutes depending on the specification of the server. Install the Oracle 10g Client on the application server by using the scripts provided in the platform package.

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

To install the Oracle 10g client:

1. Run the following commands as user root on the server:

# /var/install/sbin/oracle10gR2_install

The installation conducts a number of checks:

Check Oracle User exists...

.... Done

Check oinstall group exists...

.... OK

Check dba group exists...

.... OK

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

Please select the Type of Install you wish to execute

by entering the number associated with the Install Type :

Full install (Oracle 10.2.0.1 + 10.2.0.x patch set) (1)

Oracle 10.2.0.1 Client only (2)

10.2.0.x patch set (3)

Oracle 10.2.0.x oneoff patches (4)

Oracle 10.2.0.1 Companion CD Products (5)

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

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

2. To install the client, select option 2. 3. At the prompts, specify the location of the Oracle Software and the location where you want to

install the Oracle software. Enter the paths to the Oracle Client software distribution as requested. 4. Enter the destinations for the Oracle software. In most cases, the defaults are acceptable. 5. Enter the location of the Oracle Instant Client and the SQL*Plus extension .zip files. In most cases,

the defaults are acceptable.

When the Oracle Software installation is finished, the installation will continue on to run the Oracle root.sh script.

Note: If Oracle was previously installed on the server, you might have to respond to the onscreen questions. Default values are displayed and it is recommended that you overwrite the files if they already exist.

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


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

4.3 Check Oracle Configuration

Use the dependency checker tool to validate Oracle configuration.

1. Run the dependency checker to validate Oracle configuration, as user root:

cd <target_directory>

./dependency_checker -t db

The script will validate that Oracle is installed correctly. If any FAIL messages appear, investigate them and resolve the problems before continuing the installation.


Chapter 5. Installing the IBM Tivoli Directory Server and IBM DB2

Use the scripts provided in the platform package to install IBM Tivoli Directory Server and IBM DB2.

Note: Perform these procedures on a standalone, directory server, or application server.

5.1 Copying the Required Packages

Copy the following packages to the installation directory, typically /var/install/packages:

• IBM Tivoli Directory Server 6.2 Client-Server with entitlement Solaris (tds62-solaris-sparc-

base.tar) • IBM Tivoli Directory Server Fix Pack 1 Interim Fix 4 (6.2.0.1-TIV-ITDS-SolarisSparc-

IF0004.tar) • IBM Tivoli Directory Server 6.2 GSkit Solaris (tds62-solaris-sparc-gskit.tar) • IBM Tivoli Directory Server 6.2, DB2 v 9.5 Solaris (tds62-solaris-sparc-db2.tar) • DB2 9.5 Fix Pack 3 (v9.5fp3_sun64_server.tar.gz)

• IBM Tivoli Directory Server 6.2 Client-Server with entitlement Linux x86-64 (tds62-linux-

x86_64-base.tar) • IBM Tivoli Directory Server Fix Pack 1 Interim Fix 4 (6.2.0.1-TIV-ITDS-LinuxX64-IF0004.tar) • IBM Tivoli Directory Server 6.2 GSkit Linux x86-64 (tds62-linux-x86_64-gskit.tar) • IBM Tivoli Directory Server 6.2, DB2 v 9.5 Linux x86-64 (tds62-linux-x86_64-db2.tar) • DB2 9.5 Fix Pack 3 (v9.5fp3_linuxx64_server.tar.gz)

The packages are distributed on the Tivoli Netcool Performance Manager installation media in the folder depends/tds62.

5.2 Running the Installation Scripts

Install IBM Tivoli Directory Server and IBM DB2 by using the scripts provided in the platform package as follows:


# /var/install/sbin/tds_install -base <target directory> -product virtuo \ –version 6.2


It is recommended to use the /appl directory as the <target directory> value.

2. Provide the required information at the prompts, including the requests for the absolute pathnames of the TDS, DB2 and GSK packages:

Enter the full pathname of the DS package: /var/install/packages/tds62-<OS>-<arch>-base.tar

Enter the full pathname of the DS DB2 package: /var/install/packages/tds62-<OS>-<arch>-db2.tar

Enter the full pathname of the GSK package: /var/install/packages/tds62-<OS>-<arch>-gskit.tar

Enter the full pathname of the TDS patch package, if required:

Enter the location of the TDS Fix Pack 1 IF 4 package file

Enter the full pathname of the DB2 patch package, if required:

Enter the location of the DB2 9.5 Fix pack 3 package file

...performing pre-install steps for Tivoli Directory Server

DOMAIN set to cork.ie.ibm.com from /etc/resolv.conf

3. At the prompts, enter and confirm the password for the DB2 Administrator (idsinst user). This password was set up when the idsinst user was created (see 3.5 Creating User and Group Accounts).

Important: Ensure that you enter the correct password for the idsinst user.

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

----><idsinst password>

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

----><idsinst password>

Enter the remaining information requested by the script. The defaults can be used.

Please, Enter the LDAP instance location: [/appl/ldap]

---->

Instance location set to /appl/ldap

Please, Enter the encryption seed (12 digits): [165302483387]

---->

Encryption seed set to 165302483387

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

---->

Administrator DN set to cn=Directory Manager

Please, Enter the LDAP Administrator password: [<password>]

---->

Administrator password set to <password>

Please, Enter the LDAP port number: [1389]

---->

Port number set to 1389

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

---->


Secure port number set to 1636

Please, Enter the DB2 database name: [idsdb]

---->

DB name set to idsdb

.... Unpacking IBM Tivoli Directory Server.

The installation log files are /var/install/logs/tds_install_<PID>.log and /tmp/db2_install.log.<PID>.

The tds_install script also supports a -remove option. You can completely remove the TDS/DB2 installation as follows:

# /var/install/sbin/tds_install –base <target directory> –product virtuo -remove

Note: The default encryption seed for the LDAP instance referred to by the TDS/DB2 installation is autogenerated by the operating system’s pseudorandom number generator. The encryption seed used for the instance is logged in /var/install/logs/tds_install_<PID>.log and should be noted securely for future reference.

Note: If the idsinst user account becomes unavailable, for example, due to an expired or changed password, Tivoli Directory Server will no longer be able to authenticate access to DB2 and the LDAP server will become inoperative. To rectify this, see the following Technote for information on updating the TDS password for the DB2 instance: http://www-01.ibm.com/support/docview.wss?uid=swg21297067

5.3 Installing the IBM Tivoli Directory Server Client

Only install the Tivoli Directory Server Client if you are using a remote directory server and installing the directory server schema from the application server.

To install the Tivoli Directory Server Client:


# /var/install/sbin/tds_install -base <target directory> -product virtuo –version 6.2 -client

It is recommended to use the /appl directory as the <target directory> value.

2. Provide the required information at the prompts, including the requests for the absolute pathnames of the TDS package:

Enter the full pathname of the DS package: /var/install/packages/tds62-<OS>-<arch>-base.tar

.... Unpacking IBM Tivoli Directory Server.

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

The tds_install script also supports a -remove option. You can completely remove the TDS Client installation as follows:

# /var/install/sbin/tds_install –base <target directory> –product virtuo –client –remove




Chapter 6. Installing the Tivoli Netcool Performance Manager Software

Install the Tivoli Netcool Performance Manager Software by using one of the following scenarios:

• Unattended installation of a standalone system (if a response file is available) • Installation of a standalone system • Installation of a distributed system

Note: If you are upgrading Tivoli Netcool Performance Manager, consult the Tivoli Netcool Performance Manager: Upgrade Guide - Wireless Component.

Note: It is recommended not to interrupt the installation at any point. The installation will exit if there is a problem.

Important: Before installing Tivoli Netcool Performance Manager, you are strongly advised to read the Tivoli Netcool Performance Manager: Release Notes. Release notes can contain information specific to your installation that is not contained in this guide. Failure to consult the release notes might result in a corrupted, incomplete or failed installation. You are also advised to refer to the following link for all current known issues: http://www-01.ibm.com/support/docview.wss?rs=3256&uid=swg21407459

6.1 Prerequisites

Installed Software:

• Oracle 10g RDBMS • IBM TDS and IBM DB2 • Perl 5.6.1, on the server that will contain the Gateway components • All of the required RHEL packages on RHEL servers


http://www-01.ibm.com/support/docview.wss?rs=3256&uid=swg21407459

6.2 Unattended Installation of a Standalone System

You can install Tivoli Netcool Performance Manager on a single server by using a response file to provide the necessary configuration information. Response files provided with some distributions provide all of the information necessary for an unattended installation. Check the Release Notes to see if your software distribution includes a response file.

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

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

To install Tivoli Netcool Performance Manager using a response file:

1. Place all of the Tivoli Netcool Performance Manager core packages in to the /appl directory. Core packages are listed in section 2.1.2.3.

2. Copy all the technology pack packages, the technology pack order file and gateway packages in to /app.


# cd /appl

# ksh pmw_install -wmcr /appl/virtuo -r <path to response file name>

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

After you have accepted the license agreement, the unattended installation proceeds. After installing the Tivoli Netcool Performance Manager software, the installation automatically installs the gateways and technology packs.

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

$WMCROOT/admin/logs/pmw_install.log

/appl/oracle/product/10.2.0/db_1/cfgtoollogs/dbca/trace.log


6.3 Installing a Standalone System

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

6.3.1 Running an Interactive Installation

Start an interactive installation by running the pmw_install script. At the prompts, provide the required information.

To run an interactive installation:

1. Place all of the Tivoli Netcool Performance Manager software packages in the /appl directory of the server.

2. Run the following as user root:

# cd /appl

# ksh pmw_install -wmcr <WMCROOT>

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

Read and accept the license agreement. The following menu is displayed:

What Type of Virtuo System Are you Installing?

1. Standalone server

2. Application Components only

3. Loader Components only

4. Directory Server Components only

5. Database Components only

6. Skip package deployment

7. Exit PMW Install

---->

3. To install a standalone system, select option 1. 4. At the prompt, enter yes to deploy the packages.

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

The installation proceeds to configure the core software.

Please, Verify Environment Settings

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

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


The installation lists the default values of Tivoli Netcool Performance Manager environment variables. These variables set server hostnames and various TCP port numbers and will vary from location to location. You can accept the default values, restore values to their default settings or change individual values.

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

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

proceed.

6.3.2 Installing the JBoss Application Server

The installation proceeds to install the JBoss Application Server.

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

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

2. At the prompt, enter the location of the JBoss archive. The installation searches the location you provide for version 4.0.3 SP1 of the JBoss Application Server in .zip, .tar.gz or .tar.bz2 format.

Please enter the location of the JBoss 4.0.3SP1 archive (or q to quit)!: [/appl]

---->/appl

The installation will expand the archive into the necessary location:

...........

Buildfile: /appl/virtuo/admin/common/install/scripts/build.xml

init:

[echo] JBOSS VERSION=4.0.3SP1

[echo] JBoss Location=/appl

find-archive:

expand-tar-gz:

[echo] Expanding gzipped tarfile

[untar] Expanding: /appl/jboss-4.0.3SP1.tar.gz into /appl/virtuo


expand-tar-bz2:

expand-zip:

all:

[echo] Expansion complete

[move] Moving 1273 files to /appl/virtuo/as

...........

[delete] Deleting directory /appl/virtuo/jboss-4.0.3SP1

init:



...........


If you provide an incorrect location, the installation stops and provides you with a Web address from which you can download a suitable JBoss archive.

6.3.3 Installing the Directory Server schema

The installation proceeds to install the directory server schema.

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

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

2. At the prompt, enter the LDAP passwords for the directory server users: Directory Manager and SysAdmin:

Please enter the password for 'Directory Manager', the Directory Server User [<password>]:

Please enter the password for 'SysAdmin', the Directory Server User [<password>]:

DS schema installed.

6.3.4 Installing the Database

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

The installation proceeds to install the Tivoli Netcool Performance Manager database.

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

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

2. At the prompts, enter your database System Identifier (SID) and system passwords. You can choose to specify a different database creation template. If you do, ensure that the templates name is of the format <template name>.dbt:

Please, Enter your Database SID (8 character maximum): [vtdb]

---->

Found default template: /appl/virtuo/admin/oracle/conf/vtdb.dbt

Please, Enter the full path of the TNPMW database template: [/appl/virtuo/admin/oracle/conf/vtdb.dbt]

---->

TNPMW database will be created using template /appl/virtuo/ admin/oracle/conf/vtdb.dbt

Please, Enter the sys user password: [<password>]

----><password>

Please, Enter the system user password: [<password>]

----><password>


6.3.5 Installing the Database Schema

The installation proceeds to install the database schema.

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

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

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

Please, Enter the Virtuo Database SID: [vtdb]

---->

Database SID set to "vtdb"

Please, Enter the Database sys user password: [<password>]

---->

Database user sys password set to "<password>"

Please, Enter the Database virtuo user password: [<password>]

---->

Database user virtuo password is set to "<password>"

.... Starting Database Schema 'core'

Creating database schema 'core' in SID 'vtdb'. This may take several minutes ..

..

.... Database Schema Creation finished successfully

6.3.6 Database Schema Post-Installation Tasks

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

At the prompt, enter yes to run post-installation tasks on the schema:

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

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

Please, Enter the TNPMW Database SID: [vtdb]

---->


Please, Enter the SYSDBA Database user name: []

---->sys

Database user name with SYSDBA priv is set to "sys"

Please, Enter the SYSDBA Database user sys password: []

----><password>

Database user sys password is set to "<password>"

Please, Enter the Database user virtuo name: [virtuo]

---->

Database schema name is set to "virtuo"

Please, Enter the Database user virtuo password: [<password>]


---->


.... Starting Loading JAR Files To 'virtuo' Schema

Loading JAR files to database schema 'virtuo' in 'vtdb' database...

...

...

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

6.3.7 Installing the Cronjobs

The installation proceeds to install the cronjobs.

To install the Tivoli Netcool Performance Manager cronjobs, provide the required information when prompted. The recommended responses are shown below.

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

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

Please select the type of TNPMW System you are installing by

entering the number associate with the system type :

All Inclusive (1)

Application (2)

Loader (3)

Directory Server (4)

Database (5)

Gateway (6)

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

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

Select option 1 to see all of the cronjobs on the system.

Please enter the ORACLE_HOME Directory [/appl/oracle/product/10.2.0/db_1]:

(Enter . if unknown)

Please enter the vtdb Database Archive Directory [/oradump/vtdb]:


Please enter the Directory Server log Directory [/appl/ldap/idsslapd-idsinst/logs]:


Please enter the TNPMW Log Directory [/appl/virtuo/logs]:


Please enter the TNPMW Archive Logs Directory [/data/trace_archive1]:


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

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



On completion of the Cronjobs installation, the installation proceeds to install the gateways.

6.3.8 Installing the Gateways

Note: The gateways will not function without Perl 5.6.1 installed. Perl must be installed without threading enabled, and must be installed in the $WMCROOT/gways/ directory.

The installation proceeds to install the gateways and to deploy the gateway packages as follows:

1. At the prompt, enter yes to deploy the gateways on the Tivoli Netcool Performance Manager server.

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

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

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

Checking packages: gwaysperl /appl/vallent-vt-gways-vallent-NA<version>.tar.gz

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

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

Verified the following packages:

* /appl/vallent-vt-gways-vallent-NA<version>.tar.gz

2. At the prompt, enter yes to deploy the packages.


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

6.3.9 Installing the Technology Packs

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

To install technology packs, you must install and deploy packages, initialize the system, and apply the technology packs. Ensure that the technology pack packages and order file (vallent-vt- techpack_order) are in the /appl directory. The order file contains a list of technology packs for installation and the correct order for their deployment.

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

1. At the prompt, enter yes to install the technology packs at this time.

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

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

Techpack install order file found in /appl

Checking packages: vallent-vt-Neutral_Core_GOM vallent-vt-

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


* /appl/vallent-vt-Neutral_Core_GOM-1.0.tar.gz


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



Installing

Neutral_Core_GOM (1.0) ... ok

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

Ericsson_UMTS_UTRAN (1.0) ... ok

All packages installed successfully

Details in pmw_install.log

3. At the prompt, enter yes to initialize the system.

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

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

4. At the prompt, enter yes to apply the technology packs.

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

Buildfile: /appl/virtuo/admin/techpacks/build.xml

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

[wmcInit] 13:03:09,320 [main] DEBUG logging - Created Logging Directory : /appl/ virtuo/logs/vmm

[applyTechPacks] About to install modules. View logs for installation results.

5. For each technology pack you are applying, the techpack_admin tool looks in the conf/vmm directory for a tablespace mapping properties file specific to that technology pack.

Table mappings are used to assign technology pack tables optimal tablespaces.

The file name consists of:

tablespace_" + techpack_dir + "_" + release_version + ".properties"

For example: tablespace_Ericsson_UMTS_UTRAN_1.0.properties

Note: techpack_dir is the technology pack directory name under admin/techpacks, for example Ericsson_UMTS_UTRAN, and not the technology pack name.

If a properties file exists, it is loaded and validated:

Using custom tablespace settings from file /appl/virtuo/conf/vmm/ tablespace_Ericsson_UMTS_UTRAN_1.0.properties for techpack Ericsson UMTS UTRAN

The techpack_admin tool try to map each table name to a tablespace by matching against patterns in the mappings file. It will log the following warning messages to document the tablespace used to create each table, for example:

Creating table ERI_AAL2_PATH_VCC_TP_MBH in user defined tablespace TRAFFIC_MEDIUM

or;

Creating table ERI_RADIO_LINK_STATE_MBH in default tablespace TRAFFIC_JUMBO

If the file is found to contain invalid syntax, the following error is returned and the install fails:

Syntax error in tablespace properties file /appl/virtuo/conf/vmm/tablespace_Ericsson_UMTS_UTRAN_1.0.properties


If no file is found or if the file is not readable, you must confirm that you want to proceed with the default tablespace configuration, for example:

WARNING: Tablespace properties file /appl/virtuo/conf/vmm/ tablespace_Ericsson_UMTS_UTRAN_1.0.properties does not exist!

Do you want to continue with techpack default tablespace settings? [y|n]

Enter y to use default tablespace settings. If you enter n the installation will fail and no technology packs are applied.

6. If the specific or default tablespace settings have been applied successfully, the installation continues:

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

[applyTechPacks] All modules installed successfully.

[delete] Deleting: /appl/virtuo/admin/techpacks/new_techpacks

[echo] Analyzing Tech Pack tables ...

[wsqlplus] Reading /appl/virtuo/admin/techpacks/analyze/vmm_analyze.pks

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

[wsqlplus] Package dropped.

[wsqlplus] Commit complete.

[echo] Analyze complete

BUILD SUCCESSFUL

Total time: 40 minutes 18 seconds

6.3.10 Encrypting Passwords

The installation will encrypt all stored Tivoli Netcool Performance Manager system passwords.

At the prompt, enter yes to encode the system passwords.

Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yes Replacing all passwords with encoded passwords... Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties.N Encoding values in /appl/virtuo/conf/externalreporting/default.properties Encoding values in /appl/virtuo/conf/externalreporting/default.properties.N 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/as/as-default.properties Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.BACKUP Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.N Encoding values in /appl/virtuo/conf/ldap/default.properties 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.

The installation is now complete. To configure your Tivoli Netcool Performance Manager system, see Chapter 8 Post-Installation Tasks.


6.4 Installing a Distributed System

You can distribute Tivoli Netcool Performance Manager across a number of servers by using the interactive installation scripts provided.

6.4.1 Running an Interactive Installation

To install a distributed system, run the pmw_install script on each individual server to install the required components. Enter information as required by the installation scripts. You should install the servers (or components on shared servers) in the following order:

1. Database server 2. Directory server 3. Application server (includes gateways and technology packs if applicable) 4. Loader server 5. Gateway server (if installed separately) 6. Technology packs (if installed separately)

6.4.2 Installing a Database Server

To install a database server:

1. Place all of the Tivoli Netcool Performance Manager software packages in the /appl directory of the database server.


# cd /appl

# ksh pmw_install -wmcr <WMCROOT> [ -a ]

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

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

3. Read and accept the license agreement and the following menu is displayed:

What Type of System Are you Installing ?







7. Exit TNPMW Install


---->

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


6.4.2.1 Configuring the Database



1. Accept Variable Values below

2. Reset Variables to Default values

3. Change WMCHOST=<server_name>

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

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


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

1. Select option 3 and change the value of WMCHOST to the hostname of the application server. 2. Change any other values that you want to change from the default values. 3. When you are satisfied that the environment variable values are correct, accept the values and

proceed.

6.4.2.2 Installing the Database

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

The installation proceeds to install the database.

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


2. At the prompts, enter your database System Identifier (SID) and system passwords. You can choose to specify a different database creation template. If you do, ensure that the template's name is of the format <template name>.dbt:

Please, Enter your Database SID (8 character maximum):

---->vtdb


Please, Enter the full path of the TNPMW database template: [/appl/virtuo/admin/oracle/conf/vtdb.dbt]

---->

TNPMW database will be created using template /appl/virtuo/ admin/oracle/conf/vtdb.dbt]



----><password>


----><password>

Note: After you install the Tivoli Netcool Performance Manager database on the database server, copy the ${ORACLE_HOME}/network/admin/tnsnames.ora file to the same location on the application server that has the Oracle 10g client installed.

6.4.2.3 Installing the Database Schema

The installation proceeds to install the database schema as follows:

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


2. At the prompts, enter the database SID:

Please, Enter the Virtuo Database SID:

---->vtdb


3. At the prompt, enter the password for the database system user:

Please, Enter the Database sys user password:

----><password>


4. At the prompt, enter the password for the database virtuo user:

Please, Enter the Database virtuo user password:

----><password>



Creating Database Schema 'core' in . This may take several minutes ...

..


6.4.2.4 Running Post-installation Tasks on the Database Schema

The installation proceeds to run post-installation tasks on the database schema as follows:

1. At the prompt, enter yes to run post-installation tasks on the Tivoli Netcool Performance Manager database schema.


2. At the prompt, enter the database SID:


---->


3. At the prompt, enter the name of the database system user:



---->sys


4. At the prompt, enter the password for the database system user:


----><password>

Database user sys as sysdba password is set to "<password>"

5. At the prompt, enter the name of the database virtuo user:

Please, Enter the Database user virtuo name:

---->virtuo


6. At the prompt, enter the password for the database virtuo user:

Please, Enter the Database user virtuo password:

----><password>




....


6.4.2.5 Installing the Cronjobs

To install the Tivoli Netcool Performance Manager cronjobs:

1. The installation will prompt you for the following installation details. The recommended responses are shown below (the prompts displayed can vary depending on your installation):


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



All Inclusive (1)

Application (2)

Loader (3)


Database (5)

Gateway (6)

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

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



Please enter the vtdb Database Archive Directory [/oradump/vtdb]:



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

Once the cronjob installation has completed successfully, the cronjob installation log output can be found at the following location:


6.4.2.6 Encrypting the Passwords

The installation can encrypt all stored Tivoli Netcool Performance Manager system passwords.


Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yes Replacing all passwords with encoded passwords... Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties.N Encoding values in /appl/virtuo/conf/externalreporting/default.properties Encoding values in /appl/virtuo/conf/externalreporting/default.properties.N 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/as/as-default.properties Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.BACKUP Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.N Encoding values in /appl/virtuo/conf/ldap/default.properties 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.

6.4.3 Installing a Separate Directory Server

You can separate the directory server from the application server using one of these two methods:

• Configure the directory server schema from the application server. This is the recommended method. It does not require that you run the pmw_install script on the directory server. If you are using this method, skip this procedure and go on to install the application server as described in 6.4.4 Installing the Application Server.

• Install the directory server packages and configure the directory server schema on the directory server by using the pmw_install script, as described in this procedure. Enter extra information at the prompts, such as the locations of the application and database servers.

Install a separate directory server as follows:

1. Place all of the Tivoli Netcool Performance Manager software packages in the /appl directory of the directory server.


# cd /appl


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


The –a option is used in a distributed installation scenario, where a different type of Tivoli Netcool Performance Manager server is to be installed “on top” of an existing one, for example, a Loader server on top of a previously installed application server.










---->

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


6.4.3.1 Installing the Directory Server Schema


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


2. At the prompt, enter the LDAP password for the directory server user Directory Manager:


3. At the prompt, enter the LDAP password for the directory server user SysAdmin:


4. At the prompt, enter the application server hostname:

Please enter the TNPMW appserver hostname:

5. At the prompt, enter the database server hostname:

Please enter the database server hostname:

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

6. At the prompt, enter the LDAP password for the directory server user System:

Please enter the password for ‘System’, the Directory Server User [<password>]:



1. At the prompts, enter these recommended responses:



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



All Inclusive (1)

Application (2)

Loader (3)


Database (5)

Gateway (6)

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

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








At the prompt, enter yes to encode the system passwords:

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

Replacing all passwords with encoded passwords...

...

Passwords may also be stored in /appl/virtuo/admin/logs/pmw_install.log, so it should be removed when not needed anymore.

6.4.4 Installing the Application Server

To install the application server:

1. Place all of the Tivoli Netcool Performance Manager software packages in the /appl directory of the server.


# cd /appl


<WMCROOT> is the location in which you want to install Tivoli Netcool Performance Manager. The default installation directory is: /appl/virtuo.

The –a option is used in a distributed installation scenario, where a different type of Tivoli Netcool Performance Manager system is to be installed “on top” of an existing one, for example, a Loader system on top of a previously installed application server.











---->

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


6. Verify the correct values for the following variables:

WMCHOST The hostname of the application server

VTDBHOST The hostname of the database server

LDAPHOST The hostname of the LDAP server






4. Change VTDBHOST=<server_name>

5. Change LDAPHOST=<server_name>

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

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


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

7. Select option 4 and change the value of VTDBHOST to the hostname of the database server and the value of LDAPHOST to the hostname of the DS server.

8. Select option 5 and set the value of LDAPHOST to the hostname of the directory 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.

6.4.4.1 Installing the JBoss Application Server

The installation proceeds to the installation of the JBoss Application Server as follows:


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

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

2. At the prompt, enter the location of the JBoss archive. The installation searches the location you provide for version 4.0.3 SP1 of the JBoss Application Server in .zip, .tar.gz or .tar.bz2 format.


---->/appl

The installation will expand the archive into the necessary location:

...........

Buildfile: /appl/virtuo/admin/common/install/scripts/build.xml

init:



find-archive:

expand-tar-gz:




expand-tar-bz2:

expand-zip:

all:



...........

[delete] Deleting directory /appl/virtuo/jboss-4.0.3SP1

init:



...........

If you enter an incorrect location, the installation stops and a Web address is provided from which you can download a suitable JBoss archive.

6.4.4.2 Installing the Directory Server Schema

Note: If you have already configured the Directory server schema using the procedure in 6.4.3 Installing a Separate Directory Server, then answer no at the prompt.


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


2. At the prompts, enter the LDAP passwords for the directory server users: Directory Manager, SysAdmin and System:




Please enter the password for ‘System’, the Directory Server User [<password>]:



1. At the prompts, enter these recommended responses:


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



All Inclusive (1)

Application (2)

Loader (3)


Database (5)

Gateway (6)

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

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










On completion of the Cronjobs installation, the installation proceeds to encrypt the passwords.

6.4.4.4 Installing the Gateways

The Tivoli Netcool Performance Manager Gateways are installed in $WMCROOT/gways. The gateways installation package should be placed in the same directory as the core Tivoli Netcool Performance Manager packages. The gateways installation package file is:

gways-gateway-framework-<version>.tar.gz.


1. At the prompt, enter yes to deploy the gateways on the Tivoli Netcool Performance Manager server:

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

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

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

Checking packages: gwaysperl /appl/vallent-vt-gways-vallent-NA<version>.tar.gz

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

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


* /appl/vallent-vt-gways-vallent-NA<version>.tar.gz

2. At the prompt, enter yes to deploy the packages:


Installing

gways-vallent (NA<version>) ... ok


See $WMCROOT/admin/logs/pmw_install.log log file for installation errors.

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

6.4.4.5 Installing the Technology Packs

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

To install technology packs, you must install and deploy packages, initialize the system, and apply the technology packs. Ensure that the technology pack packages and order file (vallent-vt- techpack_order) are in the /appl directory. The order file contains a list of technology packs for installation and the correct order for their deployment.

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

1. At the prompt, enter yes to install the technology packs:

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

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


Checking packages: vallent-vt-Neutral_Core_GOM vallent-vt-

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



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

2. At the prompt, enter yes to deploy the packages:


Installing



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



Details in pmw_install.log

3. At the prompt, enter yes to initialize the system:


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

4. At the prompt, enter yes to apply the technology packs:


Buildfile: /appl/virtuo/admin/techpacks/build.xml

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

[wmcInit] 13:03:09,320 [main] DEBUG logging - Created Logging Directory : /appl/ virtuo/logs/vmm

[applyTechPacks] About to install modules. View logs for installation results.

5. For each technology pack you are applying, the techpack_admin tool looks in the conf/vmm directory for a tablespace mapping properties file specific to that technology pack.

Table mappings are used to assign technology pack tables optimal tablespaces.

The file name consists of:

tablespace_" + techpack_dir + "_" + release_version + ".properties"

For example: tablespace_Ericsson_UMTS_UTRAN_1.0.properties

Note: techpack_dir is the technology pack directory name under admin/techpacks, for example Ericsson_UMTS_UTRAN, and not the technology pack name.

If a properties file exists, it is loaded and validated:

Using custom tablespace settings from file /appl/virtuo/conf/vmm/ tablespace_Ericsson_UMTS_UTRAN_1.0.properties for techpack Ericsson UMTS UTRAN

The techpack_admin tool try to map each table name to a tablespace by matching against patterns in the mappings file. It will log the following warning messages to document the tablespace used to create each table, for example:

Creating table ERI_AAL2_PATH_VCC_TP_MBH in user defined tablespace TRAFFIC_MEDIUM

or;

Creating table ERI_RADIO_LINK_STATE_MBH in default tablespace TRAFFIC_JUMBO

If the file is found to contain invalid syntax, the following error is returned and the install fails:

Syntax error in tablespace properties file /appl/virtuo/conf/vmm/tablespace_Ericsson_UMTS_UTRAN_1.0.properties

If no file is found or if the file is not readable, you must confirm that you want to proceed with the default tablespace configuration, for example:

WARNING: Tablespace properties file /appl/virtuo/conf/vmm/ tablespace_Ericsson_UMTS_UTRAN_1.0.properties does not exist!

Do you want to continue with techpack default tablespace settings? [y|n]


Enter y to use default tablespace settings. If you enter n the installation will fail and no technology packs are applied.

6. If the specific or default tablespace settings have been applied successfully, the installation continues:

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


[delete] Deleting: /appl/virtuo/admin/techpacks/new_techpacks

[echo] Analyzing Tech Pack tables ...

[wsqlplus] Reading /appl/virtuo/admin/techpacks/analyze/vmm_analyze.pks

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

[wsqlplus] Package dropped.

[wsqlplus] Commit complete.

[echo] Analyze complete

BUILD SUCCESSFUL







Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties

Encoding values in /appl/virtuo/conf/alarm_external_api/alarmapi.properties.N

Encoding values in /appl/virtuo/conf/externalreporting/default.properties

Encoding values in /appl/virtuo/conf/externalreporting/default.properties.N

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/as/as-default.properties

Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties

Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.BACKUP

Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.N

Encoding values in /appl/virtuo/conf/ldap/default.properties

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.

You must also install the loader components on the application server. See 6.4.5 Installing a Loader Server. When installing the loader components, run the pmw_install script with the -a option.


6.4.5 Installing a Loader Server

To install a loader server:

1. Place all of the Tivoli Netcool Performance Manager software packages in the /appl directory of the server:


# cd /appl


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

The –a option is used where a different type of Tivoli Netcool Performance Manager system is to be installed “on top” of an existing one, for example, a Loader system on top of a previously-installed Application server.










---->

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


6.4.5.1 Configuring the Loaders

1. Ensure that you enter the correct values for the following variables:

WMCHOST The hostname of the application server

VTDBHOST The hostname of the database server

LDRHOST The hostname of the loader server



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

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



3. Change LDRHOST=<server_name>



5. Change VTDBHOST=<server_name>


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

2. Select option 4 and change the value of WMCHOST to the hostname of the application server. 3. Select option 5 and change the value of VTDBHOST to the hostname of the database server. 4. Change any other values that you want to change from the default values. 5. When you are satisfied that the environment variable values are correct, accept the values and

proceed.


To install the cronjobs:

1. The installation will prompt you for the following installation details. The recommended responses are shown below:


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



All Inclusive (1)

Application (2)

Loader (3)


Database (5)

Gateway (6)

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

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





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






At the prompt, enter yes to encode the system passwords:








Encoding values in /appl/virtuo/conf/as/as-default.properties.BACKUP

Encoding values in /appl/virtuo/conf/as/as-default.properties


Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.BACKUP


Encoding values in /appl/virtuo/conf/ldap/default.properties


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.

Note: For instructions on how to proceed after the loader software has been installed on the new server, see 7.13 Creating a Loader on a Distributed Server.

6.4.6 Installing the Gateways Separately

You can install the gateways separately from a core installation. The gateways are installed in $WMCROOT/gways. Place the gateways installation package in the same directory as the core Tivoli Netcool Performance Manager packages. The recommended location is /appl.

To install the gateways, copy the EPM packages to a directory of your choice. In the following example the /appl directory is used.

1. Execute the following commands as user virtuo:

cd /appl/virtuo/admin/common/install/scripts

./deploy_gateways -pkgdir /appl

The deploy_gateways script searches the location you specify for files of the form gways-gateway-framework-*.tar.gz. If you do not specify a directory, it searches in the current directory. If no file names matching this pattern are found, it looks for files that match the pattern vallent-vt-gway*.tar.gz.

Note: If you want to install gateways other than the standard ones, run deploy_gateways as follows: ./deploy_gateways -pkgdir /appl -gateways <gw1>,<gw2>,…


where <gw1>,<gw2>,… is a comma-separated list of gateway packages.



Installing

gways-vallent (NA9.1.2.18.01) ... ok


For installation error messages, see the $WMCROOT/admin/logs/pmw_install.log log file.


Chapter 7. Installing the Technology Packs Separately

Note: In a distributed installation, install the technology packs on the application server only unless otherwise indicated.

Note: It is recommended not to interrupt the installation of technology pack installation.

You install technology packs by using the deploy_techpacks script and the techpack_admin tool. Before you install a technology pack, ensure that the main Tivoli Netcool Performance Manager schema is installed. For more information on using the techpack_admin tool, see the Tivoli Netcool Performance Manager: Administration Guide - Wireless Component.

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

7.1 Starting the System

To start the system:

1. Check if the application server has started:

sap disp

2. If the application server is not started, run the following commands, as user virtuo.

sap start as

7.2 Setting up Users and Data Sources

Before installing technology packs, create the users and data sources:

1. As user virtuo, run the following command:

sys_init -u sysadm -p <password> -h <fully-qualified hostname>

If the users and data sources already exist on the system you will see the following message. You can continue the installation.

ERROR: The system is already initialized

2. Alternatively, use a web browser to open:

http://<hostname>:8080/sysinit

Log in with the userid sysadm and password to create the users and data sources.


7.3 Checking Database Space

Check the Tivoli Netcool Performance Manager database to make sure tablespace sizing is correct, as per the customer sizing response file. All tablespaces should be the correct size for your network.

Before you install the technology packs, there should be at least 50% free space in each tablespace.

To check tablespaces using Oracle Enterprise Manage Console (or another tool):

1. Connect to the database as user virtuo. 2. Select Storage on Enterprise Manage Console; select TableSpaces. 3. Check the Used % column (last column on right) and confirm that none have exceeded 50% (for

example WM_CLIENT). If they have, add a new dbf file by: a. Double-clicking on table space. b. Copying a dbf entry that exists and pasting it into a new row. c. Modifying the name to make it unique.

7.4 Installing the Technology Pack Step 1

To install the technology pack:

1. As user virtuo copy the technology pack EPM packages (for example, vallent-vt-<techpack name1>.gz, vallent-vt-<techpack name2>.gz, and so on) and the order file (vallent-vt- techpack_order) into the $WMCROOT/admin/techpacks/packages directory.

The order file contains a list of technology packs for installation and the correct order for their deployment.

2. Install the technology packs as user virtuo as follows:

cd /appl/virtuo/admin/common/install/scripts

./deploy_techpacks -wmcr $WMCROOT -pkgdir $WMCROOT/admin/techpacks/packages

The installation searches the directory specified by -pkgdir for the vallent-vt-techpack-order file. The script will use this list and attempt to install each of the technology packs in turn. The installation looks for the technology pack packages in the same directory as the vallent-vt-techpack-order file.

To install a custom set of technology packs, run deploy_techpacks as follows:

./deploy_techpacks -wmcr $WMCROOT -pkgdir $WMCROOT/admin/techpacks/

packages -techpacks <techpack1>,<techpack2>,...

<techpack1>,<techpack2>,… is a comma-separated list of technology pack packages. The release notes for your distribution will state if this step is necessary.

The following output is displayed:

Techpack install order file found in /appl/virtuo/admin/techpacks/packages

Checking packages: <techpacks>


<package 1>

<package 2>

...

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


3. Enter yes to confirm the package deployment. 4. When the installation is complete, check the following:

• The technology packs are installed in $WMCROOT/admin/techpacks. • The generated file $WMCROOT/admin/techpacks/new_techpacks contains the complete list of

installed technology packs in the correct order. • If any errors occurred during the installation. See the

$WMCROOT/admin/logs/pmw_install.log file for any error messages.

7.5 Installing the Technology Pack Step 2

Run the $WMCROOT/bin/techpack_admin script to configure the new technology packs.

The techpack_admin script looks for a file called new_techpacks generated during Installing the Technology Pack Step 1. This file contains a list of technology packs to install in the database by using the techpack_admin script.

1. To apply the technology packs, as user virtuo, run the following commands:

sapmon start

sapmgr start

sap start as

techpack_admin -a

The techpack_admin -a script causes a number of changes that you must verify:

• Creation of technology pack traffic tables in the database • Loading of the technology pack loadmaps • Configuration of the new loaders • Service Application Server (SAP) configuration for new loaders

7.6 Performing Post-Installation Checks for the Technology Packs

To ensure that the technology packs are installed correctly, check the following items.

• The technology packs are successfully installed under $WMCROOT/admin/techpacks • There are no error messages in log file $WMCROOT/logs/vmm/vmm-server.log • The wmd_field_def table in the database is populated • Run this command as user virtuo:

schema_admin -checkmodel

This query determines the hierarchy used in reporting. If this query returns NULL, or if the reportable column in the output is set to N, then there is a problem and you should uninstall and reinstall the technology packs.

• Generic loader start script generated called $WMCROOT/bin/run_njloader • Check the database for rows entered in the following loadmap tables:

LC_DATASOURCE


LC_LOADMAP

LC_RELATIONS

LC_RULESET

LC_LOADER_CONFIG_PROPERTIES

SOURCE_TABNAME can be null, this means that the nc table has no associated performance tables.

• Loader data directories created:

$WMCROOT/var/loader/spool/<DSname_DSversion>/<DS_version>/

$WMCROOT/var/loader/spool/<DSname_DSversion>/<DS_version>/good

$WMCROOT/var/loader/spool/<DSname_DSversion>/<DS_version>/bad

• To get information on the rulesets associated with the technology packs installed, enter the following query:

SQL> select RULESET_ID, DESCRIPTION, TYPE from LC_RULESET;

• Ensure the source folder for loading files is set correctly in the loader properties. Run the following command as user virtuo:

loader_admin -unload all_loader_properties.xml -instance ALL

A file called all_loader_properties.xml is created.

Example content of a all_loader_properties.xml is shown below:

<loaderconfig>

<loader>

<name>alcgsmbss_b9</name>

<property>

<name>itm.enabled</name>

<value>FALSE</value>

</property>

…..

</loader>

<loader>

<name>motgsmbss_gsr80</name>

….

</loader>

</loaderconfig>

There should be a <loader> section for each installed loader. If there is not a <loader> section for each loader, then there has been a problem during technology pack installation. In this case uninstall and re-install the technology pack.

Check that each <loader> section contains a datasource.folder property:

<property>

<name>datasource.folder</name>

<value>/appl/virtuo/var/loader/spool/dsname_dsversion/dsversion</value>

</property>


The datasource name and version will have white spaces and non-alphanumeric characters removed. For example, <property> <name>datasource.folder</name> <value>/appl/virtuo/var/loader/spool/nkbss_oss31ed3/OSS3.1_ED3</value> </property> The datasource folders do not need to exist when the technology pack is installed. If they do not exist, they will be created by the loader on first startup. In this case, they must to be specified in a location where the virtuo user will have permission to create them. The datasource.good and datasource.bad directories must also be specified in a location where the virtuo user will have permission to create them. By default they are subdirectories of the datasource folder, and so have the correct permissions.

If the datasource folder properties are not correct, update them as appropriate. A full description of how to update loader properties is given in the Loader Configuration section of the Tivoli Netcool Performance Manager: Administration Guide - Wireless Component.

The rest of the all_loader_properties.xml file can also be examined to see that the properties are correct for the current installation. When updating loader properties, it is better to export the properties for just the instance you want to change by specifying the instance name when using the loader_admin tool.

• To get information on data sources associated with the loadmaps and technology packs installed, enter the following query:

SQL> select DATASOURCE_NAME, DATASOURCE_VERSION from LC_DATASOURCE;

Ensure that:

• The DATASOURCE_NAME and version is contained within the VALUE of the property. • The directory specified in the NAME exists. For example:

DATASOURCE_NAME DATASOURCE_VERSION NAME

Nokia BSS OSS3.1 ED3 /appl/virtuo/var/loader/spool/nokiabss_oss31ed3/OSS3.1_ED3

• SAP property files created for each loader type:

$WMCROOT/conf/processes/processes-load_<loader>.properties

Note: The timezone setting for a loader currently defaults to the time zone on the installation server. Confirm that this setting is correct for the data you are loading. If necessary, change the setting by using the loader_admin tool.

7.7 Starting the SAP Process Monitor Tool

Start the Tivoli Netcool Performance Manager process management tool:

1. Run the following commands, as user root:

svcadm disable sapmgr-na

svcadm enable sapmgr-na

service sapmgrvirtuo --full-restart


2. Check that the application server has started and that all the configured loaders have stopped by executing the following command as user virtuo:

sap disp

The following output should be displayed showing the application server has started and all the configured loaders have stopped:

NAME STATE SINCE

as STARTED 17:54:38

nc_cache STARTED 17:55:07

alarm_cache STARTED 17:55:13

<loader> stopped -

. . .

. . .

7.8 Starting the Application Server 1. To check if the application server has started, run the following command as user virtuo.

sap disp

If the application server is started, then you will see output similar to the following:

NAME STATE SINCE

as STARTED 17:54:38



2. If the application server is not started, run the following commands as user virtuo.

sap start as

sap disp

The application server status should be shown as started.

NAME STATE SINCE

as STARTED 17:54:38



7.9 Starting the Loaders

You can now start the newly configured loaders.

1. Start the loaders as user virtuo

$ sap start <loader name>

2. Check the latest loaders are shown as added:

$ sap disp

NAME STATE SINCE


as STARTED 12:15:55

nc_cache stopped 12:16:32

alarm_cache stopped 12:17:48

<loader> STARTED 12:15:50

<loader>1 STARTED 12:15:52

3. Check the loader logs for start up issues with any of the loaders:

$WMCROOT/logs/loader/*.log

7.10 Configuring Multiple Identical Loaders

Typically, you would configure and start more than one loader of a particular type.

The following examples illustrate how to add additional loaders of a particular type. Run commands as user virtuo unless otherwise indicated.

1. Create a new loader instance by using default system properties, or by using the properties of an existing loader instance. To create a loader instance by using default properties, first use lcm_admin to check the data source name and version of the loader you want to create:

$ lcm_admin –list

Data Source Information

Techpack Name Version DataSource Name Version Technology Vendor

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

Ericsson GSM BSS 1.0 Ericsson BSS R10 GSM Ericsson

2. To add a new loader instance, use the loader_admin command, giving an arbitrary name for the instance and the data source name and version from the required technology pack:

$ loader_admin –init –instance ericssconbss_r10_1 –dsname “Ericsson BSS” –dsversion R10

Buildfile: /appl/virtuo/conf/loader/loader_admin.xml

init:

[initlog] 18:14:11,483 [main] WARN logging - TRCE-0022 : The name of the process is null or empty.

initloader:

[initloader] Initialise Loader:

[initloader] Instance Name: [ericssconbss_r10_1]

[initloader] Datasource Name: [Ericsson BSS]

[initloader] Datasource Version: [R10]

[initloader] New properties created for [ericssconbss_r10_1]

[initloader] Created sap process file for [ericssconbss_r10_1]

[initloader] Restarted sapmgr

[initloader] New instance creation completed

3. To create a new instance from the properties of an existing instance:

$ loader_admin –init –instance ericssconbss_r10_1 -copy ericssonbss_r10

Buildfile: /appl/virtuo/conf/loader/loader_admin.xml

init:


[initlog] 18:17:27,389 [main] WARN logging - TRCE-0022 : The name of the process is null or empty.

initloader:

[initloader] Initialise Loader:

[initloader] Instance Name: [ericssconbss_r10_1]

[initloader] Source instance name: [ericssonbss_r10]

[initloader] New properties created for [ericssconbss_r10_1]

[initloader] Created sap process file for [ericssconbss_r10_1]

[initloader] Restarted sapmgr

[initloader] New instance creation completed

BUILD SUCCESSFUL

Total time: 8 seconds

4. Whichever method you use to create the new loader, use the sap disp command to check that it is now in the SAP process list. (Note that SAP might be unavailable for a few seconds after loader_admin –init while the sapmgr process re-initializes):

NAME STATE SINCE

as STARTED Oct 23, 2008

nc_cache STARTED Oct 29, 2008

alarm_cache STARTED Oct 29, 2008

load_ericsson bss_r10 stopped -

load_ericssconbss_r10_1 stopped –

7.11 Loading Data

Note: Distributed systems only. In a distributed installation, load data on the loader servers only.

Place data files (.lif) in the loader spool directory. Files will be processed and placed in either the good or bad directory. You can configure Tivoli Netcool Performance Manager gateways to generate .lif files in the appropriate loader directory.

For example:

/appl/virtuo/var/loader/spool/<DSname_DSversion>/<DS_version>

7.11.1 Verifying Data Loading

To verify data loading:

• Check technology pack tables for network configuration (NC) and traffic data loading into the tables. The Traffic tables are stored in the traffic_large tablespace in the database pointed to by ORACLE_SID for example, vtdb.

• Data .lif files should be processed and put in either the good or bad directories under the generated loader directory for the configured loader, for example:

$WMCROOT/var/loader/spool/<DSname_DSversion>/<DS_version>/good

$WMCROOT/var/loader/spool/<DSname_DSversion>/<DS_version>/bad


7.12 Removal of Loadmaps and Loader Configuration

Use this procedure if loader configuration fails or for a point release upgrade. This procedure removes all of the loader properties files in /appl/virtuo/conf/processes/.

Important: Remove all installed technology packs before undertaking this procedure. Use the techpack_admin -u command to uninstall technology packs. See the Tivoli Netcool Performance Manager Administration Guide - Wireless Component for information on uninstalling technology packs.

To perform a reinstall of the loader and loadmap configuration, complete the following steps:

1. Stop LCM, sapmgr and sapmon as user root:

svcadm disable sap-na


svcadm disable sapmon-na

service sapvirtuo stop

service sapmgrvirtuo stop

service sapmonvirtuo stop

2. Remove spool directories as user virtuo.

rm -rf /appl/virtuo/var/loader/spool/*

3. Delete LC_* table rows as user virtuo.

SQL> delete from lc_datasource;

SQL> delete from lc_loadmap;

SQL> delete from lc_relations;

SQL> delete from lc_ruleset;

SQL> delete from lc_loader_config_properties where loader_name != 'SYSTEM';

4. Remove SAP loader properties files as user virtuo.

rm -rf /appl/virtuo/conf/processes/*load*.properties

5. Reinstall the technology packs and loaders by using the procedures starting at 7.1 Starting the System.

7.13 Creating a Loader on a Distributed Server

When you install technology packs on the application server, the installation creates the loader instances on the application server by default. To configure a separate loader server, you need to relocate these instances to the loader server.

Note: Before you can move a loader instance to another server, you must install the loader software packages on the new server.


Ensure that the loader server has been installed by using the procedure in 0 You must also install the loader components on the application server. See 6.4.5 Installing a Loader Server. When installing the loader components, run the pmw_install script with the -a option.

Installing a Loader Server.

To start a loader instance on a distributed server, it is necessary to relocate the sap process manually. (If a new instance is required, first create the instance on the application server as described in 7.9 Starting the Loaders).

To relocate the SAP process, complete the following steps on the application server:

1. If the loader instance that you want to relocate is running, stop the instance:

$ sap stop load_<loadername>

2. Edit the SAP process file for the loader:

$WMCROOT/conf/processes/processes-load_<loadername>.properties.

Change the value of the hostname property to the required target server:

com.comnitel.process.load_<loadername>.host=<servername>

Save the file.

3. Stop and restart the SAP manager. To stop the SAP manager, run the following commands as user root:


Check that the SAP manager has been disabled:

svcs "*-na*"

service sapmgrvirtuo stop

4. Restart the SAP manager:


service sapmgrvirtuo start

5. Check the loader status:

sap disp -l

The loader being moved should show the new hostname:

NAME STATE SINCE HOST GROUP STIME PID


as STARTED Oct 23, 2008 <core_host> asgroup Oct 23, 2008 17277

nc_cache STARTED Oct 29, 2008 <core_host> loadercache Oct 29, 2008 6716

alarm_cache STARTED Oct 29, 2008 <core_host> loadercache Oct 29, 2008 6726

load_<loadername> stopped - <target_host> Ericsson GSM BSS - -

You can now stop and start this loader as normal by using sap start from either the application server or the distributed loader server. Note that when the loader first starts on the new server, it will create its data source folder on the new server.


Chapter 8. Post-Installation Tasks

Complete the following post-installation tasks:

• Provisioning Stored Busy Hours, Summaries and Data Availability • Configuring Application Server Memory (Optional) • Configuring Loader Server Memory (Recommended) • Checking the Time Zone Settings for the Report Scheduler • Changing the Default Client Ports • Integrating IBM Tivoli Monitoring (optional)

8.1 Provisioning Stored Busy Hours, Summaries and Data Availability

A number of technology packs contain Stored Busy Hour (SBH), Summary, and Data Availability definitions. You must provision these definitions before you can use them.

8.1.1 Stored Busy Hours Definitions

If a technology pack contains SBH definitions, these definitions are contained in an XML file. The SBH definition file for each technology pack is:

<TP_ROOT>/busyhours/BusyHourInstance.xml

You can provision SBH definitions by using the sbh_admin tool to import an SBH definition file. The sbh_admin tool is located in:

$WMCROOT/bin

You can run the sbh_admin tool from any directory as user virtuo.

Usage

sbh_admin -i [-f <file> | -p <directory>] -m [overwrite | ignore | fail]

-i Import

-f Import the Stored Busy Hour Definition from <file>.

-p Import all busy hour definitions stored in <directory>. All files with an .xml suffix are imported.

-m mode:

overwrite: If the definition already exists, update it.

ignore: If the definition already exists, do not update it and do not fail the import

fail: If the definition already exists, fail the import.

Examples


sbh_admin -i -f BusyHourInstance.xml -m overwrite

Import the SBHs defined in BusyHourInstance.xml, overwriting the definitions if they already exist.

sbh_admin -i -p indir -m overwrite

If the two files SBH1.xml and SBH2.xml exist in the indir directory, the definitions in SBH1.xml and SBH2.xml are imported.

8.1.2 Summary Definitions

If a technology pack contains Summary definitions, these definitions are contained in an XML file.

The Summary definition file for each technology pack is:

<TP_ROOT>/summaries/SummaryInstance.xml

You can provision summary definitions by using the summary_admin tool to create each definition in a definition file. The summary_admin tool is located in:

$WMCROOT/bin

You can run the summary_admin tool from any directory as user virtuo.

Note: If Summary definitions are provided but not provisioned, an attempt to use these definitions will result in an error. For example, opening a report template that uses KPIs with Summary definitions specified in a technology pack’s SummaryInstance.xml.

Usage

The full usage of the tool is not documented here. Only usage relevant to provisioning a definition file is shown.

summary_admin -c -f <file>

-c Create

-f Create Summary Definitions from <file>.

Examples

summary_admin -c -f SummaryInstance.xml

Create the Summaries defined in SummaryInstance.xml.

8.1.3 Data Availability Definitions

If a technology pack contains Data Availability definitions, these definitions are contained in an XML file. This file contains information about the technology pack, and a list of blocks of data that are loaded for that technology pack.

If the value of the block is set to true, that is, <block name="ATMUSAGE">true</block>, then after the file is loaded the loader will start producing Data Availability (DA) statistics every time it loads a block of ATMUSAGE data.


Note: This file is intended to be user-customized: you can switch blocks on or off. It is important to realize that blocks which are tracked take approximately twice as long to load as blocks that are not. Only high-level entities (MSC, BSC, ...) should be tracked, but not low-level entities (TRX, ...).

The Data Availability definition file for each technology pack is:

<TP_ROOT>/dataavailability/dataavailability<techpack_name>.xml

You can provision data availability definitions by using the lcm_admin tool. The lcm_admin tool is located in:

$WMCROOT/bin

You can run the lcm_admin tool from any directory as user virtuo.

Usage

The full usage of the tool is not documented here. Only usage relevant to provisioning a definition file is shown.

lcm_admin -load <data_availability.xml>

Examples

lcm_admin -load dataavailability_umts_siemens_utran_umr050_1.0.0.0.xml

8.2 Configuring Application Server Memory (Optional)

On larger Tivoli Netcool Performance Manager installations, configuring Java Virtual Machine (JVM) heap memory settings can improve performance and allow for better application server usage.

You can configure the heap memory to suit the size of your system and the amount of system usage, particularly for running large reports.

To configure the heap memory, edit the jvm.args property in the $WMCROOT/conf/as/jvm-default.ini file.

8.2.1 The jvm.args Property

The jvm.args property contains the following settings:

-Xms512m -Xmx512m -XX:+AggressiveHeap

8.2.1.1 -Xms<n>

-Xms<n> specifies the initial size of the memory allocation pool in bytes. Append the letter m or M to indicate megabytes, or g or G to indicate gigabytes. The default value is 1024 MB.

Examples include:

-Xms1024m

-Xms1G


8.2.1.2 -Xmx<n>

-Xmx<n> specifies the maximum size of the memory allocation pool in bytes. Append the letter m or M to indicate megabytes, or g or G to indicate gigabytes. The default value is 1024 MB.

Examples include:

-Xmx2048m

-Xmx2G

8.2.1.3 -XX:+AggressiveHeap

-XX:+AggressiveHeap is a Garbage Collection Tuning setting. The option inspects the server resources (size of memory and number of processors), and attempts to set various parameters to be optimal for long-running, memory allocation-intensive jobs. The physical memory on the servers must be at least 256 MB before AggressiveHeap can be used. The size of the initial heap is calculated based on the size of the physical memory and attempts to make maximal use of the physical memory for the heap (that is, the algorithms attempt to use heaps nearly as large as the total physical memory).

8.2.2 Recommended jvm.args Property Settings for Application Servers

It is highly recommended to set the same values for both –Xms and –Xmx. Table 6 lists the recommended settings.

Table 6: Recommended jvm.args Property Settings for Application Servers

System Size Memory Setting

Demo -Xms512m and -Xmx512m

Small -Xms512m and -Xmx512m

Production At least -Xms2048m and –Xmx2048m (Confirm this recommendation with performance testing)

Complete documentation for all JVM settings is available from the Sun Java Web site http://java.sun.com/.

8.3 Configuring Loader Server Memory (Recommended)

You can improve loader performance by configuring the Java Virtual Machine (JVM) memory settings. You can configure each loader individually. It is recommended that you balance the memory for loaders according to their throughput.

To configure the heap memory, edit the loader properties file for the loader process.

8.3.1 The SAP Configuration params Property

Each loader properties file contains a params property. By default, it is of the form:

com.comnitel.process.load_<instance-name>.params=<instance-name>

For example:


http://java.sun.com/

com.comnitel.process.load_nokiabss_oss31ed3.params=nokiabss_oss31ed3

The location for a loader's properties file is:

<WMCROOT>/conf/processes/processes-load_<loader>.properties

By default, the JVM heap memory setting for loaders is 1,536 MB (1.5 GB) for both maximum and minimum. You can modify the default settings by providing alternate values for the initial size of the memory allocation pool as follows:

com.comnitel.process.load_<instance-name>.params=<instance-name> <min> <max>

By default, the value is in bytes. Append the letter m or M to indicate megabytes, or g or G to indicate gigabytes. If you provide only one value, it becomes both minimum and maximum. For optimal performance, it is highly recommended to use identical settings for both.

For example, enter the following to set both the minimum and maximum memory to 2 GB:

com.comnitel.process.load_nokiabss_oss31ed3.params=nokiabss_oss31ed3 2g

Note: It is only possible to set loader process settings in this way. You cannot set other SAP processes with this mechanism.

Restart sapmgr after you change a process configuration file. As user virtuo, run the command:

$ sapmgr restart

Note: This action does not restart any of the services, such as loaders or the application server.

When changing the configuration of a running loader, you must restart the loader process to use the new settings as follows:

1. Run this command:

$ sap stop nokiabss_oss31ed3

2. Wait until the loader stops, and then run the following command:

$ sap start nokiabss_oss31ed3

8.3.2 Recommended JVM Memory Size Settings for Loader Servers

The amount of memory that you should allocate to each loader process depends on the throughput and size of files being handled by the loader. Low-volume processes could be set with a maximum of 1 GB. High-volume processes configured without multithreading should be set to at least 2 GB, and high-volume processes with multithreading set to at least 3 GB.

Table 7 lists the recommended settings for both maximum and minimum memory:

Table 7: Recommended JVM size settings for Loader servers

System Size Memory Setting

Demo 1g

Small 1526m

Production At least 2g (Confirm this recommendation with performance testing)


8.4 Checking the Time Zone Settings for the Report Scheduler

Check that the time zone settings for the report scheduler correct in the following location:

/etc/default/login

/etc/localtime

8.4.1 Setting the Time Zone

If the timezone is not set or is incorrectly set. Use the tz_admin tool to set or change the timezone.

For example:

tz_admin -addcurtzr <timezone_name>

For more information on setting time zones for the report scheduler, see Chapter 9 of the Tivoli Netcool Performance Manager: Administration Guide - Wireless Component.

8.5 Changing the Default Client Ports

The default ports used by the Tivoli Netcool Performance Manager client are as follows:

• HTTP server: 8080 • Alarm service: 4444 (required for the alarm window)

After installation, information for these ports is stored in these two files:

• $WMCROOT/conf/as/as-default.properties • $WMCROOT/as/server/default/deploy/jbossweb-tomcat55.sar/server.xml

The conf/as/as-default.properties file contains both port values. The $WMCROOT/as/server/default/deploy/jbossweb-tomcat55.sar/server.xml file contains the HTTP server port.

To change the default ports, update the port values in both files. After you make changes, stop and restart the application server.

Note: For the Tivoli Netcool Performance Manager client to work, these two ports must be open on any firewall between the server and the client PC.

8.6 Configuring a Multi-homed application server

A multi-homed server is a server with more than one IP address. If the Tivoli Netcool Performance Manager application server is multi-homed, a problem may occur when client alarm Java applets attempt to communicate with the Jboss server. Alarm applets are used in the Tivoli Netcool Performance Manager Alarms GUI applications.


Depending on the application server's configuration it may be the case that only one IP address is visible to the clients (alarm applets) on their IP range/subnet. If the RMI registry has bound the RMISEVER stub to an NIC that is not available to the client, the client will be unable to connect to the server host.

If this problem occurs, the RMISEVER must know what NIC/ IP address to use. That is, the IP address of the server that the clients can resolve. This can be configured using a JVM parameter:

1. Edit the following file:

/appl/virtuo/conf/as/jvm-default.ini

2. Add the following parameter:

Djava.rmi.server.hostname=%<ip address|subnet>%

Where: %<ip address|subnet>% is the IP address or subnet that the client can resolve.

8.7 Integrating IBM Tivoli Monitoring

IBM Tivoli Monitoring integration is an optional feature. The Tivoli Netcool Performance Manager installation procedure will not automatically configure the Tivoli Netcool Performance Manager ITM agents.

For information on installing ITM agents and integrating ITM with Tivoli Netcool Performance Manager, see the IBM Tivoli Netcool Performance Manager: IBM Tivoli Monitoring Integration Guide - Wireless Component.

For information on installing ITM, and additional information on deploying agents to a server, see the IBM Tivoli Monitoring: Installation and Setup Guide. For information on using and configuring ITM, see the IBM Tivoli Monitoring: User's Guide.

All IBM Tivoli Monitoring product documentation can be found at: http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?toc=/com.ibm.itm.doc/toc.xml


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?toc=/com.ibm.itm.doc/toc.xml

8.8 Integrating Tivoli Common Reporting

Tivoli Common Reporting integration is an optional feature. Tivoli Common Reporting is a reporting tool available to users of Tivoli products.

The Tivoli Netcool Performance Manager - Wireless component installation procedure will not automatically integrate Tivoli Common Reporting. This section provides an overview of the main prerequisites for integrating Tivoli Common Reporting with Tivoli Netcool Performance Manager - Wireless component.

8.8.1 Prerequisites

Prerequisites:

• Tivoli Common Reporting • Oracle client • LDAP configuration

8.8.2 Tivoli Common Reporting

Tivoli Common Reporting must be installed. There are two integration deployment scenarios:

• Tivoli Common Reporting is installed as part of the Tivoli Netcool Performance Manager - Wireline component installation.

• Standalone Cognos BI Server 8.4, Tivoli Common Reporting is installed as a standalone application.

For more information installing or upgrading Tivoli Common Reporting, see: Tivoli Common Reporting for Asset and Performance Management

To install Tivoli Common Reporting follow the instructions given in Tivoli Common Reporting for Asset and Performance Management. Installation should be performed as user root.

8.8.3 Oracle client

To connect Tivoli Common Reporting to the Wireless database an Oracle client must be installed. The Oracle client must be installed on the same server as Tivoli Common Reporting. A 32-bit Oracle client is installed with Tivoli Common Reporting.

After installation of the client the tnsnames.ora file must be updated to add a reference to the Wireless database. An entry called VTDB must be added to the tnsnames.ora file. The following is an example entry.

VTDB= (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 9.111.111.111)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = VTDB) ) )

A Wireless report when executed in Tivoli Common Reporting will search for the entry.


http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr_cog.doc/tcr_welcome.html




See Cognos Install Documentation Set Up Database Connectivity for the Reporting Database, for more information.

Oracle client can be downloaded from: http://www.oracle.com/technology/software/products/database/index.html

8.8.4 LDAP configuration

In order to manage all users from a single repository, you can use the LDAP instance created for the Tivoli Netcool Performance Manager - Wireless component installation.

8.8.4.1 Environment variable setup

In order to create a datasource connection to the Oracle database and Tivoli Common Reporting, the Oracle client library loading path must be set in your environment. The following instructions outline how this is done.

1. Stop Tivoli Common Reporting, for example:

/opt/IBM/tivoli/tipv2Components/TCRComponent/bin/stopTCRserver.sh server1 -user <tipuser> -password <tippassword>

2. Edit the startTCRserver.sh script to add the following variables:

ORACLE_HOME=/appl/oracle/product/10.2.0/db_1

LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$LD_LIBRARY_PATH

TNS_ADMIN=$ORACLE_HOME/network/admin/tnsnames.ora

The startTCRserver.sh script is located in:

/opt/IBM/tivoli/tipv2Components/TCRComponent/bin

3. Start Tivoli Common Reporting, for example:

/opt/IBM/tivoli/tipv2Components/TCRComponent/bin/startTCRserver.sh server1 -user <tipuser> -password <tippassword>

8.8.4.2 Single Tivoli Integrated Portal installation

Complete the steps in this section to configure LDAP on a single Tivoli Integrated Portal Installation.

For a multiple Tivoli Integrated Portal server installation, repeat the instructions in this section for each instance that is part of the distributed environment.

Before you begin

You should have the following information:

• Location of the Tivoli Integrated Portal installation directory, by default: /opt/IBM/tivoli

• LDAP administration username and password • LDAP properties:

• LDAP host name • Directory server port number • LDAP base entry • User suffix • Group suffix


http://publib.boulder.ibm.com/infocenter/c8bi/v8r4m0/index.jsp?topic=/com.ibm.swg.im.cognos.inst_cr_winux.8.4.0.doc/inst_cr_winux_id5775SetUpDatabaseConnectivityfortheRepo.html

http://www.oracle.com/technology/software/products/database/index.html

• Organization container suffix

Refer to your LDAP administrator for the values for these LDAP properties.

Complete the followings steps to configure LDAP on a single Tivoli Integrated Portal installation.

1. Open the /opt/IBM/tivoli/tipv2/profiles/TIPProfile/bin/ldap.properties file in an editor of your choice.

2. Ensure the following properties are set:

Property Value

LDAPRepositoryName PMWLDAPInstance

LDAPServerType IDS6

LDAPHost Fully qualified hostname. For example, "server.ibm.com" LDAPPort Directory server port number: 1389

SSLEnabled false

SSLConfiguration NodeDefaultSSLSettings

LDAPBindDN "cn\=Directory Manager"

LDAPBaseEntry LDAP base entry. For example: "dc\=ibm,dc\=com"

VMMRealmName TIPRealm

GroupEntityType Group

GroupSuffix Group suffix: For example: "ou\=Groups,dc\=ibm,dc\=com"

OrgContainerEntityType OrgContainer

OrgContainerSuffix Organization container suffix. For example: "ou\=Development,dc\=ibm,dc\=com"

UserEntityType PersonAccount

UserSuffix User suffix. For example: "ou\=People,dc\=ibm,dc\=com"

Ensure all the properties are uncommented.

3. Set the TIP_HOME environment variable:

export TIP_HOME=/opt/IBM/tivoli/tipv2

4. Change directory:

cd /opt/IBM/tivoli/tipv2/profiles/TIPProfile/bin

5. Enable the new settings:

./configureVMMLDAP.sh $TIP_HOME <ldap_password> ldap.properties

6. Restart the Tivoli Integrated Portal application server:

./stopServer.sh server1 -username <tipadmin user> -password <tipadmin password>

./startServer.sh server1 -username <tipadmin user> -password <tipadmin password>

7. Login to Tivoli Integrated Portal, for example:

https://<servername>:<port>/ibm/console/logon.jsp

8. Enter the Tivoli Integrated Portal administration username and password.

9. Expand Users and Groups.

10. Click Manage Users, and click Search.


Users from Tivoli Netcool Performance Manager should be displayed, similarly Groups will be displayed if any exist.

8.8.4.3 Create a data source

To verify a connection with the PMW database you must create a data source. A data source connection supplies the information that Tivoli Common Reporting needs to connect to a database.

1. Open your browser and in the address box type http://<servername>:<port>/ibm/console/logon.jsp and press Enter.

2. Enter your Tivoli Integrated Portal username and the password.

3. In the Navigation frame on the left expand Reporting and click Common Reporting.

4. In the Work with reports window on the right choose IBM Cognos Administration from the Launch drop-down list.

5. Go to the Configuration tab, and open the Data Source Connections section.

6. Create a new Data Source by clicking the new button .

The New Data Source wizard is displayed.

7. Enter a name of your choice and click Next.

8. Select Oracle as the connection type.

9. For Isolation Level leave Use the default object gateway checked. Click Next.

The isolation level specifies how transactions that modify the database are handled.

10. Enter the SQL*Net connect string, and enter a username and password for the database connection.

The SQL*Net connect string must match exactly the Net Service Name defined in the tnsnames.ora file configured in the Oracle Client on the server running Tivoli Common Reporting.


11. Click Test the connection to verify you can successfully connect to the database. 12. Click the Test button.

A Result status of Succeeded should appear. Close the page.

13. Close any remaining pages and then click Finish to complete the connection.


Chapter 9. Starting Tivoli Netcool Performance Manager

Start Tivoli Netcool Performance Manager after installation.

9.1 Reboot the Server

Reboot the server to ensure all the Tivoli Netcool Performance Manager processes start automatically and correctly.

Before rebooting a server, stop all processes by running the following command as user virtuo:

$ sap stop -f

To reboot the server, run the following commands as user root on each of the Tivoli Netcool Performance Manager servers:

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

# shutdown -r now

Important: Distributed systems only. In a distributed system, you must reboot the Tivoli Netcool Performance Manager servers in the following order: database server, directory server, application server and loader servers.

9.2 Process Checks

Check the system status to see if processes are running correctly as follows:

On Solaris 10, run this single command as user root to check the status of the system:

# svcs -x "application/virtuo*"

Sample output:

svc:/application/virtuo/sap-na:na (Virtuo SAP server)

State: online since Tue Sep 30 16:39:31 2008

See: /var/svc/log/application-virtuo-sap-na:na.log

Impact: None.


svc:/application/virtuo/sapmon-na:na (Virtuo SAP monitor)


See: /var/svc/log/application-virtuo-sapmon-na:na.log

Impact: None.

svc:/application/virtuo/tds-na:na (TNPMW LDAP server)


See: /var/svc/log/application-virtuo-tds-na:na.log

Impact: None.

svc:/application/virtuo/sapmgr-na:na (Virtuo SAP manager)


See: /var/svc/log/application-virtuo-sapmgr-na:na.log

Impact: None.

svc:/application/virtuo/database-na:global (Virtuo Database)


See: /var/svc/log/application-virtuo-database-na:global.log

Impact: None.

On Linux, pass the status command to the init.d services:

# service dboravirtuo status

# service tdsna status

# service sapmonvirtuo status

# service sapmgrvirtuo status

# service sapvirtuo status

Sample output:

# service dboravirtuo status

Database listener is running.

Database instance vtdb is running.

# service tdsna status

TDS LDAP server is running

TDS admin server is running

# service sapmonvirtuo status

sapmon process running

# service sapmgrvirtuo status

sapmgr process running

# service sapvirtuo status

NAME STATE SINCE

as STARTED 17:21:28

asd STARTED 17:25:04




load_ericssonbss_r10 STARTED 17:26:39

load_nokiabss_oss31ed3 STARTED 17:26:44

load_motorolabss_gsr7 STARTED 17:26:49

load_motorolautran_usr10 STARTED 17:26:54

load_ericssonutran_r30 STARTED 17:26:59


9.3 Complete Startup of Netcool Performance Manager

Important: Distributed systems only. In a distributed system, perform a complete startup on the server hosting the application component.

Run the following commands to ensure SAP process management is running, and then start the remaining Tivoli Netcool Performance Manager processes.

Run the following commands as user root:

svcadm enable sapmon-na


service sapmonvirtuo start

service sapmgrvirtuo start

Run the following commands as user virtuo:

sap disp

Run the following command as user root:

svcadm enable sap-na

service sapvirtuo start

The location of the process log files is determined by the WMCLOGDIR setting in the $WMCROOT/conf/environment/default.properties file.

Ensure that no exceptions have occurred in these files. If the process has started successfully, each process log file should return the line Process Startup done when it has started successfully.


Appendix A: Installation Output

This appendix details example output associated with the installation of all the packages on a standalone Tivoli Netcool Performance Manager server. The output shown is for an interactive installation.

Script started on Wed Jun 03 17:38:17 2009

# ksh pmw_install -wmcr /appl/virtuo

Making PMW top-level directory: /appl/virtuo

Making software archive directories: under /appl/virtuo/admin/software

Looking for bootstrap package

Found vallent-vt-common-PMW9.2.0.38.tar.gz

Extracting and running bootstrap package

Looking for bootstrap script

Running vallent-vt-common.install

Copyright 2008 IBM Ireland PDL, All Rights Reserved

This installation script will install the Performance Management for Wireless common

software version PMW9.2.0.38 on your system.

Do you wish to continue? yes

� �[63;1H [KInternational Program License Agreement

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

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

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

Do you agree with the terms of this license? yes

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 profile

Setting up virtuo User Profile

....doneCompleted Virtuo Software Installation

Logs can be seen in pmw_install.log

Installation is complete.What Type of Virtuo System Are you Installing?

1. Virtuo Framework (excluding Gateways and Techpacks)







7. Exit PMW Install

---->1

Checking packages: jre ant java-libs as-core core sap njloader ds-conf db-install db-conf


* /appl/vallent-vt-jre-PMW9.2.0.38.tar.gz

* /appl/vallent-vt-ant-PMW9.2.0.38.tar.gz

* /appl/vallent-vt-java-libs-PMW9.2.0.38.tar.gz

* /appl/vallent-vt-as-core-PMW9.2.0.38.tar.gz

* /appl/vallent-vt-core-PMW9.2.0.38.tar.gz

* /appl/vallent-vt-sap-PMW9.2.0.38.tar.gz

* /appl/vallent-vt-njloader-PMW9.2.0.38.tar.gz

* /appl/vallent-vt-ds-conf-PMW9.2.0.38.tar.gz

* /appl/vallent-vt-db-install-PMW9.2.0.38.tar.gz

* /appl/vallent-vt-db-conf-PMW9.2.0.38.tar.gz


Installing

jre (PMW9.2.0.38) ... ok

ant (PMW9.2.0.38) ... ok

java-libs (PMW9.2.0.38) ... ok

as-core (PMW9.2.0.38) ... ok

core (PMW9.2.0.38) ...

Sun Microsystems Inc. SunOS 5.10 Generic January 2005

You have new mail.Please, Verify Environment Settings



3. Change WMCHOST=<server_name>-zone2.cork.ie.ibm.com

4. Change VTDBHOST=<server_name>-zone2.cork.ie.ibm.com

5. Change LDAPHOST=<server_name>-zone2.cork.ie.ibm.com

6. Change SMTP_HOST=<server_name>-zone2.cork.ie.ibm.com

7. Change SMTP_PORT=25

8. Change REPLY_ADDRESS=virtuo@<server_name>-zone2.cork.ie.ibm.com

9. Change SERVER_IP_ADDRESS=9.162.124.162

10. Change SHORT_IP_ADDRESS=9.162.124

11. Change WMCROOT=/appl/virtuo

12. Change WMCLOGDIR=/appl/virtuo/logs/

13. Change WMCVARDIR=/appl/virtuo/var/

14. Change LDAPPORT=1389

15. Change LDAPROOT=dc=cork,dc=ie,dc=ibm,dc=com

16. Change LDAP_PASSWORD=<password>

17. Change OPERATOR=Company1

18. Change ORACLEPORT=1521

19. Change VTDBSID=vtdb

20. Change VTDB_USERNAME=virtuo

21. Change VTDB_PASSWORD=<password>


22. Change SAPMONPORT=9009

23. Change OMPORT=9008

24. Change ASHTTPPORT=8080

25. Change ASREDIRPORT=8443

26. Change ASAJPPORT=8086

27. Change ASWEBSRVPORT=8083

28. Change ASBRIDGEPORT=10091

29. Change ASNSPORT=1099

30. Change ASJRMPINVOKPORT=4444

31. Change ASPOOLINVOKPORT=4445

32. Change ASRMIPORT=1098

33. Change ASUIL2PORT=8093

34. Change ASHSQLPORT=1701

35. Change ORBPORT=3528

36. Change ORBSSLPORT=3529

---->1

Configuring of /appl/virtuo files ...

....done

ok

sap (PMW9.2.0.38) ... ok

njloader (PMW9.2.0.38) ...


You have new mail.Please, Verify Environment Settings



3. Change LDRHOST=<server_name>-zone2.cork.ie.ibm.com


5. Change VTDBHOST=<server_name>-zone2.cork.ie.ibm.com

6. Change ORACLEPORT=1521

7. Change VTDBSID=vtdb

8. Change VTDB_USERNAME=virtuo

9. Change VTDB_PASSWORD=<password>

10. Change WMCROOT=/appl/virtuo



13. Change SAPMONPORT=9009

14. Change OMPORT=9008


---->1


....done

ok

ds-conf (PMW9.2.0.38) ... ok

db-install (PMW9.2.0.38) ... ok

db-conf (PMW9.2.0.38) ...


You have new mail.Please, Verify Environment Settings 1. Accept Variable Values below







7. Change MSTRCACHE_RMI=9876

8. Change ALRMCACHE_RMI=9877

---->1


....done

ok

All packages installed successfullyDetails in pmw_install.logWould you like to perform task JBOSS_INSTALL ? [yes/no] >yes


You have new mail.


---->

Deploying JBoss 4.0.3SP1...

Buildfile: /appl/virtuo/admin/common/install/scripts/build.xmlinit:


[echo] JBoss Location=/applfind-archive:expand-tar-gz:



[untar] Expanding: /appl/jboss-4.0.3SP1.tar.gz into /appl/virtuoexpand-tar-bz2:expand-zip:all:



[move] Moving 5 files to /appl/virtuo/as/server/defaultinit:


[echo] JBoss Location=/applcopy-libs:

[copy] Copying 3 files to /appl/virtuo/as/server/default/lib

[copy] Copying 10 files to /appl/virtuo/lib/tp

[delete] Deleting directory /appl/virtuo/jboss-4.0.3SP1init:


[echo] JBoss Location=/applfix-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/tempinit:


[echo] JBoss Location=/applsignjarpmw:

[echo] Signing JBoss client jar

[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.earBUILD SUCCESSFUL

Total time: 30 seconds




You have new mail.

Using local LDAP server, port 1389... OK.

Please enter the password for 'Directory Manager', the Directory Server User [<password>]:Please enter the password for 'SysAdmin', the Directory Server User [<password>]:Directory Server "SysAdmin" user password set to "<password>" DS schema installed.


Please, Enter your Database SID (8 character maximum): [vtdb]

---->


Please, Enter the full path of the PMW database template: [/appl/virtuo/admin/oracle/conf/vtdb.dbt]

---->/appl/virtuo/admin/oracle/conf/ vtdb_small.dbt^[[D…../vtdb_small.dbt

PMW database will be created using template /appl/virtuo/admin/oracle/conf/vtdb_small.dbt


---->


---->

Creating and starting Oracle instance

1% complete

2% complete

3% complete

7% complete

Creating database files

8% complete

9% complete

10% complete

11% complete

12% complete

13% complete

14% complete

15% complete

Creating data dictionary views

17% complete

20% complete

22% complete

23% complete

24% complete

25% complete

26% complete

27% complete

32% complete

34% complete

35% complete

37% complete

39% complete

Adding Oracle JVM


40% complete

52% complete

63% complete

75% complete

78% complete

Completing Database Creation

80% complete

82% complete

85% complete

91% complete

98% complete

100% complete

Look at the log file "/appl/oracle/product/10.2.0/db_1/cfgtoollogs/dbca/vtdb/vtdb0.log" for further details.

Sun Microsystems Inc. SunOS 5.10 Generic January 2005Wed Jun 03 18:25:31 IST 2009 Oracle Net Configuration Assistant

Parsing command line arguments:

Parameter "silent" = true

Parameter "responsefile" = /tmp/netca10gR2_vtdb.rsp

Parameter "log" = /tmp/netca.log

Done parsing command line arguments.

Oracle Net Services Configuration:

Configuring Listener:LISTENER

Listener configuration complete.

Oracle Net Listener Startup:

Running Listener Control:

/appl/oracle/product/10.2.0/db_1/bin/lsnrctl start LISTENER

Listener Control complete.

Listener started successfully.

Default local naming configuration complete.

Created net service name: vtdb

Profile configuration complete.

Oracle Net Services configuration successful. The exit code is 0Importing /appl/virtuo/admin/oracle/install/startup/database-na.xml into SMF repository... done

Waiting for DB listener for vtdb

Running post-install procedures for vtdb database.

Making post-install changes

Sun Microsystems Inc. SunOS 5.10 Generic January 2005SQL*Plus: Release 10.2.0.4.0 - Production on Wed Jun 3 18:26:44 2009Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected to:

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

With the Partitioning, Data Mining and Real Application Testing optionsSQL> 2

System altered.SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

With the Partitioning, Data Mining and Real Application Testing options

Sun Microsystems Inc. SunOS 5.10 Generic January 2005SQL*Plus: Release 10.2.0.4.0 - Production on Wed Jun 3 18:26:45 2009Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected to:

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production


With the Partitioning, Data Mining and Real Application Testing optionsSQL> 2 3 4 5 6 7 8 9 10 11 12 13 14

PL/SQL procedure successfully completed.SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

With the Partitioning, Data Mining and Real Application Testing options

Creating OEM repository and console accessible by port 1158

Sun Microsystems Inc. SunOS 5.10 Generic January 2005STARTED EMCA at Jun 3, 2009 6:26:46 PMEM Configuration Assistant, Version 10.2.0.1.0 Production

Copyright (c) 2003, 2005, Oracle. All rights reserved.Jun 3, 2009 6:26:47 PM oracle.sysman.emcp.EMConfig perform

INFO: This operation is being logged at /appl/oracle/product/10.2.0/db_1/cfgtoollogs/emca/vtdb/emca_2009-06-03_06-26-46-PM.log.

Jun 3, 2009 6:26:50 PM oracle.sysman.emcp.EMReposConfig createRepository

INFO: Creating the EM repository (this may take a while) ...

Jun 3, 2009 6:30:16 PM oracle.sysman.emcp.EMReposConfig invoke

INFO: Repository successfully created

Jun 3, 2009 6:30:22 PM oracle.sysman.emcp.util.DBControlUtil secureDBConsole

INFO: Securing Database Control (this may take a while) ...

Jun 3, 2009 6:30:56 PM oracle.sysman.emcp.util.DBControlUtil secureDBConsole

INFO: Database Control secured successfully.

Jun 3, 2009 6:30:56 PM oracle.sysman.emcp.util.DBControlUtil startOMS

INFO: Starting Database Control (this may take a while) ...

Jun 3, 2009 6:32:36 PM oracle.sysman.emcp.EMDBPostConfig performConfiguration

INFO: Database Control started successfully

Jun 3, 2009 6:32:36 PM oracle.sysman.emcp.EMDBPostConfig performConfiguration

INFO: >>>>>>>>>>> The Database Control URL is https://<server_name>-zone2.cork.ie.ibm.com:1158/em <<<<<<<<<<<

Enterprise Manager configuration completed successfully

FINISHED EMCA at Jun 3, 2009 6:32:36 PM


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

Please, Enter the Virtuo Database SID: [vtdb]

---->


Please, Enter the Database sys user password: [Password]

---->


Please, Enter the Database virtuo user password: [<password>]

---->



Creating database schema 'core' in SID 'vtdb'. This may take several minutes ...

.

..


.... Log file is located in /appl/virtuo/admin/oracle/schema/core/install_schema.log

.... Database Schema 'core' Creation completed


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



---->



---->sys



----><password>

Database user sys password is set to "<password>"

Please, Enter the Database user virtuo name: [virtuo]

---->


Please, Enter the Database user virtuo password: [<password>]

---->




|..../arguments: '-user' 'virtuo/***@vtdb' '-verbose' '-resolve' '/appl/virtuo/admin/oracle/loadedJars/lib/na-traffic-engineering-intf.jar' '/appl/virtuo/admin/oracle/loadedJars/lib/na-traffic-engineering-impl.jar'

……|creating : resource META-INF/MANIFEST.MF

loading : resource META-INF/MANIFEST.MF

created : CREATE$JAVA$LOB$TABLE

creating : resource copyright.txt

loading : resource copyright.txt

creating : resource META-INF/INDEX.LIST

loading : resource META-INF/INDEX.LIST

..../creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/constants/TrafficEngineeringErrorConstants

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/constants/TrafficEngineeringErrorConstants

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionAPI/TECWrapper

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionAPI/TECWrapper

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionAPI/TECWrapperNullHandler

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionAPI/TECWrapperNullHandler

identical: META-INF/MANIFEST.MF

creating : resource copyright.txt

loading : resource copyright.txt

creating : resource META-INF/INDEX.LIST

loading : resource META-INF/INDEX.LIST

creating : class com/ibm/tivoli/tnpmw/trafficengineering/exception/TrafficEngineeringException

loading : class com/ibm/tivoli/tnpmw/trafficengineering/exception/TrafficEngineeringException

identical: com/ibm/tivoli/tnpmw/trafficengineering/function/constants/TrafficEngineeringErrorConstants

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/AbstractKaufmanFunctions$kaufman_roberts


loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/AbstractKaufmanFunctions$kaufman_roberts

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/AbstractKaufmanFunctions

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/AbstractKaufmanFunctions

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/AbstractTECFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/AbstractTECFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/CIRCFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/CIRCFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/CRITFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/CRITFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/ENGSETFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/ENGSETFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/GOSFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/GOSFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanAllCFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanAllCFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanMaxPBFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanMaxPBFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanMinCFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanMinCFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanPBFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanPBFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/NumberToStringFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/NumberToStringFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/PercentFailFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/PercentFailFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/PercentOKFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/PercentOKFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/TC4Function

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/TC4Function

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/TOFFFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/TOFFFunction

creating : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/ThresholdDivFunction

loading : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/ThresholdDivFunction

skipping : resource META-INF/MANIFEST.MF

skipping : resource copyright.txt


skipping : resource META-INF/INDEX.LIST

resolving: class com/ibm/tivoli/tnpmw/trafficengineering/function/constants/TrafficEngineeringErrorConstants

\resolving: class com/ibm/tivoli/tnpmw/trafficengineering/function/functionAPI/TECWrapper

resolving: class com/ibm/tivoli/tnpmw/trafficengineering/function/functionAPI/TECWrapperNullHandler

skipping : resource META-INF/MANIFEST.MF

skipping : resource copyright.txt

skipping : resource META-INF/INDEX.LIST

resolving: class com/ibm/tivoli/tnpmw/trafficengineering/exception/TrafficEngineeringException

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/constants/TrafficEngineeringErrorConstants

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/AbstractKaufmanFunctions$kaufman_roberts

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/AbstractKaufmanFunctions

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/AbstractTECFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/CIRCFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/CRITFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/ENGSETFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/GOSFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanAllCFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanMaxPBFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanMinCFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/KaufmanPBFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/NumberToStringFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/PercentFailFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/PercentOKFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/TC4Function

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/TOFFFunction

skipping : class com/ibm/tivoli/tnpmw/trafficengineering/function/functionImpl/ThresholdDivFunction

.... Loading JAR Files To 'virtuo' Schema Is Completed

.... Starting Importing Stored Outline To 'virtuo' Schema

Importing outline to database schema 'virtuo' in 'vtdb' database...Import: Release 10.2.0.4.0 - Production on Thu Jun 4 09:04:30 2009Copyright (c) 1982, 2007, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

With the Partitioning, Data Mining and Real Application Testing optionsExport file created by EXPORT:V10.02.01 via conventional path

import done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set

import server uses AL32UTF8 character set (possible charset conversion)

export client uses WE8MSWIN1252 character set (possible charset conversion)

. importing OUTLN's objects into OUTLN

. . importing table "OL$" 1 rows imported

. . importing table "OL$HINTS" 35 rows imported


. . importing table "OL$NODES" 6 rows imported

Import terminated successfully without warnings.File created.

System altered.

System altered.



Configuring core cronjobs.......What Type of PMW System Are you Installing ?

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

Please select the type of PMW System you are installing by


All Inclusive (1)

Application (2)

Loader (3)


Database (5)

Gateway (6)

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

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

1


(Enter . if unknown)Please enter the vtdb Database Archive Directory [/oradump/vtdb]:

(Enter . if unknown)Please enter the Directory Server log Directory [/appl/ldap/idsslapd-idsinst/logs]:

(Enter . if unknown)Please enter the PMW Log Directory [/appl/virtuo/logs]:

(Enter . if unknown)Please enter the PMW Archive Logs Directory [/data/trace_archive1]:


Setting up CRON environment ...Filtering old cronjobs ...

.... DoneSetting up root cronjobs ...Finished setting up roots cronjobs ....

Setting up user cronjobs ...Finished setting up 's crontab ....

Restarting Cron ...

.... cron daemon stopped

.... cron daemon startedPlease view pmw_install.log for install detailsWould you like to perform task GATEWAYS_INSTALL ? [yes/no] >yes


You have new mail.

Checking packages: /appl/vallent-vt-gways-vallent-PMW9.2.0.38.tar.gz


* /appl/vallent-vt-gways-vallent-PMW9.2.0.38.tar.gz


Installing

gways-vallent (PMW9.2.0.38) ... ok


Creating gateway log directory: /appl/virtuo/logs/gwaysDetails in pmw_install.logWould you like to perform task TECHPACKS_INSTALL ? [yes/no] >yes


You have new mail.



Checking packages: vallent-vt-Neutral_Core_GOM vallent-vt-Neutral_GSM_BSS_NSS_GOM vallent-vt-Neutral_GPRS_UMTS_CN_GOM vallent-vt-Neutral_GPRS_BSS_GOM vallent-vt-Neutral_UMTS_UTRAN_GOM vallent-vt-Neutral_GSM_Core vallent-vt-Ericsson_GSM_BSS vallent-vt-Nokia_GSM_BSS vallent-vt-Motorola_GSM_BSS vallent-vt-Motorola_UMTS_UTRAN vallent-vt-Ericsson_UMTS_UTRAN



* /appl/vallent-vt-Neutral_GSM_BSS_NSS_GOM-1.0.tar.gz

* /appl/vallent-vt-Neutral_GPRS_UMTS_CN_GOM-1.0.tar.gz

* /appl/vallent-vt-Neutral_GPRS_BSS_GOM-1.0.tar.gz

* /appl/vallent-vt-Neutral_UMTS_UTRAN_GOM-1.0.tar.gz

* /appl/vallent-vt-Neutral_GSM_Core-1.0.tar.gz

* /appl/vallent-vt-Ericsson_GSM_BSS-1.0.tar.gz

* /appl/vallent-vt-Nokia_GSM_BSS-1.0.tar.gz

* /appl/vallent-vt-Motorola_GSM_BSS-1.0.tar.gz

* /appl/vallent-vt-Motorola_UMTS_UTRAN-1.0.tar.gz

* /appl/vallent-vt-Ericsson_UMTS_UTRAN-1.0.tar.gz


Installing


Neutral_GSM_BSS_NSS_GOM (1.0) ... ok

Neutral_GPRS_UMTS_CN_GOM (1.0) ... ok

Neutral_GPRS_BSS_GOM (1.0) ... ok

Neutral_UMTS_UTRAN_GOM (1.0) ... ok

Neutral_GSM_Core (1.0) ... ok

Ericsson_GSM_BSS (1.0) ... ok

Nokia_GSM_BSS (1.0) ... ok

Motorola_GSM_BSS (1.0) ... ok

Motorola_UMTS_UTRAN (1.0) ... ok


All packages installed successfullyDetails in pmw_install.logSun Microsystems Inc. SunOS 5.10 Generic January 2005

You have new mail.

Starting application server...


You have new mail.Licensed Materials - Property of IBM5724W86(C) Copyright IBM Corp. 2005, 2009 All Rights Reserved.Waiting for appserver...

Thu Jun 4 09:10:17 IST 2009: as is at state exec. Waiting for state STARTED



Thu Jun 4 09:11:37 IST 2009 as now up, clock started 091002000, now 091137000

Appserver ready.



You have new mail.Licensed Materials - Property of IBM5724W86(C) Copyright IBM Corp. 2006, 2009 All Rights Reserved.09:12:04,407 INFO [SystemInit] Login...

09:12:29,166 INFO [SystemInit] Operation Succeeded



You have new mail.


Buildfile: /appl/virtuo/admin/techpacks/build.xmlcopyright-info:

[echo] Licensed Materials - Property of IBM

[echo] 5724W86

[echo] (C) Copyright IBM Corp. 2005, 2009 All Rights Reserved.set-install-mode-from-env:set-default-install-mode:set-install-mode:init:

[wmcInit] 09:12:39,052 [main] DEBUG logging - Created Logging Directory : /appl/virtuo/logs/vmmapply:

[applyTechPacks] About to install modules. View logs for installation results.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Neutral_Core_GOM_1.0.properties does not exist!

[applyTechPacks] Do you want to continue with techpack default tablespace settings? [y|n]

y

[applyTechPacks] Using default tablespace settings for techpack Neutral Core GOM[applyTechPacks] No report templates to apply.

[applyTechPacks] elapsedTime for Install = 7155

[applyTechPacks] Module Neutral_Core_GOM 1.0 processed in under 8 seconds.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Neutral_GSM_BSS_NSS_GOM_1.0.properties does not exist!


y

[applyTechPacks] Using default tablespace settings for techpack Neutral GSM BSS/NSS GOM[applyTechPacks] No report templates to apply.


[applyTechPacks] Module Neutral_GSM_BSS_NSS_GOM 1.0 processed in under 36 seconds.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Neutral_GPRS_UMTS_CN_GOM_1.0.properties does not exist!


y

[applyTechPacks] Using default tablespace settings for techpack Neutral GPRS/UMTS CN GOM[applyTechPacks] No report templates to apply.


[applyTechPacks] Module Neutral_GPRS_UMTS_CN_GOM 1.0 processed in under 16 seconds.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Neutral_GPRS_BSS_GOM_1.0.properties does not exist!


y

[applyTechPacks] Using default tablespace settings for techpack Neutral GPRS BSS GOM[applyTechPacks] No report templates to apply.


[applyTechPacks] Module Neutral_GPRS_BSS_GOM 1.0 processed in under 28 seconds.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Neutral_UMTS_UTRAN_GOM_1.0.properties does not exist!


y

[applyTechPacks] Using default tablespace settings for techpack Neutral UMTS UTRAN GOM[applyTechPacks] No report templates to apply.


[applyTechPacks] Module Neutral_UMTS_UTRAN_GOM 1.0 processed in under 34 seconds.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Neutral_GSM_Core_1.0.properties does not exist!


y

[applyTechPacks] Using default tablespace settings for techpack Neutral GSM Core[applyTechPacks] elapsedTime for Install = 188372


[applyTechPacks] Module Neutral_GSM_Core 1.0 processed in under 4 minutes.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Ericsson_GSM_BSS_1.0.properties does not exist!


y

[applyTechPacks] Using default tablespace settings for techpack Ericsson GSM BSS[applyTechPacks] elapsedTime for Install = 291366

[applyTechPacks] Module Ericsson_GSM_BSS 1.0 processed in under 5 minutes.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Nokia_GSM_BSS_1.0.properties does not exist!


y

[applyTechPacks] Using default tablespace settings for techpack Nokia GSM BSS[applyTechPacks] elapsedTime for Install = 283792

[applyTechPacks] Module Nokia_GSM_BSS 1.0 processed in under 5 minutes.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Motorola_GSM_BSS_1.0.properties does not exist!


y

[applyTechPacks] Using default tablespace settings for techpack Motorola GSM BSS[applyTechPacks] elapsedTime for Install = 289938

[applyTechPacks] Module Motorola_GSM_BSS 1.0 processed in under 5 minutes.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Motorola_UMTS_UTRAN_1.0.properties does not exist!


y

[applyTechPacks] Using default tablespace settings for techpack Motorola UMTS UTRAN[applyTechPacks] elapsedTime for Install = 134208

[applyTechPacks] Module Motorola_UMTS_UTRAN 1.0 processed in under 3 minutes.[applyTechPacks] WARNING: Tablespace properties file /appl/virtuo/conf/vmm/tablespace_Ericsson_UMTS_UTRAN_1.0.properties does not exist!


y

[applyTechPacks] Using default tablespace settings for techpack Ericsson UMTS UTRAN[applyTechPacks] elapsedTime for Install = 248923

[applyTechPacks] Module Ericsson_UMTS_UTRAN 1.0 processed in under 5 minutes.

[delete] Deleting: /appl/virtuo/admin/techpacks/new_techpacksBUILD SUCCESSFUL




You have new mail.Licensed Materials - Property of IBM5724W86(C) Copyright IBM Corp. 2005, 2009 All Rights Reserved.asd exec

asd STARTED

nc_cache exec

nc_cache STARTED

alarm_cache exec

alarm_cache init

alarm_cache starting

alarm_cache STARTED

load_ericssonbss_r10 exec

load_ericssonbss_r10 STARTED

load_nokiabss_oss31ed3 exec


load_nokiabss_oss31ed3 STARTED

load_motorolabss_gsr7 exec

load_motorolabss_gsr7 STARTED

load_motorolautran_usr10 exec

load_motorolautran_usr10 STARTED

load_ericssonutran_r30 exec

load_ericssonutran_r30 STARTEDWould you like to perform task ENCODE_PASSWDS ? [yes/no] >yesReplacing all passwords with encoded passwords... Encoding values in /appl/virtuo/conf/as/as-default.properties









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

Enabling sap...

Done.

....

script done on Thu Jun 04 09:42:33 2009


Appendix B: Log file errors

Oracle installation

Checking for noexec_user_stack=1; found no entry. Failed

The Oracle Installation log output is found in:

/var/install/logs/oracle10g_install_<PID>.log

Following the installation of Oracle, the following error may be seen in the Oracle Installation log.

Checking for noexec_user_stack=1; found no entry. Failed

This error can be safely ignored.

Performing check for SwapSpace

The Oracle Inventory log output is found in:

/appl/oracle/product/oraInventory/logs/oraInstall<timestamp>.out

Following the installation of Oracle, the following error may be seen in the Inventory log.

Performing check for SwapSpace

Checking available swap space requirements ...

Expected result: <size>MB

Actual Result: <size>MB

Check complete. The overall result of this check is: Failed <<<<

This error can be safely ignored.


Appendix C: Dependency Checker errors

GYMWI0001E Directories missing from root user PATH The following directories are missing from the root user PATH: <missing_dirs> You must ensure that the root user profile is sourced before running 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 configured You must set up a domain name on the server and ensure the fully qualified hostname is valid ------------------------------------------------------------- GYMWI0003E Hostname <FQDN> resolves to loopback IP address x.x.x.x - must be a real IP address The 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 Only Linux and SunOS (Solaris) are supported ------------------------------------------------------------- GYMWI0006E SunOS version <OS_VER> is not supported. Must be 5.10 Solaris 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 release level for <OS> ------------------------------------------------------------- GYMWI0010E Unable to determine release level for <OS> from HW_REL: <HW_REL> ------------------------------------------------------------- GYMWI0011E HW_REL for <OS> is <HW_REL>: Required level is 8/07 You must install the latest recommended patch cluster ------------------------------------------------------------- GYMWI0012E Processor type <PROC_TYPE> is not supported for <OS> SunOS 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.1 or later ------------------------------------------------------------- GYMWI0016E <dir> is not a directory -------------------------------------------------------------


GYMWI0017E Insufficient space on <fs> partition. Space required on this partition: KB Space available: KB The following required directories are mounted on this partition: ------------------------------------------------------------- GYMWI0018E One or more required <OS> packages not installed Missing 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>: ------------------------------------------------------------- GYMWI0052E ERROR: invalid package release for <pkg>: ------------------------------------------------------------- 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 _.WE8ISO8859P1 ------------------------------------------------------------- GYMWI0031E Installed Oracle version is invalid ------------------------------------------------------------- GYMWI0032E Oracle oneoff patches not installed


The 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 file DB creation may fail if this file has invalid contents. ------------------------------------------------------------- GYMWI0046E ${pkg_count} versions of ${_core_pkg} found There can only be 1 version of each package in ${_pkg_dir} ------------------------------------------------------------- GYMWI0047E TNPM core packages not found The following core packages could not be found: ${missing_pkgs} ------------------------------------------------------------- GYMWI0053E JBoss archive not found The JBoss 4.0.3 SP1 package should be located in ${BASE_DIR} ------------------------------------------------------------- GYMWI0046E ${pkg_count} versions found There can only be 1 version of each package in ${_pkg_dir} ------------------------------------------------------------- GYMWI0048E TDS/DB2 packages not found The following TDS/DB2 packages could not be found: -------------------------------------------------------------


Notices This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in all countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing IBM Corporation North Castle Drive Armonk NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome Minato-ku Tokyo 106-0032 Japan.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the products and/or the programs described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation 5300 Cork Airport Business Park Kinsale Road Cork Ireland.

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 material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

IBM, the IBM logo and ibm.com are trademarks of International 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 and trademark information " at www.ibm.com/legal/copytrade.shtml.

• Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

• Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

.


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

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

• Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft

Corporation in the United States, other countries, or both. • Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. • UNIX is a registered trademark of The Open Group in the United States and other countries. • Other company, product or service names may be trademarks or service marks of others.


®

Printed in the Republic of Ireland.

Documents

Tivoli Netcool Performance Manager: Installation Guide ... · PDF fileNetcool Performance Manager 1.3.1 Document Revision R2E1 Tivoli Netcool Performance Manager: Installation Guide