PEEKS AND POKES: Centralized configuration for serverside FSI applications

The current release of FSI Server and FSI Cache are the first two serverside FSI applications to support centralized configurations. This new feature allows placing the configuration files outside of the webapps context directory. This makes updating FSI applications a lot easier, as the old version can simply be undeployed without loosing the configuration.
As soon as the new version is deployed it will automatically use the previous configuration files. In order to use the centralized configuration the location of the configuration files needs to be specified in the tomcat startup options, or the equivalent when using a different application server. For example, placing the FSI Server configuration files in /etc/fsi/fsi-server would be the obvious on Linux server systems. To achieve this the following needs to be added to the JVM startup parameters:


The path to the configuration for FSI Cache can be set using


FSI Server will expect to find the following directories and files beneath the given location:
config containing the configuration files usually located in WEB-INF/config/. server_profile and importer_profiles containing the profiles usually located in WEB-INF/server_profiles and WEB-INF/importer_profiles.

FSI Cache will expect the subdirectories config and profiles containing the files usually located in their counterparts in the WEB-INF folder.

When setting up FSI Server or FSI Cache using centralized configurations you should make sure the application data is also stored outside the webapp context. In case of FSI Server this is the images and storage and in case of FSI Cache this is the cached data.