![]() |
VOOZH | about |
TIBCO Data Virtualization (TDV) is an enterprise data virtualization solution that orchestrates access to multiple and varied data sources. When paired with the AlloyDB Tibco DV Adapter, you get federated access to live AlloyDB data directly within TIBCO Data Virtualization. This article explains how to deploy an adapter and create a new data source based on AlloyDB.
With built-in optimized data processing, the CData TIBCO DV Adapter offers unmatched performance for interacting with live AlloyDB data. When you issue complex SQL queries to AlloyDB, the adapter pushes supported SQL operations, like filters and aggregations, directly to AlloyDB. Its built-in dynamic metadata querying allows you to work with and analyze AlloyDB data using native data types.
In a console, navigate to the bin folder in the TDV Server installation directory. If there is a current version of the adapter installed, you will need to undeploy it.
.\server_util.bat -server localhost -user admin -password ******** -undeploy -version 1 -name AlloyDB
Extract the CData TIBCO DV Adapter to a local folder and deploy the JAR file (tdv.alloydb.jar) to the server from the extract location.
.\server_util.bat -server localhost -user admin -password ******** -deploy -package /PATH/TO/tdv.alloydb.jar
You may need to restart the server to ensure the new JAR file is loaded properly, which can be accomplished by running the composite.bat script located at: C:\Program Files\TIBCO\TDV Server <version>\bin. Note that reauthenticating to the TDV Studio is required after restarting the server.
.\composite.bat monitor restartOnce you deploy the adapter, you can create a new data source in TDV Studio for AlloyDB.
With the AlloyDB Tibco DV Adapter, you can easily create a data source for AlloyDB and introspect the data source to add resources to TDV.
The following connection properties are usually required in order to connect to AlloyDB.
You can also optionally set the following:
Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.
No further action is required to leverage Standard Authentication to connect.
There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.
Find instructions about authentication setup on the AlloyDB Server here.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.
The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.
👁 Filling in Connection Information (Salesforce is shown.)
Once the data source is created, you can introspect the data source by right-clicking and selecting Open. In the dashboard, click Add/Remove Resources and select the Tables, Views, and Stored Procedures to include as part of the data source. Click Next and Finish to add the selected AlloyDB tables, views, and stored procedures as resources.
👁 Introspecting the Data Source (Salesforce is shown.)After creating and introspecting the data source, you are ready to work with AlloyDB data in TIBCO Data Virtualization just like you would any other relational data source. You can create views, query using SQL, publish the data source, and more.
Learn more:
TIBCO DV Adapters