Skip to content

olap-engine-server-components.md

Latest commit

 

History

History
63 lines (45 loc) · 4.61 KB

olap-engine-server-components.md

File metadata and controls

63 lines (45 loc) · 4.61 KB
title OLAP Engine Server Components | Microsoft Docs
ms.custom
ms.date 03/06/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology analysis-services
ms.topic reference
helpviewer_keywords
Analysis Services, architecture
ports [Analysis Services]
XML/A listener
server architecture [Analysis Services]
ms.assetid 5193c976-9dcd-459c-abba-8c3c44e7a7f2
author minewiskan
ms.author owend
manager craigg

OLAP Engine Server Components

The server component of [!INCLUDEmsCoName] [!INCLUDEssNoVersion] [!INCLUDEssASnoversion] is the msmdsrv.exe application, which runs as a Windows service. This application consists of security components, an XML for Analysis (XMLA) listener component, a query processor component and numerous other internal components that perform the following functions:

  • Parsing statements received from clients

  • Managing metadata

  • Handling transactions

  • Processing calculations

  • Storing dimension and cell data

  • Creating aggregations

  • Scheduling queries

  • Caching objects

  • Managing server resources

Architectural Diagram

An [!INCLUDEssASnoversion] instance runs as a stand-alone service and communication with the service occurs through XML for Analysis (XMLA), by using either HTTP or TCP. AMO is a layer between the user application and the [!INCLUDEssASnoversion] instance. This layer provides access to [!INCLUDEssASnoversion] administrative objects. AMO is a class library that takes commands from a client application and converts those commands into XMLA messages for the [!INCLUDEssASnoversion] instance. AMO presents [!INCLUDEssASnoversion] instance objects as classes to the end user application, with method members that run commands and property members that hold the data for the [!INCLUDEssASnoversion] objects.

The following illustration shows the [!INCLUDEssASnoversion] components architecture, including all major elements running within the [!INCLUDEssASnoversion] instance and all user components that interact with the instance. The illustration also shows that the only way to access the instance is by using the XML for Analysis (XMLA) Listener, either by using HTTP or TCP.

Analysis Services System Architecture Diagram

XMLA Listener

The XMLA listener component handles all XMLA communications between [!INCLUDEssASnoversion] and its clients. The [!INCLUDEssASnoversion] Port configuration setting in the msmdsrv.ini file can be used to specify a port on which an [!INCLUDEssASnoversion] instance listens. A value of 0 in this file indicates that [!INCLUDEssASnoversion] listen on the default port. Unless otherwise specified, [!INCLUDEssASnoversion] uses the following default TCP ports:

Port Description
2383 Default instance of [!INCLUDEssNoVersion] [!INCLUDEssASnoversion].
2382 Redirector for other instances of [!INCLUDEssNoVersion] [!INCLUDEssASnoversion].
Dynamically assigned at server startup Named instance of [!INCLUDEssNoVersion] [!INCLUDEssASnoversion].

See Configure the Windows Firewall to Allow Analysis Services Access for more details.

See Also

Object Naming Rules (Analysis Services) Physical Architecture (Analysis Services - Multidimensional Data) Logical Architecture (Analysis Services - Multidimensional Data)