Analyze Live HCL Domino Data in SAS Viya

SAS Viya is an analytics platform that enhances data management, machine learning, and analytics, fostering efficient decision-making and insights. When paired with CData Connect AI, you get instant, cloud-to-cloud access to HCL Domino data for building predictive models, crafting stunning insights to make data-driven decisions, and more. This article shows how to connect to Connect AI from the SAS Viya cloud platform and integrate live HCL Domino data into your self-service AI and analytics deployments.

CData Connect AI provides a pure SQL, cloud-to-cloud interface for HCL Domino, allowing you to easily integrate with live HCL Domino data in SAS Viya — without replicating the data. CData Connect AI looks exactly like a SQL Server database to SAS Viya and uses optimized data processing out of the box to push all supported SQL operations (filters, JOINs, etc.) directly to HCL Domino, leveraging server-side processing to return HCL Domino data quickly.

Configure HCL Domino Connectivity for SAS Viya

Connectivity to HCL Domino from SAS Viya is made possible through CData Connect AI. To work with HCL Domino data from SAS Viya, we start by creating and configuring a HCL Domino connection.

1. Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a Connection

2. Select "HCL Domino" from the Add Connection panel
👁 Selecting a data source

3. Enter the necessary authentication properties to connect to HCL Domino.

   Connecting to Domino

   To connect to Domino data, set the following properties:

   • URL: The host name or IP of the server hosting the Domino database. Include the port of the server hosting the Domino database. For example: http://sampleserver:1234/
   • DatabaseScope: The name of a scope in the Domino Web UI. The driver exposes forms and views for the schema governed by the specified scope. In the Domino Admin UI, select the Scopes menu in the sidebar. Set this property to the name of an existing scope.

   Authenticating with Domino

   Domino supports authenticating via login credentials or an Entra ID (formerly Azure AD) OAuth application:

   Login Credentials

   To authenticate with login credentials, set the following properties:

   • AuthScheme: Set this to "OAuthPassword"
   • User: The username of the authenticating Domino user
   • Password: The password associated with the authenticating Domino user

   The driver uses the login credentials to automatically perform an OAuth token exchange.

   EntraID (formerly AzureAD)

   This authentication method uses Entra ID (formerly Azure AD) as an IdP to obtain a JWT token. You need to create a custom OAuth application in Entra ID (formerly Azure AD) and configure it as an IdP. To do so, follow the instructions in the Help documentation. Then set the following properties:

   • AuthScheme: Set this to "EntraID (formerly AzureAD)"
   • InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
   • OAuthClientId: The Client ID obtained when setting up the custom OAuth application.
   • OAuthClientSecret: The Client secret obtained when setting up the custom OAuth application.
   • CallbackURL: The redirect URI defined when you registered your app. For example: https://localhost:33333
   • AzureTenant: The Microsoft Online tenant being used to access data. Supply either a value in the form companyname.microsoft.com or the tenant ID.

     The tenant ID is the same as the directory ID shown in the Azure Portal's Entra ID (formerly Azure AD) > Properties page.

   👁 Configuring a connection (Salesforce is shown)
   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add HCL Domino 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.

With the connection configured and a PAT generated, you are ready to connect to HCL Domino data from SAS Viya.

Connecting to CData Connect AI from SAS Viya

The following steps detail the process of loading data from HCL Domino into SAS Viya using the established connection in CData Connect AI.

1. Download and install the CData Connect AI JDBC driver.
   • Open the Integrations page of CData Connect AI.
   • Search for and select JDBC.
   • Download and run the setup file.
   • When the installation is complete, the JAR file can be found in the installation directory (inside the lib folder).
2. Now, log in to SAS Viya and navigate to the Applications Menu at the top-left corner.
3. Select Develop Code and Flows from the Analytics Life Cycle topic. 👁 Select Develop Code and Flows
   
4. Navigate to the Explorer tab and click on SAS Server on the left panel.
5. Follow the steps to upload the JAR file of the CData Connect JDBC driver:
   • Right-click on the "Home" directory.
   • Click on Upload files.
   • Place the JAR file in the specified location and note its file path. 👁 Click on Upload files to upload the JAR file in the Home folder
     👁 JAR file uploaded
     👁 Save the location of the JAR file from File Properties
     
6. Once done, navigate to the Libraries tab and click on Create a new library connection (on the top left corner as shown below) for the CData Connect JDBC. 👁 Navigate to the Libraries tab and click on Create a new library connection
   
7. Enter the library connection settings:
   • Connection name: enter a name for your connection
   • Library name (libref): enter a reference for your library
   • Library type: choose "SAS/ACCESS to JDBC"
8. Click on the Properties tab and set Library attributes to READONLY. 👁 Click on the Properties tab and set Library attributes to READONLY
   
9. Click the Connection Options tab and enter the following details:
   • Hive JDBC driver's class name: cdata.jdbc.connect.ConnectDriver
   • Java CLASSPATH: enter the file path to the JAR driver file (Refer to Step 5) 👁 Fill Hive JDBC driver's class name
     👁 Fill Java CLASSPATH
     
10. Click on Test connection. If it succeeds, click on Save and connect. 👁 Successful test connection
    
11. Click on to add a new tab and select SAS program. 👁 Select SAS program to write SQL Queries
    
12. Fill in the code block below with your setup parameters:
    • Libref: enter the library reference you defined in Step 9.
    • ClassPath: enter the file path to the JAR driver file.
    • Username: enter your CData Connect username. This is displayed in the top-right corner of the CData Connect interface. For example, [email protected].
    • DefaultCatalog: enter the connection configured in CData Connect AI that you want to query.
    • Password: enter the PAT you generated in the "Add a Personal Access Token" section.

    libname [Libref] JDBC 
    classpath=[ClassPath] 
    class="cdata.jdbc.connect.ConnectDriver" 
    URL="jdbc:Connect:AuthScheme=Basic;User=[Username];DefaultCatalog=[DefaultCatalog];DefaultSchema=dbo;Password=[PAT]"; 
     
    proc sql; 
    
    SELECT * FROM [Libref].MyTable; 
    
    quit; 
    

13. Click on Run. You can see the data load from CData Connect AI into SAS Viya.

Live Access to HCL Domino Data from Cloud Applications

At this point, you have a direct, cloud-to-cloud connection to HCL Domino data from SAS Viya. You can build predictive models, craft insights to make data-driven decisions, and more — all without replicating HCL Domino data.

Try Connect AI and get real-time data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications.