EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB14715: How to use the XMLA Connectivity Test Tool available in MicroStrategy 9.x


Community Admin

• Strategy


MicroStrategy 9.x ships a commandline tool to confirm connectivity from a MicroStrategy Intelligence Server or client machine to an XMLA data source. The utility is called XMLATest.exe and is located in C:\Program Files\Common Files\MicroStrategy. It may be launched in the Windows file explorer or from the commandline. In UNIX environments, the utility is launched using the command mstrxmlatest from the directory /bin.

Strategy 9.x ships a commandline tool to confirm connectivity from a Strategy Intelligence Server or client machine to an XMLA data source. The utility is called XMLATest.exe and is located in C:\Program Files\Common Files\Strategy. It may be launched in the Windows file explorer or from the commandline. In UNIX environments, the utility is launched using the command mstrxmlatest from the directory /bin.
 
When run, the tool presents a number of prompts for XMLA connectivity details: 

  • URL to the XMLA provider
  • Database user ID and password (optional)
  • Data source information (optional, as it would be entered into an XMLA database connection object in Strategy)
  • Catalog name (optional, as in the XMLA database connection in Strategy)

After the responses are collected, the XMLA Test tool will issue an XMLA Discover call and report the results in the console. Success can be seen with a row set listing data sources available in the catalog. Error messages indicate incorrect connectivity details, or possibly misconfiguration on the database server or XMLA provider.
 
User name, data source information and catalog need not be specified. Answers in these fields affect the type of query that is issued against the XMLA provider.
 

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

January
B234JanuaryC2345MonthLetterMetricFebruaryA823FebruaryB234FebruaryC2345FieldIf emptyIf providedUser IDAnonymous authentication is usedPassword is requested; this user ID and password are used to authenticateData source informationDISCOVER_DATASOURCES query is issued; result should list the available data sources for the XMLA providerCatalog name is requestedCatalogDBSCHEMA_CATALOGS query is issued; result should list the available catalogs in the given data sourceMDSCHEMA_CUBES query is issued; result should list the available cubes in the given catalog

An example of a successful transcript against Microsoft Analysis Services follows. User responses are italicized.
 
Welcome to XMLATest.
Please type the target URL, starting with http:
http://sql-server-2005.----.----------.com/xmla/msmdpump.dll
Please type the UID to login to that URL. If no UID needed, just press <ENTER> key:
Please type the name of the DataSource on XMLA source. If unknown, just press <ENTER> key:
SQL-SERVER-2005
Please type the name of the Catalog on XMLA source. If unknown, just press <ENTER> key:
Get SOAP reply:
================================
<row><CATALOG_NAME>Adventure Works DW</CATALOG_NAME><DESCRIPTION>A Unified Dimensional Model that encompasses the Adventure Works data warehouse.</DESCRIPTION><ROLES>*</ROLES><DATE_MODIFIED>2006-04-18T14:49:31</DATE_MODIFIED></row><row><CATALOG_NAME>Calumo Sample Data</CATALOG_NAME><DESCRIPTION/><DATE_MODIFIED>2006-08-09T14:50:45</DATE_MODIFIED></row><row><CATALOG_NAME>EA Works DW</CATALOG_NAME><DESCRIPTION>A Unified Dimensional Model that encompasses the EA Works data warehouse.</DESCRIPTION><DATE_MODIFIED>2006-04-18T16:01:53</DATE_MODIFIED></row><row><CATALOG_NAME>EA01 Works DW</CATALOG_NAME><DESCRIPTION>A Unified Dimensional Model that encompasses the EA01 Works data warehouse.</DESCRIPTION><DATE_MODIFIED>2006-04-21T20:33:29</DATE_MODIFIED></row><row><CATALOG_NAME>Labs Works DW</CATALOG_NAME><DESCRIPTION>A Unified Dimensional Model that encompasses the Labs Works data warehouse.</DESCRIPTION><DATE_MODIFIED>2005-12-09T21:58:20</DATE_MODIFIED></row><row><CATALOG_NAME>XDA Works DW</CATALOG_NAME><DESCRIPTION>A Unified Dimensional Model that encompasses the XDA Works data warehouse.</DESCRIPTION><DATE_MODIFIED>2006-03-16T19:57:48</DATE_MODIFIED></row><row> <CATALOG_NAME>XDA_Dev</CATALOG_NAME><DESCRIPTION/><DATE_MODIFIED>2006-05-03T22:11:40 </DATE_MODIFIED></row><row><CATALOG_NAME>XDA_Dev_COPY</CATALOG_NAME> <DESCRIPTION/><DATE_MODIFIED>2006-07-05T19:04:59</DATE_MODIFIED></row> </root></return></DiscoverResponse></soap:Body></soap:Envelope> ================================
End of XMLATest run. Press <ENTER> to quit.
An unsuccessful run will end with an error, of which the following is one possible example:
 
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault xmlns="http://schemas.xmlsoap.org/soap/envelope/"> <faultcode>XMLAnalysisError.0xc1180001</faultcode><faultstring>Either the user, SQL-SERVER-2005\XMLAUser, does not have access to the Adventure Works database, or the database does not exist.</faultstring><detail><Error ErrorCode="3239575553" Description="Either the user, SQL-SERVER-2005\XMLAUser, does not have access to the AdventureWorks database, or the database does not exist." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile=""/></detail></soap:Fault></soap:Body></soap:Envelope>
In this case, an incorrect value was entered for the catalog name.
 
Notes:

  • This utility is intended only to verify connectivity. It is not a way to log in and execute MDX queries.
  • Because it does not activate Strategy components to parse the XMLA return value and construct a report display, it is ideal to identify connectivity issues that are independent of the Strategy architecture. That is, if an error occurs in Strategy Desktop and also occurs in the XMLA Test tool, then the error must involve the connectivity details and the issue must be resolved outside of Strategy Desktop.
  • Strategy uses an entirely different component, JCO, to connect to SAP BW. JCO is supplied by SAP and not installed with Strategy. XMLATest.exe is not able to use the JCO layer and cannot be used to test SAP BW connectivity. Consult the following Strategy Knowledgebase article for details on the HelloSAP utility, which may be used to test basic connectivity to SAP systems.

KB18482 - How to use the HelloSAP utility to verify connectivity to SAP systems in Strategy Intelligence Server 8.1.x and 9.x
 


Comment

0 comments

Details

Knowledge Article

Published:

April 16, 2017

Last Updated:

May 5, 2017