...
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.
- Specify if an JDBC driver provided with the installation should be used for the Reporting Database Connection or whether an external driver is required.
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 DBMS type can be found in the database configuration for job history section of the
- 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 thejetty_base/resources/joc
folder.
...