Bridge Gateway private (DMZ)

It is possible to run your own private Bridge Gateway instead of the default public Bridge Gateway.

To do so, you can use a DMZ Server with some additional configuration. Add the following “addApplication” block to the “StartupService“ in configuration file ./etc/startup_dmz.xml on the DMZ Server.

<Configure class="com.ebd.hub.services.startup.StartupService">
...
  <Call name="addApplication">
        <Arg>
            <New class="de.lobster.scm.dmz.bridge.BridgeGatewayServerApp">
                <Set name="logLevel">ALL</Set>
                <Set name="tunnelServer">
                    <New class="de.lobster.scm.dmz.transport.NioTunnelServer">
                        <Set name="tunnelBindAddress">0.0.0.0</Set>
                        <Set name="tunnelPort">8444</Set>
                    </New>
                </Set>
                <!-- Endpoint must match the http server to be accessible from the platform instance -->                
                <!-- SSL must be configured and enabled in etc/admin.xml -->                
                <Set name="httpServerName">Administrative Server</Set>
                <Set name="gatewayBaseEndpoint">https://dmz-address.internal-customer-network.de:9000/bridge/</Set>
                <Set name="gatewayHost">dmz-address.external-customer-network.de:8444</Set>
            </New>
        </Arg>
   </Call>
...
</Configure>

Parameters

Parameter	Description
gatewayBaseEndpoint	Address of the DMZ (and the Bridge subpath) as seen from the Lobster Data Platform. This is the URL the Lobster Data Platform uses to send its requests to Bridges. (The internal/hidden/private Gateway address of the DMZ server so to speak.)
gatewayHost	This is the address that is used by the Bridge to establish a tunnel. (The public Gateway address of the DMZ server so to speak.)

DMZ memory settings

The DMZ memory may have to be increased. Following the recommended minimal memory settings for the JVM of a DMZ server used as a private Bridge Gateway:

Operating system: 8GB RAM

Java heap memory: 4GB

Java direct memory: 1GB

JVM parameter

→ See section System properties.

-Xms4096M -Xmx4096M -XX:MaxDirectMemorySize=1024M

Linux

JAVA_OPTIONS="-Xms4096M -Xmx4096M -XX:MaxDirectMemorySize=1024M -server ...

Windows console

set OPTIONS=-Xms4096M -Xmx4096M -XX:MaxDirectMemorySize=1024M -server ...

Windows service

...
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=4096
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=4096
...
wrapper.java.additional.<some number>=-XX:MaxDirectMemorySize=1024M

Documentation Index