xMatters 4.1 patch 011 Release Notes

Contents

Document Overview

Release Overview

Installing This Patch

Appendices

Document Overview

These release notes are for the following xMatters patch release: 

Patch version: PATCH-410-011

Build: 1050

Revision: 50672 

Release date: January 18, 2012

NOTE: This document is subject to change after the initial release of this patch.

Release Overview

This is a cumulative patch for version 4.1.0 features and issues, and should be applied to all xMatters Application Nodes, Notification Nodes and Web Servers (and to the DataSync Server, if applicable). Before applying this patch, you must upgrade to xMatters 4.1.0. 

Because this is a cumulative patch, you should install the patch with the highest version number. For an overview of features and fixes included in previous patch releases, see the 4.1 patch 010 release notes

Support Policy Reminder

The xMatters Support Policy was updated in February 2009. 

Features Added In This Patch Release

Template Company Script Packages

Administrators can now choose whether Companies in a multiple-Company deployment should use the Template script packages for their Event Domains, or whether to use the script package from an imported Event Domain. For more information about this feature, consult the xMatters installation and administration guide.

(xMatters Reference: PRE-7969, PRE-8030)

New scripting method to "Check for Next"

A new scripting method has been added to the notification object: @notification::isEscalatable determines whether the notification can be escalated using the notifyNext method. For more information, see the xMatters Online Developers Guide.

(xMatters Reference: PRE-7968)

Updated graphing library

The library used by xMatters to generate and display the Node Network Statistics and User and Group Performance Reports has been updated to be compatible with more browser versions and to improve visibility.

(xMatters Reference: PRE-6850)

Added support for HTTP proxies to the HTTP Device Engine

The HTTP Device Engine has been updated to allow the use of Socket Proxies, similar to the existing WCTP process. For more information about this feature, see the xMatters installation and administration guide.

(xMatters Reference: PRE-8037)

Issues Fixed in This Patch Release

To see details about an issue, click the related link in the Details column:

xMatters ReferenceIssue Fixed
Details Link

PRE-7845

Auto-archive purge job incorrectly removes lengthy One Time Coverages.

Details
PRE-7935 Stack trace when a Group Supervisor views a Team of which they are a member Details
PRE-7937 Unable to import a previously exported Event Domain into xMatters Details
PRE-7956 Adding a Subscription via web services does not allow Device Type Overrides Details
PRE-8046 Implemented a change to address Health Monitor and OutOfMemory errors Details
PRE-8049 Application Audit Report filters incorrectly expect numeric values Details
PRE-8051, PRE-8052 Issues with Coverage Rotation Teams cause stack traces and skipped rotations Details
PRE-8067 When creating a One Time Coverage, the default option is Reuse Existing Team Details

 

Installing This Patch

Apply this patch to all xMatters Application Nodes, Notification Nodes and Web Servers (and any DataSync installations, if applicable).

Files Included With This Patch

  • PATCH-410-011.tar.gz
  • PATCH-410-011.zip 
  • PATCH-410-011-DataSync.tar.gz
  • PATCH-410-011-DataSync.zip 

WebSphere Files

You can find the following archive files listed with their associated patches here

  • PATCH-410-011-websphere.tar.gz
  • PATCH-410-011-websphere.zip 

These archive files contain the following WAR files for use with IBM WebSphere 7:

  • PATCH-410-011-axis2-websphere7.war: Contains xMatters Web Services files.
  • PATCH-410-011-cocoon-websphere7.war: Contains web user interface files.

If you have already deployed these files on a previous xMatters deployment, you must uninstall the existing files and then reinstall the new files based on the instructions in the "Advanced xMatters Administration" chapter of the xMatters Installation and Administration Guide.

Warning: Existing Integrations

When applying an xMatters patch to an existing; installation, the patch may overwrite some files that were already modified for an integration. This may cause the integration to stop working. If this occurs, using the integration documentation, re-apply the configuration changes and validate the integration. (See also Integration stops working after applying AlarmPoint patch.) 

In particular, note that the following xMatters integrations may edit pre-existing xMatters Node or Web User Interface files:

  • HP NNMI: Updates web.xml in webserver\webapps\axis2\WEB-INF (see the section "Initialize the Incident Subscription Manager" in the integration guide)
  • HP Service Manager (Adv): Updates classpath on node-start.conf on Windows and node.sh on Unix (see the section "Initialize the Web Services Library" in the integration guide)
  • HP Service Center (Adv): Updates classpath on node-start.conf on Windows and node.sh on Unix (see the section "Initialize the Web Services Library" in the integration guide) 

Warning: Database Changes

Be aware that this patch includes the following database changes that may impact your replication mechanism (consult with your database administrator for further details):

DDL

On all supported databases (Oracle, SQL Server, DB2):

  • Adds table DATABASECHANGELOG
  • Adds column CUS_FIELDS to table NTFN_EVS
  • Creates index IDX_DISPATCH on table LIVE_NTFN
  • Adds Procedure DISPATCH_QUERY 

On DB2 Only

  • Adds Type NTFN_IDS BIGINT ARRAY[]

DML

On all supported databases (Oracle, SQL Server, DB2):

  • Updates table PROV_PROTS setting SESSION_MAX_SIZE
  • Adds Node Component: Notification Response Processor
  • If missing, re-add permission 18210 (view.menuitem.AddCustomPage) to function 100 (Super/Company Administrator)
  • If missing, re-add permission 18211 (view.screen.AddCustomPage) to function 100 (Super/Company Administrator)

Pre-Installation Steps

Before installing this patch:

  1. Shut down all Node processes.
  2. Shut down all Webserver processes.
  3. Back up the xMatters Database. 

Note:This patch includes path names longer than 100 characters. As a result, you must use a GNU-compatible version of tar to extract the tar archives.

Installation Steps

To install this patch:

  1. Back up the xMatters installation directory (<xMHOME>).
    • On Windows, default install directory is: C:\Program Files\AlarmPointSystems\AlarmPoint
    • On Unix, default install directory is: /opt/alarmpointsystems/alarmpoint
  2. Save the PATCH-410-011.zip or PATCH-410-011.tar.gz file to the xMatters installation directory.
  3. Do one of the following:
    • On Windows, extract (i.e., unzip) the PATCH-410-011.zip file to the installation directory and overwrite the existing files.
    • On Unix, run the following commands on the PATCH-410-011.tar.gz file and overwrite the existing files:

gunzip PATCH-410-011.tar.gz

tar -xvf PATCH-410-011.tar

  1. If you are applying this patch on:
  • Windows 32-bit, delete the following files from the Windows\system32 folder (if the files are present):
    • alarmpoint_sapi_tts.dll
    • alarmpoint_mapi.dll
  • Windows 64-bit, delete the following files from the Windows\system32\sysWOW64 folder (if the files are present):
    • alarmpoint_sapi_tts.dll
    • alarmpoint_mapi.dll
  • AIX, move the libjspAixPpc.so file from /AIX (located in the extracted patch directory) to <xMHOME>/jre/bin
    • Navigate to the <xMHOME>/jre/bin directory and set the proper permissions by executing the following command line:

chmod 755 libjspAixPpc.so

  • HP-UX Itanium, move the libjspHpxIa64.so file from /HPUX (located in the extracted patch directory) to <xMHOME>/jre/bin
    • Navigate to the <xMHOME>/jre/bin directory and set the proper permissions by executing the following command line:

chmod 755 libjspHpxIa64.so

  • HP-UX PA-RISC, move the libjspHpxPaRisc.sl file from /HPUX (located in the extracted patch directory) to <xMHOME>/jre/bin
    • Navigate to the <xMHOME>/jre/bin directory and set the proper permissions by executing the following command line:

chmod 755 libjspHpxPaRisc.sl

  • Linux 32-bit, move the libjspLux86.so file from /Linux (located in the extracted patch directory) to <xMHOME>/jre/bin
    • Navigate to the <xMHOME>/jre/bin directory and set the proper permissions by executing the following command line:

chmod 755 libjspLux86.so

  • Linux AMD 64-bit, move the libjspLux86_64bit.so file from /Linux (located in the extracted patch directory) to <xMHOME>/jre/bin
    • Navigate to the <xMHOME>/jre/bin directory and set the proper permissions by executing the following command line:

chmod 755 libjspLux86_64bit.so

  1. Do one of the following:
    • If you have not installed the DataSync component, skip to "Post-Installation Steps", below.
    • If you have installed the DataSync component, complete the remaining steps.
  2. Back up the xMatters DataSync installation directory.
    • On Windows, default DataSync install directory is: C:\Program Files\AlarmPointSystems\AlarmPoint_DataSync
    • On Unix, default DataSync install directory is:/opt/alarmpointsystems/alarmpoint_datasync
  3. Do one of the following:
    • Extract (i.e., unzip) the PATCH-410-011-DataSync.zip file to the installation directory and overwrite the existing files.
    • Run the following commands on the PATCH-410-011-DataSync.tar.gz file and overwrite the existing files:

gunzip PATCH-410-011-DataSync.tar.gz

tar -xvf PATCH-410-011-DataSync.tar 

Post-Installation Steps

After installing this patch:

  1. Restart the Node processes.
  2. Restart the web server processes. 

Important:

  • Database upgrades may take place after this patch is applied (i.e., during startup of xMatters components). The first component to be started will cause the database upgrades to be applied. This means that the subsequent startup of web servers and nodes may be delayed while they wait for the database updates to be completed. To monitor the progress of the updates, see "Determining the status of database updates", below.
  • Due to a relative paths issue, the database cannot be patched when the webserver is running on IBM WebSphere.

Determining the status of database updates

To determine the current status of database updates, open the log file(s) associated with the first xMatters component being restarted (default locations shown; only one log will include the MUTEX entries): 

Node

<xMHOME>/logs/AlarmPoint.txt 

Web Server

<xMHOME>/webserver/webapps/axis2/WEB-INF/logs/AlarmPoint_WebApp.log

<xMHOME>/webserver/webapps/cocoon/WEB-INF/logs/AlarmPoint_WebApp.log

<xMHOME>/webserver/webapps/mobilegateway/WEB-INF/logs/AlarmPoint_WebApp.log 

During component restart, you will see log entries similar to the following:

2009-01-21 22:07:02,251 [AlarmPoint Node-main] WARN - - Acquiring patch update MUTEX.
2009-01-21 22:07:21,685 [AlarmPoint Node-main] WARN - - Acquired patch update MUTEX.
2009-01-21 22:07:22,356 [AlarmPoint Node-main] WARN - - Package 1 of 8 (4.1.x/oracle/01.xml)
2009-01-21 22:07:22,356 [AlarmPoint Node-main] WARN - - Statement 1 of 2: Executing SQL Statement.
2009-01-21 22:07:22,506 [AlarmPoint Node-main] WARN - - Statement 2 of 2: Executing SQL Statement.
2009-01-21 22:07:22,516 [AlarmPoint Node-main] WARN - - Package 2 of 8 (4.1.x/oracle/02.xml)
.
.
.
2009-01-21 22:07:22,847 [AlarmPoint Node-main] WARN - - Package 8 of 8 (4.1.x/oracle/finalize.sql)
2009-01-21 22:07:22,936 [AlarmPoint Node-main] WARN - - The database update scripts have been successfully processed and deleted.
2009-01-21 22:07:22,936 [AlarmPoint Node-main] WARN - - Patch update MUTEX released.

After the message "Patch update MUTEX released" appears in the log, the database update has completed. 

Note: If the log shows that the process has not proceeded from "Acquiring patch update MUTEX" to "Acquired patch update MUTEX" in a timely manner, ensure that there are no locks on the ORGS database table. 

Appendices 

Appendix 1: Details For Issues Fixed In This Release

Auto-archive purge job incorrectly removes lengthy One Time Coverages.

When calculating which Coverages should be removed by the auto-archive process, xMatters was using the start date of One Time Coverages. This could result in long-running One Time Coverages (i.e., longer than the purge frequency) to be removed before they expired. xMatters now uses the end date of One Time Coverages to determine whether they should be purged..

(xMatters Reference: PRE-7845)

Stack trace when a Group Supervisor views a Team of which they are a member

When a Group Supervisor was a supervisor of a Group and also belonged to a Team within that Group, the Team details page would throw a stack trace if the Group Supervisor attempted to view the Team members. This issue has been addressed.

(xMatters Reference: PRE-7935)

Unable to import a previously exported Event Domain into xMatters

When importing an Event Domain into xMatters, the process would return an error related to a PropertyDescription pattern. This was due to an incorrect handling of carriage returns within an Event Domain Constant value. This issue has been addressed.

(xMatters Reference: PRE-7937, PRE-6912)

Adding a Subscription via web services does not allow Device Type Overrides

The deviceTypeOVerrides parameter within the AddSubscription web service was incorrectly attempting to set Device Type Overrides using Device names, not types. This issue has been addressed.

(xMatters Reference: PRE-7956) 

Implemented a change to address Health Monitor and OutOfMemory errors

Implemented a change originally intended to address Health Monitor and OutOfMemory errors in the xMatters on demand environment. These changes were determined to benefit other multiple-Company deployments, and are now included in other versions of xMatters.

(xMatters Reference: PRE-8046)

Application Audit Report filters incorrectly expect numeric values

The filters on the Application Audit Report page (e.g., the "Group_Name" column) would not accept text input, such as "Operations", or other Group names. These filters no longer expect a numeric input and should now accept text.

(xMatters Reference: PRE-8049)

Issues with Coverage Rotation Teams cause stack traces and skipped rotations

It was possible to create a Coverage Rotation Team that was not based on a Coverage, or based on an invalid Coverage. The interface has been updated to require that a Coverage Rotation Team be based on a valid Coverage and, in the event that a Coverage Rotation Team does not have a Coverage on which to base its rotations, its Team type will be reset to Basic.

(xMatters Reference: PRE-8051, PRE-8052))

When creating a One Time Coverage, the default option is Reuse Existing Team

Previously, when a Group Supervisor added a One Time Coverage to a Group, the default option for the Team details page was to reuse the existing Team. To make the process more consistent with the feature and more convenient for users, the default option is now "Modify Existing Team".

(xMatters Reference: PRE-8067) 

Appendix 2: Notice of Name Change

AlarmPoint Systems, Inc. is now xMatters, inc. This change extends to how we name our products: the AlarmPoint Integration Agent is now the xMatters integration agent; AlarmPoint Enterprise is now xMatters enterprise; and so on. 

You can learn more about why we changed our name here

During the ongoing transition to the new naming conventions, legacy corporate and product names will still appear in some parts of our products, such as directory paths, logs, and messages. This document reflects the new names whenever possible, while respecting the need for clarity when referring to older products, legacy issues, existing knowledge base articles, etc. 

For more information (including instructions on how to switch between the AlarmPoint and xMatters interfaces), see Common questions about rebranding from AlarmPoint to xMatters

Appendix 3: Known Issues

On Linux, serial modem Device Engines (TAP, GSM, etc.) that have experienced a connection failure due to a modem power failure (or deliberate power down) do not recover after the modem is powered on. Instead, to resolve the problem the node must be restarted. NOTE: this issue occurs only when Flow Control is set to "hardware".

(xMatters Reference: PRE-4832) 

xMatters (alarmpoint) engine version 4.0 patch 10 and version 4.1 patch 2 introduced an upgrade script that added Oracle function-based indices to improve performance. However, these indices will not become effective and used by the Oracle Cost Based Optimizer (CBO) until the statistics are gathered for the related tables and the indices themselves. For more information, see Why isn't Oracle using available indices?.

(xMatters Reference: PRE-68) 

Even when the xMatters integration agent submits a message to a Company other than the Default Company, the integration agent log indicates that the message was submitted to the Default Company.

(xMatters Reference: APE-13596)

Appendix 4: DDL Changes in This Release 

The following DDL changes have been made for this patch release:

  • Updated NODES to all have existing URLs starting with ‘tcp://’ instead of ‘http://’
  • Updated QCPS COMPONENT_TYPE for QCP_KEY HM_EXECUTABLE
  • Increased the size of USER_AGENT column to 1200

xMatters Reference

JDN-3064 Originally created by Cameron Stewart

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk