Help Center/ Data Replication Service/ API Reference/ APIs V5.0 (in OBT)/ Task Operations/ Uploading a Driver File (Deprecated)
Updated on 2024-10-25 GMT+08:00
Online Debugging
CLI Examples
View PDF
Share

Uploading a Driver File (Deprecated)

Function

This API is used to upload a driver file.

Constraints

  • This API is available only in the synchronization scenario where DB2 for LUW serves as the source database.
  • This API can be used only in certain regions. For details, see Endpoints.

URI

POST /v5/{project_id}/jdbc-driver

Table 1 Path parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID of a tenant in a region.

For details, see Obtaining a Project ID.

Request Parameters

Table 2 Request header parameters

Parameter

Mandatory

Type

Description

Content-Type

Yes

String

MIME type of the request body. Use the default value multipart/form-data. For APIs used to upload objects or images, the value varies depending on the flow type.

X-Auth-Token

Yes

String

User token obtained from IAM.

It is a response to the API for obtaining a user token. This API is the only one that does not require authentication.

After a request is processed, the value of X-Subject-Token in the header is the token value.

X-Language

No

String

Request language type.

Default value: en-us

Enumerated values:

  • en-us
  • zh-cn
Table 3 FormData parameter

Parameter

Mandatory

Type

Description

file

Yes

File

Driver file. The driver file name contains 5 to 64 characters and ends with .jar. If a driver file with the same name exists, the file is replaced by the uploaded one.

Response Parameters

None

Example Request

Uploading a driver file

https://{endpoint}/v5/5237e10fe9aa4ad5b16b6a5245248314/jdbc-driver

Example Response

Status code: 200

OK

{ }

Status Code

Status Code

Description

200

OK

Error Code

For details, see Error Code.

Parent topic: Task Operations