Distributing Content Using HTTP

Use

Transferring content using HTTP enables the automatic updating of content at regular intervals.

Process

All work steps are carried out in the Content Exchange iViews Syndicator and Subscriber.

The syndicator has to give the subscriber a local URL, user, and password. For more information, see Creating a User for Fetching the Catalog and Pull Actions .

The subscriber enters this information when creating the syndicator in the subscriber system. The user and password are needed to fetch the catalog and to transfer content using the pull method.
The syndicator creates one or more offers.

This involves defining the following data:
- Components
  
  An offer can consist of one or more components. A component is a folder in a repository with all its subfolders and the documents contained therein. You can define filters to restrict the data to be transmitted.
- Delivery rules
  
  You can define one or more delivery rules for an offer. A delivery rule determines the delivery method and can also define a schedule for the delivery.
  
  The following delivery methods are available:
  - Push
    
    This method means that the content delivery is initiated by the syndicator.
  - Pull
    
    This method means that the content delivery is initiated by the subscriber.
    
    You can use the schedule for the delivery to define a start date, end date, and an update interval.
    
    Note
    
    The ICE standard also allows for a minimum and maximum number of updates. These attributes are not supported at the moment.
- Transfer volumes
  
  To reduce the size of the packages to be transmitted, specify a maximum file size. Files larger than this value are not contained in the ICE package. Instead, the subscriber receives a URL that the subscriber system can use to download the documents in question automatically.
The subscriber logs on to the syndicator system and requests the catalog.

The catalog contains a list of all offers of the syndicator in question. The subscriber is automatically registered with the syndicator's system.
The subscriber accepts an offer, thereby creating a subscription.

The subscriber enters a target folder in one of his or her repositories. The content is transferred to this folder.

The ICE subscriber implemented by SAP provides its own delivery rule. If the syndicator offers a choice of delivery rules (for example, push or pull), the subscriber has to select one of the options when creating the subscription. A subscription only has one delivery rule in SAP Enterprise Portal.

Note

If the subscriber wants to use the push method, he or she must define a user and password that the syndicator can use to access the subscriber system. For more information, see Creating a User for Push Actions .

The syndicator enters this user in the properties of the subscriber on the Configuring Push Actions tab page.

Result

The subscribed content is delivered and updated as defined in the delivery rules.

More Information

Syndicator Tasks

Subscriber Tasks