Chapter 26 Developing a Connector for Microsoft Outlook Architecture

This chapter introduces the deployment process of the Connector for Microsoft Outlook.

This chapter contains the following sections:

• Desktop Deployment Process Tasks

• Why Use the Deployment Toolkit?

Desktop Deployment Process Tasks

Deployment of the Connector for Microsoft Outlook plug-in to each user desktop requires three distinct tasks:

• Installation. The necessary and appropriate software must be physically installed to the Outlook user's desktop. Software installation requires access privileges that often are disallowed to many or most end users. In this case, most enterprises implement a “push” method for software distribution from the system administrator to user desktops that bypasses the requirement for user access privileges. (This “push” method of distribution is explained in more detail in “Desktop Installation Methods.”) If your network serves “locked-down” Windows environments where end users cannot install software, we strongly recommend this sort of automated configuration management as a way to avoid many individual desktop visits.

• Configuration. Connector for Microsoft Outlook is installed with an assortment of configuration parameters including the server names and port numbers, user password options, directory search defaults, the log file path, and so forth. While users or administrators can manually configure these settings within Outlook at each desktop, it is far more efficient for administrators to pre-configure these for groups of users and avoid desktop visits.

• Conversion. The desktop setup wizard can convert Exchange users’ Contacts, Journal, and Notes data to local (desktop) Personal Folders (.pst) files. Any such existing personal data files associated with Microsoft Exchange and Outlook must be converted to be compatible with the plug-in. (This task does not apply to new email users who were not previously working with Microsoft Exchange.) If a user has password-protected his or her data files, these conversions will require the password associated with the protected files. The conversion function is processor-intensive and may run on the user's computer for many minutes or even hours if a user has large amounts of data to convert. For this reason the conversion utility lets a user defer the conversion of larger files to a later time, such as during a lunch break or even overnight.

The Deployment Configuration Program lets a system administrator create installation packages that will automate some or all of these tasks for end users, depending on the administrator's deployment strategy for any particular group of users.

Why Use the Deployment Toolkit?

With the deployment toolkit, an administrator can control a wide range of configuration parameters for desktop users. Mandating many or most configuration settings will bypass the need for users to ponder options, make choices and set values themselves. These automated or semi-automated installations will spare the corporate help desk many calls for guidance, support, and solutions to the inevitable problems that arise when user choices produce unexpected results. Overall, the toolkit substantially reduces the cost, time and effort required to deploy the Sun Java System Connector software.

A system administrator may create different installation packages for different groups of desktop end user—for example, to enforce different configuration schemes for users in the Sales department versus the Engineering department and so forth, or to offer configuration options to some groups of users while setting fixed parameters (eliminating the choices) for other groups.

If the organization is migrating from Microsoft Exchange, the user's installation packages will also preserve the considerable value of their existing Outlook data stored in .pst files on user desktops, as well as their Notes, Journals and Contacts stored on the Exchange server. The bundled installation packages include a conversion utility that quickly converts all such data to pure Internet addresses, so users will be able to reply to older messages, appointment invitees will receive change notices, and address books and personal distribution lists will remain serviceable after your migration to the Java Enterprise System server.