Settings
Here you can stop the server process (Integration Server). In addition, warnings for the job queue can be configured and the DMZ server can be managed.
Settings
(1) Force Stop: Provides the ability to shut down the Lobster server process. Important note: Make sure that you have the appropriate access rights to be able to restart the server process! Keep in mind that the server may be on a different machine than your client. Note: See also sections Force Stop by File and Force Stop via HTTP.
No new jobs are accepted, all active conversions are marked as Crashed Jobs (and thus resumed at restart).
All requests from the DMZ server are rejected (and therefore buffered on the DMZ server).
(2) Maintenance Stop: Provides the ability to shut down the Lobster server process. Important note: Make sure that you have the appropriate access rights to be able to restart the server process! Keep in mind that the server may be on a different machine than your client. Note: See also section Maintenance Stop via HTTP.
No new jobs are accepted, but all ongoing conversions will be completed.
All requests from the DMZ server are rejected (and therefore buffered on the DMZ server).
Load Balancing: Working Nodes log off when the job list is empty. The Node Controller shuts down when all Working Nodes are offline.
(3) Emergency Halt: Designed for rare exceptions, e.g. to edit, deactivate or export profiles before a shutdown . The GUI can still be operated normally, but the restart of a job (including file upload, etc.) and a mapping test is no longer possible. An Emergency Halt should be followed by a regular shutdown. The repeated use of the Emergency Halt without a shutdown of the Integration Server is not the intended use. Note: See also sections Emergency halt via Admin Console and Emergency Halt via HTTP.
No new jobs are accepted, but all ongoing conversions will be completed.
An email is sent to the address stored in ./etc/startup.xml.
If files are delivered via a DMZ server or SAP ALE, they will not be lost. However, if the files come from the local system via AS2/SMTP/FTP/OFTP/SSH (for example, from the FTP service of the Integration Server), the profile will not accept the files and they will remain in the folder where they were dropped, since all those services are stopped during the Emergency Halt. They will also not be automatically processed later.
The behaviour of the system on restart is controlled by the following entries in configuration file ./etc/startup.xml. The two statements are executed in this order.
...<Set name="startInEmergencyHaltMode">false</Set><Set name="forceUnlockEmergencyHalt">false</Set>...This is the default setting. The system is not put into the Emergency Halt mode and the Emergency Halt mode is not deactivated. If you had manually triggered the Emergency Halt mode, the system starts in Emergency Halt mode. If you had not manually triggered the Emergency Halt mode, it starts in normal mode.
...<Set name="startInEmergencyHaltMode">true</Set><Set name="forceUnlockEmergencyHalt">false</Set>...The system is put into the Emergency Halt mode and the Emergency Halt mode is not deactivated. The system therefore always starts in the Emergency Halt mode. This setting is not recommended!
...<Set name="startInEmergencyHaltMode">arbitrary</Set><Set name="forceUnlockEmergencyHalt">true</Set>...The value of the first parameter can be true or false here. The second parameter always disables the Emergency Halt mode, which means that the system always starts in normal mode. This is the recommended setting for a productive system!
(4) Number of jobs in queue: If more jobs (all priorities except Single Run are considered) than this number are in the queue over a certain period of time (5), a warning email will be sent (see entry in ./etc/startup.xml). If a value less than 1 is entered in this field, the monitoring of the queue is inactive.
(5) Warning after minutes: This field sets the time period in minutes. See (4).
Important note: The changes in (4) and (5) are only temporary after clicking "Apply". After restarting the system, the values are taken from the configuration file ./etc/startup.xml again!
...<Set name="warningQueueSize">0</Set><Set name="warningQueueSizeTime">30</Set>...(6) DMZ status: The status of the DMZ server.
(7) New DMZ IP/Message port: The address of the DMZ server can be changed at runtime. For this, specify the new address and port number and click button Apply. Note : After a restart, the DMZ server entered in configuration file ./etc/startup.xml is used again . Note: This can also be done via HTTP. See section Set New DMZ Server via HTTP.
(8) DMZ reset: If this button is clicked, the list of active DMZ servers is recreated, i.e. emptied and the current DMZ server is entered. Note: This list is also empty after a restart. The DMZ server entered in the configuration file ./etc/startup.xml is then automatically entered first. This list is only used to check the number of DMZ servers allowed by the license. If a new request comes from a DMZ server, it is first checked whether this server is already in the list. If yes, the request is allowed. If no, then this DMZ server is entered into the list, if the maximum number is not yet reached, and the request is allowed. If the maximum number is reached, then the request is rejected.