xMatters 4.1 patch 010 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-010

Build: 1006

Revision: 49454

Re-release: January 3, 2012

Build: 1011

Revision: 50457

NOTE: This document is subject to change after the initial release of this patch. If you would like to be alerted when the document is modified, clickReceive email notifications on the Actions menu to the right of this document.

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.

Re-released on January 3, 2012

This patch was re-released for the following reasons:

  • Addressed an issue where a User could inadvertently create a Coverage Rotation Team that was not associated with a Coverage on which to base the rotation.
  • Addressed an issue where a User could inadvertently update a Coverage Rotation Team so that its next rotation was over-written. This would cause the Team to rotate immediately, resulting in what appeared to be a double Rotation.

Support Policy Reminder

The xMatters Support Policy was updated in February 2009.

Features Added In This Patch Release

For more details about the features below, see the 4.1 Patch 10 and 4.0 Patch 18 New Feature Overview.

New Team Type: Coverage Rotation

Support has been added for a new Team type: the Coverage Rotation Team changes the order in which members are contacted based on how often a particular Coverage occurs. For configuration details, refer to thexMatters user guide for this patch (to be republished shortly after this patch is released).

(xMatters Reference: PRE-7688)

Quotas Page

Company and Super Administrators can now view the Company Quotas page to view how they are tracking against subscribed licensing. For details, refer to the xMatters installation and administration guide for this patch (to be republished shortly after this patch is released).

(xMatters Reference: PRE-7801)

Current User Added to "Recently Used" List

The current web User is now available to select in the Recently Used list when sending a message or adding members to a Team.

(xMatters Reference: PRE-7800)

FindWhoIsOnDuty web service now returns Temporary Replacements

The FindWhoIsOnDuty web service now lists a User's Temporary Replacements in the results, rather than the original User.

(xMatters Reference: PRE-7882)

Purge Security Audits now available as a Schedule Job

The Purge Security Audits feature has been moved to the Process Expired Data page, available via the Schedule Job menu on the Admin tab in the web user interface. This consolidates all of the purge/archive data tasks in one place.

(xMatters Reference: PRE-7880)

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

Temporary Replacements causing extra entry in the Exhaustive Report.

Details

PRE-7683

Exported Submitted Notifications Reports display "N/A" in the Recipient column.

Details

PRE-7681, PRE-7680

Duplicate vox files and database entries when adding a recording.

Details

PRE-7664

FindWhoIsOnDuty web service does not properly return list of Devices.

Details

PRE-7797

The purge data jobs incorrectly remove some recurring Coverages.

Details

PRE-7817

Upgrade Oracle 11g driver to JRE 1.6.

Details

PRE-7798

Export Integration returns a stack trace when there are German characters in script.

Details

PRE-7835

Exported monthly report for Groups shows incorrect dates.

Details

PRE-7925

Health Monitor does not check database connectivity.

Details

PRE-7826

Encoded URLs cause issues on BlackBerry Devices.

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-010.tar.gz
  • PATCH-410-010.zip
  • PATCH-410-010-DataSync.tar.gz
  • PATCH-410-010-DataSync.zip

WebSphere Files

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

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

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

  • PATCH-410-010-axis2-websphere7.war: Contains xMatters Web Services files.
  • PATCH-410-010-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 an xMatters 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-010.zip or PATCH-410-010.tar.gz file to the xMatters installation directory.
  3. Do one of the following:
    • On Windows, extract (i.e., unzip) the PATCH-410-010.zip file to the installation directory and overwrite the existing files.
    • On Unix, run the following commands on the PATCH-410-010.tar.gz file and overwrite the existing files:

gunzip PATCH-410-010.tar.gz

tar -xvf PATCH-410-010.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-010-DataSync.zip file to the installation directory and overwrite the existing files.
    • Run the following commands on the PATCH-410-010-DataSync.tar.gz file and overwrite the existing files:

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

tar -xvf PATCH-410-010-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

Temporary Replacements causing extra entry in the Exhaustive Report.

When sending a notification to a Group that includes Users with assigned Temporary Replacements and notification delays, the Exhaustive Report includes a duplicate entry ("User A is replaced by User B") for the Users with Temporary Replacements.

(xMatters Reference: PRE-7676)

Exported Submitted Notifications Reports display "N/A" in the Recipient column.

When exporting the Submitted Notifications Report to Excel, the Recipient column only contains "N/A" instead of the expected target recipient.

(xMatters Reference: PRE-7683)

Duplicate vox files and database entries when adding a recording.

When adding a new recorded message to an Event Domain that does not exist in the system, the script adds two recordings, one to "common", and one to "null". The recording should only be added as a global recording.

(xMatters Reference: PRE-7681)

FindWhoIsOnDuty web service does not properly return list of Devices.

When sending a FindWhoIsOnDuty request with the includeRecipientDetails flag set to true, the returned results should include a "devices" sublist containing the Device details of the returned Users. Instead, this sublist is empty.

(xMatters Reference: PRE-7664)

The purge data jobs incorrectly remove recurring Coverages.

The Process Expired Data settings (accessed via the Schedule Jobs page in the web user interface) incorrectly calculate the start point for some recurring Coverages and delete them unnecessarily.

(xMatters Reference: PRE-7797)

Upgrade Oracle 11g driver to JRE 1.6.

According to Oracle, using the Java5 drivers for 10g with the 11g database is an unsupported deployment.

(xMatters References: PRE-7817)

Export Integration returns a stack trace when there are German characters in script.

When using the Export Integration feature (available on the Event Domains page in the web user interface), the application returns a stack trace if there are German characters within the script.

(xMatters Reference: PRE-7798)

Exported monthly report for Groups shows incorrect dates.

When exporting a Group's monthly schedule to Excel, the dates for the start and end of the report may be incorrectly advanced by one day.

(xMatters Reference: PRE-7835)

Health Monitor does not check database connectivity.

Due to the implementation of a separate feature, the Health Monitor no longer checks database connectivity and does not send email messages in the event of a connection failure.

(xMatters Reference: PRE-7925)

Encoded URLs cause issues on BlackBerry Devices.

Encoded URLs cause BlackBerry Devices (BES OS version 5.x and 6.x) to incorrectly display the URL.

(xMatters Reference: PRE-7826)

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.

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- 2933 Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk