Hibernate configuration for the JobScheduler database should not be required

Current Situation

• The JobScheduler database is only necessary to get task and order logs directly from the database.
• If the database connection cannot be acquired then the JobScheduler sends the log.
• So, a log cannot be send only if the JobScheduler is down and the database connection fails.
• Nevertheless, the web services expect a hibernate configuration for the JobScheduler database.

Desired Behavior

• A hibernate configuration for the JobScheduler database should not be required.
• Only a warning is logged if the hibernate configuration not found.