Managing data source connections » Creating a data source connection to an OLAP source (MDX cube source)

Creating a data source connection to an OLAP source (MDX cube source)

When you import data from an MDX cube source, you must establish communication between MicroStrategy and your data source. To establish communication, you create an MDX connection, which enables MicroStrategy Web to retrieve data from your data source.

MDX cube sources include Microsoft Analysis Services, Cognos TM1, SAP BW, and Essbase.

Prerequisites

If you are using Microsoft Analysis Services, install the Microsoft Analysis Services OLEDB Provider on the machine where you installed MicroStrategy products and the MicroStrategy MDX Cube Provider. The version that you install depends on your operating system’s architecture:
If you install on a 32-bit operating system, install the 32-bit Microsoft Analysis Services OLEDB Provider.
If you install on a 64-bit operating system, install the 64-bit Microsoft Analysis Services OLEDB Provider.

For information on how to install the Microsoft Analysis Services OLEDB Provider, refer to your third-party Microsoft Analysis Services documentation.

If you are using Cognos TM1, install the TM1 OLEDB Provider on the machine where you installed MicroStrategy products and the MicroStrategy MDX Cube Provider. The version that you install depends on your operating system’s architecture:
If you install on a 32-bit operating system, install the 32-bit TM1 OLEDB Provider.
If you install on a 64-bit operating system, install the 64-bit TM1 OLEDB Provider.

For information on how to install the TM1 OLEDB Provider, refer to your third-party TM1 documentation.

If you are using SAP BW, install the 3.x SAP Java Connector files. For information on where to install these files, refer to the MDX Cube Reporting Guide. You need a valid login for the SAP Service Marketplace to download the SAP Java Connector files. The version that you install depends on your operating system’s architecture:
If you install on a 32-bit operating system, you must download and install the 32-bit version of the 3.x Java Connector.
If you install on a 64-bit operating system, you must download and install the 64-bit version of the 3.x Java Connector.
If you are using Essbase:
Install the Essbase client, including the Essbase C API, on the machine where you installed MicroStrategy products and the MicroStrategy MDX Cube Provider. The version that you install depends on your operating system’s architecture:
If you install on a 32-bit operating system, install the 32-bit Essbase client.
If you install on a 64-bit operating system, install the 64-bit Essbase client.
For information on how to install the Essbase client libraries, refer to your third-party Oracle documentation.
Install Oracle Essbase Provider Services on the application server machine to verify that access is available to the Oracle Essbase server via the service console. For information on installation procedures, refer to your third-party documentation (http://www.oracle.com/technology/products/bi/).

To create a new database connection to an MDX cube source

1 On any page, click Create on the icon bar on the left, and then select Access External Data. The Connect to Your Data page opens.
2 Click OLAP. The Import From Cubes Options dialog box opens.
3 On the MDX Connections panel, click Add. The Data Source dialog box opens.
4 From the Database drop-down list, select the type of database to connect to, such as SAP or Microsoft Analysis Services.
5 From the Version drop-down list, select the version of the database to connect to.
6 If you are using Microsoft Analysis Services, complete the following steps:
a In the Uniform Resource Locator, type the URL of the XMLA Provider that was configured for HTTP access. For example: http://fully-qualified-machinename/MicroStrategyMDX/MicroStrategyMDX.asmx.

The fully-qualified-machinename is usually of the form machine.domain.company.com. You can also use the IP address as the fully-qualified-machinename. The URL is not case sensitive.

b In the Data Source Information field, type the fully qualified machine name or the IP address of the machine where the Microsoft Analysis Services server is running.
c In the Catalog field, use Microsoft’s SQL Server Management Studio to view the Analysis Server which contains the cubes to work with in MicroStrategy. The database that contains the cube becomes the catalog.
7 If you are using Cognos TM1, complete the following steps:
a In the Uniform Resource Locator, type the URL of the MicroStrategy MDX Cube Provider that was configured for HTTP Access. This connector is installed as part of a MicroStrategy installation to support connections to TM1. The default URL is in the following format:

http://fully-qualified-machinename/MicroStrategyMDX/MicroStrategyMDX.asmx

The fully-qualified-machinename is usually of the form machine.domain.company.com. You can also use the IP address as the fully-qualified-machinename.

b In the Data Source Information field, type the fully qualified machine name of the machine where the TM1 Admin Server is running.
c The Catalog represents the name of the TM1 server configuration, which is defined in the TM1S.cfg file. For more information, see your third-party TM1 documentation.
8 If you are using Essbase, complete the following steps:
a In the Uniform Resource Locator, type the URL of the provider that was configured for HTTP access. For example: http://fully-qualified-machinename/MicroStrategyMDX/MicroStrategyMDX.asmx.

The fully-qualified-machinename is usually of the form machine.domain.company.com. You can also use the IP address as the fully-qualified-machinename. For Oracle Essbase the URL is usually case sensitive.

b In the Host Name field, type the DataSourceInfo (DSI) value using the following syntax:

Provider=Essbase;Data Source=<machine name>

c In the Catalog field, use the Oracle Essbase application containing the database to connect to with MicroStrategy. Use the Essbase Administration Console to view the applications and databases available on the server.
9 If you are using SAP BW, select the logon method, which determines the type of SAP BW system that you are connecting to:
To connect to a specific SAP BW application server, click Application server and complete the steps below:
a In the Application Server field, type the name or IP address of the SAP BW Server.
b In the SAP Router String field, type the SAP router string, which is only required if you use an SAP Router.
c In the System Number field, type the system number from the SAP BW system.
d In the Client Number field, type the client number from the SAP BW system.
e In the Language field, type the language code provided by your SAP administrator. For example, EN is the language code for English.
To connect to an SAP BW message server, click Message server and complete the following steps. The SAP BW message server acts as a load balancing mechanism for a cluster of SAP BW application servers. Once connected to the SAP BW message server, the SAP BW system can use its load balancing capabilities to connect to an SAP BW application server.
a In the Message Server field, type the name or IP address of the SAP BW Server.
b In the SAP Router String field, type the SAP router string, which is only required if you use an SAP Router.
c In the System ID field, type the system ID from the SAP BW system.
d In the Logon group field, type the SAP BW logon group that determines what SAP BW application servers in the cluster can be accessed.
e In the Client Number field, type the client number from the SAP BW system.
f In the Language field, type the language code provided by your SAP administrator. For example, EN is the language code for English.
10 Provide the User name and Password to use to connect to the database.
11 In the Data Source Name field, type a name for the database connection.
12 Click OK to create the connection.

Once you have created a connection to your data source, you can import data from your data source. For steps, see Importing data from an MDX cube source.

Related topics

Importing data from an MDX cube source
Editing, deleting, renaming, or duplicating a database connection