Teradata OLAP Server User Guide Release 14.10 B035-4109-053K September 2013
The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Active Data Warehousing, Active Enterprise Intelligence, Applications-Within, Aprimo, Aprimo Marketing Studio, Aster, BYNET, Claraview, DecisionCast, Gridscale, MyCommerce, Raising Intelligence, Smarter. Faster. Wins., SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, "Teradata Raising Intelligence" logo, Teradata ServiceConnect, Teradata Source Experts, "Teradata The Best Decision Possible" logo, The Best Decision Possible, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its affiliates in the United States and other countries. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. Apache, Apache Hadoop, Hadoop, and the yellow elephant logo are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. Apple, Mac, and OS X all are registered trademarks of Apple Inc. Axeda is a registered trademark of Axeda Corporation. Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda Access, Axeda Software Management, Axeda Service, Axeda ServiceLink, and Firewall-Friendly are trademarks and Maximum Results and Maximum Support are servicemarks of Axeda Corporation. Data Domain, EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of Oracle. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Hortonworks, the Hortonworks logo and other Hortonworks trademarks are trademarks of Hortonworks Inc. in the United States and other countries. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI is a registered trademark of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. NetVault is a trademark or registered trademark of Quest Software, Inc. in the United States and/or other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation. Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in the U.S.A. and other countries. Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc. Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries. Unicode is a registered trademark of Unicode, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners.
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN "AS-IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please email:
[email protected]. Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback.
Copyright © 2000-2013 by Teradata Corporation. All Rights Reserved.
Preface Purpose This book provides information about Teradata OLAP Server. The Teradata OLAP Server allows you to connect from XMLA-compatible Business Intelligence (BI) clients to a Teradata Database, enabling powerful query and analysis of your multi-dimensional data.
Audience This book is intended for use by: •
Users who interface with the Teradata Database
Supported Releases This book supports the following releases: •
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: •
13.00.00.10 or later
•
13.10.00.06 or later
•
14.00.00 or later
•
14.10 or later
Teradata Schema Workbench supports the following Teradata ODBC Driver versions: •
13.00.00.06 or later
•
13.10.00.05 or later
•
14.00.04 or later
•
14.10 or later
Prerequisites The following prerequisite knowledge is required for this product: •
Familiarity with multidimensional models, such as OLAP cubes
Teradata OLAP Server User Guide, Release 14.10
3
Preface Changes to This Book
•
Familiarity with BI concepts
•
Familiarity with XMLA client/UI products such as SAP BusinessObjects Analysis
•
JBoss Application Server 7 management concepts
Changes to This Book The following changes were made to this book in support of the current release. Changes are marked with change bars. For a complete list of changes to the product, see the Teradata OLAP Server Release Definition associated with this release. Date and Release
Description
September 2013 14.10
New document.
Additional Information Additional information that supports this product is available at the web sites listed in the table that follows. Type of Information
Description
Access to Information
Release overview
Use the Release Definition for the following information:
1 Go to http://www.info.teradata.com/.
• Overview of all of the products in the release • Information received too late to be included in the manuals • Operating systems and Teradata Database versions that are certified to work with each product • Version numbers of each product and the documentation for each product • Information about available training and the support center
3 Type 4109 in the Publication Product ID box.
Late information
4
2 Under Online Publications, click General Search. 4 Click Search. 5 Select the appropriate Release Definition from
the search results.
Teradata OLAP Server User Guide, Release 14.10
Preface Additional Information
Type of Information
Description
Access to Information
Additional product information
Use the Teradata Information Products web site to view or download specific manuals that supply related or additional information to this manual.
1 Go to http://www.info.teradata.com/. 2 Under the Online Publications subcategory,
Browse by Category, click Data Warehousing. 3 Do one of the following:
• For a list of Teradata Tools and Utilities documents, click Teradata Tools and Utilities, and then select an item under Releases or Products. • Select a link to any of the data warehousing publications categories listed. Other books related to Teradata OLAP Server are: • ODBC Driver for Teradata User Guide B035-2509 • Teradata Aggregate Designer User Guide B035-4103 • Teradata Schema Workbench User Guide B035-4106 CD-ROM images
Access a link to a downloadable CD-ROM image of all customer documentation for this release. Customers are authorized to create CD-ROMs for their use from this image.
1 Go to http://www.info.teradata.com/. 2 Under the Online Publications subcategory,
Browse by Category, click Data Warehousing. 3 Click CD-ROM Images. 4 Follow the ordering instructions.
Ordering information for manuals
Use the Teradata Information Products web site to order printed versions of manuals.
1 Go to http://www.info.teradata.com/. 2 Under Print & CD Publications, click How to
Order. 3 Follow the ordering instructions.
General information about Teradata
The Teradata home page provides links to numerous sources of information about Teradata. Links include:
1 Go to www.teradata.com. 2 Select a link.
• Executive reports, case studies of customer experiences with Teradata, and thought leadership • Technical information, solutions, and expert advice • Press releases, mentions, and media resources
Teradata OLAP Server User Guide, Release 14.10
5
Preface Additional Information
6
Teradata OLAP Server User Guide, Release 14.10
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Changes to This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Chapter 1: Teradata OLAP Server Windows Administration . . . . . . . . . . . . . . . 13 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Install the ODBC Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Create a Data Source Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Install a Java SE Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Download and Install JBoss Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Configure Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Start JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Test JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Stop JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Install the Teradata OLAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Configure Teradata OLAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Configure the Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Configure JVM Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Confirm Teradata OLAP Server Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Alternative Teradata OLAP Server Deployment Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Deploying Multiple Teradata OLAP Server Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Display the Version Number of Teradata OLAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Upgrade an Existing Teradata OLAP Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Uninstall the Teradata OLAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Teradata OLAP Server User Guide, Release 14.10
7
Table of Contents
Chapter 2: Teradata OLAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 SAP BusinessObjects Analysis, edition for OLAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Create a New OLAP Data Source Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Connect to a Teradata OLAP Server Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 SimbaO2X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Appendix A: Teradata OLAP Server Installation Checklist . . . . . . . . . . . . . . . . . . . .31
Appendix B: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Web Server Does Not Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Browsing to the XMLA Service Start Page Displays an Error . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Using Logging to Troubleshoot MDX and SQL Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Turning On Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Turning Off Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Capturing XMLA Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
8
Teradata OLAP Server User Guide, Release 14.10
List of Figures
Figure 1: Teradata OLAP Service Architecture Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Teradata OLAP Server User Guide, Release 14.10
9
List of Figures
10
Teradata OLAP Server User Guide, Release 14.10
List of Tables
Table 1: JVM Memory Allocation Parameters to Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Teradata OLAP Server User Guide, Release 14.10
11
List of Tables
12
Teradata OLAP Server User Guide, Release 14.10
CHAPTER 1
Teradata OLAP Server Windows Administration
The Teradata OLAP Server allows you to connect from XMLA-compatible Business Intelligence (BI) clients to a Teradata Database, enabling powerful query and analysis of your multi-dimensional data. This chapter describes how to install and configure Teradata OLAP Server on computers running a Microsoft® Windows® operating system and JBoss Application Server. Note: Installation and configuration instructions are presented in a progression. Some steps, as indicated, must be completed in the order listed. For your convenience, use the checklist available in Appendix A: “Teradata OLAP Server Installation Checklist.”
Architecture Figure 1 on page 14 illustrates the relationships between components involved in running the Teradata OLAP Server. Implementing the Teradata OLAP Server involves installing and testing each component.
Teradata OLAP Server User Guide, Release 14.10
13
Chapter 1: Teradata OLAP Server Windows Administration Software Requirements Figure 1: Teradata OLAP Service Architecture Diagram
Software Requirements Teradata OLAP Server is supported on the following operating systems, applications and libraries: •
Windows Server® 2008 R2 Service Pack 1 or Windows Server® 2012
•
Shared International Components for Unicode (ICU) Libraries for Teradata Version 14.00.00.00 or later (64-bit)
•
Teradata Global Security Services (GSS) Client Version 14.00.00.00 or later (64-bit)
•
ODBC Driver for Teradata Version 14.00.00.03 or later (64-bit) Note: Teradata OLAP Server uses 64-bit architecture, so the ODBC driver must use 64-bit architecture as well.
14
Teradata OLAP Server User Guide, Release 14.10
Chapter 1: Teradata OLAP Server Windows Administration Install the ODBC Driver
•
Java® SE Development Kit (JDK) 6 Update 35 or later (64-bit), or JDK 7 Update 10 or later (64-bit)
•
JBoss Application Server 7.1.1 Note: JBoss requires that you install a JDK, rather than a Java Runtime Environment (JRE).
Install the ODBC Driver Teradata OLAP Server communicates with the database using an Open Database Connectivity (ODBC) interface. To install the ODBC Driver for Teradata, you must install the following software in the following order: 1
Shared ICU Libraries for Teradata
2
Teradata GSS Client
3
ODBC Driver for Teradata
To install Shared ICU Libraries for Teradata: 1
In a new folder, extract the contents of the ZIP archive containing the 64-bit version of Shared ICU Libraries for Teradata.
2
In the \DISK1 subfolder, double-click to run the file named setup.exe.
3
In the Shared ICU Libraries for Teradata dialog, click the drop-down arrow next to the Language field, then select the language for the installation, and then click OK.
4
In the Installation Wizard, click Next.
5
Select the radio button to accept the terms of the license agreement if you agree, and then click Next.
6
To change the installation location, click the Change button, then browse to the desired folder, and then click OK. To accept the installation location, click Next.
7
Click Install.
8
When the installation completes, click Finish.
To install the Teradata GSS Client: 1
In a new folder, extract the contents of the ZIP archive containing the 64-bit version of the Teradata GSS Client.
2
Double-click to run the file named setup.exe.
3
In the Teradata GSS Client dialog, click the drop-down arrow next to the Language field, then select the language for the installation, and then click OK.
4
In the Installation Wizard, click Next.
Teradata OLAP Server User Guide, Release 14.10
15
Chapter 1: Teradata OLAP Server Windows Administration Create a Data Source Name 5
Select the radio button to accept the terms of the license agreement if you agree, and then click Next.
6
Click Install.
7
When the installation completes, click Finish
To install the 64-bit ODBC Driver for Teradata: 1
In a new folder, extract the contents of the ZIP archive containing the 64-bit version of the ODBC Driver for Teradata.
2
In the \DISK1 subfolder, double-click to run the file named setup.exe.
3
In the ODBC Driver for Teradata dialog, click the drop-down arrow next to the Language field, then select the language for the installation, and then click OK.
4
In the Installation Wizard, click Next.
5
Select the radio button to accept the terms of the license agreement if you agree, and then click Next.
6
To change the installation location, click the Change button, then browse to the desired folder, and then click OK. To accept the installation location, click Next.
7
Click Install.
8
When the installation completes, click Finish
Create a Data Source Name After installing the ODBC Driver for Teradata, you need to create a Data Source Name (DSN) for accessing your Teradata Database.
To create a new ODBC Driver for Teradata Data Source Name (DSN): 1
In Windows, click the Start menu, and then click Control Panel.
2
If you view the Control Panel by Category, then click System and Security.
3
Click Administrative Tools, and then double-click Data Sources (ODBC). Note: The 64-bit Windows operating system includes a 64-bit ODBC Data Source Administrator as well a 32-bit ODBC Data Source Administrator. The 64-bit ODBC Administrator is located at C:\Windows\System32\odbcad32.exe and runs when you double-click Data Sources (ODBC) in Administrative Tools in the Control Panel. The 32-bit ODBC Administrator is located at C:\Windows\SysWOW64\odbcad32.exe.
16
4
In the ODBC Data Source Administrator dialog, click the System DSN tab, and then click Add.
5
In the Create New Data Source dialog, click Teradata in the Name column, and then click Finish.
Teradata OLAP Server User Guide, Release 14.10
Chapter 1: Teradata OLAP Server Windows Administration Install a Java SE Development Kit 6
In the ODBC Driver Setup for Teradata Database dialog, type a name for your data source in the Name field in the Data Source area.
7
In the Description field, type relevant details about the DSN.
8
In the Name or IP Address field, type the host name or IP address of your Teradata Database server.
9
In the Authentication area, complete fields as needed for the DSN to connect to your Teradata Database.
10 In the Optional area, type appropriate values in the Default Database and Account String
fields as needed. 11 Click the Options button, then select driver options as needed to configure your DSN, and
then click OK. 12 In the ODBC Driver Setup for Teradata Database dialog, click OK to save your DSN. 13 Click OK to close the ODBC Data Source Administrator window.
Note: Test the DSN you created to ensure that the DSN successfully connects to your Teradata Database.
Install a Java SE Development Kit To install a Java SE Development Kit (JDK): 1
In your Web browser, type http://www.oracle.com/technetwork/java/javase/downloads/ index.html in the Address field, and then press Enter.
2
Download an appropriate version of the JDK.
3
Double-click to run the file you downloaded in step 2.
4
In the Installation Wizard, click Next.
5
To change the installation location for the JDK, click the Change button, then browse to the desired folder, and then click OK. To accept the installation location, click Next.
6
In the Java Setup – Destination Folder dialog, to change the installation location for the JDK, click the Change button, then browse to the desired folder, and then click OK. To accept the installation location, click Next.
7
When the installation completes, click Close.
Teradata OLAP Server User Guide, Release 14.10
17
Chapter 1: Teradata OLAP Server Windows Administration Download and Install JBoss Application Server
Download and Install JBoss Application Server To download JBoss Application Server: 1
In your Web browser, type http://www.jboss.org/jbossas in the Address field, and then press Enter.
2
Click the Downloads link, and then download the ZIP archive containing JBoss Application Server 7.1.1 Final.
3
In a new folder, extract the contents of the ZIP archive you downloaded in step 2.
4
Install the JBoss Application Server. For instructions on installing and configuring JBoss Application Server, see the README.txt file included in the JBoss Application Server download as well as JBoss documentation at https://docs.jboss.org/author/display/AS71/Documentation.
Configure Environment Variables The JAVA_HOME environment variable must specify the folder where the Java Development Kit is installed on the computer where you are installing Teradata OLAP Server. Note: For the remainder of this guide, the name JAVA_HOME is used to refer to the full pathname of the directory where the JDK is installed.
To set the JAVA_HOME environment variable: 1
Click the Start menu, and then click Control Panel.
2
If you view Control Panel by Category, then click System and Security.
3
Click System, and then click Advanced system settings.
4
In the System Properties dialog, click the Advanced tab, and then click the Environment Variables button.
5
Do one of the following: •
In the System Variables area, if the JAVA_HOME variable does not exist, then click the New button. In the New System Variable dialog, type JAVA_HOME in the Variable Name field. In the Variable Value field, type the path to the root folder of the Java Development Kit installation on the computer. For example, the path may be C:\Program Files\Java\jdk1.6.0_37. When finished, click OK.
•
If the JAVA_HOME variable exists, then ensure that variable value is correctly set as the path to the root folder of the JDK installation on the computer.
Note: Do not set the value of the JAVA_HOME environment variable to the path of the /bin subfolder.
18
Teradata OLAP Server User Guide, Release 14.10
Chapter 1: Teradata OLAP Server Windows Administration Start JBoss
You also need to set the JBOSS_HOME environment variable to specify the folder where the JBoss Application Server is installed. Note: For the remainder of this guide, the name JBOSS_HOME is used to refer to the full pathname of the directory where JBoss is installed.
To set the JBOSS_HOME environment variable: 1
Do one of the following: •
If the JBOSS_HOME environment variable does not exist in the System Variables area in the Environment Variables dialog, then click the New button. In the New System Variable dialog, type JBOSS_HOME in the Variable Name field. In the Variable Value field, type the path to the root folder of the JBoss Application Server installation on the computer. When finished, click OK.
•
If the JBOSS_HOME environment variable exists, then ensure that the variable value is correctly set as the path to the root folder of the JBoss Application Server installation on the computer.
Start JBoss To start JBoss: 1
Click the Start menu, then click All Programs, then click the Accessories folder, then rightclick Command Prompt, and then click Run as administrator. Note: Opening a new Command Prompt window is necessary to recognize any changes to environment variables that you made in the section “Configure Environment Variables” on page 18.
2
In the Command Prompt window, browse to the root folder where JBoss is installed.
3
Type cd bin, and then press Enter.
4
Type standalone.bat, and then press Enter. Note: Running standalone.bat without any parameters binds JBoss to the localhost IP address 127.0.0.1. As a result, the XMLA Service is not accessible from remote computers. For testing purposes, you can start JBoss by typing standalone.bat –b 0.0.0.0 to bind to all IP addresses, making the XMLA Service accessible from all remote computers. Binding JBoss to all IP addresses is not recommended for production systems due to a lack of security. See JBoss documentation at https://community.jboss.org/wiki/ JBossRunParameters for full details on run script parameters.
Note: Read the messages appearing in the Command Prompt window when JBoss starts to confirm that JBoss is operating successfully.
Teradata OLAP Server User Guide, Release 14.10
19
Chapter 1: Teradata OLAP Server Windows Administration Test JBoss
Test JBoss Confirm that your JBoss installation operates successfully prior to installing Teradata OLAP Server.
To confirm that JBoss is operating successfully: 1
Start JBoss using the procedure described in “Start JBoss” on page 19.
2
Open a web browser.
3
In the Address field, type a URL including the IP address to which your web server is bound, then type a colon (:), then type the port where the web server is listening, and then press Enter. For example, if your web server uses the default port and you bound the Web server to the IP address 127.0.0.1, then type http://localhost:8080/. If you successfully installed JBoss, then the browser displays a page informing you that the web server is running.
4
If other computers need to access the Teradata OLAP Server, then repeat step 3 on the other computers as needed to confirm that all computers can access your JBoss installation.
Stop JBoss To stop JBoss: 1
Select the Command Prompt window where you started JBoss, and then press Ctrl+C.
2
When prompted to terminate the batch job, type y, and then press Enter.
Install the Teradata OLAP Server Run the Teradata OLAP Server installer on the machine hosting the JBoss Application Server. After installation, you will find the following directory hierarchy in the installation location: •
deployment •
•
•
20
XmlaWebService.war
docs •
Release.txt
•
Teradata OLAP Server User Guide.pdf
scripts •
Native OLAP Connector Trace Settings Off.reg
•
Native OLAP Connector Trace Settings On.reg
Teradata OLAP Server User Guide, Release 14.10
Chapter 1: Teradata OLAP Server Windows Administration Configure Teradata OLAP Server
The XmlaWebService.war is a Web Archive File (WAR). This is a compressed archive used to distribute the Teradata OLAP Server web application. This WAR file must be deployed into the JBoss Application Server in order to activate the OLAP Server functionality.
To deploy Teradata OLAP Server: 1
In the folder %JBOSS_HOME%\standalone\deployments, create a folder named webapps if the folder does not already exist.
2
In the folder you created in step 1, extract the contents of the XmlaWebService.war file archive file. Folder name should be XmlaWebService.war.
3
Create an empty file with the name XmlaWebService.war.dodeploy in the webapps directory to instruct JBoss to deploy the OLAP Service on startup.
Configure Teradata OLAP Server To configure Teradata OLAP Server, you need to set: •
The data source
•
Memory options
Configure the Data Source The DataSources.xml file specifies the Data Source Name (DSN) that Teradata OLAP Server uses. Note: When editing elements in the DataSources.xml file, avoid using special characters such as &, , " or '.
To edit the DataSources.xml file: 1
In a text editor, open the file JBOSS_HOME\standalone\deployments\webapps\ XmlaWebService.war\WEB-INF\classes\com\simba\DataSources.xml.
2
In the element, type a descriptive name for the data source. Note: Typing a value in the element is required.
3
In the element, type relevant details related to the data source. In the element, provide the connection string for the data source using the syntax Data Source=DataSourceName where DataSourceName is the name of the DSN that you typed in step 6 of the procedure in “To create a new ODBC Driver for Teradata Data Source Name (DSN):” on page 16. For example: Data Source=Teradata_DSN
Teradata OLAP Server User Guide, Release 14.10
21
Chapter 1: Teradata OLAP Server Windows Administration Confirm Teradata OLAP Server Deployment 4
In the element, type the URL to the Teradata OLAP Server virtual folder to indicate to JBoss how to access the service’s deployed files. For example, if your JBoss installation uses the default port and you bind JBoss to the default IP address 127.0.0.1: http://localhost:8080/XmlaWebService/
Note: See “Start JBoss” on page 19 for more information on binding JBoss to an IP address. 5
Save and close the DataSources.xml file.
Configure JVM Memory Usage Table 1 lists parameters to set for allocating JVM memory for JBoss. Table 1: JVM Memory Allocation Parameters to Set
Parameter
Description
-Xms64M
Set the minimum memory requirement for heap space to 64MB.
-Xmx4096M
Set the maximum heap size to 4 GB.
-XX:MaxPermSize=512M
Set the maximum permanent generation memory to 512 MB.
-Xss256k
Set the maximum stack frame size to 256 KB.
To set JVM memory use: 1
In a text editor, open the file JBOSS_HOME\bin\standalone.conf.bat.
2
As needed, update the line of code defining memory usage via the JAVA_OPTS variable. For example: set "JAVA_OPTS=-Xms4096M -XX:MaxPermSize=512M -Xss256k"
3
Save and close the standalone.conf.bat file.
Confirm Teradata OLAP Server Deployment To confirm that the Teradata OLAP Server runs: 1
Restart JBoss. Note: After deploying Teradata OLAP Server, JBoss renames the file XmlaWebService.war.dodeploy to XmlaWebService.war.deployed.
2
22
In your Web browser, append the text XmlaWebService/ to the URL that you typed in step 3 in the procedure in “Test JBoss” on page 20, and then press Enter. For example, if the
Teradata OLAP Server User Guide, Release 14.10
Chapter 1: Teradata OLAP Server Windows Administration Alternative Teradata OLAP Server Deployment Naming
Web server uses the default port and you bound the Web server to the IP address 127.0.0.1, then type http://localhost:8080/XmlaWebService/ Note: The slash (/) at the end of the URL you typed in step 2 is required. If JBoss successfully deployed the Teradata OLAP Server, then the browser displays the Start page listing Discover and Execute methods under the heading XmlaWebService. Note: During testing, you can start and stop Teradata OLAP Server by starting and stopping your Web server using the Windows command line. In a production system, administering your Web server using the tools that the Web server provides allows you to administer Teradata OLAP Server without stopping the Web server.
Alternative Teradata OLAP Server Deployment Naming How you name the deployment folder in the %JBOSS_HOME%\standalone \deployments\webapps directory will impact the name of the Teradata OLAP Server instance when deployed to JBoss. Up to this point, we have utilized the folder name XmlaWebService.war. However, you can provide a name for the web service that is more meaningful for your environment by altering the name of the deployment folder. For example, if you copy the distribution WAR file contents to a folder with name ProductionDB.war in the deployments directory, JBoss will start a web service with endpoint name ProductionDB. This web service will be accessible at URL http:///ProductionDB. Make sure that the dodeploy file name matches whatever folder name you choose. In the example provided above, the dodeploy file name would be ProductionDB.war.dodeploy.
Deploying Multiple Teradata OLAP Server Instances It is possible to deploy multiple instances of the Teradata OLAP Server in a single instance of JBoss. Deploying multiple Teradata OLAP Server instances enables you to associate each instance with a separate ODBC DSN to provide access to multiple database machines or a single database machine with differing user credentials. To deploy multiple instances, follow the instructions described in “Alternative Teradata OLAP Server Deployment Naming” on page 23 to ensure each deployed instance has a unique name. Make sure to edit the DataSources.xml configuration of each instance as described in “Configure the Data Source” on page 21.
Teradata OLAP Server User Guide, Release 14.10
23
Chapter 1: Teradata OLAP Server Windows Administration Display the Version Number of Teradata OLAP Server
Display the Version Number of Teradata OLAP Server To display the version number of the Teradata OLAP Server you have installed: 1
In your Web browser, type the URL for the Start page of your Teradata OLAP Server, then append the text serviceversion.jsp, and then press Enter.
The Web browser displays version number of the installed Teradata OLAP Server.
Upgrade an Existing Teradata OLAP Server Installation To upgrade from a previous version of Teradata OLAP Server to the latest version: 1
Stop JBoss Application Server. Note: For details on stopping your Web server, see “Stop JBoss” on page 20.
2
In the \webapps folder where you installed Teradata OLAP Server, move to another folder or delete any of the following files or folders that exist: •
XmlaWebService.war
•
XmlaWebService.war.deployed
3
Follow the procedure in “Install the Teradata OLAP Server” on page 20 to install the latest version of the Teradata OLAP Server.
4
Edit the DataSources.xml file using the procedure in “Configure the Data Source” on page 21.
5
Start JBoss.
Uninstall the Teradata OLAP Server To uninstall Teradata OLAP Server:
24
1
If no Web services are running other than the XMLA Service, then you can stop your Web server. See “Stop JBoss” on page 20 for details.
2
Remove the DSN that you created in the section “Create a Data Source Name” on page 16: a
In Windows, click the Start menu, and then click Control Panel.
b
If you view the Control Panel by Category, then click System and Security.
c
Click Administrative Tools, and then double-click Data Sources (ODBC).
Teradata OLAP Server User Guide, Release 14.10
Chapter 1: Teradata OLAP Server Windows Administration Uninstall the Teradata OLAP Server
3
d
In the ODBC Data Source Administrator dialog, click the System DSN tab, then select the DSN that you created for the Teradata OLAP Server to connect to the database, and then click Remove.
e
In the confirmation dialog, click Yes.
Delete the XmlaWebService.war folder and the XmlaWebService.war.deployed file from the folder JBOSS_HOME\standalone\deployments\webapps\.
Teradata OLAP Server User Guide, Release 14.10
25
Chapter 1: Teradata OLAP Server Windows Administration Uninstall the Teradata OLAP Server
26
Teradata OLAP Server User Guide, Release 14.10
CHAPTER 2
Teradata OLAP Server
This document describes how to use the Teradata OLAP Server with the following analysis tools: •
SAP BusinessObjects Analysis, edition for OLAP 4.1 SP1 and later
•
SimbaO2X
SAP BusinessObjects Analysis, edition for OLAP This section explains how to use SAP BusinessObjects Analysis, edition for OLAP with the Teradata OLAP Server. Note: Prior to using the Teradata OLAP Server, you must follow the installation instructions in Chapter 1: “Teradata OLAP Server Windows Administration.”
Create a New OLAP Data Source Connection To create a new OLAP data source connection to the Teradata OLAP Server: 1
Open BusinessObjects Enterprise Central Management Console (BOE CMC) in your Web browser. For example, the URL may be http://IPAddress:PortNumber/boe/cmc/ where IPAddress is the IP address of the Web application server hosting Central Management Console and PortNumber is the port number on which the Web application server is listening.
2
Log on to Central Management Console.
3
In the Organize area of the Central Management Console, click OLAP Connections.
4
Click the New Connection (
5
In the Name field, type a name for your connection. For example, you may type My Teradata OLAP Server.
6
In the Provider list, click Teradata.
7
In the Server Information field, type the URL of the Teradata OLAP Server. For example, the URL may be http://IPAddress:PortNumber/XmlaWebService/ where IPAddress is the IP address of the Web application server hosting Teradata OLAP Server and PortNumber is the port number on which the Web application server is listening.
) button.
Note: The slash (/) at the end of the URL is required.
Teradata OLAP Server User Guide, Release 14.10
27
Chapter 2: Teradata OLAP Server SAP BusinessObjects Analysis, edition for OLAP 8
Click Connect to connect to the server to choose a cube.
9
In the Log On to the Data Source dialog, type your user name and password for accessing the data source, and then click OK. Note: If you receive the error message "Failed to get connections for connection…" then your JBoss server may not be configured to accept connections from remote servers. See the Chapter 1: “Teradata OLAP Server Windows Administration”for more details. If you receive the error message "Failed to browse connections using resource [{0}]: a RuntimeException occurred…" then verify that you typed the correct user name and password for accessing the data source.
10 In the Cube Browser dialog, select the desired cube, and then click Select. 11 Click the drop-down arrow next to the Authentication field, and then select Prompt. 12 Click Save.
Your connection appears in the list of OLAP connections. For detailed instructions on how to create OLAP data source connections, see the SAP BusinessObjects Analysis, edition for OLAP Administrator Guide at http://help.sap.com/ businessobject/product_guides/boexir4/en/xi4_aa_admin_en.pdf
Connect to a Teradata OLAP Server Data Source A data source is a repository object that is created by your system administrator. It contains the information that is required for SAP BusinessObjects Analysis, edition for OLAP to connect to an OLAP server. These instructions assume that your administrator has created a data source object for the Teradata OLAP Server OLAP data provider. When this is done, then you will have this data source available to add to your workspace.
To add a data source to your workspace: 1
Open BI launch pad in your Web browser. For example, the URL may be http:// IPAddress:PortNumber/boe/bi/ where IPAddress is the IP address of the Web application server hosting BI Launch Pad and PortNumber is the port number on which the Web application server is listening.
2
Log into BI launch pad.
3
In the toolbar, click the Applications menu, and then click Analysis edition for OLAP.
4
In the Open Data Source dialog, select the connection to use, and then click OK.
5
If the Logon window appears, type your credentials for accessing the database that the connection you selected in step 4 accesses in the User name and Password fields, and then click OK. Note: If authentication fails, you may have typed your login credentials incorrectly, or your credentials may not be configured correctly in the Central Management Console. The Teradata OLAP Server may also be offline.
28
Teradata OLAP Server User Guide, Release 14.10
Chapter 2: Teradata OLAP Server SimbaO2X
The name of the data source appears in the Data panel. Below the name of the data source, the data objects contained in the data source appear in the Metadata Explorer. If the Web page does not display correctly, then use a different Web browser. For detailed instructions on how to connect to data sources using Analysis, refer to the SAP BusinessObjects Analysis, edition for OLAP User Guide at http://help.sap.com/businessobject/ product_guides/boexir4/en/xi4sp2_aa_user_en.pdf.
SimbaO2X This section explains how to use SimbaO2X with the Teradata OLAP Server. SimbaO2X is a standards-based ODBO to XMLA client-side driver allowing ODBO applications to work in a web services environment. For more information and documentation about SimbaO2X, refer to http://www.simba.com/connectors/simbao2x. Note: Prior to using the Teradata OLAP Server, you must follow the installation instructions in Chapter 1: “Teradata OLAP Server Windows Administration.”
To connect to Teradata OLAP Server from Microsoft Excel using SimbaO2X: 1
Install SimbaO2X. Note: The bitness of the version that you install must match the bitness of the version of Excel that you are using. For example, if you are using 32-bit Excel, then you should install SimbaO2X_x86_VersionNumber.exe where VersionNumber is the version number of Simba O2X.
2
In Excel, click the Data tab, then click From Other Sources, and then click From Data Connection Wizard.
3
In the Data Connection Wizard, select Other/Advanced, and then click Next.
4
In the Data Link Properties dialog, scroll down as needed to select Simba O2X Provider, and then click Next.
5
In the XMLA Connection URL field, type the URL for the Teradata OLAP Server. For example, the URL may be http://IPAddress:PortNumber/XMLAWebService/ where IPAddress is the IP address of the Web server hosting Teradata OLAP Server and PortNumber is the port on which the Web server is listening. Note: The slash (/) at the end of the URL is required.
6
Type your credentials for accessing the BI repository in the Username and Password fields.
7
Select the Allow Saving Password check box.
8
Click the Test Connection button. If the test is successful, then a dialog appears informing you that you have successfully connected to your server. Click OK.
9
In the Data Link Properties dialog, click OK.
10 In the Data Connection Wizard, click the drop-down arrow next to the Select the
Database That Contains the Data You Want field, and then select the desired database.
Teradata OLAP Server User Guide, Release 14.10
29
Chapter 2: Teradata OLAP Server SimbaO2X 11 Select the Connect to a Specific Cube check box. 12 Select a cube, and then click Next. 13 In the Save Data Connection File and Finish dialog, type a descriptive name for the Office
Data Connection (ODC) file to store the data source information in the File Name field. 14 [Optional] Select the Save Password in File check box. 15 [Optional] Select the Always Attempt to Use This File to Refresh Data check box. 16 Click Finish.
When the Import Data dialog appears, Excel is connected to the BI repository. Note: If an authorization error occurs, ensure that you selected the Allow Saving Password and Save Password in File check boxes. If any other errors occur, see the Appendix B: “Troubleshooting” for troubleshooting information.
30
Teradata OLAP Server User Guide, Release 14.10
APPENDIX A
Teradata OLAP Server Installation Checklist
To install and configure Teradata OLAP Server, ensure that the following tasks are complete: 1.
All software you install meets “Software Requirements” on page 14.
2.
Software related to the ODBC Driver for Teradata is installed, and installed in the following order: 1 Shared ICU Libraries for Teradata 2 Teradata GSS Client 3 ODBC Driver for Teradata
3.
The DSN you created successfully connects to your Teradata Database.
4.
The Java SE Development Kit (JDK) is installed.
5.
JAVA_HOME and JBOSS_HOME system environment variables are correctly set.
6.
The JBoss Application Server starts and stops successfully.
7.
All computers requiring access to the Teradata OLAP Server can access your JBoss installation using a Web browser.
8.
The JBOSS_HOME\standalone\deployments\webapps folder contains: • A folder—not an archive—named XmlaWebService.war • A file named XmlaWebService.war.dodeploy or XmlaWebService.war.deployed
9.
The DataSources.xml file correctly specifies the following elements: • • • •
10.
JVM memory is allocated suitably considering the hardware specifications of the computer hosting JBoss Application Server.
11.
Your Web browser successfully displays the Start page for the Teradata OLAP Server listing Discover and Execute methods under the heading XmlaWebService.
12.
The Start page for the Teradata OLAP Server that your Web browser displays is not being retrieved from the browser cache.
13.
You can successfully connect to your Teradata OLAP Server using a Business Intelligence (BI) client application.
Teradata OLAP Server User Guide, Release 14.10
31
Appendix A: Teradata OLAP Server Installation Checklist
32
Teradata OLAP Server User Guide, Release 14.10
APPENDIX B
Troubleshooting
To resolve issues during the installation of Teradata OLAP Server, refer to the troubleshooting guidelines below. Creating log files as described in “Using Logging to Troubleshoot MDX and SQL Issues” on page 34 and monitoring the XMLA data stream as explained in “Capturing XMLA Interaction” on page 35 can help Technical Support assist in resolving issues. For technical support, contact Teradata.
Web Server Does Not Start Confirm that the JAVA_HOME and JBOSS_HOME system environment variables are set to the correct installation locations as described in the section “Configure Environment Variables” on page 18.
Browsing to the XMLA Service Start Page Displays an Error If attempting to open the XMLA Service Start page in your Web browser displays an error page, then troubleshoot as follows: 1
In your Web browser Address field, confirm that the URL to access the XMLA Service Start page ends with a slash mark (/).
2
Confirm that all software listed in the section “Software Requirements” on page 14 is installed on the computer where you want to install Teradata OLAP Server.
3
Confirm that the ODBC DSN that you configured in the DataSources.xml file exists in the 64-bit ODBC Administrator. See “Create a Data Source Name” on page 16 and “Configure the Data Source” on page 21 for more details.
4
Confirm that your Web server is bound to an appropriate IP address so that remote hosts can access the server. See “Start JBoss” on page 19 for more details.
Teradata OLAP Server User Guide, Release 14.10
33
Appendix B: Troubleshooting Using Logging to Troubleshoot MDX and SQL Issues
Using Logging to Troubleshoot MDX and SQL Issues When connecting to or analyzing an external OLAP source, error messages may not contain enough information to troubleshoot problems. To help troubleshoot issues, you may need to turn on logging for the Teradata OLAP Server. When logging is enabled, repeat the steps that cause the error. Note: Only turn on logging long enough to capture a problem. Logging slows down the Teradata OLAP Server and can consume a large quantity of disk space.
Turning On Logging To turn on logging: 1
Ensure that the BI client application that you are troubleshooting is not running.
2
Ensure that the Teradata OLAP Server is not running.
3
In the installation location for Teradata OLAP Server, browse to the \scripts subfolder, and then double-click the registry file named Native OLAP Server Trace Settings ON.reg.
4
Restart the Teradata OLAP Server.
5
Restart the client program.
The log files are saved using names like TeradataOLAPServer..log and are automatically split into 5 MB files, so there may be a number of consecutive log files. Note: The Native OLAP Server Trace Settings ON.reg file contains the path to the log file, which, by default, is set to C:\logs. To change the path, in the .REG file update the line that begins with “Path”=. The path you enter will include backslashes. Backslashes are special characters that must be escaped with a second backslash. For example: "Path"="C:\\Users\\jsmith"
Turning Off Logging To turn off logging:
34
1
Ensure that the BI client application that you are troubleshooting is not running.
2
Ensure that the Teradata OLAP Server is not running.
3
In the installation location for Teradata OLAP Server, browse to the \scripts subfolder, and then double-click the registry file named Native OLAP Server Trace Settings OFF.reg.
4
Restart the Teradata OLAP Server.
Teradata OLAP Server User Guide, Release 14.10
Appendix B: Troubleshooting Capturing XMLA Interaction 5
Restart the client program.
Capturing XMLA Interaction Fiddler is a Web debugging proxy that logs all HTTP(S) traffic between your computer and the Internet. You can configure Fiddler to capture the XMLA data stream between a client, such as Microsoft Excel, and Teradata OLAP Server. For details, see the document How to Capture XMLA Interaction Using Fiddler located at: http://www.simba.com/wp-content/ uploads/2013/05/HOW-TO12060713-CaptureXMLAInteractionUsingFiddler.pdf.
Teradata OLAP Server User Guide, Release 14.10
35
Appendix B: Troubleshooting Capturing XMLA Interaction
36
Teradata OLAP Server User Guide, Release 14.10
Index
A
T
alternative deployment naming 23
Teradata GSS Client installing 15 Teradata OLAP Server alternative deployment naming 23 architecture 13 configuring 21 configuring JVM memory usage 22 configuring the Data Source Name 21 confirming deployment 22 deploying multiple instances 23 displaying version number 24 installation checklist 31 installation troubleshooting 33 installing 20 uninstalling 24 upgrading 24 troubleshooting Teradata OLAP Server installation 33
D Data Source Name creating 16
E Environment Variables configuring 18 JAVA_HOME 18 JBOSS_HOME 19
J Java SE Development Kit installing 17 JBoss Application Server downloading and installing 18 starting 19 stopping 20 testing 20
O ODBC Driver installing 15, 16 OLAP Server software requirements 14
R Release Definition 4
S SAP BusinessObjects Analysis edition for OLAP 27 OLAP data source connection, connecting 28 OLAP data source connection, creating 27 Shared ICU Libraries for Teradata installing 15 SimbaO2X using with Microsoft Excel 29 software releases supported 3
Teradata OLAP Server User Guide, Release 14.10
37
Index
38
Teradata OLAP Server User Guide, Release 14.10
