![]() |
VOOZH | about |
APOS Live Data Gateway (LDG) is a data connection and data transformation solution that enables live data connectivity and expanded data source options for SAP Analytics Cloud and other SAP solutions. When paired with CData Connectors, users can build semantic layer views for live AlloyDB data, enabling real-time analytics on AlloyDB just like working with a relational database.
With built-in optimized data processing, the CData Connector offers unmatched performance for interacting with live AlloyDB data. When you issue complex SQL queries to AlloyDB, the driver pushes supported SQL operations, like filters and aggregations, directly to AlloyDB and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze AlloyDB data using native data types.
In order to access AlloyDB data through the APOS Live Data Gateway, you will need to download the connector files from APOS and install them on the machine hosting the Live Data Gateway. An APOS representative can deliver the necessary files.
Before establishing the connection to AlloyDB from the APOS Live Data Gateway, you need to configure the AlloyDB JDBC Connection String.
For assistance in constructing the JDBC Connection String, 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.
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.
π Using the built-in connection string designer to generate a JDBC URL (alloydb is shown.)
Your connection string will look similar to the following:
jdbc:AlloyDB:User=alloydb;Password=admin;Database=alloydb;Server=127.0.0.1;Port=5432
After installing the connector files and configuring the connection string, you are ready to connect to AlloyDB in the Live Data Gateway Admin tool and build a semantic layer view in the Live Data Gateway Web UI.
jdbc:AlloyDB:User=alloydb;Password=admin;Database=alloydb;Server=127.0.0.1;Port=5432
At this point, we are ready to build our semantic layer view in the Live Data Gateway Web UI.
With the Semantic Layer View created, you are ready to access your AlloyDB data through the APOS Live Data Gateway, enabling real-time data connectivity to AlloyDB data from SAP Analytics Cloud and other SAP solutions.
Please visit APOS Systems - APOS Solutions - Request Evaluation Software to request evaluation software or email [email protected] for more information on working with your live AlloyDB data in APOS Live Data Gateway.
Download a free trial of the AlloyDB Driver to get started:
Download NowLearn more:
π AlloyDB IconRapidly create and deploy powerful Java applications that integrate with AlloyDB.