Enable Java messaging services for web content

Web Content Manager can send notifications after events, including item state changes, or services starting and stopping. These notifications can be delivered as messages to the Java messaging service. Classes of events...

Item events:

• Item created
• Item updated
• Item moved
• Item deleted

Syndication events:

• Starting
• Stopping

Pre-render events:

• Starting
• Stopping

To enable Java messaging services for web content:

1. Configure the messaging services parameters in the WCM MessagingService service using the WAS console.

2. cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh create-wcm-jms-resources -DPortalAdminId=username -DPortalAdminPwd=foo -DuseRemoteEndPoints=true/false

   An administrator user name and password is not required if we have already specified the portal administrator username and password using the PortalAdminId and PortalAdminPwd settings in wkplc.properties.

   The "-DuseRemoteEndPoints" parameter is only used on clustered systems. If true, the task will use all node end points on the current setup. If set to "false", the task will use the end points of the current node.

3. Restart HCL WebSphere Portal.

Results

The create-wcm-jms-resources command creates a topic space named IWK.Topic.Space and the topics IWKTopics_Items, IWKTopics_PreRender and IWKTopics_Syndication in that space for the different events.

The messages are sent with no expiration time and need to be consumed, otherwise the queue will fill up.

There is a default limit of 50.000 messages per queue topic. Once that limit is reached messages cannot be stored anymore in the queue and exceptions will be logged in the Portal server log file.

See Types of messaging providers for information on the default implementation of the WAS JMS implementation and choices of message providers.

Parent Developing

Related tasks:

Set service configuration properties

Related reference:

Web Content Manager service configuration