Page History

...

The JOC Cockpit can be operated with HTTPS. However, due to problems often experienced with certificate validation, we do not recommend configuring the JOC Cockpit to use HTTPS during the initial installation and configuration procedure. Instead, we recommend that the JOC Cockpit is installed and tested with HTTP and the default shiro Shiro authentication and that HTTPS and, if required, LDAP authentication are is added in a second step. See the JOC Cockpit - Authentication and Authorization and JOC Cockpit - HTTPS Authentication articles for more information.

...

Language Selection
- Select the language to be used for the setup: English and German are available.
Step 1 - Welcome Screen
Image RemovedImage Added

Step 2 - Licensing Agreement
- The License Agreement shown in Step 2 of the installation has to be accepted before installation can take place.
  Image AddedImage Removed
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/js7/joc on Linux systems and
  - C:\Program Files\sos-berlin.com\js7\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.
  Image RemovedImage Added

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 the 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/js7/joc
  - Log files are saved by default in:
    - /var/log/sos-berlin.com//js7/joc on Linux systems.
  - The default path to the jetty_base directory and log files on Windows systems is:
    - C:\ProgramData\sos-berlin.com\js7\joc .
      Image Modified
- 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 a 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.

Image Removed

Step 6 - Configure the Reporting Database Connection
- Specify the parameters for the connection to the Reporting Database.
- Image Removed
- 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

JOC Configuration
- The JS7 JOC Cockpit can be installed in a cluster. So if the JOC Cockpit is installed as a cluster it is required to provide a title to the JOC. By default the title is joc, this can be modified as per the user.
  Image Added
- The security level for the signing mechanism can be added at the time of JOC Cockpit installation for a security level used for the signing of deployment objects such as workflows. See the Secure Configuration Article for more information. The JS7 JOC Cockpit provides three types of signing mechanisms:
  - Low: This mechanism is easy to use as it does not require any user interaction for the signing operation to be performed.
  - Medium: This mechanism is similar to the low signing mechanism except for the fact that the private key stored with the current user's profile is used for the signing of configuration objects.
  - High: This mechanism has the highest security level and this requires any configuration objects to be exported and to be signed individually outside of JOC Cockpit.
Step 6 - Database Management System
- Choose the DBMS to be used by the JOC Cockpit for the database system.
- The database connection settings can be either species directly or can be provided by hibernate configuration file. If the settings are specified directly then it is required to choose the database system otherwise the hibernate configuration file path can be specified after checking the option with hibernate configuration file.
  Image Added
- The database system is specified in the upper selection on this form. It is recommended that the box in the centre of the form remains checked so that the script which creates and fills the necessary database tables can be executed.
Step 7 - Database connection Configuration
- Specify the parameters for the connection to the Database.
  Image Added
- 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 JS7 JOC Cockpit.
- 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:
  - hibernate.cfg.xml
  This file can be modified at a later date if required using a text editor. The JS7 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 8 - Specify the JDBC Driver for the Database Connection

Specify if a JDBC driver provided with the installation should be used for the Database Connection or whether an external driver is required.
The information shown in this form depends on the DBMS previously selected:
- The jTDS JDBC® the driver delivered with the JOC Cockpit 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 9 - 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

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 Removed

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

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 folder

Step 13 - Completion
- The last step of the installation shows a summary of the installation (success/error) and paths to relevant information.
  Image RemovedImage 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.

...

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.

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

The joc_install.xml the 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
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"

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"/>
        <userInput/>
    <!-- Only necessary for Unix (root permissions required) --/com.izforge.izpack.panels.UserInputPanel>
    <com.izforge.izpack.panels.HTMLLicencePanel id="gpl_licence"/>
            <entry key="withJocInstallAsDaemon" value="yes"/>
<com.izforge.izpack.panels.TargetPanel id="target">
        
        <!-- Path to Jetty base directory 
     SELECT THE INSTALLATION PATH
             It must be absolute! 
             For example:
                 /homeopt/[user]/sos-berlin.com/js7/joc on Linux
                 C:\ProgramDataProgram Files\sos-berlin.com\js7\joc on Windows -->
        <installpath>[:choose absolute installation  <entry key="jettyBaseDir" value=""/path of JOC:]</installpath>
        
    </com.izforge.izpack.panels.TargetPanel>
    <com.izforge.izpack.panels.UserInputPanel id="jetty">
            <userInput>
            <!-- Java options for Jetty. -->
            <!-- InitialJOC memoryrequires pool (-Xms) in MB -->
  a servlet container such as Jetty. 
          <entry key="jettyOptionXms" value="128"/>
     If a servlet container already installed then <!-- Maximum memory pool (-Xmx) in MB -->
            <entry key="jettyOptionXmx" value="512"/>
you can use it. 
               <!-- Thread stackOtherwise size (-Xss) in KB -->
    a Jetty will be installed in addition if withJettyInstall=yes.
        <entry key="jettyOptionXss" value="4000"/>
       You need root permissions to <!-- Further Java optionsinstall JOC with Jetty. -->
            <entry key="jettyOptionswithJettyInstall" value="yes"/>
            
        </userInput>
    </com.izforge.izpack.panels.UserInputPanel>
    
    <com.izforge.izpack.panels.UserInputPanel id="reportingDatabase"<entry key="jettyPort" value="4446"/>
        <userInput>
    <!-- Specify the name of the Windows service <!-- Reporting Database Configuration -->or Linux Daemon (default: joc).
            
     Only necessary for multiple instances of JOC <!-- Database connection settings can be specified with following entries such as
on one server. It must be 
                 unique per server. This entry is deactivated by a comment  databaseHost, databasePort, ... or by a hibernate configuration file 
because it
                 MUST NOT BE CHANGED DURING OVER-INSTALLATION! -->
      Posible values are 'withoutHibernateFile' (default) and 'withHibernateFile'.  <!-->
            <entry key="reporting.databaseConfigurationMethodjettyServiceName" value="withoutHibernateFilejoc"/>
                 -->
            <!-- ChooseOnly thenecessary databasefor management system. Supported values are 'mysql' for MySQL,Windows -->
            <entry key="jettyStopPort" value="40446"/>
   'oracle' for Oracle, 'mssql' for MS SQL Server, 'pgsql' for PostgreSQL.
                 Only if reporting.databaseConfigurationMethod=withoutHibernateFile  <!-- Only necessary for Unix (root permissions required) -->
            <entry key="reporting.databaseDbmswithJocInstallAsDaemon" value="mysqlyes"/>
            
            <!-- PathTo toenter a hibernateJOC configuration file if reporting.databaseConfigurationMethod=withHibernateFile -->User (default=current User). 
            <entry key="reporting.hibernateConfFile" value=""/>
   For Unix only (root permissions required)!!! -->
   
        </userInput>
 <entry   </com.izforge.izpack.panels.UserInputPanel>
key="runningUser" value=""/>
     
    <com.izforge.izpack.panels.UserInputPanel id="reportingDbconnection">
  <!-- Path to Jetty base directory <userInput>
            <!-- Reporting Database Configuration  if reporting.databaseConfigurationMethod=withoutHibernateFile -->For example:
                 /home/[user]/sos-berlin.com/js7/joc on Linux
            <!-- Enter the name or ip address of the database host      C:\ProgramData\sos-berlin.com\js7\joc on Windows -->
            <entry key="jettyBaseDir" value=""/>
            <!-- Choose (yes or no) This entry can alsowether the JOC's Jetty should be used to configure the URL(s) for Oracle RAC databases.(re)started at the end of the installation -->
            <entry key="launchJetty" value="yes"/>
   For   example:
      
           <entry key="reporting.databaseHost" value="(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=OFF)(FAILOVER=ON)
     <!-- Java options for Jetty. -->
            <!-- Initial memory pool (ADDRESS=(PROTOCOL=TCP)(HOST=tst-db1.myco.com)(PORT=1604))
   -Xms) in MB -->
            <entry     (ADDRESS=(PROTOCOL=TCP)(HOST=tst-db2.myco.com)(PORT=1604)))key="jettyOptionXms" value="128"/>
            <!-- Maximum memory      (CONNECT_DATA=(SERVICE_NAME=mydb1.myco.com)(SERVER=DEDICATED)))"/pool (-Xmx) in MB -->
            <entry key="jettyOptionXmx" value="512"/>
         The "reporting.databaseSchema" and "reporting.databasePort" entries should then be left empty. <!-- Thread stack size (-Xss) in KB -->
            <entry key="reporting.databaseHostjettyOptionXss" value="4000"/>
            
<!-- Further           <!-- Enter the port number for the database instance. Default ports are for MySQL 3306, Java options -->
            <entry key="jettyOptions" value=""/>
            
     Oracle 1521, MS SQL</userInput>
 Server 1433, postgreSQL 5432. --> </com.izforge.izpack.panels.UserInputPanel>
    <com.izforge.izpack.panels.UserInputPanel id="joc">
       <entry key="reporting.databasePort" value=""/> <userInput>
            
            <!-- EnterJOC thecan schema -->
            <entry key="reporting.databaseSchema" value=""/>be installed in a cluster. Please type a unique title to identify the cluster node, 
            
     e.g. Primary or     <!-- Enter the user name for database accessSecondary (default = hostname). Max. length is 30 characters -->
            <entry key="reporting.databaseUserjocTitle" value=""/>
            
            <!-- Enter the password for database access Choose yes if JOC is a standby node in a cluster -->
            <entry key="reporting.databasePasswordisStandby" value="no"/>
            
        </userInput>
    </com.izforge.izpack.panels.UserInputPanel>
    
    <com.izforge.izpack.panels.UserInputPanel id="reportingJdbc">
        <userInput>
            <!-- Reporting Database Configuration  Security Level for the signing mechanism: possibly values are 'LOW', 'MEDIUM' and 'HIGH'
                 NOT SUPPORTED FOR SYBASE AND DB2 -->
HIGH:
                    public PGP keys are stored for verification only
            <!--  You can specify an external JDBC connectorall thensigning setwill reporting.internalConnectorbe =done no
externally outside of JOC Cockpit
             For license reasons MySQL, MSMEDIUM:
 SQL Server and Oracle ojdbc7 JDBC 
             a private PGP key driverswill arebe notstored provided.for signing
                 Alternatively you can usesigning thewill mariadbbe JDBCdone Driverautomatically forwith MySQLthe andprovided key
                 theLOW:
 jTDS JDBC Driver for MS SQL Server and Sybase which is provided. 
       no keys will be stored
      An Oracle ojdbc6 JDBC driver is also provided. -->
      signing will be done internally with default     keys -->
            <!-- You can choose between 'yes' or 'no' for using the internal JDBC connector
  <entry key="securityLevel" value="LOW"/>
            
        </userInput>
    </com.izforge.izpack.panels.UserInputPanel>
   or not -- <com.izforge.izpack.panels.UserInputPanel id="database">
        <userInput>
    <entry key="reporting.internalConnector" value="yes"/>
             <!-- Reporting Database Configuration -->
            
            <!-- Select the path to JDBC Driver -->Database connection settings can be specified with following entries such as
            <entry key="reporting.connector" value=""/>
            
     databaseHost, databasePort, ... or by a hibernate configuration file 
           </userInput>
    </com.izforge.izpack.panels.UserInputPanel>
  Posible values 
are 'withoutHibernateFile' (default)  <com.izforge.izpack.panels.UserInputPanel id="database"and 'withHibernateFile'. -->
        <userInput>
    <entry key="databaseConfigurationMethod" value="withoutHibernateFile"/>
      <!-- JobScheduler Database Configuration -->
            
            <!-- Set 'yes' if the Reporting and the JobSchedulerChoose the database aremanagement thesystem. same.
                 Supported values Ifare 'yesh2' thenfor furtherH2 JobScheduler(for databaseevaluation variables are ignored. -->only), 'mysql' for MySQL,
            <entry key="sameDbConnection" value="yes"/>
   'oracle' for Oracle, 'mssql' for MS SQL Server, 'pgsql' for PostgreSQL.
            <!-- Database connection settings can beOnly specifiedif with following entries such asdatabaseConfigurationMethod=withoutHibernateFile -->
            <entry     databaseHost, databasePort, ... or by a hibernate configuration file 
   key="databaseDbms" value="mysql"/>
            
            <!-- Path Posibleto valuesa arehibernate 'withoutHibernateFile' (default) and 'withHibernateFile'.configuration file if databaseConfigurationMethod=withHibernateFile -->
            <entry key="databaseConfigurationMethodhibernateConfFile" value="withoutHibernateFile"/>
                 
            <!-- ChooseYou thecan databasechoose management system. Supported values are 'mysql' for MySQL,
                 'oracle' for Oracle, 'mssql' for MS SQL Server, 'pgsql' for PostgreSQL,between 'on' or 'off' to create the database tables.
                 'db2'If foryou DB2have andmodified 'sybase'the forinitial Sybase.data 
of an already existing installation,  
           Only if databaseConfigurationMethod=withoutHibernateFile -->
   then the modifications will be undone. Data added remains <entry key="databaseDbms" value=""/>unchanged. 
            
     This entry should be only 'off', when <!-- Path to a hibernate configuration file if databaseConfigurationMethod=withHibernateFile you sure, that all tables are already created. -->
            <entry key="hibernateConfFiledatabaseCreateTables" value="on"/>
            
        </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 for H2 1521, 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,abd MS SQL Server and Oracle ojdbc7 JDBC 
                 drivers are not provided. 
                 Alternatively you can use the mariadb JDBC Driver for MySQL andwhich 
is provided. 
               the jTDS JDBCFor Driver for MS SQL Server and Sybase which is provided you have to specify an external JDBC connector. 
                 An Oracle ojdbc6ojdbc8 JDBC driver is also provided.
                 An internal JDBC connector for DB2 is notalso availableprovided. -->
                 
            <!-- 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="connectorLicenseconnector" 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>

Batch installation is started by opening a terminal or command window in the folder containing the setup.* file and typing:

...

Call the JOC Cockpit login form in a web browser and enter the User Name and Password.
After a first installation of the JOC Cockpit the default User Name and Password of root:root and Shiro Authentication will be active, if changes have not been made to the shiro.ini configuration file. Note that in the default configuration the root user is assigned the all role, which has all permissions available.
See the Authentication and Authorization - Configuration article for information about the configuration of other user-profiles and authentication methods.
Note that on some systems the web service may take a minute to start and display the login form shown below.

...

The default configuration for the Jetty server means that it automatically started with the operating system. However, it can also be stopped and started from the command line.

...

Space shortcuts

Page tree

Versions Compared

Old Version 3

New Version 4

Key

Language Selection

Step 1 - Welcome Screen
Image RemovedImage Added

Step 2 - Licensing Agreement

Step 3 - Target Path for the Installation

Anchor
jetty-base
jetty-base
Step 4 - Jetty Installation & Configuration

Default Paths

Step 5 -

Step 6 - Configure the Reporting Database Connection

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

JOC Configuration

Step 6 - Database Management System

Step 7 - Database connection Configuration

Step 8 - Specify the JDBC Driver for the Database Connection

Configuring the JDBC Driver-URL for Oracle RAC databases

Step 9 - Processing the Installation

Step 12 - External Processes

Configuring the JDBC Driver-URL for Oracle RAC databases

Step 8 - Specify the Database Connection Used by the JobScheduler

Step 9 - Specify the JobScheduler DBMS

Step 10 - Configure the JobScheduler Database Connection

Step 11 - Processing the Installation

Step 12 - External Processes

Step 13 - Completion

Operation

Configuration

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 3

New Version 4

Key

Language Selection

Step 1 - Welcome ScreenImage RemovedImage Added

Step 2 - Licensing Agreement

Step 3 - Target Path for the Installation

Anchorjetty-basejetty-baseStep 4 - Jetty Installation & Configuration

Default Paths

Step 5 -

Step 6 - Configure the Reporting Database Connection

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

JOC Configuration

Step 6 - Database Management System

Step 7 - Database connection Configuration

Step 8 - Specify the JDBC Driver for the Database Connection

Configuring the JDBC Driver-URL for Oracle RAC databases

Step 9 - Processing the Installation

Step 12 - External Processes

Configuring the JDBC Driver-URL for Oracle RAC databases

Step 8 - Specify the Database Connection Used by the JobScheduler

Step 9 - Specify the JobScheduler DBMS

Step 10 - Configure the JobScheduler Database Connection

Step 11 - Processing the Installation

Step 12 - External Processes

Step 13 - Completion

Operation

Configuration

Step 1 - Welcome Screen
Image RemovedImage Added

Anchor
jetty-base
jetty-base
Step 4 - Jetty Installation & Configuration