Provide solution to use database jobs with JobScheduler Universal Agent

Current Situation
Jobs which use the database by reading database connection information from factory.ini or hibernate.cfg do not work in the Universal Agent because the Universal Agent does not have these connection files.

Desired Behaviour
Jobs which use the database should be able to run on JobScheduler Universal Agent as well.

Solution

• Jobs will read connection data from the parameters
• Jobs that depend on hibernate will have the option to specify connection informations for establishing a hibernate session from the parameters. At the moment there are no hibernate based database jobs

Jobs affected
The following list of JITL jobs are prepared to run on an agent.

• sos.scheduler.managed.JobSchedulerManagedDBReportJob
• sos.scheduler.managed.JobSchedulerManagedDatabaseJob
• sos.scheduler.managed.JobSchedulerManagedExecutableJob
• sos.scheduler.db.JobSchedulerPLSQLJobJSAdapterClass
• sos.scheduler.db.SOSSQLPlusJobJSAdapterClass

The following jobs are not intended to run on an agent as they are housekeeping jobs or system jobs

• com.sos.jitl.housekeeping.cleanupdb.JobSchedulerCleanupSchedulerDbJSAdapterClass
• com.sos.dailyschedule.job.CheckDailyScheduleJSAdapterClass
• com.sos.dailyschedule.job.CreateDailyScheduleJSAdapterClass
• com.sos.jitl.reporting.job.inventory.InventoryJobJSAdapterClass
• com.sos.jitl.reporting.job.report.AggregationJobJSAdapterClass
• com.sos.jitl.reporting.job.report.FactJobJSAdapterClass
• com.sos.scheduler.notification.jobs.history.CheckHistoryJobJSAdapterClass
• com.sos.scheduler.notification.jobs.cleanup.CleanupNotificationsJobJSAdapterClass
• com.sos.scheduler.notification.jobs.reset.ResetNotificationsJobJSAdapterClass
• com.sos.scheduler.notification.jobs.notifier.SystemNotifierJobJSAdapterClass