Obtaining the Driver JAR Package and Configuring JDK 1.8
Environment preparation includes obtaining the driver JAR package and configuring JDK 1.8.
Obtaining the Driver Package
Download the driver package and its verification package listed in Table 1.
- Verifying the software package integrity on a Linux server:
- Upload the software package and verification package to the same directory on the VM.
- Run the following command to verify the integrity of the software package:
cat GaussDB_driver.zip.sha256 | sha256sum --check
If OK is displayed in the command output, the verification is successful.
GaussDB_driver.zip: OK
- Verifying the software package integrity on a Windows server:
- Press Win+R to open the Run dialog box. Type cmd in the text box and press Enter to open the Command Prompt window.
- Run the following command to obtain the hash value of the driver package:
certutil -hashfile {local_directory_of_the_driver_package}\{driver_package_name} sha256
- Replace {local_directory_of_the_driver_package} with the actual download path, for example, C:\Users.
- Replace {driver_package_name} with the name of the downloaded driver package, for example, GaussDB_driver.zip.
Example: certutil -hashfile C:\Users\GaussDB_driver.zip sha256
- Compare the hash value obtained in 2 with the hash value of the verification package obtained in Table 1.
Obtaining the Driver JAR Package
Decompress the obtained driver package, find the JDBC driver package GaussDB-Kernel_Database version number_OS_64bit_Jdbc.tar.gz, and decompress it. After the decompression, you will obtain the following driver packages in JAR format:
- gsjdbc4.jar: The main class name is org.postgresql.Driver, and the URL prefix of the database connection is jdbc:postgresql. This driver package applies to the scenario where services are migrated from PG. The driver class and loading path are the same as those before the migration, but the supported APIs are different. The APIs that are not supported need to be adjusted on the service side.
- opengaussjdbc.jar: The main class name is com.huawei.opengauss.jdbc.Driver. The URL prefix of the database connection is jdbc:opengauss. This driver package is recommended. This driver package is used when both PG and GaussDB are accessed in a JVM process.
- The loading paths and URL prefixes of driver classes vary in different driver packages, but their functions are the same.
- gsjdbc200.jar: This driver package applies to the scenario where services are migrated from Gauss200. The driver class and loading path are the same as those before the migration, but the supported APIs are different. The APIs that are not supported need to be adjusted on the service side.
- The gsjdbc4.jar driver package cannot be used to operate the PG database. Although the connection can be successfully established in some versions, some API behaviors are different from those of PG JDBC, which may cause unknown errors.
- The PG driver package cannot be used to operate the GaussDB database. Although the connection can be successfully established in some versions, some API behaviors are different from those of GaussDB JDBC, which may cause unknown errors.
Configuring JDK 1.8
JDK 1.8 must be configured on the client. JDK supports multiple platforms such as Windows and Linux. The following uses Windows as an example to describe the configuration method:
- Enter the following command in the MS-DOS window (command prompt in Windows) to check the JDK version:
java -version
Ensure that the JDK version is JDK 1.8. If JDK is not installed, download the installation package from the official website and install it.
- Configure system environment variables.
- Right-click My computer and choose Properties.
- In the System window, click Advanced system settings in the navigation pane.
- In the System Properties dialog box, click Environment Variables on the Advanced tab page.
- In the System variables area of the Environment Variables dialog box, click New or Edit to configure system variables. For details, see Table 2.
Table 2 Variables Variable
Operation
Variable Value
JAVA_HOME
- If the variable exists, click Edit.
- If the variable does not exist, click New.
Specifies the Java installation directory.
Example: C:\Program Files\Java\jdk1.8.0_131
Path
Click Edit.
- If JAVA_HOME is configured, add %JAVA_HOME%\bin before the variable value.
- If JAVA_HOME is not configured, add the full Java installation path before the variable value:
C:\Program Files\Java\jdk1.8.0_131\bin
CLASSPATH
Click New.
.;%JAVA_HOME%\lib;%JAVA_HOME%\lib\tools.jar
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot