Integrating AlloyDB Data in Talend Cloud Data Management Platform

Qlik's Talend Cloud Data Management Platform supports various data environments, enabling analytics for smarter decisions, operational data sharing, data and application modernization, and establishing data excellence for risk reduction. When paired with the CData JDBC Driver for AlloyDB, you can improve data integration, quality, and governance for your AlloyDB Data. This article shows how you can easily integrate to AlloyDB using a CData JDBC Driver in Talend Cloud Data Management, and then view the data for simultaneous use in your workflow.

Prerequisites

Before connecting the CData JDBC Driver to view and work with your data in Talend Cloud Data Management Platform, make sure to download and install the latest version of Talend Studio on your system. Also, ensure that you have the required prerequisites.

1. A Talend Cloud Data Management account with appropriate permissions.
2. The CData JDBC Driver for AlloyDB, which can be downloaded from the CData website.

Connect to AlloyDB in Talend as a JDBC data source

Access Talend Data Management Cloud

1. Run the Talend Cloud Data Management Platform installed on your local system and click on Other Login Mode.
2. Click on Manage Connections. Set Repository to "Local" and enter the Name, Description and User E-mail in the respective spaces. Set the Workspace path and click on OK.
3. Now, select the Create a new project radio button to add a new project name and click on Create.
4. The new project should appear under the Select an existing project section. Click on Open. The Talend Cloud Data Management Platform workspace opens up.

Create a new connection

1. In the navigation pane, locate and expand the Metadata dropdown. Right-click on Db Connections and select Create Connection.
2. Search for and select 'JDBC' in the Find section of the Database Connection window. Then, click on Finish.
3. Enter the Name, Purpose and Description of the new database in Talend where you need to load the AlloyDB data. Click on Next.

4. Generate a JDBC URL for connecting to AlloyDB, beginning with jdbc:alloydb: followed by a series of semicolon-separated connection string properties.

   The following connection properties are usually required in order to connect to AlloyDB.

   • Server: The host name or IP of the server hosting the AlloyDB database.
   • User: The user which will be used to authenticate with the AlloyDB server.
   • Password: The password which will be used to authenticate with the AlloyDB server.

   You can also optionally set the following:

   • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
   • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

   Authenticating with Standard Authentication

   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.

   Authenticating with pg_hba.conf Auth Schemes

   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.

   Authenticating with MD5 Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

   Authenticating with SASL Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

   Authenticating with Kerberos

   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.

   Built-in Connection String Designer

   For assistance in constructing the JDBC URL, use the connection string designer built into the AlloyDB JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

   java -jar cdata.jdbc.alloydb.jar

   Fill in the connection properties and copy the connection string to the clipboard.

   A typical JDBC URL is below:

   jdbc:alloydb:User=alloydb;Password=admin;Database=alloydb;Server=127.0.0.1;Port=5432

5. Enter the JDBC URL copied from CData JDBC Driver for AlloyDB in Edit new database.

6. Click on the "(+) Add" button under Drivers. A 'newLine' will appear in the Drivers board. Click on (...) at the end of the new line, select the Install a new module radio button, and click on (...) to add the path to the JAR file, located in the 'lib' subfolder of the installation directory. Click on OK.
7. Select the Driver Class as cdata.jdbc.alloydb (JAR file obtained from your installation directory given in the previous step).

Test the new connection

1. Click on Check Connection. If the entered details are correct, a "Connection successful" confirmation prompt will appear. Click on "OK" and "Finish".
2. Once the connection is established, right-click on the newly created connection and select Retrieve Schema. You can use the filters as well to retrieve the data as per your requirements. Click on Next.
3. Expand the "CData" catalog in the Schema window and select the tables you want to import from the AlloyDB schema. Click on Next.
4. In the next step, select the columns you want to view from the table and click on Finish.
5. All the selected tables from the AlloyDB schema are now populated under the Table Schemas section of the JDBC connection.
6. Right-click on any of the selected tables and click on Data Viewer to preview the data from the data source.

Get Started Today

Download a free, 30-day trial of the CData JDBC Driver for AlloyDB and integrate AlloyDB data into Talend Cloud Data Management Platform. Reach out to our Support Team if you have any questions.