TIBCO ...TIBCO ActiveMatrix Service Performance Manager Installation |v Preface TIBCO ActiveMatrix® Service Performance Manager is an enterprise software

TIBCO ActiveMatrix®

Service Performance Manager

InstallationSoftware Release 1.3.0March 2010

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIB, TIBCO, TIBCO ActiveMatrix, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO BusinessWorks are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 2008-2010 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Changes from the Previous Release of TIBCO ActiveMatrix Service Performance Manager Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTIBCO ActiveMatrix® Service Performance Manager Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

How to Contact TIBCO Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Installation Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Supported Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15System Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Installer Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Installer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Supported Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Supported Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Recommended Email Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Supported Services for Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing Hibernate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installing TIBCO ActiveMatrix Service Performance Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Installing on zLinux Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Working with ActiveMatrix Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Pre-creating Database Tables (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Post-Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Post-Installation Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Running the Post-installation Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Verifying Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Making the SPM Services Highly Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Making the Rule Service Fault Tolerant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

TIBCO ActiveMatrix Service Performance Manager Installation

iv | Contents

Example: Deploying Rule Service on three Nodes from Different Machines in Different Subnet . . . . . . . . . 70

Installing and Configuring BusinessWorks Service Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Enabling or Disabling the BusinessWorks Service Probe from TIBCO Administrator . . . . . . . . . . . . . . . . . . 76

Common Logging Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Scalability Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Uninstalling the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Appendix A Performing the Post Installation from the Command-line or Manually . . . . . . . . 89

Performing Post Installation Steps From the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Performing the Post Installation Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Appendix B Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111


| v

Preface

TIBCO ActiveMatrix® Service Performance Manager is an enterprise software platform that monitors and proactively manages the health and performance of both Information Technology (IT) and Business services based on Service Level Agreements (SLAs).

Topics

• Changes from the Previous Release of TIBCO ActiveMatrix Service Performance Manager Installation, page vi

• Related Documentation, page vii

• Typographical Conventions, page viii

• How to Contact TIBCO Support, page xi

This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. Please see the readme.txt file for the availability of this software version on a specific operating system platform.


vi | Changes from the Previous Release of TIBCO ActiveMatrix Service Performance Manager Installation

Changes from the Previous Release of


This section itemizes the major changes from the previous release of this guide.

Supported Software

Updates to the supported platforms, databases, browers, and services, see the section Installation Overview on page 14.

TIBCO ActiveMatrix

The instructions to install ActiveMatrix Service Performance Manager with ActiveMatrix Service Bus and ActiveMatrix Service Grid 2.2.x and 2.3.0 releases are provided in the section, Working with ActiveMatrix Products on page 35.

Database Tables

If you want to run ActiveMatrix Service Performance Manager with a database user that has minimum privileges, refer to section, Pre-creating Database Tables (Optional), on page 39.

Post-Installation Procedures

When a new ActiveMatrix Administrator Server is created with Post-installation Tool, to register the model changes in the database and to start the foundation services, you need to follow Steps For the New ActiveMatrix Administrator Server on page 56.

If the post-installation is aborted or the post-installation fails, you need to clean up the environment. See Cleaning the SPM Environment on page 93 and Troubleshooting on page 99 for details.

TIBCO ActiveMatrix BusinessWorks Service Probe

Enabling or Disabling the BusinessWorks Service Probe from TIBCO Administrator is possible. See 76 for details.

FAQ

Some more question and solutions provided in Frequently Asked Questions on page 103.


Preface | vii

Related Documentation

This section lists documentation resources you may find useful.

TIBCO ActiveMatrix® Service Performance Manager DocumentationThe following documents form the TIBCO ActiveMatrix® Service Performance Manager documentation set:

• TIBCO ActiveMatrix Service Performance Manager Installation Read this manual for instructions on site preparation and installation.

• TIBCO ActiveMatrix Service Performance Manager User’s Guide Read this manual for instructions on using the product to build and configure rules for service performance monitoring and management. It also provides details on various dashboards and reports available for monitoring the system and business performance.

• TIBCO ActiveMatrix Service Performance Manager Release Notes Read the release notes for a list of new and changed features. This document also contains lists of known issues, closed issues, and migration information.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products:

• TIBCO ActiveMatrix® Service Bus

• TIBCO ActiveMatrix® Service Grid

• TIBCO ActiveMatrix® BusinessWorks

• TIBCO Enterprise Message Service™

• TIBCO Administrator™

• TIBCO ActiveMatrix® Management Agent for WebSphere

• TIBCO ActiveMatrix® Management Agent for WCF


viii | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

TIBCO_SPM_HOME

Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco.

Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. The directory into which such products are installed is referenced in documentation as ENV_HOME. The value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

TIBCO ActiveMatrix Service Performance Manager installs into a directory within TIBCO_HOME. This directory is referenced in documentation as TIBCO_SPM_HOME. The value of TIBCO_SPM_HOME depends on the operating system. For example on Windows systems, the default value is C:\tibco\spm\1.3.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]


Preface | ix

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical OR that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand para1 | param2 | param3


x | Typographical Conventions

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}

Table 2 Syntax Typographical Conventions

Convention Use


Preface | xi

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibco.com/services/support

https://support.tibco.com

xii | How to Contact TIBCO Support


| 13

Chapter 1 Installation

This chapter describes how to install TIBCO ActiveMatrix Service Performance Manager on supported platforms.

Topics

• Installation Overview, page 14

• Installation Prerequisites, page 20

• Installing Hibernate, page 23

• Installing TIBCO ActiveMatrix Service Performance Manager, page 28

• Working with ActiveMatrix Products, page 35

• Pre-creating Database Tables (Optional), page 39

• Post-Installation Procedures, page 40

• Verifying Installation, page 59

• Making the SPM Services Highly Available, page 65

• Making the Rule Service Fault Tolerant, page 66

• Installing and Configuring BusinessWorks Service Probe, page 73

• Common Logging Configuration, page 80

• Scalability Guidelines, page 84

• Uninstalling the Software, page 86


14 | Chapter 1 Installation

Installation Overview

This section explains how to install TIBCO ActiveMatrix Service Performance Manager. TIBCO ActiveMatrix Service Performance Manager is based on the TIBCO ActiveMatrix platform. During the installation of TIBCO ActiveMatrix Service Performance Manager, runtime components of the ActiveMatrix platform will also be installed.

Service Probes

The TIBCO ActiveMatrix Service Performance Manager provides installable components called "Service Probes", that allow the monitoring of TIBCO BusinessWorks (standalone) and TIBCO ActiveMatrix Service Grid applications.

TIBCO ActiveMatrix Service Performance Manager

TIBCO ActiveMatrix Service Performance Manager contains the following main components:

• Administrator Installs all the basic components including ActiveMatrix Service Performance Manager Administrator and TIBCO Management Daemon.

• Service Probe for TIBCO ActiveMatrix Allows you to monitor and manage services created in TIBCO ActiveMatrix.

• Service Probe for TIBCO BusinessWorks Allows you to monitor and manage services created in TIBCO BusinessWorks.

• System Services Includes the following major services:

Action Manager Manages the assurance of SLAs and processing of SLA actions.

Rules Service Collects and aggregates service and infrastructure metrics. Runs SLA rules.

Action Service Provides a set of built-in actions that can be associated with rules. These actions can be triggered when conditions in the rules are met.

Alert Notification Service Sends alert notifications to the specified business users if there are any SLA violations.

You must install ActiveMatrix service probe on machines with ActiveMatrix runtime and run the Node Upgrader utility for all the nodes from TIBCO_AMX_HOME\server\bin.


Installation Overview | 15

• Documentation Installs TIBCO ActiveMatrix Service Performance Manager documentation.

Installation ModesThree installation modes are available: GUI, console and silent. When installing in the GUI mode, you can choose to first create the ActiveMatrix Administrator Server and Node as part of the installation process. Or else, you can create administrator server and node after installation also.

Installation TypesTwo installation types are available:

• Typical—The typical installation type installs all the products in the package on the specified platform.

• Custom—The custom installation type allows you to select the products and components to install. When you select the custom installation type, the TIBCO ActiveMatrix Service Performance Manager components are available for selection.

Supported Platforms• Microsoft Windows Server 2003 on x86

• Microsoft Windows XP Professional on x86

• Microsoft Windows Server 2003 and 2008 - 64 bit

• Solaris 10 on SPARC 32-bit and 64-bit

• Solaris 10 x86 32 bit and 64 bit

• Red Hat Enterprise Linux 4.x, 5.1, and 5.2 32-bit (x86) and 64-bit (x86-64)

• SUSE Linux Enterprise v10, SP2 for IBM zSeries - 32 bit and 64 bit

• SUSE Linux Enterprise 10 x86 and x86-64

• HP-UX 11i V3/11.31 on IA-64/Itanium

• AIX 5.3 and 6.1 Power PC 64-bit

System MemoryA minimum of 3 GB of physical memory is required.



Installer Account

Microsoft Windows

You must have administrator privileges for the machine on which TIBCO ActiveMatrix Service Performance Manager is installed.

If you do not have administrator privileges, the installer exits. In such a case, you must log out of the system and log in as a user with the required privileges, or request your system administrator to assign the administrator privileges to your account.

If you want to install the product on a network drive, you must ensure that the account used for installation has permission to access the network drive.

UNIX

TIBCO ActiveMatrix Service Performance Manager can be installed by a regular (non-root) user and super-user (root). Different users can install the same product at different locations.

A graphic environment such as CDE or XWindows is required to run the installer in GUI mode.

Installer Log FileThe installer log file, tibco_universal_installer.<timestamp>.<username>_install.txt, is written to the .TIBCO folder of the user’s home directory. The installer log file captures the following information:

• Installation environment details such as the user who invoked the installer, hostname, JAVA_HOME in the environment, Operating System details, and so on.

• List of assemblies installed.

Disk SpaceWhen a TIBCO ActiveMatrix Service Performance Manager package is unpacked, it is extracted into a temporary folder. The installer requires up to 500 MB of free space to extract the package to a temporary folder.



Temporary Disk Space Required by the Installer

The installer requires at least 70 MB of free space in the temporary directory. On Microsoft Windows, the temporary directory location is %SystemDrive%:\Documents and Settings\user_name\Local Settings\Temp

If your system does not have sufficient disk space in the default temporary area, you can run the installer with a different temporary directory by using the following option:-is:tempdir /new_temp

where /new_temp has sufficient free disk space.

The installer calculates the disk space required in the product home location for the selected components before the actual installation (copying of files to system) begins. The installer will proceed only if sufficient free disk space is available in the product home location.

The universal installer for the product requires about 600 MB of free disk space to install the TIBCO ActiveMatrix Service Performance Manager.

If the disk space required is consumed by another process while the installer is copying the files, the disk space available may be reduced. In such a case, the installer may fail and will then give a failure message.

While performing the installation, do not run other processes that consume disk space in the product home location.

Disk Space After Installation

A typical install of TIBCO ActiveMatrix Service Performance Manager that includes basic TIBCO ActiveMatrix components consumes about 700 MB of disk space under TIBCO_HOME. The TIBCO ActiveMatrix Service Performance Manager alone consumes about 85 MB of disk space.

Supported DatabasesA database is required for storing TIBCO ActiveMatrix Administration and ActiveMatrix Service Performance Manager information.

The supported databases are:

• Oracle 9i Release 2 (9.2)

• Oracle 10g Release 1 (10.1)

• Oracle 10g Release 1 (10.1) RAC







• Microsoft SQL Server 2005

• Microsoft SQL Server 2008

• HSQLDB 8.1 (for development only)

Supported BrowsersA web browser is required to verify installation.

The supported web browsers are:

• Microsoft Internet Explorer 7.0

• Mozilla Firefox 2.0, 3.0

Recommended Email ServersTo send email alerts, you can use one of the following email servers:

• Magic WinMail Server V2.3

• James Apache email server 2.3.1

Supported Services for Performance MonitoringUsing ActiveMatrix Service Performance Manager, you can monitor the performance of the following services:

• TIBCO ActiveMatrix BusinessWorks web services—Install Service Probe for TIBCO ActiveMatrix BusinessWorks while installing ActiveMatrix Service Performance Manager. See TIBCO ActiveMatrix Service Performance Manager User’s Guide for details.

• TIBCO ActiveMatrix infrastructure and services created in ActiveMatrix Service Grid, ActiveMatrix Service Bus, and TIBCO ActiveMatrix Implementation Types—Install Service Probe for TIBCO ActiveMatrix while installing ActiveMatrix Service Performance Manager. Also, you need to install ActiveMatrix Service Performance Manager on all the machines where ActiveMatrix Administrator is running for the UI plug-ins work correctly. See TIBCO ActiveMatrix Service Performance Manager User’s Guide for details.



• Microsoft Windows Communication Foundation (WCF) Services—Install TIBCO ActiveMatrix Management Agent for WCF with Service Probe for WCF. Refer to Chapter 4 in TIBCO ActiveMatrix Management Agent for WCF User’s Guide for details.

• Java EE Web Services and Service References (JAXRPC/JAXWS) which are deployed and running in IBM WebSphere Application Server— Install TIBCO ActiveMatrix Management Agent for WebSphere with Service Probe for WAS. Refer to Chapter 7 in TIBCO ActiveMatrix Management Agent for WebSphere User’s Guide for details.



Installation Prerequisites

This section lists the prerequisites to install TIBCO ActiveMatrix Service Performance Manager.

PrerequisitesThis section lists the required and optional products that work with TIBCO ActiveMatrix Service Performance Manager.

Hibernate 3.2.5 (Required)

Required. Hibernate must be installed before installing any TIBCO ActiveMatrix product. If the variable TIBCO_HOME is not specified, you must specify the location for TIBCO_HOME while installing Hibernate. All subsequent TIBCO ActiveMatrix products will be installed under TIBCO_HOME.

The order in which you install the base products is important. You must install the base products in the order they are listed below.

If you want to install TIBCO Adapters or TIBCO Enterprise Message Service 5.0, install it before installing ActiveMatrix Service Performance Manager.

If you want to install only ’ActiveMatrix BusinessWorks Service Probe’ on a machine, there is no need to install hibernate.


Installation Prerequisites | 21

TIBCO Enterprise Message Service 4.4.0 or Higher (Required)

Required. TIBCO Enterprise Message Service is used by the SOAP and JMS containers that are installed with TIBCO ActiveMatrix.

TIBCO ActiveMatrix Service Grid 2.2.0 or Higher (Optional)

Required only if you want to monitor TIBCO ActiveMatrix services.

TIBCO ActiveMatrix Service Bus 2.2.0 or Higher (Optional)

Required only if you want to monitor TIBCO ActiveMatrix Service Bus services or external services that are virtualized by the Service Bus.

TIBCO ActiveMatrix BusinessWorks Service Engine 5.7 and 5.7.x (Optional)

Required only if you want to monitor BusinessWorks services.

To monitor BusinessWorks services engines, it is recommended that you install ‘TIBCO ActiveMatrix BusinessWorks’ and ‘TIBCO ActiveMatrix BusinessWorks Service Engine’ before installing ‘TIBCO ActiveMatrix Service Performance Manager’. However, if you install BusinessWorks after installing ActiveMatrix Service Performance Manager, see the section For New Installation or Deployment of BusinessWorks on page 74.

TIBCO ActiveMatrix Service Performance Manager requires Hibernate and Enterprise Message Services installed. Also, based on the products that you want to monitor, one or more of the following products should be installed:

• TIBCO ActiveMatrix Service Grid

• TIBCO ActiveMatrix Service Bus

• TIBCO ActiveMatrix Implementation Type for C++

• TIBCO ActiveMatrix Implementation Type for Scripting in Ruby

• TIBCO ActiveMatrix BusinessWorks

• TIBCO ActiveMatrix Management Agent for WebSphere

• TIBCO ActiveMatrix Management Agent for WCF

ActiveMatrix Service Performance Manager 1.3.0 is based on ActiveMatrix Service Grid 2.3.0 and embeds certain runtime components. It also supports ActiveMatrix Service Grid 2.2.x. This leads to few variations to the order of installation and certain specific instructions for each. See Working with ActiveMatrix Products on page 35 for details.



TIBCO ActiveMatrix BusinessWorks 5.6, 5.7.1, 5.7.2, 5.8 (Optional)

In a distributed setup, the Service Probe for BusinessWorks component is required component to be installed on the machine where TIBCO BusinessWorks is installed. See the sections, Service Probe for BusinessWorks (step 9) and Installing and Configuring BusinessWorks Service Probe on page 73 for details.

To execute BusinessWorks actions, you need to install TIBCO Rendezvous 8.2 or higher (install TIBCO Runtime Agent 5.6.2 or higher).

TIBCO ActiveMatrix Management Agent for WebSphere 1.2.0 (Optional)

Required only if you want to monitor Java EE Web Services and Service References (JAXRPC/JAXWS) which are deployed and running in IBM WebSphere Application Server.

Refer to TIBCO ActiveMatrix Management Agent for WebSphere documentation for details on installation and configuration.

TIBCO ActiveMatrix Management Agent for WCF 1.2.0 (Optional)

Required only if you want to monitor Microsoft Windows Communication Foundation (WCF) Services.

Refer to TIBCO ActiveMatrix Management Agent for WCF documentation for details on installation and configuration.

You must have TIBCO Runtime Agent 5.5.4 or higher installed on your machine for BusinessWorks Service Probe to work.


Installing Hibernate | 23

Installing Hibernate

You must install Hibernate before installing a TIBCO ActiveMatrix product.

If TIBCO_HOME does not exist on the machine, its location must be specified when installing Hibernate. All subsequent TIBCO software will be installed under TIBCO_HOME.

Install Hibernate using one of the modes described in the sections:

• Installing in GUI Mode on page 23

• Installing in Console Mode on page 26

• Installing in Silent Mode on page 26

Installing in GUI Mode

To install Hibernate in GUI mode:

1. Open the physical media or download the Hibernate package.

2. Extract the Hibernate archive file to a temporary directory.

3. Navigate to the temporary directory that contains the Universal Installer.

4. Run TIBCOUniversalInstaller.

5. The Welcome screen appears. Click Next.

6. The License Agreement screen appears. After reading through the license text, click I accept the terms of the license agreement and then click Next.

7. The Installation Environment location screen appears. If the TIBCO_HOME directory is not found, you are prompted for the directory name. Click Browse

On machines where TIBCO ActiveMatrix is running, Hibernate will be already available and there is no need to reinstall it.



to specify the directory path or accept the default location. The next screen shows the default location on Windows.

On UNIX machines, for root users, the default installation directory is /opt/tibco. For non-root users, the default installation directory is /myhome/tibco, where myhome is the home directory of the user

8. The Hibernate installer displays the location where Hibernate will be installed. Click Next.

The default installation environment is TIBCO_HOME. We recommend you to install this product in the default TIBCO_HOME where all the other TIBCO ActiveMatrix products are installed.



9. Choose the installation type, Typical or Custom. Choosing Typical installs the default components. Choosing Custom allows you to select the components to install. Click Next.

10. The Pre Install Summary screen appears listing your choices. Click Install.

11. The Post Install Summary screen appears indicating Hibernate has been successfully installed. Click Finish.



Installing in Console Mode

To install Hibernate in console mode:



3. Using a console window, navigate to the temporary directory that contains the Universal Installer.

4. Run TIBCOUniversalInstaller -console.

5. Complete the installation by responding to the console window prompts.

Installing in Silent Mode

The following procedure explains how to install Hibernate in silent mode. The TIBCOUniversalInstaller.silent file is packaged in the directory that contains the Universal Installer. You must edit the file with information for your environment before launching the silent installation. The file includes comments that describe the installation properties you can set.

While you can use the TIBCOUniversalInstaller.silent file, it is good practice to copy the file to a different name and use that file for the silent install.

If errors occur during installation, they will be listed in the installation log file (see the User_Home/.TIBCO directory).



The .silent file contains statements about Environments (see sample below). These Environments have nothing to do with ActiveMatrix environments and are are related to multi TIBCO_HOME support in the Universal Installer which ActiveMatrix does not support. The section should be ignored.

Sample:<entry key="createNewEnvironment">true</entry><entry key="environmentName">TIBCO-HOME2</entry><entry key="environmentDesc">my installation</entry>



3. Using a console window, navigate to the temporary directory that contains the universal installer.

4. Copy the TIBCOUniversalInstaller.silent file and name the file.

5. Using a text editor, open the copied file and update the install location, and features to install.

6. Run: TIBCOUniversalInstaller -silent -V responseFile="myfilename.silent"

If you are using the TIBCOUniversalInstaller.silent file, you need not supply the file name and can run: TIBCOUniversalInstaller -silent

A line similar to the following is written to the installer log file when installation completes:Install, com.tibco.installer.util.TIBCOInstaller, dbg.Debug, The installation has completed. Please check the log file for additional information.



Installing TIBCO ActiveMatrix Service Performance Manager

This section describes the steps to install TIBCO ActiveMatrix Service Performance Manager. You can use one of the following modes for the product installation:

• Installing in GUI Mode

• Installing in Console Mode

• Installing in Silent Mode

Before proceeding to install, ensure that all the pre-requisites are met. Refer to the previous sections for details.

Installing in GUI Mode

In the GUI mode, the installer is invoked by double-clicking the install icon. The installer presents panels that allow you to make choices about product features, product installation location, and so on.

The installation procedure for Microsoft Windows and Unix platforms is almost the same. Wherever the steps differ, platform specific information is provided.

The following procedure explains how to install the product in GUI mode.

1. Open the physical media or download the TIBCO ActiveMatrix Service Performance Manager package. For example, TIB_amx-spm_1.3.0_win_x86.zip for Microsoft Windows platform.

2. Extract the contents of the package to a temporary directory.

3. Navigate to the temporary directory that contains the universal installer.

4. Run TIBCOUniversalInstaller. You can do so in one of the following ways:

— Double-click the installer icon.

— On the command prompt, provide the absolute path of the installer file without specifying any options. The installer defaults to GUI mode.

The Welcome screen appears.

5. Click Next.

6. The License Agreement screen appears. After reading through the license text, click I accept the terms of the license agreement and then click Next.

7. The Installation Environment screen appears. Select the default Environment TIBCO_HOME where Hibernate is also installed. Click Next.


Installing TIBCO ActiveMatrix Service Performance Manager | 29

8. Select Typical to install all the available features or Custom to choose the features to install. Click Next.

9. If you selected Custom in step 9, the Product Features screen appears. This screen lists the components available for installation.

The installer displays the following components of ActiveMatrix Service Performance Manager:

Administrator: Select to install the ActiveMatrix Service Performance Manager Administrator. It includes the basic components such as User Interface (UI) and Command Line Interface (CLI). The disk space required to install this component is 438 MB.

Service Probe for TIBCO ActiveMatrix: Select to install the service monitoring unit for TIBCO ActiveMatrix. To monitor the ActiveMatrix services, you need to install this component on a machine on which TIBCO ActiveMatrix Service Grid or TIBCO ActiveMatrix Service Bus is running. Make sure that you run the node upgrader utility on all the existing nodes. The disk space required to install this component is 35 MB.

Service Probe for TIBCO BusinessWorks: Select to install the service monitoring unit for TIBCO BusinessWorks. You must only install the BusinessWorks service probe on a machine on which TIBCO BusinessWorks Standalone is running.

In a distributed setup, you must install ActiveMatrix Service Performance Manager Administrator on a machine where ActiveMatrix Administrator is installed.



System Services: Select to install the system services for the alert server, action manager, standard action services, and rule services. The disk space required to install this component is 67 MB.

Documentation: Installs the ActiveMatrix Service Performance Manager documentation for your reference. The disk space required to install this component is 38 MB.

By default, all the components are selected. Clear the check box next to the component that you do not want to install and click Next.

10. The installer prepares the bundled components for installation based on the components selected for install. A Pre-Install Summary screen appears. Verify the list of products selected for install and then click Install. Click Yes to All to close any pop up windows that display during installation.

11. If you have selected the TIBCO ActiveMatrix Administrator component for installation, the TIBCO ActiveMatrix Administrator screen appears during installation.

Click Next after making your selections.

The Post-Install Summary screen appears. This screen summarizes the installation process.

12. Click Finish to complete the installation process and close the installer window.

13. After the installation is complete, run the ActiveMatrix Service Performance Manager Post Installation Configuration tool. See Post-Installation Procedures on page 40 for details.

When installing in GUI mode with the TIBCO ActiveMatrix Administrator component selected, the installer provides the option of starting the database server and invoking the ActiveMatrix Administrator server creation wizard to create the first ActiveMatrix Administrator Server and node.

It is recommended that you do not create Administrator server at this point. You can create Administrator server during the post-installation using the Post-Installation Configuration Tool.

However, if you wish to create Administrator server, make sure that you update all configuration and property files and start TIBCO Enterprise Message Service and Hibernate. For detailed instructions, refer to TIBCO ActiveMatrix Administration.



Installing in Console Mode

In console mode, you can install the product in a non-Windows environment.

The following procedure explains how to install the product in console mode.

1. Open the physical media or download the TIBCO ActiveMatrix Service Performance Manager package.



4. Run TIBCOUniversalInstaller with the option -console.

On Microsoft Windows, run:TIBCOUniversalInstaller.exe -console

On UNIX platforms, run:TIBCOUniversalInstaller.bin -console

5. Complete the installation by responding to the console window prompts.


While running in the console mode, you can use the following keys to move through the installation process:

Enter: Moves forward in the installer.

BackSpace or 2: Goes back to the previous screen.

3: Cancels the Wizard and exits the installation or uninstallation.

5: Redisplays the current screen.

Installing in Silent Mode

In the silent mode, the universal installer does not prompt for any inputs during installation. Instead, the inputs are read from a response file that can be provided as a command line parameter. If no value is specified, the installer uses the default TIBCOUniversalInstaller.silent file.

The TIBCOUniversalInstaller.silent file is packaged in the directory that contains the universal installer. You must edit the file with information for your environment before launching the silent installation. The file includes comments that describe the installation properties you can set. While you can use the TIBCOUniversalInstaller.silent file, it’s good practice to copy the file to a different name and use that file for the silent install.



The following procedure explains how to install the product in silent mode.

1. Open the physical media or download the TIBCO ActiveMatrix Service Performance Manager package.



4. Make a copy of the TIBCOUniversalInstaller.silent file and rename the file.

5. Using a text editor, open the copied file and update the install location, and features to install.

6. Add the following entries in the file:

<entry key="reinstallFeatures">false</entry>

If this is false and TIBCO ActiveMatrix Service Grid or TIBCO ActiveMatrix Service Bus is installed, then TIBCO ActiveMatrix is not reinstalled.

<entry key="feature_Administrator_spm">true</entry>

<entry key="feature_Service Probe for TIBCO ActiveMatrix_spm">true</entry>

<entry key="feature_Service Probe for TIBCO BusinessWorks_spm">true</entry>

<entry key="feature_System Services_spm">true</entry>

<entry key="feature_Documentation_spm">true</entry>

7. Run the following command:

On Microsoft Windows platform, run:

TIBCOUniversalInstaller.cmd -silent -V

responseFile=<responseFileName>.silent

On UNIX platforms, run:

TIBCOUniversalInstaller.bin -silent -V

responseFile=<responseFileName>.silent

If you are using the TIBCOUniversalInstaller.silent file, you need not specify the response file name.

A line similar to the following is written to the installer log file when the installation completes:... Install, com.tibco.installer.util.TIBCOInstaller, dbg.Debug, Executing Event:::OnEndInstall




Installing on zLinux PlatformThe following procedure provides detailed steps to install TIBCO ActiveMatrix Service Performance Manager on SUSE Linux Enterprise v10, SP2 for IBM zSeries.

Installation Prerequisites

1. As the installer requires a large number of files open concurrently, increase the file handle limit for the user performing the installation.

For example: % set ulimit -n 2048.

• If a nonroot user is installing the product, ensure that the maximum number of open files hard limit is set to at least 2048. This can be checked from bash with the following command:

$ ulimit -aH

Look for the open files line to see what the hard limit is set to.

For example: $ ulimit -aHcore file size (blocks, -c) unlimiteddata seg size (kbytes, -d) unlimitedfile size (blocks, -f) unlimitedpending signals (-i) 16384max locked memory (kbytes, -l) 32max memory size (kbytes, -m) unlimitedopen files (-n) 2048pipe size (512 bytes, -p) 8POSIX message queues (bytes, -q) 819200stack size (kbytes, -s) unlimited\cpu time (seconds, -t) unlimitedmax user processes (-u) 16384virtual memory (kbytes, -v) unlimitedfile locks (-x) unlimited

• If the open files line shows less than 2048, add the following line to the file:

/etc/security/limits.conf:* hard nofile 2048

2. Set the soft limit equal to hard limit using the following command:

ulimit -n 2048

3. For the setting to take effect, log out and log in again.

4. Install TIBCO ActiveMatrix Service Performance Manager in console mode using the installation steps mentioned in the section, Installing in Console Mode on page 31.




The LD_LIBRARY_PATH variable cannot be set to reflect the location of the bundled JRE in your profile until the installation is complete.

To complete post- install tasks, do the following:

• Prepend the location of the JRE bundled in your product (TIBCO_HOME/tibcojre64/1.6.0/bin) to the LD_LIBRARY_PATH variable in your user profile script.

• Change to the TIBCO_HOME/managementdaemon/2.0/bin/ directory and run managementscript.

• Change to the TIBCO_HOME/managementdaemon/2.0/daemonlets/com.tibco.matrix.daemonlet directory and run amxdaemonletscript.

You cannot run the Post-installation Configuration tool from the UI mode on zLinux. To perform the post-installation from the command line, refer to the section, Performing Post Installation Steps From the Command Line, on page 90.


Working with ActiveMatrix Products | 35

Working with ActiveMatrix Products

As ActiveMatrix Service Performance Manager embeds certain runtime components of TIBCO ActiveMatrix, the order of product installation is important. Based on your existing setup and requirement, follow the relevant steps for the product installation and configuration.

Installing the ‘ActiveMatrix Service Performance Manager’ Over the Existing ActiveMatrix Setup (Recommended Order)

If you are installing the product on an already existing ActiveMatrix setup such as TIBCO ActiveMatrix Service Grid and TIBCO ActiveMatrix Service Bus, there is a high possibility that nodes have been created and are running.

To install TIBCO ActiveMatrix Service Performance Manager on top of an existing TIBCO ActiveMatrix installation, you must first stop the nodes and all the applications.

The recommended order of installation is:

1. TIBCO Enterprise Message Service

2. Hibernate

3. TIBCO ActiveMatrix Service Grid 2.3.0

4. TIBCO ActiveMatrix Service Performance Manager 1.3.0

Consider the following points during product installation:

• Installation Environment—If your system already has TIBCO ActiveMatrix installed on it, you must install ActiveMatrix Service Performance Manager in the same installation environment. The default installation environment is TIBCO_HOME. We recommend you install this product in the default TIBCO_HOME where all the other TIBCO ActiveMatrix products are installed.

• When a higher version of product (like ActiveMatrix Service Performance Manager or ActiveMatrix Service Grid) is installed over an existing setup of

For monitoring ActiveMatrix services in a distributed setup, you need to install the following ActiveMatrix Service Performance Manager components:

• Install the ActiveMatrix Service Performance Manager Administrator on a machine where ActiveMatrix Administrator is installed.

• Install Service Probe for ActiveMatrix on a machine on which TIBCO ActiveMatrix Service Grid or TIBCO ActiveMatrix Service Bus is running. Make sure that you run the node upgrader utility on all the existing nodes. The disk space required to install this component is 35 MB.



TIBCO ActiveMatrix products, run the following post installation step to make sure the tra files are up to date:

TIBCO_SPM_HOME/bin/UpdateInstallation.bat

• ActiveMatrix Node Migration Path—As TIBCO ActiveMatrix Service Performance Manager is based on ActiveMatrix 2.3.0, you must upgrade Management Daemon, ActiveMatrix Administrator Server, and all the existing nodes to 2.3.0 version as outlined in TIBCO ActiveMatrix Service Grid 2.3.0 Release Notes.

• Replace Existing Objects—As TIBCO ActiveMatrix Service Performance Manager is based on ActiveMatrix 2.3.0, the new or updated components exist in the following order:

— ActiveMatrix Service Grid 2.3.0

— ActiveMatrix Service Performance Manager 1.3.0

Based on your setup and the order of installation, you may encounter one of the following scenarios. While installing ActiveMatrix Service Performance Manager 1.3.0, the installer prompts to replace the existing files with "Yes, Yes to All, No, No to All" dialogs at few stages and the recommendations are as follows:

When you install ‘ActiveMatrix Service Performance Manager’ over ‘ActiveMatrix Service Grid’, you must install the Service Probe for ActiveMatrix on all the machines with ActiveMatrix runtime and run the Node Upgrader utility for all nodes from TIBCO_AMX_HOME\server\bin. See TIBCO ActiveMatrix Service Performance Manager Release Notes for details on the Node Upgrader utility.

Table 3 Installation Order

Scenario Installation Order Recommendation to Replace Existing Objects

Scenario 1 1. Install ActiveMatrix Service Grid 2.3.0

2. Install ActiveMatrix Service Performance Manager 1.3.0

Select Yes To All.


Working with ActiveMatrix Products | 37

For example, the steps for installing ‘ActiveMatrix Service Performance Manager 1.3.0’ on the existing setup of ‘ActiveMatrix Service Grid 2.3.0’ are as follows:

1. Shut down all ActiveMatrix nodes.

2. Shut down ActiveMatrix Management Daemon.

3. Install ActiveMatrix Service Performance Manager 1.3.0. See Installing in GUI Mode on page 28 for details.

4. Select Yes to All in the Replace Existing Object?

5. Upgrade ActiveMatrix Administrator Server, Management Daemon, and all the existing nodes as outlined in the TIBCO ActiveMatrix Service Grid 2.3.0 Release Notes.

6. Start the ActiveMatrix database server, Management Daemon, and the ActiveMatrix Administrator.

7. Perform the post installation tasks as outlined in the Post-Installation Procedures on page 40. You must choose to use the existing ActiveMatrix Administrator in the Post-Installation Configuration Tool and leave everything else in the default settings.

Scenario 2 1)

1. Install ActiveMatrix Service Grid 2.2.x


3. Upgrade to ActiveMatrix Service Grid 2.3.0


If you choose to upgrade ActiveMatrix Service Grid to 2.3.0, select Yes to All.

While installing ActiveMatrix Service Performance Manager 1.3.0, select Yes to All.

Scenario 3 1. Install ActiveMatrix Service Performance Manager 1.3.0

2. Install ActiveMatrix Service Grid 2.3.x

While installing ActiveMatrix Service Grid 2.3.x, select No to All.

Table 3 Installation Order

Scenario Installation Order Recommendation to Replace Existing Objects

During installation of ‘ActiveMatrix Service Performance Manager’ on top of ‘ActiveMatrix Service Grid’, the system informs that some of the files existing in the system are newer than the one being installed.



If TIBCO ActiveMatrix Administrator is running as a Windows service and you install ActiveMatrix Service Performance Manager, you need to uninstall and reinstall ActiveMatrix Administrator service from the command line.

Otherwise, ActiveMatrix Administrator continues running with old classpath entries and ActiveMatrix Service Performance Manager web services do not get registered properly.


Pre-creating Database Tables (Optional) | 39

Pre-creating Database Tables (Optional)

If you do not want ActiveMatrix Service Performance Manager to create database tables automatically, you can pre-create the ActiveMatrix schema (database tables) before running the Post Installation Configuration tool. Doing so allows you to run ActiveMatrix Service Performance Manager with a database user that has minimum privileges.

1. To create ActiveMatrix Schema refer to "Pre-creating ActiveMatrix Schema" section in the TIBCO ActiveMatrix Administration guide.

2. Load TIBCO_HOME/spm/<version>/scripts/ddl/tables_<yourdbtype>.sql to your db.

3. Edit TIBCO_HOME/amxadministrator/<version>/bin/startadminserver.template.tra and add the following lines:

java.property.monitormanage.update.schema=falsejava.property.spm.update.schema=false

4. Run the Post-Installation Configuration Tool as described in the following section.

Do not follow the steps in this section if you want ActiveMatrix Service Performance Manager to create the database tables automatically and give SPM database user the table creation permissions.




After installing TIBCO ActiveMatrix Service Performance Manager, you must perform the following steps in order to activate the ActiveMatrix Service Performance Manager services.

TIBCO ActiveMatrix Administrator Server is a separate engine from an ActiveMatrix runtime node. TIBCO ActiveMatrix Service Performance Manager adds the user interface and web services on to the ActiveMatrix Administrator Server.

During post installation, a new ActiveMatrix runtime node to deploy and start the System Services is created. It also creates a new environment to support this runtime node. The default name of ActiveMatrix Service Performance Manager environment is spmsysenv and of node is spmsysenv_spmsysnode. These can be changed in either the Post Installation Tool or by editing the data.properties file located in TIBCO_SPM_HOME/scripts. This way ActiveMatrix Service Performance Manager keeps its own services separate from the services and nodes that it manages.

Post-Installation Configuration ToolThe Post-Installation Configuration tool provides a graphical user interface for setting up the SPM System Services and Administration Server. The tool can:

• Create a new Administration Server to deploy and configure the SPM System Services, or

• Use an existing Administration Server to deploy and configure the SPM System Services.

At the end of the tool's execution run, a new ActiveMatrix environment and node are created where the SPM System Services are deployed and hosted.

If you already have an existing ActiveMatrix Administrator server and plan to use it for ActiveMatrix Service Performance Manager runtime, you must start ActiveMatrix Administrator server, database, and management daemon before running the Post Installation Configuration tool.


Post-Installation Procedures | 41

Alternatively, the post installation tasks can be performed from the command line or manually. The zLinux platform does not support running the Post-installation Configuration tool from the UI mode. So the post-installation can be performed only from the command-line on this platform. Refer to Appendix A, Performing the Post Installation from the Command-line or Manually, on page 89 for detailed steps.

By default, the Post-installation tool sets default values for the following components:

• SPM System Node

• TIBCO ActiveMatrix Admin Server

• TIBCO ActiveMatrix Messaging Server

• TIBCO ActiveMatrix Service Performance Manager System Services Shared Resources

• TIBCO ActiveMatrix Service Performance Manager Action Manager Service substitution variables

• TIBCO ActiveMatrix Service Performance Manager Action Services substitution variables

• TIBCO ActiveMatrix Service Performance Manager Alert Services substitution variables

Using an Existing Administrator Server

If you plan to use an existing ActiveMatrix Administrator Server with the Post-installation Configuration tool, you must wait for the ActiveMatrix Administrator Server to start up completely.

To check whether the ActiveMatrix Administrator Server is completely up and running, start the ActiveMatrix Administrator Server and check that the Build and Configure Rules and View and manage Dashboards perspectives (that is, the perspectives specific to ActiveMatrix Service Performance Manager) are available in TIBCO ActiveMatrix Administrator UI.

Depending on your choice of using an existing ActiveMatrix Administrator Server or creating a new Administrator Server, you need to start only the SPM node or Administrator Server, System Services, Management Daemon (and HSQLDB).



If these perspectives are not visible in ActiveMatrix Administrator, you can manually upload spmui.war as follows:

1. Access Configure Enterprise Assets > Administrator Cluster > Plug-ins in ActiveMatrix Administrator.

2. Select the following plug-ins from the TIBCO_SPM_HOME\webapp folder:

rajax.war—Reverse Ajax plugin Wrapper

spmui.war—TIBCO ActiveMatrix Service Performance Manager

3. Click Deploy.

4. Re-login to TIBCO ActiveMatrix Administrator and check the perspectives.

SSL Enabled Administrator Server

If you plan to use an existing ActiveMatrix Administrator Server that is SSL enabled, follow these steps before running the Post Installation Configuration tool:

1. Modify the adminURL property in TIBCO_HOME\spm\<version>\scripts\login.properties to use https instead of http.

2. Import the Administrator server’s certificate into JRE’s keystore:

keytool -keystore TIBCO_HOME\jre\<version>\lib\security/cacerts -import -file <servercert file name> -storepass changeit

3. Open the file TIBCO_HOME\amx\<version>\server\templates\security-config.xml and search for the property scheme and set it's value from http to https. Make sure that you replace the value at both instances of "scheme".

Setting the AIX Platform to Run the Post-installation Tool

To run the Post-installation Configuration tool on AIX, IBM Java5 32-bit JRE or SDK must be installed into /usr/java5. The IBM Java5 32-bit for AIX can be downloaded from http://www.ibm.com/developerworks/java/jdk/aix/service.html.

If IBM Java5 32-bit is installed in a different location, edit TIBCO_SPM_HOME/postinstalltool/SPMPostInstallationTool.ini to change /usr/java5 to the correct path.

You cannot point to TIBCO_HOME/tibcojre64/1.6.0 since that is a 64-bit JRE.



Running the Post-installation Configuration ToolTo run the Post-installation tool, do the following:

1. Start TIBCO Enterprise Message Service Server.

2. Locate the Post-installation tool at the following installation folder:

TIBCO_SPM_HOME\postinstalltool

3. To launch the tool, double-click the file:

SPMPostInstallationTool.exe

4. In the TIBCO ActiveMatrix SPM System Node Information dialog, the values for the following properties are set:

Figure 1 TIBCO ActiveMatrix SPM System Node Information

TIBCO Home—The path where TIBCO ActiveMatrix Service Performance Manager product is installed.

Environment Name—The name of the environment to deploy a node on which all SPM system services will run. The default name of the environment is spmsysenv.

Node Name—The name of the node on which all SPM system services will run. The default name of the node is spmsysenv_sysnode.

Node Management Port—The port on which the node listens and responds to management and control functions using JMX protocol.

Node Default HTTP Connector Port—The default port on which the node listens for incoming HTTP requests.

Do not change the default value of the above property TIBCO Home.



5. Click Next.

6. Provide information about the TIBCO ActiveMatrix Administrator Server where the SPM system environment and node will be connected.

Use existingAdministrator

Server

By default, the SPM environment and node are connected to the existing TIBCO ActiveMatrix Administrator server and Use existing Administrator Server is checked.

Figure 2 TIBCO ActiveMatrix Administrator Server Information

The values for the following properties are set by default:

Administrator Server User Name displays the default Admin username value as ’root’.

Administrator Password displays the obfuscated password. The default password value is ’tibco’.



To know how to create an obfuscated password, see Creating an Obfuscated Password on page 93.

You can either use the existing Administrator Server or create a new Administrator Server.

By default, Use Existing Administrator Server is selected.

a. Enter the Administrator Server Connection information as follows:

Administrator Server Host displays the default value of host as ${machine name}, that is, local host.

Administrator Server Port displays the default value for the port as 8120.

Administrator Server Instance Name displays the default name of the administrator instance, that is, admin.

If the Administrator server does not use the default username/password (that is, root/tibco), you must change the value of the username/password field to an existing super user in Administrator server.

If you choose to Use Existing Administrator Server, you must start the following services either from the Windows Services dialog or from the command line:

• TIBCO ActiveMatrix Database: Start the database that is used for ActiveMatrix Administrator server. For example,

On Windows, click Start > All Programs > TIBCO > TIBCO ActiveMatrix > Start HSQLDB Server.

From the command line on all platforms, run TIBCO_HOME/amx/hsqldb/bin/amx-db.

• TIBCO ActiveMatrix Management Daemon: Start this service only if it is not running.

On Windows, click All Programs > TIBCO > TIBCO Management Daemon > Management Daemon.

From the command line on all platforms, execute TIBCO_HOME/managementdaemon/<version>/bin/managementdaemon

• TIBCO ActiveMatrix Administrator server

To start the ActiveMatrix Administrator server, run TIBCO_HOME/amxadministrator/<version>/bin/amx_admin



AdministratorServer

DatabaseDetails

You can enter details about one of the following database:

• Existing ActiveMatrix Administrator database—This database can store information about rules, assurance, and actions along with ActiveMatrix Service Performance Manager statistics.

• New database—This database can store information related to assurance and actions that can take effect after a rule is triggered. However, the data related to ActiveMatrix Service Performance Manager statistics can be stored only into ActiveMatrix Administrator database. After the post-installation is complete, a quartz JDBC shared resource connection is created in ActiveMatrix Administrator that points to new database rather than the existing ActiveMatrix Administrator database.

b. Enter the Administrator Server Database Details as follows:

Database Type—Select the database type for server data persistence. The default database is HSQL. If you want to use any external database, select the appropriate database type from the drop-down list.

Database User Name—User name used while creating the database. The default user name is ‘admin’.

Database Password—Password used while creating the database. The default password is ‘<blank>’ or no password (that is, leave the field empty).

Database JDBC URL—The JDBC URL specified for the database connection. You must replace the {machine name} with the actual host name on which your database Server is running.

Database JDBC Driver—The JDBC driver used to connect to the database.

To use Oracle or SQL server as a database for ActiveMatrix Administrator Server, enter appropriate values for User Name and Password or keep the default value <unset> for successful deployment of AlertSA.

If you keep the fields blank or null, the AlertSA gets deployed with errors.

To use Oracle RAC as a database, enter Database JDBC URL as oracle:oci:@<ServiceName>. Note that the datadirect drivers shipped with ActiveMatrix Service Performance Manager do not support TAF feature of Oracle RAC, so it is recommended that you use oracle oci drivers when using the Oracle clusters for your database instances.

If you use Oracle RAC with oracle oci drivers, the connection to Oracle RAC cannot be tested using the Test Connection button.



Database Max Connections—Maximum number of simultaneous connections to the database that can be open.

c. If you are using an external database such as MSSQL or Oracle, you can validate the database connection details using the Test Connection button.

To validate the connection details of external database:

— Start the database server.

— Enter correct configuration information for all the above database properties.

— Click Test Connection.

A Database Connection Test Results window is displayed with the test results for the database connection. It informs whether the connection to the database was successful or failed with the given values.

7. Click Next.

The Test Connection button is enabled only after you enter configuration information. To test the database connection, you must first start the database server.

If you use HSQLDB, the Test Connection button remains disabled.



Create NewAdministrator

Server

8. If you do not want to use the existing Administrator Server, clear Use Existing Administrator Server. It enables the following options to create a new Administrator Server with the default HSQL database or any external database.

Figure 3 TIBCO ActiveMatrix Administrator Server Information

Provide the following details for New Administrator Server:

Administrator Server Cluster Name—The name of the cluster in which ActiveMatrix Administrator server is created. The default value is amx.

Administrator Server Instance Name—The name of the ActiveMatrix Administrator server instance. The default value is admin.

Administrator Server Management Port—The default port used for Administrator server communication. The default value is 8110.



Provide the details for the Database to be used by the Administrator Server as explained in the Administrator Server Database Details on page 46.

9. Click Next.

10. Specify information for the Messaging server to be used in the SPM System Environment.

Figure 4 TIBCO ActiveMatrix Messaging Server Information

Messaging Server Provider URL—The server URL used to create the connection factory. The default value is tcp://${machine name}:7222 where the {machine name} is the actual host name on which your TIBCO Enterprise Message Service Server is running.

The default setting for the Provider URL works in the following circumstances:

— All nodes created in the environment are colocated with the TIBCO Enterprise Message Server.

— The TIBCO Enterprise Message Service Server is configured to use the default port of 7222.

Messaging Server Name—A name that is unique across all messaging servers and shared resource definitions in all environments administered by the same TIBCO ActiveMatrix Administrator cluster. Names are not case-sensitive.

Messaging Server User Name—A user name used to create a connection to the connection factory.

Messaging Server Password—The password used to create a connection to the connection factory. If a password has not been defined, leave this field empty. The default password is <blank> or no password (that is, leave this field empty).



11. Click Next.

12. Specify information about the HTTP and JMS Shared resources to be used with the SPM system services.

Figure 5 TIBCO ActiveMatrix SPM System Services Shared Resources

HTTP Shared Resource Name—The name of the shared resource used to access HTTP messages.

HTTP Shared Resource port—The port used by HTTP Shared Resource for communication.

JMS Shared Resource Name—The name of the shared resource used for JMS configurations.

13. Click Next.

14. Configure TIBCO ActiveMatrix SPM System Services: Alert Server for delivering alert messages to users using Simple Mail Transfer Protocol (SMTP).

This configuration will be used for sending SPM alerts and the values provided for Alert SMTP user name, password, and address will be used as “From” for the alerts.

These configurations are not validated, ensure that you enter correct values.



Figure 6 TIBCO ActiveMatrix SPM System Services Alert Server

The values for TIBCO SMTP server are displayed by default in the above dialog. You must specify the values for your mail server to receive the alert messages.

Alert SMTP Server Name—The name of the SMTP server.

Alert SMTP Port—The port number used by SMTP for sending and receiving alerts.

Alert SMTP User—The user name of the SMTP server.

Alert SMTP Password—The password to authenticate the SMTP user.

Alert From Address—The email address configured for SMTP users.

Alert Max Per Digest—Maximum number of alerts that can be received as a digest.

Do not leave the Alert SMTP User and Password fields empty. If you do not want to specify authentication information, use the special value <unset> for both the username and password.



15. Configure the TIBCO ActiveMatrix SPM System Services: ActionManager service parameters.

Figure 7 TIBCO ActiveMatrix SPM System Services: Action Manager

High Rule Priority Threshold—Sets the % value for high rule priority threshold. The default value is 60. The email alert message will be sent with High importance for all the Rules set with High priority.

Low Rule Priority Threshold—Sets the % value for low rule priority threshold. The default value is 20. The email alert message will be sent with Low importance for all the Rules with low priority.

16. Click Next.

17. Configure the SPM ActionServices service parameters by specifying the following values:



Figure 8 TIBCO ActiveMatrix SPM System Services: ActionServices

Max Wait Time to Provision Node Service (in milliseconds)—The system waits for the specified amount of time for the Provision Node action to provide a new node.

ActiveMatrix Service Performance Manager allows you to associate the Provision Node action with a rule. When a condition in the rule is met, the associated action is triggered. See TIBCO ActiveMatrix Service Performance Manager User’s Guide for details.

Max Percentage JVM Available on Node to deploy services—The system checks for the percentage of JVM available on the node before deploying a service on it.

InvokeScript Service: Management Daemon JMX Protocol—The name of the JMX protocol to be used for invoking script on a remote machine. The JMX protocol can be used for invoking actions specific to BusinessWorks.

InvokeScript Service: Management Daemon JMX Port—The port on which JMX server is running.

Make sure that you configure the port even if you do not plan to use the Invoke Script action.



Management Port Range for ProvisionNode Service—The port numbers that can be used for running services on the newly provided nodes by the ProvisionNode action.

Min—The minimum value or the lowest bound for the port.

Max—The maximum value or the highest bound for the port.

Default HTTP Connector Port Range for ProvisionNode Service—The port numbers that can be used for HTTP communication.

Min—The minimum value or the lowest bound for the port.

Max—The maximum value or the highest bound for the port.

18. Click Next.

19. The Confirmation dialog displays the values of all the parameters.

Figure 9 Confirmation

20. Scroll and verify all the parameter values and then click Run.

The window displays logs of all scripts being executed. After running all the scripts successfully, the windows displays the message as “Build Successful” as shown below.



Figure 10 Running the Scripts

21. Click Close to close the window.

When the post installation task are completed successfully, the “BUILD SUCCESSFUL” message appears in the window.

Startup and Shutdown Scripts

After running the post-installation steps, the following scripts from the TIBCO_SPM_HOME/bin directory can be used for the system startup and shutdown.

• start_default.bat (or start_default.sh)—Starts the ActiveMatrix Service Performance Manager foundation servers.

If the Post-installation tool is aborted using Cancel or the post-installation tool fails, you need to clean up the environment using the procedure described in Appendix B, Troubleshooting, on page 99.



• stop_default.bat (or stop_default.sh)—Stops all the ActiveMatrix Service Performance Manager foundation servers.

Steps For the Existing ActiveMatrix Administrator Server

After running the post-installation tool with the existing Administrator Server, the system first deploys and starts the ActiveMatrix Service Performance Manager system services and in the end, it shuts down the SPM system node spmsysenv_spmsysnode.

So to start the ActiveMatrix Service Performance Manager foundation services, you must start the SPM system node from ActiveMatrix Administrator by selecting Configure an Environment > spmsysenv> spmsysenv_spmsysnode > Start.

Steps For the New ActiveMatrix Administrator Server

In the Post-Installation Configuration Tool, if you have selected the option to create New Administration Server (that is, unselected the Use existing Administrator Server option) in step 8, the system creates the TIBCO ActiveMatrix Administration server, deploys and starts the ActiveMatrix Service Performance Manager system services and shuts down all the services in the end.

To register the model changes in the database and to start the ActiveMatrix Service Performance Manager foundation services:

• Set the following properties to "True" in TIBCO_HOME\amxadministrator\data\amx\admin\bin\amx_admin.tra file as follows:

java.property.monitormanage.update.schema=Truejava.property.spm.update.schema=True

• Run the following command:

TIBCO_SPM_HOME\bin\start_default.bat (or start_default.sh)

The command starts the following services in different windows:

— TIBCO ActiveMatrix Database

— TIBCO ActiveMatrix Management Daemon

— TIBCO ActiveMatrix AdminServer

— TIBCO ActiveMatrix Service Performance Manager System Services node

Once you start the Admin Server and System Services node, you can use the same instance to monitor other ActiveMatrix runtime nodes or for running BW engines.



Steps For ActiveMatrix Administrator Server Cluster

If the ActiveMatrix Administrator is running in a cluster mode and you want to register multiple Administrator servers in the SPM environment, follow these steps:

1. Make sure that all ActiveMatrix Administrator Servers, Management Daemon, and SPM node are running.

2. Access the Deploy to an Environment perspective and select spmsysenv.

a. Select ActionManagerSA and click Deploy.

b. Select Substitution Variables and locate the following substitution variables:

— amx_admin_port

— amx_admin_host

c. Enter a comma (,) or semicolon (;) separated list of Administrator servers and corresponding ports in a sequential manner.

For example;

amx_admin_port=<machine1PortNumber>,<machine2PortNumber>

Do not close any of the above windows as closing a window stops the corresponding service.



amx_admin_host=<machine1>,<machine2>

d. Deploy ActionManagerSA and start it.

e. Similarly, update ActionServiceSA by repeating the above steps (a to c).

3. Edit SPM node tra file in TIBCO_HOME\amx\data\<SPM environment name>\<SPM node name>\bin\<SPM environment name>_<SPM node name>.tra file to add the following properties:

— spm.actions.node.recover.wait.time.milliseconds=30000

— spm.actions.node.recover.retry.count=4

4. Restart the SPM node.


Verifying Installation | 59

Verifying Installation

You can verify the installation by checking the following steps:

1. Click Start > Programs> TIBCO> TIBCO ActiveMatrix Service Performance Manager and make sure that Documentation and other menus exist.

2. Browse to TIBCO_HOME, the folder where TIBCO ActiveMatrix products are installed. Typically, TIBCO_HOME is c:\tibco. You can see the following directory structure after the product installation.

Table 4 SPM Directory Structure

Component Description

TIBCO_HOME\_installInfo The location where the installation information for TIBCO ActiveMatrix, Hibernate, and ActiveMatrix Service Performance Manager exists.

TIBCO_HOME\_uninstall The location where the universal installer exists.

TIBCO_AMX_HOME directory TIBCO ActiveMatrix install directory. For example, c:\tibco\amx.

TIBCO_HOME\amx The location where all files specific to TIBCO ActiveMatrix are stored.

TIBCO_HOME\amxadministrator(that is, AMX_ADMIN_HOME)

The location where all files and folders specific to ActiveMatrix Administrator are stored. It is specified as AMX_ADMIN_HOME.

TIBCO_HOME\components The location where the TIBCO ActiveMatrix design time components such as Eclipse are installed.

TIBCO_HOME\log The location where the logs related to TIBCO ActiveMatrix are stored.

TIBCO_HOME\managementdaemon The location where the configuration files, logs, and uninstallers related to management daemon are stored.

TIBCO_HOME\spm\1.3

(That is, TIBCO_SPM_HOME)

TIBCO ActiveMatrix Service Performance Manager install directory for version 1.3. This folder contains all the files and folders related to ActiveMatrix Service Performance Manager. It is referred as TIBCO_SPM_HOME in the documentation.



TIBCO_HOME\tibcojre The location where JRE is installed.

TIBCO_HOME\tools The location where the machine model is located.

TIBCO_HOME\uninstaller_archives The location where the information about product installation is stored that can be used during product uninstallation.

TIBCO_HOME\spm\logs The location where ActiveMatrix Service Performance Manager log files are created.

TIBCO_SPM_HOME\assemblies The location where service assemblies for Action Services, Action Manager, Alerts, and Rule Services are located.

TIBCO_SPM_HOME\bin The directory contains scripts to start TIBCO ActiveMatrix database, management daemon, Administrator Server, ActiveMatrix Service Performance Manager services, and system services node are installed.

TIBCO_SPM_HOME\doc The location where the ActiveMatrix Service Performance Manager documentation are installed. It contains the Installation and User’s Guide.

TIBCO_SPM_HOME\plugins The location where TIBCO BusinessWorks Service Probe configuration files are installed.

TIBCO_SPM_HOME\postinstalltool The location where the post-installation tool is installed. Use this tool to configure and setup SPM system services and run the SPM node.

TIBCO_SPM_HOME\samples The directory contains:

• The sample XML data files for the Command Line Interface (CLI). These sample XML files are based on the standard schema files. Using these sample files as a reference, you can generate the data files per your business requirement.

• Some utilities to facilitate integration of SPM with Spotfire, and also validation of Custom Metrics xpath expressions.

• The samples for email alert and SNMP alert templates.




3. After you install TIBCO ActiveMatrix Service Performance Manager and perform the post-installation tasks, you can see the environment, node, and services related ActiveMatrix Service Performance Manager installed on your machine.

In your browser’s address box, enter a URL of the following format:

http://<hostname>:<port>/amxadministrator

For example: http://amxserver.acme.com:8120/amxadministrator. The port is the HTTP port you specified for the ActiveMatrix Administrator server when you created it.

4. To access the ActiveMatrix Service Performance Manager perspectives, provide the following credentials:

Username: root

Password: tibco

TIBCO_SPM_HOME\schemas The location where the XSD files for the Command Line Interface are stored. It also contains a few sample files for CLI.

TIBCO_SPM_HOME\scripts The location where the scripts to deploy ActiveMatrix Service Performance Manager system services using the CLI are installed.

TIBCO_SPM_HOME\tutorial The location of the tutorial file and contents are: amx, bw, scripts.

TIBCO_SPM_HOME\uninstaller_archives

The location where ActiveMatrix Service Performance Manager uninstall programs are installed.

TIBCO_SPM_HOME\webapp The location where ActiveMatrix Service Performance Manager web applications are created.


The above credentials (root and tibco) are the default Administrator server authentication values. However, if you have used the non-default values for username/password (the values that you specified in the Post Installation Configuration tool) for Admin server, you must use those values to access the ActiveMatrix Service Performance Manager perspectives.



5. Click the Perspectives dropdown and make sure that the following perspectives that are specific to ActiveMatrix Service Performance Manager, appear in the dropdown list:

— Build and Configure Rules

— View and Manage Dashboards

Figure 11 ActiveMatrix Service Performance Manager Perspectives

6. Select the Configure Enterprise Assets perspective from the drop-down. The Environments table displays the spmsysenv environment specific to ActiveMatrix Service Performance Manager.



Figure 12 Configure Enterprise Assets > Environment spmsysenv

Click Configure an Environment from the Perspective drop-down and select spmsysenv from the Environment list.

Figure 13 Environment spmsysenv > Node spmsysenv_sysnode

All the ActiveMatrix Service Performance Manager services get deployed on a node spmsysenv_sys in the spmsysenv environment by default. You can change the default node or environment name by setting appropriate values in the Post-Installation Configuration Tool.

Figure 14 Deploy to an Environment > Service Assemblies in spmsysenv



The Service Assemblies table displays the following service assemblies specific to ActiveMatrix Service Performance Manager.

• ActionManagerSA

• AlertSA

• RuleServiceSA

• ActionServicesSA

TIBCO ActiveMatrix Service Performance Manager creates spmsysenv environment, spmsysenv_sysnode node, and deploys all the services specific to ActiveMatrix Service Performance Manager to this node.

It is recommended that you do not deploy any other business services to spmsysenv environment or spmsysenv_sysnode node.


Making the SPM Services Highly Available | 65

Making the SPM Services Highly Available

The service assemblies specific to ActiveMatrix Service Performance Manager can be made highly available. You can deploy the following service assemblies on multiple ActiveMatrix nodes:

• ActionManagerSA

• AlertSA

• ActionServicesSA

To make these services highly available, follow these steps:

1. Login to TIBCO ActiveMatrix Administrator.

2. Select the Deploy to an Environment from the Perspective drop-down.

3. Select the Environment spmsysenv.

4. From the Service Assemblies table, select one of the above SAs.

The details of the selected SA are displayed in the lower panel.

5. Click the Service Units tab.

6. From the Service Units table, select the JavaSU for that SA.

The Mapped Nodes table displays that the JavaSU is deployed on the default system node spmsysenv_sysnode.

7. Click the Edit button to map the service to different nodes than the default node.

— In the Node Mapping tab:

From the Mapped Nodes table, remove spmsysenv_sysnode.

From Available Nodes, select two nodes and add them into the Mapped Nodes table.

— Click Save.

8. Click the Redeploy button to deploy the SA on the newly mapped nodes.

9. Repeat the above steps for the remaining SAs.



Making the Rule Service Fault Tolerant

TIBCO ActiveMatrix Service Performance Manager provides the capability to run the RuleServiceJavaSU on multiple nodes and also provides a mechanism to run the Rule Service in primary and secondary modes.

The RuleServiceSA service assembly contains two service units:

• RuleServiceJavaSU—a Java component

• RuleServiceSOAPSU—a SOAP component.

The rule service engine runs inside the Java component. To achieve the load balance mechanism for the rule service, you need to deploy Rules Service Java SU on more than one node. Mapping the Java component to multiple nodes enables the fault tolerance mode for rule service.

When the RuleServiceJavaSU is mapped to two or more ActiveMatrix nodes, the first node starts the rule service in primary mode and the rest of the nodes are in the hot standby mode. If the primary node goes down or if the rule service on another node with higher priority comes up, another node with the next highest priority takes over as primary.

To make the RuleService fault tolerant, follow these steps:

1. Login to TIBCO ActiveMatrix Administrator.

2. Select the Deploy to an Environment from the Perspective drop-down.

3. Select the Environment spmenv.


Making the Rule Service Fault Tolerant | 67

Figure 15 Deploy to an Environment > spmenv

4. From the Service Assemblies table, select RuleServiceSA.

5. Click Undeploy.

6. Select RuleServiceSA.

The details of the selected RuleServiceSA are displayed in the lower panel.

7. Click the Service Units button.

8. From the Service Units table and select RuleServiceJavaSU.

The Mapped Nodes table displays that the RuleServiceJavaSU is deployed on the default system node spmsysenv_sysnode.

9. Click the Edit button to map the service to different nodes than the default node.

10. In the Node Mapping tab:

— From the Mapped Nodes table, remove spmsysenv_sysnode.

— From Available Nodes, select two nodes and add them into Mapped Nodes table.

— Click Save.

It is recommended that you select nodes on different machines for fault tolerance.



Figure 16 Mapping Nodes

11. Click General Settings > Substitution Variables and set the value of rule_service_in_ft_mode to true.

12. Optionally, you can inject additional properties to RuleServiceSA before redeploying the service assembly. See the section Adding Properties to Rule Service on page 68 for details.

13. Click the Deploy button to deploy the RuleServiceSA on the newly mapped nodes.

14. Click the Start button to start the RuleServiceSA.

Adding Properties to Rule Service

Rule service running on an ActiveMatrix node may need to be added with some additional properties when running in the fault tolerant mode.

For example, if a particular ActiveMatrix node needs to have a high priority all the time, you can set the priority property, be.ft.priority, to a lower value in the rs.properties file. It ensures that the rule service running on that node always gets the primary role even after it goes down at some point and the secondary takes over. In such case, the node with the highest priority will always be primary irrespective of the order in which the ActiveMatrix nodes are started. Typically, a powerful machine (machine 1) is always assigned as Primary and less powerful machines (machines 2 and 3) as Secondaries. For some reason if the primary (machine 1) goes down, the secondary (machine 2 or 3) will become the primary. Eventually, when the machine 1 comes up, it takes over as Primary if it is assigned with lower priority value.

To add properties to the engine running in the rule service, follow these steps:

1. Open the sample properties file rs.properties available in the TIBCO_SPM_HOME\samples directory.



2. Add the required properties in the sample properties file from the following list.

3. Copy the rs.properties file to the machine where the node with rule service is running.

4. Edit the node tra file in TIBCO_HOME\amx\data\<environment>\<node>\bin folder and add the following parameter:

java.property.spm.ruleservice.additional.props=<path>/rs.properties

5. For the properties to take effect, restart the node with the rule service.

Primary Node, Secondary Node, and Failover

• TIBCO ActiveMatrix Service Performance Manager always runs the rule service in standalone mode. To run the rule service on multiple nodes in fault tolerant mode, configure it on multiple nodes and set the substitution variable rule_service_in_ft_mode to true.

• The first node that starts the rule service is called the primary node. You can identify whether a rule service instance deployed on a node is primary or secondary from the log files. The user interface does not show any distinction between an Active and Inactive rule service node.

• All the subsequent nodes started after the first node and with the rule service deployed on them are called secondary nodes. The secondary nodes are in

Table 5 Additional Properties

Property Name Description

be.ft.priority=10 Sets the machine priority. The lower the number the higher the priority.

tangosol.coherence.clusteraddress=239.192.20.125

tangosol.coherence.clusterport=15972

tangosol.coherence.cluster=myCluster

Specifies the cluster address properties to avoid the rule service clashing with other installations. You can use it for multicast node discovery. These properties can be used if the rule service is deployed on different machines on the same subnet.

tangosol.coherence.wka1=10.97.107.11

tangosol.coherence.wka1.port=16222

tangosol.coherence.wka2=10.97.112.103

tangosol.coherence.wka2.port=17222

tangosol.coherence.localhost=10.97.107.11

tangosol.coherence.localport=16222

Specifies well-known address values for unicast communication. These properties can be used if the rule service is deployed on different machines on different subnets.



standby mode. The user interface shows that the Service Unit deployed on the secondary node is Running. The log file spm.log of the node available in the TIBCO_HOME\amx\data provides information about how the rule service instance was started.

• During failover, if the rule service instance running on the primary node is stopped or the ActiveMatrix node is stopped, one of the rule service instances running on the secondary node takes over and becomes the primary. The secondary server starts and continues to process the messages.

• In cases where the primary and secondary are on different machines on the network, the secondary takes over if the primary loses connection to the network.

When a node restarts (or reconnects to the network in the case of a lost connection), it assumes responsibility from the node with the next lowest priority. So, when a primary engine recovers, it takes over from the secondary that had been functioning as primary.

• However, when the original primary server comes up, it doesn’t get the primary state by default. This is because all the ActiveMatrix nodes are assigned with the priority 10 by default.

If you want to assign the most powerful machine as a primary server, set the java.property.spm.ruleservice.priority to "1” in the node TRA file where the rule service is deployed. The <node>.tra file for any node exists in the TIBCO_HOME\amx\data\<environment>\<environment>_<node>\bin folder.

If the original primary server’s TRA has “java.property.spm.ruleservice.priority=1”, every time the machine comes up, it goes back to become the primary server.

Example: Deploying Rule Service on three Nodes from Different Machines in Different Subnet

Here is the procedure to deploy a rule service on three nodes from different machines in a different subnet.

Prerequisites:

• ActiveMatrix Service Performance Manager Foundation Servers (database, management daemon, TIBCO Administrator server, SPM node and system services) up and running on Machine1

• ActiveMatrix Service Performance Manager installed on to Machine2 which is in a different subnet and Management daemon is running.



• ActiveMatrix Service Performance Manager installed on to Machine3 which is in a different subnet than Machine1 and Machine2 and the Management daemon is running.

1. In ActiveMatrix Administrator, bind Machine2 and Machine3 with Machine1 and enable the machines for the <spm_system_environment> environment.

2. Make sure that ActiveMatrix Service Performance Manager system services are up and running on the <spmsysenv_sysnode> node.

3. In ActiveMatrix Service Performance Manager environment <spm_system_environment>, create the following new nodes:

— node spmsysnode-s1 on Machine1



4. Copy the sample properties file TIBCO_SPM_HOME\samples\rs.properties to the machines Machine1, Machine2 and Machine3 where the node with the rule service is running.

5. Add the following properties to the rs.properties file copied to each machine.

rs.properties on Machine1 for spmsysnode-s1:

tangosol.coherence.wka1=10.97.107.11tangosol.coherence.wka1.port=16222tangosol.coherence.wka2=10.97.112.103tangosol.coherence.wka2.port=17222tangosol.coherence.wka3=10.97.109.14tangosol.coherence.wka3.port=18222tangosol.coherence.localhost=10.97.107.11tangosol.coherence.localport=16222


tangosol.coherence.wka1=10.97.107.11tangosol.coherence.wka1.port=16222tangosol.coherence.wka2=10.97.112.103tangosol.coherence.wka2.port=17222tangosol.coherence.wka3=10.97.109.14tangosol.coherence.wka3.port=18222tangosol.coherence.localhost=10.97.112.103tangosol.coherence.localport=17222


tangosol.coherence.wka1=10.97.107.11tangosol.coherence.wka1.port=16222tangosol.coherence.wka2=10.97.112.103tangosol.coherence.wka2.port=17222tangosol.coherence.wka3=10.97.109.14tangosol.coherence.wka3.port=18222



tangosol.coherence.localhost=10.97.109.14tangosol.coherence.localport=18222

6. Add the following property in spmsysnode-s1, spmsysnode-s2, and spmsysnode-s3 node tra files:

java.property.spm.ruleservice.additional.props=<path to rs.properties file>

7. Start the pmsysnode-s1, spmsysnode-s2, and spmsysnode-s3 nodes.

8. Undeploy the RuleServiceSA.

9. Select RuleServiceSA in the <spm_system_environment>.

— Map the service unit RuleServiceJavaSU with spmsysnode-s1, spmsysnode-s2, and spmsysnode-s3. Remove the mapping with spmsysenv_sysnode node.

— Click General Settings > Substitution Variables and set the value of rule_service_in_ft_mode to true.

— Save the changes.

10. Deploy and start the RuleServiceSA.


Installing and Configuring BusinessWorks Service Probe | 73

Installing and Configuring BusinessWorks Service Probe

TIBCO ActiveMatrix Service Performance Manager allows you to monitor BusinessWorks web services. For details on the supported versions, refer to product readme at TIBCO_SPM_HOME/readme.

By installing and configuring only the BusinessWorks Service Probe on the machine on which BusinessWorks is installed, the following BusinessWorks activities can be monitored:

• Service (Web services over HTTP and JMS)

• SOAP Events Source

• SOAP Request Reply

• Invoke Partner

The installation and configuration instructions differ for a new or existing setup of TIBCO BusinessWorks.

Based on your requirement, refer to the following sections for details.

• For New Installation or Deployment of BusinessWorks

• For Existing BusinessWorks Deployments

Consider the following points while using the BusinessWorks Service Probe:

• When you install BusinessWorks Service Probe (as part of ActiveMatrix Service Performance Manager installation) on the machine where TIBCO BusinessWorks is installed, the probe edits the bwengine.tra file to set the path of TIBCO_SPM_HOME.

• If you install a new version of TIBCO ActiveMatrix Service Performance Manager and want to revert to the previous version of ActiveMatrix Service Performance Manager, you must edit bwengine.tra file and set the correct values for TIBCO_SPM_HOME and the corresponding jar files versions in the following properties:— tibco.env.CUSTOM_EXT_PREPEND_CP

— tibco.env.SPM_PROBE_CP

The following steps assume that you have installed the BusinessWorks Service Probe component of TIBCO ActiveMatrix Service Performance Manager on the machine where TIBCO BusinessWorks is installed.

For changes in the bwengine.tra to take effect, you need to restart the BusinessWorks engine.



• If you make any modifications in the bwengine.tra file, make sure that the TIBCO_SPM_HOME variable is defined before using it in any subsequent property definition.

• To trigger BusinessWorks specific custom actions, the TIBCO ActiveMatrix management daemon must be up and running on all the machines where the BusinessWorks service probe is installed.

For New Installation or Deployment of BusinessWorks

1. Make sure that the following software is installed on your machine:

— TIBCO BusinessWorks

— TIBCO Administrator

2. If TIBCO BusinessWorks is installed after ActiveMatrix Service Performance Manager installation on the same machine, run the command:

TIBCO_SPM_HOME/bin/spmcmdline.bat TIBCO_SPM_HOME/scripts/updatespm.xml post.install.tasks.bwserviceprobe

3. Create the TIBCO Administrator domain if it does not exist.

4. Edit TIBCO_SPM_HOME\plugins\bwserviceagent.properties to provide following information:

For TIBCO ActiveMatrix Administrator Server:amx_admin_server_urls=http://localhost:8120

amx_admin_server_auth_username=root

amx_admin_server_auth_password=<obfuscated root password>

If TIBCO BusinessWorks is installed after installing only the ’BusinessWorks Service Probe’ component (as part of ActiveMatrix Service Performance Manager installation), you need to run the following command:

TIBCO_HOME\tools\bin\tibcommander TIBCO_SPM_HOME\scripts\updatespm.xml post.install.tasks.bwserviceprobe

For Windows 64 bit, you must reinstall all the ActiveMatrix Service Performance Manager components that were installed before installing TIBCO BusinessWorks.

That is, if you have installed only the ’ServiceProbe for BusinessWorks’ component of ActiveMatrix Service Performance Manager before installing ActiveMatrix BusinessWorks, reinstall only the ’Service Probe for BusinessWorks’ component after TIBCO Business Works installation.



#Custom Metrics Enable/Disable:serviceprobe.custommetrics.enable=true

5. If ActiveMatrix Service Performance Manager Server and TIBCO BusinessWorks Service Probe are running on two different machines, ensure you modify your Monitoring Configuration (on the ActiveMatrix Service Performance Manager Server) as follows:

Make sure that the Monitoring Configuration's JMS shared resource uses the host name of the JMS Server instead of the localhost.

6. To run BusinessWorks Service Probe and start publishing statistics:

a. Start ActiveMatrix Service Performance Manager Server (Make sure that at least the TIBCO ActiveMatrix database and TIBCO Enterprise Message Service server are started).

b. Start TIBCO Administrator and the Hawk Agent.

c. Deploy and start the BusinessWorks project.

You can see the published statistics message using TIBCO_EMS_HOME\bin\tibemsmonitor -m Q.r.activematrix.stats.amx

where amx is the TIBCO ActiveMatrix Admin Cluster Name.

For Existing BusinessWorks Deployments

1. Edit TIBCO_SPM_HOME/plugins/bwserviceagent.properties to provide the following information:

For TIBCO ActiveMatrix Administrator Server:amx_admin_server_urls=http://localhost:8120

amx_admin_server_auth_username=root

amx_admin_server_auth_password=<obfuscated root password>

#Custom Metrics Enable/Disable:serviceprobe.custommetrics.enable=true

Note that only URLs of ActiveMatrix Administrator servers that exist in the same cluster can be specified for amx_admin_server_urls.

For the amx_admin_server_urls parameter, you can specify multiple URLs separated by a delimiter. The default value of the delimiter is "; " (semicolon) that can be changed using the amx_admin_server_url_delimeter parameter.

For amx_admin_server_urls, you can specify multiple URLs separated by "; " delimiter. The default value of delimiter is ";" (semicolon) that can be changed using the amx_admin_server_url_delimeter parameter.



2. If ActiveMatrix Service Performance Manager Server and BusinessWorks Service Probe are running on different machines, make sure to modify your Monitoring Configuration (on the ActiveMatrix Service Performance Manager Server) as follows:

a. Make sure that the Monitoring Configuration's JMS Shared resource is using the JMS Server host name instead of local host.

b. From the TIBCO BusinessWorks Administrator, stop the BusinessWorks applications that you want to monitor.

3. To run BusinessWorks Service Probe and start publishing statistics:

a. Make sure that ActiveMatrix Service Performance Manager System Services is started (at least, the TIBCO ActiveMatrix Administrator Server and TIBCO Enterprise Message Service server must be started).

b. Restart the BusinessWorks applications.

Enabling or Disabling the BusinessWorks Service Probe from TIBCO Administrator

To enable or disable BusinessWorks Service Probe from TIBCO Administrator, you need to make changes to bwengine.tra and bwengine.xml file as follows:

1. Backup the deployed BusinessWorks engine tra files so it can be replaced after installing ActiveMatrix BusinessWorks Service Probe (as part of ActiveMatrix Service Performance Manager installation). This is because the ActiveMatrix Service Performance Manager installer updates all deployed engine tra files to enable probe.

2. Install ActiveMatrix BusinessWorks Service Probe.

Installer updates TIBCO_HOME/bw/<version>/bin/bwengine.tra to include SPM probe classes and properties.

3. Go to TIBCO_HOME/bw/<version>/bin/bwengine.tra and comment out the following two lines.

ServiceAgent.SPM.Class=com.tibco.matrix.spm.bw.monitoring.serviceagent.SPMServiceAgent# com.tibco.matrix.spm.bw.service.agent.tra=%SPM_HOME%/plugins/bwserviceagent.properties

This step should be executed on each server that has ActiveMatrix BusinessWorks Service Probe (as part of ActiveMatrix Service Performance Manager installation) installed.



4. Update TIBCO_HOME/bw/<version>/lib/com/tibco/deployment/bwengine.xml to include following two properties. This step should be executed on each machine used to create EAR file.

<property> <name>SPM Probe class name</name> <option>ServiceAgent.SPM.Class</option> <default></default> <description>SPM Probe class name</description></property><property> <name>SPM Probe TRA file location</name> <option>com.tibco.matrix.spm.bw.service.agent.tra</option> <default></default> <description>SPM probe TRA file location</description></property>

5. Create the EAR file.

6. Upload the EAR file through TIBCO Administrator.



7. To enable the SPM service probe for this engine, go to PAR configuration and specify appropriate values for the following properties:— Service.Agent.SPM.Class

— com.tibco.matrix.spm.service.agent.tra

Here the values used are

ServiceAgent.SPM.Class=com.tibco.matrix.spm.bw.monitoring.serviceagent.SPMServiceAgent

com.tibco.matrix.spm.bw.service.agent.tra=%SPM_HOME%/plugins/bwserviceagent.properties

As %SPM_HOME% is already in TIBCO_HOME/bw/<version>/bin/bwengine.tra (updated by ActiveMatrix Service Performance Manager installer), you can use %SPM_HOME% to specify value for service agent tra file location.

8. Deploy and start you application.

To disable the SPM probe, keep the values for these two properties blank.



If SPM probe is turned On, you can see TIBCO Enterprise Message Service connections from this BW engine to SPM-EMS. Also, the service appears in the SPM dashboard after the service is invoked.



Common Logging Configuration

TIBCO ActiveMatrix Service Performance Manager supports Common Logging to log the event messages published from the Service Probe into the node logger.

Follow these steps to configure the Log service:

1. Open the file TIBCO_HOME\amx\data\%ENVIRONMENT%\%NODE%\config\bootStrap.xml for editing for all nodes.

2. Look for the following line at the end of the file:“” (almost at the end of the file).

3. Add the following section below the line.

 <logger name="com.tibco.matrix.spm.serviceprobe.CommonLoggingJMSSinkOutputHandler" additivity="false" ><level value ="INFO"/> <appender-ref ref="_%ENVIRONMENT%.%NODE%_appender"/> </logger> 

4. Make sure to substitute %ENVIRONMENT% and %NODE% with the environment and node name.

5. Select Configure Enterprise Assets from the Perspective drop-down list.

6. Click the Administrator Cluster link.

7. Click the Log Service link.

8. Click the New button.

9. Edit the JDBC Connection and JMS Connection fields according to the descriptions provided in the following table.

Table 6 Common Logging Configuration

Field Description

JDBC Connection

The database where log entries are stored. A drop-down list contains the existing JDBC shared resource definitions. Before selecting a connection you must configure a JDBC shared resource definition. If you want the JDBC shared resource definition to use a log datastore in the HSQLDB database, you must first configure the HSQLDB datastore.

JMS Connection

The JMS connection on which all the administrator servers in a cluster receive log entries. A drop-down list displays the existing JMS shared resource definitions. Before selecting a connection you must configure a JMS shared resource definition.


Common Logging Configuration | 81

10. Click Save and Start.

11. Restart the Log Service plug-in by navigating to Configure Enterprise Assets > Administrator Cluster > Plug-ins.

See ’Chapter 10 - Managing Logging’ in the TIBCO ActiveMatrix Administration guide for more information.

You see an spm.log in the TIBCO_AMX_HOME>/amx/data/<environment>/<node name>/logs directory.

Configuration to Log Events

To log events from the Rule Builder, follow these steps:

1. Access Configure Enterprise Assets > Administrator Cluster > Log Services and create a new log service. Either create your own JMS and JDBC connections under the Shared Resource Definitions or use the Monitoring JMS Configuration and Quartz JDBC Configuration provided by ActiveMatrix Service Performance Manager.

Add all of the Available Models to the Selected Models.

2. Set the new log service to default.

3. Start the new log service.

4. Restart the Log Service plug-in by navigating to Configure Enterprise Assets > Administrator Cluster > Plug-ins > TIBCO Common Logging.

5. Access the Configure an Environment perspective and select the spmsysenv environment.



Select the spmsysenv_sysnode and in the Logging Configurations area and edit the spmsysenv_sysnode configuration to assign the values:

— Severity—Info

— Appender — JMS

Click Apply.

6. Access the Deploy to an Environment perspective and select the spmsysenv environment.

Select the ActionManagerSA and in the Logging Configurations area, edit the ActionManagerSA configuration to assign the values:

— Severity—Info

— Appender — JMS

Click Apply.

7. Restart the SPM system node spmsysenv_sysnode.

8. Modify bootstrap.xml by taking the following steps:

a. At the spmsysenv_sysnode command line, type "generate_log_config".

The generated logging configuration will be located at TIBCO_HOME\amx\data\spmsysenv\spmsysenv_sysnode\generated\ma

trix-log4j.xml.

b. In TIBCO_HOME\amx\data\spmsysenv\spmsysenv_sysnode\config\bootstrap.xml search for the logger "com.tibco.matrix.spm.rule.log". The entry will look similar to the following:

<logger additivity="false" name="com.tibco.matrix.spm.rule.log"><level value="OFF"/></logger>

c. Modify this logger to match the following:

<logger additivity="false" name="com.tibco.matrix.spm.rule.log"><level value="INFO"/><appender-ref ref="_ActionManagerSA_appender"/></logger>

d. Verify that the name of the appender-ref ref matches the ActionManagerSA appender name in the generated matrix-log4j.xml in step 6a. Look under '<hierarchy name="ActionManagerSA.ActionManagerJavaSU">'. If they do not match change the appender-ref ref to match the appender name.

9. Optionally for TIBCO Spotfire integration, if you want to log statistics to the database, add the following to bootstrap.xml:


Common Logging Configuration | 83

<logger additivity="false" name="com.tibco.matrix.spm.ruleservice.agent.stats"><level value="OFF"/><appender-ref ref="_spmsysenv.spmsysenv_sysnode_appender"/></logger>

See Appendix D - Integration with TIBCO Spotfire in TIBCO ActiveMatrix Service Performance Manager User’s Guide for details.

10. Restart the SPM system node.



Scalability Guidelines

TIBCO ActiveMatrix Service Performance Manager can be deployed in a distributed manner. Using the custom installation option, the following components can be installed on separate machines:

• Administrator

• Service Probe for TIBCO ActiveMatrix

• Service Probe for TIBCO BusinessWorks

• System Services

For example,

• On Machine 1, you can install the following components of TIBCO ActiveMatrix Service Performance Manager:

— Administrator

— Sytem Services

• On Machine 2, you can install the following components of TIBCO ActiveMatrix Service Performance Manager:

— Administrator

— Service Probe for TIBCO ActiveMatrix

— System Services

• On Machine 3, you can install:

— TIBCO ActiveMatrix Service Grid

— TIBCO BusinessWorks

— Service Probe for TIBCO ActiveMatrix (component of TIBCO ActiveMatrix Service Performance Manager)

— Service Probe for TIBCO BusinessWorks (component of TIBCO ActiveMatrix Service Performance Manager)

To set up the ActiveMatrix Service Performance Manager runtime (that is, SPM node and system services) on machine 2, run the Post Installation tool and use the existing ActiveMatrix Administartor Server running on Machine1.


Scalability Guidelines | 85

In the above setup:

• ActiveMatrix Administrator is on Machine1,

• SPM Node and system services are on Machine 2, and

• Monitoring objects for ActiveMatrix and/or BusinessWorks are on Machine 3.

The ActiveMatrix Service Performance Manager System Services contain the following service assemblies:

• RuleServiceSA

• ActionManagerSA

• AlertManagerSA

• ActionServiceSA

To make these services fault tolerant and highly available, refer to Making the SPM Services Highly Available on page 65 and Making the Rule Service Fault Tolerant on page 66.



Uninstalling the Software

If you have multiple TIBCO ActiveMatrix products installed, the installer shows uninstall options for each product. See TIBCO ActiveMatrix Installation for details about uninstalling ActiveMatrix products.

Following procedure explains how to uninstall the TIBCO ActiveMatrix Service Performance Manager.

1. Perform the following steps before un-installing ActiveMatrix Service Performance Manager:

a. Make sure that SPM foundation servers are up and running.

b. Remove the tasks performed by the Post Installation Configuration Tool by running the following command:

<spm_home>\bin>spmcmdline ..\scripts\spm_bootstrap.xml spm-e2b

This command cleans up the SPM environment in TIBCO ActiveMatrix Administrator.

c. If you want to delete the ActiveMatrix administrator server that was created using the Post Installation Configuration Tool, run the following command:

First, make sure that ActiveMatrix Administrator is stopped and database is running.

<tibco_home>\amxadministrator\<amx_version>\bin> deleteadminserver.exe ..\..\data\<cluster_name>_<server_name>.xml

This command deletes the ActiveMatrix administrator server.

d. Stop all TIBCO services while running the uninstaller.

e. If you have installed ActiveMatrix Service Performance Manager over existing TIBCO ActiveMatrix products, remove SPM references from admin.tra, node.tra, and amx_osgi.properties files by running the following command from TIBCO_SPM_HOME\scripts folder:

..\bin\spmcmdline.bat updatespm.xml pre.uninstall.tasks

2. Navigate to TIBCO_HOME\_uninstall directory and run universal_uninstall.

The wizard provides uninstall options for all ActiveMatrix products.

The steps differ based on whether you have installed TIBCO ActiveMatrix products or TIBCO BusinessWorks before installing ActiveMatrix Service Performance Manager.


Uninstalling the Software | 87

3. Select the check box for the products that need to be uninstalled and click Uninstall.

4. When uninstalling, popup windows display warnings indicating that update files will be deleted.

Click Yes to All to remove the file and subsequent files in the assembly. The popup windows are generated for each installed assembly so you may see multiple popup windows.

The summary screen appears.

5. Click Finish to exit the uninstall wizard.— After running the uninstaller, manually delete the following directories

under TIBCO_HOME:

— spm

— amx

— amxadministrator

— log

— managementdaemon

— tools

— components

— tibcojre

6. If you have installed ActiveMatrix Service Performance Manager over existing TIBCO ActiveMatrix products, uninstall the SPM plug-in from TIBCO ActiveMatrix Administrator as follows:

— Select Configure Enterprise Assets > Administrator Cluster > Plug-ins.

— From the Plug-ins area, select TIBCO ActiveMatrix Service Performance Manager and click the Stop button.

— Select Undeploy to undeploy the plug-in.

— Delete spmui.war and rajax.war from the TIBCO_HOME\amxadministrator\plugins folder.

If your have installed ActiveMatrix Service Performance Manager over existing TIBCO ActiveMatrix products, do not delete any other folder than the ‘spm’ folder as it can break your existing ActiveMatrix setup.




| 89

Appendix A Performing the Post Installation from the Command-line or Manually

This appendix provides manual steps to perform post installation tasks after installing ActiveMatrix Service Performance Manager. These steps can be performed if you do not intend to use the Post Installation Configuration Tool.

Topics

• Performing Post Installation Steps From the Command Line, page 90

• Performing the Post Installation Manually, page 94


90 | Appendix A Performing the Post Installation from the Command-line or Manually

Performing Post Installation Steps From the Command Line

To get the ActiveMatrix Service Performance Manager services up and running, perform the following steps:

1. Access TIBCO_SPM_HOME\scripts.

2. Copy data.properties-template to data.properties.

3. In the data.properties and login.properties files, the default Admin server authentication values for username is root and password is tibco.

For example, the authentication values in data.properties are set as follows:ADMIN_USER_NAME=rootADMIN_USER_PASSWORD=tibco

If you do not want to use these default authentication properties for Admin server, update all the occurrences of Admin username and obfuscated password in data.properties and login.properties files.

To know how to create an obfuscated password, see Creating an Obfuscated Password on page 93.

4. Edit data.properties to specify values for the following property:

— messagingServer.providerUrl=tcp\://<machine name>:7222

5. Start TIBCO Enterprise Message Service as follows:

— On Windows, click Start > Run > services.msc.

The Services dialog appears.

— In the Services dialog, select TIBCO Enterprise Message Service server on the ports specified in data.properties. For example, TIBCO EMS Server (PID:xxxx).

— Right-click and select Start.

6. Based on your existing setup, execute one of the following tasks:

• For an existing AMX Admin Server Setup on page 91

• For a New Setup, page 92


Performing Post Installation Steps From the Command Line | 91

For an existingAMX Admin

Server Setup

Task A To use an existing ActiveMatrix Administrator server:

a. Start the following services either from the Windows Services dialog or from the command line:

— TIBCO ActiveMatrix Database

On Windows, click Start > All Programs > TIBCO > TIBCO ActiveMatrix > Start HSQLDB Server.

From the command line on all platforms, run TIBCO_HOME/amx/hsqldb/bin/amx-db.

— TIBCO ActiveMatrix Management Daemon

On Windows, click All Programs > TIBCO > TIBCO Management Daemon > Management Daemon.

From the command line on all platforms, execute TIBCO_HOME/managementdaemon/<version>/bin/managementdaemon

— TIBCO ActiveMatrix Administrator server

To start the ActiveMatrix Administrator server, run TIBCO_HOME/amxadministrator/<version>/bin/amx_admin

b. Verify the default values set in the data.properties and login.properties files. You may need to change the values if you are not using the default values in your ActiveMatrix setup.

c. If you plan to use an existing ActiveMatrix Administrator Server that is SSL enabled,

— Modify the adminURL property in TIBCO_HOME\spm\<version>\scripts\login.properties to use https instead of http.

— Import the Administrator server’s certificate into JRE’s keystore:

keytool -keystore TIBCO_HOME\jre\<version> -import -file servercert -storepass changeit



d. Run the following commands from TIBCO_SPM_HOME\bin:

— spmcmdline.bat TIBCO_SPM_HOME\scripts\spm_bootstrap.xml pre-node-startup

(Use spmcmdline.bat (for Windows) and spmcmdline.sh (for UNIX))

This command installs and uploads the service assemblies required to run TIBCO ActiveMatrix Service Performance Manager.

— Manually start the SPM System node. The default name of SPM System node is spmsysenv_sysnode.

— spmcmdline.bat TIBCO_SPM_HOME\scripts\spm_bootstrap.xml post-node-startup

This command deploys the service assemblies and starts ActiveMatrix Service Performance Manager services.

Optionally, the above three steps can be performed by running the following command:

spmcmdline.bat TIBCO_SPM_HOME\scripts\spm_bootstrap.xml spm-e2e

For a New Setup Task B For a New Setup

a. Set the correct values in the data.properties and login.properties files. You may need to change the values if you are not using the default values in your ActiveMatrix setup.

b. Run the following command from TIBCO_SPM_HOME\bin:

spmcmdline.bat TIBCO_SPM_HOME\scripts\build_runtime_setup.xml

Running the above script generates the spmcmdline.log file inside the TIBCO_SPM_HOME/logs directory.

The command creates the TIBCO ActiveMatrix Administration server, deploys and starts the ActiveMatrix Service Performance Manager system services and shuts down the services in the end.

Here after, to start and stop all required services, use the scripts in the TIBCO_SPM_HOME/bin directory:

— TIBCO_SPM_HOME\bin\start_default.bat (or start_default.sh)

— TIBCO_SPM_HOME\bin\stop_default.bat (or stop_default.sh)

To start all required services, run the following command:

Do not run build_runtime_setup.xml specified in the next step if you are using the existing ActiveMatrix Administrator server.


Performing Post Installation Steps From the Command Line | 93

TIBCO_SPM_HOME\bin\start_default.bat (or start_default.sh)

For more information, see Steps For the New ActiveMatrix Administrator Server on page 56.

Creating an Obfuscated Password

To create an obfuscated password:

1. Run AMX_ADMIN_HOME/<version>/bin/passwordobfuscator password, where password is the password you want to obfuscate, in a terminal window. The obfuscator will output the following:

Encrypted password, contained in brackets: [#!LjNSm/lIwW7uwiLvcZQwuA==]

Cleaning the SPM Environment

If the post-installation is aborted or the post-installation fails, you need to clean up the environment using the following procedure.

1. Make sure that SPM foundation servers are up and running.

2. Remove the tasks performed by the post-installation by running the following command:

<spm_home>\bin>spmcmdline ..\scripts\spm_bootstrap.xml spm-e2b

This command cleans up the SPM environment in TIBCO ActiveMatrix Administrator.

3. If you want to delete the existing ActiveMatrix Administrator Server, run the deleteadminserver.exe command,



This command deletes the ActiveMatrix administrator server.

Optionally, you can clean the environment manually using the procedure described in Appendix B, Troubleshooting, on page 99.



Performing the Post Installation Manually

If you do not plan to use the TIBCO ActiveMatrix Service Performance Manager Post Installation Configuration tool, perform the following steps to manually deploy and configure the ActiveMatrix Service Performance Manager system services.

Pre-requisites

• ActiveMatrix Administrator server is already created using the TIBCO ActiveMatrix Administrator Creation Wizard or from the command line

• Database used for ActiveMatrix Administrator, ActiveMatrix Administrator Server, and Management Daemon are running

• TIBCO Enterprise Message Service (EMS) is running

Procedure

Task A Disable Monitoring

To avoid TIBCO ActiveMatrix Manager running on both ActiveMatrix Administrator server and the SPM system node at the same time, disable monitoring from TIBCO ActiveMatrix Administrator > Configure Enterprise Assets > Administrator Cluster > Monitoring Configuring settings.

Task B Create SPM System Environment

To deploy ActiveMatrix Service Performance Manager system services, create a new TIBCO ActiveMatrix environment named SPMSysEnv from TIBCO ActiveMatrix Administrator > Configure Enterprise Assets > Environment Definitions.

It is recommended that you create a new ActiveMatrix environment for ActiveMatrix Service Performance Manager and do not use any existing ActiveMatrix environments.


Performing the Post Installation Manually | 95

Task C Create SPM System Node

In theActiveMatrix Service Performance Manager environment SPMSysEnv, create a new node named SPMSysNode from TIBCO ActiveMatrix Administrator > Configure an Environment > SPMSysEnv > Node > New.

Task D Start SPM System Node

For the new node SPMSysNode, enter values for Messaging Server, Management Port, Product, and Default Connector based on the machine on which ActiveMatrix Service Performance Manager is installed.

Once the configuration of the ActiveMatrix Service Performance Manager system node is complete, click Install from TIBCO ActiveMatrix Administrator > Configure an Environment > SPMSysEnv > Node.

Task E Create Shared Resources and Associate with SPM System Node

• From TIBCO ActiveMatrix Administrator > Configure Enterprise Assets > Shared Resource Definitions, create a JMS, JDBC, and HTTP shared resource.

• Associate JDBC and HTTP shared resource with SPM system environment from TIBCO ActiveMatrix Administrator > Configure an Environment > SPMSysEnv > Shared Resource Definition.

• Install JDBC and HTTP shared resources on the SPM system node from TIBCO ActiveMatrix Administrator > Configure an Environment > SPMSysEnv > Nodes > Shared Resource.

• Map JMS shared resource to TIBCO Enterprise Message Service that will be used to enable monitoring.

• Map JDBC shared resource to the database that is used for ActiveMatrix Administrator.

Task F Upload SPM Service Assemblies

Upload RuleServiceSA, ActionManagerSA, AlertSA, ActionServicesSA from TIBCO_SPM_HOME\assemblies from TIBCO ActiveMatrix Administrator > Deploy to an Environment > SPMSysEnv.

Make sure that you do not deploy any services other than ActiveMatrix Service Performance Manager on this node.

Do not auto-import shared resources by clearing the Import Shared Resource Definition option on the Browse to Upload Service Assemblies Archive File dialog.



Task G Configure SPM Service Assemblies

• Map all service units of ActionManagerSA, ActionServiceSA, AlertSA, and RuleServiceSA to the SPM system node SPMSysNode from TIBCO ActiveMatrix Administrator > Deploy to an Environment > SPMSysEnv > Service Assemblies > <Service Assembly> > Service Units.

• Map HTTP shared resource installed into SPMSysEnv node in the previous step to SPM service assemblies except for ActionServicesSA from TIBCO ActiveMatrix Administrator > Deploy to an Environment > SPMSysEnv > ServiceAssemblies > <Service Assembly> > Shared Resource Profiles.

• Map JDBC shared resource installed into SPMSysEnv node in the previous step to SPM service assembly ActionManagerSA from TIBCO ActiveMatrix Administrator > Deploy to an Environment > SPMSysEnv > Service Assemblies > <Service Assembly> > Shared Resource Profiles.

Figure 17 Mapping Shared Resources

• Configure substitution variables as necessary from TIBCO ActiveMatrix Administrator > Deploy to an Environment > SPMSysEnv > Service Assemblies > <Service Assembly> > Substitution Variables.

For the AmxAdminPassword substitution variable, obfuscate the password for ActiveMatrix Administrator using passwordobfuscator in TIBCO_HOME/amxadministrator\<version>/bin.

Even though RuleServiceSA displays both RuleServiceSA and ActionManagerSA substitution variables, and ActionManagerSA displays ActionManagerSA, AlertSA, and ActionServiceSA substitution variables, you need to configure only substitution variables relevant to the service assembly.


Performing the Post Installation Manually | 97

Also for the /com.tibco.alert.delivery.composite/Shared Resources/SubstitutionVariables/password in AlertSA use passwordobfuscator.

Task H Deploy and Start SPM Service Assemblies

Deploy all service assemblies (ActionManagerSA, ActionServiceSA, AlertSA, and RuleServiceSA) from TIBCO ActiveMatrix Administrator > Deploy to an Environment > SPMSysEnv > Service Assemblies > <Service Assembly> > Deploy and Start them.



Task I Enable Monitoring

Enable monitoring from TIBCO ActiveMatrix Administrator > Configure Enterprise Assets > Administrator Cluster > Monitoring Configuring settings.

Task J Verify Deployment

Go to TIBCO ActiveMatrix Administrator > Monitor & Manage perspective and make sure it displays all SPM services such as ActionManagerService and RuleService.

Do not use the View and Manage Dashboards perspective of ActiveMatrix Administrator to view SPM services as it filters all the SPM services.


| 99

Appendix B Troubleshooting

This appendix provides solutions to some of the problems that you may encounter when working with TIBCO ActiveMatrix Service Performance Manager.

Topics

• Troubleshooting, page 100

• Frequently Asked Questions, page 103


100 | Appendix B Troubleshooting

Troubleshooting

Problem Is it possible to clean up the environment if:

• the post-installation tool is aborted using Cancel

• the post-installation fails

• you want to create a new setup and delete the existing SPM environment.

Solution If the post-installation fails, you need to clean up the environment based on the stage where it failed.

Task A Disable Monitoring

To avoid TIBCO ActiveMatrix Manager running on both ActiveMatrix Administrator server and the SPM system node at the same time, disable monitoring from TIBCO ActiveMatrix Administrator > Configure Enterprise Assets > Administrator Cluster > Monitoring Configuring Settings.

Task B Stop, Undeploy, and Delete SPM Service Assemblies

Undeploy all service assemblies (ActionManagerSA, ActionServiceSA, AlertSA, and RuleServiceSA) from TIBCO ActiveMatrix Administrator > Deploy to an Environment > SPMSysEnv > Service Assemblies > <Service Assembly> > Stop, Undeploy, and Delete them.

Task C Stop, Uninstall, and Delete SPM System Node

From TIBCO ActiveMatrix Administrator > Configure an Environment > SPMSysEnv > Node > SPMSysNode > Stop, Uninstall, and Delete the SPMSysNode node.

Task D Delete SPM System Environment

From TIBCO ActiveMatrix Administrator > Configure Enterprise Assets > Environment Definitions > Select SPMSysEnv and Delete the environment.

Task E Delete Shared Resources Associated with SPM System Node

From TIBCO ActiveMatrix Administrator > Configure Enterprise Assets > Shared Resource Definitions, delete the JMS, JDBC, and HTTP shared resources that were associated with SPM System node.

For example, delete the shared resources Monitoring JMS Configuration, Quartz JDBC Configuration, and spmHTTPServer-8093.


Troubleshooting | 101

Task F Re-run the Post-installation

Running the above steps clean the SPM environment and you can perform the post-installation again to setup the SPM environment.

Since there is an existing ActiveMatrix Administrator server that was created during the previous run of post-installation, you need to run the Post Installation Configuration tool with existing ActiveMatrix Administrator server. Refer to Use existing Administrator Server on page 44 for details.

However, if the post-installation has failed during the ActiveMatrix Administrator server creation, delete the existing ActiveMatrix Administrator server using the deleteadminserver.exe command,


In this case, since there is no existing ActiveMatrix Administrator Server, create ActiveMatrix Administrator Server during post-installation. Refer Create New Administrator Server on page 48.

Problem Opening the Build and Configure Rules perspective and View and Manage Dashboards perspective throws a 500 error that states "Service not found operation terminated."

The environment is as follows:

• TIBCO ActiveMatrix 2.0.2

• TIBCO ActiveMatrix Service Grid 2.0.2

• TIBCO ActiveMatrix Service Bus 2.0.2

• TIBCO ActiveMatrix BusinessWorks Service Engine 5.6.3

The order of installation is as follows:

• Installed ActiveMatrix 2.0 products

• Upgraded to ActiveMatrix 2.0.1 as per the instructions provided in the TIBCO ActiveMatrix Release Notes to upgrade from 2.0.0 to 2.0.1.

• Upgraded Service Grid to 2.0.2 as per the upgrade instructions in TIBCO ActiveMatrix Service Grid 2.0.2 Release Notes.

• Installed TIBCO ActiveMatrix BusinessWorks Service Engine 5.6.3

• TIBCO ActiveMatrix Service Performance Manager 1.1




The order of startup is as follows:

• HSQL DB

• Management Daemon from Windows Service

• ActiveMatrix Administrator from Windows Service

• SPM Node from within ActiveMatrix Administrator

• Checked that the SPM services are started when the node is started.

Solution This issue occurs if you run ActiveMatrix Administrator as a Windows service.

If you have ActiveMatrix Administrator running as a Windows service and you install ActiveMatrix Service Performance Manager, you need to --uninstall and --install ActiveMatrix Administrator admin service again.

If not, ActiveMatrix Administrator will continue running with old classpath entries and SPM web services are not properly registered.

Problem Even after configuring the SMTP mail server settings, alerts do not get delivered to the specified users.

Solution Test your SMTP server settings using the Alert Service Tester provided in the TIBCO_SPM_HOME\samples\Alerts directory. refer to the readme.txt file in the folder for testing details.

Problem Running the post-installation configuration tool on HP-UX Itanium fails with the following error message:

"The SPMPostInstallationTool executable launcher was unable to locate its companion shared library."

"Unable to find library ‘libgcc_s.so.0’"

How can this issue be resolved?

Solution Set the following system variables:

SHLIB_PATH=$SHLIB_PATH:/opt/hp-gcc-4.2.4/lib

export SHLIB_PATH


Frequently Asked Questions | 103

Frequently Asked Questions

This section lists some of the commonly asked questions.

Running the Post-installation

Question What if TIBCO Enterprise Message Service (EMS) is not running during post-installation?

Answer During post-installation if EMS is not running, the SPM node does not start and the deployment of SPM services fail.

To work around this issue, start EMS and restart the SPM node. Then, perform all the remaining tasks starting from Task H by referring to the section, Performing the Post Installation Manually, on page 94.

Question How to complete post-installation procedure if the post-installation configuration tool on existing ActiveMatrix Administrator server fails due to environmental issues?

For example, if post-installation fails during the sa-add script execution due to some environment/user issue, how to complete the remaining tasks?

Answer First, make sure that there are no setup issues.

If no issues are observed in the existing setup, you can continue with the remaining post-install tasks by referring spm_bootstrap.xml file located in TIBCO_SPM_Home/scripts.

• Make sure ActiveMatrix Administrator Server, ActiveMatrix database, and Management Daemon are running.

• Check whether the SPM node is in the Installed state.

• Run the following command from the command line:

TIBCO_SPM_HOME/bin> spmcmdline.bat ../scripts/spm_bootstrap.xml sa-add sa-update su sr-add sr-update node-start post-node-startup

Question If a new Administrator Server was created during ActiveMatrix Service Performance Manager installation and the Post Installation Configuration tool was run successfully using the new Administrator, why did the ActiveMatrix Administrator fail to enable monitoring?



Answer If you have created ActiveMatrix Administrator with non-default cluster and instance names (for example, myCluster and myAdmin) and selected Use existing Administrator Server on the Post-installation Configuration tool, you must change the default value “admin” to “myAdmin” in the Administrator Server Instance Name field in TIBCO ActiveMatrix Administrator Server Information Post Installation Configuration dialog.

If you miss changing the default value “admin” to “myAdmin” in the Administrator Server Instance Name field, the Post installation tool runs successfully with the “BUILD SUCCESSFUL” message. However, at the end of post installation, there is an error while enabling monitoring. To workaround this issue, enable monitoring from TIBCO ActiveMatrix Administrator > Configure Enterprise Assets > Administrator Cluster > Monitoring Configuring settings.

Service Probes

Question When BusinessWorks Service Probe was installed, the bwengine.tra got updated with SPM variables. However, starting bwengine with BW Service Probe failed with ClassNotFound exception. Is there any resolution?

Answer This is because the variables got added at the end of the file. Move the variables to correct place in bwengine.tra as shown below:

## Copyright (c) 2003-2004 TIBCO Software Inc.# All Rights Reserved.# This software is the confidential and proprietary information of# TIBCO Software Inc.##==========================================================# *** Common variables. Modify these only. ***#==========================================================#tibco.env.PSP=;tibco.env.TIB_HOME=C:/tibcotibco.env.JVM_LIB_PATH=C:/tibco/jre/1.5.0/bin/server/jvm.dlltibco.env.JVM_LIB_DIR=C:/tibco/jre/1.5.0/bintibco.env.RV_HOME=C:/tibco/tibrv/8.1tibco.env.TIB_JAVA_HOME=C:/tibco/jre/1.5.0tibco.env.TPCL_HOME=C:/tibco/tpcl/5.6tibco.env.TRA_HOME=C:/tibco/tra/5.6tibco.env.TRA_APPEND_VERSION=5.6tibco.env.HAWK_HOME=C:/tibco/hawktibco.env.BW_HOME=C:/tibco/bw/5.6tibco.env.BW_PLUGINS_HOME=C:/tibco/bw/plugins## Other arguments to application, JVM etc.#tibco.env.SPM_HOME=c:/spm13v22bwprobe/spm/1.3



tibco.env.SPM_PROBE_CP=%SPM_HOME%/../../components/eclipse/plugins/com.tibco.matrix.spm.bw.monitoring.serviceagent_1.3.0.002.jar%PSP%%SPM_HOME%/../../components/eclipse/plugins/com.tibco.neo.launch_1.2.100.001.jar%PSP%%SPM_HOME%/../../components/eclipse/plugins/org.eclipse.osgi_3.2.2.R32x_v20070118.jartibco.env.CUSTOM_EXT_APPEND_CP=%SPM_PROBE_CP%tibco.env.CUSTOM_EXT_PREPEND_CP=%SPM_HOME%/../../components/eclipse/plugins/com.tibco.tpcl.org.slf4j.log4j12_1.3.1.010%PSP%%SPM_HOME%/../../components/eclipse/plugins/com.tibco.neo.common.util_2.2.1.002.jar

tibco.env.APP_ARGS=tibco.env.HEAP_SIZE=256M

Administrator Server Configuration

Question After running the post-installation tool, if the ActiveMatrix Administrator server protocol is changed (http to https or reverse), does it need any changes in the configuration?

Answer If you change the ActiveMatrix Administrator server protocol from http to https or the reverse, you need to follow these steps:

1. Stop all the ActiveMatrix Service Performance Manager system services by running the following command:

TIBCO_SPM_HOME\bin\stop_default.bat

2. Access the Deploy to an Environment perspective and select spmsysenv. Select ActionServiceSA and click Substitution Variables and locate the amx_admin_protocol substitution variable.

3. Enter http or https.

4. Redeploy ActionServiceSA.

Question Why does ActiveMatrix Administrator Server in an SPM environment take a long time to start up?

Answer To reduce the time to restart ActiveMatrix Administrator Server, you can set the following properties in the TIBCO_HOME\amxadministrator\data\amx\admin\bin\amx_admin.tra file:java.property.monitormanage.update.schema=false

java.property.spm.update.schema=false

Leveraging TIBCO Hawk for Monitoring

Question Can TIBCO Hawk be used in place of ActiveMatrix Service Performance Manager for monitoring the ActiveMatrix applications and for sending alerts to an email and send the alert traps to Tivoli?



What kind of monitoring is currently possible with TIBCO Hawk in monitoring ActiveMatrix applications in general in SOA environment?

Answer The use of TIBCO Hawk for monitoring ActiveMatrix applications is currently limited to a few scenarios. Currently, TIBCO Hawk can only connect to the following data sources produced by ActiveMatrix:

• Log files from ActiveMatrix nodes and Administrator server

• JMX MBeans that track ActiveMatrix node life cycle (note that these are not publicly documented).

• Access to service metrics is limited to an Administration MBean that provides a subset of metrics that is available in the Monitoring & Management perspective of the ActiveMatrix Administrator.

The ActiveMatrix Service Performance Manager roadmap includes requirements to make SPM metrics available to other consumers, especially TIBCO Hawk.

Missing ActiveMatrix Service Performance Manager Specific Perspectives from TIBCO ActiveMatrix Administrator

Question Why don't I see the SPM perspectives even after installing TIBCO ActiveMatrix Service Performance Manager 1.1.0?

Answer When you install ActiveMatrix Service Performance Manager on top of TIBCO ActiveMatrix Service Grid 2.0, ActiveMatrix Service Performance Manager installs only the necessary 2.0.2 components. You need to upgrade your ActiveMatrix installation to 2.0.2 by upgrading the Administrator, node as outlined in the ActiveMatrix Service Grid Release Notes and then install ActiveMatrix Service Performance Manager.

See the section Installing the ‘ActiveMatrix Service Performance Manager’ Over the Existing ActiveMatrix Setup (Recommended Order) for details.

Question How do I manually upload SPM wars if the SPM perspectives are not visible in ActiveMatrix Administrator even after successful post-installation?

Answer Go to Configure Enterprise Assets > Administrator Cluster > Plug-ins > Deploy > Browse to TIBCO_SPM_HOME\webapp\spmui.war and rajax.war files and deploy and start the plug-ins. Restart the browser.

Modifying Parameters of Custom Actions

Question Where can I modify the values of the parameters in the custom actions that are copied from the template actions?



Answer In ActiveMatrix Service Performance Manager 1.x, Custom Action parameters are not editable from the UI. This can be done using the CLI (Command line Interface). CLI enables you to create custom actions with parameters. Read section Over of Custom Actions in chapter 6 of TIBCO ActiveMatrix Service Performance Manager User’s Guide to understand more about custom actions.

You can also review the tutorial examples to see how this can be done. For example, you can search a file called: TIBCO_SPM_HOME/tutorial/scripts/tutorial_amx_spmdata.xml-template which defines a custom action.

Configuring Mail Server

Question How do I change my mail server configuration?

Answer In order to configure the mail server, perform the following steps:

1. Go to the "Deploy to an Environment" perspective in TIBCO ActiveMatrix Administrator.

2. Select the Environment "spmsysenv".

3. In the Substitution Variables of the AlertSA configure the following variables:

/com.tibco.alert.delivery.composite/Shared

Resources/SubstitutionVariables/smtpServer and /com.tibco.alert.delivery.composite/Shared

Resources/SubstitutionVariables/smtpPort variables appropriately.

4. Stop and Redeploy the AlertSA Service Assembly.

5. Restart your SPM node, that is, spmsysenv_sysnode.

While trying to redeploy the AlertSA, if you get an error about invalid values for the username and password, set the values to a blank space.

Question Why don’t I receive any alerts or get any emails in my Inbox?

Answer The default email server is smtp.tibco.com. You need to change that if smtp.tibco.com is not accessible.

Question My mail server is configured correctly but I’m still unable to receive any emails. Any solution?

Answer You need to configure a destination in the SPM profile. See Chapter 9 Creating and Editing Profiles in TIBCO ActiveMatrix Service Performance Manager User’s Guide.



Missing Statistics in the Dashboard

Question Why am I not able to see any statistics in my dashboard?

Answer You must enable Monitoring.

In TIBCO ActiveMatrix Administrator,

1. Select the Configure Enterprise Assets perspective.

2. Select the Administrator Cluster link.

3. Click the Monitoring Configuration link.

4. In the Monitoring Configuration area, click Edit.

5. For Enable Monitoring?, click Yes.

6. Click Save.

Question I have enabled Monitoring but still the statistics are not seen in the dashboard. Why?

Answer Connect to the JMS server using tibemsadmin and check if the activematrix.stats.<amx cluster name> queue is created and messages are being received.

Question Why is data not visible in the dashboard even after defining a rule and rule package?

Answer Make sure that you have enabled the rule.

Question Why is data not visible in the dashboard even after the rule is enabled?

Answer Make sure that the rule is configured with a schedule that is not valid at this time.

Question Why don’t I see any statistics for my BusinessWorks services?

Answer Check if the engine started correctly. A -p need to be passed as a parameter to bwengine.

Question Why don't all services listed in ‘Monitor & Manage’ show up in the Services dashboard?

Answer The Services dashboard does not display statistics for SPM system services.

Question Why don’t I see my BusinessWorks, WAS, or WCF services in the services with top 20 hits list?



Answer The Monitor and manage perspective is only for monitoring and managing services deployed into an ActiveMatrix environment.

For BusinessWorks, WAS, or WCF services, use the Services dashboard in View and Manage dashboards perspective.

Logging Configuration

Question Is it possible to change the log level to debug mode for logging the SPM node?

Answer For nodes that are already created, edit the bootStrap.xml located in TIBCO_HOME/amx/data/<envName>/<nodeName>/config directory.

There is no need to re-start the ActiveMatrix nodes after making the following change. ActiveMatrix runtime nodes will pick the configuration as soon as the config file is saved. To avoid errors due to due to logging configuration save the XML only when it looks correct.

Note that the default log level for the following plug-ins is INFO and should be changed to DEBUG to see more log messages:

• "com.tibco.matrix.spm"

• "com.tibco.matrix.monitoring"

• "com.tibco.matrix.servicegrid.monitoring"

• "com.tibco.alert"

• "com.tibco.alerts"

• "org.quartz"

The default log level for “com.tibco.matrix.spm.metricsmanager.MetricsManagerLogger” is WARN and needs to be changed to INFO or DEBUG to see all engine logging from rule service.

For Enabling SPM logging for ActiveMatrix Administrators:

Add the following logger information to matrix-log4j.xml in TIBCO_HOME/amxadministrator/<version>/templates

For existing ActiveMatrix admin servers, edit the matrix-log4j XML located in TIBCO_HOME/amxadministrator/data/<adminCluster>/<adminInstance>/config directory.

<logger name="com.tibco.matrix.spm" additivity="false"><level value ="INFO"/><appender-ref ref="file"/></logger>



Question When ActiveMatrix Service Performance Manager 1.2.0 is installed over ActiveMatrix Service Grid 2.2.x and you start the debugger node from TIBCO Business Studio, exceptions are thrown. Is there a way to rectify these exceptions in the debugger mode?

Answer To avoid booting the rule service and getting exceptions in debugger mode, open TIBCO_HOME\amx\2.2\server\templates\amx_osgi.properties and exclude com.tibco.matrix.spm.rules.ruleservice.implementation. That is, add it to amx.exclude.plugins.

You must revert these changes when not running in debugger mode.

SPM Data Management

Question If a BusinessWorks application (associated with ActiveMatrix Service Performance Manager) is deleted, why do the SPM dashboards still show data associated with the deleted application?

Answer The Service Probes for BusinessWorks and WCF do not publish the events related to uninstallation and deletion of applications. Hence, the date is retained in the database which appears in the SPM dashboards.

To delete this data, use the spmamangedata.jsp utility located at TIBCO_SPM_HOME\samples\ManageMonitoredObjects. Please refer to readme.txt for details in the same location.

Integrating With Spotfire

Question Why is ActiveMatrix Service Performance Manager not getting integrated with Spotfire even after following all the instructions?

Answer Check the version of Spotfire Analytics Server. Note that Spotfire Analytics Server 10.1 is the minimum requirement for integration with Spotfire.


| 111

Index

B

BusinessWorks Service Probeinstalling and configuring 73

C

changes from the previous release viCommon logging

configuration 80JDBC connection 80JMS connection 80

Configure enterprise assets 63customer support xi

D

Directory structure of installation 59Disk space

after installation 17temporary disk space required by the installer 17

H

Hibernate 20

I

Installationdirectory structure 59prerequisites 20

Installation modesconsole mode 31GUI mode 28silent mode 31

Installation typescustom 15typical 15

Installeraccount (Windows and UNIX) 16Log File 16

InstallingBusinessWorks Service Probe 73Hibernate 23TIBCO ActiveMatrix Service Performance

Manager 28

N

Node spmsysenv_sysnode 63

O

Obfuscated password 93

P

prerequisites 20

R

Running the SPM services 54


112 | Index

S

Scalability guidelines 84Service assemblies table

ActionManagerSA 64ActionServicesSA 64AlertSA 64RuleServiceSA 64

Service probesfor TIBCO ActiveMatrix 14for TIBCO BusinessWorks 14overview 14

spmsysenv environment 63service assemblies 63

support, contacting xiSupported

browsers 18databases 17platforms 15

System memory 15System services

Action Manager 14Action service 14Alert notification service 14Rules service 14

T

technical support xiTIBCO_HOME viii, 23Troubleshooting 100

U

Uninstalling 86UNIX 16

V

Verifying the installation 80