Fix
- [JITL-331] - Reporting plugin should synchronize the "waiting_for_agent" order steps
- [JITL-332] - Inventory plugin should store agent even if agent is unavailable
- [JITL-333] - JobScheduler Tasks should be reported in Reporting tables even when running in Job Chains
- [JITL-334] - The ConfigurationMonitor throws a Null Pointer Exception
- [JITL-335] - Inventory plugin does not read the actual live folder but only the default live folder
- [JITL-336] - When executing the fact plugin sometimes an LockAcquisitionException occurs
- [JITL-337] - InventoryPlugin: "MappingException: No Dialect mapping for JDBC type: -9" occurs when using native MS SQL Driver
- [JITL-339] - Postprocessors which are implemented with Java JobSchedulerAdapter class are terminating with an error
- [JITL-340] - Inventory plugin should find objects in cache folder from remote configuration too
- [JITL-341] - The JITL JOB JobSchedulerCheckEventsJSAdapterClass should not throw an transaction already startet exception
- [JITL-342] - Inventory Plugin has always to determine the Supervisor if a Supervisor is configured
- [JITL-344] - JobSchedulerEventDBItem does not work with jodatime
- [JITL-347] - InventoryPlugin: NonUniqueObjectException when processing backlogged events
- [JITL-348] - com.sos.jitl.checkrunhistory.JobChainHistory
- [JITL-349] - ReportingPlugin (FactNotificationPlugin) - original exception should be visible when using Monitoring Interface
- [JITL-356] - SSH Job throws error "Universal Agent does not support method" when running on an Agent
- [JITL-358] - Improve Exception Handling for Inventory Plugin
- [JITL-363] - Wrong nodes in JOC Cockpit history if job chain has a file_order_sink configuration
- [JITL-364] - InventoryPlugin: When saving a Job configuration with a process class sometimes an 'Transaction already active' error occurs
- [JITL-368] - JOC should run with ORACLE 12c
- [JITL-377] - Expected duration of jobs is wrongly calculated
- [JITL-379] - Split orders running on an agent should have node parameters from the xml_payload from the root order
- [JITL-380] - The job JobSchedulerDequeueMailJob should be able to run in a job chain
- [JITL-385] - SSH Job doesn´t return ExitCode of shell in case of error
- [JITL-386] - JobScheduler Master Setup throws an error with NPE when using MSSQL integrated security.
- [JITL-387] - Possibly NPE in Inventory Plugin when reading private.conf
- [JITL-388] - DailyPlan raises SSLHandshakeException called by InventoryPlugin when JobScheduler has HTTPS configuration
- [JITL-389] - Not all objects of a new folder are shown after the folders is added to the live folder
- [JITL-391] - SOSHibernate should raise a specific exception if the hibernate configuration path is wrong
- [JITL-393] - <show_calendar> should not remove spaces in the answer.
- [JITL-398] - CheckRunHistory API with Spooler throws a null pointer exception
- [JITL-407] - Enable proxy settings in JITL REST client
- [JITL-414] - Universal Agent Batch installation feature should substitute instance script per host
- [JITL-416] - Node parameters in the form node/param should be availabe for substitution in the script tag e.g. for the ssh job
- [JITL-417] - The link for the current setup file for the Universal Agent should be available in the download file for the batch installer
- [JITL-418] - Batch installer does not provide values coming from a profile for substitution in the installation script
- [JITL-419] - Batchinstaller reads the value for the auth_file from the auth_method_parameter
- [JITL-420] - SOSHibernateObjectOperationException should be extended by the dump of the db item object
- [JITL-421] - JobScheduler Master running in an active cluster produces error messages "ORA-00001: unique constraint"
- [JITL-423] - JITL job CreateDailyPlan should consider the configuration directory setting
- [JITL-424] - The SSH Job should set preCommand and postCommands for Windows and Linux automatically
- [JITL-425] - It should be possible to define an installation script per host in the Universal Agent Batch Installer
- [JITL-428] - JITL Jobs should show the stack trace in case of an error
- [JITL-429] - It should be possible to define global properties agentOptions for the Universal Agent Batchinstaller
- [JITL-430] - The sync node in the job chain for the batch installation procedure can be removed
- [JITL-431] - The batch installation procedure for the Universal Agent should configure automatic start on server startup
- [JITL-432] - History of jobs and job chains is not updated in time
- [JITL-433] - NPE in InitializeInventoryInstancePlugin
- [JITL-434] - FactPlugin does not set a notification task end property
- [JITL-435] - JobScheduler Monitoring Interface should handle next steps after sending the recovery message
- [JITL-611] - Parameter "result_list_file" should be accessible in JITL JobSchedulerExistsFile
Deprecation
- [JITL-171] - Use of SSH jobs based on the Trilead implementation is deprecated
- [JITL-367] - <param name="global_configuration_params"> no longer available.
- [JITL-411] - Retirement of classic configuration monitor for node parameters
- [JITL-456] - Retirement of JITL Job JobSchedulerCleanupSchedulerDbJSAdapterClass
Feature
- [JITL-212] - Provide a function for checking the job history in job monitors by use of web services
- [JITL-280] - Add JMS support to the JobScheduler Monitoring Interface
- [JITL-323] - Provide database access layer to allow jobs to run custom SQL statements
- [JITL-346] - Original SQL exception should be visible when using hibernate
- [JITL-351] - Add Agent identification to Monitoring Interface
- [JITL-352] - Add Cluster member identification to Monitoring Interface
- [JITL-353] - Monitoring Interface should recognize the configured JobChain/Job/TimerJobChain with the leading "/" character
- [JITL-359] - SOSHibernateOpenSessionException should extend SOSHibernateInvalidSessionException
- [JITL-360] - SOS Hibernate should not use the deprecated hibernate session Criteria API
- [JITL-374] - JITL join job for optimized synchronization in a split & join workflow pattern
- [JITL-390] - ResultSet2CSVJob should use SOSHibernateSQLExecutor
- [JITL-400] - JobScheduler Monitoring Interface should support standalone jobs
- [JITL-401] - JobScheduler Monitoring Interface should support the job timers
- [JITL-408] - InventoryPlugin updates runtimes of an edited and assigned calendar at JobScheduler start
- [JITL-412] - InventoryPlugin event processing has to check assigned calendars
- [JITL-422] - SOSHibernate should raise a specific exception when using transactions with versioning
- [JITL-427] - JobScheduler Montitorig Interface. Performance improvement for SystemNotifier job.
- [JITL-436] - New implementation for JobSchedulerManagedDatabaseJob
Sub-task
- [JITL-394] - Approve issue for 1.12 ResultSet2CSVJob should use SOSHibernateSQLExecutor
- [JITL-395] - Approve issue for 1.12 SOSHibernate should raise a specific exception if the hibernate configuration path is wrong
- [JITL-397] - Approve Issue for release 1.12
- [JITL-406] - Approve JITL-402 Issue for 1.12
- [JITL-409] - Approve for release 1.12 - JITL-401: JobScheduler Monitoring Interface should support the job timers
- [JITL-410] - Approve for release 1.12 - JITL-400 : JobScheduler Monitoring Interface should support standalone jobs
- [JITL-426] - Approve issue for 1.12 - JITL-212 : Provide a function for checking the job history in job monitors by use of web services
Edit/Copy Release Notes
The text area below allows the project release notes to be edited and copied to another document.