============================ xMatters Patch Release Notes ============================ Patch version: PATCH-410-005 Build: 310 Revision: 42796 Document revision date: January 27, 2011 Copyright xMatters, inc. 1994-2011 --------------------- 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 at www.xmatters.com. 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 the article "Common questions about rebranding from AlarmPoint to xMatters", available on the xMatters (user) community web site. ------- SUMMARY ------- This document covers the following: * Versions of xMatters this patch affects * Behavior the issues display * Fixes included in this patch * How to install this patch (including any prerequisites) * Files included in this patch package * Issue status (i.e., which version of xMatters includes this patch) NOTE: This document is subject to change after the initial release of this patch. The latest version of this document is available in the "Patches/Misc. Downloads" section of the xMatters (user) community web site (https://connect.xmatters.com/). -------------------------- AFFECTED xMatters VERSIONS -------------------------- This is a cumulative patch for version 4.1.0 issues, and should be applied to all xMatters Application Nodes, Notification Nodes and Web Servers (and to the DataSync Server, if applicable). --------------------- PATCH FILE MANAGEMENT --------------------- Applying this patch does not automatically overwrite existing properties files (e.g., log4j.xml, custom.properties). This is to prevent inadvertent overwriting of client modified properties. Instead, this patch includes several files with a ".patch" extension (e.g., log4j.xml.patch, custom.properties.patch). These .patch files represent the latest versions of these files. It is recommended that you compare the .patch files against your deployment's files to determine the specific needs of your environment. WARNINGS ******** - 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 the article titled "Integration stops working after applying AlarmPoint patch" on the xMatters (user) community web site.) 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) - Before applying this patch, you must upgrade to xMatters 4.1.0. After upgrading, it is recommended that you apply the latest xMatters 4.1 patch, UNLESS your upgrade path is not compatible with the latest patch. To determine whether your upgrade path is compatible with the latest patch, see the article titled "AlarmPoint Patch Compatibility Matrix" on the xMatters (user) community web site. REMINDER: The xMatters Support Policy was updated in February 2009. You can access the updated Technical Support Policy document on the xMatters (user) community web site (https://connect.xmatters.com/support). After logging in, click the Support tab, and then download the document from the menu on the left of the page. This cumulative patch provides fixes for all entries under "ISSUES FIXED IN THIS PATCH RELEASE". ------------------------------------ FEATURES ADDED IN THIS PATCH RELEASE ------------------------------------ Features added in xMatters 410 patch 5: *************************************** 13. New Node Network Statistics Report assists node troubleshooting. The new Node Network Statistics Report provides the ability to assess and troubleshoot the performance of node communication. The report returns data regarding the number of network interruptions, application layer latency between nodes, and whether the network connection was symmetric for a specified period. (xMatters Reference: PRE-4708) 12. Added new One-Time Coverage Team "Assign Existing Team" option. Prior to applying this patch, Modify Team options on the One-Time Coverage page included Reuse Existing Team and Modify Existing Team. This patch adds a new option called "Assign Existing Team" that allows Users to select a different existing Team to assign to the Coverage (Reuse Existing Team assigns the existing Team members and escalation schedule to the new shift). (xMatters Reference: PRE-3930) 11. xMatters (alarmpoint) 4.1 certified for Avaya CM 6 and Session Manager. xMatters (alarmpoint) engine 4.1 has been certified by Avaya as compliant with Avaya Communication Manager 6 (scheduled for June 2011 release) and Avaya Session Manager (the replacement for Avaya SIP Enablement Services (SES)). (xMatters Reference: PRE-3747, PRE-4551) 10. Additional roleName argument added to FindPersons web service. A new search parameter named "roleName" has been added to the FindPersons web service call to provide the ability to limit the results to Users with a specific xMatters (alarmpoint) Role. NOTE: Before you can use this new parameter, you must first recompile an existing Java client (existing Java Clients that are not recompiled will continue to function as before). (xMatters Reference: PRE-4704) 9. Support added for Simple SMS Replies. You can now configure xMatters to accept simple SMS responses to notifications. These simple replies require Users to enter only a single digit as a response to a notification, rather than entering a phrase that includes the notification key. (xMatters Reference: PRE-3761) 8. Email response handling improved to respect whitespace and reduce errors. Email response handling has been improved so that response parsing respects whitespace and reduces response errors. For details, see the article "How can I reduce the number of errors caused by User email responses?" on the xMatters Support web site. (xMatters Reference: PRE-4109) 7. New FindActiveUserNotifications web service added. The new FindActiveUserNotifications web service returns a list of all active notifications for the specified User. Results can be further limited to a specific Event Domain or incident ID. (xMatters Reference: PRE-3931) 6. Active License file can now be exported to Excel for troubleshooting. The Active Licence file page now includes an Export link that allows a Super Administrator to export the license file to Excel. The file can then be sent to xMatters Support for assistance troubleshooting licensing issues. (xMatters Reference: PRE-4502) 5. New Replay Event feature allows existing Events to be launched again. The new Replay Event link on the Event Summary Report allows existing Events to be launched Event again. This feature aids in troubleshooting notifications or diagnosing delivery problems. (xMatters Reference: PRE-3746) Features added in xMatters 410 patch 4: *************************************** 4. Support added for Long SMS via SMPP. Long SMS support via SMPP allows SMS messages longer than 160 characters to be sent to an SMS-enabled device. (xMatters Reference: PRE-3158) 3. Support added for simple SMS replies via SMPP. Simple SMS support via SMPP allows notification recipients to respond with simple numeric responses, which is more convenient and less error-prone than having to type out longer text strings on mobile devices. For example, instead of typing out "Acknowledge", the recipient is presented with a choice such as "Reply 1 to Acknowledge". (xMatters Reference: PRE-3761) Features added in xMatters 410 patch 3: *************************************** 2. New Holiday Behavior setting provides greater Holiday Coverage flexibility. The new Holiday Behavior setting on the Schedule Details page allows you to specify whether and how holidays affect existing Coverages. For example, in some cases, you may choose to have a Coverage that would normally span midnight to end at midnight when there is a holiday the next day. In other cases, you may want the Coverage to span midnight. Similarly, Coverages that start during the holiday can also be controlled by this setting, allowing you to specify whether and for what duration the Coverage operates during a holiday. (xMatters Reference: PRE-1970) 1. LDAP Servers configuration page now allows creation of multiple servers. The LDAP Servers configuration page now provides for the creation of multiple LDAP servers (i.e., versus the previous behavior of multiple templates on a single server). This allows administrators to configure separate LDAP servers that use simple bind, anonymous bind, or authenticated search bind, and also provides the ability to authenticate Users across all LDAP configurations. (xMatters Reference: PRE-1355) ---------------------------------- ISSUES FIXED IN THIS PATCH RELEASE ---------------------------------- Issues fixed in xMatters 410 patch 5: ************************************* 136. xMatters mobile access (formerly Mobile Gateway) component does not work with WebSphere 7. (xMatters Reference: PRE-1461) 135. "Only show supervised groups" check box does not work as expected. The Find Groups page includes a checkbox labeled "Only show supervised groups". When checked, the search results should not include any Groups for which the logged in User is not a Supervisor; however, the search results still include non-supervised Groups. (xMatters Reference: PRE-3016) 134. Memory leak when reconnecting nodes eventually causes OutOfMemoryError. In some cases, a node can experience an OutOfMemory error after a number of connection failures between itself and another node. (xMatters Reference: PRE-4306) 133. Companies cannot be deleted from the system even when not in use. The following message is displayed when an attempt is made to delete a Company from the system: "Could not delete Company . Deleting is not permitted because it is currently in use." This occurs even when the Company is not currently in use. (xMatters Reference: PRE-3070) 132. Misconfigured node results in duplicated notifications and node shut down. When a misconfigured node loses bidirectional communication with other nodes, the misconfigured node shuts down and generates errors that cause duplicate notifications to be sent out. (xMatters Reference: PRE-4499) 131. Changes to Custom Holidays are not reflected on the Site Holidays page. (xMatters Reference: PRE-136) 130. Setting setDeviceFilter to exclude all Devices has opposite effect. Using setDeviceFilter(deviceType,boolean) in an Action Script to exclude all Devices actually results in all Devices receiving notifications. (xMatters Reference: PRE-200) 129. New phone script method isLanguageSupported added. Prior to applying this patch, the voice recordings script includes a hard-coded list of available languages that is presented even if they are not all supported by the Company. To help make these scripts more generic and maintainable, a new phone script method named isLanguageSupported has been added. This method queries whether a specified language is supported in the Company. (xMatters Reference: PRE-207) 128. Group escalation continues even after Group Fill Count is met. Scenarios with multiple recipients including a Group do not terminate when the Group Fill count is met. Instead, escalations continue within the Group if the Additional Fill Count requires another recipient to respond affirmatively. (xMatters Reference: PRE-219) 127. Cannot delete Company Admins who received (and replied to) notifications. (xMatters Reference: PRE-2097) 126. Send a Quick Message panel stack trace when target name >100 characters. The Send a Quick Message panel displays a stack trace when any target name in the Recently Used List is longer than 100 characters. In most cases, validation prevents any target name (User, Group, etc.) from exceeding 100 characters. However, it is possible to exceed the 100-character validation limit when the target name includes an escape character (e.g., "&") followed by characters that denote multiple characters. When such a target is listed in the Recently Used List, it causes a stack trace. (xMatters Reference: PRE-2098) 125. Removing Web Service User function causes all web service requests to fail. Removing the out-of-the-box Web Service User Function from the system causes all web service requests to fail with an authentication error. This function should be hidden so that is not inadvertently removed (this Function is intended for internal xMatters use only). (xMatters Reference: PRE-2427) 124. Nodes in different deployments connect resulting in unexpected behavior. In some cases, due to a configuration error, nodes in different xMatters (alarmpoint) engine deployments can connect, resulting in unexpected behavior. In particular, this situation can arise when migrating databases between non- production and production environments. To resolve this issue, authentication has been added to the node (authentication is disabled by default). The messageBusTarget.authenticating property in the node default.properties file controls this behavior. If this setting's value is "true", the node includes authentication details within each message, and ensures that other nodes with which it communicates provide the same authentication details in return. NOTE: the values used for authentication are drawn from the database configuration details, and must be exactly the same for all nodes in the network. (The JDBC_URL and JDBC_USERNAME properties from the common.properties files are used to ensure that all nodes are configured using the same database. Because there is no third-party arbiter available for authentication, these values must not only point to the same database, they must be EXACTLY the same. Deployed nodes that reference the same database, but use a different JDBC_URL or JDBC_USERNAME will not authenticate correctly). (xMatters Reference: PRE-2610) 123. Archiving job may enter infinite loop when many old events are active. The Archive Data Schedule Job (located at Admin > Schedule Jobs in the web user interface) can enter an infinite loop when many old events are still active at archive time. In such cases, the archiving job never finishes. (xMatters Reference: PRE-3647) 122. DataSync error when importing Sites that include Clusters. When attempting to import Sites that include Clusters using the Data Synchronization tool, the import fails and an error similar to the following is written to the DataSync log: "Could not find property: primaryCluster for class: class com.invoqsystems.apex.model.location.Site :: com.invoqsystems.apex.model. location.Site.setPrimaryCluster(com.invoqsystems.apex.model.location.Cluster)". (xMatters Reference: PRE-3672) 121. Access to static content on the web server should be limited. Currently, all files (e.g., flow scripts, forms, JSPs, XLSs, etc.) in the webapps/cocoon/alarmpoint directory are served by Jetty's ResourceHandler as static content. This means that users can access these files through a browser without authentication or authorization, which represents a security risk. Accessible static content should be limited to files that are not a security risk (e.g., CSS files, images, help files, etc.). (xMatters Reference: PRE-3984) 120. Protocol Provider Maximum PIN length field increased to 20 characters. (xMatters Reference: PRE-4006) 119. Chronological Exhaustive Report displays data in non-chronological order. (xMatters Reference: PRE-4007) 118. Defining SoapListPredicateParameter list predicate values more intuitive. After installing this patch, defining SoapListPredicateParameter list predicate values is more intuitive. NOTE: this may break backwards compatibility for existing SoapListPredicateParameter deployments; check the latest version of the xMatters Online Developer's Guide. (xMatters Reference: PRE-4027) 117. Resources page Proxy Server Port field should allow values <1024. (xMatters Reference: PRE-4028) 116. SMTP Protocol Provider Domain Name field should allow 100 characters. (xMatters Reference: PRE-4056) 115. JSP files do not compile in WebSphere, causing any attempted JSP page access (e.g., sign-on page, response hyperlinks, etc.) to fail. (xMatters Reference: PRE-4059) 114. Database update does not work because components acquired concurrently. The database patch update fails because multiple xMatters (alarmpoint) engine components (e.g., node, web server) acquire the mutex at the same time. (xMatters Reference: PRE-4342) 113. Subscription matching query must be redesigned to handle more event tokens. Currently, there is a limit on the number of event token values that can be part of the SQL query for Subscription matching. This query should be redesigned so that the query size is reduced, resulting in a greater number of event token values that can be handled. (xMatters Reference: PRE-4364) 112. Excel export of incomplete Group causes stack trace on Monthly View page. Groups that do not include any Teams should not be exportable to Excel. However, on the Monthly View page for a Group that does not have a Team, the Export Excel Document button is still available and results in a stack trace when clicked. To resolve this issue, every Group Coverage should be checked to ensure it has at least one Team. (xMatters Reference: PRE-4434) 111. Custom Messaging panel max character setting logic is flawed. The developer of a Custom Messaging panel can specify the maximum allowable characters for a message. However, there are two problems with the current logic: when max characters is set <1000, the system still allows up to 1000 characters (despite the warning message displayed); and, if max characters is set >1000, the system still truncates messages at 1000 characters (without a warning). This should be changed such that max character settings are respected, up to a maximum of 4000 characters. (xMatters Reference: PRE-4434) 110. Additional logging required when Device Engine 'ignores' responses. When xMatters (alarmpoint) engine receives an invalid response from a Device (e.g., due to improper or incomplete formatting), it ignores the response but does not log the reason for this. Additional logging is required to record why the response was invalid and thus ignored. (xMatters Reference: PRE-4485) 109. SMPP Device Engine tracks status reporting even when not set to do so. The SMPP Device Engine has a setting named Support Status Report that is meant to track status reports sent by the Protocol Provider. However, even when this setting is not selected, the system tracks the status reports, which can cause performance issues. The underlying logic should be modified to ensure that such tracking does not take place unless specified. (xMatters Reference: PRE-4497) 108. On the Component Status Summary page, the expand ("+") button does not work for Integration Agent details. (xMatters Reference: PRE-4508) 107. SMPP status (Device delivery/error) is not displayed in Exhaustive Report. (xMatters Reference: PRE-4477) 106. ListGroupMembers web service call does not provide all Group members. If its ignoreCoverages flag is set to true, the ListGroupMembers web service actually returns Group members that are present on any Coverage. This should be corrected such that setting ignoreCoverages to true processes all Group Teams (i.e., not just those that are part of a Coverage). (xMatters Reference: PRE-3776) 105. Monthly View shows incorrect day or displays incorrect day's details. In rare cases, selecting a given day in the Monthly View calendar incorrectly displays details for the following day (e.g., clicking the 11th displays details for the 12th). The default display for 'today' has the opposite issue: if today is the 15th, details for today are shown, but the default shaded day on the calendar grip is for the 16th (tomorrow). While this has no functional impact, it can cause User confusion. (xMatters Reference: PRE-3775) Issues fixed in xMatters 410 patch 4: ************************************* 104. Callout for Voice Recordings fails with "Person does not exist" exception. When attempting to make a Voice Recording, the callout fails and an entry similar to the following is written to the node log: "AlarmPointUserDoesNotExistException: Person does not exist." (xMatters Reference: PRE-3692) 103. New script methods added to enable/disable PSTN and SIP call analysis. Two new script methods, enableCallAnalysis() and disableCallAnalysis() have been added to provide the ability to enable and disable call analysis in PTSN and SIP. (By default, call analysis is enabled.) (xMatters Reference: PRE-3938) 102. Health Monitor leaks database connections without any limit. Currently, the Health Monitor opens but does not explicitly close database tester connections (another process is relied upon to do so, but it may not run frequently enough in some cases). The Health Monitor should explicitly close such connections. (xMatters Reference: PRE-3910) 101. Threading issue can cause exception when starting SMPP Device Engine. In rare cases, starting the SMPP Device Engine produces an exception similar to the following: 2010-07-25 13:06:45,325 [AlarmPoint Node-main] DEBUG - - Restart worker pool 2010-07-25 13:06:45,325 [pool-2-thread-1] WARN - - Exception in thread "pool-2-thread-1" . . . [Truncated] This is caused by a threading problem. (xMatters Reference: PRE-3673) 100. Data synchronization does not work for Users authenticating with LDAP. After applying xMatters (alarmpoint) engine version 4.0 patch 11 or version 4.1 patch 3, data synchronization does not work for Users authenticating with LDAP. (xMatters Reference: PRE-3663) 99. Holiday Duration period defaults to 24 minutes rather than 24 hours. (xMatters Reference: PRE-3655) 98. Changing default Company name causes Mobile Gateway login to fail. After modifying the name of the Default Company, Mobile Gateway login fails because the Default Company name is hardcoded. (Web login works correctly.) (xMatters Reference: PRE-3607) 97. Added ability to configure TOS for SIP. After applying this patch, you can configure TOS (Type of Service) settings for SIP. For details, see the article "Configuring TOS for SIP" on the xMatters (user) community web site. (xMatters Reference: PRE-3135, DOC-2424) 96. "# not yet notified" varies for the same event after it has terminated. On the Event Summary Report, the "# not yet notified" value varies for the same event even after it has terminated. (xMatters Reference: PRE-3686) 95. DataSync Team import fails due to name length; no error message provided. When an attempt to import a Team using the Data Synchronization tool fails because the Team name exceeds the maximum allowed length, no reason for the failure is provided in the log. (xMatters Reference: PRE-3023) 94. Resources error logged when APAgent cannot connect to AlarmPoint. In some cases after running for an extended period, APAgent cannot connect to AlarmPoint and an error similar to the following is logged: "WARN - - Exception: Not enough resources to run the ECS processor. Client communication pool requires an even number of resources". This problem is caused by a thread pool issue that results in an 'orphaned' slave thread. (xMatters Reference: PRE-3004) 93. QueryGroup web service call response contains duplicated elements. (xMatters Reference: PRE-2549) 92. Temporary Replacement page is missing User's name in title. The Temporary Replacement page does not include the User's name in its title; for example, the page title reads "Temporary Replacement Schedule for" rather than "Temporary Replacement Schedule for Bob Smith". (xMatters Reference: PRE-2209) 91. Changes to Registry.cfg are not propagated to AG trunk. Modifications made to the Registry.cfg file are not properly propagated to the VoiceObject.configure file for AG trunk. (xMatters Reference: PRE-2129) 90. Added support for configuring email encode on Lotus Notes Device Engines. (xMatters Reference: PRE-2075) 89. Added ability to specify which HREFs are excluded from URL encoding. Some customers want to be able to have on their custom pages, and to be able to exclude such tags from being URL-encoded. For details, see the article "Specifying include/exclude patterns for external URLs" on the xMatters (user) community web site. (xMatters Reference: PRE-223, PRE-348) 88. Component Status Report shows last IA heartbeat with minute resolution. Although Integration Agent heartbeats occur (by default) every 10 seconds, the Component Status Report provides only 'minutely' resolution for the heartbeats. This should be changed to show heartbeat intervals to the second. (xMatters Reference: PRE-206) 87. Field added for setting callin script used by SIP DE for each Company A new field was added to the Company Details page that allows administrators to specify the callin script used by the SIP Device Engine for each Company. Previously, all Companies in a deployment were required to use the same callin script for SIP responses. (xMatters Reference: PRE-187) 86. Injecting incident ID longer than 250 characters causes stack trace. Injecting an event with an incident ID longer than 250 characters results in a stack trace. (xMatters Reference: PRE-179) 85. GSM Device Engine stack traces when characters in alphabet extension table. The GSM Device Engine stack traces when GSM messages contain characters in the GSM 7-bit default alphabet extension table. (xMatters Reference: PRE-177) 84. DataSync does not check for invalid values of list type Custom Fields. During processing, the Data Synchronization tool does not check whether a list type Custom Field includes a value that has not been specified for the list. (xMatters Reference: PRE-146) 83. Deleting Group involved in active notification process causes stack trace. (xMatters Reference: PRE-142) 82. Max field on Custom Field Details page allows values higher than database. On the Custom Field Details page, the Max field allows more than 100 characters (i.e., greater than the 100 characters allowed by the related database table). If the Max field is set to 101 and a Custom Field value is later specified that is 101 or more characters, a stack trace results. (xMatters Reference: PRE-134) 81. Patch updates do not work with special JDBC connection URLs. Changing the common.properties file to use a special JDBC URL will cause patch updates to fail. (xMatters Reference: PRE-74) 80. Temporary MG license causes errors after upgrade to permanent license. After installing AlarmPoint Express (which includes a temporary Mobile Gateway license), several Users are given Mobile Gateway access. Later, a permanent AlarmPoint Enterprise license (which does not include the Mobile Gateway license) is applied. Attempting to add the Mobile Gateway access Users to Teams, etc., results in errors stating that the maximum number of Mobile Gateway access Users has been exceeded. In such circumstances, if the new licensing does not include the Mobile Gateway, all Users should automatically be set as non- Mobile Gateway access Users. (xMatters Reference: PRE-32) Issues fixed in xMatters 410 patch 3: ************************************* 79. Stacktrace occurs when deleting Recording on Initiate Scenario page. On a DB2 database deployment, a stacktrace occurs when attempting to delete a Recording on the Initiate Scenario page. (xMatters Reference: PRE-41) 78. DataSync export fails to process Team Members on DB2. On DB2, a DataSync export will fail to process Team Members and an error message similar to the following will be generated: com.invoqsystems.apex.datasynchronizer.exceptions. AlarmPointErrorLimitExceededException: Too many errors generated. Processing halted. Processing does not actually stop (it finishes successfully), but DS_TEAM_MEMBERSHIPS is empty. (xMatters Reference: PRE-72) 77. Some Permissions are missing from the list of Available Permissions. Some Permissions do not appear in the Available Permissions list in the web user interface. This means that if you remove some permissions (e.g., ability.act.Developer, ability.act.SupportUser) from some functions (e.g., Developer, Support User), it is not possible to add them back to the function because they do not appear in the Available Permissions list. (xMatters Reference: PRE-133) 76. Incorrect Integration Service capitalization causes all IAs to fail. An Integration Agent that registers an Integration Service with incorrect capitalization (i.e., the wrong case) causes all other Integration Agents to fail indefinitely. (xMatters Reference: PRE-135) 75. Health Monitor hangs when attempting to create event for database failure. When the Health Monitor detects a database failure, it attempts to create a new event and post it (i.e., if the notification target is configured). However, creating a new event requires database access. If no database failover has been configured, the Health Monitor will hang because it is waiting for database access; and, if database failover is configured, the Health Monitor does not try to gain access to the failover database. (xMatters Reference: PRE-140) 74. Outlook may not parse new line characters in email subject line. When sending notifications through the SMTP Device Engine, an email subject line that includes new line characters may not be parsed properly by Microsoft OutLook. (xMatters Reference: PRE-143) 73. Port number should be logged when TAP or any serial port connection fails. When multiple serial ports are configured and the sending of an initial string fails do to a timeout, it is currently not possible to tell which port has failed. The port number should be logged when port initialization fails. (xMatters Reference: PRE-149) 72. Temporary Replacement validation incorrectly allows replacement overlap. It is possible to create a Temporary Replacement that overlaps an existing replacement, causing the existing replacement not to be honored. The validation should be changed so that the overlapping of Temporary Replacements is not allowed. (xMatters Reference: PRE-147) 71. Company Administrator can view data for another Company via report. Under a multi-tenancy license, a Company Administrator can select and view data for another Company via the Notification Throughput Details Report. Company Administrators should be able to view data for their own Company only. (xMatters Reference: PRE-151) 70. Patch 400-006 causes DS_DEVICE_TIMEFRAMES reorg pending state issue on DB2. After applying xMatters 4.0 patch 6 (400-006) and executing the patch database update scripts on a DB2 database, the DS_DEVICE_TIMEFRAMES table goes into the reorg pending state. (xMatters Reference: PRE-157) 69. SMTP DE peformance issues in POP/IMAP accounts with many messages. Using an SMTP Device Engine with a POP/IMAP email account that has a large number of email messages can affect the overall performance and processing of notifications for the associated notification server. This is because the Device Engine attempts to read all messages at once, causing increased memory usage that affects processing times. (xMatters Reference: PRE-168) 68. SubmitAPXML can fail with an UNKNOWN_APPLICATION_ERROR response. In some cases, the SubmitAPXML web service can fail unexpectedly with an UNKNOWN_APPLICATION_ERROR response. When SubmitAPXML is used by an Integration Agent, this can result in repeated submissions, potentially flooding the system with the same event. (xMatters Reference: PRE-1702) 67. DataSync does not support adding phone login/password to an existing User. After a new User has been created without a phone login/password, the User cannot then be updated via Data Synchronization to include a phone login/password. DataSync should check whether the existing User has phone credentials; if not, the phone password should be added (i.e., without disabling it). (xMatters Reference: PRE-2041) 66. Coverages not displayed correctly when Holidays associated with Group. Group Coverages are not displayed correctly when Holidays are associated with the Group. If Holidays are excluded from the coverage a one hour segment may be remaining. If Holidays are included on the coverage a second shift may appear that starts and ends one hour later. (xMatters Reference: PRE-2093) 65. "call" string causes @event::terminate() script method to stack trace. Script method @event::terminate() stack traces when the target name of any recipient has the word "call" in it. (xMatters Reference: PRE-2095) 64. Multiple messages cannot be sent during a single SNPP connection. Currently, the SNPP Device Engine uses one connection to send one message. When the engine sends the next message in the same batch, it must reconnect to the SNPP server. This causes problems when the job contains many messages (in cases of lengthy connection times, notifications will take longer to send and may also result in duplicate notifications because they cannot be processed quickly enough). (xMatters Reference: PRE-2126) 63. Log information is lost (overwritten) when Device Engines are stopped. (xMatters Reference: PRE-2127) 62. Unhandled exception (or silence) when TTS engine encounters "% f". When a message contains a sequence of characters that includes "% f" to be spoken through a TTS engine, an unhandled exception (or silence) can result. A new installer for the Phone runtime binaries that provide the CT ADE libraries has been created to resolve this issue. This new installer is called AlarmPointPhoneRuntime.exe and can be found in the patch under the tools/phone-runtime directory. For more information, refer to the article "Deploying the new PSTN installer included with Patches 400-011 and 410-003" available on the xMatters (user) community web site (https://connect.xmatters.com/). (xMatters Reference: PRE-2173) 61. TTS engine does not play audio for Asian languages. The TTS engine does not play audio for Asian languages (Chinese, Japanese, Korean). (xMatters Reference: PRE-2218) 60. Web Service Audit Report unstable due to Integration Agent registrations. The Web Service audit report becomes unusable when using integrations that require Integration Agents to be registered in xMatters. (xMatters Reference: PRE-2481) 59. SSO requests do not include query string. In SSO configurations, URL requests requiring some query data may not display the correct page results. This means that Users must enter the data in the web user interface and resubmit the page to obtain results. (xMatters Reference: PRE-2491) 58. Group Details page stack traces when User logged in via SSO. When a User has logged on via SSO, the Group Details page displays a stacktrace when the Group includes the logged-in User as a member. (xMatters Reference: PRE-2510) 57. SUCP Device Engine does not support reply messages from the User's device. The SUCP Device Engine does not work with service providers that send reply messages from the User's device. This can result in notification retries or failures in xMatters. Support should be added to handle SUCP reply messages. (xMatters Reference: PRE-2685) Issues fixed in xMatters 410 patch 2: ************************************* 56. Memory leak causes OutOfMemory error leading to node & web server failure. A third-party library issue causes memory leaks that may lead to OutOfMemory errors and the eventual failure of the related node or web server. (xMatters Reference: PRE-2103) 55. Device Engine concurrency limited by message processing thread pool size. Even if a Device Engine's WebUI-configured Concurrent Threads limit (Line Appearances for SIP/PSTN) exceeds its Spring-configured message processing thread pool size, the Device Engine will not be able to concurrently process more notifications than defined in its Spring configuration. (Note that this issue was listed as a Known Issue in the AlarmPoint 4.1 release notes.) (xMatters Reference: PRE-1862) 54. Stack trace occurs when editing text predicates for a Scenario. After a Scenario including text predicates is successfully created, later adding another text predicate causes a stack trace. (xMatters Reference: PRE-2013) 53. Web server logs are truncated after restart, hindering troubleshooting. If a web server is restarted (e.g., due to hanging, performance issues, etc.), the logs are truncated, causing diagnostic information to be lost and hindering the troubleshooting process. (xMatters Reference: PRE-1923) 52. Unhandled exception in web service can display internal server page. Providing a bad URL (e.g., http://localhost:8888/api/services/ AlarmPointWebService?wsdl=') when using web services can cause the internal server page to be displayed. This can be a potential security issue, as the server page includes a link (i.e., "Home") to the admin servlet. The displayed error should be modified so that it does not display the Home link. (xMatters Reference: PRE-1791) 51. Fields on the Company Quotas page should be limited to nine digits. On the Company Quotas page, specifying the current allowable number of digits in any field causes a stack trace. Fields on this page should be limited to nine digits. (xMatters Reference: PRE-1775) 50. xMatters does not receive any DTMF data from the SIP server. In some cases, xMatters does not receive any DTMF data from the SIP server. This means that Users cannot log in to their accounts even when the correct password is input from a Phone Device. This issue is caused by SIP servers that do not follow RFC2833 to send DTMF data to xMatters. If the SDP (Session Description Protocol) does not contain attributes defined in RFC2833, an ERROR message should be logged. (xMatters Reference: PRE-1454) 49. IA appears as FAILED after first heartbeat when it should be ACTIVE. The Integration Agent appears as FAILED in the Component Status Report after its first successful heartbeat; it should instead be marked as ACTIVE. (Note that after the second successful heartbeat the agent is correctly marked as ACTIVE.) In addition to the potential for confusion, this results in the return of FAILED services to the Integration Agent, which causes integration-to-integration requests using the ServiceAPI to fail (i.e., since no active service will be found). (xMatters Reference: PRE-81) 48. Total node shutdown timeout should be configurable. Once the node manager receives a shutdown command, it tries to shut down all components in an orderly manner. However, if the manager cannot shut down a component after five minutes, the node will be terminated regardless of the issue. Currently, this timeout should be configurable. (NOTE: the custom.properties file now includes the nodeManager.shutdownTimeout setting, which has a default value of 300 seconds). (xMatters Reference: PRE-79) 47. IA that heartbeats less frequently than 30 seconds appears as FAILED. An Integration Agent that registers less frequently than every 30 seconds always appears as FAILED in the Component Status Report. Additionally, after 30 seconds, the FAILED agent's services appear as FAILED. However, from the perspective of the Integration Agent, the heartbeats all appear to be succeeding. (xMatters Reference: PRE-73) 46. Health Monitor message generated during normal processing. In some cases, the Health Monitor generates messages for normal operations on the SIP Device Engine. The list of conditions that trigger these messages should be modified to include only those events that require an alert to be sent. (xMatters Reference: PRE-71) 45. Clicking Perform Selected Actions when no Alert selected performs action. In the My Alerts area of a User's Home Page (or on their Active Alerts page), clicking Perform Selected Actions results in a "Your response has been posted" message, even when no Alert has been selected in the table. (xMatters Reference: PRE-66) 44. Support User should not be able to create or delete Users or Groups. The Support User Role currently includes the ability to create and delete Groups; this Role should not have these permissions. (xMatters Reference: PRE-53) 43. No error is displayed when bad data is entered via web Device Validation. If bad data is entered when validating a Device via the web user interface, no error message is displayed. If the User has not seen what a successful validation looks like, this could lead the User to believe that the validation was successful. (xMatters Reference: PRE-48) 42. Group Supervisors can view and details for Groups they do not supervise. From the Who Is On Duty Report, Group Supervisors can view and edit Team details for Groups they do not supervise. (xMatters Reference: PRE-47) 41. Exhaustive Report displays internal Protocol Provider details. If notification delivery fails due to an authentication failure, the Exhaustive Report displays the Protocol Provider's Server IP address. However, the Exhaustive Report should not display internal details about the configuration. (xMatters Reference: PRE-43) 40. Null Address Range causes Address Range TON and NPI to be ignored On the SMPP Device Engine Details page, leaving the Address Range setting blank (i.e., null) causes the Address Range TON and Address Range NPI settings to be ignored. (xMatters Reference: PRE-37) 39. Split Size should be mandatory when Split Long Message is selected. On the settings pages for Protocol Providers, selecting Split Long Message should cause Split Size to become a mandatory setting (i.e., it cannot be left blank). (xMatters Reference: PRE-36) 38. WS_AUDIT table uses the wrong sequence (Oracle and DB2 only). In the xMatters (Oracle or DB2) database, the WS_AUDIT table does not sequence its data correctly, causing errors (e.g., when using the FindGroups web service operation). (xMatters Reference: PRE-35) 37. Permissions page shows duplicate permissions for merged Admin account. When xMatters Administrator accounts are merged (i.e., Super Admin and Company Admin are merged), the Permissions page for the merged Admin displays some permissions twice. (xMatters Reference: PRE-34) 36. Cannot reduce the number of licensed Users in one-Company deployment. In non-multi-tenancy xMatters deployment (i.e., a deployment with only one Company), attempting to reduce the number of licensed Users results in the following error message: "The license of users is less than the configured quota values of all companies, to downgrade a license the quota must be reduced first". (xMatters Reference: PRE-30) 35. Stack trace occurs when trying to remove Event Domain with active events. When an Event Domain still has active events, a stack trace occurs if removal of the domain is attempted. Deletion should be prevented (with message) when the Event Domain has active events. (xMatters Reference: PRE-28) 34. Cannot add Admin User's Devices to a Group when Admin accounts are merged. (xMatters Reference: PRE-25) 33. Only xMatters enterprise should include the Low-Use User Report. xMatters workgroup currently includes the Low-Use User Report; this report should be limited to AlarmPoint enterprise. (xMatters Reference: PRE-23) 32. On SSL, Internet Explorer displays error when saving Data Import results. When attempting to save the results of a Data Import on an SSL connection (i.e., by clicking the "Download Result" button), Internet Explorer displays an error message. (xMatters Reference: PRE-18) 31. Existing Custom Subscription Panels drop Devices when opened and re-saved. Users will unexpectedly lose notifications to BES and Numeric Pager Devices if an existing Subscription Panel (that has not been modified to support Device Names) is opened and re-saved for any reason. (xMatters Reference: PRE-1972) 30. setPresentation has new optional parameter specifying Device Type. On the notification script object, setPresentation has a new optional parameter that allows you to specify a Device Type. This causes the presentation script to generate content only for this Device Type (for example, when you do not want to generate BROWSER & VOICE content). Current behavior when no DEVICE TYPE is passed will remain the same (i.e., content for BROWSER and VOICE will be generated). (xMatters Reference: PRE-1681) 29. SNPP Device Engine does not handle the 88x response code properly. The SNPP Device Engine does not handle an 88x response code to the MSTAtus command properly, treating it as user replied. The handling should be modified to match section "4.6.10 MSTAtus " of the SNPP protocol. (xMatters Reference: PRE-17) Issues fixed in xMatters 410 patch 1: ************************************* 28. Custom Messaging Panels not ordered properly after upgrade to 4.1. Existing message panels are not ordered properly after upgrading to xMatters 4.1 running against a DB2 database. Although the panels remain usable, they exhibit the following symptoms: * The panels are displayed out of order on Messaging tab's left menu (the Quick Message Panel should appear first) * All of the panels are ranked as "0" in the Order column of the table on the Custom Messaging Panels page * The Reorder page for Messaging Panels throws a stacktrace when saved. (xMatters Reference: APE-19210) 27. Upgrading to xMatters 4.1 may cause Custom Subscription Panels errors. Existing xMatters integrations (e.g., to HP NNMi) that include Custom Subscription Panels may experience errors after xMatters is upgraded to version 4.1. In particular, a "String index out of range" exception occurs on xMatters integrations that have a summary panel for Subscription details. (xMatters Reference: APE-19108) 26. Group Schedules set to end after X occurrences cannot be notified. After applying xMatters 4 patch 5 (Patch 400-005), newly-created Groups with Schedules set to end after a specified number of occurrences cannot be notified (and the node generates a stacktrace). (xMatters Reference: APE-18846) 25. Some SIP servers (e.g., Avaya) do not recognize xMatters DTMF tones. (xMatters Reference: APE-18172) 24. getDigits script method can only capture up to ten digits on SIP. The getDigits script method for the phone script object can only capture up to ten digits on SIP. This applies to all uses of getDigits, including Login IDs, passwords, conference numbers, etc. For example, if a User attempts to enter an 11-digit Phone Login ID, the returned number will include only the first 10 digits (resulting in an invalid login). (xMatters Reference: APE-18171) 23. Unable to view home page when xMatters configured for SSO. If xMatters is configured for SSO and a User successfully logs into xMatters via SSO and subsequently logs out, they will be redirected to the xMatters login page (i.e., a page with a URL ending in SSOSignOn.do). When the User logs in again (using valid credentials), the login is successful but the User is presented with a page indicating that they do not have the proper permissions to view their xMatters home page. (xMatters Reference: APE-18141) 22. LDAP authentication logging has been improved to assist with debugging. (xMatters Reference: APE-18137) 21. Deleting Company can cause SIP Device Engine callin/callout & TTS failure. In a multi-Company deployment, deleting a Company can cause the SIP Device Engine callin, callout, and TTS engine to fail. (xMatters Reference: APE-18136) 20. SMPP password field does not validate field length. The SMPP specification allows for a short password, and the SMPP Device Engine correctly detects passwords that are too long and logs an error. However, this error is not obvious to Users in xMatters; the password should be validated in the associated configuration field, providing the User with immediate feedback when an invalid password is specified. (xMatters Reference: APE-18131) 19. Assign Permissions page displays permission names instead of descriptions. The Assign Permissions page currently displays the formal names of Permissions (e.g., view.screen.PersonDetails) rather than descriptions of the Permissions. While these names generally match the URL for each page, they may not be congruent with the page title, which can cause User confusion. (xMatters Reference: APE-18113) 18. FindWhoIsOnDuty web service call response includes duplicate Users. When the FindWhoIsOnDuty web service call is run against a Group with duplicate Users across Teams, the response includes a detailed recipient list with duplicate Users. This data duplication can delay response times and serialization, and in extreme cases can cause out-of-memory errors. (xMatters Reference: APE-18086) 17. No Health Monitor Message is sent when SIP registration fails. When a SIP Device Engine fails to register with the SIP Server, the Health Monitor should send out a message to this effect. (xMatters Reference: APE-17570) 16. Add 'export to Microsoft Excel' option to Company Quotas page. (xMatters Reference: APE-17400) 15. xMatters URLs can be improperly shared, causing potential security issue. xMatters URLs can be improperly shared, which can cause a potential security issue. In particular, Users with the same permissions who share URLs may be able to view the other User's xMatters pages via the shared URL. (xMatters Reference: APE-17368) 14. User's notification status may be reported on the wrong Exhaustive Report. A User's notification status may be reported on the wrong Exhaustive Report for simultaneous events that reach voicemail. (xMatters Reference: APE-16934) 13. AddEvent web service call does not allow null values for event tokens. The AddEvent web service call does not allow null values for event tokens. This can cause some custom integrations to receive an unexpected unsuccessful response code. (xMatters Reference: APE-16597) 12. Health Monitor events not created for a failed Protocol Provider. In a multi-Company xMatters deployment, Health Monitor events are not created for a failed Protocol Provider if the notification target is not in the default Company. (xMatters Reference: APE-16412) 11. Log message and script report ANAYLSIS_ERROR instead of actual error. When the xMatters Phone Device Engine encounters connection errors such as NetworkDown or another telco network signal, the log message reports ANAYLSIS_ERROR instead of the actual error. (xMatters Reference: APE-16175) 10. Custom Attributes Details page accessible without proper permissions. (xMatters Reference: APE-16158) 9. View Sent Messages page displays only one of multiple predicate values. xMatters 4.0 patch 5 added functionality to allow the selection of multiple values for one predicate in a Custom Messaging Panel. However, after sending a message with multiple predicate values selected through such a messaging panel, the View Sent Messages page displays only one of values. (xMatters Reference: APE-16138) 8. Cannot delete Subscription when it has an active alert. Currently, if there are active alerts for a Subscription, it cannot be deleted. This can become an issue for longer-lifecycle Subscriptions for which there are always active alerts (i.e., the Subscription can never be deleted). (xMatters Reference: APE-15724) 7. EventScriptObjectImpl.getUniquePersons method can cause stacktrace. When message recipients in different Companies have the same User ID, a script including the EventScriptObject.getUniquePersons method causes a stack trace to be logged and notifications are not sent out. The method should be modified so that it distinguishes between Users with identical IDs in different Companies (i.e., the method should be Company 'aware'). (xMatters Reference: APE-15720) 6. SMTP Device Engine cannot send multiple emails in one connection. To maximize message throughput, the SMTP Device Engine should be able to send multiple emails in a single connection. After applying xMatters 4.0 patch 9, the xMatters SMTP Device Engine will support multiple emails in one socket connection. For details, see the article titled "How can I configure AlarmPoint to send multiple emails through one connection?" on the xMatters (user) community web site. (xMatters Reference: APE-15714) 5. Add new isValid method to ExternalServiceMessage script object. A new method called isValid should be added to the ExternalServiceMessage script object. The script should use this method before it tries to send messages to an external service. (xMatters Reference: APE-15675) 4. Adding an empty (i.e., blank) Event Domain Predicate causes stacktrace. Attempting to save an Event Domain Predicate with a null value causes a stacktrace to occur. (xMatters Reference: APE-15452) 3. Pagination on the Groups I Supervise page does not work correctly. In some cases, the incorrect page is displayed on the Groups I Supervise page. For example, clicking the page 6 button may display page 10 of the results. (xMatters Reference: APE-14962) 2. Support User should not be able to create or delete Users or Groups. Users who have the Support User Role can currently create or delete Users and Groups; these permissions should be removed from the Role. (xMatters Reference: APE-13480) 1. External key of DataSync's DS_USERS table is case-insensitive for imports. The external key of the Data Synchronizer's DS_USERS table is case-insensitive when importing users. For example, if an attempt is made to import a new User with an external key of "test-user" and there is an existing User with an external key of "TEST-USER" (imported via a previous Data Sync), the new User is not imported, and details for the existing User will instead be updated. The external key should be case-sensitive. (xMatters Reference: APE-15531) ------------ 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) After applying xMatters (alarmpoint) engine version 4.1 patch 4 and starting the node, attempting to install another node results in an error. A workaround for this issue is described in the article "Cannot install new node after applying 4.1 patch 4", available on the xMatters support web site. Note that this issue will be fixed in an upcoming patch. (xMatters Reference: PRE-4817) 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) After applying xMatters (alarmpoint) engine version 4.0 patch 11 or version 4.1 patch 3, data synchronization does not work for Users authenticating with LDAP. For further information, refer to the article "Data synchronization does not work for Users authenticating with LDAP after applying patch 400-011 or 410-003", available on the xMatters (user) community web site. This issue will be fixed for the 410-004 patch release. (xMatters Reference: PRE-3663) 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) ---------------------- INSTALLING THIS PATCH ---------------------- Apply this patch to all xMatters Application Nodes, Notification Nodes and Web Servers (and any DataSync installations, if applicable). WARNING: This patch includes database changes (see next section) that may impact your replication mechanism; consult with your database administrator for further details. Database changes ---------------- 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) Before installing this patch: ----------------------------- 1. Shut down all Node processes. 2. Shut down all Webserver processes. 3. Back up the xMatters Database. To install this patch: ---------------------- 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. 1. Back up the xMatters installation directory. - On Windows, default install directory is: C:\Program Files\AlarmPointSystems\AlarmPoint - On Unix, default install directory is: /opt/alarmpointsystems/alarmpoint 2. Save the @patch_version@.zip or @patch_version@.tar.gz file to the xMatters installation directory. 3. Do one of the following: - On Windows, extract (i.e., unzip) the @patch_version@.zip file to the installation directory and overwrite the existing files. - On Unix, run the following commands on the @patch_version@.tar.gz file and overwrite the existing files: gunzip @patch_version@.tar.gz tar -xvf @patch_version@.tar 4. If you are applying this patch on: - Windows, delete the following files from the Windows\system32 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 /jre/bin Navigate to the /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 /jre/bin Navigate to the /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 /jre/bin Navigate to the /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 "After installing this patch", 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: /opt/alarmpointsystems/alarmpoint_datasync 7. Do one of the following: - Extract (i.e., unzip) the @patch_version@-DataSync.zip file to the installation directory and overwrite the existing files. - Run the following commands on the @patch_version@-DataSync.tar.gz file and overwrite the existing files: gunzip @patch_version@-DataSync.tar.gz tar -xvf @patch_version@-DataSync.tar After installing this patch: ---------------------------- 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. 1. Restart the Node processes. 2. Restart the Webserver processes. 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 ---- /logs/AlarmPoint.txt. Web Server ---------- /webserver/webapps/axis2/WEB-INF/logs/ AlarmPoint_WebApp.log /webserver/webapps/cocoon/WEB-INF/logs/ AlarmPoint_WebApp.log /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. ------------------------------ FILES INCLUDED WITH THIS PATCH ------------------------------ @patch_version@.tar.gz @patch_version@.zip @patch_version@-DataSync.tar.gz @patch_version@-DataSync.zip --------------- WEBSPHERE FILES --------------- The "Patches/Misc. Downloads" section of the xMatters (user) community web site (https://connect.xmatters.com/) includes the following archive files: @patch_version@-websphere.tar.gz @patch_version@-websphere.zip These archive files contain the following WAR files for use with IBM WebSphere 7: - @patch_version@-axis2-websphere7.war: Contains xMatters Web Services files. - @patch_version@-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 (available for download from the xMatters (user) community site). END OF FILE