skip to main content
Hybrid Data Pipeline API reference : Management API : Driver Files API : Export config files for data source
  

Try Now
Export config files for data source

Purpose

Exports the config file for a specified non-relational data source. The file will be returned as an XML response.

URL

https://<myserver>:<port>/api/mgmt/datasources/{id}/export/driverfiles/config

Method

GET

URL Parameters

<myserver> is the hostname or IP address of the machine hosting the Hybrid Data Pipeline server for a standalone installation, or the machine hosting the load balancer for a load balancer installation. For a standalone installation, <port> is the port number specified as the Server Access Port during installation. For a load balancer installation, <port> must be either 80 for http or 443 for https. Whenever port 80 or 443 are used, it is not necessary to include the port number in the URL.
The {id} parameter must also be specified in the URL.
Parameter
Description
Valid Values
{id}
The ID of the data source.
The ID is auto-generated when the data source is created and cannot be changed.

Sample Server Response


Status code: 200
Successful response

<?xml version='1.0' encoding='UTF-8'?>
<Database xmlns="http://test-datadirect.com/cloud/config" version="2">
<User name="**********" defaultSchema="*****">
<UseSchema name="*****"/>
<UseSchema name="PUBLIC"/>
</User>
<Map name="*****" type="Eloqua">
<ConfigOptions>UPPERCASEIDENTIFIERS=1;...;...</ConfigOptions>
<SessionOptions>DATABASENAME=;USER=;...;...</SessionOptions>
</Map>
<MapDatabase uppercaseidentifiers="true" ... truncateMethod="asis">
<Schema native="ELOQUA" rename="ELOQUA" default="true">
<Table native="Account" rename="ACCOUNT">
<Column rename="ID" path="id/*" key="1" dataType="LONG"/>
<Column rename="CURRENTSTATUS" ... dataType="TEXT" .../>
<Column rename="NAME" path="name/*" dataType="TEXT" .../>
</Table>
...
</Schema>
</MapDatabase>
</Database>

Sample Server Failure Response


{
"error":
{
"code": 222208728,
"message": "No config cloud db driver file found."
}
}

Authentication

Basic Authentication using Login ID and Password.

Authorization

The user must have either the Administrator (12) permission, or the MgmtAPI (11) permission and ViewDataSource (2) permission on the applicable data source.