Apama 10.15.0 | Developing Apama Applications | Developing Apama Applications in EPL | Using EPL Plug-ins | Using the distributed MemoryStore | Configuring a distributed store | Configuring a distributed store
 
Configuring a distributed store
After a distributed store has been added to the project, you can configure it.
You can configure frequently-used settings for a distributed store in the Distributed MemoryStore editor. These settings are those in the .properties file. For other settings, you need to edit the .xml file directly.
*To configure a distributed store
1. Specify any provider-specific configuration options in either the Standard properties section of the editor or, for TCStore, in the TCStore sections of the editor.
2. In the Classpath section, specify the names of the required provider-specific .jar files. This is only required if Other was used as the store type (that is, if you are not using TCStore or BigMemory Max).
a. Click the Plus (Add Classpath) button. A new line is added to the location list.
b. In the new line, specify the name of the .jar file. When you specify the path to a .jar file, you should use substitution values rather than a full path name (for example, use ${installDir.mystore}/lib/my.jar).
3. In the Custom property substitution variables section, specify the name and values of additional substitution variables (${varname}), if any, used by the distributed cache. The .properties file contains substitution variables that are used by the .xml configuration file.
You can define your own property substitution variables here, which will be written to the .properties file when you save. You can then edit the .xml file (see below) to use your own property substitution variables wherever you wish.
a. Click the Plus (Add Variable) button. A new line is added to the list of substitution variables.
b. In the new line, specify the name and value of the substitution variable you want to add.
4. (If needed.) In the Configuration files section, you can access the Spring .xml and .properties files. Click on the file name links to open them in the appropriate editor.
For more information on specifying property values, see Configuration files for distributed stores.