SAP Crystal Reports JDBC-ODBC Bridge Connector
In this article you will learn how to integrate Using JDBC-ODBC Bridge Connector you will be able to connect, read, and write data from within SAP Crystal Reports. Follow the steps below to see how we would accomplish that. Driver mentioned in this article is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc. If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started. |
See also
|
Create ODBC Data Source (DSN) based on ZappySys JDBC Driver
To get data from JdbC-OdbcBridge using SAP Crystal Reports we first need to create a DSN (Data Source) which will access data from JdbC-OdbcBridge. We will later be able to read data using SAP Crystal Reports. Perform these steps:
-
Install ZappySys ODBC PowerPack.
-
Open ODBC Data Sources (x64):
-
Create a User Data Source (User DSN) based on ZappySys JDBC Bridge Driver
ZappySys JDBC Bridge DriverYou should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version. -
Now, we need JDBC Bridge Connection. Lets create it. When you see DSN Config Editor with zappysys logo first thing you need to do is change default DSN Name at the top and Configure JDBC Bridge Driver. Enter Credentials (In this Example We have used PostgreSQL Credentials) and then Click on Test Connection to verify your credentials.
Note: Enter suitable JDBC Driver Credentials, You can read data from any JDBC Driver -
This example shows how to write simple SOQL query (JDBC Bridge Object Query Language). It uses WHERE clause. For more SOQL Queries click here.
SOQL is similar to database SQL query language but much simpler and many features you use in database query may not be supported in SOQL (Such as JOIN clause not supported). But you can use following Queries for Insert, Update, Delete and Upsert(Update or Insert record if not found).SELECT orderid, customerid, orderdate, orderamount FROM "public"."zappysys" -
Click OK to finish creating the data source
How to read JDBC-ODBC Bridge data in SSIS
In this section we will learn how to configure and use JDBC-ODBC Bridge Connector in the ODBC Source to get data from JDBC-ODBC Bridge.
-
Begin with opening Visual Studio and Create a New Project.
Select Integration Service Project and in new project window set the appropriate name and location for project. And click OK.
-
In the the new SSIS project screen you will find the following:
- SSIS ToolBox on left side bar
- Solution Explorer and Property Window on right bar
- Control flow, data flow, event Handlers, Package Explorer in tab windows
- Connection Manager Window in the bottom
Note: If you don't see ZappySys SSIS PowerPack Task or Components in SSIS Toolbox, please refer to this help link. -
Now, Drag and Drop SSIS Data Flow Task from SSIS Toolbox. Double click on the Data Flow Task to see Data Flow designer.
-
From the SSIS toolbox drag and drop ODBC Source on the dataflow designer surface
-
Double click on ODBC Source component to configure it.
-
Click on New... button, It will open Configure ODBC Connection Manager, Click on New... button to configure new connection using Connection Manager.
-
Select User OR System DSN from the lists of data source names and then click on Test Connection and you will get Test Connection successful message click on OK to close that message and click on OK to close the Connection Manager window.
-
ODBC Connection Manager is set. Now, Select Data access mode: Table Name and select your desired table from the list of tables or views then click on Preview... and click on Close and OK button to save configuration settings.
-
That's it; we are done. In a few clicks we configured the ODBC Source Component to read JDBC-ODBC Bridge data using SSIS.
Read data in SAP Crystal Reports from the ODBC data source
-
First of all, open SAP Crystal Reports and create the new Crystal Report.
-
And it will open the new data source selection window. Under ODBC(RDO) double click on the Make New Connection and Select the desired ODBC DSN, in our case we need to select JdbC-OdbcBridgeDSN which we created in upper section. And Click on Next.
JdbC-OdbcBridgeDSN -
Expand the Connection and under the data select the desired table(s) or view(s) and click Add > button and click on Next.
JdbC-OdbcBridgeDSNJdbC-OdbcBridgeDSN -
Add the desired Fields to Display in the Reports. Here we are adding all fields and click on Finish.
-
That's it and you will be able to load the data in the Report.
Using ZappySys Driver Custom Views and Store Procedure in SAP Crystal Report
You can create parameterized Stored Procedure and Virtual Tables on the same Data Source (ODBC DSN or Data Gateway Data Source). Please refer to this article for the same. You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.Using Custom Views in the SAP Crystal Report
After establishing the connection with JdbC-OdbcBridgeDSN Data Source you can use the custom view in SQL Crystal Report.
Using Custom Store Procedure in the SAP Crystal Report
-
First of all, create the custom store procedure in the ZappySys Driver. Please refer to this article to create the custom store procedure.
-
After establishing the connection with JdbC-OdbcBridgeDSN Data Source you can use the custom Store Procedure in SQL Crystal Report. Same way you can write custom queries also in the query box.
JdbC-OdbcBridgeDSN
Create Custom Store Procedure in ZappySys Driver
You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.
Steps to create Custom Store Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
-
Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
-
Enter the desired Procedure name and click on OK:
-
Select the created Store Procedure and write the your desired store procedure and Save it and it will create the custom store procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
CREATE PROCEDURE [usp_get_orders] @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>' AS SELECT * FROM Orders where OrderDate >= '<@fromdate>';
-
That's it now go to Preview Tab and Execute your Store Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
Exec usp_get_orders '1996-01-01';
-
Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
-
Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
Create Custom Virtual Table in ZappySys Driver
ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.
Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.
-
Go to Custom Objects Tab and Click on Add button and Select Add Table:
-
Enter the desired Table name and click on OK:
-
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
-
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
SELECT "ShipCountry", "OrderID", "CustomerID", "EmployeeID", "OrderDate", "RequiredDate", "ShippedDate", "ShipVia", "Freight", "ShipName", "ShipAddress", "ShipCity", "ShipRegion", "ShipPostalCode" FROM "Orders" Where "ShipCountry"='USA'
-
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
SELECT * FROM "vt__usa_orders_only"
-
Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
-
Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
Conclusion
In this article we discussed how to connect to JDBC-ODBC Bridge in SAP Crystal Reports and integrate data without any coding. Click here to Download JDBC-ODBC Bridge Connector for SAP Crystal Reports and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).
Download JDBC-ODBC Bridge Connector for SAP Crystal Reports
Documentation
Other App Integration scenarios for JDBC-ODBC Bridge
Other Connectors for SAP Crystal Reports
Download JDBC-ODBC Bridge Connector for SAP Crystal Reports
Documentation
How to connect JDBC-ODBC Bridge in SAP Crystal Reports?
How to get JDBC-ODBC Bridge data in SAP Crystal Reports?
How to read JDBC-ODBC Bridge data in SAP Crystal Reports?
How to load JDBC-ODBC Bridge data in SAP Crystal Reports?
How to import JDBC-ODBC Bridge data in SAP Crystal Reports?
How to pull JDBC-ODBC Bridge data in SAP Crystal Reports?
How to push data to JDBC-ODBC Bridge in SAP Crystal Reports?
How to write data to JDBC-ODBC Bridge in SAP Crystal Reports?
How to POST data to JDBC-ODBC Bridge in SAP Crystal Reports?
Call JDBC-ODBC Bridge API in SAP Crystal Reports
Consume JDBC-ODBC Bridge API in SAP Crystal Reports
JDBC-ODBC Bridge SAP Crystal Reports Automate
JDBC-ODBC Bridge SAP Crystal Reports Integration
Integration JDBC-ODBC Bridge in SAP Crystal Reports
Consume real-time JDBC-ODBC Bridge data in SAP Crystal Reports
Consume realtime JDBC-ODBC Bridge API data in SAP Crystal Reports
JDBC-ODBC Bridge ODBC Driver | ODBC Driver for JDBC-ODBC Bridge | ODBC JDBC-ODBC Bridge Driver | SSIS JDBC-ODBC Bridge Source | SSIS JDBC-ODBC Bridge Destination
Connect JDBC-ODBC Bridge in SAP Crystal Reports
Load JDBC-ODBC Bridge in SAP Crystal Reports
Load JDBC-ODBC Bridge data in SAP Crystal Reports
Read JDBC-ODBC Bridge data in SAP Crystal Reports
JDBC-ODBC Bridge API Call in SAP Crystal Reports