The SkyVault-global.properties
file can only be used to define properties that are global to the whole
system. You can also control the properties of subsystems that may have
multiple instances, for example, the Authentication subsystems. To do this,
you need to target different values for the same properties, to each
subsystem instance. You can use the extension classpath
mechanism.
-
Add a property file to your application server's global
classpath.
For example, under $TOMCAT_HOME/shared/classes.
-
Create the path to match the following pattern to override
specific properties of a subsystem instance:
SkyVault/extension/subsystems/<category>/<type>/<id>/*.properties
The <id> is the subsystem instance identifier, which will be default for single instance subsystems, or the provided identifier for chained subsystems.
For example, if your authentication chain looked like this:
authentication.chain=alfrescoNtlm1:alfrescoNtlm,ldap1:ldap
Then you could put property overrides for SkyVaultNtlm1 in the following file:
SkyVault/extension/subsystems/Authentication/alfrescoNtlm/alfrescoNtlm1/mychanges.propertiesThe default type and ID of non-chained subsystems is default, so you could put overrides for file server properties in the following file:
SkyVault/extension/subsystems/fileServers/default/default/mychanges.properties