Adding a Cache Manager Configuration File to
Integration Server
If you have an existing cache manager configuration file (for example, one that you created manually or one that you copied from another
Integration Server
), you can add it to your
Integration Server
using the following procedure.
If you are adding a configuration file that you created manually (rather than copying a configuration file from another
Integration Server
), verify that the file satisfies the following conditions before you perform this procedure:
The name of the file ends with the extension “.xml”.
The name of the file does not begin with the characters “SoftwareAG”.
The <ehcache> element includes the name attribute. The name attribute specifies the name of the cache manager (the name under which the cache manager will be registered in
Integration Server
). Make sure the name does not begin with the characters “SoftwareAG”. Make sure the name is unique among cache managers on the
Integration Server
to which you are copying the file.
Example:
<ehcache name="MyCacheManager">
The rejoin attribute is set to “true” if the cache manager is configured to use a
Terracotta Server Array
. In other words, if the <terracottaConfig> element is present and its url attribute is specified, make sure the rejoin attribute is also specified and that it is set to “true.”
Example:
<terracottaConfig url="srv3A:9510,srv3B:9510" rejoin="true">
All distributed caches that are defined in the configuration file include the <nonstop> element.
Integration Server
requires all distributed caches to run in nonstop mode.
Example:
<cache
name="JLSCache01"
eternal="true"
maxElementsInMemory="5000"
overflowToDisk="false"
copyOnWrite="true"
copyOnRead="true">
<terracotta> <nonstop></nonstop> </terracotta>
</cache>
Note:
If you have created your own configuration file, be aware that
Integration Server Administrator
does not preserve comments when it updates a configuration file. If your configuration file includes comments, those comments will be discarded the first time someone edits it using
Integration Server Administrator
.
To manually add a cache manager to an
Integration Server
1.
Copy your configuration file to the
Integration Server_directory
\instances\
instance_name
\config\Caching directory.
2.
Restart
Integration Server
to initialize the cache manager.
Note:
If the file that you copied to
Integration Server
in step 1 replaced the configuration file for a cache manager that is already registered on
Integration Server
, you can reload the cache manager using
Integration Server Administrator
instead of restarting the
Integration Server
. (If the cache manager is currently shut down, start it first and then reload it.) For procedures, see
Reloading a Cache Manager
.
3.
Open
Integration Server Administrator
and go to
Settings > Caching
to verify that
Integration Server
was able to add your cache manager successfully.
If the cache manager is not listed on the
Settings > Caching
page or if it is not functioning properly, consult the server log or the
Terracotta Ehcache
log to see whether errors occurred during the initialization process. For information about viewing the
Terracotta Ehcache
log, see
Logging
Terracotta Ehcache Activity
. If there are problems with the configuration file (for example, if
Integration Server
could not parse the file or the file contains a duplicate cache manager name),
Integration Server
records an error message in the server log and writes a full stack trace to the error log.
