WebSphere Dashboard Framework - Scheduling alerts in a WebSphere Portal server cluster

Added by Rob Flynn | Edited by IBM contributor

IBM contributor

Rob Flynn on January 5, 2010 | Version 9

Edit
More Actions ▼

Rate this article 1 stars

Rate this article 2 stars

Rate this article 3 stars

Rate this article 4 stars

Rate this article 5 stars

expanded

No abstract provided.

Tags: Alerts, Scheduling, Cluster

Scheduling alerts in a vertical cluster

Create a Dashboard project the includes the Alerts Scheduler feature set. Develop other dashboard portlets in this project.
In Eclipse, disable the automatic scheduler startup for the project:
Open the file WEB-INF/config/scheduler/scheduler.properties and change the value for the entry "bowstreet.util.scheduler.start" from true to false. By default its value is true.
Deploy the WAR to the cluster.
Open the Administrative console on the deployment manager, enter your cluster members page.
Determine which cluster member is the "scheduler" member, where the Alerts Scheduler runs. Start all other members except the "scheduler" member.
Go to Your WAR directory\WEB-INF\config\scheduler, open scheduler.properties and change the value for the entry "bowstreet.util.scheduler.start" from false to true.
Enter your cluster members page and start the "scheduler" member.
Go to Your WAR directory\WEB-INF\config\scheduler, open scheduler.properties, and change the value for the entry "bowstreet.util.scheduler.start" from true to false. This setting prevents you from starting the scheduler in other cluster members accidentally.

Scheduling alerts in a horizontal cluster

Create a Dashboard project the includes the Alerts Scheduler feature set. Develop other dashboard portlets in this project.
Open the file WEB-INF/config/scheduler/scheduler.properties and change the value for the entry "bowstreet.util.scheduler.start" from true to false. By default its value is true.
Deploy the project as a Portlet WAR to the primary node in the cluster. It will be distributed to other nodes automatically.
Determine which node is the "scheduler" node, where the Alerts Scheduler runs. In its WEB-INF/config/scheduler/scheduler.properties file, change the value for the entry "bowstreet.util.scheduler.start" back from false to true. This node is the one where Alerts Scheduler actually runs.
Start all nodes in the cluster.

Edit
More Actions ▼

collapsed

Attachments (0)

collapsed

expanded

Copy and paste this wiki markup to link to this article from another article in this wiki.

Link:

Go Elsewhere	Stay Connected	Help	About
IBM Collaboration Solutions wikis IBM developerWorks IBM Software support	IBMSocialBizUX on Twitter IBMSocialBizUX on Facebook Lotus product forums IBM Social Business UX blog IBM Collaboration Solutions	Wiki Help Forgot user name/password Wiki design feedback Content feedback About the wiki	About IBM Privacy Accessibility IBM Terms of use Wiki terms of use