S2: Scheduling Activities tasks 

Activities uses the open source Quartz scheduler. The following jobs must be scheduled to run on a dedicated node; otherwise Quartz loses the JDBC connection to the database when it attempts to run:
• AutoComplete
• DatabaseRuntimeStats
• TrashAutoPurge

To schedule these tasks correctly, on the deployment manager open the wsadmin client in a command window and enter the following commands:

execfile("C:\IBM\WebSphere\AppServer\profiles\Dmgr01/config/bin_lc_admin/activitiesAdmin.py")

If prompted to select which server to make the change on, enter 1. Now check out the configuration files for activities with the following command:

ActivitiesConfigService.checkOutConfig("C:\temp", "dmgrCell01")

From the temp directory, open the oa-jobs.xml file and specify a server to run each of these tasks on. The value must take the format of
cell name/node name/server name

Below is an example of what this entry would be for the DatabaseRuntimeStats job:



Make the same change for the other jobs and then save the .xml file. Before checking the file back into the system, disable the cluster scheduler by running the following command:

ActivitiesConfigService.updateConfig("clusterScheduler.enabled","false")

Now check in the file:

ActivitiesConfigService.checkInConfig()

Now clear the existing jobs from memory and the database by running the following command:

Scheduler.purgeJobs("cluster")

Exit the wsadmin client and synchronize the changes across all the nodes. Restart the activities cluster for the changes to take effect.

---

Go to the next topic:

S2: Scenario environment
S2: Prerequisites
  S2: Configuration diagrams
S2: Machine details
S2: Installing Lotus Connections in an Enterprise level deployment

S2: Preinstallation tasks
S2: Installing Lotus Connections on node 1
S2: Adding nodes 2 and 3 to the cluster
S2: Post installation tasks
S2: Setting up the Web server
S2: Configuring SSL and adding features to the SSL trust store
S2: Editing the configuration file
S2: Scheduling Activities tasks
S2: Tuning WebSphere Application Server for optimal performance

S2: Starting Lotus Connections
S2: Configuring an administrative user for Blogs
S2: Integrating Lotus Connections with Lotus Quickr for WebSphere Portal
S2: Enabling Sametime awareness on Lotus Connections
S2: Troubleshooting

Table of Contents:
Lotus Connections 2.5 Enterprise level deployment scenario