Startup configuration for service operation (Windows)

If the Integration Server is to be run as a Windows service, this must be done via the wrapper framework. The following files are involved.

• ./bin/IS_as_SERVICE.bat

• ./etc/wrapper.conf

wrapper.conf

During the first configuration the file wrapper.conf has to be adapted to your needs. Some areas shall be briefly explained here.

set.JAVA_HOME=C:\j2sdk1.4.2_11
set.HUB_HOME=C:\IS
set.PATH=%HUB_HOME%\lib\win;%PATH%

The individual entries above correspond to the entries in the configuration file ./bin/hubenv.bat, as described in Startup configuration via start script (Windows).

#Java Classpath (include wrapper.jar) Add class path elements as needed starting from 1
wrapper.java.classpath.1=%HUB_HOME%/bin/wrapper.jar
wrapper.java.classpath.2=%HUB_HOME%/bin/starter.jar

These entries apply to the start of the Integration Server as a service. The used classes must of course be made known to the virtual machine.

 CAUTION   The libraries specified here are only visible to the wrapper that launches the Integration Server as a service. Own libraries added here (as specified in the comment) will not be visible within the running Integration Server. To add your own libraries or directories, proceed as described below.

wrapper.java.library.path.1=%PATH%

In principle the path for own DLLs can be set here. However, as shown in the example, the PATH variable is set, so the procedure described in the "Setting the library path" section in Startup configuration via startup script (Windows) can still be applied.

Setting the system parameters

If system parameters are to be set, this is done via the configuration parameter wrapper.java.additional.1 (and following). Following an example.

# Java Additional Parameters
wrapper.java.additional.1=-server
wrapper.java.additional.2=-Dhub.home="%HUB_HOME%"
wrapper.java.additional.3=-Dhub.log="%HUB_HOME%/logs"
wrapper.java.additional.4=-Dhub.port=80

The setting of the initial and maximum memory takes place via own configuration parameters (wrapper.java.initmemory and wrapper.java.maxmemory).

Setting the classpath

Since the classpath set in the configuration file is only used for the wrapper, the classpath must be set via a system property. There are two system properties available.

Individual values are separated by semicolons, as in MS-DOS.