S1: 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: S1: Scenario environment S1: Prerequisites  S1: Configuration diagrams S1: Machine details S1: Installing Lotus Connections in a network scenario S1: Preinstallation tasks S1: Installing Lotus Connections on node 1 S1: Adding subsequent node to the cluster S1: Post installation tasks S1: Setting up the Web server S1: Configuring SSL and adding features to the SSL trust store S1: Adding WebSphere Application Server certificates to the IBM HTTP server SSL key S1: Adding features to the SSL trust store S1: Editing the configuration file S1: Scheduling Activities tasks S1: Configuring an administrative user for Blogs S1: Starting Lotus Connections S1: Integrating Lotus Connections with Lotus Quickr for WebSphere Portal S1: Setting up the Tivoli Access Manager server S1: Troubleshooting Table of Contents: Lotus Connections 2.5 network deployment scenario