Page History

...

• 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.
    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 Modified
      
      

  • 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
    

  • 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 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.

  • 
    
    
    

...