JobScheduler URL mapping for the JOC web services

Current Situation

• In almost all cases a JobScheduler Master has a URL in the form http(s)://[jobSchedulerHost]:[jobSchedulerHTTP(S)Port].
• JOC Cockpit web services know this URL because the JobScheduler Master stores this information to the Reporting Database.
• If the JobScheduler Master is running in a docker container or behind a reverse proxy then the URL can be different and the JobScheduler Master cannot know by which URL it is accessible.
  In this case the JOC Cockpit web services use a non-working URL for requests to the JobScheduler Master and a URL mapping is required.

Desired Behavior

• A URL mapping is introduced for JOC's web services with the configuration file
  ./jetty_base/resources/joc/joc.configuration.properties.
  • This file is not created by the installer as it is exclusively required to specify optional configuration items.
  • A sample file joc.configuration.properties-example is available that you can rename as a starting point for your version of the file.
• A setting in this property file has the form

  jobscheduler_url_myJobSchedulerHost1_myJobschedulerHTTPPort1 = url1
  jobscheduler_url_myJobSchedulerHost2_myJobschedulerHTTPPort2 = url2
  

• all entries have a prefix jobscheduler_url_
• Please note that the key has to be in lowercase and contains always the HTTP port even if the URL uses the HTTPS protocol
• Each mapping is added to a new line.