skip to main content
Getting Started with DataDirect Cloud : Creating a Data Source definition

Try DataDirect Cloud Now

Creating a Data Source definition

You define the information that DataDirect Cloud needs to connect to the data store in a Data Source defintion. You can store the credentials to the data store in the Data Source definition or have client applications provide it when they connect to DataDirect Cloud.
The steps in this topic apply generally but the available options differ by data store type. When you are logged in to your DataDirect Cloud account, follow these steps to create a Data Source:
1. In the left navigation panel, click Data Sources to open the Data Sources view.
2. Click +New Data Source. The Data Stores page opens.
3. From the list of Data Stores, click the logo for the type of data store you want to connect to.
4. The Create Data Source dialog opens. Note: To set up a data source for data stores behind a firewall, you must first install and configure an On-Premises Connector. See Using DataDirect Cloud On-Premise Connector for more information. If applicable, select On-Premise or Cloud depending on the type of data store you want to connect.
5. On the General tab, enter a data source name, and complete other fields identified as required. If applicable, enter the login credentials required for the data store. If you do not enter the login credentials, a pop-up dialog will be displayed when you try to connect.
To persist the login credentials of the data store, you must enter the credentials in the data source definition page.
6. If applicable, on the Security tab, enter the information to specify the type of authentication or encryption.
7. If applicable, on the OData tab, select options to configure a schema map, and specify cache and page size. See Enabling OData Access for a Data Source for more information.
You must configure a schema map to enable the data source for OData.
8. If applicable, on the DataTypes tab, select options to configure and map data types.
9. If applicable, on the Mapping tab, select options to create mapping between data models and subsequently use it for queries and updates.
10. If applicable, on the Advanced tab select options to configure advanced behavior. The following provide details on the fields specific to each supported cloud data store:
Table 1. Connection parameter pages for each data store
Data Store
Connection Pages
Amazon Redshift
Apache Hadoop Hive
Google Analytics
Microsoft Dynamics CRM
Microsoft SQL Server
Oracle Eloqua
Note: The Eloqua data store has been replaced by the Oracle Marketing Cloud data store. For compatibility purposes, the Eloqua data store remains available for access in this release. However, the Eloqua data store will be deprecated in a future release.
Oracle Marketing Cloud
Oracle Service Cloud
Progress OpenEdge
Progress Rollbase
Salesforce-based data sources
Sybase ASE
11. When you are satisfied with the Data Source definition, finish by clicking one of the following:
*Click Save to create the definition without testing the connection. You can test later by executing a query in the SQL Testing view.
*Click Test Connection to establish a connection with the Data Store, create the data source, and save the data source.
*Click Save to create the Data Source .
If you click Test Connection without specifying the login credentials, a pop-up dialog appears. Enter the login credentials for the data source and click OK. The credentials are not persisted and you must enter the credentials for subsequent access. To persist the login credentials, you must enter them in the data source definition page.
The new Data Source will be displayed in the list on the Data Sources page.
If you created an OData-enabled data source, the icon beside it indicates the status of the schema map generation. The following table provides details of the icons:
Schema Synch in progress
The synching of schema map is in progress. The number denotes the percentage of syncing completed.
Synch completed successfully
The schema map was synched successfully.
Errors when synching a schema map
There were errors while synching the schema map. You need to synch the schema map again.
Schema map resynch needed
You need to synch the schema map again.