Editing BI XMLA System Properties
Use
The BI XMLA (XML for Analysis) system template provides business intelligence functionality to systems you create based on XMLA-compliant OLAP data sources such SAP BI systems 3.0A or greater, or Microsoft Analysis Services, Hyperion, MicroStrategy, and MIS systems. The template for a BI XMLA system defines the specific parameters needed to connect to these data sources and contains a reference to the BI XMLA Connector. The BI XMLA system inherits these properties, some with default values, others that require the setting of values. You edit the system by inserting needed property values and by modifying default values, if necessary.
The template contains many properties, not all of which can be edited, and not all of which are necessary to establish a connection to the back-end system.
The table below lists the properties needed to create a system based on the BI XMLA system template. Each has an explanation of the value that should be set.
Procedure
...
1. From the top-level navigation bar, choose System Administration → System Configuration.
2. From Detailed Navigation, choose System Landscape.
3. In the Portal Catalog, right-click the system whose properties you want to edit, and from the drop-down list choose Open → Properties. This opens the System Landscape Editor.
4. Set your BI XMLA system properties according to the details in the table below.
Property |
Value |
Category: BI / Business Intelligence |
|
BI Directory Provider |
If Yes, specifies that this BI system is accessible from applications in the Business Explorer suite, where supported. |
Category: Connection Properties |
|
Database Name |
● Name of the database. Mandatory. ● For example, Local Analysis Server |
Server URL |
● URL for the server. Mandatory. ● For example: ○ SAP BI system XMLA provider – http://[domain:port]/ (see Note below table) ○ Microsoft Analysis Server – http://[domain:port]/ |
Statefulness |
● Indicates support for statefulness. Optional. ● Options are: ○ true – statefulness is supported ○ false – statefulness is not supported |
Category: Information |
The property values in this category are assigned during the running of the System wizard and, except for Description, Object is a Template, and System Name are not for editing. |
Description |
An optional description of the system, if one was not inserted during the running of the System wizard. |
Object is a Template |
Defines the system you have created as a template upon which you can base other systems. If selected, this sytem will appear as a template the next time you go to create a system. |
System Name |
● The name assigned to the system when running the System wizard. ● Mandatory, exists for each system. |
Category: User Management |
|
Logon Method |
Specifies authentication mechanism. The two options are: ● UIDPW - Log on to your XMLA provider using User/Password. Use this method for XMLA-based access to non-SAP BI system providers, or for User/Password access to SAP BI system providers. ● SAPLOGONTICKET - Log on to your XMLA provider using SAP Logon Ticket (supported by SAP BI system XMLA providers). Use this property if you want to use Single Sign-On (SSO) to access SAP BI systems. See note below table. |
User Mapping Type |
● Defines the type of user mapping needed for connection; who can perform user mapping ● Valid values: user/admin/admin,user For more information, see System Properties for User Mapping |
Category: Show All |
|
CodeLink |
● A reference to the portal component upon which the system is based. ● Mandatory; assigned while running the System wizard. |
com.sap.portal.reserved.system. |
● The name of the BI XMLA Connector, through which the system connects. ● It must take the form SDK_XXXX and the letters must be all upper-case. ● Mandatory when working with a connector. |
ComponentType |
● The portal component (system) you have just created. ● Mandatory; required by the system landscape service. |
System Type |
● Type of system. ● Mandatory; assigned while running the System wizard. |
● To find the URL of an SAP BI system XMLA provider:
Start transaction SE37and 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.
● To configure Single Sign-On:
If you are using the SAPLOGONTICKET authentication method, configure BI to accept user/SAPLogonTicket pairs for authentication (instead of only user/password pairs) using the procedures below:
○ Configure SSO between the AS Java and the SAP
BI system (so that ABAP accepts SSO from the AS Java) using the instructions
in the following document:
Accepting Logon
Tickets Issued by the AS Java
○ Configure SSO between the SAP BI system and
the AS Java (so that the AS Java accepts SSO from ABAP) using the instructions
in the following document:
Configuring the AS
Java to Accept Logon Tickets
5. Save your settings.
To finish configuring your system, assign an alias and, if necessary, configure user mapping. See: