Introduction
- JOC Cockpit makes use of the
joc.properties
configuration file populated by installation options. This file can be found in the following locations:- Windows:
C:\ProgramData\sos-berlin.com\js7\joc\resources\joc\joc.properties
- Linux:
/var/sos-berlin.com/js7/joc/resources/joc/joc.properties
- Windows:
- Restart the JOC Cockpit instance to apply changes to its configuration file.
Installation Options
Logger Settings
Setting | Sample Value | Explanation |
---|---|---|
log4j.configuration | log4j2.xml | Specifies the file name of the log4j2 configuration file to be used. This file is expected with the configuration folder |
- For details see JS7 - Log Rotation and JS7 - Log Levels and Debug Options
Database Connection Settings
Setting | Sample Value | Explanation |
---|---|---|
hibernate_configuration_file | hibernate.cfg.xml | Specifies the connection URL, account and authentication for the connection to the database. |
- For details see JS7 - Database
Controller Connection Settings
Setting | Sample Value | Explanation |
---|---|---|
jobscheduler_connection_timeout | 2 | Specifies the time (in seconds) to establish a connection to a Controller. |
jobscheduler_socket_timeout | 5 | The time (in seconds) waiting for data after the connection to a Controller is established. Technically the setting specifies the maximum duration for inactivity between two data packets. |
HTTPS Connection Settings
Setting | Sample Value | Explanation |
---|---|---|
https_with_hostname_verification | true | Specifies if hostname verification should be performed for HTTPS connections. |
keystore_path | ../../resources/https-keystore.p12 | The keystore includes the private key and server certificate created for incoming HTTPS connections (Server Authentication) and optionally for outgoing connections that request mutual authentication (Client Authentication). If separate certificates should be used then consider to store the Client Authentication certificate in the client keystore, see below. |
| PKCS12 | The 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. Note that for PKCS12 keystores the same password applies to all keys. | |
client_keystore_path | ../../resources/https-client-keystore.p12 | The client keystore includes the private key and certificate for outgoing connections that request mutual authentication (Client Authentication) from a separate certificate. If a certificate is created for both Server Authentication and Client Authentication purposes then the keystore has to be used, see above. |
| PKCS12 | The client keystore types PKCS12 and JKS are supported. |
client_keystore_password | The client keystore is protected by a password. | |
client_key_password | The private keys in the client keystore are protected by a password. Note that for PKCS12 keystores the same password applies to all keys. | |
truststore_path | ../../resources/https-truststore.p12 | The truststore includes the public key and/or certificates for outgoing HTTPS connections (Server Authentication). |
truststore_type | PKCS12 | The truststore types PKCS12 and JKS are supported. |
truststore_password | The truststore is protected by a password. |
Custom Logo Settings
Setting | Default Value | Explanation |
---|---|---|
custom_logo_name | The logo file indicated by this name has to be located in ./jetty_base/webapps/root/ext/images | |
custom_logo_height | The logo height in pixel. Possible units are specified according to: https://www.w3schools.com/cssref/css_units.asp (default px). | |
custom_logo_position | bottom | Possible values for the position are top and bottom . |
Dashboard Settings
Setting | Sample Value | Explanation |
---|---|---|
title | PRIMARY 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. |
ordering | 0 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 a JOC Cockpit instance as visible from the Cluster Status widget of the JS7 Dashboard view.ordering
: The order of appearance of a JOC Cockpit instance with the Cluster Status widget of the JS7 Dashboard view. An ordering 0 indicates the leftmost occurrence.
Installation Options
Setting | Sample Value | Explanation |
---|---|---|
security_level | low | JOC Cockpit is installed for a security level used for signing of deployment objects such as workflows:
|
- Changes to the above setting are ignored. Instead, the above setting is applied by the installer for informational purposes only.
- To modify the security level of JOC Cockpit re-run the installer and select the respective installation option.
Overview
Content Tools