...
| Code Block |
|---|
| language | xml |
|---|
| title | Example: JobScheduler Database Connection in scheduler_install.xml |
|---|
|
<com.izforge.izpack.panels.UserInputPanel id="dbconnection">
<userInput>
<!-- JobSchedulerDatabase Configuration. -->
<!-- Enter the name or ip address of the database host -->
<entry key="databaseHost" value=""/>
This entry can also be used <!-- Enterto configure the port numberURL(s) for theOracle databaseRAC instancedatabases.
Default ports areFor for example:
- MySql®: 3306, <entry key="databaseHost" value="(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=OFF)(FAILOVER=ON)
- Oracle® Database: 1521, (ADDRESS=(PROTOCOL=TCP)(HOST=tst-db1.myco.com)(PORT=1604))
- Microsoft® SQL Server: 1433,
(ADDRESS=(PROTOCOL=TCP)(HOST=tst-db2.myco.com)(PORT=1604)))
- postgreSQL: 5432, (CONNECT_DATA=(SERVICE_NAME=mydb1.myco.com)(SERVER=DEDICATED)))"/>
- IBM® DB2: 50000,
- Sybase: 5000The "databaseSchema" and "databasePort" entries should then be left empty. -->
<entry key="databasePortdatabaseHost" value=""/>
<!-- Enter the schemaport -->number
for the database instance.
<entry key="databaseSchema" value=""/>
Default ports are for <!--
Enter the user name for database access -->
- <entry key="databaseUser" value=""/>
MySql®: 3306,
<!-- Enter the password for database access -->
Oracle® Database: 1521,
<entry key="databasePassword" value=""/>
- Microsoft® SQL <!-- You must provide the MySql®, Microsoft® SQL Server or Sybase JDBC® Driver respectively if you selected corresponding DBMS type.Server: 1433,
- postgreSQL: 5432,
For license reasons MySql®- IBM® DB2: 50000, Sybase
and Microsoft® SQL Server JDBC® Drivers are not provided.
- Sybase: 5000. -->
Alternatively you can use:
<entry key="databasePort" value=""/>
<!-- Enter the schema --> the
MariaDB® JDBC® Driver for MySql® and
<entry key="databaseSchema" value=""/>
<!-- Enter the jTDS JDBC® Driver for Microsoft® SQL Server and Sybase which is provided.--> user name for database access -->
<entry key="databaseUser" value=""/>
<!-- YouEnter canthe choosepassword betweenfor 'yes'database or 'no' for using the jTDS JDBC® Driver
access -->
<entry key="databasePassword" value=""/>
This entry has only an effect for<!-- You must provide the MySql®, Microsoft® SQL Server or Sybase -->JDBC®
Driver respectively if you selected corresponding DBMS type.
<entry key="connectorJTDS" value="yes"/>
<!-- You can choose between 'yes' or 'no' for using the MariaDB® JDBC® DriverFor license reasons MySql®, Sybase and Microsoft® SQL Server JDBC® Drivers are not provided.
ThisAlternatively entryyou hascan onlyuse:
an effect for MySql® -->
<entry key="connectorMaria" value="yes"/>
</userInput>
</com.izforge.izpack.panels.UserInputPanel> |
| Code Block |
|---|
| language | xml |
|---|
| title | Example: JobScheduler Database Driver in scheduler_install.xml |
|---|
|
<com.izforge.izpack.panels.UserInputPanel id="jdbc">
- the MariaDB® JDBC® Driver for MySql® and
<userInput>
<!-- Configurationthe forjTDS JDBC® Driver
for Microsoft® SQL Server and Sybase which is provided.-->
This entry is only necessary if the package 'Database Support' is chosen and<!-- You can choose between 'yes' or 'no' for using the jTDS JDBC® Driver
youThis selectedentry ahas DBMSonly typean likeeffect MySql®,for Microsoft® SQL Server or Sybase in the previous <userInput> element. -->
<!-- You must provide the MySql®, Microsoft® SQL Server or Sybase JDBC® Driver respectively if you selected corresponding DBMS type.
<entry key="connectorJTDS" value="yes"/>
<!-- You can choose between 'yes' or 'no' for using the MariaDB® JDBC® Driver
For license reasons MySql® and Microsoft® SQL Server JDBC®This Driversentry arehas notonly provided.an
effect for MySql® -->
<entry key="connectorMaria" value="yes"/>
</userInput>
</com.izforge.izpack.panels.UserInputPanel> |
| Code Block |
|---|
| language | xml |
|---|
| title | Example: JobScheduler Database Driver in scheduler_install.xml |
|---|
|
<com.izforge.izpack.panels.UserInputPanel id="jdbc">
<userInput>
Specify the JDBC® Driver source (e.g. mysql-connector-java-*.jar for MySql®, sqljdbc.jar for Microsoft® SQL Server, jconn3.jar for Sybase).
<!-- JobScheduler Database Alternatively you can use:Configuration -->
<!-- You can specify an external -JDBC theconnector MariaDB®then JDBC®set DriverinternalConnector for MySql® and = no
For -license thereasons jTDSMySQL, JDBC® Driver for Microsoft®Sybase, MS SQL Server and Sybase,Oracle whichojdbc7 isJDBC provided.
-->
<!-- Select the pathdrivers toare JDBC®not Driver -->
provided.
<entry key="connector" value=""/>
Alternatively you can use the mariadb JDBC Driver for MySQL and
<!-- Only for DB2: Select the path to DB2 license filethe forjTDS JDBC Driver -->
<entry key="connectorLicense" value=""/>
for MS SQL Server and Sybase which is provided.
An
Oracle ojdbc6 JDBC driver is </userInput>also
</com.izforge.izpack.panels.UserInputPanel> |
Please read The JobScheduler Database Support Package Forms section in the Dialog Installation chapter of this installation guide for more information.
The Reporting Database Configuration Settings
Reporting information may be saved in the same database as used by the JobScheduler Master or in a separate one. The configuration of the DBMS and DB connection for a separate reporting database is similar to that already made of the JobScheduler database. Note that a separate reporting database is not supported for Sybase or DB2 DBMSs.
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> |
Please read The JobScheduler Database Support Package Forms section in the Dialog Installation chapter of this installation guide for more information.
The Reporting Database Configuration Settings
Reporting information may be saved in the same database as used by the JobScheduler Master or in a separate one. The configuration of the DBMS and DB connection for a separate reporting database is similar to that already made of the JobScheduler database. Note that a separate reporting database is not supported for Sybase or DB2 DBMSs.
The following section of the scheduler_install.xml file specifies whether or not a separate reporting database is to be used.
| Code Block |
|---|
| language | xml |
|---|
| title | Example: Reporting Database Configuration in scheduler_install.xml |
|---|
|
<com.izforge.izpack.panels.UserInputPanel id="reportingDatabase">
<userInput>
<!-- Reporting Database Configuration
NOT SUPPORTED FOR SYBASE AND DB2 -->
<!-- Set 'yes' if the JobScheduler and the Reporting database are the same.
If 'yes' then further Reporting database variables are ignored. -->
<entry key="sameDbConnection" value="yes"/>
<!-- Choose the database management system. Supported values are 'mysql' for MySQL,
'oracle' for Oracle, 'mssql' for MS SQL Server, 'pgsql' for PostgreSQL. -->
<entry key="reporting.databaseDbms" value=""/>
</userInput>
</com.izforge.izpack.panels.UserInputPanel> |
The following two sections The following section of the scheduler_install.xml file specifies whether or not a separate reporting also have to be configured if a separate reporting database is to be used.
| Code Block |
|---|
| language | xml |
|---|
| title | Example: Reporting Database Configuration Connection in scheduler_install.xml |
|---|
|
<com.izforge.izpack.panels.UserInputPanel id="reportingDatabasereportingDbconnection">
<userInput>
<userInput>
<!-- Reporting DatabaseReportingDatabase Configuration
NOT SUPPORTED FOR SYBASE AND DB2 -->
<!-- Set 'yes' ifEnter the JobSchedulername andor theip Reportingaddress database areof the same.
If 'yes' then further Reporting database variables are ignored. -->
host
<entry key="sameDbConnection" value="yes"/> This
entry can also be used to configure the URL(s) for Oracle RAC databases.
<!-- Choose the database management system. Supported values are 'mysql' for MySQL,
For example:
<entry 'oracle' for Oracle, 'mssql' for MS SQL Server, 'pgsql' for PostgreSQL. -->
key="reporting.databaseHost" value="(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=OFF)(FAILOVER=ON)
<entry key="reporting.databaseDbms" value=""/>
(ADDRESS=(PROTOCOL=TCP)(HOST=tst-db1.myco.com)(PORT=1604))
</userInput>
</com.izforge.izpack.panels.UserInputPanel> |
The following two sections of the scheduler_install.xml file also have to be configured if a separate reporting database is to be used.
| Code Block |
|---|
| language | xml |
|---|
| title | Example: Reporting Database Connection in scheduler_install.xml |
|---|
|
<com.izforge.izpack.panels.UserInputPanel id="reportingDbconnection">
(ADDRESS=(PROTOCOL=TCP)(HOST=tst-db2.myco.com)(PORT=1604)))
<userInput>
<!-- ReportingDatabase Configuration (CONNECT_DATA=(SERVICE_NAME=mydb1.myco.com)(SERVER=DEDICATED)))"/>
NOT SUPPORTED FOR SYBASE AND DB2 -->
<!-- Enter the name or ip address of the database host --> 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® Database: 1521,
- Microsoft® SQL Server: 1433,
- postgreSQL: 5432. -->
<entry key="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=""/>
<!-- You have to provide the MySQL or MS SQL Server JDBC driver respectively if you selected
corresponding DBMS type. For license reasons MySQL and MS SQL Server JDBC Drivers
are not provided. Alternatively you can use the mariadb JDBC Driver for MySQL and the
jTDS JDBC Driver for MS SQL Server which are provided. -->
<!-- You can choose between 'yes' or 'no' for using the jTDS JDBC® Driver
This entry only affects MS SQL Server. -->
<entry key="reporting.connectorJTDS" value="yes"/>
<!-- You can choose between 'yes' or 'no' for using the MariaDB® JDBC® Driver
This entry has only an effect for MySql® -->
<entry key="reporting.connectorMaria" value="yes"/>
</userInput>
</com.izforge.izpack.panels.UserInputPanel> |
| Code Block |
|---|
| language | xml |
|---|
| title | Example: Reporting Database Driver in scheduler_install.xml |
|---|
|
<com.izforge.izpack.panels.UserInputPanel id="reportingJdbc">
<userInput>
<!-- Reporting Database Configuration
NOT SUPPORTED FOR SYBASE AND DB2 -->
NOT SUPPORTED FOR SYBASE AND DB2 -->
<!-- You can Configurationspecify foran JDBC®external DriverJDBC
connector then set reporting.internalConnector = no
This entry is only necessary ifFor thelicense packagereasons 'Database Support' is chosenMySQL, MS SQL Server and
Oracle ojdbc7 JDBC
you selected a DBMSdrivers typeare likenot MySql®,provided. Microsoft®
SQL Server or Sybase in the previous
Alternatively you can use the mariadb JDBC Driver <userInput>for element. -->
MySQL and
<!-- You have to provide the jTDS JDBC MySQLDriver orfor MS SQL Server JDBCand driverSybase respectivelywhich if you selectedis provided.
correspondingAn DBMSOracle type.ojdbc6 ForJDBC licensedriver reasonsis MySQLalso and MS SQL Server JDBC Drivers are
provided. -->
not provided. Specify the JDBC Driver source (e.g. mysql-connector-java-*.jar for MySQL,
<!-- You can choose between 'yes' or 'no' for using the internal JDBC connector
sqljdbc.jar for MS SQL Server). Alternatively you can useor the mariadb JDBC Driver for
not -->
<entry key="reporting.internalConnector" value="yes"/>
MySQL and the jTDS JDBC Driver for MS SQL Server which is provided. -->
<!-- Select the path to JDBC®JDBC Driver -->
<entry key="reportingconnectorreporting.connector" value=""/>
</userInput>
</com.izforge.izpack.panels.UserInputPanel> |
...