Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Query HCL Domino Data as a MySQL Database in Node.js
Execute MySQL queries against HCL Domino data from Node.js.
You can use the SQL Gateway from the ODBC Driver for HCL Domino to query HCL Domino data through a MySQL interface. Follow the procedure below to start the MySQL remoting service of the SQL Gateway and start querying using Node.js.
Connect to HCL Domino Data
If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can use the built-in Microsoft ODBC Data Source Administrator to configure the DSN. This is also the last step of the driver installation. See the "Getting Started" chapter in the help documentation for a guide to using the Microsoft ODBC Data Source Administrator to create and configure a DSN.
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 Azure Active Directory 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.
AzureAD
This authentication method uses Azure Active Directory as an IdP to obtain a JWT token. You need to create a custom OAuth application in Azure Active Directory 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 "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 Azure Active Directory > Properties page.
Configure the SQL Gateway
See the SQL Gateway Overview to set up connectivity to HCL Domino data as a virtual MySQL database. You will configure a MySQL remoting service that listens for MySQL requests from clients. The service can be configured in the SQL Gateway UI.
Query HCL Domino from Node.js
The following example shows how to define a connection and execute queries to HCL Domino with the mysql module. You will need the following information:
- Host name or address, and port: The machine and port where the MySQL remoting service is listening for MySQL connections.
- Username and password: The username and password of a user you authorized on the Users tab of the SQL Gateway.
- Database name: The DSN you configured for the MySQL remoting service.
Connect to HCL Domino data and start executing queries with the code below:
var mysql = require('mysql'); var connection = mysql.createConnection({ host : 'localhost', database : 'CData Domino Sys', port : '3306', user : 'mysql_user', password : 'test' }); connection.connect(); connection.query('SELECT * FROM ByName', function(err, rows, fields) { if (err) throw err; console.log(rows); }); connection.end();