tibco activematrix service performance manager … · aix 6.1 power pc 64-bit ... you can now...

TIBCO ActiveMatrix®

Service Performance Manager

Release NotesSoftware Release 1.3.1March 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

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 1.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 1.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Release 1.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Release 1.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Release 1.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Release 1.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Scenario 1: Monitoring ActiveMatrix Service Grid / ActiveMatrix Service Bus / ActiveMatrix BusinessWorks Service Engine Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Scenario 2: Monitoring Only the Standalone TIBCO BusinessWorks Services . . . . . . . . . . . . . . . . . . . . . . 19Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Scenario 1: Monitoring ActiveMatrix Service Grid / ActiveMatrix Service Bus / ActiveMatrix BusinessWorks Service Engine Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Scenario 2: Monitoring Only the Standalone TIBCO BusinessWorks Services . . . . . . . . . . . . . . . . . . . . . . 32Release 1.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Release 1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

TIBCO ActiveMatrix Service Performance Manager Release Notes

iv | Contents


| 1

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 10

• Deprecated Features, page 12

• Migration and Compatibility, page 13

• Closed Issues, page 43

• Known Issues, page 63


https://support.tibco.com

2 | Release Notes

New Features

This section lists features added since the last major (1.0) release of this product.

Release 1.3.1Following are new features in this release.

• The Service Probe for TIBCO BusinessWorks enables monitoring of both services and calls to those services (references). The monitoring of non-SOAP processes, sub-processes, and activities for references is now automatically disabled when no static calls are found.

• The Service Probe for TIBCO BusinessWorks can now be disabled/enabled per installation, or for selected BusinessWorks service instances through a check box in TIBCO Administrator when a BusinessWorks EAR file is deployed.

To turn off monitoring, add the following properties in {TIBCO_HOME}/spm/1.3/plugins/bwserviceagent.properties:— serviceprobe.disableMonitoring (default false)

— serviceprobe.disableReferenceProcessing (default false)

Alternatively, if you want to change the configuration of Service Probe for TIBCO BusinessWorks in selected engines, edit {TIBCO_HOME}/bw/<version>/bin/bwengine.tra and add the following properties. To change the probe configuration of selected engines in the deployed applications, the tra file <application name>-Process_Archive.tra located at {TIBCO_HOME}/tra/domain/<domain name>/application/<application name>/ needs to be edited to add the following properties.

— java.property.tibco.monitormanage.serviceprobe.bw.disableMoni

toring (default false)

— java.property.tibco.monitormanage.serviceprobe.bw.disableRefe

renceProcessing (default false)

Setting serviceprobe.disableMonitoring to true disables monitoring for all BusinessWorks engines on the machine.

Similarly, setting serviceprobe.disableReferenceProcessing to true disables processing of referenced activities such as SOAP Request/Reply and Invoke Partner invocations. In other words, even if the project contains any SOAP Request/Reply or Invoke Partner activities, they are not processed.


New Features | 3

• The monitoring interval is now configurable for the Service Probe for TIBCO BusinessWorks to allow the frequency of published statistics messages to be changed.

To set the monitoring interval, add the following property in {TIBCO_HOME}/spm/1.3/plugins/bwserviceagent.properties:— serviceprobe.publishIntervalSeconds (default 15, minimum 15,

maximum 60, valid values: 15, 20, 30, 60)

Alternatively, if you want to change the configuration of Service Probe for TIBCO BusinessWorks in selected engines, edit {TIBCO_HOME}/bw/<version>/bin/bwengine.tra and add the following property. To change the probe configuration of selected engines in the deployed applications, the tra file <application name>-Process_Archive.tra located at {TIBCO_HOME}/tra/domain/<domain name>/application/<application name>/ needs to be edited to add the following property:

— java.property.tibco.monitormanage.serviceprobe.publishInterva

lSeconds (default 15, minimum 15, maximum 60, valid values:

15, 20, 30, 60)

Release 1.3.0Following are new features in this release.

• This product version adds support for the following software and platforms:

— JRE 1.6.0_18 or higher

— TIBCO Rendezvous 8.2

— TIBCO Enterprise Message Service 5.1.4

— Databases:

Microsoft SQL Server 2008

Oracle 11g Release 1 (11.1)

Oracle 11g Release 1 (11.1) RAC

— Platforms:

AIX 6.1 Power PC 64-bit

Microsoft Windows Server 2003 and 2008 - 64 bit

SUSE Linux Enterprise 10.3 x86 and x86-64

• TIBCO ActiveMatrix Service Grid or TIBCO ActiveMatrix Service Bus version 2.3.0 is now supported as the minimum version.


4 | Release Notes

• TIBCO Spotfire version 3.0 is now supported. The examples include samples with Oracle along with SQL Server.

• The TIBCO ActiveMatrix Service Performance Manager Post-installation Configuration tool is now supported on Solaris10 x86 64-bit platform.

• Performance improvement for service probes (up to 50% less overhead).

Release 1.2.0

Support Performance Monitoring of WCF and WAS Services

You can now monitor the performance of the following web services from the View and Manage Dashboards perspective:

• Microsoft Windows Communication Foundation (WCF) Services.

• Java EE Web Services and Service References (JAXRPC/JAXWS) which are deployed and running in IBM WebSphere Application Server.

To enable ActiveMatrix Service Performance Manager to monitor the above services, you need to install the ‘Service Probe for WCF’ and ‘Service Probe for WAS’ as part of the respective Management Agent installations. Refer to TIBCO ActiveMatrix Management Agent for WCF and TIBCO ActiveMatrix Management Agent for WebSphere documentation for details.

Support Rule Service in Fault Tolerant Mode

A capability to run the SPM Rule Service on multiple nodes and a mechanism to transition a node from Active to Inactive state is provided.

The SPM Rule Service runs inside the Java service unit RuleServiceJavaSU. To enable the rule service fault tolerance, you need to load balance the JAVA service unit. Mapping the Java component to multiple nodes enables the rule service fault tolerance.

Centralized TIBCO Spotfire Integration

Metrics can now be sent to a Spotfire database from the Rule Service rather than from individual ActiveMatrix nodes. This reduces the nodes that have knowledge (and connectivity) to the database as well as supporting metrics collection from data outside of ActiveMatrix nodes. For example, metrics can now be collected more easily from ActiveMatrix BusinessWorks, and via service probes from WCF and WAS.


New Features | 5

New Platform and Database Support

The minimum version supported by TIBCO ActiveMatrix Service Performance Manager 1.2.0 for monitoring and managing ActiveMatrix Service Grid or ActiveMatrix Service Bus services is 2.1.0.

This product version supports the following new platforms and databases:

• Platforms

Red Hat Enterprise Linux 5.2 32-bit and 64-bit

AIX 5.3 POWER 64 bit

• Database



• Web Browser

Mozilla Firefox 3.0

Samples for Alert Template

Sample templates for SNMP and Email Alerts are provided in the TIBCO_SPM_HOME\samples\AlertTemplate folder.

Release 1.1.1There are no new features added for this release.

Release 1.1.0Following are the new features in this release.

Custom Metrics Support in the Rule Builder

You can now set conditions on custom metrics for a service operation or service operation instance as target objects. These are monitored and managed service operations or service operation instances in ActiveMatrix and BusinessWorks.

Note that Firefox 3.0 is supported only for SPM perspectives (Build and Configure Rules and View and Manage Dashboards) and not for the rest of ActiveMatrix perspectives.


6 | Release Notes

To set condition on custom metrics, you need to first define the custom metrics using the Command Line Interface (CLI). Once defined, the custom metrics appear in the Rule Builder: Step 3 of 4 — Creating Conditions metrics drop-down list.

Once added, the custom metric data can be viewed in the Services and Operation table in the Services Dashboard.

Summary Reports in the Dashboards

From the View and Manage Dashboards perspective, you can generate various summary reports from the Rules, Services, and Infrastructure dashboards.

From the Rules Dashboard, you can generate the following reports:

• Single Rule Summary Report—Displays details of rule, rule condition charts, and the actions associated with the rule are displayed in the report.

The Alerts tab provides the list of alerts generated for the rule.

• Multiple Rules Summary Report—Displays the details of the selected rules such as Trigger Status, Rule Type, Target Object Type, Created, Modified, Owner, and so on in a table.

The Alerts tab provides the list of alerts generated for these rules.

• Single Rule Package Summary Report—Displays details of the rule package and lists the rules contained in the rule package in a table.

The report also includes the Rules and Alerts tab which display the rule details and the alerts generated for the rules in the rule package.

• Multiple Rule Packages Summary Report—Displays the details of the selected rule packages such as Triggers, Schedule, Consumer, Provider, and so on in a table.

From the Services Dashboard, you can generate the following reports:

• Single Service Summary Report—Displays details of services such as Faults, Successes, and Total Hits. Also, the number of rules set on the selected service and deployment details of the service are displayed in the Rules and Deployment tables. The charts for Hits and Average Response Time are also displayed.

• Multiple Services Summary Report—Displays a table providing the details of selected services such as Status, Uptime, Throughput, Service Provider, and so on.

• Single Operation Summary Report—Displays the operation details such as Faults, Successes, and Total Hits. The number of rules set on the selected operation and the operation deployment details are shown in the Rules and


New Features | 7

Deployment tables. The Hits and Average Message Size are displayed in the chart format.

• Multiple Operations Summary Report—Displays the Operations table with details such as Average Response Time, Average Message Size, Faults, Successes, and so on. The Classifier statistics table displays details of the selected service operation from the Operations table.

The services and operations report provides additional information about the selected object in the Metrics & Rules, Deployment Details, Rules, and Alerts tabs. In addition, the services reports contain an additional tab for Operations.

From the Infrastructure Dashboard, you can generate the following reports:

• Single Machine Summary Report—The summary report displays machine details such as OS, Memory, Free and Total Physical Memory and Status. In addition, the Rules and Services table displays the details about the rules and services running on the selected machine.

• Multiple Machines Summary Report—Displays a table with machine details such as Status, Physical Memory, Swap Size, and so on.

The machines report displays addition information about the selected machine in the Rules, Service Instances, Nodes/Engines, and Alerts tab.

• Single Node Summary Report—Displays node details such as JVM Memory, Availability, Status, and so on. The details of rules and services running on the node are displayed in the Rules and Services table.

• Multiple Nodes Summary Report—Displays the Nodes/Engines table which shows details such as CPU Usage, CPU Time, JVM Memory and so on.

The Nodes report displays addition information about the selected nodes in the Rules, Service Instances, and Alerts tab.

• Single Service Instance Summary Report—Displays details such as Faults, Successes, and Deployment Details and details about the rules set on the service instance. The Hits and Average Response Time are displayed as charts.

• Multiple Service Instances Summary Report—Displays a table with service instance details such as Node Name, Uptime, Throughput, and so on.

The Service Instances report provides additional information about the selected object in the Metrics & Rules, Deployment Details, Operations Instances, Rules, and Alerts tabs.

• Single and Multiple Operation Instance Summary Report—The format of this report is same as Single and Multiple Operations Summary Report.


8 | Release Notes

Post-Installation UI Tool

To simplify the ActiveMatrix Service Performance Manager post-installation task, a new UI tool is provided. This tool helps you deploy SPM system services, configure ActiveMatrix Admin Server, Messaging Server, and database.

Export SPM Objects Through CLI

The SPMAdminTask now supports the Export action which allows you to export SPM objects into an output file. For exporting the data, the data file must follow the spmcli_export.xsd schema.

Release 1.0.0Following are the new features in this release.

• TIBCO ActiveMatrix™ Service Performance Manager provides the capability to monitor and manage web services running in TIBCO ActiveMatrix and TIBCO BusinessWorks products.

ActiveMatrix Service Performance Manager version 1.0 supports the following products:

— TIBCO BusinessWorks 5.4 or TIBCO ActiveMatrix BusinessWorks 5.6

— TIBCO ActiveMatrix Service Grid 2.0.2

— TIBCO ActiveMatrix Service Bus 2.0.2

• The product interface supports both, Graphical User Interface (GUI) as well as Command Line Interface (CLI).

The graphical interface is divided into the following two perspectives which are plugged into TIBCO ActiveMatrix Administrator:

— Build and Configure Rules

— View and Manage Dashboards

The command line interface supports most of the actions that you can perform from the user interface and some additional action also.

• The Build and Configure Rules perspective is the design-time of TIBCO ActiveMatrix Service Performance Manager. Using the following links in this perspective, you can define rule packages and rules for service performance monitoring:

Rule Packages, Objectives, and Rules

Target Objects

Custom Actions


New Features | 9

Schedules

Profile

For better service performance, you can even associate appropriate custom actions with rules. These actions will be triggered when the condition defined in a rule is met and will try to get the service performance within the specified limits.

• The View and Manage Dashboards perspective is the run-time mode that offers you various default views for service performance monitoring and management. The dashboard provides the following main views:

Alerts—Displays all received alerts for the selected target object or objects.

Browse—Allows you to browse for data by rule packages and standalone rules, services (deployment), infrastructure, and by target object groups.

Rule Dashboard—Allows you to monitor alerts and triggers generated for Rules and Rule Packages.

Services Dashboard—Allows you to monitor alerts, deployment details, and rules triggered for the selected service or service operation.

Infrastructure Dashboard—Allows you to monitor machine and node/engine data.


10 | Release Notes

Changes in Functionality

This section lists changes in functionality since the last major 1.0.0 release of this product.

Release 1.3.1There is no change in functionality for this release.


Release 1.2.0

Updates in SPM Perspectives

• The Rule Builder now supports additional target objects, Server and Host Process, to create rules for monitoring WAS or WCF services.

• Custom Action creation is supported on the additional target objects ‘Server’ and ‘Host Process’.

• Both SPM perspectives use "Service Containers" as a representation of nodes, engines, servers, and host processes.

• A new field named Domain Type is available in all dashboards and reports.


Release 1.1The following are changes in functionality in this release.


Changes in Functionality | 11

Tutorial

The sample tutorial example is updated with custom metric and custom action examples. The updated tutorial files are located inside TIBCO_SPM_HOME\tutorial folder after the product installation. To read the latest Sample Tutorial documentation, refer to Chapter 13 of TIBCO ActiveMatrix Service Performance Manager User’s Guide.

Dashboards

The Browse Panel now allows you to browse by Rules, Services, Infrastructure, and Target Objects Groups. You can create reports of any object by selecting the View Details button.

The new View Details button in the Rules, Services, and Infrastructure dashboard allows creation of single or multiple objects summary report.


12 | Release Notes

Deprecated Features

This section describes deprecated features and lists equivalent features that accomplish the same result, if relevant. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the equivalent feature.

Release 1.3.1There is no deprecated feature for this release.

Release 1.3.0This product version does not support Spotfire Analytics Server 10.1 and Spotfire Client 2.x.

Release 1.2.0Though the current release of ActiveMatrix Service Performance Manager 1.2.0 supports Oracle 9i and FireFox 2.0, the future release may not support it. You should avoid becoming dependent on these version and upgrade to Oracle 10g and Firefox 3.0.


Migration and Compatibility | 13

Migration and Compatibility

This section explains how to migrate from a previous release to this release.

Release 1.3.1See the product readme for instructions on upgrading from release 1.3.0 to 1.3.1.

Release 1.3.0ActiveMatrix Service Performance Manager 1.3.0 is compatible with ActiveMatrix Service Grid 2.3.0 and bundles the ActiveMatrix 2.3.0 platform components.

The steps to migrate to ActiveMatrix Service Performance Manager 1.3.0 differ depending on the existing setup and the services being monitored.

• Scenario 1: Monitoring ActiveMatrix Service Grid / ActiveMatrix Service Bus / ActiveMatrix BusinessWorks Service Engine Services, page 13

• Scenario 2: Monitoring Only the Standalone TIBCO BusinessWorks Services, page 19

Scenario 1: Monitoring ActiveMatrix Service Grid / ActiveMatrix Service Bus / ActiveMatrix BusinessWorks Service Engine Services

Use the following steps to upgrade to ActiveMatrix Service Performance Manager to 1.3.0 from — ActiveMatrix Service Performance Manager 1.2.0 with ActiveMatrix Service Grid 2.2.x /ActiveMatrix Service Bus 2.2.x /ActiveMatrix BusinessWorks Service Engine Services 5.x.

• Task A: Shut down all ActiveMatrix Processes, on page 14

• Task B: Install ActiveMatrix Service Grid 2.3.0, on page 14

• Task C: Install ActiveMatrix Service Performance Manager 1.3.0, on page 14

• Task D: Optionally Upgrade the ActiveMatrix Administrator Database, on page 15

• Task E: Upgrade the Management Daemon, on page 15

• Task F: Upgrade the Existing ActiveMatrix Administrator Server, on page 16

• Task G: Upgrade All Existing Nodes, on page 16

• Task H: Upgrade SPM Service Assemblies, on page 17


14 | Release Notes

Task A Shut down all ActiveMatrix Processes

Shut down all ActiveMatrix processes in the sequence—ActiveMatrix nodes running on the machine, SPM system node, ActiveMatrix Administrator Server, and Management Daemon.

Task B Install ActiveMatrix Service Grid 2.3.0

Install ActiveMatrix Service Grid 2.3.0 over the setup—ActiveMatrix Service Performance Manager 1.2.0 + ActiveMatrix Service Grid 2.2.x.

Task C Install ActiveMatrix Service Performance Manager 1.3.0

1. Stop all TIBCO ActiveMatrix processes—ActiveMatrix nodes, SPM node, ActiveMatrix Administrator Server, Management Daemon.

2. Install ActiveMatrix Service Performance Manager 1.3.0.

3. Execute following utility to perform sync installation: TIBCO_HOME/amx/2.3/server/bin >SyncInstallation

4. Execute following command from TIBCO_Home/spm/1.3/bin: UpdateInstallation.bat.

5. Update the following .properties files:

— Create data.properties file from the template (TIBCO_Home/spm/1.3/scripts/data.properties-template) and add the appropriate entries as per your environment. Refer to the data.properties file in the TIBCO_HOME/spm/1.2/scripts folder.

— Similarly, add the required entries in the TIBCO_Home/spm/1.3/scripts/login.properties file by referring to login.properties in TIBCO_Home/spm/1.2/scripts.

You may encounter error about a missing plug-in. It is a harmless error and can be safely ignored. Even though the flattener complains about the missing dependency for a "com.tibco.matrix.spm.serviceprobe.admin.services.impl_1.3.0" plug-in, it correctly includes the latest version of that plug-in (1.4.0).

In a distributed setup, the Service Probe for ActiveMatrix component of ActiveMatrix Service Performance Manager 1.3.0 must be installed on the machine where SPM node and ActiveMatrix nodes are configured.



Task D Optionally Upgrade the ActiveMatrix Administrator Database

To manually upgrade the database:

1. Start the ActiveMatrix Administrator database.

2. Open a terminal window.

3. Change to the directory AMX_ADMIN_HOME/2.3/bin/.

4. Run dbscriptgenerator –generateupdates. This command determines the difference between the database schema in a previously installed product and the schema for the current product and saves the difference into a DDL file.

The command prompts you to enter the name of the ActiveMatrix Administrator cluster and the name of the ActiveMatrix Administrator server. Type the cluster name and server name.

5. Apply the DDL file to the schema using your database’s SQL tool.

Updating HSQLDB

To update an HSQLDB database:

1. Copy AMX_HOME/hsqldb/bin/sqltool.rc to the user home location. For example, on Windows it would be C:\Documents and Settings\username.

2. Execute the following command at a prompt with the HSQLDB database running:

java -jar ENV_HOME/components/eclipse/plugin/com.tibco.tpcl.org.hsqldb_1.8.100.001/hsqldb.jar urlid AMX_ADMIN_HOME/2.3/scripts/dbschema.ddl

where urlid is the name of the ActiveMatrix Administrator cluster name and can be found in the sqltool.rc file.

The ddl file to precreate schema generates alter table and the create table statements. You must manually delete all the initial values of alter tables so that the scripts directly starts executing the create table statements.

Task E Upgrade the Management Daemon

To upgrade Management daemon:

1. Change to the directory TIBCO_HOME/tools/bin/.

tibcommander -f ../../managementdaemon/2.0/bin/MDCacheCleaner.xml

You must perform this step, even if you plan to work with new clusters.


16 | Release Notes

2. On Windows, to reinstall managementdaemon service, execute the following commands from TIBCO_HOME\managementdaemon\2.0\bin:— managementdaemon.exe --uninstall

— managementdaemon.exe --install -noshell -redirect

Task F Upgrade the Existing ActiveMatrix Administrator Server

To upgrade an ActiveMatrix Administrator server:


2. Run this command:

tibcommander.exe -Dclustername=cluster -Dadminname=instance -f TIBCO_HOME\amxadministrator\2.3\bin\adminupgradersp1.xml

3. On Windows, reinstall the TIBCO ActiveMatrix Administrator service and execute the following commands from

TIBCO_Home\amxadministrator\data\<cluster name>\<server name>\bin- <clustername>_<adminservername>.exe --uninstall- <clustername>_<adminservername>.exe --install -noshell -redirect

4. If you have created Administrator Server using the Post-installation Configuration tool in ActiveMatrix Service Performance Manager 1.2..0, you must 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

5. Start ActiveMatrix processes in the sequence—Management Daemon and ActiveMatrix Administrator Server.

6. In TIBCO ActiveMatrix Administrator > Configure Enterprise Assets > Administrator Cluster> Plug-ins, check that the Status of TIBCO ActiveMatrix Service Performance Manager Plug-in is Running and Version is 1.3.0.

Task G Upgrade All Existing Nodes

To upgrade all existing runtime nodes on this system.

To upgrade 2.2.1 nodes to 2.3.0:

1. Ensure the ActiveMatrix Administrator database is running.



2. Upgrade all nodes:

a. Change to the directory TIBCO_HOME/tools/bin/.

b. Run this command to update node1 through nodeN:tibcommander -f ../../amx/2.3/server/bin/nodeupgrader.xml -Dnodes=environment1/node1,...,environmentN/nodeN -l nodeupgrader.log

3. Start SPM node.

Task H Upgrade SPM Service Assemblies

You can upgrade SPM 1.2.0 service assemblies to SPM 1.3.0 from the command-line or from GUI.

Using CLI

1. cd TIBCO_HOME/spm/1.3/scripts

../bin/spmcmdline spm_bootstrap.xml spm-upgrade-all-sa

2. Start all the ActiveMatrix nodes.

Using GUI

1. Login to TIBCO ActiveMatrix Administrator, select the Deploy to an Environment from the Perspective drop-down and select the Environment spmsysenv.

2. From the Service Assemblies table, select all service assemblies (SAs) and click Stop.

3. Select ActionManagerSA and click Undeploy.

— In General Information, click the Edit button.

— In the Archive File field, click Update.

— Browse and select the new ActionManagerSA.zip from the TIBCO_SPM_HOME/assemblies path.

— Click OK and Save.

— Click Deploy.

To reduce the time to start 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=falsejava.property.spm.update.schema=false


18 | Release Notes

4. Select ActionServicesSA and click Undeploy.



— Browse and select the new ActionServicesSA.zip from the TIBCO_SPM_HOME/assemblies path.


— Click Deploy.

5. Select AlertSA and click Undeploy.



— Browse and select the new AlertSA.zip from the TIBCO_SPM_HOME/assemblies path.


— Click Deploy.

6. Select RuleServiceSA and click Undeploy.



— Browse and select the new RuleServiceSA.zip from the TIBCO_SPM_HOME/assemblies path.


— Click Deploy.

7. Start all the SPM service assemblies. The SA version should be 1.3.0.

8. Start all the ActiveMatrix nodes.



Scenario 2: Monitoring Only the Standalone TIBCO BusinessWorks ServicesTo install ActiveMatrix Service Performance Manager 1.3.0 over an existing installation of ActiveMatrix Service Performance Manager 1.2.0 with Service Probe for BusinessWorks, follow these steps:

• Task A: Shut down All ActiveMatrix Processes, on page 19

• Task B: Install ActiveMatrix Service Performance Manager 1.3.0, on page 19

• Task C: Optionally Upgrade the ActiveMatrix Administrator Database, on page 20

• Task D: Upgrade Management Daemon, on page 21

• Task E: Upgrade an ActiveMatrix Administrator Server, on page 21

• Task F: Upgrade SPM System Node, on page 22

• Task G: Upgrade SPM Service Assemblies, on page 22

• Task H: Update TIBCO ActiveMatrix BusinessWorks Properties, on page 24

Task A Shut down All ActiveMatrix Processes

Shutdown the ActiveMatrix processes in the given sequence:

— SPM System Node

— ActiveMatrix Administrator servers

— Management Daemon

Task B Install ActiveMatrix Service Performance Manager 1.3.0

1. Launch the ActiveMatrix Service Performance Manager 1.3.0 TIBCOUniversalInstaller executable from a temporary directory and complete the installation.


— Create data.properties file from the template (TIBCO_Home/spm/1.3/scripts/data.properties-template) and add the appropriate entries as per your environment. Refer to the data.properties file in the TIBCO_Home/spm/1.2/scripts folder.


3. Execute following utility to perform sync installation:

TIBCO_Home/amx/2.3/server/bin >SyncInstallation


20 | Release Notes

4. Execute following command from TIBCO_SPM_HOME/bin: UpdateInstallation.bat. (or UpdateInstallation.sh)

Task C Optionally Upgrade the ActiveMatrix Administrator Database

To manually upgrade the database:

1. Start the ActiveMatrix Administrator database.

2. Open a terminal window.

3. Change to the directory AMX_ADMIN_HOME/2.3/bin/.

4. Run dbscriptgenerator –generateupdates. This command determines the difference between the database schema in a previously installed product and the schema for the current product and saves the difference into a DDL file.

The command prompts you to enter the name of the ActiveMatrix Administrator cluster and the name of the ActiveMatrix Administrator server. Type the cluster name and server name.

5. Apply the DDL file to the schema using your database’s SQL tool.

Updating HSQLDB

To update an HSQLDB database:

1. Copy AMX_HOME/hsqldb/bin/sqltool.rc to the user home location. For example, on Windows it would be C:\Documents and Settings\username.

2. Execute the following command at a prompt with the HSQLDB database running:

java -jar ENV_HOME/components/eclipse/plugin/com.tibco.tpcl.org.hsqldb_1.8.100.001/hsqldb.jar urlid AMX_ADMIN_HOME/2.3/scripts/dbschema.ddl

where urlid is the name of the ActiveMatrix Administrator cluster name and can be found in the sqltool.rc file.

The ddl file to precreate schema generates alter table and the create table statements. You must manually delete all the initial values of alter

You may encounter error about a missing plug-in. It is a harmless error and can be safely ignored. Even though the flattener complains about the missing dependency for a "com.tibco.matrix.spm.serviceprobe.admin.services.impl_1.3.0" plug-in, it correctly includes the latest version of that plug-in (1.4.0).

In a distributed setup, the Service Probe for BusinessWorks component of ActiveMatrix Service Performance Manager 1.3.0 must be installed on the machine where TIBCO BusinessWorks is installed.



tables so that the scripts directly starts executing the create table statements.

Task D Upgrade Management Daemon

To upgrade Management Daemon:

1. Upgrade all ActiveMatrix Administrator servers bound to that Management Daemon.

2. Run the upgrader:

a. Change to the directory TIBCO_Home/tools/bin/.

b. Run tibcommander –f ../../managementdaemon/2.0/bin/managementdaemonupgrader.xml.

c. Run tibcommander –f ../../managementdaemon/2.0/bin/MDCacheCleaner.xml.

3. Reinstall the Management Daemon Windows service as follows:

a. Change to the directory TIBCO_Home/managementdaemon/2.0/bin.

b. Run managementdaemon.exe --uninstall.

c. Run managementdaemon.exe --install -noshell -redirect.

4. Start Management Daemon.

Task E Upgrade an ActiveMatrix Administrator Server


1. Ensure that the ActiveMatrix Administrator database server is running.


a. Change to the directory TIBCO_Home/tools/bin.

b. Run

tibcommander.exe -Dclustername=cluster -Dadminname=instance -fTIBCO_HOME\amxadministrator\2.3\bin\adminupgradersp1.xml

where clustername and adminname are respectively the names of the cluster and Administrator server.


22 | Release Notes

3. Reinstall the ActiveMatrix Administrator Windows service as follows:

a. Change to the directory TIBCO_Home/amxadministrator/data/clustername/servername/bin

b. Run clustername_servername.exe --uninstall.

c. Run clustername_servername.exe --install -noshell -redirect.

4. Start the server. If you run the server startup script (amx_admin) to start the server, run the file in TIBCO_Home/amxadministrator /2.3/bin/.

5. Clear the browser cache before accessing the ActiveMatrix Administrator UI.

6. In TIBCO ActiveMatrix Administrator > Configure Enterprise Assets > Administrator Cluster> Plug-ins, check that the Status of TIBCO ActiveMatrix Service Performance Manager Plug-in is Running and Version is 1.3.0.

Task F Upgrade SPM System Node

To upgrade SPM system node:


2. Upgrade node:


b. Run tibcommander –f ../../amx/2.3/server/bin/nodeupgrader.xml

-Dnodes=<spm_environment_name>/<spm_environment_node_name> -l nodeupgrader.log

3. If the node was installed as a Windows service, reinstall the service as follows:

a. Change to the directory TIBCO_Home/amx/data/<spm_environment_name>/<spm_environment_node_name>/bin/.

b. Run <spm_environment_node_name>.exe --uninstall.

c. Run <spm_environment_node_name>.exe --install -noshell -redirect.

4. Start the SPM node.

Task G Upgrade SPM Service Assemblies

You can upgrade SPM 1.2.0 service assemblies to SPM 1.3.0 from the command-line or from GUI.

Using CLI



cd TIBCO_HOME/spm/1.3/scripts


Using GUI








— Click Deploy.






— Click Deploy.



24 | Release Notes






— Click Deploy.






— Click Deploy.


Task H Update TIBCO ActiveMatrix BusinessWorks Properties

1. Specify values for the required entries in the TIBCO_HOME/spm/1.3/plugins/bwserviceagent.properties file by referring to bwserviceagent.properties file in TIBCO_HOME/spm/1.2/plugins folder.

amx_admin_server_url_delimeteramx_admin_server_urlsamx_admin_server_auth_usernameamx_admin_server_auth_password#Custom Metrics Enable/Disableserviceprobe.custommetrics.enable=true#Test Mode Prefix (If BW Engine Running from command line) com.tibco.spm.bw.serviceprobe.TestModePrefix=test

2. Restart TIBCO ActiveMatrix BusinessWorks engine for the changed properties to take effect.



Release 1.2.0TIBCO ActiveMatrix Service Performance Manager 1.2.0 is not compatible with Internet Explorer 6.0.

ActiveMatrix Service Performance Manager 1.2.0 is compatible with ActiveMatrix Service Grid 2.2.1 and bundles the ActiveMatrix 2.2.1 platform components.

The steps to migrate to ActiveMatrix Service Performance Manager 1.2.0 differ depending on your existing setup and the services being monitored.

• Scenario 1: Monitoring ActiveMatrix Service Grid / ActiveMatrix Service Bus / ActiveMatrix BusinessWorks Service Engine Services, page 13

• Scenario 2: Monitoring Only the Standalone TIBCO BusinessWorks Services, page 19

Scenario 1: Monitoring ActiveMatrix Service Grid / ActiveMatrix Service Bus / ActiveMatrix BusinessWorks Service Engine Services

Use the following steps to upgrade to ActiveMatrix Service Performance Manager to 1.2.0 from — ActiveMatrix Service Performance Manager 1.1.1 with ActiveMatrix Service Grid 2.2.0 /ActiveMatrix Service Bus 2.2.0 /ActiveMatrix BusinessWorks Service Engine Services 5.x.

If your setup includes ActiveMatrix Service Performance Manager 1.1.1 with ActiveMatrix Service Grid 2.2.1, to upgrade to ActiveMatrix Service Performance Manager 1.2.0, you need to execute steps provided in Task H to Task J.

• Task A: Shut down all ActiveMatrix Processes, on page 26

• Task B: Install ActiveMatrix Service Grid 2.2.1, on page 26

• Task C: Upgrade the Management Daemon, on page 26

• Task D: Upgrade the Existing ActiveMatrix Administrator Server, on page 27

• Task E: Upgrade All Existing Nodes, on page 27

• Task F: Upgrade bootStrap.xml on Existing Nodes, on page 27

• Task G: Migrate Previous Log Services Created with a DB Destination, on page 28

• Task H: Install ActiveMatrix Service Performance Manager 1.2.0, on page 28

• Task I: Start ActiveMatrix Processes and Upgrade All Nodes, on page 29

• Task J: Upgrade SPM Service Assemblies, on page 30


26 | Release Notes

Task A Shut down all ActiveMatrix Processes

Shut down all ActiveMatrix processes in the sequence—ActiveMatrix nodes running on the machine, SPM system node, ActiveMatrix Administrator Server, and Management Daemon.

Task B Install ActiveMatrix Service Grid 2.2.1

1. Install ActiveMatrix Service Grid 2.2.1 over the setup—ActiveMatrix Service Performance Manager 1.1.1 + ActiveMatrix Service Grid 2.2.0.

2. Run the following commands:

— On Windows:

cd TIBCO_HOME/tools/bin

./tibcommander -f ../../spm/1.1/scripts/updatespm.xml

post.install.tasks.

— On UNIX:

cd TIBCO_HOME/spm/1.1/bin

./spmcmdline.sh ../scripts/updatespm.xml post.install.tasks

Task C Upgrade the Management Daemon

After installing 2.2.1 on top of 2.2.0, you must run this utility to clear the cache:


tibcommander -f ../../managementdaemon/2.0/bin/MDCacheCleaner.xml

2. On Windows, to reinstall managementdaemon service, execute the following commands from TIBCO_HOME\managementdaemon\2.0\bin

— managementdaemon.exe --uninstall

— managementdaemon.exe --install -noshell -redirect

If the file flattening operation fails with java.lang.OutOfMemoryError.Java heap space when running on command line, increase the max JVM Heap Size to 512MB or higher from the original 56MB value in spmcmdline.tra and re-run the command.

You must perform this step, even if you plan to work with new clusters.



Task D Upgrade the Existing ActiveMatrix Administrator Server

After installing 2.2.1 on top of 2.2.0, perform these steps to upgrade the existing ActiveMatrix Administrator servers:

1. Change to the directory ENV_HOME/tools/bin/.

2. Run this command:

tibcommander.exe -Dclustername=cluster -Dadminname=instance -f TIBCO_HOME\amxadministrator\2.2\bin\adminupgradersp1.xml upgrade_minor

3. On Windows, reinstall the TIBCO ActiveMatrix Administrator service and execute the following commands from

TIBCO_Home\amxadministrator\data\<cluster name>\<server name>\bin- <clustername>_<adminservername>.exe --uninstall- <clustername>_<adminservername>.exe --install -noshell -redirect

4. Start ActiveMatrix processes in the sequence—Management Daemon and ActiveMatrix Administrator Server.

Task E Upgrade All Existing Nodes

After installing 2.2.1 on top of 2.2.0 you must upgrade all existing runtime nodes on this system.

To upgrade 2.2.0 nodes to 2.2.1:


2. Upgrade all nodes:

a. Change to the directory ENV_HOME/tools/bin/.


3. Start SPM node and then all the ActiveMatrix nodes.

Task F Upgrade bootStrap.xml on Existing Nodes

If you have made changes to the bootStrap.xml file on existing nodes, you must upgrade the nodes with the new bootStrap.xml file.

To upgrade bootStrap.xml file on existing nodes:

New nodes will automatically get the new bootStrap.xml file, because the 2.2.1 installation replaces the old version.


28 | Release Notes

1. Stop the node where you want to upgrade bootStrap.xml

2. Back up the bootStrap.xml file from node/config

3. Copy the new bootStrap.xml from TIBCO_HOME/amx/2.2/server/templates.

4. If you have any custom manual steps in your original bootStrap.xml file, copy them into the new bootStrap.xml file.

5. Restart the node.

Task G Migrate Previous Log Services Created with a DB Destination

1. If a log service was created with a database destination before running the Service Pack installer, execute this SQL command on the log service database to change table BASEEVENTFORMAT to add CONVERSATIONID varchar(255):alter table BASEEVENTFORMAT add CONVERSATIONID varchar(255)

2. In the ActiveMatrix Administrator, open the Configure Enterprise Assets perspective > Administrator Cluster > Plug-ins. The TIBCO Common Logging plug-in version should be 1.2.100.

3. If the TIBCO Common Logging plug-in version is not 1.2.100, perform these steps:

a. In the ActiveMatrix Administrator, open the Configure Enterprise Assets perspective -> Administrator Cluster -> Plug-ins. Undeploy the TIBCO Common Logging plug-in.

b. Upload and deploy LogServiceAndViewer.war located in TIBCO_HOME\amxadministrator\plugins.

c. If step b reports an error, manually remove the folder TIBCO_HOME\amxadministrator\data\clustername\servername\archives\ public_html\LogServiceAndViewer

d. Redo step a.

e. Restart the Browser to log in again.

Task H Install ActiveMatrix Service Performance Manager 1.2.0

1. Stop all TIBCO ActiveMatrix processes—ActiveMatrix nodes, SPM node, ActiveMatrix Administrator Server, Management Daemon.


3. Execute following utility to perform sync installation: TIBCO_HOME/amx/2.2/server/bin >SyncInstallation



4. Execute following command from TIBCO_Home/spm/1.2/bin: UpdateInstallation.bat.


— Create data.properties file from the template (TIBCO_Home/spm/1.2/scripts/data.properties-template) and add the appropriate entries as per your environment. Refer to the data.properties file in the TIBCO_HOME/spm/1.1/scripts folder.


Task I Start ActiveMatrix Processes and Upgrade All Nodes

1. Ensure that ActiveMatrix Administrator database is running.

2. If you have created Administrator Server using the Post-installation Configuration tool in ActiveMatrix Service Performance Manager 1.1.1, you must 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

3. Start ActiveMatrix processes in the sequence:


— ActiveMatrix Administrator Server

4. Upgrade all existing runtime nodes on this system as follows:

a. Change to the directory ENV_HOME/tools/bin/.


5. Start SPM node and then all the ActiveMatrix nodes.

In a distributed setup, the Service Probe for ActiveMatrix component of ActiveMatrix Service Performance Manager 1.2.0 must be installed on the machine where ActiveMatrix runtime is installed.


30 | Release Notes

Task J Upgrade SPM Service Assemblies

You can upgrade 1.1.1 service assemblies to 1.2.0 from the command-line or from GUI.

Using CLI



Using GUI







— In Substitution Variables, select and set value for "/com.tibco.matrix.spm.actionservicescomposite/Shared Resources/SubstitutionVariables/snmp_transport_address" to udp:localhost/162 instead of udp:localhost/161.


— Click Deploy.








— In Substitution Variables, select and set value for /com.tibco.matrix.spm.actionservicescomposite/SharedResource

s/SubstitutionVariables/amx_admin_protocol. The value could be http or https.


— Click Deploy.





— In Substitution Variables, select and set obfuscated password value for /com.tibco.alert.delivery.composite/Shared

Resources/SubstitutionVariables/password. If there is no password, then no changes are required.


— Click Deploy.






— Click Deploy.



32 | Release Notes

Scenario 2: Monitoring Only the Standalone TIBCO BusinessWorks ServicesTo install ActiveMatrix Service Performance Manager 1.2.0 over an existing setup of ActiveMatrix Service Performance Manager 1.1.1 with Service Probe for BusinessWorks, follow these steps:

• Task A: Shut down All ActiveMatrix Processes, on page 32

• Task B: Install ActiveMatrix Service Performance Manager 1.2.0, on page 32

• Task C: Upgrade an ActiveMatrix Administrator Server, on page 33

• Task D: Upgrade Management Daemon, on page 33

• Task E: Upgrade SPM System Node, on page 34

• Task F: Upgrade SPM Service Assemblies, on page 34

• Task G: Update BusinessWorks Properties, on page 36

Task A Shut down All ActiveMatrix Processes

Shutdown the ActiveMatrix processes in the given sequence:

— SPM System Node

— ActiveMatrix Administrator servers


Task B Install ActiveMatrix Service Performance Manager 1.2.0



— Create data.properties file from the template (TIBCO_Home/spm/1.2/scripts/data.properties-template) and add the appropriate entries as per your environment. Refer to the data.properties file in the TIBCO_Home/spm/1.1/scripts folder.


3. Execute following utility to perform sync installation:

TIBCO_Home/amx/2.2/server/bin >SyncInstallation



4. Execute following command from TIBCO_SPM_HOME/bin: UpdateInstallation.bat. (or UpdateInstallation.sh)

Task C Upgrade an ActiveMatrix Administrator Server


1. Ensure that the ActiveMatrix Administrator database server is running.


a. Change to the directory TIBCO_Home/tools/bin.

b. Run tibcommander –f TIBCO_Home/amxadministrator/2.2/bin/adminupgradersp1.xml -Dclustername=clustername -Dadminname=servername

-Dadmin.version=2.0 -l adminupgrader.log

where clustername and servername are respectively the names of the cluster and Administrator server.

3. Reinstall the ActiveMatrix Administrator Windows service as follows:

a. Change to the directory TIBCO_Home/amxadministrator/data/clustername/servername/bin

b. Run clustername_servername.exe --uninstall.

c. Run clustername_servername.exe --install -noshell -redirect.

4. Start the server. If you run the server startup script (amx_admin) to start the server, run the file in TIBCO_Home/amxadministrator/2.2/bin/.

5. Clear the browser cache before accessing the ActiveMatrix Administrator UI.

Task D Upgrade Management Daemon

To upgrade Management Daemon:

1. Upgrade all ActiveMatrix Administrator servers bound to that Management Daemon.

In a distributed setup, the Service Probe for BusinessWorks component of ActiveMatrix Service Performance Manager 1.2.0 must be installed on the machine where TIBCO BusinessWorks is installed.


34 | Release Notes



b. Run tibcommander –f ../../managementdaemon/2.0/bin/managementdaemonupgrader.xml.

c. Run tibcommander –f ../../managementdaemon/2.0/bin/MDCacheCleaner.xml.

3. Reinstall the Management Daemon Windows service as follows:

a. Change to the directory TIBCO_Home/managementdaemon/2.0/bin.

b. Run managementdaemon.exe --uninstall.

c. Run managementdaemon.exe --install -noshell -redirect.

4. Start Management Daemon.

Task E Upgrade SPM System Node

To upgrade SPM system node:


2. Upgrade node:


b. Run tibcommander –f ../../amx/2.2/server/bin/nodeupgrader.xml

-Dnodes=<spm_environment_name>/<spm_environment_node_name> -lnodeupgrader.log

3. If the node was installed as a Windows service, reinstall the service as follows:

a. Change to the directory TIBCO_Home/amx/data/environmentname/nodename/bin/.

b. Run <spm_environment_node_name>.exe --uninstall.

c. Run <spm_environment_node_name>.exe --install -noshell -redirect.

4. Start the SPM node.

Task F Upgrade SPM Service Assemblies

You can upgrade 1.1.1 service assemblies to 1.2.0 from the command-line or from GUI.

Using CLI





Using GUI







— In Substitution Variables, select and set value for "/com.tibco.matrix.spm.actionservicescomposite/Shared Resources/SubstitutionVariables/snmp_transport_address" to udp:localhost/162 instead of udp:localhost/161.


— Click Deploy.





— In Substitution Variables, select and set value for /com.tibco.matrix.spm.actionservicescomposite/SharedResource

s/SubstitutionVariables/amx_admin_protocol. The value could be http or https.


— Click Deploy.



36 | Release Notes





— In Substitution Variables, select and set obfuscated password value for /com.tibco.alert.delivery.composite/Shared

Resources/SubstitutionVariables/password. If there is no password, then no changes are required.


— Click Deploy.






— Click Deploy.


Task G Update BusinessWorks Properties

1. Specify values for the required entries in the TIBCO_HOME/spm/1.3/plugins/bwserviceagent.properties file by referring to bwserviceagent.properties file in TIBCO_HOME/spm/1.2/plugins folder.

amx_admin_server_url_delimeteramx_admin_server_urlsamx_admin_server_auth_usernameamx_admin_server_auth_password#Custom Metrics Enable/Disableserviceprobe.custommetrics.enable=true#Test Mode Prefix (If BW Engine Running from command line) com.tibco.spm.bw.serviceprobe.TestModePrefix=test

2. Restart BusinessWorks engine for the changed properties to take effect.



Release 1.1.1The steps to migrate to ActiveMatrix Service Performance Manager 1.1.1 differ depending on your existing setup and product versions.

• If you are upgrading from ActiveMatrix Service Performance Manager 1.1.0 to 1.1.1, follow the steps in Migrating ActiveMatrix Service Performance Manager from Release 1.1.0 to Release 1.1.1 (Standalone) on page 37.

• If you are upgrading to ActiveMatrix Service Performance Manager 1.1.1 over ActiveMatrix 2.2.0, follow the steps in Migrating ‘ActiveMatrix Service Performance Manager’ Installed over ‘ActiveMatrix Service Grid’ on page 39

Migrating ActiveMatrix Service Performance Manager from Release 1.1.0 to Release 1.1.1 (Standalone)

To install ActiveMatrix Service Performance Manager 1.1.1 over an existing setup of ActiveMatrix Service Performance Manager 1.1.0 (with Service Grid nodes and Administrator running), follow these steps:

1. Gracefully stop all the ActiveMatrix components in this order:

— All Service Grid nodes

— SPM System Node

— ActiveMatrix Administrator


— ActiveMatrix Database


3. For ActiveMatrix 2.0.x, set the following database connection parameters in the TIBCO_Home\amx\2.x\server\bin\NodeUpgrader.tra file:

— java.property.db.driver

— java.property.db.url

— java.property.db.user

— java.property.db.password

If you install ActiveMatrix Service Performance Manager 1.1.1 without any underlying ActiveMatrix product (that is, to monitor TIBCO BusinessWorks standalone), follow the instructions specific to ActiveMatrix 2.0.x.


38 | Release Notes

4. Ensure that the ActiveMatrix database is running. For existing nodes, ensure that the nodes are in the stopped state and then run the node upgrader command to upgrade system node and each ActiveMatrix node:

For ActiveMatrix 2.1.0

TIBCO_Home\tools\bin\tibcommander -f TIBCO_Home\amx\2.1\server\bin\nodeupgrader.xml -Dnodes=all

For ActiveMatrix 2.0.x

TIBCO_Home\tools\bin\tibcommander -f TIBCO_Home\amx\2.0\server\bin\nodeupgradersp1.xml -Denvname=<ENV_NAME> -Dnodename=<NODE_NAME>

5. Optionally, to persist the Actions in the database instead of in-memory scheduler, update the existing ActionManagerSA in TIBCO ActiveMatrix Administrator as follows:

a. Start the Management Daemon, ActiveMatrix Administrator, and SPM system node (spmsysenv_sysnode).

b. In TIBCO ActiveMatrix Administrator, select Deploy to an Environment and spmsysenv.

— From the Service Assemblies table, select all service assemblies (SAs) and click Stop.

— Select ActionManagerSA and click Undeploy.


In the Archive File field, click Update.

Browse and select the new ActionManagerSA.zip from the TIBCO_SPM_HOME\assemblies path.

Click OK and Save.

— In Substitution Variables, select amx_admin_root_password and provide the ActiveMatrix Administrator obfuscated password.

c. In TIBCO ActiveMatrix Administrator, select Configure Enterprise Assets > Shared Resource Definition.

— Click New and select JDBC. Configure the JDBC Shared resource as follows:

Name—Quartz JDBC

Connection Type—JDBC

Configure the JDBC Shared Resource with the database used for the ActiveMatrix Administrator.

— Click Save.



— Select the Environment Definition link from the top bar.

— From the Environments table, select the SPM environment spmsysenv.

From the lower panel, select Shared Resource Definition and click Edit.

— From the Shared Resources Definitions table, select the newly added JDBC resource named Quartz JDBC.

— In the Enabled? column, select Yes.

— Click Save.

d. In TIBCO ActiveMatrix Administrator, select Configure an Environment and spmsysenv.

— From the Nodes table, select spmsysenv_sysnode.

— Select Shared Resources, click Edit.

— In the Shared Resources table, for Quartz JDBC, select Yes in the Enabled at Startup? column.

— Click Save.

— Click Install.

e. In TIBCO ActiveMatrix Administrator, select Deploy to an Environment and spmsysenv.

— From the Service Assemblies table, select ActionManagerSA.

— From the lower panel, select Shared Resource Profile and click Edit.

— For QuartzJDBC, in the Shared Resources column, select the newly added Quartz JDBC.

— Click Save.

— Select Deploy to deploy the ActionManagerSA.

— Start all the service assemblies.

6. Start all the service assemblies (SAs) and ActiveMatrix nodes, as required.

Migrating ‘ActiveMatrix Service Performance Manager’ Installed over ‘ActiveMatrix Service Grid’

If you have followed the following installation order, use the following steps to upgrade to ActiveMatrix Service Performance Manager 1.1.1:

1. Install ActiveMatrix Service Grid 2.2.0

Optionally, create ActiveMatrix Administrator Server.

2. Install ActiveMatrix Service Performance Manager 1.1.1


40 | Release Notes

Task A Install ActiveMatrix Service Performance Manager 1.1.1 over ActiveMatrix Service Grid 2.2.0

1. Install ActiveMatrix Service Grid 2.2.0.

2. Optionally, create TIBCO ActiveMatrix Administrator Server.


4. Edit TIBCO_HOME/spm/1.1/scripts/updatespm.xml as follows:

— Locate the line: <include name="com.tibco.neo.launch_1.2.*"/>.

— Replace "1.2.*" with "1.2.3*": <include name="com.tibco.neo.launch_1.2.3*"/>.

5. Run the following commands:

— On Windows:


./tibcommander -f ../../spm/1.1/scripts/updatespm.xml

post.install.tasks.

— On UNIX:

cd TIBCO_HOME/spm/1.2/bin

./spmcmdline.sh ../scripts/updatespm.xml post.install.tasks

6. Perform this step only if ActiveMatrix Administrator Server is already created and you plan to use it with ActiveMatrix Service Performance Manager Post Installation Configuration tool.

Before you run the Post Installation Configuration tool, edit createadminserver.tra in TIBCO_Home/amxadministrator/2.2/bin directory and change the teneo.mapping property to JOINED. The default value is SINGLE_TABLE.

If the file flattening operation fails with java.lang.OutOfMemoryError.Java heap space when running on command line, increase the max JVM Heap Size to 512MB or higher from the original 56MB value and re-run the command.



Change the following: # -- TIBCO Persistence --

# Property for specifying the type of teneo mapping

java.property.teneo.mapping=SINGLE_TABLE

as shown: # -- TIBCO Persistence --

# Property for specifying the type of teneo mapping

java.property.teneo.mapping=JOINED

7. Perform this step only if you plan to create a new ActiveMatrix Administrator Server using the ActiveMatrix Service Performance Manager Post Installation Configuration tool. If you plan to use an existing ActiveMatrix Administrator, you don't need to make this change.

Before running the Post Installation Configuration tool, edit the file updatespm.xml as follows:

— Open the updatespm.xml file located in TIBCO_Home/spm/1.1/scripts directory from any text editor.

— Search for substring="2.0" and locate a line with <contains string="${amxadmin.version}" substring="2.0"/>.

— Replace the substring "2.0" with "2.0.x".

— Save and exit the editor.

8. Edit TIBCO_Home/spm/1.1/postinstalltool/configuration/org.eclipse.update/platform.xml as follows:

— Search for <feature id="com.tibco.tpcl.jdbc" url="features/com.tibco.tpcl.jdbc_1.0.100.003/"

version="1.0.100.003">

— Replace 1.0.100.003 with 1.0.0.010 (version installed with SPM 1.1.x). Your line should look like this: <feature id="com.tibco.tpcl.jdbc" url="features/com.tibco.tpcl.jdbc_1.0.0.010/"

version="1.0.0.010">.

9. Save the changes.

Task B Start all ActiveMatrix Processes

Start ActiveMatrix processes in the sequence:

• ActiveMatrix Database (if not running)

• Management Daemon


42 | Release Notes

• ActiveMatrix Administrator Server

Task C Run ActiveMatrix Service Performance Manager Post-installation

1. Edit TIBCO_HOME/spm/1.1/scripts/data.properties file and update the values of ActiveMatrix Administrator parameters and ActiveMatrix database properties.

2. Run the Post Installation Configuration Tool as follows:

— Go to TIBCO_HOME/spm/1.1/postinstalltool

— run the command: SPMPostInstallTool -clean

3. Use the existing TIBCO ActiveMatrix Administrator Server and complete the ActiveMatrix Service Performance Manager runtime setup.

Release 1.1.0Migration of TIBCO ActiveMatrix Service Performance Manager from 1.0.0 to 1.1.0 release is not supported.


Closed Issues | 43

Closed Issues

The table in this section list issues that were closed in the named releases.

Closed in Release

Change Request ID Summary

1.3.1 SPM-3035 When TIBCO Enterprise Message Service server was stopped and restarted, SPM Rule Service could not reconnect to Enterprise Message Service server.

1.3.1 SPM-3030 Enabling the Service Probe for TIBCO BusinessWorks resulted in the increased response time for the web services created in TIBCO BusinessWorks 5.7.1, 5.7.2 or 5.8.

1.3.1 SPM-3028 Removed support for 32-bit zSeries Linux from the product readme.

1.3.1 SPM-2982 Updated the Release Notes document to specify JRE 1.6.0_18 or higher as a minimum supported version.

1.3.0 SPM-2938 During the BusinessWorks engine startup, the BusinessWorks Service Probe sometimes failed to start (with specific types of projects), and threw the 'java.lang.ExceptionInInitializerError' exception.

1.3.0 SPM-2927 When TIBCO ActiveMatrix BusinessWorks EAR file is deployed in TIBCO Administrator, you can enable or disable "Service Probe for BusinessWorks" through TIBCO Administrator. Refer to TIBCO ActiveMatrix Service Performance Manager Installation guide for the detailed steps.

1.3.0 SPM-2912 Bean Component variables did not work as custom action parameter values.

1.3.0 SPM-549 Custom action incorrectly contained double quotes in a string parameter by schema definition.

1.3.0 SPM-548 All the possible values for MonitoredObjectName context information are documented in the ’Customizing Alert Templates > Beans’ appendix to pass as valid values when used as a parameter in a custom action. See TIBCO ActiveMatrix Service Performance Manager User’s Guide for details.

1.3.0 SPM-536 The View and Manage dashboard showed incorrect Fault/Success statistics for a BusinessWoks process, whenever the process went through an error transition.


44 | Release Notes

1.3.0 SPM-534 When a spurious message came into the queue, the spm.log file showed NullpointerException instead of meaningful message.

1.3.0 SPM-527 TIBCO ActiveMatrix Service Performance Manager supports JRE version 1.6.0.

1.3.0 SPM-524 In the TIBCO ActiveMatrix Service Performance Manager Installation guide, the ’Post Installation Procedure > Administrator Server Database Details’ section clarifies that when Existing Administrator Server option is used during the post-installation, the database configuration is set for the assurance actions only and not for the SPM statistics.

1.3.0 1-96THQ9

SPM-418

(HP-UX Itanium): SPM node crashed with an error and generated a core dump.

1.3.0 SPM-219 The Service Probe for BusinessWorks produced the same logging data to the console every 15 seconds degrading the system performance.

1.3.0 1-9FSHJX

SPM-211

Post-installation: (Solaris10 x86 64 and 32 bit) The Post Installation Configuration tool was not supported on Solaris10 x86 64 bit platform.

1.3.0 SPM-50 In TIBCO ActiveMatrix Service Performance Manager Installation guide, FAQ > Using SSL Enabled EMS in a Distributed Setup section specifies two new properties that need to be set for the SSL Enabled EMS in a distributed setup.

1.3.0 1-9ZT73D

SPM-49

When only Service Probe for BusinessWorks was installed on a machine, the variable ${spm.product.version} was not replaced with correct version in bwengine.tra.

1.3.0 1-A0AKWS

SPM-38

Restarting the BusinessWorks engine or service did not reset the BusinessWorks service or operation status to 0 for the Since Started timeframe.

1.3.0 SPM-15 TIBCO ActiveMatrix Service Performance Manager Installation guide > the ’Supported Services for Performance Monitoring’ section mentions that TIBCO ActiveMatrix Service Performance Manager needs to be installed on the machine where ActiveMatrix Administrator is running. This ensures that UI plug-ins work correctly.

Closed in Release



Closed Issues | 45

1.3.0 SPM-14 Rules based on the Since Started period did not clear even when the statistics was reset as a result of restarting a node or a service.

1.3.0 SPM-13 TIBCO ActiveMatrix Service Performance Manager User’s Guide > ’Building Rules on Custom Metrics : Registering Custom Metrics with the CLI : MetricFunction’ section provides the supported list of aggregate metric functions.

1.3.0 SPM-11 Installing the Service Probe for BusinessWorks on a machine without installing Hibernate was not possible.

1.3.0 SPM-7 TIBCO ActiveMatrix Service Performance Manager User’s Guide > Chapter 3 > Setting the Permission for User Interface section provides information about the type of permission required to Create Rule from the View and Manage dashboard.

1.3.0 SPM-6 Reports were displayed only for ’superuser’ from the View and Manage dashboard. No reports were displayed for a user who was owner or had view or edit permissions only.

1.3.0 SPM-4 The View and Manage dashboard did not show the correct status intermittently for Hit/Faults, even though the service were running.

1.3.0 SPM-2 The Services dashboard did not display any ActiveMatrix services for a user with only read permission for the dashboards.

1.2.0 1-8YPNX1 Rule: When a rule was enabled and disabled repeatedly within a few seconds, an exception was seen in the ActiveMatrix Admin console.

1.2.0 1-91C0F9 Performance: When ActiveMatrix Administrator server with Oracle database was not created using Service Performance Manager post installation tool, the SPM node took approximately 10 minutes to start.

Ensure that the following property is set in SPM node tra file: "java.property.monitormanage.update.schema=false"

1.2.0 1-91RMV7 When logging to the same SQL server instance as that of TIBCO ActiveMatrix data store, exceptions were thrown in the amx_admin node console.

Closed in Release



46 | Release Notes

1.2.0 1-945P9T If you used an authenticated EMS server on a remote machine, setting the EMS password in data.properties and running the post installation using spmcmdline showed a "javax.jms.JMSSecurityException: invalid name or password" exception in the SPM node logs during SPM node startup.

1.2.0 1-96NBBM ActiveMatrix Service Performance Manager did not support blank space in the installation directory.

1.2.0 1-977S1T Infrastructure Dashboard > Single Machine Summary: An unresponsive script error was occasionally seen when the Service Instances tab was selected.

1.2.0 1-978WCX ActiveMatrix node failed to start on a machine on which TIBCO ActiveMatrix 2.0.2 and the Service Probe for ActiveMatrix was installed.

This has been fixed with ActiveMatrix Service Grid 2.2.1 where only ActiveMatrix Service Probe of ActiveMatrix Service Performance Manager 1.2.0 is installed.

1.2.0 1-97BJOO Infrastructure Dashboard: HTML tags were seen in the alert messages for alerts on machines and nodes/engine objects.

1.2.0 1-97GBZA Distributed Setup: In a distributed setup where ’ActiveMatrix Service Performance Manager’ was installed on machines 1 and 2, and ActiveMatrix Administrator was running on machine 1 along with an SPM node and ’ActiveMatrix Service Grid’ node, the Deploy Service action failed because the management daemon was unable to notify the status of the provisioned node in time. The Deploy Service action failed since the node was not up.

1.2.0 1-97SXE5 (Linux 32 bit) When starting a node, the Metrics Manager failed to start and threw a java.lang.UnsatisfiedLinkError error in the node console.

1.2.0 1-97XVVH Rule: If you disabled and enabled monitoring, and created a few rules, the rules did not get triggered even after the rule condition was satisfied.

Closed in Release



Closed Issues | 47

1.2.0 1-9CNEZJ Distributed Setup: In a distributed setup where ’ActiveMatrix Service Performance Manager 1.1.1’ was installed on machine 1 and 2, and Admin and Runtime components of ’ActiveMatrix Service Grid 2.1.0’ were installed on machine 1, if a rule was configured to send an email alert as well as invoke the DeployServiceAction, triggering and clearing the rule threw the “java.lang.reflect.UndeclaredThrowableException” exception.

This has been fixed in ActiveMatrix Service Performance Manager 1.2.0 with ActiveMatrix Service Grid 2.2.1.

1.2.0 1-9CSZMF (Linux) Installing ’ActiveMatrix Service Grid 2.1.0’ over ’ActiveMatrix Service Performance Manager 1.1.1’ and starting SPM Metrics Manager throws java.lang.UnsatisfiedLinkError errors in the system node.

This has been fixed in ActiveMatrix Service Performance Manager 1.2.0 over ActiveMatrix Service Grid 2.2.1.

1.2.0 1-9E5HS3 When ’ActiveMatrix Service Performance Manager 1.1.1’ is installed over ’ActiveMatrix Service Performance Manager 1.1.0’, the property values specified in the data.properties file was replaced with the default values.

The issue no longer exists when ActiveMatrix Service Performance Manager 1.2.0 is installed over 1.1.1.

1.2.0 1-9EHR6Q The Rule service was not fault-tolerant when distributed on ActiveMatrix Service Grid nodes. None of the rule service instances took the role of a master.

Refer to the section Making the Rule Service Fault Tolerance in the TIBCO ActiveMatrix Service Performance Manager Installation guide.

1.2.0 1-9F22I5 (Linux) The post installation task updatespm_bw failed on the Linux 64 bit platform.

1.2.0 1-9FVFSD Migration: While migrating from ActiveMatrix Service Performance Manager version 1.1.0 to 1.1.1 with enabled rules in the triggered state, the triggered rules are re-triggered and actions and alerts are executed.

The issue no longer exists when you migrate a project from ActiveMatrix Service Performance Manager 1.1.0 to 1.2.0.

Closed in Release



48 | Release Notes

1.2.0 1-9FVFSW On migrating a project from ‘ActiveMatrix Service Performance Manager 1.1.0’ to 1.1.1, the SPM Node console threw an "ERROR: Could not synchronize database state with session" exception. The ActionManager and RuleService service assemblies displayed the version number 1.1.0 instead of 1.1.1.

The issue no longer exists when you migrate a project from version 1.1.1 to 1.2.0.

1.2.0 1-9G647B (UNIX): When ActiveMatrix Service Performance Manager 1.1.1 was installed over 1.1.0 with an existing start_default.sh, executing the newly replaced start_default.sh displays a permission denied.

The issue no longer exists when ActiveMatrix Service Performance Manager 1.2.0 is installed over 1.1.1.

1.2.0 1-9GM8CH Performance: If the service was hit while Rules were getting enabled in working memory, the SPM Node console displayed the error "basemodel.datatypes.DoubleMetricHistory ERROR - Invalid double value ? defaulting to 0".

1.2.0 1-9H01YF Post-installation: The ActiveMatrix Service Performance Manager Post- Installation Configuration Tool failed when there were multiple products installed in TIBCO_AMX_HOME. For example,

• TIBCO ActiveMatrix Service Grid 2.1.0

• TIBCO ActiveMatrix Policy Manager 3.0

• TIBCO ActiveMatrix Policy Agent 3.0

• TIBCO ActiveMatrix BusinessStudio Designer 1.0.0 (MTG)

• TIBCO ActiveMatrix BusinessWorks Service Engine 5.7.0

1.2.0 1-9LR1HN A new version of com.tibco.tpcl.jdbc bundled with ActiveMatrix Service Grid 2.2 had some meta-data changes that broke ActiveMatrix Service Performance Manager 1.1.1 Post Installation Configuration tool.

This has been fixed in ActiveMatrix Service Performance Manager 1.2.0 with ActiveMatrix Service Grid 2.2.1.

Closed in Release



Closed Issues | 49

1.2.0 1-9NNSOJ TIBCO ActiveMatrix Service Performance Manager Post Installation Configuration tool failed to create a new ActiveMatrix Administrator when used with an existing installation of ActiveMatrix Service Grid 2.2.0.

This has been fixed with ActiveMatrix Service Grid 2.2.1.

1.2.0 1-9O0J0J When ActiveMatrix Service Performance Manager tried to flatten the *.tra files, it filtered the com.tibco.neo.launch* plug-in with just the <major>.<minor> version. When more than one version of 1.2.x was available in the component store, a stack overflow error was thrown.


1.2.0 1-9O87BR TIBCO ActiveMatrix Service Grid 2.2 used the SINGLE_TABLE teneo option to create tables. After a rule was triggered, the trigger status update failed with a db error about an ambiguous startTime column error.


1.2.0 1-9W2UMN Uninstalling ActiveMatrix Service Performance Manager 1.1.1 removed ActiveMatrix Service Grid hotfixes and other infrastructure virtual product hotfixes.

This has been fixed in ActiveMatrix Service Performance Manager 1.2.0.

1.1.1 1-929NOE TIBCO ActiveMatrix Service Performance Manager installer allowed Service Probe for TIBCO ActiveMatrix feature to be installed on machines without TIBCO ActiveMatrix runtime.

1.1.1 1-9GVWUN Logging: Even after setting the Log Events item in Rule Dashboard > Rule Summary Report, the events were not getting logged for the Common Logging.

1.1.1 1-9GVZ67 In Rules Dashboard > Rule Summary Report > Summary tab, if the Log Events? item is set to 'Yes', the View Log link is now displayed when running ActiveMatrix Service Grid 2.1.0.

1.1.1 1-97N6ST When ’TIBCO ActiveMatrix Service Performance Manager 1.1.0’ was installed over ’TIBCO ActiveMatrix Service Grid 2.1.0’ and the JMS logging was configured to a SQL server database for a node, starting the node displayed a Null Pointer Exception on the node console.

Closed in Release



50 | Release Notes

1.1.1 1-971GIJ When TIBCO ActiveMatrix Service Performance Manager was installed over TIBCO ActiveMatrix Service Grid 2.0.2 and there was an existing ActiveMatrix Admin node, exceptions were seen when Management Daemon was started for the first time.

1.1.1 1-980LRE When ActiveMatrix Service Performance Manager 1.1.0 was installed over ActiveMatrix Service Grid 2.1.0, the stop_default.bat (or stop_default.sh) failed to stop processes.

1.1.1 1-90YEU6 Action Manager: The Action Manager did not resume assurance for custom actions and alerts on restart.

1.1.1 1-91D68F Rules and Rule Packages Report: Incorrect data was displayed in the columns that were based on the selected time period. For example, Triggering Duration.

1.1.1 1-91P1N6 Rules Dashboard: The Trigger table did not respect Past Hour time period. It displayed the data for Period greater than Past Hour.

1.1.1 1-98OESD Post-installation: (Solaris) The ActiveMatrix Service Performance Manager Post- Installation Configuration Tool failed on Solaris 10 Sparc machine with the following setup:

• TIBCO Runtime Agent 5.6.0

• TIBCO ActiveMatrix BusinessWorks 5.6.3

• TIBCO ActiveMatrix BusinessWorks Service Engine 5.6.4

• TIBCO Enterprise Message Server 5.0

• Hibernate 3.2.5

• TIBCO ActiveMatrix Service Grid 2.1

• TIBCO ActiveMatrix Service Performance Manager 1.1.0

1.1.1 1-9CNF38 Rule Builder 2 of 4 - Choose Target Object: No results were displayed when creating a Shared Criteria target object of any Type for a setup where ’ActiveMatrix Service Grid 2.1.0’ was installed over ’ActiveMatrix Service Performance Manager’ and all the servers were upgraded to 2.1.

1.1.1 1-91RJGN Rules Dashboard: The rule summary table columns for #Alerts and #CustomActions showed values for the most recent trigger of this rule and not the accumulated value of all triggers for the rule.

Closed in Release



Closed Issues | 51

1.1.1 1-97HQON Rules Dashboard: Rule Package were not displayed in the Triggered state even when rules inside it were triggered.

1.1.1 1-97J9OM SPM CLI: While exporting the standalone rules, the ‘Keyword’ attribute did not work.

1.1.1 1-97N6DX Alerts: When DWR published a message, the incoming data had wrong value. For example, the target object type serviceOperation showed as Operation.

1.1.1 1-9909LF Documentation: The TIBCO ActiveMatrix Service Performance Manager User’s Guide did not provide steps to configure the mail server.

The detailed steps to configure the mail server are available in TIBCO ActiveMatrix Service Performance Manager Installation guide. See the Frequently Asked Questions > Configuring Mail Server section in the Appendix B of the TIBCO ActiveMatrix Service Performance Manager Installation guide.

1.1.1 1-9AYXF5 Documentation: The TIBCO ActiveMatrix Service Performance Manager User’s Guide does not mention that for custom actions based on "add by endpoint" needs soapAction to be doAction and undoAction respectively.

The following note has been added in Chapter 6 - Setting Custom Action> Actions Editor section:

Note that for the custom actions based on "add by endpoint" needs soapAction to be doAction and undoAction respectively. Also, the custom action endpoint must implement the SPMActionPT port type from the wsdl file located at TIBCO_SPM_HOME/schemas/spmaction.wsdl.

1.1.1 1-9936DL When the BusinessWorks Service Probe started on UNIX, the BusinessWorks Service Agent threw a Null Pointer Exception.

1.1.1 1-996B7H The BusinessWorks Service Agent threw a java.util.ConcurrentModification exception when the monitored service was hit.

1.1.1 1-993T0L If a BusinessWorks project contained a process other than the 'BW Service/SOAP Event Source Process Starter' process (for example, 'JMS Queue Receiver'), the BusinessWorks Service Agent threw a Null Pointer Exception.

Closed in Release



52 | Release Notes

1.1.1 1-996B4Y If a service had a Reference Service (SOAPRequestReply) and the service port name did not match with the binding name in the Reference Service WSDL, the BusinessWorks Service Agent threw a Null Pointer Exception.

1.1.1 1-99B68D If the Reference Service contained the SOAPEventSource Service, BusinessWorks Service Probe did not publish the start/stop event of Reference Services.

1.1.1 1-99CD1R If a Reference Service was configured using the InvokePartner activity, the BusinessWorks Service Probe did not publish statistics for execution of Reference Service.

1.1.1 1-98ZVAN Running ‘TIBCO ActiveMatrix Service Performance Manager’ on ‘ActiveMatrix Service Grid 2.1.0’ and creating a rule on a target object group with shared criteria did not return any results.

1.1.1 1-995U8Z On UNIX, error was thrown when accessing the service, operation, service instance, and operation instance report screens as well as the 'Metrics and Rules' tab in the dashboards.

1.1.1 1-9C9MTO Use of underscore (_) was not allowed while specifying the object names such as Custom Actions, Rules, Rule Packages, Schedules, Objectives, Roles, Target Object Groups, and Custom Metrics.

1.1.1 1-977X50 SPM CLI: When a delete action was performed on a custom metric bundle using the CLI, the custom metrics were deleted but exceptions were seen in the SPM node console.

Closed in Release



Closed Issues | 53

1.1.1 1-9AJOLX Custom Metric: The User Security context document from TIBCO Policy Manager was not available to extract custom metrics information in TIBCO ActiveMatrix Service Performance Manager.

If you use TIBCO ActiveMatrix Policy Manager for Authentication policies and enable Security Context Propagation (see the ActiveMatrix Policy Manager documentation for details), you can register custom metrics to extract information from the SAML 2.0 assertions that contain the user information forwarded by the Policy Manager.

Here is an abbreviated SAML 2.0 assertion sample that is available to Service Performance Manager:

<ns0:SecurityEnvelope xmlns:ns0="http://xsd.tns.tibco.com/2007/scc/envelope" xmlns="http://xsd.tns.tibco.com/2007/scc/envelope" xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> <saml:Assertion ID=" Dc6MDA" IssueInstant="2008-09-18T16:28:12.306-07:00" Version="2.0"> <saml:Issuer>www.tibco.com</saml:Issuer> <saml:Subject> <saml:NameID>John</saml:NameID> </saml:Subject> … … </saml:Assertion></ns0:SecurityEnvelope>

You can write the following custom metric expression to extract a classifier for the user name: {{flow=input,document=userInformation}}//saml:Subject/sa

ml:NameID

where the prefix ‘saml’ is associated with the namespace ‘urn:oasis:names:tc:SAML:2.0:assertion’.

Note that the expression context specifies ‘document=userInformation’. This is a special identifier that ensures that the XPath expression is evaluated in the context of the security context that has been propagated from ActiveMatrix Policy Manager.

For more on SAML 2.0 assertions and their contents, refer to: http://www.oasis-open.org/specs/#samlv2.0

Closed in Release



54 | Release Notes

1.1.1 1-9407ZP

1-9FXPEP

Logging: In Rule Dashboard > Rule Summary Report, even after setting the Log Events item, the events are not getting logged for the Common Logging.

Follow these steps to manually configure the Logging configuration for the standalone use of TIBCO ActiveMatrix Service Performance Manager:

1. Open TIBCO ActiveMatrix Administrator and select Configure Enterprise Assets > Administrator Cluster > Log Service.

a. Click Edit and configure the JMS and JDBC connections by:

— either creating your own JMS and JDBC connections under the Shared Resource Definitions

— or using the Monitoring JMS Configuration and Quartz JDBC Configuration provided by ActiveMatrix Service Performance Manager.

b. Restart the Log Service plug-in by selecting Plug-ins and TIBCO Common Logging plug-in.

2. Select Configure an Environment > spmsysenv environment.

a. Select spmsysenv_sysnode and the Logging Configurations link from the lower panel.

b. Click Edit.

c. Set the Severity to Info and Appender to JMS.

d. Click Apply.

3. Select Deploy to an Environment > spmsysenv environment.

a. Select the ActionManagerSA service assembly and Logging Configurations from the lower panel.

b. Click Edit to update the ActionManagerSA configuration.

c. Set the Severity to Info and Appender to JMS.

d. Click Apply.

Closed in Release



Closed Issues | 55

1-9407ZP 4. Modify the bootStrap.xml file available at TIBCO_Home\amx\data\<SPM_ENV>\<SPM_NODE>\config as follows:

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\matrix-log4j.xml.

b. Copy the appender and logger for "_spmsysenv.spmsysenv_sysnode_appender" from the generated configuration into TIBCO_Home\amx\data\spmsysenv\spmsysenv_sysnode\config\bootstrap.xml after the line containing “”.

c. Modify the name of the newly added appender (SPMLogEventsAppender).

d. Modify the name of the newly added logger to “com.tibco.matrix.spm.rule.log”.

e. Modify the appender-ref reference of the newly added logger to match the name of the newly added appender in step 4c.

After modifications, the updates look as shown:<appender class="com.tibco.commonlogging.appender.BEFJMSAppender" name="logEventsAppender"><param name="serverUrl" value="tcp://localhost:7222"/><param name="retry" value="1"/><param name="password" value="#!piEJaxEeE3wJVWXBW0Si5g=="/><param name="queueName" value="5779cbfe-de10-40e8-9cd1-095020227b18"/><param name="userName" value="admin"/></appender><logger additivity="true" name="com.tibco.matrix.spm.rule.log"><level value="INFO"/><appender-ref ref="logEventsAppender"/></logger>

6. Restart the SPM System Node.

When ‘TIBCO ActiveMatrix Service Performance Manager 1.1.1’ is installed over ‘ActiveMatrix Service Grid 2.1.0’, the issue exists even after performing the above steps (1-9GVWUN).

Closed in Release

56 | Release Notes

1.1.0 1-91RJ0H Installation: Occasionally, Management daemon threw warnings in the Management Daemon console when ActiveMatrix Service Performance Manager was installed over TIBCO ActiveMatrix Service Grid.

1.1.0 1-91K1O1 To create ActiveMatrix Administrator server with Oracle or SQL database using build_runtime_setup.xml, the values for variables DB URL and DB drivers could not be specified in the data.properties.

1.1.0 1-90EPYU ActiveMatrix Service Performance Manager service assembly got deployed with errors when it was redeployed after making changes to substitution variable.

1.1.0 1-91C0NP (UNIX 64 bit only): start_default and stop_default located inside TIBCO_SPM_HOME/bin failed to run with the "Error: JAVA_HOME is not defined correctly. We cannot execute /home/spmqa1/tibspmv18.1/tibcojre/1.5.0/bin/java" exception.

1.1.0 1-91BRBS (Linux): Starting SPM node on a 64 bit machine displayed the following error on the SPM node console:

"Exception in thread "Thread-83" java.lang.UnsatisfiedLinkError:

/home/spmqa1/tibspmv18.1/tibcojre64/1.5.0/lib/amd64/liba

wt.so: Can't load AMD 64-bit .so on a AMD 64-bit

platform".

1.1.0 1-91N3PP BusinessWorks Service Probe: Statistics were not getting updated for BusinessWorks Services having References (SOAP Request Reply). As a result, rules defined on Source (BW Services using SOAP Request Reply activities) were never triggered. The Statistics of the source were getting added to the Reference.

1.1.0 1-91N3QJ BusinessWorks Service Probe: Suspend Starter Process, ResumeProcessStarter, and ResumeAllProcessStartersAndProcesses actions failed when rules were defined on referenced services (SOAP Event Source).

Rules on BusinessWorks referenced services did not work in the 1.0.0 release.

Closed in Release



Closed Issues | 57

1.1.0 1-9171VF In the Rule Packages -> Objectives panel, the View Recipients link was not seen intermittently.

1.1.0 1-8XS3HT Rule Package: While creating an objective for a rule package, the following error was displayed intermittently:

"500 error code, OperationFaultRulesExceptiongetObjectiveRules operation:

The objective id must be of type long".

1.1.0 1-91CAWL Rule Packages: When a rule created from a Rule Package panel was opened for editing, the values specified in the Recipients list did not persist.

1.1.0 1-9130KT Rule Package and Rule: If you use more than 256 characters to specify the name or description of a rule, rule package, or an objective, the "500 error code" exception was thrown. If large descriptions were provided for a rule, the rule summary panel did not display data for Target Object, Conditions, Alert, Action, or Log.

1.1.0 1-8ZLYB7 Rule Library: If you edit a rule, and change certain fields such as name, the prompt to save the changes did not appear.

1.1.0 1-91EK3B Rule Library: Search failed while searching for a string with combination of a number or capital letter as first letter or second, that is, 1A, A1, 1Aaa.

1.1.0 1-91HTM6 Rule Package: Deleting an objective from a rule package directly deleted the objective without any user confirmation.

1.1.0 1-91G0ZF Rule Package: Saving a rule package without specifying the Role displayed the following error:

"Server response: soapenv:ClientOperationFaultRulePackagesExceptionThe Role

id must be of type long"

1.1.0 1-91G5TW Rule: An incomplete Rule could also be enabled as part of Rule Package.

Closed in Release



58 | Release Notes

1.1.0 1-91R22N Rule: When a rule with aggregate function 5th percentile was created, the count metric function was used instead of 5th percentile aggregate function.

1.1.0 1-91ADVZ Rule Editor: On editing a rule, the Revert button should not be enabled for any step unless any data was modified on the step. Currently, the Revert button is enabled when you click Edit for a rule.

1.1.0 1-91QSX9 Rule: While defining a rule on BW Services/Operations no Actions were displayed by default on Step 4 of 4 - Set Actions. Search with "*" also failed to return any results.

1.1.0 1-9116TA Rule: Rules did not get triggered for the metric “# of services" for Node if used with the operators "Less than Equal to", "Less than", "Equal to" and "Not Equal To".

1.1.0 1-91QSXU Rule: Rule defined on Groups using the "Current Selection" criteria on Service Instance/Operation Instance were not getting triggered.

1.1.0 1-9171HN Rule: When a rule condition was set on the metric called Running on target objects and the SPM node was restarted, a series of Trigger and Clear alerts were displayed after every one minute. The Administrator console showed XFire exceptions.

1.1.0 1-90QY0V Rule Builder: Step 2 of 4 - Choose Target Object dialog, the Group Members list showed a node twice when clicked on View Members in Create Group Based on Shared Criteria for Type Node.

1.1.0 1-9171GQ Rule Builder: Step 2 of 4 - Choose Target Object dialog, the service instances and service operation instances were displayed in the Deployment tab. Service Instances were seen when All Services Assemblies option was selected and Service Operation Instances were seen when All Service option was selected.

1.1.0 1-8ZJ91H Rule Builder: Step 2 of 4 - Choose Target Objects dialog, TIBCO BusinessWorks Service Operations did not appear for selection if the corresponding BusinessWorks services were not executed at all.

1.1.0 1-8XT3Q0 Rule Builder: Step 2 of 4 Choose Target Object, when you search for a service and select the same service, the Current Selection and Path to Selection showed the same value. The Path to Selection now shows the complete path, environment>node>services.

Closed in Release



Closed Issues | 59

1.1.0 1-8ZK7G5 Schedules: Non admin user could not replace schedules with other schedules using the Replace Individually option.

1.1.0 1-90OK3F Browse in Dashboard: When Browse > Rules is clicked and multiple rule packages are selected, all the objectives in the selected rule packages were not displayed for selection.

1.1.0 1-8ZU5TS Alerts: The metric name was not seen intermittently in the email alert subject line for the first trigger alert.

1.1.0 1-90P8AU Alert: The metric value displayed in the email alert for Total Physical Memory size for a machine was wrong. It showed 2147483647 for the first trigger.

1.1.0 1-91113P Alert: The value of TotalSwapSpaceSize was seen in bytes while the value of FreeSwapSpaceSize is in kilobytes in the email alert. Both were not consistent and displayed in MB.

1.1.0 1-90WK49 Alert: The username was seen as null in the email alert if the alert was configured to send to a Group.

1.1.0 1-90RCT2 Alert: The metric value displayed in the email alert for deployedServiceCount was wrong.

1.1.0 1-91O7CT Alert: Alerts were not generated for objective rules when sent to Group recipients. ’Destination not found’ error was seen in the spm.log file.

1.1.0 1-90RD3D Referenced Target Objects: The Group Criteria column showed an internal ID for Group target objects.

1.1.0 1-90O8X3 Custom Action: The custom actions ProvisionNode and DeployService did not check for type of target objects. If a user tried to set these actions on BusinessWorks target objects in the Rule Builder Step 4 of 4 - Set Action, the system failed perform a check and threw exceptions.

1.1.0 1-8ZLYHJ Custom Action: The custom actions KillAllProcess, StopApplicationInstance, SuspendAll and DelayedStopApplicationInstance Actions failed with an exception.

Closed in Release



60 | Release Notes

1.1.0 1-91ERT2 SNMP Action: The spmAlertState variable did not show the severity in text. It just showed an integer and user id to look at the MIB to find the corresponding severity.

1.1.0 1-91EROI SNMP Action: The SNMP alert message did not display the metric units in the condition statement.

1.1.0 1-91ERRG SNMP Action: The metric value for Deployed Service Count was displayed as null in the SNMP alert message.

1.1.0 1-8ZTUPL SNMP Action: The spmAlertConditions fields did not show the actual value that generated the alert in the SNMP alert message.

1.1.0 1-91ERUQ SNMP Action: If the User defined Templates parameters were not specified for an SNMP User Trap action, it did not use the bundled user alert templates. NullPointerException was seen in the spm.log file.

1.1.0 1-8YS0FI SPM CLI: Using CLI, a hidden action could also be set as a Custom Action for a rule.

1.1.0 1-90WE7O SPM CLI: The sum or count aggregator function were not supported for creating rule condition through CLI.

You can use the sum but avoid using the count aggregator function.

1.1.0 1-91D7RS SPM CLI: The log details for any execution using spmcmdline.bat were stored in admincmdline.log instead of spmcmdline.log in TIBCO_SPM_HOME/data/logs.

1.1.0 1-8YS09H SPM CLI: It was possible to create a rule on one type of target object and condition could be set on different type of target objects using CLI. That is, a rule had JavaHelloComp service as target object but had condition set on Node type of target object.

1.1.0 1-91P0US Alert: The Group Id was seen in the generated email alert if Consumer and Provider values are Groups.

1.1.0 1-8ZK0LT Rules Dashboard: If the rule was enabled and disabled multiple times, trigger table only showed triggers since the last time the rule was enabled.

Closed in Release



Closed Issues | 61

1.1.0 1-8Z3V6X Rules Dashboard: The View drop-down and Set Columns icon did not appear in Internet Explorer but appear in Firefox browser.

1.1.0 1-91G5NH Rule Dashboard: The Currently Triggered or Currently Not Triggered options were applicable only to the rules displayed on the current page. The filter options should filter rules on all the pages.

1.1.0 1-91P70R Rules Dashboard: When a Rule Packages contains multiple rules in an Objective and if they were viewed in the Rules dashboard, "Unresponsive Script" warning message was displayed.

1.1.0 1-91RJ83 Service Dashboard: The JVM Committed Memory column was empty in Services and Operations table.

1.1.0 1-8WK31H Performance: SPM node consumed more than 1 GB of memory when kept running for more than 24 hours.

Closed in Release



62 | Release Notes

1.1.0 1-8ZNOPP SPM Logging: The ActiveMatrix Service Performance Manager logs were not printed in a single file. Some exceptions were getting printed in the log file whereas some related exceptions were printed in the SPM node console.

To get all logs in one file, edit TIBCO_HOME/amx/data/<sysenv>/<sysnode>/config/bootStrap.xm:

In <main_configuration>/<base_hierarchy>/<log4j:configuration> add:

<appender name="SPMFileAppender" class="org.apache.log4j.RollingFileAppender"><param name="File" value="spm.log"/><param name="MaxFileSize" value="2048KB"/><param name="MaxBackupIndex" value="9"/><layout class="org.apache.log4j.PatternLayout"><param name="ConversionPattern" value="%d [%t] %-5p - %m%n"/></layout></appender><logger name="com.tibco.matrix.spm" additivity="false" ><level value ="WARN"/><appender-ref ref="SPMFileAppender"/></logger><logger name="com.tibco.matrix.monitoring" additivity="false" ><level value ="WARN"/><appender-ref ref="SPMFileAppender"/></logger><logger name="com.tibco.matrix.servicegrid.monitoring" additivity="false" ><level value ="WARN"/><appender-ref ref="SPMFileAppender"/></logger><logger name="com.tibco.cep" additivity="false" ><level value ="WARN"/><appender-ref ref="SPMFileAppender"/></logger>

SPM logs can be found under TIBCO_HOME/amx/data/<sysenv>/<sysnode>/logs/spm.log.

Closed in Release

Known Issues | 63

Known Issues

The table in this section lists known issues in this release.

Change Request ID Summary/Workaround

Installation, Setup, and Migration

SPM-3038 Summary The Rule Service does not auto-reconnect to TIBCO Enterprise Message Service when the EMS configuration is specified using JNDI.

Workaround Restart the Rule Service to reconnect to the Enterprise Message Service server.

1-9ZMF8R

SPM-51

Summary If ActiveMatrix Service Performance Manager is installed in a directory with spaces in the directory name, stop_default.bat fails to stop processes with "failed to open files" error.

Workaround Edit build_stop.xml located in TIBCO_SPM_HOME\scripts and add single quotes arguments specifying spmcmdline.tra and spm_bootstrap.xml as shown:

<arg line=' "${spm.home}/bin/spmcmdline.tra" '/><arg line=' "${spm.home}/scripts/spm_bootstrap.xml" '/>

SPM-2935 Summary When migrating from TIBCO ActiveMatrix Service Performance Manager version 1.2.0 to 1.3.0, an error about a missing plug-in is displayed.

Workaround It is a harmless error and can be safely ignored. Even though the flattener complains about the missing dependency for a "com.tibco.matrix.spm.serviceprobe.admin.services.impl_1.3.0" plug-in, it correctly includes the latest version of that plug-in (1.4.0).

SPM-2992 Summary If TIBCO ActiveMatrix Service Performance Manager is to be reinstalled, all the components installed earlier must be selected for reinstallation.

Workaround None

1-A03F9A

SPM-43

Summary Using the SSL enabled JMS in the distributed multi-platform environments is not supported.

Workaround None

1-9TPBQP

SPM-125

Summary When the database is down, the alerts data is lost and is not displayed in the Dashboard UI.

Workaround None


64 | Release Notes

1-9UCZBJ

1-9WZL5A

SPM-93

Summary The rule service does not start when:

• Monitoring is disabled or enabled,

• The monitoring configuration is changed, or

• The rule service is restarted.

Workaround Restart the nodes hosting rule service Java Service Unit.

1-9RWEW1

SPM-143

Summary Rules do not get triggered if the Rule ServiceSA is stopped and restarted.

Workaround Restart the SPM node.

1-97XTGR

SPM-369

Summary When you disable and enable monitoring for two ActiveMatrix Administrator instances cluster setup, the Monitor & Manage perspective does not display new statistics and a Null Pointer Exception is seen in the spm.log file. Starting the rule service displays multiple exceptions in the spm.log file and fails to trigger any rules.

Workaround: Restart the SPM node.

1-9V0A5S

SPM-110

Summary When restarted, the rule service can take a few minutes to completely initialize. This time can increase with the number of monitoring domains. You should take this initialization time into account when maintaining the rule service.

Workaround None

SPM-2986 Summary (Windows 64 bit) After installing TIBCO ActiveMatrix Service Performance Manager 1.3.0, running the post-installation tasks for BusinessWorks service probe' fails. That is, UpdateInstallation script fails to update BusinessWorks installation if run after installation.

Workaround Reinstall all the ActiveMatrix Service Performance Manager components that were installed earlier (that is, the components that were installed before installing TIBCO BusinessWorks).

For example, if you have installed only the ’ServiceProbe for BusinessWorks’ component of ActiveMatrix Service Performance Manager 1.3.0 before installing TIBCO BusinessWorks, reinstall only ’ServiceProbe for BusinessWorks’ component of ActiveMatrix Service Performance Manager 1.3.0.

1-960FRJ

SPM-445

Summary The BusinessWorks engine startup time with the 'BusinessWorks service probe' enabled is more than without the BusinessWorks service probe installed.

Workaround None



Known Issues | 65

SPM-2932 Summary During the BusinessWorks engine startup, the ActiveMatrix BusinessWorks Service Probe failed to start sometimes and threw the 'java.lang.ExceptionInInitializerError' exception.

Workaround Open the defaultVars.substvar file from the BusinesWorks Project and assign "domain" as value to the Domain global variable.

1-9TWG2N

SPM-122

Summary If ActiveMatrix and WAS service probes are running on the same Windows machine, the rule set on Free Physical Memory condition gets triggered and cleared continuously.

Workaround None

SPM-2911 Summary If a container process is killed for WAS or BusinessWorks services and you do not hit any service, the container status does not appear Stopped in the UI even after 5 minutes.

Workaround Hit any service once and then kill the container process to update the status in the UI.

1-9YU04X

SPM-66

(UNIX): Running the UpdateInstallation.sh script on UNIX throws exceptions.

Workaround Increase the JVM heap size in TIBCO_SPM_HOME\bin\spmcmdline.tra to 512MB or higher.

1-A1D8GX

SPM-29

Summary (SUSE Linux Enterprise Server v10) The Rule Service failed to start with a "UnsatisfiedLinkError" error in the spm.log file.

Workaround Remove ../ from the end of tibco.env.LD_LIBRARY_PATH=%tibco.flattener.library.path%%PSP%%LD_LI

BRARY_PATH%%PSP%/home/user/tibcospmga/tibcojre64/1.5.0/lib/amd64/..

/ from the spmsysenv_spmsysenv_sysnode.tra file and restart the system node.

1-97LX3J

SPM-377

Summary After installing ActiveMatrix Service Performance Manager over TIBCO ActiveMatrix Service Grid 2.1 using an Oracle database, when you login to TIBCO ActiveMatrix Administrator for the first time, an error 500 message with a stack dump is displayed.

Workaround Restart the ActiveMatrix Administrator and the SPM Node spmsysenv_sysnode processes.



66 | Release Notes

1-96THP5

SPM-419

Summary When you start ActiveMatrix Management Daemon on a machine on which TIBCO Rendezvous is not installed, error messages such as: "SpmMaAmiAdapter - Error initializing SPM Machine Agent: Native implementation required" are seen in the Management Daemon log file.

Workaround These errors can be ignored. These are harmless error messages that do not prevent the functioning of the Service Performance Manager machine agent.

SPM-2989 Summary FT Mode: When the Rule Service is configured to run in a fault tolerant mode, an exception is occasionally seen in logs while stopping a node with rule service running.

Workaround It is a harmless exception that can be ignored.

1-9YPZUL

SPM-69

Summary FT Mode: When running the rule service in the fault tolerance mode, if the secondary node and then the primary node is shutdown, NPE is seen in the primary node console. The java.lang.RuntimeException: Error in persistServiceAssembly exception is also seen in the spm.log file.

Workaround It is a harmless exception that can be ignored.

1-9VR6G6

SPM-103

Summary FT Mode: When running the rule service in the fault tolerance mode, if the primary rule service goes down and the secondary rule service becomes primary, the service data may be lost occasionally for a fraction of a minute.

Workaround None

1-9RA669

SPM-145

Summary FT Mode: When the rule service is setup in the fault tolerance mode and the Java component of the rule service is redeployed on nodes other than the SPM system node, none of the new nodes appear as the primary nodes in the spm logs.

Workaround

1. Stop all nodes in the SPM environment.

2. Restart the SPM node and let it start completely.

3. Restart the fault tolerant nodes.

The first fault tolerant node which starts up completely becomes primary.

SPM-2914 Summary When the alert service is set to fault tolerant mode and the SPM profile > Frequency is set to Batch per hour, duplicate alerts are sent instead of a single alert.

Workaround None



Known Issues | 67

1-9RFM6H

SPM-144

Summary FT Mode: In the fault tolerance mode of rule service, RuleServiceProvider fails to start on stopping and restarting the RuleServiceSA.

Workaround

1. Stop the SPM node and the fault tolerant nodes.

2. Restart the SPM node and let it start completely.

3. Restart the fault tolerant nodes.

Post Installation

1-9XVDUE

SPM-77

Summary The default Oracle driver provided by ActiveMatrix Service Performance Manager does not support TAF feature of Oracle clusters.

Workaround Use vendor specific drivers such as Oracle thick driver to support TAF. Add the custom JDBC driver jar files under TIBCO_HOME/amxadministrator/lib/ext and restart your TIBCO ActiveMatrix Administrator. To make the custom driver class available during service invocation, copy the driver files to TIBCO_HOME/amx/server/lib/ext area. Enter the appropriate JDBC driver class and URL in the fields provided in the post-installation configuration tool.

For example, for Oracle Thick driver:Database JDBC URL: oracle:oci:@<ServiceName>

Database JDBC Driver: oracle.jdbc.driver.OracleDriver

1-A07OQJ

SPM-40

Summary When Oracle thick driver is used to connect to the ActiveMatrix Administrator Server database, the Test Connection button fails to test the database connection and always gives a Success message.

Workaround None

1-9UUCHN

SPM-112

Summary When multiple users install ActiveMatrix Service Performance Manager in different locations on the same machine and try to run the Post-installation tool, the post-installation fails while uploading the Service Assemblies.

Workaround Set the java.property.java.io.tmpdir property to a fresh directory in the TIBCO_Home\amxadministrator\data\amx\admin\bin\amx_admin.tra file.



68 | Release Notes

1-9Q5XJS

SPM-155

Summary Post-installation: Running ActiveMatrix Service Performance Manager Post- Installation Configuration Tool overwrites the selected Shared Resource for monitoring and uses a non SSL JMS for monitoring.

Workaround After running the ActiveMatrix Service Performance Manager Post- Installation Configuration Tool, manually configure the JMS Configuration for monitoring: Access the Configure Enterprise Assets perspective > Administrator Cluster > Monitoring Configuration and select the appropriate JMS Configuration

1-9CG0YE

SPM-319

Summary The ActiveMatrix Service Performance Manager Post- Installation Configuration Tool does not provide an option to cleanup all the tasks performed while setting up SPM runtime.

Workaround To manually cleanup the SPM runtime, execute the following command:

1. TIBCO_SPM_HOME\bin>spmcmdline ..\scripts\spm_bootstrap.xml spm-e2b

This command cleans up the SPM environment in ActiveMatrix Administrator.

2. TIBCO_Home\amxadministrator\<amx_version>\bin> deleteadminserver.exe ..\..\data\amx_admin.xml

This command deletes the ActiveMatrix Administrator server.

1-9UVM1O

SPM-111

Summary Stopping the SPM Node after the post-installation throws "org.quartz.JobPersistenceException" in the spm.log file.

Workaround It is harmless error that can be ignored.

1-9X3ETO

SPM-90

Summary (zLinux) The script does not exit even after the post installation is executed from the command line.

Workaround Kill the ActiveMatrix Management Daemon externally using the killall command.

1-9YRVSX

SPM-67

Summary (HP-UX Itanium) After running the post-installation tool with the Create New ActiveMatrix Administrator option, the ManagementDaemon does not automatically stop and throws an error.

Workaround Kill the ManagementDaemon process manually after the Post-installation.



Known Issues | 69

1-9YQKM3

SPM-68

Summary (AIX) The post-installation fails as Administrator Server takes a long time to automatically load the SPM plug-ins.

Workaround Once the post-installation fails:

1. Manually start the database (if not running), ManagementDaemon, and ActiveMatrix Administartor.

2. Load spmui.war and rajax.war plug-ins located at TIBCO_HOME\amxadministrator\plugins manually.

3. Re-run the post-installation tool and proceed with spm runtime setup using the existing Administrator Server option.

Uninstallation

1-9145SZ

SPM-493

Summary Uninstaller: Uninstallation of BusinessWorks Service Probe does not remove all the entries added to the bwengine.tra file during installation. Also, this does not impact the behavior of BusinessWorks Services.

Workaround Run the following command:


tibcommander.exe -f ../../spm/1.1/scripts/updatespm.xml pre.uninstall.tasks.bwserviceprobe

1-96KPTR

SPM-428

Summary Uninstalling ActiveMatrix Service Performance Manager which was installed on top of ActiveMatrix Service Grid 2.0.2 fails. Starting Management Daemon throws com.tibco.neo.launch.LaunchException error and also Node installation fails.

Workaround Remove SPM references from admin.tra, node.tra, and amx_osgi.properties

Command Line Interface (CLI)

1-95XD2V

SPM-446

Summary SPM CLI: Template is not exported when exportAll is setup or Template element is specified in SPM CLI export data file.

Workaround Preserve the template file used to load the templates using SPM CLI.



70 | Release Notes

1-9YU2V5

SPM-65

Summary CLI: When you use Oracle as a ActiveMatrix database and run the post-installation script post-node-startup for the first time from the command line, a Constraint Violation Error (cannot insert NULL into ("SPM"."METRICS MANAGERCONFIGURATION"."CURRENTMETRICSMANAGERNODE")) is seen in the ActiveMatrix Administrator.

Workaround This error can be ignored as all the post-node-startup tasks get executed successfully.

1-95VOJD

SPM-450

Summary SPM CLI: After adding a new user using the "username" attribute of SPMAdminTask, if you add an SPM object from the SPMAdmin task with the new username, occasionally the previous user appears as owner for that particular object in the GUI.

Workaround Separate user creation and rule creation into different spmcmdline runs.

1-9S3F83

SPM-140

Summary Custom Metric: Custom Metric bundle name can not have a hyphen in the name.

Workaround Do not use hyphen (-) in the custom metric bundle name.

1-9Y9CWX

SPM-72

Summary Custom Metric: When the custom metrics or the custom metric bundles defined on the service operation are deleted and new requests are sent, the service and operation statistics do not get updated. Hibernate related exceptions are seen in the spm.log file.

Workaround After deleting the custom metrics, restart the SPM node or the node hosting the rule service.

1-9VJ9QR

SPM-108

Summary Custom Metric: Deleting custom metric throws exceptions in the SPM node logs.

Workaround Stop the SPM system node and then delete the custom metric bundle using the CLI.

Dashboards in TIBCO ActiveMatrix Administrator

1-9108QK

SPM-494

Summary Monitor & Manage: When rule service is stopped, Monitor & Manage shows services as running even if the node on which the services are running is stopped.

Workaround Restart rule service.



Known Issues | 71

1-9Z8S0B

SPM-63

Summary Monitor & Manage: At the time of node being installed/started/stopped/uninstalled, attempts to access/refresh the Monitor & Manage dashboard may result in a 500 error (org.hibernate.exception.LockAcquisitionException).

Workaround None

1-9U6DAV

SPM-115

Summary Dashboards and Summary Reports: When the node hosting the rule service is stopped, the JVM memory statistics do not get updated for other runtime nodes in the dashboards and summary reports. For example, the JVM memory value is displayed even for the stopped nodes.

Workaround Run the rule service in the fault tolerance mode.

1-91RJLP

SPM-487

Summary While accessing the server using Internet Explorer 7.0, a runtime error dialog pops up.

Workaround Follow these steps:

1. Open Internet Explorer.

2. On the Tools menu, click Internet Options.

3. Click the Advanced tab.

4. Make sure that the Disable Script Debugging check box is selected, and then click Apply.

5. Close Internet Explorer.

1-97LW9D

SPM-378

Summary SPM Profile: The language set in SPM Profile is not reflected in the alerts generated.

Workaround None

1-9WDI2M

SPM-101

Summary SPM Profile: The Time Zone value set in Alert Preferences under SPM Profiles is not reflected in Alert Message.

Workaround None

1-9Y0MUD

SPM-75

Summary Rule: If a rule is in the triggered state and the target object associated with it is removed, the rule does not get cleared.

Workaround Before undeploying a target object, disable the rule associated with it.

1-9FV5B9

SPM-210

Summary Rule: When a rule is enabled, stopping and starting the ActiveMatrix Administrator and SPM system node throws errors in the log files.

Workaround Ignore these errors as they are harmless.



72 | Release Notes

1-93XQNH

SPM-472

Summary Rule: A rule on service operation instance target object includes a condition on containing service operation or service does not trigger even when the conditions are met.

Workaround None

1-91CQUX

SPM-492

Summary Rule: The rule service always takes the old target object even when the rule is disabled and edited to use a new target object.

Workaround

1. Disable the rule.

2. Duplicate the rule.

3. Change target object in the newly created rule.

4. Enable the new rule.

SPM-2936 Summary (HP-UX Itanium) Rule: Creation of rule fails when servers are run as a root user.

Workaround

1. Edit TIBCO_HOME/amxadministrator/data/<adminClusterName>/<adminNodeName>/bin/<adminClusterName>_<adminNodeName>.tra and add the following line:

java.property.java.security.egd=/dev/random

2. Restart TIBCO ActiveMatrix Administrator.

1-96X1ED

SPM-415

Summary Rule Builder 2 of 4 - Choose Target Objects: The results returned by the Name filter for For Shared Criteria target objects are not case sensitive.

Workaround None. Group filter criteria keys are case insensitive.

1-9Z9R9C

SPM-62

Summary Rule Builder 2 of 4 - Choose Target Objects: The Save and Next button is incorrectly enabled under the following conditions:

• A Target Object Group of type Based on Current Selection is being configured.

• The current selection is an All option.

• The current selection is selected in a non-AMX Monitoring Domain.

Workaround Close the Rule Builder and then edit the rule.



Known Issues | 73

1-9ZV1QG

SPM-44

Summary Rule Builder 2 of 4 - Choose Target Objects: After selecting the Create Custom Group option, the system incorrectly allows you to add a WAS cell from the Monitoring Domains in the Group field. If you add a WAS monitoring domain and click Save and Next, an error dialog is displayed.

Workaround Do not add All Cells or a WAS Cell to a custom group. By mistake if you do, close the error dialog and then the Rule Builder. You can edit the rule to configure the target object appropriately.

1-97CZPA

SPM-387

Summary Rule Builder 3 of 4 - Create Conditions: The aggregate drop-down is not visible if the name of the target object is long.

Workaround Use higher screen resolutions to develop rules in the Build & Configure Rules perspective.

1-940GAS

SPM-470

Summary Custom Action: Even if the rule associated with the SNMP Alert Action is disabled, the SNMP trap message includes rule conditions.

Workaround None

1-9VUF8P

SPM-102

Summary Rule, Custom Action, Schedule: When Oracle or SQL Server 2005 is used as the database and you enter a number (for example, 123) to specify the name of a rule, action, or schedule, 500 error code is seen.

Workaround Do not use alpha-numeric numbers in the name.

1-9T34Q9

SPM-130

Summary Rule, Alert: The third rule condition metric value shows as "null" in an alert under the following 2 conditions:

1. The triggering target object is a WAS or WCF operation.

2. The third condition is on a classifier metric.

Workaround None

1-9X8VTV

SPM-88

Summary Schedule: The Schedule Builder does not accept start time as 12 PM or 12 AM and throws an error "The end time should be greater than the start time!".

Workaround Use CLI to create such schedules.

1-9753XU

SPM-406

Summary Dashboard: In Internet Explorer, the "Failed to read input error" exception is seen occasionally.

Workaround Ignore this error as it is harmless and continue using Internet Explorer.



74 | Release Notes

1-9ZHWML

SPM-56

Summary View and Manage Dashboards: In Browse mode, if you select All Machines or All Services and click the View Details button, a blank report or an error dialog appears.

Workaround Do not click the View Details button when an All option is selected. If View Details is clicked then navigate away from the report screen.

1-9ZLFH9

SPM-54

Summary View and Manage Dashboards: When you click the View Logs button on a Report screen of a WAS or WCF object (machine, service container, service, or operation), an error dialog is displayed.

Workaround Logging on WAS and WCF objects is currently not supported.

1-97AR3A

SPM-396

Summary Rules Dashboard: The filter drop-down does not display using the default resolution 1024x768.

Workaround The filter drop-down is visible in resolutions higher than 1024x769.

1-9432W9

SPM-469

Summary Rules Dashboard: Rule Package Report: The column display configuration is not preserved while switching between flat and hierarchical views in the same report.

Workaround None

1-9FA5PH

SPM-222

Summary Rule Dashboard: The statistics in the Trigger table do not get updated dynamically when columns are added or removed from the Master table or when an Alert windowshade is opened.

Workaround If you change columns or view alerts in the Dashboard screens, click the Refresh button to get dynamic updates to visible columns.

1-97NHLL

SPM-376

Summary Rules Dashboard: The Trigger Start Time and Trigger End Time in the Rule and Rule Packages table displayed the last Trigger instance's Start Time and End Time irrespective of the Time period selected.

Workaround None

1-A0AT75

SPM-37

Summary Rule Dashboard: In Multiple Rules Report, alerts are not displayed in the Alerts tab.

Workaround Use one of the following ways to view the alerts:

• Access the Alerts tab of the single Rules report

• Select the rules in the Rules Dashboard to populate the Alerts table.



Known Issues | 75

1-9ZT73Y

SPM-48

Summary Infrastructure Dashboard: If the service is deployed on multiple nodes and some of the nodes are in stopped state, the service instance status toggles between Running and Stopped state but the rule service processes the service instances correctly.

Workaround None

1-97GC57

SPM-385

Summary Infrastructure Dashboard: Start date and Uptime for newly deployed service instances is same of the containing service's start time.

Workaround None

1-9Y6AYX

SPM-73

Summary Infrastructure Dashboard: In a Service, Operation and Service Container Report, accessing the Operations, Rules, or the Service Instances tab for the first time does not display any data in Firefox 3.0.

Workaround Click another tab and then the Operation, Rules, or Service Instances tab to see the data.

1-9RY975

SPM-142

Summary Infrastructure Dashboard: The value for CPU Time and CPU Usage appears 0 for WAS servers on all platforms except Solaris.

Workaround None

1-9ZX3KM

SPM-45

Summary Reports: In the View and Manage Dashboards perspective, the report screens do not correctly render for WCF, WAS, and ActiveMatrix objects.

Workaround Restart the management daemon.

1-9VOTY2

SPM-105

Summary (HP-UX Itanium) Infrastructure Dashboard: The Open File Descriptor value is not published for TIBCO ActiveMatrix node.

Workaround None

1-9XX5P2

SPM-76

Summary (AIX and zLinux) Infrastructure Dashboard: The values for the following metrics do not get published for TIBCO ActiveMatrix, BusinessWork, and WAS Service probes on the platforms that use IBM JDK:

• Committed Virtual Memory Size

• Free Physical Memory Size

• Free Swap Space Size

• Process CPU Time

• Total Swap Space Size

Workaround None



76 | Release Notes

Miscellaneous

1-9YU4MJ

SPM-64

Summary If a new node is created with the same name as a previously deleted node, the Hit statistics data associated with the deleted node incorrectly displays for the newly created node.

Workaround None

1-9WFV01

SPM-100

Summary Restarting the database throws exceptions in the spm.log file.

Workaround Use the fault-tolerant database configuration or restart the SPM node when the database is restarted.

1-9ZM1XT

SPM-52

Summary BusinessWorks Tutorial: If ActiveMatrix Service Performance Manager is installed in a directory with spaces in the name, the tutorial for ActiveMatrix BusinessWorks fails to load.

Workaround Edit tutorial_build.xml and add correct quotes for BusinessWorks project paths as shown below.

<param name="args" value='-p ${TIBCO_BW_HOME}/bin/bwengine.tra "${tutorial.root}/bw/BookOrderBWProject" '/>

1-9QLXQF

SPM-153

Summary ActiveMatrix Policy Manager: While associating TIBCO ActiveMatrix Policy Manager with SPM Environment, if the ActiveMatrix plug-in agent is running on SPM System node, the Policy Manager console shows the agent status as degraded.

Workaround Policy Management of SPM system services is not recommended.

1-9ASQX9

SPM-359

Summary BusinessWorks Tutorial: In the BusinessWorks tutorial, editing a BusinessWorks rule before hitting the corresponding BusinessWorks service or operation once (that is, before sending a single request), throws a "java.lang.NullPointerExceptionorg.apache.axis2.AxisFault" exception.

Workaround Edit the rule using Command Line Interface (CLI).

1-95TLMZ

SPM-451

Summary When ActiveMatrix Administrator Server is created with Oracle database, service assemblies in Deploy to an Environment perspective occasionally show status as "Running with Errors" when started.

Workaround Wait for a few minutes, the status will correctly show "Running".

