Introduced in the 14.10 OLAP Solutions release, Teradata OLAP Server provides an XMLA service hosted on JBoss 7.1.1 to provide data access interaction between SAP BusinessObjects (BO) 4.1 and the Teradata ROLAP environment. The Teradata OS solution requires deploying one or more Web service WAR files to the JBoss deployment environment. We have recently introduced a toolbox to facilitate the deployment and configuration of these Web services.

Deploying Web Service

This article describes how to use the Teradata OLAP Server Deployment Toolbox to successfully deploy your XMLA web services to the JBoss deployment environment.

Before launching the Teradata OLAP Server Deployment Toolbox, you must gather the following information.

  • XMLAWebService – This is the path to the XMLAWebService.war file found in the Teradata OLAP Server installation directory. By default, the path will be the directory <Teradata OLAP Server install location>\deployment. Unless the installation location was altered, this should equate to C:\Program Files\Teradata\Client\14.10\Teradata OLAP Server\deployment.
  • Web service name – This is the name of the Web service you intend to deploy. The value chosen will impact the URL via which the SAP BO accesses the Teradata OLAP Server. For example, if you specify a Web service name of MarketingEOMReports, the Web service will be available at the URL http://<jbossmachinename:portnumber>/MarketingEOMReports.
  • ODBC Data Source Name (DSN) – Teradata OLAP Server utilizes the 64 bit ODBC driver to connect to the Teradata Database machine. You must define a 64 bit data source with appropriate credentials to access the databases and tables which will be accessed to produce your reports.

Once this information has been derived, it’s time to launch the Teradata OLAP Server Deployment Toolbox. The toolbox can be launched from the Start menu via the Teradata Client 14.10/Teradata OLAP Server Deployment Toolbox shortcut.  Alternatively, you can run the executable directly. The executable file is located in the <Teradata OLAP Server install location>\Tools\Teradata OLAP Server Deployment Toolbox directory. Unless the installation location was altered, this should equate to C:\Program Files\Teradata\Client\14.10\Teradata OLAP Server\Tools\Teradata OLAP Server Deployment Toolbox.  To launch the toolbox from the toolbox directory, double click the Teradata OLAP Server Deployment Toolbox.exe executable file.

Once the toolbox is launched, the welcome screen is displayed. Press the Deploy Teradata OLAP Server to proceed.

On the next screen, enter the Teradata OLAP Server WAR File Location, Web service Name and ODBC DSN Name you gathered previously. To begin the deployment process, press Next.

The toolbox performs some validation tasks prior to deploying the WAR file. Validation progress is displayed at the bottom of the screen. Any validation issues identified are reported to allow you an opportunity to resolve them and restart the deployment process.

Once validation is complete, the toolbox begins the process of deploying the WAR file. If the Web service name you provided conflicts with an existing deployment, the toolbox displays the following dialog, allowing you the option to overwrite (replace) the existing deployment.

Once deployment completes, the toolbox displays a summary page indicating the directory location where the WAR file was deployed within JBoss and the Web service URL (Note: URL assumes you have chosen to invoke JBoss with the –b option to bind JBoss to all listen IP addresses on the host. If not, substitute localhost for the host name portion of the URL).

Validating Deployment

If JBoss was operational at the time you ran the toolbox to perform the deploy, JBoss should have detected the deployment request and automatically started the new Web service. If JBoss was not active, you’ll want to start JBoss now to bring up the Web service. Once the Web service is active, confirm you can access the Web service via a browser window.  Please see the Teradata OLAP Server User Guide (B035-4109-053K) for more details on how to properly configure the host machine, administer JBoss and validate proper deployment of Web services.


josephferrao 3 comments Joined 07/14
31 Jul 2014

Will this version of OLAP server be compatible with Teradata 14.00 or 13.10 servers? We currently have 13.00 and upgrading to 14.00 with the 14.10 ODBC driver.
Joe Ferrao

Joe Ferrao

geonil 5 comments Joined 12/09
01 Aug 2014

Hi Joe,
Teradata OLAP Server supports following TD Databases and ODBC.
• Teradata Database versions 13.00, 13.10, 14.00, and 14.10
• Teradata Schema Workbench 14.10
Teradata Schema Workbench can connect to Teradata Database versions:
• or later
• or later
• 14.00.00 or later
• 14.10 or later
Teradata Schema Workbench supports the following Teradata ODBC Driver versions:
• or later
• or later
• 14.00.04 or later
• 14.10 or later
If possible, latest Databases and ODBC is always better.

josephferrao 3 comments Joined 07/14
02 Sep 2014

Hi Geonil,
Thanks a bunch for your response. We are definitely planning to use Teradata OLAP Server (Database being 14.10) and SAP BusinessObjects 4.1 for OLAP Analysis using the XMLA Webservice.
I have a followup question. I couldn't get a definitive answer in the fourms. Currently in BOBJ we have QUERY_BAND set up in BOBJ universes, to track which BOBJ user has been running a query via a BOBJ report / universe. I know QUERYBANDING exists for Teradata OLAP Connector but not sure how to set that up in BOBJ using OLAP Server.
Any pointers would be much appreciated.
Regards & Thanks - Joe

Joe Ferrao

bevzerov 1 comment Joined 09/10
03 Sep 2014

Hi Joe,
A-OLAP does not have a feature to enter Query Band.  Currently Teradata OLAP Connector (TOC) has a built in/preset Query Band setting that cannot be changed. Query Band for SESSION from TOC looks like this:
=S> UserId=DBC;ApplicationName=MDX-XMLA Provider for OLAP;Version=;Schema=TAA;
If you have a request for a customer to have Query Band setting allowed, this would have to be worked through Product Manager (Mark Hasenstab) to be implemented in the future.
Boris Evzerov

Boris Evzerov

You must sign in to leave a comment.