Using a File for the Service Blacklist
Using a file for the service blacklist can make it easier to specify the same set of blacklisted services across the servers in your organization. Keep the following information in mind when using a file for the service blacklist:
The file must specify each service or interface for the blacklist on a different line.
The
watt.server.service.blacklis value must be the relative path to the file or the absolute path to the file as where:
A relative path has the format: file:{relativePath}
For a relative path, Integration Server expects the file to be in the home directory of Integration Server which is defined in the watt.server.homeDir parameter. If the watt.sever.homeDir parameter is not set, Integration Server expects to find the file in the current working directory, that is the value of the Java 'user.dir' system property.
For example:
watt.server.service.blacklist=file:blacklist.txt
watt.server.service.blacklist=file:custom/blacklist.txt
An absolute path has the format: file:/
directoryName/
filenameFor example:
watt.server.service.blacklist=file:/opt/blacklist.cnf
Wildcards cannot be used in the values for
watt.server.service.blacklist or in the file that contains the service blacklist.
If you update the contents of the service blacklist file, you must restart
Integration Server for changes to take effect.
You can set the server configuration parameter to a comma-separated list, relative path to a file, or the absolute path to a file. You cannot specify a combination of these.
If the referenced file does not exist or cannot be read when
Integration Server starts,
Integration Server does not blacklist any services and continues starting up.
Integration Server logs a warning message about the referenced file, specifically:
[ISS.0007.0009W] "ACLManager: error processing "watt.server.service.blacklist" property file. Stack trace: stackTrace
If one of the entries in the list is a syntactically invalid name of a service or an interface,
Integration Server ignores the entry.