Key Features & Benefits

• Support of Jabber native XMPP protocol
• Persistent TCP/IP connection between WMP and Jabber XCP servers
• Authentication with Jabber account credentials from the device.
• Single user logon (single identity) used from Jabber Desktop Messenger and RIM clients
• Configurable Application log for tracing problems
• Integration with BES/MDS. The solution leverages BES/MDS to implement the communication between the client application and the Jabber server.
• MDS Gateway is deployed behind the corporate firewall on the same machine as the BES/MDS server
• Resident mode - IM application runs in the background
• Push - leverages the Push capability of MDS (BES Mobile Data Service)
• Separate Activities screen with active conversations and active chat rooms and sessions
• IM client can transmit and receive extended presence information (online, busy, away, and not available) as well as recognize the device of origin (desktop or mobile user).
• Contacts or Buddy List can be managed (add, drop, edit) can be done from the device in the field or from a desktop.
• Contacts and Buddies can and be organized into personalized groups for easy recognition and access.
• Custom notifications and alerts (audio, vibration) can be set up for new inbound messages.
• Message history can be displayed with timestamps.
• While supporting Jabber XCP, WMP also supports other EIM and public IM networks

Software requirements

• Windows NT / 2000 / 2003 servers
• MS SQL Standard Edition or MSDE database
• Microsoft SQL Server 2000 client installed on all WMP cluster machines
• BES/MDS server for deployment of BlackBerry™ clients

Hardware requirements

• Pentium 4 - 1 GHz CPU(s)
• 512 MB RAM
• 20 GB available HDD space

Integration Architecture