AggreGate Server is started by a special Launcher created during the installation process. Launcher type depends on the operating system:
| • | Under Windows, launcher is a small executable file, ag_server.exe, accessible through the Start menu (Start > Programs > AggreGate > Server) or as a desktop shortcut: |
| • | Under Unix, it's the AggreGate_server shell script, for example. |
AggreGate Server installer creates three launchers those extension depends to the operating system:
| • | ag_server for a normal startup |
| • | ag_server_console for starting server and showing its output in the console window (note, that logging to files and other destinations is not disabled in this case) |
| • | ag_server_service for starting server as a service |
Server Startup Problems
If your AggreGate Server fails to start or appears to work incorrectly, please check the following sections:
Launcher properties file may be used to pass additional options to Java Virtual Machine running AggreGate Server. 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 ag_server.exe are passed using Launcher Properties File ag_server.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> |
Changing Language
Default launcher properties file contains -Duser.language=XX option that is used to define language used by AggreGate Server. Default language is selected during AggreGate Server installation process.
|
If the language was changed after the first launch of AggreGate Server, database will contain data (system resource descriptions, events, etc.) in the language that was active during previous launches. |
Modifying The Classpath
The following options may be added to the *.vmoptions files to modify the classpath of the AggreGate Server's Java Virtual Machine:
-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 AggreGate Server. For example, Java Database Connectivity (JDBC) driver file path should be appended to the classpath when switching to another database engine. |
The following options may be added to the *.vmoptions files in order to control amount of memory used by AggreGate Server: