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.

XMLA Service-Definition Keywords<br />

Currently, the XMLA service-definition file enables you to specify only that all authorized data is exposed to XMLA<br />

requests, as illustrated in the following example:<br />

Service {*}<br />

8.2.3 XMLA Security Considerations<br />

Enabling access to data by means of XMLA opens up some security considerations that you need to address, for<br />

example, the data you want to expose, who can start the XMLA service, and so on.<br />

If you want to use XMLA to expose data to users and clients in <strong>SAP</strong> <strong>HANA</strong> XS, you need to bear in mind the<br />

security considerations described in the following list:<br />

● Data Access<br />

●<br />

Restrict user select authorization for data exposed by the XMLA service<br />

● XMLA Statistical content<br />

Restrict access to the URL/Path used to expose XMLA content in the Web browser, for example, using the<br />

application-access file (.xsaccess)<br />

8.2.4 Multidimensional Expressions (MDX)<br />

Multidimensional Expressions (MDX) is a language you can use to query multidimensional data stored in OLAP<br />

cubes.<br />

MDX uses a multidimensional data model to enable navigation in multiple dimensions, levels, and up and down a<br />

hierarchy. With MDX, you can access pre-computed aggregates at specified positions (levels or members) in a<br />

hierarchy.<br />

Note: MDX is an open standard. However, <strong>SAP</strong> has developed extensions to MDX that are designed to<br />

enable faster and more efficient access to multidimensional data, for example, to serve specific <strong>SAP</strong><br />

<strong>HANA</strong> application requirements and to optimize the resultset for <strong>SAP</strong> <strong>HANA</strong> clients.<br />

MDX is implicitly a hierarchy-based paradigm. All members of all dimensions must belong to a hierarchy. Even if<br />

you do not explicitly create hierarchies in your <strong>SAP</strong> <strong>HANA</strong> data model, the <strong>SAP</strong> <strong>HANA</strong> modeler implicitly<br />

generates default hierarchies for each dimension. All identifiers that are used to uniquely identify hierarchies,<br />

levels and members in MDX statements (and metadata requests) embed the hierarchy name within the identifier.<br />

In <strong>SAP</strong> <strong>HANA</strong>, the standard use of MDX is to access <strong>SAP</strong> <strong>HANA</strong> models (for example, analytical and attribute<br />

views) that have been designed, validated and activated in the modeler in the <strong>SAP</strong> <strong>HANA</strong> studio. The studio<br />

provides a graphical design environment that enables detailed control over all aspects of the model and its<br />

language-context-sensitive runtime representation to users.<br />

MDX in <strong>SAP</strong> <strong>HANA</strong> uses a runtime cube model, which usually consists of an analytical (or calculation) view that<br />

represents data in which dimensions are modeled as attribute views. You can use the analytical view to specify<br />

whether a given attribute is intended for display purposes only or for aggregation. The key attributes of attribute<br />

views are linked to private attributes in an analytical view in order to connect the entities. One benefit of MDX in<br />

<strong>SAP</strong> <strong>HANA</strong> is the native support of hierarchies defined for attribute views.<br />

Note: MDX in <strong>SAP</strong> <strong>HANA</strong> includes native support of hierarchies defined for attribute views. <strong>SAP</strong> <strong>HANA</strong><br />

supports level-based and parent-child hierarchies and both types of hierarchies are accessible with MDX.<br />

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

Defining Web-based Data Access<br />

P U B L I C<br />

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

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

Saved successfully!

Ooh no, something went wrong!