skip to main content
Using Hybrid Data Pipeline : Creating data sources with the Web UI : How to create a data source in the Web UI
  

Try Now

How to create a data source in the Web UI

A Hybrid Data Pipeline data source contains the information that allows the service to connect to the backend data store.
Take the following steps to create a Hybrid Data Pipeline data source.
Note: These steps apply generally to all data stores, but the available options differ by data store type. Consult the topics that follow for information specific to supported data stores.
1. Navigate to the Data Sources view by clicking the data sources icon .
2. Click + NEW DATA SOURCE to open the Data Stores page.
3. From the list of data stores, click data store to which you want to connect.
The Create Data Source page opens.
4. Provide required information in the fields provided under each of the tabs.
5. Click Save to create the data source definition.
6. Click TEST to establish a connection with the data store.
If you create 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:
Icon
Description
Schema Synch in progress
The synchronization of the schema map is in progress. The number denotes the percentage of synchronization completed.
Sync completed successfully
The schema map was synchronized successfully.
Sync completed successfully, with warning messages
The schema map was synchronized successfully, but there are some table/column warnings. Hybrid Data Pipeline allows users to know the details of the tables/columns and/or functions that were dropped while generating the OData Model for a given schema map of a Data Source. The number of warnings shown is limited to 100. If there are more than 100 errors/warnings, you can use the Schema API to retrieve table and column warnings.
Errors when synching a schema map
Errors occurred while synchronizing the schema map. You must address the errors and synchronize the schema map again. Hybrid Data Pipeline allows users to know the details of the tables and/or columns that were dropped while generating the OData Model for a given schema map of a Data Source. The number of errors/warnings shown is limited to 100. If there are more than 100 errors/warnings, you can use the Schema API to retrieve table and column warnings.
Schema map resynch needed
You must synchronize the schema map again.