Configure Syndication

 

+ Search Tips   |   Advanced Search

 

Contents

  1. Overview
  2. Syndication in a decentralized, multiple author environment
  3. Using partial or full updates
  4. Set the recurring task interval
  5. Defining the live server as a Subscriber only
  6. Using port 9080
  7. Disabling Syndication
  8. Default Encoding

 

Overview

Syndication can affect performance if large amounts of data are syndicated. You can define various settings to reduce the impact on performance.

As an IWWCM environment can be accessed remotely, the Site Administrator can create the relationship between Syndicators and Subscribers at the same time on a single computer. They do not require physical access to either Server.

Take things slowly. If you are configuring Syndication remotely, be careful not to lose track of where you are. As the information you are entering for both Syndicators and Subscribers is similar, it is easy to mix them up.

 

Syndication in a decentralized, multiple author environment

In a decentralized, multiple author environment there can limitations when trying to merge changes from different authors using different servers.

For example:

  1. User 1 edits Content A on Server A.

  2. User 2 edits Content A on Server B.

  3. User 2 saves Content A after User 1 saves Content A, but before Syndication occurs.

  4. The changes made last are the ones that are saved. Therefore, the changes made to Content A by User 1 will be overwritten by the changes made by User 2.

To minimize the impact of this limitation, modify deployment.itemChangedTaskDelay in aptrixjpe.properties to shorten the time needed between edits to start Syndication. Because Syndication is an expensive operation when Syndicating large amounts of data, modification of this property should be carefully considered and tested.

 

Using partial or full updates

You can determine whether Syndication will provide partial or full updates.

  • A partial update occurs when only those items that have changed are syndicated.
  • A full update occurs when all items on the Syndicator are syndicated to the Subscriber. A full update consists of changed and unchanged items.

The Information and Content Exchange (ICE) protocol allows for partial updates, and due to the amount and size of data that a Web site could contain, a partial update is extremely important. When Syndication runs automatically, only changed items are syndicated, which is a partial update of the Web site.

Since automatic Syndication occurs only when the Changed Task detects no changes in the item gatherer, you might need to wait for an off-peak period Syndication to occur. If you require immediate Syndication, you can manually syndicate partial updates by clicking the Syndicator Update button in either the Syndicator or Subscriber item windows.

If you require a full update of the Subscriber, click the Syndicator Rebuild button in either the Syndicator or Subscriber item windows. You might need a full update if the data store on the Subscriber is lost or corrupted.

 

Set the recurring task interval

The task that detects if the item gatherer has registered changed items runs every 30 seconds by default. When it detects items have changed in the past 30 seconds, Syndication does not occur. When the task detects that no items have changed in the past 30 seconds but the item gatherer has registered changed items awaiting Syndication, Syndication does occur. The likelihood of Syndication occurring increases with a smaller interval. The longer the interval, the longer the task will take to detect when the item gatherer has not registered new changed items and, therefore, the less often Syndication will occur.

If you change the interval to 6 hours, the server needs to wait for at least 6 hours before Syndication can run. If one change occurs during the 6-hour interval, Syndication cannot run for at least 12 hours. A large interval might result in changes never being syndicated, for example from the development server to the live server. The following parameter in the aptrixjpe.properties file defines the recurring task interval: 

deployment.itemChangedTaskDelay=30

 

Defining the live server as a Subscriber only

A Syndicator server contains the two item gatherers and the recurring task, which impact server performance when they run. A Subscriber server does not contain the item gatherers and the recurring task does not run, which gives greater performance. Live servers should only be subscribers. The following parameter in the aptrixjpe.properties file defines the server as a Subscriber only: 

deployment.subscriberOnly=True

 

Using port 9080

Syndication uses the Information and Content Exchange (ICE) protocol to transmit data from the Syndicator to the Subscriber, sending XML files over HTTP. The XML files might be fairly large, which might cause issues when posting through the IBM HTTP server. To avoid this issue, use the appserver port, which, for WebSphere Application Server, is 9080. The following parameters in the aptrixjpe.properties file, which include the port tag, define the Syndication modules: 

  deployment.itemDispatcherUrl=http://[HOST]:[PORT]/wps/wcm/connect?MOD=ItemDispatcher
  deployment.syndicatorUrl=http://[HOST]:[PORT]/wps/wcm/connect?MOD=Synd
  deployment.subscriberUrl=http://[HOST]:[PORT]/wps/wcm/connect?MOD=Subs

 

Disable Syndication

Syndication can be disabled on either the Syndicator or the Subscriber. Disable Syndication if you plan to make a big change to your Web site on the development server and need to first ensure that the change is acceptable. Once the change is accepted enable Syndication.

The Syndicator and Subscriber item windows contain an Enabled checkbox. If you clear the checkbox, all requests for full or partial Syndication updates are disabled, even if the request is manual.

 

Default Encoding

The default encoding of an IWWCM site can be set in the DefaultEncoding setting in the connect.cfg file. Syndicators and Subscribers must use the same default encoding. Otherwise, content may be corrupted when Syndication occurs.

Parent topic: Syndication

IBM Workplace Web Content Management - V5.1.0.1 -

 

Workplace Web Content Management is a trademark of the IBM Corporation in the United States, other countries, or both.

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.