Adding or modifying an HTTP server
(1) All existing HTTP servers are listed here. Double-click or right-click to get to the settings of the server. By default, you will find the two servers Main Server (./etc/hub.xml → Communication of Lobster Integration, e.g. HTTP and AS2) and Administrative Server (./etc/admin.xml → GUI of Admin Console and Lobster Integration).
(2) You can add a new HTTP server via the context menu. See (3).
(3) The name of the server (e.g. Main Server 2) is usually set in the configuration file, see (4), and should be set there.
(4) Here you must specify the name of the configuration file of the HTTP server. You could, for example, copy the file ./etc/hub.xml, rename it to ./etc/hub2.xml and then change the name of the server and its port (<Set name="port">).
Attention: Changes are lost after a restart of the Integration Server. To make changes permanent, you need to customise the startup script or the startup configuration for the service. Please make sure that the entry is between admin.xml and factory.xml!
Start script ./bin/hub.bat (Windows)
|
if [%1]==["run"] (set ARGS=etc\hub.xml etc\admin.xml etc\hub2.xml etc\factory.xml & goto args_done) if [%1]==[] (set ARGS=etc\admin.xml etc\hub.xml etc\hub2.xml etc\factory.xml & goto args_done) |
Start script ./bin/execute.sh(Linux/Unix)
|
CONFIGS="${HUB_HOME}/etc/hub.xml ${HUB_HOME}/etc/admin.xml ${HUB_HOME}/etc/hub2.xml ${HUB_HOME}/etc/factory.xml" |
Startup configuration for service (./etc/wrapper.conf)
|
# Application parameters. Add parameters as needed starting from 1 |
Attention: If you would like Lobster Integration to accept outside HTTP requests (http(s)://<URL or IP of the Integration Server>/dw/Request) via your new HTTP server, you still need modify the configuration file ./etc/startup.xml as follows
<!-- If multiple HTTP servers are installed and servlets for Integration client should only be assigned to a specific HTTP server, use next option --><Set name="internalServerName">Main Server 2</Set>Settings of the HTTP server
(1) List of HTTP socket listeners configured for the selected server. The name of the listener, its status and the IP address and the port on which HTTP requests should be listened to are displayed.
(2) If a listener is selected in (1), the list of its handlers and contexts appears here. Please refer to the Jetty documentation for an explanation of these terms. You can stop/start a handler/context via the context menu.