The Systemite.SystemWeaver.TcpSubServer.exe does not need an .ini file since it gets its settings from the swDBServer executable. It does, however, need its own properties file for logging.


Prerequisites

  • A split server installation directory containing all required files to run the server.
  • A Systemite.SystemWeaver.TcpSubServer.exe.nlog located in the same directory as the server files.


Systemite can provide an example file or simply copy the following content into a text editor.


 

Systemite.SystemWeaver.TcpSubServer.exe.nlog

<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      autoReload="true"
      throwExceptions="false">

  <variable name="appName" value="YourAppName" />

  <targets async="true">
    <target xsi:type="File"
            name="default"
            layout="${longdate} [${threadid}] - ${level:uppercase=true}  ${message}${onexception:${newline}EXCEPTION\: ${exception:format=ToString}}"
            fileName="D:\TcpSubServer.log"
            keepFileOpen="false"
            />

    <target xsi:type="EventLog"
            name="eventlog"
            source="${appName}"
            layout="${message}${newline}${exception:format=ToString}"/>
  </targets>
  <rules>
    <logger name="*" writeTo="default" minlevel="Info" />
    <logger name="*" writeTo="eventlog" minlevel="Error" />
  </rules>
</nlog>


Configuring the Logging

  1. Save the file as Systemite.SystemWeaver.TcpSubServer.exe.nlog.
  2. Open the file and update the fileName= line to indicate the TCPSubServer.log file name and the correct path to where you want the log to be placed. Naming it TCPSubServer.log will differentiate it from the swServer.log and ensure two separate log files should you have them generating in the same location.
  3. Save your changes.


Starting the Logging

Logging will start automatically once you start and/or restart the main server. For a brief explanation of the content of this log file, see Explanation of Server Log Files.


Note: If the main server is running while you complete the configuration, it must be stopped and then restarted for the logging to begin successfully.