State Keeper

This topic provides an example of the configuration for a cluster containing three ActiveSpaces Core Servers that each runs a state keeper.

globals:
  core.servers:
    SRV1: localhost:8080
    SRV2: localhost:8081
    SRV3: localhost:8082

servers:
  SRV1:
  - realm:
      data: TIBCO_HOME/activespacesdata/realm_data
  - tibdgkeeper:
      exepath: /opt/tibco/as/current-version/bin/tibdgkeeper
      name: k1
      logfile: TIBCO_HOME/activespacesdata/logs/_default-k1.log
  SRV2:
  - realm:
      data: TIBCO_HOME/activespacesdata/realm_data
  - tibdgkeeper:
      exepath: /opt/tibco/as/current-version/bin/tibdgkeeper
      name: k2
      logfile: TIBCO_HOME/activespacesdata/logs/_default-k2.log
  SRV3:
  - realm:
      data: TIBCO_HOME/activespacesdata/realm_data
  - tibdgkeeper:
      exepath: /opt/tibco/as/current-version/bin/tibdgkeeper
      name: k3
      logfile: TIBCO_HOME/activespacesdata/logs/_default-k3.log

In this example, the following information is specified for each state keeper:

• The location of the state keeper binary

• The name of the state keeper

• The location where its logs are written

Live Backup and Restore

When you are performing a live backup and restore, add the recovery.file property to the YAML file of ActiveSpaces Core Servers and start the Core Server before starting the restore operation, that is before running the following command:

tibdg grid load --rollback

Properties

The following table lists the properties that you can configure for the state keeper when it is run in an ActiveSpaces Core Server and the equivalent command-line arguments. Other command-line arguments such as the URL for the realm and any security-related arguments are not required because the connection to the realm and authentication is handled by the hosting Core Server.