Skip to main content link. Accesskey S
  • Anonymous
  • Log on
  • Help
  • IBM logo
  • WebSphere Portal Family wiki
  • All Wikis
  • Home
  • Community Articles
  • Product Documentation
  • Learning Center


Search

Advanced Search

Categories

Tag Cloud

  • 6.0
  • 6.1
  • 6.1.0.1
  • 6.1.5
  • 7.0
  • 7.0.0.2
  • 8.0
  • actions
  • administrator
  • authoring
  • Banking template
  • best practices
  • blogs
  • builder
  • building a site
  • caching
  • catalog
  • Clickstream Engine
  • clusters
  • ConfigEngine tasks
  • content
  • customizing
  • databases
  • demo
  • deployment
  • deployment scenario
  • developer
  • developing
  • device class
  • elements
  • examples
  • Express
  • feature set
  • fix pack 2
  • Government to Business template
  • info center
  • information center
  • installation
  • installing
  • LDAP
  • Learning
  • libraries
  • LikeMinds Recommendation Engines
  • logging
  • mentors
  • message catalog
  • messages
  • migration
  • mobile
  • mobile devices
  • mobile experience
  • mobile experience 8.0
  • mobile theme
  • mobile webkit
  • MPA
  • multiplatform
  • pages
  • performance
  • personalization
  • planning
  • portal
  • Portal 6.1
  • Portal 8 theme
  • portlets
  • product doc
  • product documentation
  • projects
  • properties
  • Redbooks
  • Redbooks Wiki
  • remember me cookie
  • resources
  • REST
  • Retail Vendor template
  • rules
  • samples
  • search
  • security
  • sifters
  • sites
  • solutions catalog
  • syndication
  • test infrastructure
  • theme
  • theme optimization
  • topologies
  • troubleshooting
  • tutorials on personalization
  • video
  • wcm
  • web content
  • webkit
  • WebSphere Portal
  • WebSphere Portlet Factory
  • wikis
  • workflows
  • worksheet
  • XML configuration interface
  • z/os
  • zos
InformationInformation
You are currently viewing machine translated content. IBM translation might be available. Click IBM Translated Product Documentation to see what is available.X


Home > IBM Redbooks: Building a Web site using Lotus Web Content Management 6.1 > 5.1.2.3 Monitoring Syndication Progress
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

5.1.2.3 Monitoring Syndication Progress 

expanded Abstract
collapsed Abstract
No abstract provided.
Untitled Document

Table of contents | Next | Previous

Monitoring Syndication Progress

After the syndication relationship was setup, we monitored the progress of the data replication between syndicators and subscribers for details such as whether syndication was successful, when it occurred, and how many changes were included.

 

Monitor Syndicator/Subscriber Views

We started monitoring the syndication process by observing the Syndicator and Subscriber views. The screenshots below illustrates the new status visible in the Syndicator and Subscriber views.

 


Figure: Web Content Subscribers View – Status Active

 


Figure: Web Content Syndicators View – Status Active

 


The table below provides details about the various different status that are possible and provides a brief description –

Status

Description

Idle

The syndication process is idle.

Pending

The syndicator has received a request, but it has yet to initiate it.

Queued

The syndicator has sent a request to the syndication application, but syndication is not yet active. This state will not occur if the subscriber has initiated syndication. The status remains as Idle until syndication begins and the status then changes to Active.

Active

The syndication process is active.

Disabled

The syndication process is disabled. If syndication was already in process prior to being disabled, the status can be a combination of Disabled and Pending, Queued, or Active.

 


Once the syndication process has completed, the Syndicator and Subscriber views displayed the idle status as illustrated in the screenshots below.

 


Figure: Web Content Subscribers View – Status Idle

 


Figure: Web Content Syndicators View – Status Idle

 

Monitor the Synicator/Subscriber Status Report

We used the Last Update column entry links on the syndicator and subscriber to review the Syndicator and Subscriber status reports as illustrated in the screenshots provided below.



Figure: Syndicator Status Report

 


Figure: Subscriber Status Report

The following table describes the information available in the Syndicator and Subscriber status reports.

 

Field Name

Description

Syndicator and subscriber ID, name, and URL

This information provides identifying details about the syndicator and subscriber that are engaged in syndication.

Enabled

This field indicates whether syndication is enabled for the syndicator or subscriber.

Type

This field indicates whether partial or full syndication occurred. With partial syndication, only those items that have been updated since the last syndication are replicated. Full syndication replicates all items, regardless of whether they have been updated since the last syndication.

Started and finished time stamps

These fields provide the date and time when syndication started and finished.

Result

This field indicates whether syndication was successful.

Detail

This field provides detailed information about the syndication result, including any errors that occurred during syndication.

Updates sent

This field indicates the number of items that have been updated. This includes new items that have been added and existing items that have been updated.

Removes sent

This field indicates the number of items that have been removed.

Old state and new state for subscriber or syndicator

This field displays state information for a syndicator or subscriber before and after syndication occurred. This information is provided for the opposite member of the syndication relationship, so for example if you are viewing syndication results for a syndicator, the old and new states for the subscriber are displayed.

If successful, this field indicates the actual change of status. If syndication has failed, this indicates what should have been the change of status.

Note: The syndication state only displays a list of item gatherer ids and the current state. It is designed to be used as a diagnostic tool when troubleshooting syndication.

Update summary

This lists:

  • the number of updates sent
  • the number of successful updates
  • the number of failed updated

Note: The number of updates listed here does not directly relate to the number of items updated. For example, if you create a library and then create a taxonomy item in the library, you have updated a single item. However in the Update summary this will be displayed as three updates; one for the library, one for the new taxonomy and one for its version.

Update details

This section provides additional information to the Update summary section. It lists:

  • the number of items that didn't require an update because they have already been updated
  • the number of new items created
  • the number of items updated
  • the number of failed updates
  • the number of items that didn't require removal because they have already been removed
  • the number of items removed
  • the number of failed removals

 

Monitor the Subscriber directory

Once Syndication has started, you can monitor its progress by looking at the <WP_Profile>\PortalServer\wcm\ilwwcm\system\subscriber\<SUBSCRIBER-ICE- ID> directory on the Subscriber server.

As items are being retrieved from the Syndicator, this directory will grow. After all items are retrieved, they will start to be saved within the Subscribers repository. As each item is saved in the repository, its corresponding file entry will be removed from the above directory.

The screenshots provide below illustrates this.

 


Figure: Subscribers File System Directory during Syndication

 

 


Figure: Subscribers File System Directory after Syndication

 

Files can remain in the subscriber directory for any of the following reasons:

  • A failed attempt to save to the database due to a software error
  • Syndication is interrupted or killed before it completes writing to the database
  • WCM is not handling the syndication changes properly

 

Monitor the logs

Once the syndication process is completed, we noticed the following entries in the SystemOut.log for the Syndicator and the Subscriber

Syndicator logs

[ 9/1/08 1:42:55:078 EDT] 00000055 SyndicatorTas I IWKSY1028X: Subscription: IWKSY1096X: [IceId: <8efd48804b09fd3ab22efe116174738a> Current State : <d525eb804a9086648cfdae756e4fc596:1219699739265>] updated successfully.

Subscriber logs

[ 9/1/08 1:43:45:500 EDT] 00000041 SubscriberTas I IWKSY1034X: Finished processing update for subscription: IWKSY1096X: [IceId: <8efd48804b09fd3ab22efe116174738a> Current State : <ICE-INITIAL>]


expanded Article information
collapsed Article information
Category:
IBM Redbooks: Building a Web site using Lotus Web Content Management 6.1
Tags:
wcm

This Version: Version 4 October 22, 2009 11:46:24 AM by Amanda J Bauman  IBMer

expanded Attachments (0)
collapsed Attachments (0)

 


expanded Versions (2)
collapsed Versions (2)
Version Comparison     
Version Date Changed by               Summary of changes
This version (4) Oct 22, 2009 11:46:24 AM Amanda J Bauman  
2 Nov 5, 2008 1:17:00 PM John Bergland  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedSubscribe to RSSHelpAbout
  • All Lotus and WebSphere Portal wikis
  • IBM developerWorks
  • IBM Software support
  • IBM Social Business User Experience Blog
  • IBMSocialBizUX on Twitter
  • IBMSocialBizUX on Facebook
  • Lotus product forums
  • IBM Social Business UX blog
  • IBM Collaboration Solutions
  • Recently added feedRecently added
  • Recently edited feedRecently edited
  • Recently added comments feedRecently Added Comments
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Contact IBM
  • IBM Terms of use
  • Wiki terms of use