Oracle® Unified Messaging

Release Notes

Release 2.1.2 for Sun SPARC Solaris 2.6

January, 2001

Part No. A86092-02

These release notes accompany Unified Messaging Release 2.1.2 for Sun SPARC Solaris 2.6. They contain the following topics:

• What's in this Release?

• System Requirements

• Software Requirements

• Client Certification

• Migration Issue

• Known Bugs

• Additional References

What's in this Release?

Unified Messaging Release 2.1.2 contains the following features and functionality:

• Reference implementation of JSP-based client

  Unified Messaging now ships with a reference implementation of JSP-based client templates. It's a fully featured client that enables users for email, voice mail, and LDAP access.

• SMS Gateway

  SMS (Short Messaging Services) Gateways are implemented in Java technology.

• Middle Tier Technology Stack

  Based on Apache web server, Apache JServ servlet engine, and Oracle Java Server Pages (OJSP) engine.

System Requirements

• 50 MB of disk space

• 128 MB of memory

Software Requirements

Unified Messaging requires the following software components and associated versions:

Software Components	Version
Oracle Email Server	5.2
Oracle8i Data Server	8.1.7
Oracle Internet Directory	2.1.1
Oracle Internet Application Server	1.0.2.1
JDK/JRE	1.1.8 & 1.2.2
Netscape Communicator or Microsoft Internet Explorer JavaScript-enabled browser	4.6 or 4.7 or higher 5.0.x
Real Audio Server (optional)	5.0
Tiff to Gif Conversion Tool (optional)

Note: The Unified Messaging Java beans are compiled with JDK 1.1.8 and customers extending these Java beans should compile with JDK 1.1.8.

Client Certification

The following client software versions have been tested and certified for the Unified Messaging Release 2.1.2:

• Netscape Communicator 4.6 or higher

Migration Issue

Unified Messaging Release 2.1.2 is a change to Internet standard technology stack (Apache and JServ) and away from Oracle Application Server. Therefore, there is no upgrade procedure for this release. Oracle Unified Messaging 2.1 customers must install a new Web node configuration, and Unified Messaging 2.0 customers must install a new release and create the new database objects, then export old information and import into new.

Known Bugs

The following bugs are known to exist in Unified Messaging Release 2.1.2 and are grouped by process or component. Workarounds are given when appropriate.

Bug Number	Description
938087	Unified Messaging beans API does not expose a method to set importance fields in outgoing messages.
904916	Automatic deletion of a DL when its last member is deleted is not working and leaves a DL with no member.
851888	Folder.getMessageCount() method returns a number that includes deleted messages.
885498	Searching of Public and Shared folders is not permitted. eMail Server 5.1 does not support searching of these folders.
886559	If a message window is opened from a search results screen, the previous/next buttons will return the previous/next message in the folder from which the message came from, not from the search result list.

Additional References

For information not covered in these Installation Guide, refer to the following sources:

• Oracle Unified Messaging Installation Guide

• Oracle Unified Messaging Developer's Guide

• Oracle Support Services web site at http://support.oracle.com