Common questions about rebranding from AlarmPoint to xMatters

Q: Can I still use the classic AlarmPoint look-and-feel in the web user interface? 

A: Yes - the xMatters version 4.1 application now supports both the new xMatters theme and the classic AlarmPoint theme. The selection of each theme is controlled by the specified URL used to access the web UI application. 

To access the classic AlarmPoint theme, use the familiar /alarmpoint prefix in your URL; for example:

http://localhost:8888/alarmpoint

To access the new xMatters theme, use the new /xmatters prefix in your URL; for example:

http://localhost:8888/xmatters 

Note that the AlarmPoint theme is not available in xMatters version 5.0.

Q: How 'deep' does the xMatters rebranding extend from a technical perspective?

A: The new corporate branding only applies to the user interface application. The following will not reflect the new styling:

  • Any custom pages, message panels, or subscription panels that have the CSS embedded in the page. This includes any AlarmPoint integrations.
  • AlarmPoint presentation scripts that generate HTML emails. These are customer defined and usually customized. As a result, they must be updated manually (see the next question, below).
  • Mobile Gateway integrations
  • Default installation directories will still present the usual AlarmPoint paths and directories (e.g., on windows, C:\Program FIles\AlarmPoint Systems\AlarmPoint; on *nix, /opt/alarmpointsystems/alarmpoint).

Q: How do I re-style HTML emails manually? 

A: To have the xMatters logo and colors in your HTML email notifications, you must modify the presentation scripts for each domain, as described in the following steps: 

1. Do one of the following:

  • If you are using a newer integration, open PRESENTATION > createHTMLDeviceContent Script.
  • If you are using a older integration, open PRESENTATION > Presentation.
NOTE: if you are using an older script, you must also update the subscriptionPresentation and quickMessagePresentation scripts. 

2. Search for $styleinfo and replace the entire section with the text below:

# Add style information.
$styleinfo = ""

3. After updating the CSS, update the logo by opening the default presentation script and the messaging > presentation scripts and adding or modifying the following line:

$resourceURL = $main.alarmpointURL & "static/images/xmatters/logos/xmatters_email.gif" 

NOTE: You must also deploy the xmatters.gif to /images/xmatters/logos. 

 

Q: If I'm fronting the web server, will I have to make any changes? 

A: Yes. Follow the steps appropriate for your fronting server below: 

Microsoft IIS

1. Open the uriworkermap.properties file, which should read as follows (before changes are made):

/alarmpoint/*=alarmpoint
/static/*=alarmpoint
/api/services/*=alarmpoint
/mg/*=alarmpoint
/jsp/*=alarmpoint

2. Do one of the following:

  • If you want both the AlarmPoint and xMatters web interfaces to be available, add the following line:

/xmatters/*=alarmpoint

  • If you want only the xMatters web interface to be available, add the line above (/xmatters/*=alarmpoint) and delete following line:
/alarmpoint/*=alarmpoint

3. Save the file. 

Apache

Follow the instructions in the Installation and Administration Guide, and then add the following two lines to the lines under "To front the AlarmPoint Web User interface":

ProxyPass /xmatters/ http://internal-host:8888/xmatters
ProxyPassReverse /xmatters/ http://internal-host:8888/xmatters 

Q: Is product licensing affected by this change? 

A: Yes; the new xMatters product names map as follows to the old AlarmPoint names:

  • xMatters lite replaces AlarmPoint Express
  • xMatters workgroup replaces AlarmPoint Professional
  • xMatters enterprise replaces AlarmPoint Enterprise

NOTE: There is no xMatters product equivalent for AlarmPoint Standard. 

Only xMatters workgroup requires a new license key, which will work only for products that have applied version 4.1 patch 3. Previous patch levels will not recognize or accept the xMatters workgroup license version. However, AlarmPoint license version keys will still work as expected. 

License Uploading
License key uploads are not affected by user interface styling (i.e., AlarmPoint vs. xMatters look and feel). For example, all license keys can be uploaded in both the classic AlarmPoint UI or the new xMatters UI. Each UI style displays different logos depending on the version key used. (Again, note that the xMatters workgroup version key is supported only in 4.1 Patch 3 and later.) 

User Interface License Logos
The user interface displays different logos depending on the version key used, and each user interface style can only handle the version keys for which it was designed. For example, applying an AlarmPoint Professional license key causes the classic AlarmPoint UI to display the AlarmPoint Professional logo; however, the new xMatters UI will only display the xMatters logo with no version (i.e., because there is no such product as xMatters Professional). Conversely, applying an xMatters workgroup license key causes the new xMatters UI to display the xMatters workgroup logo; however, the classic AlarmPoint UI will only display the AlarmPoint logo with no version (i.e., because there is no such product as AlarmPoint workgroup). 

The following list summarizes how license key names map to logos in the user interface:

  • VERSION_EXPRESS: xMatters lite OR AlarmPoint Express
  • VERSION_STANDARD: xMatters OR AlarmPoint Standard
  • VERSION_PROFESSIONAL: xMatters OR AlarmPoint Professional
  • VERSION_WORKGROUP: xMatters workgroup OR AlarmPoint
  • VERSION_ENTERPRISE: xMatters enterprise OR AlarmPoint Enterprise
  • VERSION_SERVICE_PROVIDER: xMatters OR AlarmPoint Service Provider 

xMatters Reference

DTN-2390, DTN-2464, JDN-1062

Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk