Oracle Application Server Provider for Microsoft Exchange 2003 - Release Notes
OracleAS Portal Integration Solutions
Oracle Application Server Provider for Microsoft Exchange
- Release Notes
| Creation Date: |
June 2005 |
| Status: |
Production |
Portlet Name:
|
exchange
|
Contents
System Requirements
Installation
Known Issues
System Requirements
The following are the recommended and minimum requirements to use and install
the Oracle Application Server Provider for Microsoft Exchange:
| Application Server |
OracleAS 9.0.2 or later |
| OracleAS Portal Version |
3.0.9.8.2, 9.0.2.x, 10.1.2.x |
| Browsers |
Netscape 4.0.8 and above,
Microsoft Internet Explorer 4.0.1 with Service Pack 1 and above |
| Microsoft Exchange Server |
2003 |
| Microsoft Internet Information Services (IIS) |
5.0 |
Note: You may encounter JavaScript errors when using
a browser older than those listed above.
Release
The Oracle Application Server Provider for Microsoft Exchange 2003 emulate a web interface to Microsoft
Exchange 2003 Server. Currently there are 3 set of components exposed by this provider:
1. Inbox
2. Contacts
3. Calendar
Independent portlets are provided to access each of the above components.
These portlets render functionalities of Outlook Web Access (OWA) in the
OracleAS Portal environment, thus leveraging the advantages of OracleAS
Portal while providing a web access to Microsoft Exchange Server 2003.
Note:
All the deep links within the portlet will take the user to the
Microsoft Exchange Server 2003 and automatically authenticates the user with
SSO.
If the OracleAS Portal and the Microsoft Exchange Server
2003 reside in different domains then the only possible way to integrate is use ISAPI Filter, refer to the Oracle Application Server Provider for Microsoft Exchange 2003 - Installation Instructions document for more details.
Installation
Follow the instructions within Oracle Application Server Provider for Microsoft Exchange 2003 - Installation Instructions.
Known Issues
- When using the OracleAS Provider for Microsoft Exchange 2003 with OracleAS Portal 10.1.2 the request to the Login Server fails. This causes the deep links into OWA to fail.
- Microsoft Internet Explorer 6.0.2 and later applies a security patch that protects any program making basic authentication, hence the Exchange 2003 external application login does not work.
- The Contacts portlet allows the user to filter contacts by last name starts
with. However, the filter actually returns contacts that contain
the given string. This is an issue with Microsoft's CDO library. According
to CDO documentation, the filter on the PR_SURNAME
field should filter last names by the starts with
condition (see the comments about FL_PREFIX in
this MSDN page).
- There are some known performance issues with CDO sessions and ASP
sessions. Due to Remote Procedure Call (RPC) limitations, there may be a scalability
limitation to using CDO-based applications (refer to pp. 349-350 of Piemonte
and Jamison, "Developing Applications Using Outlook 2000, CDO, Exchange and
Visual Basic", 1999).
- The Microsoft Exchange portlets have not yet been tested for the
scenario where the Microsoft IIS server and the Microsoft Exchange server
reside in different domains. It is assumed that this could be successfully
achieved if there is a mutual trust relationship between the two separate
domains and if the users from the Microsoft Exchange domain are given the
right to log on locally to the IIS server.
- Routing
through the Login Server mechanism to basic authenticate the user
will not work on Microsoft Internet Explorer 6+ and on any other
version where Microsoft's
Security Q832894 patch is applied.
- Routing
through the Login Server to access some of the contents where special
characters like { or } are used, the URL access to that content fails,
due to Login Server is not capable to handle these requests. It some
how discards these special characters and redirects the user to the
URL, hence MS-Exchange is not able to understand the URL request and
fails to serve the data. Thus you will notice 404 Page could not be
found or 404 File not found errors.
Trademarks
Oracle and the Oracle logo are
trademarks or registered
trademarks of Oracle Corporation in the United States and other
countries.
All other names are trademarks and/or registered
trademarks of their respective owners.
|