Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SettingDefault ValueExplanation
https_with_hostname_verificationfalse

Specifies if hostname verification should be performed for HTTPS connections.

keystore_path../../etc/https-keystore.p12The keystore includes the private key and certificate for incoming HTTPS connections.

keystore_type

PKCS12The keystore types PKCS12 and JKS are supported.
keystore_password
The keystore is protected by a password.
key_password
The private keys in the keystore are protected by a password. Consider that for PKCS12 keystores the same password applies to all keys.
truststore_path../../etc/https-truststore.p12The truststore includes the public key and/or certificates for incoming HTTPS connections.
truststore_typePKCS12The truststore types PKCS12 and JKS are supported.
truststore_password
The truststore is protected by a password.

Login Settings

SettingDefault ValueExplanation
custom_logo_name
The logo file indicated by this name has to be located in ./jetty_base/webapps/root/ext/images
custom_logo_height
Display sequence of JOC Cockpit widget in Dashboard view
custom_logo_positionbottomPossible values for the position are top and bottom. Possible units are specified according to: https://www.w3schools.com/cssref/css_units.asp (default px).
enable_remember_metrueThe login dialog offers a 'Remember Me' checkbox. If this setting is false then this checkbox is hidden and unchecked.

Dashboard Settings

SettingDefault ValueExplanation
titlePRIMARY JOC COCKPIT
SECONDARY JOC COCKPIT
Title of the JOC Cockpit Cluster Status widget in the Dashboard view. The default value depends on the installer option for a Primary or Secondary JOC Cockpit instance.
ordering0
1
Order of appearance in JOC Cockpit Cluster Status widget in Dashboard view. The default value depends on the installer option for a Primary or Secondary JOC Cockpit instance.
  • title: The title of the respective JOC Cockpit instance as visible from the Cluster Status widget of the JS7 Dashboard view.
  • ordering: The order of appearance of the respective JOC Cockpit instance with the Cluster Status widget of the JS7 Dashboard view. An ordering 0 indicates the leftmost occurrence.

Daily Plan Settings

SettingDefault ValueExplanation
daily_plan_timezoneUTCSpecifies the time zone that is used to calculate the period of the Daily Plan
daily_plan_period_begin00:00
                                    
Specifies the offset that is applied to the time zone indicated with the daily_plan_timezone attribute.

Audit Log Settings

SettingDefault ValueExplanation
force_comments_for_audit_logfalseRequests all web services that modify JobScheduler objects by operations such as "add order", "suspend order" etc. to require specification of a comment that explains the reason for the operation. With this flag being set to true such comments are enforced.
commentsSystem maintenance; \
Repeat execution; \
Business requirement; \
Restart failed execution; \
Re-instantiate stopped object; \ Temporary stop; \
Change of JobScheduler object; \
Rerun with parameter changes; \
Change of external dependency; \
Application deployment and upgrade
Specifies the offset that is applied to the time zone indicated with the daily_plan_timezone attribute.

Operational Settings

SettingDefault ValueExplanation
default_profile_accountrootThe default account holds profile settings that are applied by default to new accounts. Such accounts can later on modify their profile settings individually.

show_view_dashboard
show_view_dailyplan
show_view_workflows
show_view_filetransfers
show_view_resources
show_view_history
show_view_auditlog
show_view_jobstreams
show_view_configuration

                                    

Normally, the user permissions control if a view such as dashboard, workflows etc. is displayed or hidden. The settings allow to display (=true) or to hide (=false) a view independently of the permissions. If the assigned value is empty (=default) then the user permissions are applied.

Installation Settings

SettingDefault ValueExplanation
security_levellow

JOC Cockpit is installed for a security level used for signing of deployment objects such as workflows: 

  • high
    • public PGP keys are stored for verification only
    • all signing will be done externally outside of JOC Cockpit
  • medium
    • a private PGP key will be stored for signing, signing will be done automatically with the provided key
  • low
    no keys will be stored, signing will be done internally with default keys
  • Changes to the above settings at run-time are ignored. Instead, the above settings are applied by the installer for information purposes.

...