Page History

...

• https_with_hostname_verification

  • This setting should be considered carefully. Effectively it forces the hostname host name in an HTTPS connection to a JobScheduler Master to be verified from the host's certificate. This guarantees that the certificate has been created for the respective host (FQDN). 

  • With this setting being assigned the value false no host name verification takes place and the HTTPS connection is vulnerable to man-in-the-middle attacks.

• configuration_file

  • This file is used for configuration details that are independent from the JOC Cockpit installation, see chapter The joc.configuration.properties File.

• truststore_path, truststore_type, truststore_password

  • A trust store is used if an HTTPS connection between clients, e.g. user browsers, and JOC Cockpit is used. For details see the JOC Cockpit - HTTPS Authentication article.

• force_comments_for_audit_log

  • Comments can be added whenever an operation is performed that modifies a JobScheduler object, e.g. if a job or job chain is started.

  • Basically a user can choose in his profile to add comments which pops up a dialog box to select or enter a comment. If this profile setting is not active then a number of operations, such as starting a job, are performed immediately without additional dialog.
  • With the force_comments_for_audit_log setting in place all users are forced to add a comment when modifying a JobScheduler object - independent of their profile settings.

• custom_logo_name, custom_logo_height, custom_logo_position

  • The custom logo is displayed on the login page.

  • Jira
    server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-473

• default_profile_account
  • The user profile of the account specified for this setting provides the default values for the profiles of new users.
  • An account is specified exactly as the user would type for login. If LDAP Configuration is in place then the domain account is specified, optionally including the domain, e.g. domain\account or account@domain or by use of the samAccountName or the respective LDAP attribute configured by the JOC Cockpit administrator.

  • Jira
    server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-477

• comments
  • Add/modify/replace items to the list of comments in any language. 
  • Each comment ends with a semicolon. If comments are to follow then the line for the current comment ends with a backslash.

Anchor
joc.configuration.properties joc.configuration.properties

The joc.configuration.properties File

This file is used for configuration details that are independent from a JOC Cockpit installation.

...