Thursday, December 17, 2009

JCR Explorer and XPath

Been running a lot of XPath queries in JCR explorer these days, trying to fix some syndication issues.

For example, getting error...

Could not save item with id DepRef(id:121212121 type: nonDraft:true draft:false purged:false parentId:919191919 timeStamp:123 stateUpdate: false versions:null moved: false) because it could not find its parent.

...means parent uuid on subscriber does not match parent uuid on syndicator. To verify, in JCR Explorer, run the following queries on both systems...

//element(*, ibmcontentwcm:siteArea)[@jcr:uuid = '121212121']
//element(*, ibmcontentwcm:siteArea)[@jcr:uuid = '919191919']

You will undoubtedly find both uuids on syndicator, but not subscriber. This will be the case even if site areas show as existing on both machines from within the authoring portlet on the subscriber.

One way to fix...

1. Delete site area child and parent on subscriber
2. Edit site area on syndicator and then save, to give item a fresh time stamp.
3. Re-syndicate

I will be adding some more syndication solutions based on the questions I have received.

Sunday, December 13, 2009

Using the Member fixer for IWWCM


Use the member fixer tool to check whether any Member Manager users or groups referenced in IWWCM items have been renamed or deleted.

The member fixer tool will not work if there are any locked items in a Web content library.

For a large number of items, use the WAS Admin console to increase the session timeout setting of the server...

Application Servers | WebSphere_Portal | Container Settings | Web Container Settings | Session Management

Run the Member Fixer Module if any of the following conditions have occurred:

* A user or group has been permanently removed from WebSphere Portal.

* If WebSphere Portal security has been enabled or disabled (or Syndicated from another server with different WebSphere Portal security settings)

* If the LDAP structure has been modified

* If you have moved your data to a Portal server and WMM is configured to use its default auto-generated ID (rather than a unique attribute from each users LDAP record).

* A user or group has been removed and then re-added to WebSphere Portal, and WMM is configured to use its default auto-generated ID (rather than a unique attribute from each users LDAP record).

Note that if the Principal Information Cache is enabled (available with PK32457 but not enabled by default), then run the Member Cache Manager Module as described in the iFix read-me before running the Member Fixer


1. To view a report of Member Manager users or groups, using a browser, open the member fixer tool...


2. If there have been changes to Member Manager users and groups, update the items that reference them. Open the following URL in the browser:


3. If the member fixer tool indicates that certain mismatched member conditions exist, enter the specified URL to correct the conditions.

For nonexistent users or groups have alternate distinguished names (DNs) available.

* To update the items that reference the nonexistent users or groups:


* To remove the members that reference the users or groups:


For Users or groups have been found with mismatched external IDs in Member Manager.

* To update the external IDs in Member Manager with correct external IDs:


To remove those users and groups with mismatched external IDs:


These URL options can be combined when the conditions occur at the same time. For example, if alternate DNs are available for nonexistent users and groups and there are mismatched external IDs in Member Manager, we might use the following URL:


Cannot locate Presentation Template for Template

This was a request from a user so here's the error and its solution (encountered during search) :

[15/11/08 3:35:38:180 SAST] 0000009c HttpConnectio 3 10: http://host/wps/wcm/myconnect/library/sitename/site area/image.jpg request sent
[15/11/08 3:35:38:180 SAST] 0000009c Node 1 40: checkNodeFlags: res= false, flag= NODE_FLAG_UTF_8_CONVERSION_FAILED
[12/11/09 3:35:38:346 SAST] 00000078 RendererModul W IWKPL1453X: Exception occured while processing request: com.aptrix.pluto.renderer.BadPathInfoException:
IWKPL1224X: Cannot locate Presentation Template for Template {bf06d0804b429520bae8fbb461ad4639, com.aptrix.pluto.presentation.Template, Authoring-Template-File-Resource, }


This error indicates that an authoring template was added to a site area but it wasn't mapped to a presentation template.IWWCM can not map it thus wont be able to render it.Use the location given, http://host/wps/wcm/myconnect/library/sitename/site area/image.jpg and navigate to the site area.

Steps to follow :

1. Select the site area
2. Select edit (Edit the site area)
3. Select template mapping
4. Map the authoring template to a presentation template
5. Save your changes

Your error has now been resolved.

Render content title from within a Menu Component

When used in the "Design for each menu search result:" section of a Menu Component, this tag will render the title of the current content item being iterated over:

Back to Top

This is very useful when using dynamic menus o display content.

Link to portal page and a WCM Site

This piece of code shows an example for how to link to a specific portal page and a WCM Site. The portal page is defined by a friendly URL mapping in WPS Remember that URL mapping is an option to you as an administrator.. In this case that URL mapping is called View. The View page is identified in the tag as the portalTarget. The portal page must have a WCM content display portlet that is configured as a listener.

<a href='context="selected" name="content/op" type="site" mode="portal" portalTarget="View"/>'>Office Productsa>

Note: If successfully configured, this tag should automatically generate an id attribute on save.

Tuesday, December 8, 2009

Talking the Talk

These common terms are used when describing IBM Lotus WCM


Elements either store Web content or generate

web content. Elements do not exist as free standing items. You store elements in "container" items.


Items can be considered as "files" or "documents"
and are used to store Web content, metadata and access control information.
There are four item-types:

Container items

  • Sites
  • site areas

  • content items
  • components

Represent different sections of a site framework.
Template items

  • Authoring templates
  • Presentation templates

An authoring templates defines:

  • which data entry fields are visible on a content item form.
  • the default values for each setting and field on a content item form.

A presentation template defines:

  • The layout of elements and components that are displayed on a Web page.
  • The default properties of a Web page.

Profile items

  • Taxonomies
  • categories

You use categories to profile certain item-types, such
as content-items. A category refers to the subject matter of your content.
You group categories within taxonomies.

Workflow items

  • Workflows
  • workflow stages
  • workflow actions

You use

workflows to control the access to, verification and eventual approval of WCM items.

When creating a workflow, you select a set of workflow stages. Workflow actions are executed upon entering or exiting a workflow stage.

Site framework

A site framework is a similar concept

to the "site map" of a traditional Web site. Whereas a site map is based on a directory structure or the links between pages in a Web site, a site framework
consists of a set of WCM items.
Each site framework consists of a single site under which a set of site areas
and content items are grouped.

Template maps

When a content item is rendered, the presentation template used to display the content item is determined by the current template map. A template map is defined in a site or site area and consists of a pairing of an authoring template with a presentation template.


You use the profiling features of Web

Content Management to group content items into different types of content.
Content items are profiled using categories or keywords, and by locating content
items under different sections of a site framework.


A workflow is used to manage the verification process of WCM items.An item is published only when it has been approved in every stage of a workflow.