Scope

• Features are provided and tested for the respective milestones.
  • JS-1291 - Getting issue details... STATUS
• Milestones
  
  • TP1: Technical Preview with basic core functionality for use with shell scripts
  • TP2: Technical Preview with support for jobs and monitors using the API, file watching and more complete proxy methods
  • TP3: Technical Preview with fully featured functionality for replacement of the previous platform specific JobScheduler Agent
  • RC1: Release Candidate with functionality to replace a previous standalone instance by Master/Agent instances

Test Results

• The following list records the test results according to milestones
• Explanations
  •  test passed
  •  test failed
  •  test to be done
  • requires rework before testing
  • needs to be discussed

Feature	Test Result TP1	Test Result TP2	Test Result TP3	Comment
Core Functionality
execution of shell jobs
stdout of shell jobs is logged as info
stderr of shell jobs is logged				stderr is logged as info, probably related to JS-1329 - Getting issue details... STATUS
non-zero exit code is treated as error
live output of log in JOC
read order id with $SCHEDULER_ORDER_ID
read job parameters as environment variables with $SCHEDULE_PARAM_
read order parameters as environment variables with $SCHEDULE_PARAM_
set order parameters using SCHEDULER_RETURN_VALUES
kill a running task				process lost in JOC, but remote process is not killed
file watching				incoming files trigger a job chain, see JS-1300 - Getting issue details... STATUS , this feature will require a JobScheduler 1.10 SNAPSHOT release as a new master functionality is used.
<file_order_sink>
JobScheduler API
API jobs with javascript				Yes, but with API restrictions, see details below
API jobs with java				Yes, but with API restrictions, see details below
Shell jobs with javascript monitor				Yes, but with API restrictions, see details below
Shell jobs with java monitor				Yes, but with API restrictions, see details below
API jobs with java monitor
API jobs with javascript monitor
spooler_init()
spooler_open()
spooler_process()
spooler_close()
spooler_exit()
spooler_process_before()
spooler_process_after()
spooler_task_before()
spooler_task_after()
spooler.create_variable_set()
spooler.job()
spooler_task.params()
spooler_task.order.params()
Variable_set.set_value()
Variable_set.var()
Variable_set.merge()
Variable_set.count()
Variable_set.substitute()
Variable_set.xml()
Variable_set.set_xml()
Log.info() (and all other log levels)
Log.filename()
Log.last()
Log.set_level()
Log.level()
Log.log_file()
Log.set_mail_on_error()
Log.set_mail_on_success()
Log.set_mail_on_process()
Log.set_mail_on_warning()
Log.start_new_file()				Runs on master. Rotates log on master. Agent uses log4j based logging, rotation can be configured in log4j configuration.
Job.set_delay_after_error(int,double)
Job.set_delay_after_error(int,String)
Job.clear_delay_after_error()
Job.set_delay_order_after_setback(int, double)
Job.set_delay_order_after_setback(int, String)
Job.max_order_setbacks()
Job.set_max_order_setbacks()
Job.configuration_directory()
Job.folder_path()
Job.include_path()
Job.name()
Job.process_class()
Job.remove()
JITL Jobs
Database Operations
JobSchedulerExtractResulSet2CSVJob
JobSchedulerManagedDBReportJob
JobSchedulerManagedDatabaseJob
JobSchedulerMySQLMaintenanceMonitor
JobSchedulerMySQLReplicationMonitor
JobSchedulerPLSQLJob
SOSSQLPlusJob
File Operations
JobSchedulerExistsFile
JobSchedulerNotExistsFile
JobSchedulerCanWrite
JobSchedulerCopyFile
JobSchedulerMoveFile
JobSchedulerRemoveFile
Job Handling
JSReportAllParameters
CopyJob2OrderParameter				job is currently not working correctly, unrelated to the agent, see JITL-179 - Getting issue details... STATUS
JobChainSplitter
JobSchedulerSynchronizeJobChains
JobSchedulerCheckRunHistory				has to be migrated, needs database settings
JobSchedulerCreateSequence				will be announced to be deprecated
JobSchedulerCriticalPathUncriticalJobNodes
JobSchedulerCronAdapter
JobSchedulerLaunchAndObserve
JobSchedulerDequeueEventsJob
JobSchedulerSubmitEventJob / JobSchedulerSubmitEventMonitor
Maintenance
JobSchedulerCleanupFiles				runs on master and on agent
JobSchedulerDatabaseMonitor				runs on master, needs database connection properties from factory.ini
JobSchedulerMailBounceHandler				runs on master, needs settings from factory.ini
AgentBatchInstaller				installs old agent, must be migrated to a job that installs the new agent
CheckDailySchedule				runs on master
JSObjects2Graphviz				runs on master, works with live folder
JobSchedulerCheckExistEvents				requires local hibernate configuration file defined in parameter configuration_file jars: com.sos-berlin.jid.daily-schedule, com.sos-berlin.jid.events, com.sos-berlin.jid.scheduler-history
JobSchedulerCleanupHistory / JobSchedulerCleanupHistoryDb / JobSchedulerDeleteHistory
JobSchedulerCleanupHistoryDB
JobSchedulerDequeueMail
JobSchedulerNotificationCheckHistoryJob
JobSchedulerNotificationCleanupNotificationsJob
JobSchedulerNotificationResetNotificationsJob
JobSchedulerNotificationStoreResultsJob
JobSchedulerNotificationSystemNotifierJob
JobSchedulerRestart
JobSchedulerTimetableJob
Other jobs
JobSchedulerHttpPostJob
SOSMailReadInbox
SOSMailProcessInbox
JobSchedulerManagedMailJob
JobSchedulerSFTPSendJob, JobSchedulerSFTPReceiveJob
SOSSSHJob2JSAdapter
SOSSSHKillJobJSAdapter
SOSSSHReadPidFileJobJSAdapter
Operations
add command abort to Agent start script				see JS-1400 - Getting issue details... STATUS
command stop for Agent start script enables running processes to complete				see JS-1400 - Getting issue details... STATUS
add command status to Agent				see JS-1410 - Getting issue details... STATUS response to this command returns information about active jobs
Operation as Windows Service				see JS-1325 - Getting issue details... STATUS