Table of Contents

Search

  1. Preface
  2. Part 1: PowerExchange CDC Introduction
  3. Part 2: PowerExchange CDC Components
  4. Part 3: PowerExchange CDC Data Sources
  5. Part 4: Change Data Extraction
  6. Part 5: Monitoring and Tuning
  7. Appendix A: DTL__CAPXTIMESTAMP Time Stamps

CDC Guide for Linux, UNIX, and Windows

CDC Guide for Linux, UNIX, and Windows

Configuring JDBC on Windows or Linux

Configuring JDBC on Windows or Linux

PowerExchange SAP HANA CDC requires JDBC access in addition to ODBC access.
PowerExchange installs the following .jar files for the SAP HANA CDC:
  • log4j-api-2.17.1.jar
  • log4j-core-2.17.1.jar
  • HanaAdapter.jar
  • commons-codec-1.15.jar (PowerExchange 10.5.4 and later)
SAP HANA CDC also requires access to the JDBC client ngdbc.jar file. To provide access to this .jar file, complete the following steps:
  1. Copy the ngdbc.jar file to the jars subdirectory in the PowerExchange installation. By default, the installation directory also includes the .jar files installed with PowerExchange.
  2. By default, PowerExchange expects the ngdbc.jar file in the jars directory. If the file is named differently or placed in a different directory, either rename the file to ngdbc.jar or move the file to the jars directory. Add a HANA_CLASSPATH statement in the dbmover.cfg file to point to all of the required .jar files. Use the separator appropriate for the environment between each file name. The following example shows the HANA_CLASSPATH statement on Windows:
    HANA_CLASSPATH="<
    install_directory
    >\jars\HanaAdapter.jar;<
    install_directory
    >\jars\log4j-api-2.17.1.jar;<
    install_directory
    >\jars\log4j-core-2.17.1.jar;<
    install_directory
    >\jars\ngdbc.jar"
    The following example shows the HANA_CLASSPATH statement on Linux:
    HANA_CLASSPATH="<
    install_directory
    >/jars/HanaAdapter.jar:<
    install_directory
    >/jars/log4j-api-2.17.1.jar:<
    install_directory
    >/log4j-core-2.17.1.jar:<
    install_directory
    >/jars/ngdbc.jar"
PowerExchange looks first for dependent jar files in the HANA_CLASSPATH statement. The location of the *.jar files specified in the dbmover.cfg HANA_CLASSPATH parameter must be fully-qualified from the root directory in which they reside. If the HANA_CLASSPATH statement is not present, PowerExchange uses the path defined in the PWX_HOME environment variable. If you do not include the HANA_CLASSPATH statement or the PWX_HOME variable, PowerExchange looks in the installation directory.
PowerExchange sets the java.class.path of the JVM that is created for the HanaAdapter.jar using the following rules:
  1. If the HANA_CLASSPATH statement is specified in the dbmover configuration file, PowerExchange uses that value.
  2. If the HANA_CLASSPATH statement is not specified in the dbmover configuration file, PowerExchange fetches the list of jar files in the
    <install>/jars
    folder and uses those fully-qualified filenames to set the CLASSPATH passed to the Java JVM.
If you did not install the jar files in the PowerExchange
<installation>/jars
directory, ensure that the HANA_CLASSPATH statement in the dbmover.cfg configuration file specifies all of the *.jar files with fully-qualified path names.

Back to Top

0 COMMENTS

We’d like to hear from you!