Java messaging services for web content
Web Content Manager supports for the notification of events such as item state changes, or services starting and stopping. These notifications can be delivered as messages to the Java messaging service.
About this task
- Item events:
- Item created
- Item updated
- Item moved
- Item deleted
- Syndication events:
- Starting
- Stopping
- Pre-render events:
- Starting
- Stopping
Procedure
Results
The create-wcm-jms-resources command creates a topic space that is 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 fills
up.
Note: There is a default limit of 50.000 messages per queue topic.
When that limit is reached messages cannot be stored anymore in the
queue and exceptions are logged in the Portal server log file.
For information about the default implementation of the WebSphere Application Server JMS implementation and choices of message providers, read Types of messaging providers.