Fix
- [JITL-203] - The job JSObjects2GraphvizJSAdapterClass ends with error
- [JITL-216] - The JITL job JobSchedulerCheckRunHistory should not consider running jobs for the last successful run
- [JITL-219] - The JITL job JobSchedulerCheckRunHistory should make use of the new class com.sos.jitl.checkrunhistory.JobHistory
- [JITL-224] - The JITL Job sos.scheduler.job.SOSSSHJob2JSAdapter should create the correct environment variables for the given node parameters
- [JITL-225] - The JITL job JobSchedulerCheckRunHistory should have an option what action should take place if the result of the query is false.
- [JITL-226] - The JITL Job sos.scheduler.job.SOSSSHJob2JSAdapter should create all environment variables with a prefix
- [JITL-229] - The JITL-Job sos.scheduler.job.SOSSSHJob2JSAdapter does not substitute node paramters like state/parameter in the script
- [JITL-233] - When starting JobScheduler Universal Agent with the JITL SSH-Job, the job should terminate.
- [JITL-235] - The function for checking the job history in Jobs and Monitors should not return an error when the queried job does not exist or did not run
- [JITL-236] - The JITL-Job sos.scheduler.job.SOSSSHJob2JSAdapter should not log the message JSJ_I_0020 twice
- [JITL-237] - SSH Jobs should clear the StdOut and StdErr before start
- [JITL-238] - Sync job should handle the sync_session_id correct
- [JITL-239] - SSH job should work with passphrase protected publickeys
- [JITL-254] - The function for checking the job history in job monitors should only take jobs with steps>0 into consideration
- [JITL-255] - SSH Job should export the environment variables in capitals.
- [JITL-256] - Some JITL jobs read parameters only on job start
- [JITL-265] - java.sql.SQLException: Value must be between 0 and getMaxRows()
- [JITL-266] - Monitoring Interface. Oracle: SQLException: ORA-01407: cannot update ("SCHEDULER"."SCHEDULER_MON_NOTIFICATIONS"."ERROR") to NULL
- [JITL-272] - Enable POST and PUT commands with a body when calling REST Web Services
- [JITL-277] - Remove non english languages for logging
- [JITL-279] - Splitter job should create order with a sync_session_id only when this is requested by an option
- [JITL-283] - Reading speed of the parameters should be as before JITL-229
- [JITL-284] - max_orders=1 configuration has no effect when multiple simultaneous Orders are submitted to a job chain with split and sync nodes
- [JITL-285] - REST web service client should consider query parameters in the URL
- [JITL-288] - Parameter substitution has error if a parameter value contains an unquoted dollar ($)
- [JITL-293] - The JITL Job sos.scheduler.managed.JobSchedulerManagedMailJob should support SMTP authorization with SSL/STARTTLS and encrypted passwords
- [JITL-296] - The JITL Job sos.scheduler.managed.JobSchedulerManagedMailJob has always the exit code 0
- [JITL-298] - The JITL Job JobSchedulerCheckRunHistoryJSAdapterClass should allow relative names for the job and job chain parameter
- [JITL-299] - The JobSchedulerCheckRunHistory should be available with pre-processing monitors
- [JITL-301] - File operation jobs such as JobSchedulerExistsFile should work even if a filename contains square brackets
- [JITL-302] - The message ..is running and returns true should be removed
- [JITL-305] - JITL Jobs should substitute \${a_param} with order parameter a_param even when job have parameter a
- [JITL-307] - JITL Job JobSchedulerHttpPostJob should guess the encoding correctly
- [JITL-309] - Resumption: SSH job should not raise an error when exporting environment variables in the remote script
- [JITL-310] - The parameter command_delimiter has %% as default and is not changed programmatically
- [JITL-312] - SCHEDULER_MON_NOTIFICATIONS should have the correct values in ORDER_TITLE, JOB_TITLE and JOB_CHAIN_TITLE
- [JITL-313] - JITL JobSchedulerSynchronizeJobChains job should sync execution on an active cluster architecture
- [JITL-315] - Non-static REST API client should be available with JITL
- [JITL-316] - Rest Api Client should have a method to access the response headers by a key
- [JITL-317] - Notification configuration should support ${param} for substitution
- [JITL-318] - Notification handling of excluded steps does not work correctly
- [JITL-319] - DBLayer for hibernate should support .get(Class, Serializable) method
- [JITL-320] - Reporting Job ReportingFacts crashes when having more then 1000 objects and running with oracle
- [JITL-321] - Monitorig Interface. StoreResultsJob failed with the java.lang.NullPointerException exception.
- [JITL-325] - The JITL Job CreateDailyPlan should also make a first check for executed jobs
- [JITL-326] - The JITL Job CreateDailyPlan should use the internal API to execute some xml commands
- [JITL-327] - JITL and JOC should use Hibernate 5.2.6
- [JITL-328] - Event Monitor should set the exit code in the generated event correct
- [JITL-330] - JITL Jobs should no longer use the tcp port for sending xml commands.
Deprecation
- [JITL-114] - Job sos.textprocessor.SOSDocumentFactoryTextProcessor uses hostWare
- [JITL-143] - Nagios NSCA support is replaced by JobScheduler Monitoring Interface
- [JITL-171] - Use of SSH jobs based on the Trilead implementation is deprecated
- [JITL-182] - JITL SCP Job is deprecated
- [JITL-306] - JITL Jobs will no longer handle missing underscores parameter names
- [JITL-322] - Table SCHEDULER_INSTANCES no longer will be supported
- [JITL-411] - Retirement of classic configuration monitor for node parameters
- [JITL-456] - Retirement of JITL Job JobSchedulerCleanupSchedulerDbJSAdapterClass
Feature
- [JITL-165] - Namespace for parameters
- [JITL-189] - Provide solution to use database jobs with JobScheduler Universal Agent
- [JITL-191] - Use of SOSHibernateConnection class instead of SOSHibernateSession
- [JITL-192] - Provide solution to use mail jobs with JobScheduler Universal Agent
- [JITL-206] - Add the PreferredAuthentications configuration to the SSH implementation with JSch
- [JITL-213] - Enable Job scripts and Monitor scripts to use REST web services
- [JITL-214] - Batch installer for JobScheduler Universal Agent
- [JITL-217] - Provide a function for checking the job history in job monitors by use of the XML interface
- [JITL-230] - JobScheduler Monitoring Interface jobs should consider updated Timer elements
- [JITL-276] - Rewrite of parameter substitution
- [JITL-282] - JMS Integration with Message Service (ApacheMQ)
- [JITL-286] - Export of job execution history from reporting database
- [JITL-287] - Make YADE JITL jobs capable of processing file order parameter
- [JITL-289] - The job JobSchedulerCheckRunHistory should have some new possible values for the parameter query
- [JITL-290] - The job JobSchedulerCheckRunHistory should query multiple jobs with a query for each job
- [JITL-292] - Enable JobSchedulerCleanupHistory job to be executed from the command line
Sub-task
Edit/Copy Release Notes
The text area below allows the project release notes to be edited and copied to another document.