This is a text description of syndarch.gif.
This illustration illustrates the Oracle Syndication Server architecture.
Oracle Syndication Server represented as a large box contains within it a square-shaped Subscription Manager box located in the lower left side, a rectangular-shaped Affiliates Manager box located in the lower right side, a rectangular Syndication Manager box located above the Subscription Manager and Affiliates Manager boxes and spanning the width of the Oracle Syndication Server box, and a rectangular-shaped Transport Protocol Manager box located above the Syndication Manager box, which also spans the width of the Oracle Syndication Server box. The Transport Protocol Manager communicates directly with content subscribers, represented as a phrase above and outside Oracle Syndication Server box and this two-way communication is shown with a connecting double-headed arrow.
The subscription manager profiles the subscriptions of each subscriber by maintaining mappings between subscriptions and catalog offers. It communicates with only the Syndication Manager as indicated by a double-headed connecting arrow.
The affiliates manager manages all the profiles of the content providers, including its preferred content provider adaptor implementation and all necessary parameters to this adaptor. It communicates with the Syndication Manager as indicated by a double-headed connecting arrow and with the Dynamic Services Framework, which is represented as a box outside of and below the Syndication Server box.
The Syndication Manager coordinates the handling of request messages from content subscribers and response messages from content providers through the Transport Protocol Manager, utilizing subscription profile information maintained by the Subscription Manager. Double-headed arrows connect it with the Transport Protocol Manager box, the Subscription Manager box, and the Affiliates Manager box.
The Transport Protocol Manager handles the content delivery to content subscribers by transforming the XML-formated content to an appropriate subscriber-specific markup language, such as HTTP/S, SMTP or WAP. A double-headed arrow connects it to the Syndication Manager box.
Content providers consist of three types of sources: file, database, and Web. Each of these content source types is modeled as a minimal set of services in the Dynamic Services Framework. A Content Provider Developer's kit is provided to let you extend support for other types of content providers and register these as new services with the Dynamic Services Framework.