After changes to the configuration files ./etc/*.xml, you have to check that no errors have occurred. The tests should preferably be done about 5 minutes after the Integration Server is fully started/restarted.

How Are the Tests Carried Out?

This depends on the operating system and the startup type of the Integration Server.

On Windows when starting in the foreground (not as service).	Observe the messages that appear in the command window input prompt.
On Windows when starting as a service.	Check file ./logs/wrapper.log.
On Unix/Linux when starting in the foreground (run).	Observe the messages in the console.
On Unix/Linux when starting as a service.	Check file ./hub.txt.

Note: Do not leave these files open in a blocking editor for a longer time. Use a non-blocking editor or copy the file and open the copy.

If there are error messages (exceptions) during or shortly after the normal start message, there is an urgent need for action. In this case, the Integration Server and therefore Lobster_data may not be available with the entire functionality. Often it is not possible to log on to the client in the event of a faulty start. Some possible causes in the following.

Invalid license.
Database hub not ready or unreachable.
Error in a configuration file after modification.
Insufficient memory.
Other serious errors, for example, a class in the wrong version.
Error output from classes, which the user has (incorrectly) developed himself.

Errors output here always indicate a serious problem and should be analyzed immediately. Since these messages are terminal outputs and do not occur in a log, they do not have a timestamp. During the normal, error-free operation, there should be no further messages after the following start message.

Lobster Integration Server (IS) started in 32453 ms , system is ready ...
--------------------------------------------------------------------------

If there is not enough memory available during operation, OutOfMemoryExceptions may appear. Most of the time, this error only leads to the termination of the profile job that has used too much memory. In rare cases, it is possible that other functions are impaired. Therefore, after an OutOfMemoryException, the entire Integration Server should be restarted. If such errors occur frequently, the memory should be increased.

Note: In order to detect OutOfMemoryExceptions, you should not only check after a restart but also afterwards, for example, once a day and obviously also if a profile job ends with an OutOfMemoryException.