Documentation Index

Fetch the complete documentation index at: https://docs.lobstersoftware.com/llms.txt

Use this file to discover all available pages before exploring further.

Setting up the startup script (Windows)

Prev Next

Warning

As of release 26.2, the new Lobster Application Wrapper is required.

When you start the Integration Server using the standard startup script, two files are involved. Both are located in the ./bin directory.

hubenv.bat

Defines the path to the Java Virtual Machine and the working directory for the Integration Server.

hub.bat

Contains all system parameters and classpath information to pass to the Java Virtual Machine at startup.

hubenv.bat

In hubenv.bat, you set two values. JAVA_HOME specifies the base directory for the Java Virtual Machine. HUB_HOME specifies the working directory for the Integration Server.

You typically modify this file in only two cases: immediately after initial installation or after updating the Java Virtual Machine to a new directory.

hub.bat

Comments in hub.bat describe each setting directly in the code. The following three sections are particularly important.

Setting the classpath

The classpath includes all directories and library files that the Integration Server can use at runtime. By default, the classpath uses all JAR and ZIP files in the ./lib directory. To add new JAR files, simply place them in this directory. The Integration Server activates them automatically.

Do you want to add directories or library files outside ./lib? Extend the CP variable in the batch file. Find the relevant location under this comment:

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

Separate multiple values with a semicolon.

Setting the library path

Do you use runtime libraries to access system resources, such as CAPI or SAP connections? Then the Java Virtual Machine must be able to access these libraries.

Windows systems search the PATH variable for DLLs. Place your own DLLs in one of the already-configured directories. Alternatively, extend the PATH variable to include your own directory.

The Integration Server adds the ./lib/shared/win directory to the PATH variable by default. Place DLLs that the Integration Server alone needs in this directory.

Do you want to add more directories? Find the relevant location under this comment:

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

Separate multiple values with a semicolon.

Setting system parameters

The batch file assembles all system parameters for starting and running the Integration Server below this comment:

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

Add or modify system parameters here, for example the minimum or maximum memory allocation for the Java Virtual Machine.

Starting and stopping the server

Call the batch file hub.bat to start the server. The server runs in the foreground. Keep the process window open for the entire runtime.

To stop the server, press Ctrl+C. Alternatively, close the process window.

Warning

If you select text in the console, it blocks the output buffer for STDOUT and STDERR. The Integration Server then halts all processes that write to STDOUT or STDERR.

Standard components do not exhibit this behavior. However, it can occur with custom classes. A single click in the console window can activate selection mode on some Windows versions. Be careful when clicking in the console.