Cisco Cisco Workload Automation 6.3 Betriebsanweisung
12
Configuring the JDBC Adapter
Configuring the JDBC Adapter
/opt/tidal/master/services/{68597802-1828-464D-BEDC-2B6E1D3C8C0C}/config/service.props
service.props entry examples:
Windows:
TDLJDBC_LOCALE=C:\\Program Files\\TIDAL\\Scheduler\\master\\services\\jdbclib\\locale
Unix:
TDLJDBC_LOCALE=/opt/tidal/master/services/jdbc/locale
6.
For connectivity to the database, you need access to the JDBC Drivers.
Note:
You must enable High Debug to view Adapter startup information in the AdapterHost log files. Refer to the
“Diagnostic Logging for the Master” in the Troubleshooting chapter in the Cisco Workload Automation User Guide
for setting debug levels.
for setting debug levels.
The JDBC Adapter includes the Master's CLASSPATH, which contains references to the JDBC driver jars for
operation with both MSSQL and SQL Server databases. These drivers are NOT distributed as part of the Master
installation but are usually sufficient for connectivity to either SQL Server (sqljdbc.jar) or Oracle Databases
(ojdbc14.jar).
operation with both MSSQL and SQL Server databases. These drivers are NOT distributed as part of the Master
installation but are usually sufficient for connectivity to either SQL Server (sqljdbc.jar) or Oracle Databases
(ojdbc14.jar).
Note:
JDBC adapter does not ship any JDBC drivers. Download the drivers from the JDBC driver website and specify
the driver path as follows:
1. Create a config directory under /master/services/{68597802-1828-464D-BEDC-2B6E1D3C8C0C}
2. Create service.props under config directory created in step 1.
3. In service.props, specify the driver path following the example:
In windows:
CLASSPATH=c:\\mylib\\jconn4.jar;c:\\DB2\\sqlj.zip;${CLASSPATH}
In Linux/Unix:
CLASSPATH=/opt/unixsa/DB_Drivers/jconn4.jar:/opt/unixsa/6.0.2/master/41/TIDAL/master/lib/ojdbc6.jar:${CLAS
SPATH}
1. Create a config directory under /master/services/{68597802-1828-464D-BEDC-2B6E1D3C8C0C}
2. Create service.props under config directory created in step 1.
3. In service.props, specify the driver path following the example:
In windows:
CLASSPATH=c:\\mylib\\jconn4.jar;c:\\DB2\\sqlj.zip;${CLASSPATH}
In Linux/Unix:
CLASSPATH=/opt/unixsa/DB_Drivers/jconn4.jar:/opt/unixsa/6.0.2/master/41/TIDAL/master/lib/ojdbc6.jar:${CLAS
SPATH}
When the Adapter process is started, its CLASSPATH includes the Master's CLASSPATH. You can determine the
CLASSPATH for the JDBC Adapter by opening the AdapterHost-xxx.log located in the ..\Master\Log directory and
searching for the following words:
CLASSPATH for the JDBC Adapter by opening the AdapterHost-xxx.log located in the ..\Master\Log directory and
searching for the following words:
*** Starting Service:JDBC
The following is an example of the startup parameters for the JDBC Adapter on Windows. Notice the inclusion of the
CLASSPATH (
CLASSPATH (
-cp) with a delimited listed of jar files. This list includes Master distributed JDBC drivers sqljdbc.jar
(SQLServer) and ojdbc14.jar (Oracle).
Note:
Should the CLASSPATH not include the driver needed to connect to the database, you may needed to do one
or both of the following:
1. Obtain the appropriate driver for your configuration
2. Specify the CLASSPATH option in Service.props, referencing the fully qualified name of the JDBC jar file.
1. Obtain the appropriate driver for your configuration
2. Specify the CLASSPATH option in Service.props, referencing the fully qualified name of the JDBC jar file.
*** Starting Service:JDBC Command is:java -Xms16m -Xmx256m -cp "C:\Program
Files\TIDAL\Scheduler\master\services\jdbcservice.pkg;C:\Program
Files\TIDAL\Scheduler\master\services\{68597802-1828-464D-BEDC-2B6E1D3C8C0C}\lib\jniLM.jar;C:\Progr
am
Files\TIDAL\Scheduler\master\services\{68597802-1828-464D-BEDC-2B6E1D3C8C0C}\lib\commons-net-1.1.0.
jar;C:\Program Files\TIDAL\Scheduler\master\lib\AdapterHost.jar;C:\Program
Files\TIDAL\Scheduler\master\lib\Scheduler.jar;C:\Program
Files\TIDAL\Scheduler\master\lib\sqljdbc.jar;C:\Program
Files\TIDAL\Scheduler\master\lib\ojdbc14.jar;C:\SAPJCO\sapjco.jar"
com.tidalsoft.service.jdbc.JDBCApp -p 6980 -id {7640B420-5530-11DE-8812-7B8656D89593}