Page History

...

• Language Selection

  • Select the language to be used for the setup: English and German are available.
    
    
    
    

• Step 1 - Welcome Screen
  

• Step 2 - Licensing Agreement

  • The License Agreement shown in Step 2 of the installation has to be accepted before installation can take place.

    
    
    

• Step 3 - Target Path for the Installation

  • The path to the installation directory for the JOC Cockpit program files - referred to later in this page as the joc_installation_directory - is set in this step.

  • The default installation paths for the JOC Cockpit are:

    • /opt/sos-berlin.com/joc on Linux systems and

    • C:\Program Files\sos-berlin.com\joc on Windows.
  • Users can use the Step 3 installation form shown below to specify their own installation path for the JOC Cockpit if required. 
    
    
    
    

• Anchor
  jetty-base jetty-base

  Step 4 - Jetty Installation & Configuration

  • The JOC Cockpit requires a Java-capable web server and comes with a Jetty server. Step 4 allows system administrators to specify whether this web server is to be installed and if so, to specify its configuration - i.e. the port(s) it uses, installation path, memory pool, etc..
  • The Install JOC ... including Jetty checkbox specifies whether the Jetty web server should be installed.

  • Default Paths

  • While the Jetty web server delivered with the JOC Cockpit is installed in the joc_installation_directory, which was configured in the previous step - the Jetty configuration files are installed in the jetty_base directory. The Jetty Base field in the form shown in the screenshot can be used to set the jetty_base directory. 
    • The default path to the jetty_base directory on Linux systems leads to the user's home directory:
      • e.g. /home/sos/sos-berlin.com/joc
    • Log files are saved by default in:
      

      • /var/log/sos-berlin.com/joc on Linux systems.

    • The default path to the jetty_base directory and log files on Windows systems is: 
      • C:\ProgramData\sos-berlin.com\joc .

  • 

  • Note that if If the Jetty delivered with the JOC Cockpit is not to be installed and either an alternative Jetty installation or another web server is to be used, then relevant configuration files for such a server such as the shiro.ini and joc.properties files will still be written to the file system. These files can then be moved by the system administrator to the suitable location for their web server as required. See the Configuration with Alternative Web Servers section below for more information.

• Step 5 - Specify the Reporting DBMS

  • Choose the DBMS to be used by the JOC Cockpit for the Reporting Database.
    Caution: the order in which the Reporting and JobScheduler Databases are configured is the opposite to that used in the installation of the JobScheduler. 

  • 
    
    
    

• Step 6 - Configure the Reporting Database Connection

  • Specify the parameters for the connection to the Reporting Database. 

  • 

  • It will be probably be obvious from the names given to the parameters in the screenshot above that the values are for a database to be used by the JobScheduler. In this case the Reporting Database Tables will be integrated in the JobScheduler Database. This will be described in the next step.

  • The database configuration for the JOC Cockpit is written to an XML file during installation and saved in the jetty_base/resources/joc folder.
    The default name of the database configuration file is:

    • reporting.hibernate.cfg.xml

    This file can be modified at a later date if required using a text editor. The JOC Cockpit service will then have to be restarted before changes made to this file are implemented.

  • The name and location of the database configuration file itself is specified in the joc.properties file, which can also be found in the jetty_base/resources/joc folder.

...

• Step 7 - Specify the JDBC Driver for the Reporting Database Connection

  • Specify if an JDBC driver provided with the installation should be used for the Reporting Database Connection or whether an external driver is required.
    Image Removed
    

• Step 8 - Specify the Database Connection Used by the JobScheduler

  • Specify whether a separate connection it to be specified for the JobScheduler Database
    Image Removed

  • If the JobScheduler(s) and JOC Cockpit share the same database then clicking Next will cause the Installation to proceed to Step 10. This step starts the installation process itself and changes to the configuration are no longer possible.  
  • If the JobScheduler(s) and JOC Cockpit use separate databases then the checkbox in the form should be deselected. In this case, clicking Next will cause the Installation to proceed to the specification of the DBMS and the connection parameters for the JobScheduler database, which are described next.

• Step 9 - Specify the JobScheduler DBMS

  • This form is identical to those already shown for the Reporting Database in Steps 5 to 8 above.
• • The information shown in this form depends on the DBMS previously selected:
    • The jTDS JDBC® driver delivered with the JobScheduler is only shown as an option when Sybase^® or Microsoft SQL Server^® DBMSs have been specified.
    • If you have specified a MySql^® DBMS then you will get a checkbox for specifying whether you want to use the MariaDB^® JDBC^® driver provided with the JobScheduler. 
    • If you do not check the jTDS JDBC^® or the MariaDB JDBC drivers then you must enter your own JDBC^® driver in the form shown below.
    • 
      Image Added
      
      

  • Configuring the JDBC Driver-URL for Oracle RAC databases

    The JDBC driver URL for Oracle RAC databases should be entered in the Host field of the database connection form. For example:

    Code Block
    jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=OFF)(FAILOVER=ON) (ADDRESS=(PROTOCOL=TCP)(HOST=tst-db1.myco.com)(PORT=1604)) (ADDRESS=(PROTOCOL=TCP)(HOST=tst-db2.myco.com)(PORT=1604))) (CONNECT_DATA=(SERVICE_NAME=mydb1.myco.com)(SERVER=DEDICATED)))

    In addition the Schema and Port fields should be left empty.
    
    

• Step 8 - Specify the Database Connection Used by the JobScheduler

  • Specify whether a separate connection it to be specified for the JobScheduler Database
    Image Added

  • If the JobScheduler(s) and JOC Cockpit share the same database then clicking Next will cause the Installation to proceed to Step 10. This step starts the installation process itself and changes to the configuration are no longer possible.  
  • If the JobScheduler(s) and JOC Cockpit use separate databases then the checkbox in the form should be deselected. In this case, clicking Next will cause the Installation to proceed to the specification of the DBMS and the connection parameters for the JobScheduler database, which are described next.

• Step 9 - Specify the JobScheduler DBMS

  • This form is identical to those already shown for the Reporting Database in Steps 5 to 8 above.

• Step 10 - Configure the JobScheduler Database Connection

  • Specify the parameters for the connection to the JobScheduler Database.

    • The DBMS type can be found in the database configuration for job history section of the $JOBSCHEDULER_DATA/factory.ini file of one of the JobSchedulers to be operated from the JOC Cockpit, where $JOBSCHEDULER_DATA is defined in the JobScheduler Master Installation - 2 - Dialog Installation article.
  • The database configuration for the JOC Cockpit is written to an XML file during installation and saved

  Step 10 - Configure the JobScheduler Database Connection

• Specify the parameters for the connection to the JobScheduler Database.

  • The DBMS type can be found in the database configuration for job history section of the $JOBSCHEDULER_DATA/factory.ini file of one of the JobSchedulers to be operated from the JOC Cockpit, where $JOBSCHEDULER_DATA is defined in the JobScheduler Master Installation - 2 - Dialog Installation article.
• The database configuration for the JOC Cockpit is written to an XML file during installation and saved in the jetty_base/resources/joc folder.
  The default name of the database configuration file is:
  
  • jobscheduler.hibernate.cfg.xml

• This file can be modified at a later date if required using a text editor. A JOC Cockpit user will then have to log in again before changes made to this file are implemented.

• The name and location of the database configuration file itself is specified in the joc.properties file, which can also be found in the jetty_base/resources/joc folder.

Image Removed


Step 11 - Processing the Installation

• This step shows the progress of the first part of the installation procedure.

• Changes to the installation configuration can no longer be made once this step has started.
  Instead configuration files such as those in the jetty_base/resources/joc folder can modified manually and then the JOC Cockpit restarted.
  Image Removed
  

Step 12 - External Processes

• folder.
  The default name of the database configuration file is:
  
  • jobscheduler.hibernate.cfg.xml

• This file can be modified at a later date if required using a text editor. A JOC Cockpit user will then have to log in again before changes made to this file are implemented.

• The name and location of the database configuration file itself is specified in the joc.properties file, which can also

• This step shows the progress of the second part of the installation procedure.

• Image Removed

• The information shown in this step will be written to the installation log file, which can be found in the jetty_base/logs folderresources/joc folder.

• 
  Image Added
  
  

• Step

  13

  11 -

  Completion

  • The last step of the installation shows a summary of the installation (success/error) and paths to relevant information.

    Image Removed

  • Note that if a problem occurs during installation a warning message will be shown here and a link to the installation log file will be provided.

• Operation

  • Go to the Initial Operation section of this article for information about opening the JOC Cockpit Interface.

Batch installation

Configuration

The joc_install.xml file has to be configured with parameters such as the installation path, database connections, etc. before installation can start.

The joc_install.xml file is shown in the code listing below. The extensive comments are intended to be self-explanatory. 

• Processing the Installation

  • This step shows the progress of the first part of the installation procedure.

  • Changes to the installation configuration can no longer be made once this step has started.
    Instead configuration files such as those in the jetty_base/resources/joc folder can modified manually and then the JOC Cockpit restarted.
    Image Added
    
    

• Step 12 - External Processes

  • This step shows the progress of the second part of the installation procedure.

  • Image Added

  • The information shown in this step will be written to the installation log file, which can be found in the jetty_base/logs folder

• Step 13 - Completion

  • The last step of the installation shows a summary of the installation (success/error) and paths to relevant information.

    Image Added

  • Note that if a problem occurs during installation a warning message will be shown here and a link to the installation log file will be provided.

• Operation

  • Go to the Initial Operation section of this article for information about opening the JOC Cockpit Interface.

Batch installation

Configuration

The joc_install.xml file has to be configured with parameters such as the installation path, database connections, etc. before installation can start.

The joc_install.xml file is shown in the code listing below. The extensive comments are intended to be self-explanatory. 

• Code Block
  language xml title Configuration of the joc_install.xml file linenumbers true
  Code Block
  language xml title Configuration of the joc_install.xml file linenumbers true collapse true
  <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- XML configuration file for JOC If you call the installer with this XML file then you accept at the same time the terms of the licence agreement under GNU GPL 2.0 License (see http://www.gnu.org/licenses/gpl-2.0.html) --> <AutomatedInstallation langpack="eng"> <com.izforge.izpack.panels.UserInputPanel id="home"> <userInput/> </com.izforge.izpack.panels.UserInputPanel> <com.izforge.izpack.panels.HTMLLicencePanel id="gpl_licence"/> <com.izforge.izpack.panels.TargetPanel id="target"> <!-- SELECT THE INSTALLATION PATH It must be absolute! For example: /opt/sos-berlin.com/joc on Linux C:\Program Files\sos-berlin.com\joc on Windows --> <installpath>[:choose absolute installation path of JOC:]</installpath> </com.izforge.izpack.panels.TargetPanel> <com.izforge.izpack.panels.UserInputPanel id="jetty"> <userInput> <!-- JOC requires a servlet container such as Jetty. If a servlet container already installed then you can use it. Otherwise a Jetty will be installed in addition if withJettyInstall=yes. You need root permissions to install JOC with Jetty. --> <entry key="withJettyInstall" value="yes"/> <entry key="jettyPort" value="4446"/> <!-- Specify the name of the Windows service or Linux Daemon (default: joc). Only necessary for multiple instances of JOC on one server. It must be unique per server. This entry is deactivated by a comment because it MUST NOT BE CHANGED DURING OVER-INSTALLATION! --> <!-- <entry key="jettyServiceName" value="joc"/> --> <!-- Only necessary for Windows --> <entry key="jettyStopPort" value="40446"/> <!-- Only necessary for Unix (root permissions required) --> <entry key="withJocInstallAsDaemon" value="yes"/> <!-- Path to Jetty base directory For example: /home/[user]/sos-berlin.com/joc on Linux C:\ProgramData\sos-berlin.com\joc on Windows --> <entry key="jettyBaseDir" value=""/> <!-- Java options for Jetty. --> <!-- Initial memory pool (-Xms) in MB --> <entry key="jettyOptionXms" value="128"/> <!-- Maximum memory pool (-Xmx) in MB --> <entry key="jettyOptionXmx" value="512"/> <!-- Thread stack size (-Xss) in KB --> <entry key="jettyOptionXss" value="4000"/> <!-- Further Java options --> <entry key="jettyOptions" value=""/> </userInput> </com.izforge.izpack.panels.UserInputPanel> <com.izforge.izpack.panels.UserInputPanel id="reportingDatabase"> <userInput> <!-- Reporting Database Configuration --> <!-- Database connection settings can be specified with following entries such as databaseHost, databasePort, ... or by a hibernate configuration file Posible values are 'withoutHibernateFile' (default) and 'withHibernateFile'. --> <entry key="reporting.databaseConfigurationMethod" value="withoutHibernateFile"/> <!-- Choose the database management system. Supported values are 'mysql' for MySQL, 'oracle' for Oracle, 'mssql' for MS SQL Server, 'pgsql' for PostgreSQL. Only if reporting.databaseConfigurationMethod=withoutHibernateFile --> <entry key="reporting.databaseDbms" value="mysql"/> <!-- Path to a hibernate configuration file if reporting.databaseConfigurationMethod=withHibernateFile --> <entry key="reporting.hibernateConfFile" value=""/> </userInput> </com.izforge.izpack.panels.UserInputPanel> <com.izforge.izpack.panels.UserInputPanel id="reportingDbconnection"> <userInput> <!-- Reporting Database Configuration if reporting.databaseConfigurationMethod=withoutHibernateFile --> <!-- Enter the name or ip address of the database host This entry can also be used to configure the URL(s) for Oracle RAC databases. For example: <entry key="reporting.databaseHost" value="(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=OFF)(FAILOVER=ON) (ADDRESS=(PROTOCOL=TCP)(HOST=tst-db1.myco.com)(PORT=1604)) (ADDRESS=(PROTOCOL=TCP)(HOST=tst-db2.myco.com)(PORT=1604))) (CONNECT_DATA=(SERVICE_NAME=mydb1.myco.com)(SERVER=DEDICATED)))"/> The "reporting.databaseSchema" and "reporting.databasePort" entries should then be left empty. --> <entry key="reporting.databaseHost" value=""/> <!-- Enter the port number for the database instance. Default ports are for MySQL 3306, Oracle 1521, MS SQL Server 1433, postgreSQL 5432. --> <entry key="reporting.databasePort" value=""/> <!-- Enter the schema --> <entry key="reporting.databaseSchema" value=""/> <!-- Enter the user name for database access --> <entry key="reporting.databaseUser" value=""/> <!-- Enter the password for database access --> <entry key="reporting.databasePassword" value=""/> </userInput> </com.izforge.izpack.panels.UserInputPanel> <com.izforge.izpack.panels.UserInputPanel id="reportingJdbc"> <userInput> <!-- Reporting Database Configuration NOT SUPPORTED FOR SYBASE AND DB2 --> <!-- You can specify an external JDBC connector then set reporting.internalConnector = no For license reasons MySQL, MS SQL Server and Oracle ojdbc7 JDBC drivers are not provided. Alternatively you can use the mariadb JDBC Driver for MySQL and the jTDS JDBC Driver for MS SQL Server and Sybase which is provided. An Oracle ojdbc6 JDBC driver is also provided. --> <!-- You can choose between 'yes' or 'no' for using the internal JDBC connector or not --> <entry key="reporting.internalConnector" value="yes"/> <!-- Select the path to JDBC Driver --> <entry key="reporting.connector" value=""/> </userInput> </com.izforge.izpack.panels.UserInputPanel> <com.izforge.izpack.panels.UserInputPanel id="database"> <userInput> <!-- JobScheduler Database Configuration --> <!-- Set 'yes' if the Reporting and the JobScheduler database are the same. If 'yes' then further JobScheduler database variables are ignored. --> <entry key="sameDbConnection" value="yes"/> <!-- Database connection settings can be specified with following entries such as databaseHost, databasePort, ... or by a hibernate configuration file Posible values are 'withoutHibernateFile' (default) and 'withHibernateFile'. --> <entry key="databaseConfigurationMethod" value="withoutHibernateFile"/> <!-- Choose the database management system. Supported values are 'mysql' for MySQL, 'oracle' for Oracle, 'mssql' for MS SQL Server, 'pgsql' for PostgreSQL, 'db2' for DB2 and 'sybase' for Sybase. Only if databaseConfigurationMethod=withoutHibernateFile --> <entry key="databaseDbms" value=""/> <!-- Path to a hibernate configuration file if databaseConfigurationMethod=withHibernateFile --> <entry key="hibernateConfFile" value=""/> </userInput> </com.izforge.izpack.panels.UserInputPanel> <com.izforge.izpack.panels.UserInputPanel id="dbconnection"> <userInput> <!-- JobScheduler Database Configuration if databaseConfigurationMethod=withoutHibernateFile --> <!-- Enter the name or ip address of the database host This entry can also be used to configure the URL(s) for Oracle RAC databases. For example: <entry key="databaseHost" value="(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=OFF)(FAILOVER=ON) (ADDRESS=(PROTOCOL=TCP)(HOST=tst-db1.myco.com)(PORT=1604)) (ADDRESS=(PROTOCOL=TCP)(HOST=tst-db2.myco.com)(PORT=1604))) (CONNECT_DATA=(SERVICE_NAME=mydb1.myco.com)(SERVER=DEDICATED)))"/> The "databaseSchema" and "databasePort" entries should then be left empty. --> <entry key="databaseHost" value=""/> <!-- Enter the port number for the database instance. Default ports are for MySQL 3306, Oracle 1521, MS SQL Server 1433, postgreSQL 5432, DB2 50000, Sybase 5000. --> <entry key="databasePort" value=""/> <!-- Enter the schema --> <entry key="databaseSchema" value=""/> <!-- Enter the user name for database access --> <entry key="databaseUser" value=""/> <!-- Enter the password for database access --> <entry key="databasePassword" value=""/> </userInput> </com.izforge.izpack.panels.UserInputPanel> <com.izforge.izpack.panels.UserInputPanel id="jdbc"> <userInput> <!-- JobScheduler Database Configuration --> <!-- You can specify an external JDBC connector then set internalConnector = no For license reasons MySQL, Sybase, MS SQL Server and Oracle ojdbc7 JDBC drivers are not provided. Alternatively you can use the mariadb JDBC Driver for MySQL and the jTDS JDBC Driver for MS SQL Server and Sybase which is provided. An Oracle ojdbc6 JDBC driver is also provided. An internal JDBC connector for DB2 is not available --> <!-- You can choose between 'yes' or 'no' for using the internal JDBC connector or not --> <entry key="internalConnector" value="yes"/> <!-- Select the path to JDBC Driver --> <entry key="connector" value=""/> <!-- Only for DB2: Select the path to DB2 license file for JDBC Driver --> <entry key="connectorLicense" value=""/> </userInput> </com.izforge.izpack.panels.UserInputPanel> <com.izforge.izpack.panels.UserInputPanel id="end"> <userInput/> </com.izforge.izpack.panels.UserInputPanel> <com.izforge.izpack.panels.InstallPanel id="install"/> <com.izforge.izpack.panels.ProcessPanel id="process"/> <com.izforge.izpack.panels.FinishPanel id="finish"/> </AutomatedInstallation>

...

• ProgramData
  • sos-berlin.com
    • joc
      • joc_home (symlink, remains after uninstall)
      • logs (directory with files, remains after uninstall)
      • resources (remains after uninstall and (empty) after full uninstall)
        • joc
          
          • jobscheduler.hibernate.cfg.xml (remains after uninstall if modified)
          • joc.properties (remains after uninstall)
          • log4j.properties (remains after uninstall if modified)
          • reporting.hibernate.cfg.xml (remains after uninstall if modified)
          • shiro.ini (remains after uninstall)
          • shiro.ini-example (only added if shiro.ini file is found)
      • temp (directory with files, remains after uninstall)
      • webapps
      • start.ini (file, remains after uninstall)

...

• Program Files
  • sos-berlin.com
    
    • joc
      
      • install (directory with files)
        • install_jetty_base.cmd
        • update_jetty_base.cmd
      • jetty (directory with files)
      • jetty_base (symlink)
      • service
      • Uninstaller (directory, the empty remains after uninstall and full uninstall)
        • uninstall.cmd
        • uninstaller.jar
      • .jocinstallinformation (file, remains after uninstall)
      • joc_install.xml (file, remains after uninstall)

...

################################################################################
### Path to log4j configuration file. Path can be absolute or relative
### to this file.
 
log4j.configuration = log4j.properties

################################################################################
### Path to hibernate configuration file of JOC's reporting database. 
### Path can be absolute or relative to this file.
 
hibernate_configuration_file = reporting.hibernate.cfg.xml

################################################################################
### Path to hibernate configuration file of a JobScheduler database. 
### Path can be absolute or relative to this file.
### The key must have the format 'hibernate_configuration_file_<jobschedulerId>'
### for a specific JobScheduler (cluster) 
### or 'hibernate_configuration_scheduler_default_file'
### for all JobSchedulers which don't have a specific setting.
 
hibernate_configuration_scheduler_default_file = jobscheduler.hibernate.cfg.xml

################################################################################
### The time (in milliseconds) to establish the connection with the 
### remote host. Default = 2

jobscheduler_connection_timeout = 2

################################################################################
### The time (in milliseconds) waiting for data after the connection
### was established; maximum time of inactivity between two data packets.
### Default = 25

jobscheduler_socket_timeout = 25

################################################################################
### Should hostname verification be carried out for https certificate. 
### Default false
 
https_with_hostname_verification = false

################################################################################
### Location of the Javaconfiguration trustorefile which contains the certificates of each 
### JobScheduler Master for HTTPS connections. with e.g. url mapping, etc.
### Path can be absolute or relative
### to this file.
#truststore_path
# configuration_file = joc../../etc/joc.jksconfiguration.properties

################################################################################
### RequestsLocation, totype alland webpassword servicesof whichthe modifyJava JobSchedulertruststore objectswhich suchcontains asthe 
### "start order", "stop job" etc. can contain a comment to certificates of eachJobScheduler Master for HTTPS connections. Path can be 
### absolute or relative to this file.

# truststore_path = ../../etc/joc.jks
# truststore_type = PKCS12
# truststore_password = 

################################################################################
### Requests to all web services which modify JobScheduler objects such as 
### "start order", "stop job" etc. can contain a comment to describe the reason.
### This flag controls if the comment is required or not. Default false

force_comments_for_audit_log = false

################################################################################
### Pre-definedSettings commentsfor useda forcustom examplelogo infile on the 'reasons' describing actions in login page 
### theThe audit log.
comments = System 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 upgradelogo file has to be located in ./jetty_base/webapps/root/ext/images
### Possible units for width are according to
### https://www.w3schools.com/cssref/css_units.asp (default px)
### Possible values for the position are "top" or "bottom" (default=bottom).

custom_logo_name = 
custom_logo_height = 
custom_logo_position = 

################################################################################
### A default profile should be available that includes any profile settings 
### that are applied by default to new users.

default_profile_account = root

################################################################################
### Pre-defined comments used for example in the 'reasons' describing actions in 
### the audit log.

comments = System 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

Explanations

• https_with_hostname_verification

  • This setting should be considered carefully. Effectively it forces the 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.

This file is not changed during an update of the JOC Cockpit.

The default location of this file after installation is the resources/joc folder.

Detailed descriptions of each parameter are included in the file and are intended to be self-explanatory.

################################################################################
### 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. 
### Here you can set a url mapping in the form
###
###          jobscheduler_url_myJobSchedulerHost_myJobschedulerHTTPPort = url
###
### 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 


# jobscheduler_url_localhost_40444 = http://docker_url

Explanations

• jobscheduler_url_<host>_<port>
  • This setting is used if a JobScheduler Master is operated, e.g. in a Docker environment, without DNS support and requires URL mapping.
  • On startup of JobScheduler Master it will propagate its hostname and port to the Reporting Database.
  • If this hostname is not publicly known in the network, e.g has not been added to the DNS, then JOC Cockpit cannot address the JobScheduler Master.
  • This setting allows to map the URL reported by the Master to the Reporting Database to a URL that is accessible by JOC Cockpit, e.g. a URL that includes an IP address.

Database Configuration Files

...

• on Linux systems in the directory:
  • /etc/default/joc if the installer was executed by the root account.
  • /home/<user>/jocrc if the installer was executed by a user account (./setup.sh -u <user>).
  • On startup JOC Cockpit will check the /home/<user>/jocrc file and only if this cannot be found it will check the /etc/default/joc  file. 
• on Windows systems in the Registry under:
  • HKLM\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\sos_joc\Parameters\Java
• Java Memory options can also be configured by opening the sos_jocw.exe which can be found in the joc_home\service directory.

...

• Tips from a user on Installation with Tomcat

...