How do I change the port for the xMatters web server after installation?

If I have already installed the web server, can I change the default port setting, or do I have to reinstall xMatters? 

By default, the xMatters web server runs on port 8888. You can set this to a different port during installation, or you can use the following steps to change the port for an existing installation.

For this example, assume that the web server (Jetty) was installed on port 8888, and you want to change it to port 80. Note that if you are doing this on a Unix system, make sure the web server process is started as ‘root’; any port under 1024 is a “privileged port” and requires ‘root’ access.

Note: The following example uses the Windows path; if you are working on a Unix system, adjust the file path accordingly.

To change the xMatters web server port:

  1. Navigate to the web server installation directory; by default, C:\Program Files\AlarmPointSystems\AlarmPoint\webserver\etc\
  2. Open the Jetty.xml file in a text editor.
  3. Locate the following line:
<SystemProperty name="jetty.port" default="8888" />
  1. Change the port number from 8888 to 80.
  2. Save and close the Jetty.xml file
  3. Restart the webserver (service or daemon).
You should now be able to use the following URL to access the xMatters login page:

http://localhost/xmatters

Note that changing the default port for the web server may affect the ability of some Devices to communicate with xMatters, specifically BlackBerry Devices. The out-of-box presentation scripts for BlackBerry Devices attempt to post to the web server on port 8888. If you change your port settings as described in the steps above, you must also change the presentation scripts. The following code illustrates the location within the default domain presentation scripts; the $content.pushurl and the FORM action URL should be changed to reflect the new port:

....  
ELSE-IF ($content.deviceclassification == "bes")  
...  
 #Fill the html part for BES device  
 #Note: content.pushurl must be present, even if url is invalid  
 $content.pushurl = "http://localhost:8888/static"  
 $content.pushtitle = $content.subject  
 $content.htmlmessage = $content.htmlmessage & "<table width=\u0022100%\u0022 border=\u00221\u0022>"  
 $content.htmlmessage = $content.htmlmessage & "<tr><td><b>Incident ID: </b></td><td>" & $event.incident_id & "</td></tr>"  
 $content.htmlmessage = $content.htmlmessage & "<tr><td><b>Situation: </b></td><td>" & $content.situation & "</td></tr>"  
 $content.htmlmessage = $content.htmlmessage & "<tr><td><b>Device: </b></td><td>" & $content.device & "</td></tr>"  
 $content.htmlmessage = $content.htmlmessage & "<tr><td><b>Time of Incident: </b></td><td>" & $userTime & "</td></tr>"  
 $content.htmlmessage = $content.htmlmessage & "</table>"  
 IF (EXISTS($content.choices))  
 $content.htmlmessage::add("<br>Your response choices are:")  
  
#You may change the URL to point to the alarmpoint web  
 $content.htmlmessage::add("<FORM action=\u0022http://localhost:8888/jsp/ProcessNotificationResponse.jsp\u0022 method=\u0022post\u0022>")  
....  

xMatters Reference

DTN-1681, SUP-1301, JDN-1096

Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk