• Servers:
  • Application server: Windows 2003 Server or higher, with IIS and ASP .Net enabled. Does not require a dedicated server.
• Client Device:
  • For email/SMS notifications: any email or SMS client.
  • For browser auto-refresh dashboard: browser with CSS and JavaScript enabled.
• If pushing notifications to BlackBerry smartphones:
  • BlackBerry Enterprise Server v4.x or v5.x
  • Smartphones: browser with CSS and JavaScript enabled.

Mobile Alerts' architecture consists of the following components:

• Management Console: a .Net web application that runs on a Microsoft IIS server, and provides all configuration and administration functionality.
• Content Collection Engine: a .Net application that performs the specified health check tests on designated devices and services, collects and logs the results, and generates the content to be sent to recipients via email, SMS or BlackBerry push.
• If using email or SMS notifications:
  • Mobile Alerts sends them via the SMTP server specified in the configuration.
• If using BlackBerry devices:
  • BlackBerry Enterprise Server: once the content has been collected and assembled, Mobile Alerts uses the Push Application Protocol (PAP) or RIM Push to deliver content to the handhelds via the Mobile Data Service module of the BlackBerry Enterprise Server. Mobile Alerts also accesses the server database to obtain user and device information in real-time.
  • Handheld BlackBerry Browser: the content delivered to the handhelds is plain HTML, therefore no special software or configuration changes are required on handhelds. Content can be pushed as a Channel or as a Message.