Enable Java messaging services for web content

Web Content Manager provides support 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.

There are three classes of events that can be delivered as messages to the Java messaging service:

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 IBM WAS administration console.

2. Run the following command from the WP_PROFILE/ConfigEngine:
   Windows™
   ConfigEngine.bat create-wcm-jms-resources -DPortalAdminId=username -DPortalAdminPwd=foo -DuseRemoteEndPoints=true/false

   UNIX™

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

   i

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

   An administrator user name and password is not required if you 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 set to 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 WebSphere Portal.

Parent

Developing

Previous

Set service configuration properties

Related reference

Web Content Management configuration services

December 14, 2011

   

 

Apr 1, 2011 1:26:17 PM

});

+

Search Tips   |   Advanced Search