28.01.2013 Views

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

particular source over the Internet, without the client having to set up a special component. XML for Analysis is<br />

optimized for the Internet in the following ways:<br />

● Query performance<br />

Time spent on queries to the server is kept to a minimum<br />

● Query type<br />

Client queries are stateless by default; after the client has received the requested data, the client is<br />

disconnected from the Web server.<br />

In this way, tolerance to errors and the scalability of a source (the maximum permitted number of users) is<br />

maximized.<br />

XMLA Methods<br />

The specification defined in XML for Analysis Version 1.1 from Microsoft forms the basis for the implementation of<br />

XML for Analysis in <strong>SAP</strong> <strong>HANA</strong>.<br />

The following list describes the methods that determine the specification for a stateless data request and<br />

provides a brief explanation of the method's scope:<br />

● Discover<br />

Use this method to query metadata and master data; the result of the discover method is a rowset. You can<br />

specify options, for example, to define the query type, any data-filtering restrictions, and any required XMLA<br />

properties for data formatting.<br />

● Execute<br />

Use this method to execute MDX commands and receive the corresponding result set; the result of the<br />

Execute command could be a mult-idimensional dataset or a tabular rowset. You can set options to specify<br />

any required XMLA properties, for example, to define the format of the returned result set or any local<br />

properties to use to determine how to format the returned data.<br />

8.2.2 XMLA Service Definition<br />

The XMLA service definition is a file you use to specify which data is exposed as XMLA collections. Exposed data is<br />

available for analysis and display by client applications, for example, a browser that uses functions provided either<br />

by the XMLA service running in <strong>SAP</strong> <strong>HANA</strong> XS or by an XMLA client library running on the client system.<br />

To expose information via XMLA to applications using <strong>SAP</strong> <strong>HANA</strong> Extended Application Services (<strong>SAP</strong> <strong>HANA</strong> XS),<br />

you define database views that provide the data with the required granularity and you use the XMLA service<br />

definition to control access to the exposed data.<br />

Note: <strong>SAP</strong> <strong>HANA</strong> XS supports XMLA version 1.1, which you can use to send MDX queries.<br />

An XMLA service for <strong>SAP</strong> <strong>HANA</strong> XS is defined in a text file with the file suffix .xsxmla, for example,<br />

XMLASrvDef.xsxmla. The file must contain only the entry {*}, which would generate a completely<br />

operational XMLA service.<br />

202<br />

P U B L I C<br />

© 2012 <strong>SAP</strong> AG. All rights reserved.<br />

<strong>SAP</strong> <strong>HANA</strong> <strong>Developer</strong> <strong>Guide</strong><br />

Defining Web-based Data Access

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!