JITL Jobs should no longer use the tcp port for sending xml commands.

Current Situation

when JITL are sending commands they usually are using the clase JobSchedulerCommand. There a socket tcp connection to the JobScheduler instance will be established to invoke the xml command.

Desired Behaviour

As the tcp port is deprecated, JobSchedulerCommand should send the command with http post.

Effected

The command line call

java -cp com.sos.scheduler-xxx.jar:log4j-xxx.jar sos.scheduler.command.SOSSchedulerCommand  -host <host> -port <port> [-timeout <timeout>]  <xml-command>

The static calls

• SOSSchedulerCommand.addOrder(host,port,state,jobChain)
• SOSSchedulerCommand.addJob(host,port,job)
• SOSSchedulerCommand.sendCommand(host,port,job,command)

Jobs/Monitors

• com.sos.jitl.eventing.EventMonitorProcessBefore
• com.sos.jitl.eventing.EventMonitorProcessAfter
• com.sos.jitl.eventing.EventMonitorTaskBefore
• com.sos.jitl.eventing.EventMonitorTaskAfter
• com.sos.jitl.eventing.JSEventsClientJSAdapterClass
• sos.scheduler.job.JobSchedulerEventJob
• sos.scheduler.job.JobSchedulerDequeueEventsJob
• sos.scheduler.job.JobSchedulerRemoteCommandJob
• sos.scheduler.job.JobSchedulerSignalJob
• sos.scheduler.job.JobSchedulerSubmitEventJob