VOOZH about

URL: https://www.cdata.com/kb/tech/alloydb-cloud-infragistics-reveal.rst

⇱ Analyze AlloyDB Data in Infragistics Reveal


Analyze AlloyDB Data in Infragistics Reveal

πŸ‘ Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Use CData Connect AI to create on OData API on top of AlloyDB data and visualize live AlloyDB data in Infragistics Reveal.

Reveal, an offering from Infragistics, serves as a data visualization tool that seamlessly integrates with CData Connect AI. Together, they empower users to deliver dynamic dashboards using real-time data from a diverse range of data sources, including AlloyDB data. In this article, we will guide you through the process of connecting to AlloyDB via Connect AI and subsequently linking Connect AI with Infragistics Reveal to construct a straightforward dashboard.

Connect to AlloyDB from Infragistics Reveal

To work with live AlloyDB data in Infragistics Reveal, 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.

  1. Log into Connect AI, click Sources, and then click Add Connection
  2. πŸ‘ Adding a Connection
  3. Select "AlloyDB" from the Add Connection panel
  4. πŸ‘ Selecting a data source
  5. 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)

  6. Click Save & Test
  7. 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.

  1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
  2. On the Settings page, go to the Access Tokens section and click Create PAT.
  3. Give the PAT a name and click Create. πŸ‘ Creating a new PAT
  4. 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 Infragistics Reveal

After connecting to AlloyDB, create a workspace for your desired table(s).

  1. 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.
  2. Click Add to add new assets to the Workspace.
  3. Select the AlloyDB connection (e.g. AlloyDB1) and click Next. πŸ‘ Selecting an Asset (Salesforce is shown).
  4. Select the table(s) you wish to work with and click Confirm. πŸ‘ Selecting Tables (Salesforce is shown).
  5. 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 Infragistics Reveal.

Create a Dashboard in Reveal

With Connect AI configured, we can visualize AlloyDB data in Reveal.

  1. Log into Reveal and click Dashboards -> New πŸ‘ Adding a new dashboard
  2. Click Data Sources -> OData Feed πŸ‘ Adding a new OData data source
  3. Specify the Connect AI OData API endpoint URL (found on the OData page): https://cloud.cdata.com/api/odata/{workspace_name} πŸ‘ Configuring the OData URL
  4. Select Generic Credentials and
    • Set Username to a Connect AI username (e.g. [email protected])
    • Set Password to the PAT for the user
    πŸ‘ Configuring the credentials
  5. Select the entity you wish to visualize πŸ‘ Selecting an entity to visualize (Salesforce is shown.)
  6. Select fields and choose a chart type πŸ‘ Visualizing data in Reveal (Salesforce is shown.)

More Information & Free Trial

At this point, you have created a simple dashboard from live AlloyDB data. For more information on creating OData feeds from AlloyDB (and more than 100 other sources), visit the Connect AI page. Sign up for a free trial and start working live AlloyDB data in tools that consume OData APIs.