The job of the network manager is evolving as we adopt Web-based, server-centric computing into a role that requires both technical and business expertise along with a keen eye for rapidly emerging technology trends. Exploring what is around the next bend is becoming increasingly important as a means of gaining a competitive edge in the marketplace.

Recently, I've been examining wireless technology and how it might impact your network, your employees and your customers. In particular, I've been looking into something called the Wireless Application Protocol (WAP), and I believe both wireless and WAP belong on your radar.

What is WAP? It is an open specification, based on IP and XML, that supports standard data formatting and transmissions with wireless devices. The WAP specification has been developed as a result of the formation of a group called the WAP Forum. The group came together in 1997 and consisted of Phone.com (previously known as Unwired Planet), Ericsson, Motorola, and Nokia. The WAP Forum has since gained several new members.

Why should you care about WAP? Well, for starters, it provides another choice for end-user computing. Suppose you have a distributed workforce that needs to access your business applications, e-mail, and the Web in real time. A WAP-enabled device (e.g., Smart Phones, Sprint PCS devices, and some handhelds) can support all of those things at a relatively low cost.

WAP also helps your organization move to a more locationless model, which should speed up decision-making and workflow. Sales and service staff in particular will be able to boost productivity by updating activity in real time, as opposed to the more time-consuming batch or synchronization methods.

Wireless use in Europe and Asia has exploded, and most of these wireless users are accessing both voice and data (Web) services. If your company is hoping to expand to reach a more global audience, WAP-together with globalization-engine technology-will allow users around the world to access your e-business applications.

How difficult will it be to implement WAP functionality on your servers? Not very. WAP can be implemented on any Web server that supports HTTP 1.1.

As defined, the WAP specification is a communication protocol and an application environment. A wireless client can access a WAP gateway and subsequently your Web server. Or, a wireless end-user can directly access an application server where you might have deployed e-business applications.

You might choose to outsource wireless Web and e--mail services. At the same time, you could implement wireless application access at your facilities. The end-user experience would be the same.

WAP Meets Web

The protocol portion of WAP includes Wireless Session Protocol (WSP), Wireless Transport Layer Security (WTLS), Wireless Transaction Protocol (WTP), Wireless Datagram Protocol (WDP) and wireless network interface definitions. WAP is compatible with a variety of operating systems, including PalmOS, EPOC, Windows CE, FLEXOS, OS/9, and JavaOS.

The WAP specification can work with different types of wireless devices and most wireless networks, including CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, and ReFLEX. Support for varied devices, networks, and basic Web serving technology shows that WAP is indeed an open standard.

WAP Apps

Aside from enabling wireless communications, WAP also includes the Wireless Application Environment (WAE). Components of WAE include Wireless Markup Language (WML), an implementation of XML specific to wireless devices; WMLScript, based on JavaScript; a browser; virtual machine; and standard library and application interfaces.

WAE can integrate with existing development tools and skills, such as Java, ASP or CGI. For more detailed technical information on the WAP specification and WML, see the WAP Forum Web site.

The application compatibility found in WAE means that it can easily be used to build custom applications or to wireless-enable existing ones. Moreover, a number of packaged applications are now available, with more on the way.

For example, those using WAP-enabled devices can already send and receive email, obtain news, weather, traffic and other information, as well as interact with ecommerce applications, banking and the corporate intranet. I recently tested a device from OmniSky that let me do all of those things from the convenience of a Palm Vxx device while on the road.

How Will WAP Affect Your Network?

Though I believe that using wireless technology to support application access is still in its infancy, it is not too early to consider the potential impacts to your network. This might be a good time to test drive some wireless devices, keeping in mind that many new and updated models are arriving this year.

You could decide to implement a completely wireless network infrastructure, but that is a topic big enough for another column (and we will examine wireless networking in another issue). Right now, let's say you are maintaining a traditional wired network and want to implement wireless client-application access only.

I'll presume that you forecast your server loads based on traditional desktop and laptop clients. One of the most important things you need to do before enabling wireless client access is to re-assess expected server load. Your wireless applications could potentially reach an audience much larger than the current application access volume you see today on your network. Adequately forecasting and preparing for added volume will definitely be necessary, especially if your applications are accessible by external customers.

The next issue has to do with testing applications that you want to deploy to wireless devices. Certainly, WAP's WAE components let you easily develop or modify existing applications. However, once you create or change applications, you'll need to test them with both regular Web browsers and wireless devices in mind.

The application testing tools vendors are only beginning to support wireless technology. One of these tools, Radview's WebLoad is capable of testing wireless applications-although a few extra steps will be needed in the current release. I expect you'll see a greater number of tools arrive this year that will facilitate wireless application testing.

Also, don't forget to consider implementing a globalization engine if you expect to reach customers around the world. Many users who access applications via wireless don't speak English. Making applications available in local-specific languages can go a long way toward satisfying worldwide customers.

The convergence of wireless (and broadband) with the Web holds interesting possibilities for your network and your company in the near future. Will you consider wireless?

Maggie Biggs (maggie@biggs.com) is the director of the InfoWorld Test Center, where she evaluates emerging technologies. She has more than 15 years of wired and wireless IT experience in the financial sector.