KB38169: Requirements for Microstrategy Intelligence Server 9.x-10.x to access a Hyperion Essbase 11 system.

 
The following requirements must be met in order for Strategy Intelligence Server 9.x - 10.x to be able to connect to Hyperion Essbase 11.

1. A Hyperion Essbase 11 system. (Make sure your Essbase version is listed in "StrategySystem Requirements for Common Certified/Supported Configurations" of your Strategy version. Check README to confirm this first)
2. XML for Analysis (XMLA) connectivity to the Hyperion Essbase system.
    
   
• The Hyperion XMLA Provider must be installed and configured on a compatible web application server. The Hyperion XMLA provider is part of Hyperion Provider Services. Hyperion is now an Oracle subsidiary; contact Oracle to obtain Hyperion Provider Services and configuration instructions.
• Hyperion Enterprise Deployment Services 11 should be installed on the application server machine to verify that access is available to the Essbase server via the Service Console.
• Normally, the Hyperion XMLA Provider 11 uses standard authentication by user ID and password to authenticate into the XMLA Provider web service. If anonymous authentication is preferred, the XMLA Provider should be configured to accept it.
• One or more Essbase user logins must be properly mapped to Enterprise Deployment Services user logins.
3. Obtain the Essbase connectivity details:
    
   
• User name and password
• IP Address or fully qualified name of the Essbase XMLA Provider host. The fully qualified name may be case sensitive.
• XMLA provider URL, for example: http://fully_qualified_name:13080/aps/XMLA. Note that the port number may be different, depending on the configuration of the web application server.
• Data Source Information should be in the form: Provider=Essbase;Data source=<machine name> -- note that the fully qualified name should not be used here.
• Catalog should be the name of the Essbase Application that contains the cubes (Databases in Hyperion terminology) to be accessed by Strategy.
4. Create a Strategy database instance, database connection and database login using the above information. Ensure that the database type for the database instance is "Hyperion Essbase." Note also that Windows NT authentication is not supported by the Hyperion XMLA provider.
    
   One database instance must be configured per Essbase Application. Essbase Applications will be mapped into Strategy catalogs, and Essbase Databases into Strategy cubes.
   

 
KB38169