3
Syndication Server Development

This chapter describes the development flow for setting up a content syndication system following the installation, deployment, and configuration of Oracle9iAS Syndication Server. The tasks include:

• Creating Additional Required Packages (see Section 3.1)

• Registering subscriber applications (see Section 3.2.1)

• Registering content providers (see Section 3.2.2)

3.1 Creating Additional Required Packages

This section describes two additional types of required packages that you must create manually and place as a zip file in either a local file directory or in a remote file location that is accessible using an HTTP URL.

• Content provider description package

  Before you can register a content provider, you must manually create this package.

• Subscriber application description package

  Before you can register a subscriber application, you must manually create this subscriber application description package.

Section 3.1.1 and Section 3.1.2 describe each of these packages in greater detail.

3.1.1 Content Provider Description Package

This section describes the content provider description package that is required in order to register a content provider. The content description package contains the name, brief description of the content provider, contact e-mail address, telephone number, postal address, and the location of the business agreement document. This package must be manually created. Instructions for creating these packages are described in this section. The Syndication Server Manager for Oracle Enterprise Manager will support automatically creating this package in a future release.

An example content provider description package (eShop_CP.zip) is supplied with Syndication Server. The contents of the manifest file /oracle/syndication/server/cp_eshop.xml points to the following cp_eshop.xml file, whose content is shown in the following example:

<?xml version="1.0"?>
<CONTENT_PROVIDER xmlns="http://www.oracle.com/ds/2000/SERVICE_DESCRIPTOR/CONTENT_
PROVIDER">
   <NAME>Sample Affiliate</NAME>
   <DESCRIPTION>Sample Affiliate</DESCRIPTION>
   <EMAIL>[e-mail]</EMAIL>
   <PHONE>[phone]</PHONE>
   <ADDRESS>one oracle drive</ADDRESS>
   <BUSINESS_TERM>/oracle/syndication/server/bizTerm.pdf</BUSINESS_TERM>
</CONTENT_PROVIDER>

For each content provider that you want to register as a content provider, you must create a content provider package zip file, exactly as shown in this sample content provider package zip file.

3.1.2 Subscriber Application Description Package

This section describes the subscriber application description package that is required before you can register a subscriber application. The subscriber application description package contains the name, brief description of the subscriber application, contact e-mail address, telephone number, postal address, and the location of the default URL for the subscriber application. This package must be manually created. The Syndication Server Manager for Oracle Enterprise Manager will support automatically creating this package in a future release.

An example subscriber application description package (foo_sub.zip) is supplied with Syndication Server. The contents of the manifest file /oracle/syndication/server/sub_foo.xml points to the following sub_foo.xml file, whose content is shown in the following example:

<?xml version="1.0"?>
<SUBSCRIBER xmlns="http://www.oracle.com/ds/2000/SERVICE_DESCRIPTOR/SUBSCRIBER" >
   <NAME>Sample Subscriber</NAME>
   <DESCRIPTION>Sample Subscriber</DESCRIPTION>
   <EMAIL>[e-mail]</EMAIL>
   <PHONE>[phone]</PHONE>
   <ADDRESS>one oracle drive</ADDRESS>
   <DEFAULT_URL>http://localhost/syndclient/OSC</DEFAULT_URL>
</SUBSCRIBER>

For each subscriber application that you want to register as a subscriber, you must create a subscriber application description package zip file, exactly as shown in this sample subscriber application description package zip file.

3.2 Registering Subscriber Applications and Content Providers

After creating the content provider description package described in Section 3.1.1 and the subscriber application description package described in Section 3.1.2, you can begin to register and manage subscriber applications and content providers.

3.2.1 Registering and Managing Subscriber Applications

See Section 4.1.1 for information on how to register and manage subscriber applications using the Manage Subscribers management task that is part of the Syndication Server Manager for OEM administration tool.

3.2.2 Registering and Managing Content Providers

See Section 4.1.3 for information on how to register and manage content providers using the Manage Content Providers management task that is part of the Syndication Server Manager for OEM administration tool.