Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Connect to SingleStore Data in RunMyProcess through Connect Cloud
Use CData Connect Cloud to create on OData API for SingleStore Data and connect to SingleStore data in Akorbi Digital RunMyProcess.
Akorbi Digital RunMyProcess makes it easy to create applications for complex business applications, such as budget application and contract management. CData Connect Cloud creates a live connection to SingleStore and can be used to generate an OData API (natively supported in RunMyProcess) for SingleStore. By pairing RunMyProcess with CData Connect Cloud, you get true cloud-to-cloud connectivity to all your SaaS and cloud-based Big Data and NoSQL sources - no need to migrate your data or write your own integrations. Simply connect to Connect Cloud from RunMyProcess as you would any other REST service and get instant, live access to your SingleStore data.
In this article, we walk through connecting to SingleStore from CData Connect Cloud and accessing SingleStore data through an OData feed in RunMyProcess.
Connect to SingleStore from RunMyProcess
To work with live SingleStore data in RunMyProcess, we need to connect to SingleStore from Connect Cloud, provide user access to the connection, and create OData endpoints for the SingleStore data.
(Optional) Add a New Connect Cloud User
As needed, create Users to connect to SingleStore through Connect Cloud.
- Navigate to the Users page and click Invite Users
- Enter the new user's email address and click Send to invite the user
- You can review and edit users from the Users page
Add a Personal Access Token
If you are connecting from a service, application, platform, or framework that does not support OAuth authentication, you can create a Personal Access Token (PAT) to use for authentication. Best practices would dictate that you create a separate PAT for each service, to maintain granularity of access.
- Click on your username at the top right of the Connect Cloud app and click User Profile.
- On the User Profile page, scroll down to the Personal Access Tokens section and click Create PAT.
- Give your PAT a name and click Create.
- The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
Connect to SingleStore from Connect Cloud
CData Connect Cloud uses a straightforward, point-and-click interface to connect to data sources.
- Log into Connect Cloud, click Connections and click Add Connection
- Select "SingleStore" from the Add Connection panel
-
Enter the necessary authentication properties to connect to SingleStore.
The following connection properties are required in order to connect to data.
- Server: The host name or IP of the server hosting the SingleStore database.
- Port: The port of the server hosting the SingleStore database.
- Database (Optional): The default database to connect to when connecting to the SingleStore Server. If this is not set, tables from all databases will be returned.
Connect Using Standard Authentication
To authenticate using standard authentication, set the following:
- User: The user which will be used to authenticate with the SingleStore server.
- Password: The password which will be used to authenticate with the SingleStore server.
Connect Using Integrated Security
As an alternative to providing the standard username and password, you can set IntegratedSecurity to True to authenticate trusted users to the server via Windows Authentication.
Connect Using SSL Authentication
You can leverage SSL authentication to connect to SingleStore data via a secure session. Configure the following connection properties to connect to data:
- SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
- SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
- SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
- SSLClientCertType: The certificate type of the client store.
- SSLServerCert: The certificate to be accepted from the server.
Connect Using SSH Authentication
Using SSH, you can securely login to a remote machine. To access SingleStore data via SSH, configure the following connection properties:
- SSHClientCert: Set this to the name of the certificate store for the client certificate.
- SSHClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
- SSHClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
- SSHClientCertType: The certificate type of the client store.
- SSHPassword: The password that you use to authenticate with the SSH server.
- SSHPort: The port used for SSH operations.
- SSHServer: The SSH authentication server you are trying to authenticate against.
- SSHServerFingerPrint: The SSH Server fingerprint used for verification of the host you are connecting to.
- SSHUser: Set this to the username that you use to authenticate with the SSH server.
- Click Create & Test
- Navigate to the Permissions tab in the Add SingleStore Connection page and update the User-based permissions.
Configure SingleStore Endpoints for RunMyProcess
After connecting to SingleStore, create a workspace and virtual dataset for your desired table(s).
- Navigate to the Virtual Datasets page and click Add to create a new Workspace (or select an existing workspace).
- Click Add to add new assets to the Workspace.
- Select the SingleStore connection (e.g. SingleStore1) and click Next.
- Select the table(s) you wish to work with and click Confirm.
- Make note of the OData Service URL for your workspace, e.g. https://cloud.cdata.com/api/odata/{workspace_name}
Sample URLs for OData Feeds
Once you have configured a connection to SingleStore, created a user, and created OData endpoints in Connect Cloud, you can access OData feeds for SingleStore data. Below, you will see the URLs to access tables and the list of tables. For information on accessing the tables, you can navigate to the OData page for Connect Cloud. For the URLs, you will need the URL of Connect Cloud: https://cloud.cdata.com/api/odata/{workspace_name}.
Table | URL | |
---|---|---|
Entity (table) List | https://cloud.cdata.com/api/odata/{workspace_name}/ | |
Metadata | https://cloud.cdata.com/api/odata/{workspace_name}/$metadata | |
Orders | https://cloud.cdata.com/api/odata/{workspace_name}/Orders |
As with standard OData feeds, if you wish to limit the fields returned, you can add a $select parameter to the query, along with other standard OData URL parameters, such as $filter, $orderby, $skip, and $top. See the help documentation for more information on supported OData queries.
With the connection and Workspace configured, you are ready to connect to SingleStore data from RunMyProcess.
Retrieve SingleStore Data from RunMyProcess DigitalSuite Studio
With the connection to SingleStore and OData endpoints created, we are ready to add SingleStore data to RunMyProcess for Retrieval.
Create a Provider
- Log into RunMyProcess and open DigitalSuite Studio.
- Click Resources to bring up the Resources page, then select then the CONNECTORS tab.
- Click the + (New Provider) button to create a new provider, choose the account to use, then click Confirm.
- In the provider settings page, configure the following properties.
- URL: Set the OData endpoint in the Connect Cloud OData page: https://cloud.cdata.com/api/odata/{workspace_name}.
- Authentication Schema: Select Login/Password.
- Login: Specify a CData Connect Cloud username (e.g. user@mydomain.com).
- Password: Specify the PAT of the Connect Cloud user.
- Fill in the same properties in the ACCEPTANCE and TEST tabs. Note: You can copy the configured settings by clicking 'Copy this configuration button,' then pasting the content in the new tab by clicking 'Paste previously copied configuration.'
- Click Save to save the properties.
Retrieve SingleStore Data by Creating a Connector
- In the CONNECTORS tab, click the button with three dots to create the provider, then select Add connector from the menu.
- In the following page, set Connector URL to the OData endpoint configured in Connect Cloud (e.g. https://cloud.cdata.com/api/odata/{workspace_name})
- Click Save then Launch to test the connector execution. Click Launch test to execute. The process is successful if you get the JSON response of your configured table information.
More Information & Free Trial
Now, you have created a provider and connector to retrieve SingleStore data. For more information on creating OData feeds from SingleStore (and more than 100 other data sources), visit the Connect Cloud page. Sign up for a free trial and start working with live SingleStore data in RunMyProcess.