When starting the Integration Server via the normal startup script, the following files are involved, all of which are in the ./bin directory.

hubenv.bat	Contains the information about the location of the Java Virtual Machine to use and the working directory of the Integration Server.
hub.bat	Contains all system parameters and classpath information that should be passed to the virtual machine at startup.

hubenv.bat

Two settings are available in hubenv.bat. "JAVA_HOME" for setting the base directory of the Java Virtual Machine to be used, and "HUB_HOME" for specifying the working directory of the Integration Server.

This file usually only needs to be customised when the initial installation has been completed or an update of the Java Virtual Machine has been made (and the Java home directory is different).

hub.bat

The setting options within hub.bat are basically self-explanatory (since commented accordingly), but the following sections should be highlighted here.

Setting the classpath

The classpath includes all directories and library files that can be used by the Integration Server at runtime. By default, all jar and zip files in the ./lib directory are already used for the classpath, so just add new jars to this directory to enable them for the Integration Server.

If additional directories or library files are to be added that are not available in the standard lib directory, the variable "CP" in the batch file must be extended.

rem ===========================================================
rem == set CLASSPATH
rem ===========================================================
set CP=%HUB_HOME%

Additional values can be added here, separated by a semicolon.

Setting the library path

If runtime libraries are used to access resources of the system (e.g. CAPI or SAP connections), these libraries must be accessible to the Java virtual machine. Windows-based systems use the PATH variable to find DLLs. You can put your own DLLs in one of the specified directories or extend the PATH variable with your own directory.

The latter is already done and the directory ./lib/shared/win is added to the PATH variable, i.e. own DLLs, which are intended for the Integration Server alone, can also be placed in this directory

If additional directories are to be added, this is done in the file below the following comment.

rem ===========================================================
rem == get drive information
rem ===========================================================
set PATH=%HUB_HOME%\lib\win;%PATH%;

Additional values are added separated by a semicolon.

Setting the system parameters

System parameters required for starting and operating the Integration Server are assembled in the batch file below the following comment.

rem ===========================================================
rem == build jvm options
rem ===========================================================
set OPTIONS=-Xmx256m -Xms256m -server -Djava.awt headless=true ...

Own system parameters can be added or adjusted here (e.g. the minimum or maximum memory usage of the virtual machine, ...).

Starting and stopping the server

Executing the batch file hub.bat starts the server. The processing takes place in the foreground, i.e. the window of the process must remain open for the entire runtime. To stop the server, the process can be aborted by pressing Ctrl+C or implicitly by closing the window in which the process is running.

Attention: In Windows Vista, closing the window will cause the process to terminate immediately. A regular termination will not take place.

Attention: If text is marked inside the console, the output buffer for STDOUT and STDERR is blocked for further output. Processes within the Integration Server that output to STDOUT or STDERR will thereby be suspended. Although standard components of the Integration Server do not behave this way, this effect must be taken into account for self-developed classes. Depending on the version of Windows, just one click within the console window is enough to activate the marking mode (e.g. Windows 2000), so please pay attention to this.