Modifying the Size of the Log File
You can use the server_config utility to increase or decrease the size of the log file for a storage session. When you change the size of the log file, you actually create a new log file of the specified size. Before creating the new log file, the server_config utility empties the old file by applying the data it contains to the storage file.
When specifying the size of the new log file, be sure the file is large enough to hold the largest document, or batch of documents, that a client will publish in a single transaction. Remember that the log file is used by all Brokers on the Broker Server.
For best performance, the log file should be placed on a dedicated device that is not used by any other application or by the storage files.
The maximum size for a log file is 2 GB on 32-bit platforms and 8 GB (as a practical limit) on 64-bit platforms.
Note:
If the existing log file contains a large amount of data, it might take several minutes for the server_config utility to empty the old log and create a new one.
To modify the size of a log file
1. Stop the Broker Server.
2. On the machine where Broker Server is installed, navigate to the following directory:
webMethods Broker_directory /bin
3. Run the following command. Type the entire command on one line.
server_config storage dataDir -session_type qs
-qs_log_file logFile logSize
Where... | Specifies... |
dataDir | The fully-qualified location of the Broker Server's data directory. Enclose the entire directory name in quotes if any portion of the name contains a space. |
type | The storage session whose log file you want to modify.  If you are modifying the log file for the configuration session or for a combined storage session, type is: configIf you are modifying the log file for the run-time data session, type is: data |
logFile | The fully-qualified name of the new log file. Note:
By convention, the names of log files have ".qs.log" as an extension. Although you are not required to use this extension when you create a log file, we recommend you do so to make the log file easy to identify. If you are running a separate-session configuration, we recommend that you specify a name that indicates whether the log file belongs to the configuration session or the run-time session (e.g., configData.qs.log or run-timeData.qs.log). |
logSize | The size of the log file. Specify the size as a number followed by a K (kilobytes), M (megabytes), or G (gigabytes). |
The following example illustrates the configuration for a combined session:
server_config storage
"C:\webMethods Broker_directory\Broker\data\awbrokersversion\my Broker"
-session_config qs
-qs_log_file "C:\webMethods Broker_directory\Broker\data\awbrokersversion\
my Broker\BrokerConfig01.qs.log" 20M
The following example illustrates the configuration for a run-time data session:
server_config storage
"C:\webMethods Broker_directory\Broker\data\awbrokersversion\my Broker"
-session_data qs
-qs_log_file
"C:\webMethods Broker_directory\Broker\data\awbrokersversion\
my Broker\BrokerData01.qs.log" 1G