These release notes are for the xMatters 5.1 release:
Release version: PATCH-510-007
Release date: September 23, 2015
To download the latest version, see the xMatters 5.x Product Suite page.
NOTE: This document is subject to change after the initial release. If you would like to be alerted when the document is modified, click Follow above this article.
This release of xMatters offers the following deployment options:
- You can install this release as a new xMatters version 5.1 deployment (i.e., you do not need to install a previous version of xMatters);
- You can use this release to patch an existing xMatters 5.x deployment up to xMatters version 5.1 patch 007 (in this case, this release should be applied to all xMatters application nodes, notification nodes, web servers, and to the Data Sync server, if applicable); or,
- You can use the included database migration tool to upgrade from xMatters 4.1 patch 023 directly to xMatters version 5.1 patch 007 (for more information and complete migration tool instructions, refer to the xMatters 5.x Documentation).
The following table lists the issues addressed since the most recent patch release and included in this version of xMatters. To see details about an issue, click the related link in the Details column:
|ARCH-3256||Notification Summary report not calculating responses correctly||Details|
|KAM-1352||Advanced Messaging scenarios not using Priority value as set in Handling section||Details|
|KAM-1399||Group synchronization over SOAP returning UNKNOWN_APPLICATION_ERROR||Details|
|SCO-6698||Deleted subscriber causing Archive/Purge job to fail||Details|
|UTA-140||Component Status Summary report shows integration services as links||Details|
|XFO-6235||Integration agent stops working if non-printing control characters included in APXML content||Details|
|XFO-6294||Cannot re-install an existing node||Details|
|XFO-6300||Attempting to save a SIP device engine causes stack trace||Details|
|XFO-6321||FindWhoIsOnDuty SOAP web service fails when the date range contains a holiday shift||Details|
|XFO-6322||Cannot remove response tracking entry||Details|
The following instructions describe how to use the installer to patch an existing xMatters 5.x deployment and upgrade it to version 5.1 patch 007. For information about installing a new xMatters 5.x deployment, see the xMatters 5.x Documentation.
Apply this patch to all xMatters application nodes, notification nodes and web servers (and any Data Sync installations, if applicable).
Installer files included with this release:
For use on:
Note that this installer file also requires a 32-bit JRE.
For use only on supported Microsoft Windows systems that are using a 64-bit JRE, and which will not require PSTN/Dialogic support.
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.)
Warning: Configuration file changes
When applying an xMatters patch, any changes you have made to the parameters in any of the configuration files may not be retained. The patch may overwrite modifications to some or all of the following files:
Any changes you may have made according to the information in the xMatters installation and administration guide will need to be reapplied.
Warning: Database changes
If you are upgrading from an older version, be aware that this patch includes database changes that may impact your replication mechanism (consult with your database administrator for further details).
These patches may also include updates to the database audit tables that can take an extreme amount of time to adjust when applying the patch. It is highly recommended that you clear the audit data (i.e., archive all your runtime data by running the Clear Runtime/History job in the web user interface) before installing any xMatters patch to reduce the amount of time required for the patch to process the data.
Note that introducing new indexes to a database may cause an increase in the required storage space. This is a normal consequence of using indexes, and assists performance of the overall system.
Before installing this patch:
- Shut down or stop all node processes.
- Shut down or stop all web server processes.
- Back up the xMatters Database.
- If you have made changes to the Template Company scripts, back up your script packages (see note about database changes, above.)
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 (referred to as <xMHOME>).
- On Linux, the default install directory is:
- On Windows, the default install directory is:
C:\Program Files (x86)\xMatters\
2. Save the xMatters installer file to your local machine.
3. Open a command prompt and navigate to the directory containing the installer file.
4. Do one of the following:
- To run the installer in GUI mode, run the following command (replace <version> with i586 or x64, depending on your version of the installer):
java -jar xmatters-installer-<version>-5.1.7.jar
- To run the installer in console mode, run the following command (replace <version> with i586 or x64, depending on your version of the installer):
java -jar xmatters-installer-<version>-5.1.7.jar -console
5. The installer displays a welcome message; press Enter (console installation) or click Next (GUI installation) to continue.
6. Specify the location on the machine where the xMatters components are installed, and then press Enter or click Next to continue.
- The installer will inspect the current installation and determine whether the patch needs to be applied.
7. Next, the installer offers the following options:
- Back up the installation folder: Selecting this option will create a backup copy of the existing xMatters installation directory (by default, saved to /opt/xmatters.bak.1/)
- Remove old application log files and temporary folder: Selecting this option will remove the temporary folders and log files from the existing installation's web server cache.
8. Select the options you want, and then press Enter or click Next to continue.
9. The installer then checks the disk to determine whether there is enough space to continue with the installation; press Enter or click Next to continue.
10. Next, the installer displays a summary of your selected options and the components included in the patch process; press Enter or click Next to continue.
- The installer will then patch your installation. When it is complete, it displays a summary page, and gives you an option to generate an automatic installation script so you can patch other components using the same options. (For more information about the automatic installation script, see the xMatters installation and administration guide.)
After installing this patch:
- Start the Node processes.
- Start 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.
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.
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 (apod/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 (apod/oracle/02.xml)
2009-01-21 22:07:22,847 [AlarmPoint Node-main] WARN - - Package 8 of 8 (apod/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.1
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.
Notification Summary report not calculating responses correctly
A customer reported an issue with the Notifications Summary report not accurately displaying all of the responses received for an event. The issue usually occurred when a user responded to a notification on a device via a different response path (such as using the web user interface instead of sending an email response). This was due to the way the system recorded responses from different response methods. This issue has been addressed, and the statistics on the Notifications Summary report should now match other reports for the same event.
Advanced Messaging scenarios not using Priority value as set in Handling section
A customer reported an issue with their Advanced Messaging scenarios where the event priority set in the Handling section would not be reflected on the actual notification. For example, some scenarios launched as LOW priority would be marked as MEDIUM priority in the Event Properties report. This issue has been addressed.
Group synchronization over SOAP returning UNKNOWN_APPLICATION_ERROR
An issue was reported with the xMatters SOAP web services where attempting to add a group (using an integration's data synchronization utility) would fail and return an UNKNOWN_APPLICATION_ERROR warning. The operation was failing because the group's Description field contained too many characters, but the default error message did not indicate the nature of the problem. The SOAP web services have been updated with a new error message that accurately identifies the mistake.
Deleted subscriber causing Archive/Purge job to fail
An issue was reported with the archiving and purging process when some deleted users were not being properly deleted (and causing the archive/purge job to fail) if they had created subscriptions. The system has been updated to remove all of a user's associated subscriptions when they are deleted, and the archive and purging process should no longer be interrupted by this issue.
Component Status Summary report shows integration services as links
An issue was reported with the Component Status Summary report where the names of integration services were rendered as hyperlinks. This was due to an incorrect permission assigned to the Super Administrator role; this issue has been addressed.
Integration agent stops working if non-printing control characters included in APXML content
As issue was reported where content that included non-printing control characters submitted to the integration agent would cause the APXML exchange to enter a feedback loop. The system has been updated to return an error when non-printing control characters are encountered that allows the integration agent to log the error and discard the message after the normal number of retries.
Cannot re-install an existing node
An issue was reported when attempting to re-install a previously existing node where the installer would not present the option to use an existing node, but prompt the user to provide a new node name and other details. The installer has been updated to provide users with the option of creating a new node or re-using an existing one.
Attempting to save a SIP device engine causes stack trace
An issue was reported with the SIP device engine page where attempting to save the device engine details when one or more required fields were not specified would cause a stack trace instead of an error message. This issue has been addressed.
FindWhoIsOnDuty SOAP web service fails when the date range contains a holiday shift
An issue was reported with the FindWhoIsOnDuty web service method where the request would fail if the date range included a holiday shift with no end date set. This was due to the way the method attempted to calculate the end of the shift for the Who's On Duty report; this issue has been addressed.
Cannot remove response tracking entry
An issue was reported with the response tracking functionality on event domains where attempting to remove a response tracking entry would result in a stack trace. This issue has been addressed.
Appendix 2: Known Issues
xMatters 5.0 patch 007 included an upgrade to the included Java version from Java 6 to Java 7. The Automated-Speech-Recognition (ASR) functionality is currently not compatible with Java 7. If an xMatters deployment includes scripts that use ASR, the node will crash. The following are examples of script calls that use ASR:
(xMatters Reference: XFO-3472)
Some flavors of Linux with SELinux enabled will not run Java 7. After installing xMatters and trying to start the node, users may encounter an issue where Java fails to start, and an error similar to the following appears in log files:
Error: dl failure on line 864
Error: failed /opt/xmatters/staging/jre/lib/i386/server/libjvm.so, because /opt/xmatters/staging/jre/lib/i386/server/libjvm.so:
cannot restore segment prot after reloc: Permission denied
This is due to an issue with SELinux identifying the Java 7 libraries as a possible security threat. To resolve this issue, you must edit the /etc/selinux/config file and disable SELlinux.
(xMatters Reference: DTN-3158)
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)
The xMatters Installer does not remove the Windows Services (i.e., the xMatters Webserver and the xMatters Node) when uninstalling. Instructions on how to manually remove the services have been added to the xMatters installation and administration guide, or are available on the Microsoft Windows Support site.
(xMatters Reference: XFO-2013, DTN-2960)
- Update SYNC_NOTIFICATIONS_SUMMARY_TRG for ARCH-3256