Sun ONE Portal Server and Microsoft Exchange Integration Cookbook
- How this Article is Organized
- Obtaining the Scripts and Tools for this Article
- Integration – A Historical Perspective
- Pre-Cooking and General Preparation
- Outlook Fat Client a la Carte Recipe
- Outlook Express Messaging Soup Recipe
- OWA Over a Netlet With a DNS Twist Recipe
- OWA Luau with Rewriter Fire Dancing: the 3 o'clock Show
- OWA Luau with Rewriter Hula Dancing: the 6 o'clock Show
- About the Author
- Ordering Sun Documents
- Accessing Sun Documentation Online
This article and corresponding scripts provide you with information and tools that are pertinent to the successful integration of Microsoft Exchange, 2000 SP3, and the Sun Open Net Environment (Sun ONE) Portal Server software (versions 3 and 6). This article is provided as a result of increased interest from Sun and Microsoft customers who are looking for an end-to-end secure thin client Exchange solution.
Rather than providing information as a top-down technical analysis of Exchange internals and problem isolation, this article clearly states integration requirements up front, provides steps to achieve those requirements, and then proceeds with a detailed explanation for each topic. Best practices with respect to advanced rewriting techniques and content pitfalls are discussed with detailed explanations as to their relevance or application.
Scripts are provided which help aid in the automation of the integration endeavor. These scripts, along with required fixes, provide a total integration solution. This article also compiles the multitude of disparate information floating about relating to integration requirements, product version compatibilities, and feasibility.
In addition to the step-by-step integration procedures, this article includes background information and the context necessary to further diagnose any integration problems which might not be covered specifically in this article.
How this Article is Organized
The primary sections of this article are presented in the form of recipes. The recipes you choose to implement depend on what environment (install level, and so forth) you are using for the integration.
Each recipe includes:
Ingredients indicate what the overall recipe consists of. This could include a count or summarization of configuration changes, customizations, and required patches. The web browser version is listed for reference, but recipes do not require a particular version of web browser.
What summarizes the procedures you need to perform.
How specifies the precise steps you must perform to accomplish necessary tasks.
Why describes the significance and purpose of each procedure.
As in baking a cake, no ingredient can be left out, or the recipe will fail and the integration will be incomplete or might not work at all.
The following recipes and related topics are provided in this article:
"Obtaining the Scripts and Tools for this Article" on page 3
"Integration A Historical Perspective" on page 5
"Pre-Cooking and General Preparation" on page 6
"Outlook Fat Client a la Carte Recipe" on page 9
"Outlook Express Messaging Soup Recipe" on page 12
"OWA Over a Netlet With a DNS Twist Recipe" on page 17
"OWA Luau with Rewriter Fire Dancing: the 3 o'clock Show" on page 22
"OWA Luau with Rewriter Hula Dancing: the 6 o'clock Show" on page 52
"Glossary" on page 60
The Sun ONE Portal Server software is referred to as the portal server for the remainder of this article.
The Sun ONE Portal Server software was formerly known as the iPlanet Portal Server software.