3.1 Terracotta Job Store for Quartz Express Installation

3.1.3a Add Terracotta Configuration

To be clustered by Terracotta, the following properties in quartz.properties must be set as follows:

org.quartz.jobStore.class = org.terracotta.quartz.TerracottaJobStore

org.quartz.jobStore.tcConfigUrl = <path/to/Terracotta/configuration>

The property org.quartz.jobStore.tcConfigUrl must point the client (or application server) at the location of the Terracotta configuration.

The client must load the configuration from a file or a Terracotta server. If loading from a server, give the server’s hostname and its Terracotta DSO port (9510 by default). The following example shows a configuration that is loaded from the Terracotta server on the local host:

org.quartz.jobStore.class = org.terracotta.quartz.TerracottaJobStore

org.quartz.jobStore.tcConfigUrl = localhost:9510

To load Terracotta configuration from a Terracotta configuration file ( tc-config.xml by default), use a path. For example, if the Terracotta configuration file is located on myHost.myNet.net at /usr/local/TerracottaHome , use the full URL along with the configuration file’s name:

org.quartz.jobStore.class = org.terracotta.quartz.TerracottaJobStore

org.quartz.jobStore.tcConfigUrl = file://myHost.myNet.net/usr/local/TerracottaHome/tc-config.xml

3.1.3b Scheduler Instance Name

A Quartz scheduler has a default name configured by the following quartz.properties property:

org.quartz.scheduler.instanceName = QuartzScheduler

Setting this property is not required. However, you can use this property to instantiate and differentiate between two or more instances of the scheduler, each of which then receives a separate store in the Terracotta cluster.

Using different scheduler names allows you to isolate different job stores within the Terracotta cluster (logically unique scheduler instances). Using the same scheduler name allows different scheduler intances to share the same job store in the cluster.

UNIX/Linux

[PROMPT] ${TERRACOTTA_HOME}/bin/start-tc-server.sh &

Microsoft Windows

[PROMPT] ${TERRACOTTA_HOME}\bin\start-tc-server.bat

• 2. Start the application servers.
• 3. Start the Terracotta Developer Console:

UNIX/Linux

[PROMPT] ${TERRACOTTA_HOME}/bin/dev-console.sh &

Microsoft Windows

[PROMPT] ${TERRACOTTA_HOME}\bin\dev-console.bat

• 4. Connect to the Terracotta cluster.

Click Connect... in the Terracotta Developer Console.

• 5. Click the Topology node in the cluster navigation window to see the Terracotta servers and clients (application servers) in the Terracotta cluster.

Your console should have a similar appearance to the following figure.

3.1.5a Procedure:

• 1. Shut down the Terracotta cluster.
• 2. Create a Terracotta configuration file called tc-config.xml with contents similar to the following:

<?xml version="1.0" encoding="UTF-8"?>

<!-- All content copyright Terracotta, Inc., unless otherwise indicated. All rights reserved. -->

<tc:tc-config xsi:schemaLocation="http://www.terracotta.org/schema/terracotta-5.xsd" 

xmlns:tc="http://www.terracotta.org/config" 

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <servers>

    <!-- Sets where the Terracotta server can be found. Replace the value of          host with the server's IP address. -->

    <server host="server.1.ip.address" name="Server1">

      <data>%(user.home)/terracotta/server-data</data>

      <logs>%(user.home)/terracotta/server-logs</logs>

    </server>

    <!-- If using a standby Terracotta server, also referred to as an ACTIVE-PASSIVE configuration, add the second server here. -->

    <server host="server.2.ip.address" name="Server2">

      <data>%(user.home)/terracotta/server-data</data>

      <logs>%(user.home)/terracotta/server-logs</logs>

    </server>

<!-- If using more than one server, add an <ha> section. -->

    <ha>

      <mode>networked-active-passive</mode>

      <networked-active-passive>

        <election-time>5</election-time>

      </networked-active-passive>

    </ha>

  </servers>

  <!-- Sets where the generated client logs are saved on clients. -->  

  <clients>

    <logs>%(user.home)/terracotta/client-logs</logs>

  </clients>

</tc:tc-config>

• 3. Install Terracotta 3.2.1 on a separate machine for each server you configure in tc-config.xml .
• 4. Copy the tc-config.xml to a location accessible to the Terracotta servers.
• 5. Perform Step 2: Install Terracotta Job Store for Quartz and Step 3: Configure Terracotta Job Store for Quartz on each application node you want to run in the cluster.

Be sure to install your application and any application servers on each node.

• 6. Edit the org.quartz.jobStore.tcConfigUrl property in quartz.properties to list both Terracotta servers:

org.quartz.jobStore.tcConfigUrl = server.1.ip.address:9510,server.2.ip.address:9510

• 7. Copy quartz.properties to each application node and ensure that it is on your application's classpath. If you are using a WAR file, add the Quartz configuration file to WEB-INF/classes or to a JAR file that is included in WEB-INF/lib .
• 8. Start the Terracotta server in the following way, replacing "Server1" with the name you gave your server in tc-config.xml :

 [PROMPT] ${TERRACOTTA_HOME}/bin/start-tc-server.sh -f <path/to/tc-config.xml> -n Server1 &

 [PROMPT] ${TERRACOTTA_HOME}\bin\start-tc-server.bat -f <path\to\tc-config.xml> -n Server1 &