![]() |
VOOZH | about |
There are a vast number of PostgreSQL clients available on the Internet. PostgreSQL is a popular interface for data access. When you pair PostgreSQL with CData Connect AI, you gain database-like access to live SAP Concur data from PostgreSQL. In this article, we walk through the process of connecting to SAP Concur data in Connect AI and establishing a connection between Connect AI and PostgreSQL using a TDS foreign data wrapper (FDW).
CData Connect AI provides a pure SQL Server interface for SAP Concur, allowing you to query data from SAP Concur without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to SAP Concur, leveraging server-side processing to return the requested SAP Concur data quickly.
CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.
SAP Concur uses the OAuth 2 authentication standard. obtain the and by registering an app with SAP Concur. See the Getting Started section of the help documentation for an authentication guide.
๐ Configuring a connection (Salesforce is shown)When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
With the connection configured and a PAT generated, you are ready to connect to SAP Concur data from PostgreSQL.
The Foreign Data Wrapper can be installed as an extension to PostgreSQL, without recompiling PostgreSQL. The tds_fdw extension is used as an example (https://github.com/tds-fdw/tds_fdw).
sudo apt-get install git git clone https://github.com/tds-fdw/tds_fdw.git cd tds_fdw make USE_PGXS=1 sudo make USE_PGXS=1 installNote: If you have several PostgreSQL versions and you do not want to build for the default one, first locate where the binary for pg_config is, take note of the full path, and then append PG_CONFIG=
sudo service postgresql start
psql -h localhost -U postgres -d postgresNote: Instead of localhost you can put the IP where your PostgreSQL is hosted.
After you have installed the extension, follow the steps below to start executing queries to SAP Concur data:
CREATE EXTENSION tds_fdw;
CREATE SERVER "SAPConcur1" FOREIGN DATA WRAPPER tds_fdw OPTIONS (servername'tds.cdata.com', port '14333', database 'SAPConcur1');
CREATE USER MAPPING for postgres SERVER "SAPConcur1" OPTIONS (username '[email protected]', password 'your_personal_access_token' );
CREATE SCHEMA "SAPConcur1";
#Using a table_name definition: CREATE FOREIGN TABLE "SAPConcur1".Departments ( id varchar, OfficeId varchar) SERVER "SAPConcur1" OPTIONS(table_name 'SAPConcur.Departments', row_estimate_method 'showplan_all'); #Or using a schema_name and table_name definition: CREATE FOREIGN TABLE "SAPConcur1".Departments ( id varchar, OfficeId varchar) SERVER "SAPConcur1" OPTIONS (schema_name 'SAPConcur', table_name 'Departments', row_estimate_method 'showplan_all'); #Or using a query definition: CREATE FOREIGN TABLE "SAPConcur1".Departments ( id varchar, OfficeId varchar) SERVER "SAPConcur1" OPTIONS (query 'SELECT * FROM SAPConcur.Departments', row_estimate_method 'showplan_all'); #Or setting a remote column name: CREATE FOREIGN TABLE "SAPConcur1".Departments ( id varchar, col2 varchar OPTIONS (column_name 'OfficeId')) SERVER "SAPConcur1" OPTIONS (schema_name 'SAPConcur', table_name 'Departments', row_estimate_method 'showplan_all');
SELECT id, OfficeId FROM "SAPConcur1".Departments;
Now, you have created a simple query from live SAP Concur data. For more information on connecting to SAP Concur (and more than 200 other data sources), visit the Connect AI page. Sign up for a free trial and start working with live SAP Concur data in PostgreSQL.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial