SingleStore Reporting in OBIEE with the SingleStore JDBC Driver

The CData JDBC Driver for SingleStore is a standard database driver that can integrate real-time access to SingleStore data into your Java-based reporting server. This article shows how to deploy the driver to Oracle Business Intelligence Enterprise Edition (OBIEE) and create reports on SingleStore data that reflect any changes.

Deploy the JDBC Driver

Follow the steps below to add the JDBC driver to WebLogic's classpath.

For WebLogic 12.2.1, simply place the driver JAR and .lic file into DOMAIN_HOME\lib; for example, ORACLE_HOME\user_projects\domains\MY_DOMAIN\lib. These files will be added to the server classpath at startup.

You can also manually add the driver to the classpath: This is required for earlier versions. Prepend the following to PRE_CLASSPATH in setDomainEnv.cmd (Windows) or setDomainEnv.sh (Unix). This script is located in the bin subfolder of the folder for that domain. For example: ORACLE_HOME\user_projects\domains\MY_DOMAIN\bin.

set PRE_CLASSPATH=your-installation-directory\lib\cdata.jdbc.singlestore.jar;%PRE_CLASSPATH%

Restart all servers; for example, run the stop and start commands in DOMAIN_HOME\bitools\bin.

Create a JDBC Data Source for SingleStore

After deploying the JDBC driver, you can create a JDBC data source from BI Publisher.

1. Log into BI Publisher, at the URL http://localhost:9502/analytics, for example, and click Administration -> Manage BI Publisher.
2. Click JDBC Connection -> Add Data Source.
3. Enter the following information:
   • Data Source Name: Enter the name that users will create connections to in their reports.
   • Driver Type: Select Other.
   • Database DriverClass: Enter the driver class, cdata.jdbc.singlestore.SingleStoreDriver.
   • Connection String: Enter the JDBC URL.

     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.

     👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
     

     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;

   • Username: Enter the username.
   • Password: Enter the password.
4. In the Security section, select the allowed user roles. 👁 The required settings for a JDBC data source. (Salesforce is shown.)
   

Create Real-Time SingleStore Reports

You can now create reports and analyses based on real-time SingleStore data. Follow the steps below to use the standard report wizard to create an interactive report that reflects any changes to SingleStore data.

1. On the global header, click New -> Data Model.
2. On the Diagram tab, select SQL query in the menu.
3. Enter a name for the query and in the Data Source menu select the SingleStore JDBC data source you created.
4. Select standard SQL and enter a query like the following:

   SELECT ShipName, ShipCity FROM Orders WHERE ShipCountry = 'USA'

   👁 The SQL query to be used to create the data set for the report's data model. (Salesforce is shown.)
   
5. Click View Data to generate the sample data to be used as you build your report.
6. Select the number of rows to include in the sample data, click View, and then click Save As Sample Data.
7. Click Create Report -> Use Data Model.
8. Select Guide Me and on the Select Layout page select the report objects you want to include. In this example we select Chart and Table.
9. Drop a numeric column like ShipCity onto the Drop Value Here box on the y-axis. Drop a dimension column like ShipName onto the Drop Label Here box on the x-axis. 👁 The dimensions and measures for a chart. (Salesforce is shown.)
   
10. Click Refresh to pick up any changes to the SingleStore data. 👁 An interactive, refresh-on-demand report. (Salesforce is shown.)