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

Build: 1360

Revision: 72707 

Release date: March 6, 2014 

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 xMatters 4.1 patch 021 Release Notes

It is strongly recommended that you review the Patch Release Notes for all patch levels between your current patch level and this latest release before applying the upgrade. Some patches may require specific configuration changes not included in these release notes. 

Issues Fixed in This Patch Release

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

Reference  Issue FixedDetails
APO-7770 Unable to import text phone devices via data sync when the system is in legacy mode Details
ARCH-2050 Node unable to establish bidirectional communication Details
SCO-4091 Auto-archive job does not check the status of notifications before delinking Details
XFO-4876 User Upload is case-insensitive when verifying, but case-sensitive when processing Details
XFO-4879 FindWhoIsOnDuty web service call fails for old rotation teams Details
XFO-5012 Data synchronization does not retain team membership order Details
XFO-5013 Full access user is able to see groups in tenant company 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-022.tar.gz
  • PATCH-410-022.zip 
  • PATCH-410-022-DataSync.tar.gz
  • PATCH-410-022-DataSync.zip 

WebSphere Files

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

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

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

  • PATCH-410-022-axis2-websphere7.war: Contains xMatters Web Services files.
  • PATCH-410-022-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 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: Spring Configuration Changes

When applying an xMatters patch, any changes you have made to the parameters in spring configuration files may not be retained. The patch may overwrite modifications to some or all of the following files:

node\assets\resources\spring\integration\*.xml

webserver\webapps\cocoon\WEB-INF\classes\resources\spring\integration\*.xml

webserver\webapps\axis2\WEB-INF\classes\resources\spring\integration\*.xml

webserver\webapps\mobilegateway\WEB-INF\classes\resources\spring\integration\*.xml 

Warning: c3p0.properties file

It is recommended that you backup the c3p0.properties file for each of the Nodes in your deployment as this file may also be affected by the patch process. Once the patch process is complete, you can use any text editor to compare your back up copy with the one installed by the patch and copy over any customization or other configuration changes. 

Warning: Database Changes

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

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 

Note: If you are installing on Windows, you must run the installer as an administrator. 

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-022.zip or PATCH-410-022.tar.gz file to the xMatters installation directory.
  3. Do one of the following:
    • On Windows, extract (i.e., unzip) the PATCH-410-022.zip file to the installation directory and overwrite the existing files.
    • On Unix, run the following commands on the PATCH-410-022.tar.gz file and overwrite the existing files:
gunzip PATCH-410-022.tar.gz
tar -xvf PATCH-410-022.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, libalarmpoint_att_tts.so and libalarmpoint_att_tts_51.so files 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
chmod 755 libalarmpoint_att_tts.so
chmod 755 libalarmpoint_att_tts_51.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-022-DataSync.zip file to the installation directory and overwrite the existing files.
    • Run the following commands on the PATCH-410-022-DataSync.tar.gz file and overwrite the existing files:
gunzip PATCH-410-022-DataSync.tar.gz
tar -xvf PATCH-410-022-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. The default locations are shown; only one log will include the MUTEX entries. Note also the log level indicated in the messages below; if your logging level is not detailed enough, you will not see the log messages. 

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 

Unable to import text phone devices via data sync when the system is in legacy mode

An issue with the data synchronization feature was preventing text phone devices from being imported properly when the system was in legacy mode. This issue has been addressed.

Node unable to establish bidirectional communication

A rare error was identifed where two previously-stable nodes were unable to establish bidirectional communication. This was traced to an issue with the timing used to reestablish connections after a node disconnected; previously addressed for xMatters version 5.1, this change has now been included in version 4.1.

Auto-archive job does not check the status of notifications before delinking

The auto-archive job did not check the status of notifications before issuing a DelinksNotificationsMessage command. This caused unnecessary duplication of commands and retrieval of notification objects from the database. This issue has been addressed.

User Upload is case-insensitive when verifying, but case-sensitive when processing

An issue was identified with the User Upload tool's validation feature. When validating the upload file, the tool would ignore case-sensitive errors, but then flag the errors when actually processing the upload job, causing a null pointer exception (but no stack trace. To address this issue, both the validation and the upload process are now case-insensitive.

FindWhoIsOnDuty web service call fails for old rotation teams

An issue was identified where the FindWhoIsOnDuty web service call would fail when retrieving information for old rotation teams. This was traced to an issue with the way the database handled the rotation direction, and would not accept a null value. To address this issue, a null value for the rotation direction field will be set by default to SECOND_TO_FIRST.

Data synchronization does not retain team membership order

In some cases, the data synchronization tool was not honoring the defined order of members within a team, and also not retaining specified escalation delays. This issue was traced to the way the database was stored the membership order as a character sequence instead of a numerical value, and has been addressed.

Full access user is able to see groups in tenant company

An issue was identified where a "Full Access User" could see groups in a tenant company. This was traced to an error with the checkObserverStatus method for groups, and has been addressed. 

Appendix 2: 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 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 3: Database Changes in This Release

This release includes the following DDL and DML updates: 

DDL Changes:

  • Add index IDX_AU_NT_EV_RECIP on AUDIT_NTFN_EVS(RECIPIENT_ID)
  • Add index IDX_AU_NT_EVA_RECP on AUDIT_NTFN_EVS_ARC(RECIPIENT_ID)
  • Add index IDX_LIV_NTN_DVC_ID on LIVE_NTFN(DVC_ID)
  • Add index IDX_DVC_DELETED_ID on DVC(DELETED_ID)

DML Changes:

  • None

xMatters Reference

JDN-4612 Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk