Skip to main content
Skip table of contents

DHL Connector

You are looking at an older version of the documentation. The latest version is found here.

Connecting DHL Track and Trace as a Data Source

To create the connection, you can either add data source in the Data Virtuality Studio or use the following statements in the Studio's SQL Editor or any connected SQL client:

SQL
CALL "SYSADMIN.createConnection"(
    "name" => 'DHL_TnT',
    "jbossCLITemplateName" => 'ws',
    "connectionOrResourceAdapterProperties" => null
);;

CALL "SYSADMIN.createDataSource"(
    "name" => 'DHL_TnT',
    "translator" => 'dhl',
    "modelProperties" => null,
    "translatorProperties" => null
);;

Usage

The DHL Track and Trace data source introduces the following stored procedures:


This list includes some stored procedures that are intended to be used by the end users (public API). Each public API procedure is assigned to an original web service request from DHL Track and Trace web service and is consistent with this request in terms of the content and the output order of result.

The description of the DHL Track and Trace web service can be found in the attached documentation.

Public API procedures

The public API procedures are as follows:

  • getStatusForPublicUser
  • dGetPiece
  • dGetPieceEvent
  • dGetPieceDetail

In addition to the public API procedures, the DHL Track and Trace data source exposes some internal procedures that are used by the public API. The output order of internal procedures is alphabetical, and the content complies with their purpose.

Internal procedures are as follows:

  • getTrackingContent
  • getPieceEvent
  • getPieceEventList
  • getPieceEventSummary
  • getPieceShipment
  • getPieceShipmentList
  • getStatusForPublicUserPiece
  • getStatusForPublicUserPieceList
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.