Ready to get started?

Download a free trial of the SingleStore Driver to get started:

 Download Now

Learn more:

SingleStore Icon SingleStore JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with SingleStore.

Create an SAP BusinessObjects Universe on the CData JDBC Driver for SingleStore



Provide connectivity to SingleStore data through an SAP BusinessObjects universe.

This article shows how to use the CData JDBC Driver for SingleStore to connect to SingleStore from SAP BusinessObjects Business Intelligence applications. You will use the Information Design Tool to analyze SingleStore data and create a universe on the CData JDBC Driver for SingleStore. You will then connect to the universe from Web Intelligence.

Create the JDBC Connection to SingleStore

Follow the steps below to create a connection to the SingleStore JDBC data source in the Information Design Tool.

  1. Copy the CData JAR and .lic file into the following subfolder in the installation directory for BusinessObjects: dataAccess\connectionServer\jdbc\drivers\jdbc. The CData JAR is located in the lib subfolder of the installation directory.
  2. Right-click your project and click New -> New Relational Connection.
  3. In the wizard that results, click Generic -> Generic JDBC datasource -> JDBC Drivers.
  4. On the next page of the wizard enter the connection details.
  5. On the next page, set the Authentication Mode option to "Use specified username and password". Enter the username, password, and JDBC URL. The JDBC URL begins with jdbc:singlestore: and is followed by a semicolon-separated list of connection properties.

    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.

    Built-in Connection String Designer

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

    java -jar cdata.jdbc.singlestore.jar

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

    When you configure the JDBC URL, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

    A typical JDBC URL is below:

    jdbc:singlestore:User=myUser;Password=myPassword;Database=NorthWind;Server=myServer;Port=3306;
  6. Enter the driver class: cdata.jdbc.singlestore.SingleStoreDriver
  7. Finish the wizard with the default values for connection pooling and custom parameters.

Analyze SingleStore Data in the Information Design Tool

You can use the JDBC connection to analyze SingleStore data in the Information Design Tool.

  1. In the Local Projects view, double-click the connection (the .cnx file) to open the SingleStore data source.
  2. On the Show Values tab, you can load table data and enter SQL queries. To view table data, expand the node for the table, right-click the table, and click Show Values. Values will be displayed in the Raw Data tab.
  3. On the Analysis tab, you can then analyze data by dragging and dropping columns onto the axes of a chart.

Publish the Local Connection

To publish the universe to the CMS, you additionally need to publish the connection.

  1. In the Local Projects view, right-click the connection and click Publish Connection to a Repository.
  2. Enter the host and port of the repository and connection credentials.
  3. Select the folder where the connection will be published.
  4. In the success dialog that results, click Yes to create a connection shortcut.

Create a Universe on the JDBC Driver for SingleStore

You can follow the steps below to create a universe on the JDBC driver. The universe in this example will be published to a repository, so it uses the published connection created in the previous step.

  1. In the Information Design Tool, click File->New Universe.
  2. Select your project.
  3. Select the option to create the universe on a relational data source.
  4. Select the shortcut to the published connection.
  5. Enter a name for the Data Foundation.
  6. Import tables and columns that you want to access as objects.
  7. Enter a name for the Business Layer.

Publish the Universe

You can follow the steps below to publish the universe to the CMS.

  1. In the Local Projects view, right-click the business layer and click Publish -> To a Repository.
  2. In the Publish Universe dialog, enter any integrity checks before importing.
  3. Select or create a folder on the repository where the universe will be published.

Query SingleStore Data in Web Intelligence

You can use the published universe to connect to SingleStore in Web Intelligence.

  1. Copy the cdata.jdbc.singlestore.lic file to the following subfolder in the BusinessObjects installation directory: \dataAccess\connectionServer\jdbc\drivers\jdbc. The license file is located in the lib subfolder of the installation directory.
  2. Open Web Intelligence from the BusinessObjects launchpad and create a new document.
  3. Select the Universe option for the data source.
  4. Select the SingleStore universe. This opens a Query Panel. Drag objects to the Result Objects pane to use them in the query.