conf.wsc File Content - ABO - Reference Guides

Back Office Configuration Guide

Reference Guides
Target Audience

The following lines show an example of a conf.wsc configuration file properties:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<Conf xmlns="" xmlns:a="" xmlns:w="" xmlns:xsi="">
<w:File format="%a %u [%t] &quot;%m %U %H&quot; %s %D %{User-Agent}i %q %b" name="<access_log_filename>">


  • <MaxFileSize> is the maximum size of files that can be uploaded to the BO. This value is set in a number of bytes as a plain number, e.g., 1000000000 stands for 1Gb. By default files uploaded to the Paf are limited to 500Mb and other files 'import to vocabulary, file repo, and so on) to 100Mb. The defined <MaxFileSize> overloads all the default values.
  • <access_log_filename> is the name of the file where is stored the Back Office access log. If the <w:AccessLog> parameter is not set, the Back Office access log is stored via the log manager.
  • <AC_host> is the name of the host where BO-AC is installed. Default value is locahost.
  • <AC_port> is the port used to communicate with BO-AC. Default value is 7200.
  • <Mongo_host> is the name of the host where MongoDB is installed.
  • <Mongo/connectionString> is accepting a full MongoDB connection string for the BOWSModule and AuditLog options. A connection string is used to connect to a MongoDB deployment: standalone, replica set, or a sharded cluster.

Several <seed> nodes can be used to indicate a cluster (e.g., Cassandra, MongoDB, etc.).