This is a text description of syndarch.gif.

This illustration describes the Oracle9iAS Syndication Server architecture.

Oracle9iAS Syndication Server represented as a large box contains within it, a square-shaped Subscription Manager box located in the lower left corner of the illustration, a rectangular-shaped Affiliates Manager box located next to the Subscription Manager box, and direcly beneath and touching the Affiliates Manager box, the Content Provider Adaptor box. A Message Manager box is located in the lower right corner of the illustration and is next to and to the right of the Affiliates Manager and Content Provider Adaptor boxes. A long rectangular Request Manager box is located directly above the Subscription Manager, Affiliates Manager, and Message Manager boxes and spans almost the entire width of the illustration. Directly above the Request Manager box is an identical-sized, long rectangular-shaped Transport Protocol Manager box that also spans the width of the illustration.

The Transport Protocol Manager communicates directly with Content Subscriber Applications, represented as a phrase at the top of the illustration that is above and outside the Oracle9iAS Syndication Server box. The two-way communication is shown with a connecting double-headed arrow.

The Subscription Manager profiles the subscriptions of each subscriber application by maintaining mappings between subscriptions and catalog offers. It communicates with only the Request Manager as indicated by a double-headed connecting arrow.

The Affiliates Manager manages all the profiles of the Content Providers who provide Content Resources, including its preferred Content Provider Adaptor implementation and all necessary parameters to this adaptor. The Affiliates Manager communicates with the Request Manager as indicated by a double-headed connecting arrow and with the Content Resources of content providers, which is represented as a phrase at the bottom of the illustration and outside of and below the entire Oracle9iAS Syndication Server box.

The Request Manager coordinates the handling of request messages from Content Subscriber Applications and response messages from Content Resources through the Transport Protocol Manager, utilizing subscription profile information maintained by the Subscription Manager. Double-headed arrows connect the Request Manager with the Transport Protocol Manager box, the Subscription Manager box, the Affiliates Manager box, and the Message Manager box.

The Transport Protocol Manager handles the content delivery to Content Subscriber Applications by transforming the XML-formated content to an appropriate subscriber application-specific markup language, such as HTTP/S and SMTP (extensible to FTP, or WAP). A double-headed arrow connects it to the Request Manager box.

Content Resources consist of three types of sources: file, database, and custom content. Each of these content source types is modeled as a minimal set of content provider operation modules as part of the Content Provider Adaptor (see ossdss.gif (Fig. 1-4) for a description of these content resources and content provider adaptors).