Convergence is a Web 2.0 client for Messaging Server, Calendar Server and Instant Messaging. Convergence includes the following high-level features:
- Ajax-based client with integrated email, calendar, address book, and instant messaging
- Drag and drop action (including drag and resize) often found in thick clients, for example, dragging and dropping messages between folders, dragging and dropping appointments, and so on
- Hi-performance, customizable interface
The Convergence client utilizes Ajax to provide a "rich" user experience. In addition, Convergence is designed to avoid potential complications brought in by plugins such as Flash. As such, Convergence focuses on using the capabilities common within the most popular types of web browsers, including Microsoft Internet Explorer, Mozilla Firefox, and Apple Safari.
This document contains the following sections:
Convergence is a feature-rich, interactive, high-performance next generation web-based communication client. Convergence is the Web 2.0 replacement for its previous web-based client, Sun Java System Communications Express. In Convergence, users experience a highly interactive, rich Internet application that provides integrated access to mail, calendar, address book, presence, and chat services. In addition, due to its highly customizable nature, Convergence is as much a development platform as it is a client.
The following figure shows a sample view of the Convergence interface.
Here's a brief look at Convergence functionality by component.
- Compose, Reply, Forward, and other typical email functions
- Spell check
- Search (subject, sender, and so on)
- Mail management: Deleting, Moving, Marking messages
- Typical calendaring functionality
- Create, edit, and delete events and tasks
- Check availability, schedule meetings with others
- Sharing calendars
- Common address book across services
- Create contacts and groups of contacts
- Corporate address book
- Import or export contact information (LDIF, vCard, CSV)
- Send email or schedule events directly from the address book
- Presence integrated with contacts
- Buddy lists, Chat capability
For more information about using the Convergence client, refer to the online help included with the product.
The following figure shows the Convergence components. The top area shows the mail, calendar, address book, and instant messaging components downloaded to the Convergence client. The middle area represents the Convergence server itself, deployed to the web container. The bottom area shows the dependencies that the Convergence server has on other Communications Suite services.
The Convergence service consists of the following core services:
- Service Proxies (Email, Calendar)
- XMPP over HTTP Gateway
- Address Book Service
- Authentication & Authorization
- SSO (Access Manager/Messaging SSO)
- Configuration management
- Basic Monitoring
The service proxies communicate by using various protocols to the Communications Suite services.
The logical architecture is a design that depicts the logical building blocks of the components and the infrastructure services needed to support them.
The logical architecture does not specify the actual hardware required to implement the deployment scenario. However, it helps you visualize the interrelationship among components, provides a basis for further analysis of use cases and identified usage patterns, and becomes the starting point for the deployment design phase.
The following figure shows the high-level logical architecture of a Convergence deployment.
If you deploy Convergence into an existing Communications Suite deployment, your existing two-tiered architecture remains unchanged with the exception of the Convergence server "sitting" between the Communications Suite servers and the clients on the internet. Architecturally, all that is required to add Convergence functionality is to add this server to your deployment.
This is the basic deployment architecture of Communications Suite. There might be some alterations required, but essentially it is a similar architecture for all deployments.
In a Convergence deployment that uses Instant Messaging, the Convergence server connects to the back-end Instant Messaging XMPP server by using httpbind on the Instant Messaging server port. See the iim_server.port parameter in the Instant Messaging server's iim.conf file. By default, iim_server.port is to 5269.
This differs from a standalone (non-Convergence) front-end/back-end Instant Messaging deployment, in which mail and calendar services access your Instant Messaging multiplexor front ends.
For an overview of security for the Convergence product, see Setting Up and Managing Convergence Security.
For other security information, see the following topics:
- Planning Calendar Server Security
- Planning Instant Messaging Security
- Planning Messaging Server Security
- Designing for Security
Use the following links to obtain further information about Convergence: