Connect to Basecamp Data in DigitalSuite Studio through RunMyProcess DSEC

The CData JDBC Driver for Basecamp implements JDBC Standards and enables a applications ranging from BI to IDE to connect with Basecamp. In this article, we describe how to connect to Basecamp data from Arkobi Digital RunMyProcess's DSEC and connect to Basecamp in RunMyProcess.

Setting up EnterpriseConnect Agent

Configure the EnterpriseConnect Agent following the EnterpriseConnect page in the RunMyProcess documentation.

Setting up JDBC Adapter

The JDBC Adapter section describes the steps to connect to RDBMS through JDBC. Follow the steps and open the JDBC.config file.

1. Create a JSON entry for the CData JDBC Driver for Basecamp, e.g.

   Basecamp = {
    "sqlDriver" : "...",
    "sqlSource" : "...",
    "sqlDriverPath" : "..."
   }
   

2. Set the "sqlDriver" field to the Class name for the CData JDBC Driver, e.g.
   cdata.jdbc.basecamp.BasecampDriver
3. Set the "sqlSource" field to a JDBC URL for connecting to Basecamp, e.g.
   jdbc:basecamp:[email protected];Password=test123;

   Built-in Connection String Designer

   For assistance in constructing the JDBC URL, use the connection string designer built into the Basecamp JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

   java -jar cdata.jdbc.basecamp.jar
   

   Fill in the connection properties and copy the connection string to the clipboard.

   Basecamp uses basic or OAuth 2.0 authentication. To use basic authentication you will need the user and password that you use for logging in to Basecamp. To authenticate to Basecamp via OAuth 2.0, obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties by registering an app with Basecamp.

   See the Getting Started section in the help documentation for a connection guide.

   Additionally, specify the AccountId connection property. This can be copied from the URL after you log in.

   👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
   
4. Set the "sqlDriverPath" field to the name of the CData JDBC Driver JAR file, e.g.
   cdata.jdbc.basecamp.jar

Sample JDBC.config File

#DBAgent Configuration
Basecamp = {"sqlDriver" : "cdata.jdbc.basecamp.BasecampDriver", "sqlSource" = "jdbc:basecamp:[email protected];Password=test123;","sqlDriverPath" = "cdata.jdbc.basecamp.jar" }

Put the JDBC driver JAR file (cdata.jdbc.basecamp.jar) into the same directory as unified-adapter-[version].jar.

👁 runmyprocess

Note: Make sure to put the CData license file (cdata.jdbc.basecamp.lic) into the same directory. Since the license is generated based on the unique identifier of the machine where the product in installed, you will need an offline activation if you want to put the file on another machine.

Starting DigitalSuite EnterpriseConnect Agent

In Windows, start RunMyProcess DigitalSuite EnterpriseConnect Agent in Windows services. To start the application through command line, see Starting the EnterpriseConnect Agent in the RunMyProcess documents.

Starting the JDBC Adapter

Start the JDBC Adapter from runAdapter.bat. Once the Adapter is running, you can access the application through the agent address (e.g. 127.0.0.1:8080). Below is an example executing the command in Windows.

... > java -Djava.util.logging.config.file=./log.properties -cp lib/* org.runmyprocess.sec2.AdapterHandler :
2021-06-09 14:37:58|INFO|correlationId=|Searching for config file...
2021-06-09 14:37:58|INFO|correlationId=|Adapter Handler started with [JDBC] configuration
2021-06-09 14:37:59|INFO|correlationId=|agent address: 127.0.0.1:8080
2021-06-09 14:38:00.251:INFO::ConnectionThread: Logging initialized @1820ms to org.eclipse.jetty.util.log.StdErrLog
2021-06-09 14:38:00|INFO|correlationId=|onConnect() websocket connection between Agent and Adapter established

Once the DigitalSuite EnterpriseConnect Agent and JDBC Adapter are running, access http://localhost:(specified-port-number)/ through your browser to open the page shown below.

👁 runmyprocess

Check the availability of the JDBC Adapter using tools such as Postman or cURL. Here, we use Postman to send the HTTP POST request.

Configure the RequestHeader as follows:

Content-Type application/json

Configure the RequestBody as follows:

{
	"protocol":"JDBC",
	"data":{
		"DBType":"Basecamp",
		"sqlUsername":"",
		"sqlPassword":"",
		"sqlStatement":"SELECT * FROM Projects"
	}
}

If the JDBC.config file contains credential information, sqlUsername and sqlPassword can be left empty. If you are not sure of the table name, you can retrieve the list of tables using the request SELECT * FROM sys_tables

The request is successful if the Status is 200 and the Body contains Basecamp data in JSON format.

👁 runmyprocess

Connect to Basecamp through DSEC Agent in DigitalSuite Studio

Create a DigitalSuite Studio project and then create a Provider in the project.

• URL: The URL for accessing JDBC Agent (e.g. http:localhost:8080/)
• Authentication Scheme: Login/password
• Login: The value from agent.user in the application.properties file
• Password: agent.password in the application.properties file
• Secured: Checked
• Use DigitalSuite EnterpriseConnect: Checked
• With domain: The value from agent.domain in application.properties file

👁 runmyprocess

Next, create a Connector in the Provider.

• Connector URL: Leave this empty
• Architecture: REST/XML-RPC
• Method: POST
• Result format: JSON
• Accept media type: application/json
• Character set: Automatic
• Content: Same as the Request body used in the JDBC Adapter
• Content type: application/json

👁 runmyprocess

The JSON data we used as the Request body in JDBC Adapter:

{
	"protocol":"JDBC",
	"data":{
		"DBType":"Basecamp",
		"sqlUsername":"",
		"sqlPassword":"",
		"sqlStatement":"SELECT * FROM Projects"
	}
}

Open Launch Test to perform the test. The test is successful if Basecamp data is shown in Result on the right pane.

👁 runmyprocess

Now you can use Basecamp data in RunMyProcess DigitalSuite Studio through DSEC.

For the detailed information on supported SQL commands, refer to the SQL Compliance section in our help documentation. For information on tables, refer to the Data Model section.