Jitterbit is an enterprise iPaaS (integration platform as a service) that lets you streamline your data workflows. When paired with CData Connect AI, Jitterbit gets access to live AlloyDB data. This article demonstrates how to connect to AlloyDB using Connect AI and integrate with live AlloyDB data in Jitterbit.
CData Connect AI provides a pure OData interface for AlloyDB, allowing you to query data from AlloyDB 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 AlloyDB, leveraging server-side processing to return the requested AlloyDB data quickly.
Configure AlloyDB Connectivity for Jitterbit
To work with AlloyDB data from Jitterbit, we need to connect to AlloyDB from Connect AI, provide user access to
the connection, and create a Workspace for the AlloyDB data.
Connect to AlloyDB from Connect AI
CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.
-
Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a Connection
- Select "AlloyDB" from the Add Connection panel
👁 Selecting a data source
-
Enter the necessary authentication properties to connect to AlloyDB.
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.
👁 Configuring a connection (Salesforce is shown)
-
Click Save & Test
-
Navigate to the Permissions tab in the Add AlloyDB Connection page and update the User-based permissions.
👁 Updating permissions
Add a Personal Access Token
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.
-
Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
-
On the Settings page, go to the Access Tokens section and click Create PAT.
-
Give the PAT a name and click Create.
👁 Creating a new PAT
-
The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
Configure AlloyDB Endpoints for Jitterbit
After connecting to AlloyDB, create a workspace for your desired table(s).
-
Navigate to the Workspaces page and click Add to create a new Workspace (or select an existing workspace).
👁 The Workspaces page.
👁 Adding a new Workspace.
-
Click Add to add new assets to the Workspace.
-
Select the AlloyDB connection (e.g. AlloyDB1) and click Next.
👁 Selecting an Asset (Salesforce is shown).
-
Select the table(s) you wish to work with and click Confirm.
👁 Selecting Tables (Salesforce is shown).
-
Make note of the OData Service URL for your workspace, e.g. https://cloud.cdata.com/api/odata/{workspace_name}
With the connection, PAT, and Workspace configured, you are ready to connect to AlloyDB data from Jitterbit.
Connect to AlloyDB from Jitterbit using Connect AI
To establish a connection from Jitterbit to CData Connect AI using the OData protocol, follow these steps.
- Log into Jitterbit.
- Create a project in Cloud Studio and provide a workspace environment for it.
👁 Creating a new project in Jitterbit.
- click Sources and enter OData in the search bar.
- Select the OData connector.
- Enter the OData connection properties.
- Connection Name: enter a connection name.
- OData Metadata URL: enter https://cloud.cdata.com/api/odata/{workspace_name}.
- Authentication: select Basic Auth.
- User Name: enter your CData Connect AI username. This is displayed in the top-right corner of the CData Connect AI interface. For example, [email protected].
- Password: enter the PAT you generated on the Settings page.
👁 Configuring connectivity to the Connect AI OData endpoint.
- Click Test to test the connection, and then click Save Changes.
- Choose the operation you want to perform and drag it to the workflow in your project.
👁 Selecting the operation for the workflow.
- Double-click the query operation to see all the tables and derived views available in your OData endpoint.
👁 Viewing the available endpoints.
- Select a table and configure the query.
You can now transform and integrate live AlloyDB data in Jitterbit.
Get CData Connect AI
To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from Jitterbit,
try CData Connect AI today!
