Network Computingwww.networkcomputing.com

Afaria provides a range of control covering software distribution, document management, systems backups, device inventory, session scripting and configuration management. Client devices can connect via any physical means: dial-up modem, wireless LAN, remote LAN, the Internet, CDMA (Code-Division Multiple Access), CDPD, GSM (Global System for Mobile Communications) and companion PC--as long as they can get a TCP/IP connection back to the Afaria server.

Ready, Set, Go

I set up the Afaria server and Microsoft SQL Server in our Syracuse University Real-World Labs®. Afaria uses a SQL database in the back end to store application logs and account information. In addition to supporting Microsoft SQL Server, Afaria supports Oracle8/8i databases. I installed both servers on identical Dell Computer Corp. OptiPlex Pentium III, 600-MHz, 256-MB machines running Windows 2000.

The software installation involved quite a few steps. For performance reasons, XcelleNet recommends that you install SQL Server and the Afaria server on separate machines. For organizations that don't have Microsoft SQL Server, Afaria provides a slimmed-down version called Microsoft Data Engine (MSDE). Before running setup on the Afaria server, I had to install Microsoft's XML (Extensible Markup Language) parser and add a user account that the Afaria server would need to log in as a service. After taking these preparatory steps, I ran the Afaria server's simple install program.

Afaria's control features are implemented as types of channels. Channels are created in a wizard interface, then an intuitive channel administrator is used to create the tasks clients perform when they're connected to the server. I found it helpful to group channels into channels sets, which let me process multiple tasks consecutively. For example, I created software-distribution channels to dispense applications to both Palm and Windows CE handhelds.

XcelleNet's Afaria (screen view) Click here to enlarge

To configure the clients, I entered the IP address of the Afaria server and typed the name of the channel it should run upon login. The client interface lets you enter only one channel to run upon connection, so I used a channel set that ran all the channels I wanted for that type of device. During the times the clients were connected, I could see logs of the transactions along with a status meter that showed the progress on both the server and the clients.

I used the Afaria Menu front-end interface to define channels, view logs, monitor active sessions, check server health, manage inventory, perform backups and create client-installation setup files. In addition to scheduling tasks to run on the clients, I configured the Afaria server to provide authentication for enhanced security. I also set up the Afaria server's Web interface for remote administration, but found its functionality disappointing compared with that of Afaria Menu. XcelleNet claims to be moving toward a completely Web-based configuration with fully functioning features.

In this version of the Afaria server, the document-management feature is supported on both Windows CE devices and Palm handhelds. I used a document-manager channel to distribute a folder full of Microsoft Word, Microsoft Excel, HTML and image files to each of the client devices. The documents were reformatted on the server so each client device could read them. Afaria also included an OEM version of DataViz Documents To Go WordView and SheetView so Palm devices could view Word and Excel documents. On some of the clients, I configured the server to upload the documents automatically, and on others I configured it so the clients would have to retrieve the documents manually. Both methods functioned as advertised.

While I was backing up my 3.9-MB mail file to the Afaria server, I noticed some bugs related to using the Afaria client on the Palm. Afaria support representatives were able to re-create the problems and determine there are some issues with the software handling certain types of MailDB files. They're working on a patch to address these issues. When the backup channels are functioning properly, they let you configure the clients to send copies of files to the server. To restore a backed-up file, you can use the backup console and mark the individual files or folders. The next time a device logs on to the server, the file will be restored automatically. The backup channels worked fine on every supported device except for the Palm.

Security, Scalability

Afaria 4.51's security mechanisms are based on authentication via NT Domain, LDAP Directory or SSL (Secure Sockets Layer) encryption. I used a Windows 2000 server to provide both authentication schemes, but I had to reinstall the server to change from NT Domain to LDAP authentication. Once authentication is enabled, all clients must provide a valid user name and password upon connection. Clients can use SSL to encrypt information transfers as data travels across insecure public networks, but I was disappointed to find that only the Windows 32-bit and CE clients could support this capability. Multiple Afaria servers can be configured on your network to provide additional capacity, localized Afaria services or load-balancing. The servers maintain the same channel information on each via automated replication.



I tested the Afaria client on a Handspring Visor Platinum, a Palm m505 handheld and a Casio Cassiopeia Pocket PC, and was impressed that the new version adds significant functionality to devices previously lacking in breadth of options and control features. This product would be very useful to any organization tasked with supporting a large number of mobile devices. If your organization has trouble providing the same level of support to its mobile users as it does to its wired users, Afaria 4.51 is a step in the right direction.