Connect to AlloyDB Data and Transfer Data in Talend

This article shows how you can easily integrate the CData JDBC driver for AlloyDB into your workflow in Talend. This article uses the CData JDBC Driver for AlloyDB to transfer AlloyDB data in a job flow in Talend.

Connect to AlloyDB in Talend as a JDBC Data Source

You can follow the procedure below to establish a JDBC connection to AlloyDB:

1. Add a new database connection to AlloyDB data: To add a new connection, expand the Metadata node, right-click the Db Connections node, and then click Create Connection.
2. In the resulting wizard, enter a name for the connection.

3. On the next page, select Generic JDBC from the DB Type menu and enter the JDBC URL.

   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
4. Enter the path to the cdata.jdbc.alloydb.jar file, located in the lib subfolder of the installation directory.
5. Right-click the connection and then click Retrieve Schema.
6. Click Next with the default options to select the tables you want to import.
7. Finish the wizard with the default options.

Output the Orders Table to a Flat File

You can follow the procedure below to transfer the Orders table to a flat file output component:

1. In the Table Schemas node, drag the tables to the workspace.
2. In the dialog that is displayed, select the tJDBCInput component.
3. Next, drag a tFileOutputDelimited component from the Business Intelligence tab of the Palette into the workspace.
4. Right-click the Orders tJDBCInput component and drag a vector to the output file.

Run the project to transfer the data.