Over the past year, many companies have deployed Microsoft Mobile Information Server 2002, Microsoft's latest version of its Wireless Application Gateway (WAG). Although Mobile Information Server has some great features, it also has some disadvantages. As a result, if you're thinking about implementing a WAG, you might want to consider some other vendors' products as well.
Do You Need a WAG?
WAG is a common term for the piece of enterprise infrastructure that acts as a gateway for mobile and wireless devices to access an enterprise's data sources and resources. WAGs have been on the market for quite some time. Typically, WAGs are installed on standalone servers that reside either in or behind a corporate demilitarized zone (DMZ). WAGs aren't required to support enterprise mobile and wireless applications, but WAGs' features often make their deployment a good architectural decision. Key reasons to implement a WAG include the following:
Multiple-device support—Most companies don't use a standard type of mobile or wireless device or a standard OS. With WAGs, companies can support multiple devices and OSs.
Multiple data-source support—Most WAGs natively support access to personal information manager (PIM) functionality, such as access to email, calendar entries, and contacts on enterprise email servers. Some WAGs also support access to custom data sources and various file types.
Remote device management—Remote device management is essential when you must support numerous mobile users who are remote or constantly on the go. Many WAGs feature remote device-management functionality. The functionality can be simple (e.g., remote device configuration, remote backup and restore) or advanced (e.g., remote software installations, remote device recovery).
Optimized wireless connectivity—Wireless network coverage, bandwidth, and reliability can vary widely. WAGs often include advanced connection-optimization and data-compression mechanisms that enhance the available bandwidth and reliability of wireless connections.
Enhanced security—Security is an important consideration when you implement mobile and wireless solutions in an enterprise. When WAGs reside in or behind the DMZ, in many cases, wireless and mobile devices can't directly connect to the corporate network. In addition, most WAGs feature enhanced authentication to prevent unauthorized access and an encryption mechanism that encrypts all data transmitted to and from the mobile device.
Multiple-connection support—When PDAs first came out, you could synchronize data only through a cradle, which meant that you needed a PC to transfer data to and from the PDA. With the introduction of WAGs came more connectivity options. Nowadays, most WAGs let you synchronize data in a variety of ways, including cradles, wireless WAN (WWAN), wireless LAN (WLAN), and Bluetooth. These connectivity options make users truly mobile yet still connected.
Industry-standard support—Most of the leading WAGs support appropriate industry standards, including XML, Simple Object Access Protocol (SOAP), SyncML, and Wireless Application Protocol (WAP). Support for industry standards is important if you want to build custom line of business (LOB) applications (i.e., applications that are vital to running an enterprise) on top of the WAG platform and integrate the WAG platform successfully into enterprise infrastructure.
Useful Server Features
Mobile Information Server has several key features, including Microsoft Outlook Mobile Access, Microsoft Server ActiveSync, Intranet Browse functionality, and notification functionality. Outlook Mobile Access is a mobile version of Outlook Web Access (OWA) that supports WAP and is accessible through microbrowser devices. Outlook Mobile Access provides realtime access to Microsoft Exchange Server email, calendar entries, tasks, personal contacts, and the Global Address List (GAL).
Server ActiveSync lets users synchronize email, calendar entries, and contacts over any connection (e.g., WWAN, WLAN, cradle, dial-up). Server ActiveSync synchronizes the data from Exchange to the wireless or mobile device, which means that even when a connection isn't available, you can use the device's features and access your data. The supported devices are Pocket PC 2003 and Pocket PC 2002 and the new Windows Powered Smartphones, which are scheduled for release later this year. Server ActiveSync can transfer data only through a Secure Sockets Layer (SSL) connection, so all data is encrypted end-to-end from the device to Mobile Information Server. Mobile Information Server truncates all messages and downloads only the first 0.5KB of each message, which makes Server ActiveSync efficient over lower bandwidth connections. You can customize the truncation to change how much of each message is downloaded.
Intranet Browse uses a reverse-proxy type of functionality to let Internet-capable microbrowser devices access microbrowser applications hosted within the corporate network. The notification functionality lets you send short messages to mobile and wireless devices that support Short Message Service (SMS) or SMTP messages. Thus, users can receive notifications about calendar changes, important email, and so forth. In addition, you can use COM or SOAP APIs to create custom applications that leverage Mobile Information Server's notification infrastructure.
If you don't have a username & password, please
register now.
Reader Comments
it's unfair comparison between MIS and SureWave Enterprise server (SES). MIS does not support some important features of WAG like supporting Mobitex, providing offline access, cradle and wireless synchronization, and supporting open standards like SyncML, SES supports all these featues and thus much advanced mobile platform than just a WAG.
Prev. page
[1]
