About the SAP BI XMLA Connector
This document is called howto.html and is delivered
in the resource adapter archive (RAR file) bi_sdk_xmla.rar.
You may extract howto.html to a separate location
for your reference before deploying the resource adapter archive. Refer
to this document for properties configuration information.
This document contains the following information:
Overview
XML for Analysis (XMLA) facilitates Web services-based, platform-independent
access to OLAP providers. The BI XMLA Connector enables the exchange of
analytical data between a client application and a data provider working
over the Web, using a SOAP-based XML communication API. This connector
sends commands to an XMLA-compliant OLAP data source in order to retrieve
the schema rowsets and obtain a result set.
The BI XMLA Connector allows you to connect applications built with the
BI Java SDK to data sources such as Microsoft Analysis Services, Hyperion,
MicroStrategy, MIS, and SAP BW 3.x. This connector is fully compliant
with the J2EE Connector Architecture (JCA).
You can also use the BI XMLA Connector to make these data sources available
in SAP BI systems via UD Connect, or to create systems in the portal.
The BI XMLA Connector implements the BI Java SDK's IBIOlap interface.
System Requirements
Requirement |
Detail |
Software prerequisites |
webservices_lib.jar - SAP J2EE SOAP Library
SAPXMLToolkit.jar - SAP XML Parser
jaxm-api.jar
saaj-api.jar
|
Supported data sources |
XMLA-compliant OLAP data sources, such as SAP BI
(BW) system release 3.0A or greater |
Supported systems |
No restrictions |
Supported application server |
SAP NetWeaver |
Connection Properties
Connection Constant |
Property Name |
Description |
Examples |
XmlaConnectionConstants.
USERNAME |
UserName |
Data source username. |
(your username) |
XmlaConnectionConstants.
PASSWORD |
Password |
Data source password. |
(your password) |
XmlaConnectionConstants.
LANGUAGE
|
Language |
Two-letter abbreviation of language. Determines logon
language for BW systems, and specifies the language of exceptions
evoked on the BI Java SDK layer. Optional. |
EN = English
DE = German |
XmlaConnectionConstants.
URL
(*see note below) |
URL |
Server URL. |
SAP BI (BW) XMLA provider -- http://[domain:port]/sap/
bw/xml/soap/xmla
MS Analysis Server --
http://[domain:port]/
isapi/msxisapi.dll |
XmlaConnectionConstants.
DATASOURCE |
DataSource |
Data source info property. |
Local Analysis Server |
XmlaConnectionConstants.
STATEFULNESS |
Statefulness |
Statefulness support. Optional. Default is
false . |
true or false
Statefulness = true works properly only in the J2EE engine
version SP Stack 12 or greater. |
XmlaConnectionConstants.
LOGONMETHOD |
Logonmethod |
Specifies authentication mechanism (logon method). |
UIDPW - Log on to your XMLA provider using User/Password.
Use this method for XMLA-based access to non-BW providers, or for
User/Password access to BW providers. This is the sole authentication
method supported in the unmanaged environment.
SAPLOGONTICKET - Log on to your XMLA provider using
SAP Logon Ticket (supported by SAP BW XMLA providers). Use this
property if you want to use the SAP Logon Ticket (SSO) to access
BW systems.
|
XmlaConnectionConstants. TIMEOUT |
Timeout |
Maximum time to wait for the SOAP connection (in
milliseconds). Default is 30000 (thirty seconds). |
60000 - to increase timeout to one minute. |
* Note: To find the URL of an SAP BI (BW) XMLA provider:
For a BW system, start transaction SE37 and execute
the function module RSBB_URL_PREFIX_GET .
Use the following values for the import parameters of the function
module:
I_HANDLERCLASS = CL_RSR_MDX_SOAP_HANDLER
I_PROTOCOL = HTTP
I_MESSAGESERVER =
The URL takes the following form: */sap/bw/xml/soap/xmla .
JNDI Name
Refer to this connector in your application by its JNDI name: SDK_XMLA .
For code samples, refer to the Connection Interfaces Javadocs package
in the documentation set delivered with the BI Java SDK.
You may clone an existing connection using the Web Application Server's
Visual Administrator. If you are using this connector with UD Connect,
when entering the resource adapter name during the cloning process, you
must prefix the JNDI name with "SDK_ " and use only all capital
letters in order for UD Connect to properly recognize the connector.
Additional Information
For more information about Sun's J2EE Connector Architecture, see:
For more information about the connection architecture in the BI Java
SDK, refer to the following documentation in the SDK distribution package:
- Connection Interfaces Javadocs package
- Developer's Guide (PDF)
For more information about XMLA, see:
|