anchor.diff:          </security-setting>
   ---- 
   
  -
  -. Add the following properties to the `<system-properties>` element:
  -+
  -* `org.kie.server.persistence.ds`: The JNDI name of your data source. For {PRODUCT}, this is `java:/jboss/datasources/rhpam`.
  -* `org.jbpm.ejb.timer.tx" value="true`: Required for clustering timers.
  -* `org.kie.server.persistence.dialect`: The hibernate dialect for your database.
  +. Add the following properties to the `<system-properties>` element and replace the following placeholders:
  +* `<JNDI_NAME>` is the JNDI name of your data source. For {PRODUCT}, this is `java:/jboss/datasources/rhpam`.
  +* `<DIALECT>` is the hibernate dialect for your database. 
   +
   The following dialects are supported:
   + 
  
positive.code: ** PostgreSQL plus: `org.hibernate.dialect.PostgresPlusDialect`
  //** Sybase: `org.hibernate.dialect.SybaseASE157Dialect`
  +
  . Save the `domain.xml` file.
  
  
  
negative.code: +
  * The `datasource-jndi-name` is the JNDI name of the database specified at the beginning of this procedure. 
  * You can enter any name for the value of the `partition` property. However, a node will only see timers from other nodes that have the same partition name. Grouping nodes into partitions by assigning partition names enables you to break a large cluster up into several smaller clusters. Doing this should improve performance. For example, instead of having a cluster of 100 nodes, where all 100 nodes are trying to execute and refresh the same timers, you can create 20 clusters of 5 nodes by giving every group of 5 a different partition name.
  * Replace the  `default-data-store` attribute value with `ejb_timer_ds`. 
  * Set the value of `refresh-interval` in milliseconds to specify how often the EJB timer connects to the database to synchronize and load tasks to be processed.
  +
  [source,xml]
  ----
  