xMatters 4.0 patch 023 Release Notes


Document Overview

Release Overview

Installing This Patch


Document Overview

These release notes are for the following xMatters patch release: 

Patch version: PATCH-400-023

Build: 500

Revision: 55969 

Release date: October 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.0.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.0.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.0 patch 022 release notes). 

Note: Language Translation Pack 4.0.0 is included with this patch; you do NOT need to install it separately).

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

This patch includes minor bug fixes and updates.

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-400-023.tar.gz
  • PATCH-400-023.zip 
  • PATCH-400-023-DataSync.tar.gz
  • PATCH-400-023-DataSync.zip

WebSphere Files

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

  • PATCH-400-023-websphere.tar.gz
  • PATCH-400-023-websphere.zip 

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

  • PATCH-400-023-axis2-websphere7.war: Contains xMatters Web Services files.
  • PATCH-400-023-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: 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: 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:





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:


2. Save the PATCH-400-023.zip or PATCH-400-023.tar.gz file to the xMatters installation directory. 

3. Do one of the following:

  • On Windows, extract (i.e., unzip) the PATCH-400-023.zip file to the installation directory and overwrite the existing files.
  • On Unix, run the following commands on the PATCH-400-023.tar.gz file and overwrite the existing files:

          gunzip PATCH-400-023.tar.gz

          tar -xvf PATCH-400-023.tar 

4. 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 

5. 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. 

6. 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:


7. Do one of the following:

  • Extract (i.e., unzip) the PATCH-400-023-DataSync.zip file to the installation directory and overwrite the existing files.
  • Run the following commands on the PATCH-400-023-DataSync.tar.gz file and overwrite the existing files:

          gunzip PATCH-400-023-DataSync.tar.gz

          tar -xvf PATCH-400-023-DataSync.tar 

Post-Installation Steps

After installing this patch:

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


  • 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


Web Server




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.0.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.0.x/oracle/02.xml)
  2009-01-21 22:07:22,847 [AlarmPoint Node-main] WARN - - Package 8 of 8 (4.0.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. 


Appendix 1: Details For Issues Fixed In This Release

This patch includes minor bug fixes and updates.

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

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 the Knowledge Base Article "Why isn't Oracle using available indices?" available on the xMatters Support site.

(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) 

Unexpected results occur in the xMatters Web User Interface and notification process when a Group's Timezone is different than the associated Site's Timezone for excluding Holidays. For example, if the Group is configured for the US/Pacific Timezone and its Site is US/Eastern, a Holiday on March 14 (the first day of Daylight Savings Time), the Holiday will incorrectly extend into March 15. As a result, it is recommended that the Group's Timezone matches the Site's Timezone if Holidays are to be excluded from the Coverage.

(xMatters Reference: APE-10288/14885/17156/17978)

xMatters Reference

JDN-3333 Originally created by Don Clark

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk