![]() |
VOOZH | about |
OutSystems is a low-code platform which provides the tools for companies to developer, deploy, and manage omnichannel enterprise applications. When paired with CData Connect AI, you get instant, cloud-to-cloud access to AlloyDB data for business applications. This article shows how to create a virtual database for AlloyDB in Connect AI and build a simple app from AlloyDB data in OutSystems.
The CData Connect AI provides a pure cloud-to-cloud interface for AlloyDB, allowing you to build reports from live AlloyDB data in OutSystems β without replicating the data to a natively supported database. As you create applications to work with data, OutSystems generates SQL queries to gather data. 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 quickly return the requested AlloyDB data.
Connectivity to AlloyDB from OutSystems is made possible through CData Connect AI. To work with AlloyDB data from OutSystems, we start by creating and configuring a AlloyDB connection.
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.
π Configuring a connection (Salesforce is shown)
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.
With the connection configured and a PAT generated, you are ready to connect to AlloyDB data from OutSystems.
The steps below outline connecting to CData Connect AI from OutSystems to create a new AlloyDB database connection.
Once you create the database connection for AlloyDB, you can create an extension that maps the tables or views to OutSystems entities. If you have not already done so, create an Application in Service Studio.
At this point, you can access and work with AlloyDB data just like you would with the standard OutSystems entities.
With Connect AI and OutSystems, you can easily build AlloyDB-connected applications. Request a free trial of Connect AI and start working with AlloyDB data in OutSystems today.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial