LinkServer is started by a special Launcher created during the installation process. Launcher type depends on the operating system: Under Unix, it's the LinkServer.sh shell script, for example.
Under Windows, it is a small executable file, LinkServer.exe, accessible through the Start menu (Start > Programs > AggreGate > LinkServer) or as a desktop shortcut (shown below).
The Launcher can be added to the auto-start sequence of the OS. This is also an OS-dependent operation. For example, under Windows you put a shortcut to the LinkServer Launcher in the Startup folder. Under FreeBSD, you create a simple shell script executing LinkServer.sh in background and put it to /usr/local/etc/rc.d/ directory. For further details, please see your operating system documentation.
LinkServer installer creates three launchers those extension depends to the operating system:
| • | linkserver for a normal startup |
| • | linkserver_console for starting server and showing its output in the console window (note, that normal logging is not disable in this case) |
| • | linkserver_service for starting server as a service |
Launcher properties file may be used to pass additional options to Java Virtual Machine running LinkServer. This file it located in the same directory with the launcher itself. Its name matches the launcher's name, and its extension is .vmoptions. For example, additional JVM options for a launcher called linkserver.exe are passed using Launcher Properties File linkserver.vmoptions. In this file, each line is interpreted as a single VM parameter.
|
It's absolutely necessary to add newline character (i.e. press ENTER when finished entering line text) in the end of every line of .vmoptions file. If there is no newline character in the end of line, it will be ignored! For example, is you have a one-line .vmoptions file, the only line must also end with new line character: -classpath/a jdbc-driver.jar<newline_character> |
In addition to the VM parameters you can also modify the classpath in the *.vmoptions files with the following options:
-classpath [classpath] |
Replace the classpath of the generated launcher. |
-classpath/a [classpath] |
Append to the classpath of the generated launcher. |
-classpath/p [classpath] |
Prepend to the classpath of the generated launcher. |
|
It's necessary to put exactly one space between -classpath parameter and its value. |
|
NEW TERM: A class path is the directory path specifying where compiled Java files are located on the local system. |
|
Append to classpath option of Launcher Properties File may be useful when making new Java libraries available to LinkServer. For example, Java Database Connectivity (JDBC) driver file path should be appended to the classpath when switching to another database engine. |
