xMatters 4.1 patch 018 Release Notes

Document Overview

Release Overview

Installing This Patch

Document Overview

These release notes are for the following xMatters patch release:

Patch version: PATCH-410-018

Build: 1

Revision: 63083

Release date: March 21, 2013

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, click Following in on the Actions menu to the right of this document, and then select the Inbox check box.

Release Overview

This is a MANDATORY cumulative patch for xMatters version 4.1.

This patch addresses an issue introduced in 4.1 patch 014 that caused unnecessary updates to a Company's Device Names from the node. The system was always treating the data as having been modified, resulting in unnecessary updates to the related database table. This unnecessary database activity (i.e., processing high volumes of events) may result in system delays.

There are two methods available to address this issue:

  1. You can apply this patch, which will automatically make the necessary changes to your system.
  2. You can perform the changes manually. For instructions on modifying the configuration files related to this issue, see this knowledge base article.

NOTE: Because this patch includes only the change discussed above, these release notes should be considered supplementary to the xMatters 4.1 patch 017 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.

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

WebSphere Files

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

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

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

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

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

gunzip PATCH-410-018.tar.gz

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

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

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

xMatters Reference

JDN-4057 Originally created by Cameron Stewart

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk