Syndication tuning
Syndication interval
The syndication interval controls the frequency of syndication while automatic syndication is enabled and can be used by administrators to put a cap on how often syndication occurs.
Automatic syndication is enabled by default when IBM WebSphere Portal is installed.
General guidelines...
Interval Recommended 30 secs - 10 mins Environments that require frequent replication, such as authoring server to...
- staging server
- test server
- distributed authoring server
10 mins - 2 hrs Staging servers to delivery servers.
Live and All item syndication
- Live item syndication:
- Only published, expired and non-workflowed items are syndicated. Draft items are not syndicated.
Used when syndicating to a staging or delivery server.
- All Item syndication:
- All published, expired and non-workflowed items are syndicated, as well as versions, draft, and deleted items. All item syndication is used when syndicating between servers within an authoring environment.
Manual syndication
It is not necessary to wait for the syndication interval to elapse in order to perform syndication. Manual syndication can be used at any time to cause syndication to occur immediately. There are different ways to take advantage of manual syndication:
- Use manual syndication in conjunction with the syndication interval to provide flexibility. For example, if you are using an increased syndication interval to optimize performance between servers, you can still perform manual syndication when update content without waiting for the next syndication.
- If you require complete control of when syndication occurs, use manual syndication as the only means of performing syndication. For this approach, disable automatic syndication so that the syndication interval setting is ignored.
Publish and expire dates
Because the syndication interval is not based on a scheduled time of the day, it is not suitable for setting up syndication to run during off-peak times. The publish date and expire date are the preferred methods for doing this.
The publish date for each content item specifies the date and time when the content should be published to a Web site. After a content item is approved and the publish date is reached, the content item is queued for syndication according to the next syndication interval. By using the publish date, you can delay the publishing of content, effectively delaying its syndication. For example, if you are using a short syndication interval to ensure timely replication of most content, you can delay the syndication of less urgent content through the publish date for that content.
The expire date specifies the date and time when the content item should be removed from a Web site. As with the publish date, use the expire date to cause the syndication activity associated with removing the content to occur at a time when other syndication activity is less intensive.
For more information on the publish and expire dates in the workflow process, refer to Workflow status.
Parent topic
Syndication