JobScheduler setup should consider that the TCP port is no longer required

Current Situation

Since version 1.11 a required http port for the JobScheduler is introduced in the setup.
The setup doesn't consider that the tcp port is no longer required
For example the update setup of the JobScheduler raises an exception if this port is missing in the scheduler.xml

Desired Behavior

• The setup should check whether the http port
  • is not empty
  • is available and should alert a message if the http port is used by another application or the JobScheduler itself is just running.
• The setup should allow that the TCP port is empty.