Connect to Sybase Data in RunMyProcess through Connect AI

Akorbi Digital RunMyProcess makes it easy to create applications for complex business applications, such as budget application and contract management. CData Connect AI creates a live connection to Sybase and can be used to generate an OData API (natively supported in RunMyProcess) for Sybase. By pairing RunMyProcess with CData Connect AI, 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 AI from RunMyProcess as you would any other REST service and get instant, live access to your Sybase data.

In this article, we walk through connecting to Sybase from CData Connect AI and accessing Sybase data through an OData feed in RunMyProcess.

Connect to Sybase from RunMyProcess

To work with live Sybase data in RunMyProcess, we need to connect to Sybase from Connect AI, provide user access to the connection, and create a Workspace for the Sybase data.

Connect to Sybase 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. Select "Sybase" from the Add Connection panel

3. Enter the necessary authentication properties to connect to Sybase.

   To connect to Sybase, specify the following connection properties:

   • Server: Set this to the name or network address of the Sybase database instance.
   • Database: Set this to the name of the Sybase database running on the specified Server.

   Optionally, you can also secure your connections with TLS/SSL by setting UseSSL to true.

   Sybase supports several methods for authentication including Password and Kerberos.

   Connect Using Password Authentication

   Set the AuthScheme to Password and set the following connection properties to use Sybase authentication.

   • User: Set this to the username of the authenticating Sybase user.
   • Password: Set this to the username of the authenticating Sybase user.

   Connect using LDAP Authentication

   To connect with LDAP authentication, configure Sybase server-side to use the LDAP authentication mechanism.

   After configuring Sybase for LDAP, you can connect using the same credentials as Password authentication.

   Connect Using Kerberos Authentication

   To leverage Kerberos authentication, begin by enabling it setting AuthScheme to Kerberos. See the Using Kerberos section in the Help documentation for more information on using Kerberos authentication.

   You can find an example connection string below:

   Server=MyServer;Port=MyPort;User=SampleUser;Password=SamplePassword;Database=MyDB;Kerberos=true;KerberosKDC=MyKDC;KerberosRealm=MYREALM.COM;KerberosSPN=server-name

   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add Sybase Connection page and update the User-based 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.
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

Configure Sybase Endpoints for RunMyProcess

After connecting to Sybase, 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).
2. Click Add to add new assets to the Workspace.
3. Select the Sybase connection (e.g. Sybase1) and click Next.
4. Select the table(s) you wish to work with and click Confirm.
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 Sybase data from RunMyProcess.

Retrieve Sybase Data from RunMyProcess DigitalSuite Studio

With the connection to Sybase and OData endpoints created, we are ready to add Sybase data to RunMyProcess for Retrieval.

Create a Provider

1. Log into RunMyProcess and open DigitalSuite Studio.
2. Click Resources to bring up the Resources page, then select then the CONNECTORS tab.
3. Click the + (New Provider) button to create a new provider, choose the account to use, then click Confirm.
4. In the provider settings page, configure the following properties.
   • URL: Set the OData endpoint in the Connect AI OData page: https://cloud.cdata.com/api/odata/{workspace_name}.
   • Authentication Schema: Select Login/Password.
   • Login: Specify a CData Connect AI username (e.g. [email protected]).
   • Password: Specify the PAT of the Connect AI user.
   
5. 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.'
6. Click Save to save the properties.

Retrieve Sybase Data by Creating a Connector

1. In the CONNECTORS tab, click the button with three dots to create the provider, then select Add connector from the menu.
2. In the following page, set Connector URL to the OData endpoint configured in Connect AI (e.g. https://cloud.cdata.com/api/odata/{workspace_name})
3. 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 Sybase data. For more information on creating OData feeds from Sybase (and more than 100 other data sources), visit the Connect AI page. Sign up for a free trial and start working with live Sybase data in RunMyProcess.