1
Overview of the Unified Messaging SDK

This chapter introduces the Unified Messaging Server Developer Kit (SDK) to the HTML developer. This chapter contains the following topics:

• Introduction to Unified Messaging

• Working with the Unified Messaging SDK

• System Requirements

Introduction to Unified Messaging

Today's business professional receives and sends messages via multiple sources: e-mail, voice mail, facsimiles, and short messages displayed on pagers. The challenge is to keep up with all these messages and quickly recognize high priority items that require immediate action. Oracle provides the solution: Unified Messaging, which integrates messages from multiple sources into a single "inbox." Unified Messaging not only consolidates all messages into a single interface, it also frees the business professional to focus on making decisions, rather than on keeping track of multiple telephone numbers, passwords, and access codes.

Unified Messaging from the Developer's Perspective

Unified Messaging provides an application development environment that includes Java packages, classes, and methods. These classes allow both front-end customization of the GUI and back-end customization of Unified Messaging functions.

The Unified Messaging SDK provides resources for both HTML developers and Java developers:

• HTML developers can use a sample client by modifying HTML pages.

• Java developers can write Java programs to extend the Unified Messaging SDK classes.

Unified Messaging Architecture

The Unified Messaging system architecture includes the following three tiers.

• Tier 1: A thin client, such as a Web browser

• Tier 2: An application layer, consisting of the Unified Messaging SDK and its environment:
  • A Unified Messaging SDK that runs in a JSP environment.

  • A Web server with JSP support enabled.

  • (Optional) RealAudio that provides audio streaming capabilities

• Tier 3: The data store layer, including:
  • An Oracle database that stores Unified Messaging information

  • The Oracle internet Directory (OiD) that stores directory information

  • The Oracle eMail Server

  • The voice mail server and message store connection

  • The facsimile server and message store connection

  • The Short Message Service (SMS) gateway

  • The Operational Support Systems (OSS) interfaces

  • (Optional) Other IMAP4-compliant e-mail message stores

Unified Messaging Components

The Oracle Unified Messaging provides components related to Tier 2 and Tier 3. Oracle requires only that the user have a standard browser (a Real Audio plugin is optional). The sample application is based upon Java Server Pages.

• Tier 1: The graphical user interface of the Unified Messaging sample application, displayed in a Web browser. The HTML interface, generated dynamically, combining information from the database and information supplied in customized JSP templates.

• Tier 2: The Apache listener and JServ engine.

• Tier 3: Oracle eMail Server and an SMS gateway.

To complete the Unified Messaging system, Unified Messaging includes the interfaces used to connect all message sources:

• Alternate e-mail servers

• Voice mail servers

• Facsimile servers

• OSS system

Working with the Unified Messaging SDK

The Unified Messaging SDK runs in a programming environment that includes the following main components:

• The Unified Messaging Applications Programming Interface (Unified Messaging API)

• Apache and JServ

• Unified Messaging sample application

Unified Messaging API

The Unified Messaging API is a set of classes and methods, written in Java, used to implement the Unified Messaging system. Application developers use the standard component and object model to create their own custom messaging solution.

Sample Application

The sample application included, provides Web access to the Unified Messaging system through browsers

The sample application consists of a set of screens that give users access to standard Unified Messaging functions, including:

• E-mail access

• Directory access

• Audio and facsimile conversion (g726 to WAV or RealAudio, TIFF to GIF)

• SMS connections

• Administrative functions

The application can be accessed at the following locations after installation of the "UMSDK Application" component of the Unified Messaging SDK:

http://<hostname:port>/um/login/jsp

System Requirements

This section describes three types of requirements for using Unified Messaging:

• Environment requirements

• Requirements for customizing the Unified Messaging GUI

• Knowledge requirements for HTML developers

Environment Requirements

The following components are required for Unified Messaging to function on all platforms:

• Oracle database

• Web server with JSP support

• Oracle eMail Server

• Oracle Internet Directory

• A Web browser

• A development tool

You do not need a special development tool to develop HTML-based applications. Use a text editor or HTML editor or, if you prefer, a Web authoring tool to create and maintain the template files that make up your application. No such special development environments or tools are provided with the Unified Messaging SDK.

Requirements for Customizing the Unified Messaging GUI

To customize the sample applications included with the Unified Messaging SDK you must have access to the following:

• Oracle database

• Web server administration authority

• An account on an Oracle eMail Server

The sample applications run in the following Web browsers:

• Netscape Navigator 4.5x

• Internet Explorer 5.x

Knowledge Requirements

HTML application developers generally work with the provided Unified Messaging API to create applications. The simplest way to create applications is to modify the HTML templates provided in the Unified Messaging sample application.

This document assumes the HTML application developer has an understanding of HTML, including form syntax. It also assumes a knowledge of general HTTP concepts including the practical use of Web browsers, Web servers, and URLs. While knowledge of browser scripting languages like JavaScript is not required to develop simple HTML applications, such knowledge will assist in developing enterprise-quality HTML applications and in understanding the Unified Messaging GUI. Java programming knowledge is not required to program HTML applications, but an understanding of general object-oriented programming concepts and the ability to read Javadoc reference information is necessary.