Connect SQL Analysis Services to IBM WebSphere Using the CData JDBC Driver

IBM WebSphere is a powerful application server that runs many enterprise level Java applications and services. When paired with the CData JDBC Driver for SQL Analysis Services, IBM WebSphere applications can connect to SQL Analysis Services and work with data using standard SQL queries instead of complex APIs. This simplifies integration, reduces development effort, and provides secure, real-time access to critical business data.

Prerequisites

1. Access to a SQL Analysis Services account (with API permissions)
2. IBM WebSphere Application Server (configured and running)
3. CData JDBC Driver for SQL Analysis Services
4. Java Servlet WAR application ready for deployment

Note: This article uses Salesforce as a demonstration data source, but the same steps can be followed to connect to any of the 250+ JDBC Drivers available in our portfolio.

Getting Started

Step 1: Download and install the CData JDBC Driver for SQL Analysis Services

Download and install the CData JDBC Driver for SQL Analysis Services, which provides a .jar file: cdata.jdbc.ssas.jar

Step 2: Install and configure IBM Websphere

1. Create an account in IBM WebSphere using the official IBM site.
2. Install and configure the IBM Websphere Application server in the local system using the documentation: IBM Websphere Application Server
3. Once the application server is installed, start the WebSphere Server using the Admin Console in your browser: https://your-server:9043/ibm/console

Step 3: Set up the JDBC provider and data source for SQL Analysis Services

1. Go to Resources, expand the JDBC section, and then select JDBC providers to create a new provider

2. Select the appropriate scope from the drop down menu

3. Click New to add a JDBC provider
• Choose User defined as the database type
• Enter cdata.jdbc.ssas.SSASConnectionPoolDataSource as the implementation class name
• Type a name for the provider, for example User defined JDBC Provider
• Enter the full path of the JDBC driver JAR file in the classpath field
• Click Next, then Finish, and save the changes to the master configuration.

4. Once the JDBC provider is created, add a JDBC data source.
• Enter the basic details such as Data Source Name and JNDI name
• Select the existing JDBC provider created earlier (e.g., CData SQL Analysis Services Provider)
• Provide the Implementation class name: cdata.jdbc.ssas.SSASConnectionPoolDataSource
• Add the Data Store Helper Class Name: com.ibm.websphere.rsadapter.GenericDataStoreHelper
• Configure security by setting authentication aliases if required
• Review the Summary page to verify all details and click Finish to complete the data source creation

5. Select the newly created data source from the list and open Custom properties
6. Add the JDBC connection string under the URL property and press OK. For example:

   jdbc:ssas:RTK=5246...;User=myuseraccount;Password=mypassword;URL=http://localhost/OLAP/msmdpump.dll;

   To connect, provide authentication and set the Url property to a valid SQL Server Analysis Services endpoint. You can connect to SQL Server Analysis Services instances hosted over HTTP with XMLA access. See the Microsoft documentation to configure HTTP access to SQL Server Analysis Services.

   To secure connections and authenticate, set the corresponding connection properties, below. The data provider supports the major authentication schemes, including HTTP and Windows, as well as SSL/TLS.

   • HTTP Authentication

     Set AuthScheme to "Basic" or "Digest" and set User and Password. Specify other authentication values in CustomHeaders.

   • Windows (NTLM)

     Set the Windows User and Password and set AuthScheme to "NTLM".

   • Kerberos and Kerberos Delegation

     To authenticate with Kerberos, set AuthScheme to NEGOTIATE. To use Kerberos delegation, set AuthScheme to KERBEROSDELEGATION. If needed, provide the User, Password, and KerberosSPN. By default, the data provider attempts to communicate with the SPN at the specified Url.

   • SSL/TLS:

     By default, the data provider attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store. To specify another certificate, see the SSLServerCert property for the available formats.

   You can then access any cube as a relational table: When you connect the data provider retrieves SSAS metadata and dynamically updates the table schemas. Instead of retrieving metadata every connection, you can set the CacheLocation property to automatically cache to a simple file-based store.

   See the Getting Started section of the CData documentation, under Retrieving Analysis Services Data, to execute SQL-92 queries to the cubes.

   Built-in Connection String Designer

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

         java -jar cdata.jdbc.ssas.jar
         

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

   

   Note: If the URL property is not available, create it and then add the JDBC connection string.

   Tip: Always test the connection string with the driver before entering it in the URL property.
7. Now open the data source and choose Test Connection

Step 4: Build the web application

1. Build the web application using preferred Java framework (Servlet, JSP, or Spring). The resulting .war file will typically follow a structure like this:

		SQL Analysis ServicesServletApp.war
		|--webcontent
		|  |--index.jsp                 -- JSP page (entry point)
		|  |
		|  |--WEB-INF/                  --Hidden from direct browser access
		|     |--web.xml                 -- Deployment descriptor
		|     |
		|     |--classes/                  --Compiled .class files
		|       |--com/example/SQL Analysis Services/
		|          |--SQL Analysis ServicesServlet.class
		|
		|--lib/                      --Dependency JARs
		|--cdata.jdbc.ssas.jar
	

2. Define the data access logic using JDBC or JPA, referencing the data source through a JNDI name
3. This article walks through JDBC connection setup and deploying a Java Servlet application
4. Package the project as a WAR (Web Application Archive) or EAR (Enterprise Archive) file for deployment
• In a terminal compile the java file using the command:

  			cd webcontent
  			jar cvf ..\SQL Analysis ServicesServletApp.war *
  		

Step 5: Deploy the SQL Analysis Services application in WebSphere

1. In the WebSphere admin console, go to Applications and select Install New Application
2. Browse and upload the WAR file, then continue with the installation wizard.

Step 6: Retrieve SQL Analysis Services data through WebSphere

1. Access the application using its context root: http://hostname:port/context-root/page
Note: Ensure the deployed application is started before opening it in the browser.

We can now view the retrieved data from the source. The data is accessible directly through IBM WebSphere. This setup demonstrates how a servlet can be deployed in WebSphere to retrieve SQL Analysis Services data using the JDBC driver, creating a strong foundation for building advanced SQL Analysis Services powered enterprise applications.

Get Started with Connecting SQL Analysis Services to IBM WebSphere

Start connecting SQL Analysis Services to IBM WebSphere with the CData JDBC Connector today. Download the free 30-day trial and explore how easy it is to enable secure, real-time data access for your applications. As always, our world-class Support Team is available to help with any questions you may have.